One more try, please help.

[CtrlAltDel]

Hi All,
I will give one more try to upgrade hdd-space in my Kenwood Phatbox.
I ran the boot cd V1.5 succesfully on my old 10GB hdd, before inserting it
into my Phatbox I have checked itīs content and found that:
The new playlist p0.m3u is located under partition phtsys/backup/ (1st pic)
and the old playlist(s) still excist under partition phtdta/profiles/default (2nd pic)

Is this correct? Because it my Phatbox doesnīt seem to get patched...

[judb]

check the phtdta\profile\profile.ini and see if the startup sound is specified...

that is how we are doing it now, not by playlist.

Also you should check the logs in the log directory on phtsys to see.. sometimes you have to do the hack several times (restarting the phatbox each time).

[CtrlAltDel]

profiles.bak:

[profiles]
active_profile=Default
enable_special_discs=1
enable_voice_prompts=1
num_discs=4

[product]
product_name=PhatNoise Music Manager
product_version=2, 3, 0, 0

[Default]
pattern=$Artist$ - $Title$
startup_sound=
num_discs=4

profiles.ini:

[Default]
num_discs=30
startup_sound=/dos/Music/flactemp.flac
pattern=$TITLE$ - $ARTIST$
album_seek=alpha

[profiles]
active_profile=Default
enable_special_discs=1
enable_voice_prompts=0
num_discs=30

[product]
product_name=PhatNoise Media Manager
product_version=3, 5, 1, 0


directory of flactemp.flac: phtsys/music/  (by the way, flactemp.flac is 0 bytes!)



Does above look right for you?

[judb]

yes that is correct.  the file doesn't have to be big, just exist for the hack to be executed.

[CtrlAltDel]

after running the entire process again i have following results:

when I inserted old dms to flash, the red and green lights start blinking for only some seconds, after
switching on HU, it  starts playing 1st song of 1st playlist but with major problems which sounds like skipping.
Because I donīt know if either the box got successfuly patched or not, I finished process on the new
dms and put it into the box. it starts reading from the new dms but it ends with
endless flashing of red and green light.
The HU doesnīt recognize the box anymore.

old dms bootload.log says: all successful

new dms bootload.log says: BOOT0-1: OK
                                         BOOT0-2: Failed


patch log files from old dms can be found here:
http://www.yourhifi.de/phathack/patch.log
http://www.yourhifi.de/phathack/patchverify.log

appreciate any help

[judb]

The patch is not complete.. run it a few more times.

[CtrlAltDel]

still same result

 new dms bootload.log says: BOOT0-1: OK
                                        BOOT0-2: Failed


iīm running out of ideas

[judb]

I don't believe that the patcher is really patching your box.  did you check the log after you re ran the patch to make sure that it is applying?

[CtrlAltDel]

Thats my feeling to  

Iīm sorry but we have to continue next week, Iīm going to travel for
some days starting tomorrow, just getting my phatbox back to work
with old dms cause I will spent appr. 25hours in my car next 5 days.  :-/
so far many thanks, I will come back to this matter soon.

[TommydCat]

I seem to be in the same boat here...
The logs from the original DMS show that the patching went successful and the verification checked out ok as well.

I put in the new DMS and it sits there for a bit (solid red light, steady blinking green light) then it powers off and I get EJECT on the head unit.  Log looks the same as above as well.

The old DMS drive is a 10gig Toshiba and the new one is a 30gig Toshiba (taken from a working laptop).  Both drives appear fine when in the cradle.

Could there be something specific about the 30gig Toshiba it doesn't like?  Where to look?

[TommydCat]

From original DMS log:
: No such file or directory
2048+0 records in
2048+0 records out

hdparm - get/set hard disk parameters - version v3.9

Usage:  hdparm  [options] [device] ..

Options:
 -a   get/set fs readahead
 -A   set drive read-lookahead flag (0/1)
 -c   get/set IDE 32-bit IO setting
 -C   check IDE power mode status
 -d   get/set using_dma flag
 -D   enable/disable drive defect-mgmt
 -E   set cd-rom drive speed
 -f   flush buffer cache for device on exit
 -g   display drive geometry
 -h   display terse usage information
 -i   display drive identification
 -I   read drive identification directly from drive
 -k   get/set keep_settings_over_reset flag (0/1)
 -K   set drive keep_features_over_reset flag (0/1)
 -L   set drive doorlock (0/1) (removable harddisks only)
 -m   get/set multiple sector count
 -n   get/set ignore-write-errors flag (0/1)
 -p   set PIO mode on IDE interface chipset (0,1,2,3,4,...)
 -P   set drive prefetch count
 -Q   print out the drive id only (60bytes\n)
 -q   change next setting quietly
 -r   get/set readonly flag (DANGEROUS to set)
 -R   register an IDE interface (DANGEROUS)
 -S   set standby (spindown) timeout
 -t   perform device read timings
 -T   perform cache read timings
 -u   get/set unmaskirq flag (0/1)
 -U   un-register an IDE interface (DANGEROUS)
 -v   default; same as -acdgkmnru (-gr for SCSI, -adgr for XT)
 -V   display program version and exit immediately
 -W   set drive write-caching flag (0/1) (DANGEROUS)
 -w   flush os cache and wakeup drive
 -X   set IDE xfer mode (DANGEROUS)
 -y   put IDE drive in standby mode
 -Y   put IDE drive to sleep
 -Z   disable Seagate auto-powersaving mode
PhatPatch v0.4 - original code by bushing, additional patches by sbingner
Verifying:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 2 @ 0bec: make rc.sh signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 3 @ 0c20: make phatd signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 4 @ 0c54: make linux signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
Patch 5 @ 0354: make ramdisk invalid signature return 0 instead of 0xFFFFFFFF: [movlne r0, 0xFFFFFFFF -> movlne r0, #0]
Expected: 0000 13a0    Actual: 0000 13a0
Verified!
Patch 6 @ 0c80: make ramdisk signature check verify 0 instead of 1: [cmp r0, #1 -> cmp r0, #0]
Expected: 0000 e350    Actual: 0000 e350
Verified!
Patch 7 @ 0358: make ramdisk valid signature return 0 instead of 1: [moveq r0, #1 -> moveq r0, #0]
Expected: 0000 03a0    Actual: 0000 03a0
Verified!
done
: No such file or directory
: No such file or directory
/dos/backup/patch.sh: kup/p: No such file or directory
: No such file or directory
2048+0 records in
2048+0 records out

The new DMS bootload.log just has null characters - no text...  built using the CD ISO (Alt-F2 Build New DMS), then signed using PMM

[jg123]

I had the null characters in my bootload.log file, too. I got it working today, though. I made a backup of my Plugins dir and my phatbox.ini file. I then reformatted and repartioned my original DMS with the 1.5 CD. I installed the VIOT plugin from PMM 3.76. I then ran the patch process from the 1.5 CD. This time it ran smoothly. I don't know if some old junk was gunking it up before I reformatted the original DMS, but it worked after the reformat. I couldn't get the AAC decoder back on there through PMM, so I just copied the entire Plugins folder onto the new DMS and the AAC decoder started working again! Hurray!! I doubled my space today. 8-)