DMS Hack not working!!!

[Triumphboy]

I've tried using the CD Hack to enlarge my DMS up to 80gb using a Toshiba disk

The Hack seems to work with the voice informing me that the hack has been done, but when I put the new disk in the headunit thinks about it for about 30 seconds and then displays 'Eject'

It's a Kenwood Keg and Headunit BTW

I've done as far as I know everything right and the old 10gb still works so what am I doing wrong?

Do I need to reset the stereo like I would if I had updated the firmware.

If that doesn't work, then what?

BTW the cradle is a USB 1.1 , does that make a difference?

[skew]

did you install the latest firmware on the 80gig?

[Triumphboy]

Not yet, do I need to?

[Triumphboy]

Right

Tried loading firmware onto new disk and running PN

Red light comes on, Display shows Loading

Then Eject

So no joy

Any ideas?

[judb]

try searching on ramdisk.sig corrupting...  that may help.

[Triumphboy]

Tried searching on that , but not found a post that made sense.

I know it says about replacing the ramdisk.sig file but what with?

[sbingner]

Tried searching on that , but not found a post that made sense.

I know it says about replacing the ramdisk.sig file but what with?

Just replace it with any OTHER .sig file and you'll be good

ie. copy initrd.sig to ramdisk.sig

[sbingner]

Judb: you should update the hack cd to corrupt the ramdisk.sig right after the hack to modify the ramdisk return expected (second to last), then fix it once the final hack is applied (last one)

If you need I can update the hack to be called as "apply 1" "verify 1", "apply 2", "verify 2" etc

[Triumphboy]

Right ok, so now I know how to do the sig file.

Is this done on the good DMS after flashing the PN or on the new DMS?

[judb]

the good dms doesn't work either I would expect... so you'll hvae to do it there to re run the hack.. this should then enable the new DMS to work.

[judb]

Judb: you should update the hack cd to corrupt the ramdisk.sig right after the hack to modify the ramdisk return expected (second to last), then fix it once the final hack is applied (last one)

If you need I can update the hack to be called as "apply 1" "verify 1", "apply 2", "verify 2" etc

Yeah, we can try and make things a little more obvious and easy to understand for the lay person..

I was thinking that it might be helpful to put in some text about where in the process it was instead of the expected > 0x333 stuff that most people don't follow.

That way the patch verify and patch logs are readable by everyone.

I'll update the scripts accordingly.. perhaps have the script verify that the patch was completed before building the new DMS?

I just worry about the size of the files as we were running out of space to fit on a single boot floppy.

[Triumphboy]

Ok, so still no joy.

This is what I've done

Rum CD on good DMS
Installed in car
Car said patch completed
Took DMS out and altered ramdisk.sig as advised
Replaced DMS in car
Car said patch completed
Swapped DMS over for new one
Car rejects new DMS
Tried changing ramdisk.sig in car
No joy there
Remembered post about aadec.sig, so changed that like ramdisk.sig
Put DMS back in car and guess what........?


It works

Hurray

Thanks guys for all the advice. Maybe we could do a complete how-to with all the possible problems covered?

[sbingner]

Ok, so still no joy.

This is what I've done

Rum CD on good DMS
Installed in car
Car said patch completed
Took DMS out and altered ramdisk.sig as advised
Replaced DMS in car
Car said patch completed
Swapped DMS over for new one
Car rejects new DMS
Tried changing ramdisk.sig in car
No joy there
Remembered post about aadec.sig, so changed that like ramdisk.sig
Put DMS back in car and guess what........?


It works

Hurray

Thanks guys for all the advice. Maybe we could do a complete how-to with all the possible problems covered?

Sounds like you had a plugin problem - removing your plugins directory from the new DMS would probably have fixed it also