Locked files after switching to 2.25

[usc45cal]

these were my files and not locked before ???? im screwed has this happened to anyone else

[caesar]

You will get that error because 2.25 does not yet support tunerlocked or custom operating system files.

[usc45cal]

My fault for not reading an email from Mr Henn sorry bill

[MikeOD]

You really shouldn't use 2.25 for any GM stuff yet...if you don't need to do your own segment swap, just keep your 2.24 updated for vehicle support and new tables and whatnot.

When we all used 2.23 before 2.24...we had to use the beta because 2.22 was not updated for new vehicles. They had to give everyone the beta all the time for anything new. 2.24 is updated all the time though for the vehicle support. I use it exclusively, unless I'm working on a Coyote Mustang.

Even if you need your own segment swap in a GM vehicle...use 2.25...swap the segment...then flash the car with 2.25, and read it back out with 2.24 and continue tuning.

[Bill@HPTuners]

You really shouldn't use 2.25 for any GM stuff yet...if you don't need to do your own segment swap, just keep your 2.24 updated for vehicle support and new tables and whatnot.

When we all used 2.23 before 2.24...we had to use the beta because 2.22 was not updated for new vehicles. They had to give everyone the beta all the time for anything new. 2.24 is updated all the time though for the vehicle support. I use it exclusively, unless I'm working on a Coyote Mustang.

Even if you need your own segment swap in a GM vehicle...use 2.25...swap the segment...then flash the car with 2.25, and read it back out with 2.24 and continue tuning.

You'll find more and more applications & features only being supported in 2.25 moving forward ie virtual ve, segment swapping as you mentioned, 2014+ gm's, 2010-2011 Camaro v6, etc. so more and more people will be switching over due to this reason alone.

[usc45cal]

Thanks for the reply bill it was very informative