Huge problem with BuildOS - Can't flash N2C-5067 anymore!

[?GotJazz?]

This is really, really bad for me! N2C-5067 is the most stable/reliable ROM I have found yet.

I have far fewer Bluetooth problems with N2C-5067, whereas almost every other ROM I have ever tried has random Bluetooth disconnects with my car every few minutes.

I now get an error that my N2C-5067 is Version 90.01, but needs to be 90.02.

How do I set up BuildOS to support flashing my old N2C-5067 configurations?

Thanks ...

¿GotJazz?

[reeg420]

oh must be the same problem as with the nuerom3 kitchen...

Give me a minute and Ill edit the kitchen_config file for no2chem's 5067 and Ill edit this post with it.

Add it to the 5067 rar file in the kitchens directory...

Actually I just looked at mine... And it calls for the right kitchen version... Dont know maybe you didnt update all the files on the last kitchen update.

Well heres the txt file by itself. Should work. You will need winRAR to add and repack this into the Titan_No2Chem_5067_WM6.1.rar. Either that or update the 5067 kitchen rar from ppckitchen.org or the updater. If its even available. I dont even check I update everything.

[?GotJazz?]

reeg420 - Unfortunately, I tried using your updated kitchen_config.txt file after upgrading BuildOS. I know - I was stoopid.

Of course, your patched kitchen_config.txt file was not usable with the new version of BuildOS. I tried changing "KitchenConfigVersion=.90.03", but apparently there was a new parameter on the "OSInfo=Titan,WM6.1,8855A,64B0000064000000????????0 000,true,00001000" line: I got a "Argument 'Length' must be greater than or equal to zero." error.

Oh, well.

¿GotJazz?

[gguruusa]

Originally Posted by ?GotJazz?

reeg420 - Unfortunately, I tried using your updated kitchen_config.txt file after upgrading BuildOS. I know - I was stoopid.

Of course, your patched kitchen_config.txt file was not usable with the new version of BuildOS. I tried changing "KitchenConfigVersion=.90.03", but apparently there was a new parameter on the "OSInfo=Titan,WM6.1,8855A,64B0000064000000????????0 000,true,00001000" line: I got a "Argument 'Length' must be greater than or equal to zero." error.

Oh, well.

¿GotJazz?

lol - you're in a rush. Slow down.

It is foolish of you guys to just think that changing the version number at the top is a good idea, or even to change other lines without understanding what you are changing. The version number changes because something material changed in the way the file is used.

OSInfo=Titan,WM6.1,00001000,64B0000064000000?????? ??0000pp,pp,tt,Static,0,0,16,1

[edit: interesting....if you see any spaces in the osinfo line above, they're rendering defects and should be removed.]

[?GotJazz?]

gguruusa - Yeah, I know that changing just the version number alone might have been risky. I write code for a living (amongst lots of other stuff). I was just hoping that since the "minor rev" indication on the version number was changed, the file format itself was unchanged. Usually in the past I have seen minor rev increments when the supporting file/database structure is unchanged, and major rev changes when the "infrastructure" has changed.

Since I'm not on the "inside track" of PPC Kitchen development, I don't know what the changes are. So, I thought I would give the version number change a shot first. If there was any problems (which there was), I expected that I would see the problem sometime during the build process.

BTW, your updated OSInfo configuration line did the trick!

Cheers!

¿GotJazz?

PS: I hope N2C-5067 will still be supported in future updates to BuildOS. I alway enjoy trying out all the new stuff y'all are working on, and am eagerly awaiting a build that works as stable for me as N2C-5067. If N2C-5067 isn't going to be supported for future BuildOS versions, I guess I'll have to stop my updates to ensure I can always get back to N2C-5067.

[gguruusa]

Originally Posted by ?GotJazz?

gguruusa - Yeah, I know that changing just the version number alone might have been risky. I write code for a living (amongst lots of other stuff). I was just hoping that since the "minor rev" indication on the version number was changed, the file format itself was unchanged. Usually in the past I have seen minor rev increments when the supporting file/database structure is unchanged, and major rev changes when the "infrastructure" has changed.

Since I'm not on the "inside track" of PPC Kitchen development, I don't know what the changes are. So, I thought I would give the version number change a shot first. If there was any problems (which there was), I expected that I would see the problem sometime during the build process.

BTW, your updated OSInfo configuration line did the trick!

Cheers!

¿GotJazz?

PS: I hope N2C-5067 will still be supported in future updates to BuildOS. I alway enjoy trying out all the new stuff y'all are working on, and am eagerly awaiting a build that works as stable for me as N2C-5067. If N2C-5067 isn't going to be supported for future BuildOS versions, I guess I'll have to stop my updates to ensure I can always get back to N2C-5067.

The version numbers change when the prior file definition no longer works.

5067 will be available until a suitably stable replacement is available.

[jazaddict]

It is foolish of you guys to just think that changing the version number at the top ... or even to change other lines without understanding

Hey hey hey....NOW you've gone too far....that changin **** I don't understand IS WHERE I LIVE BUCKO!
Why do you hate stoopid people?