I started over with everthing.

[todd1010]

I started over with a fully formatted ORIGINAL DMS, with the lastest firmware loaded and all plug-ins.

I followed the instructions again to make sure I was doing them correctly.

I'm still not getting any text in the bootload.log file I created. But here's what's written in the text file in  PHTSYS\log\patch

_________________________________________
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
backing up drive signature
2048+0 records in
2048+0 records out
backup drive sig complete
starting patch
/dos/backup/patch.sh: 8: Syntax error: Bad fd number
_________________________________________

Here's what's written in the text file in PHTSYS\log\phatpatch

_________________________________________
PhatPatch v0.2 -bushing
first 2 words of flash=c102 0025
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0004, device id=22bf
Resetting flash.
Testing patch locations:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0033 1a00    Actual: 0000 1a00
Mismatch!
Verifying:
Patch 1 @ 0bb8: make drive signature check always succeed: [bne verify_sig_failed -> bne PC+1]
Expected: 0000 1a00    Actual: 0000 1a00
Verified!
_________________________________________

I've been told that this it did sucessfully flash my phatbox, even with this.

[todd1010]

1) My next step was make a copy of my plugins folders.

2) I made a copy of the 1mb.bin file located in PHTSYS\backup.

3) I then ejected the DMS.

4) I then exchanged the OEM DMS with the new 60gb hard drive.

5) Put the "new" DMS in the cradle.

6) Went to the command prompt in Windows XP and typed in:
-----------------------------------------------------------------
c:\dd.exe if=c:\drive-sig-1mb.bin of=\\.\physicaldrive2 bs=512 count=2048
-----------------------------------------------------------------

The green light flashed on my cradle and I could hear it spin up. The in the command prompt window it went right back to:
-----------------------------------------------------------------
C:\Document and Settings\Todd>
-----------------------------------------------------------------

I didn't see any text or anything saying it was completed.

I wish someone would help me out, because this is getting aggravating. I'm lost to what I'm doing wrong.

[judb]

That appears that you are doing things right.

if you reboot your computer the DMS should be ready to use in the DMS repair CD.

[todd1010]

I went and booted up with the DMS Repair CD, hit ALT+F2, then selected repartion & reformat option.

It completely formatting my new DMS, and repartioned it. Pulled the DMS out. The boot up the PC.

Put the new DMS in the cradle, loaded the firmware first.

But when I went into my PHTSYS directory, I only had the file:  forceupdate

But I didn't have the file: forcesettings

So I deleted the one forceupdate file.

Pasted my Plugins folders to PHTSYS.

Added a couple songs in a playlist. Saved and ejected new DMS.

Went to the car, and waited for about 5 minutes for the firmware to load.

Switched on the head unit, click on CDC and it just sat there and switched back to RADIO on its own.

[judb]

I should have this boot CD metho working shortly so .. just bear with me a few minutes...

[todd1010]

Yeah I''m giving up on this method. I'll be here all day.

[judb]

I havent forgotten about you.. i am testing it out right now and running into a few minor issues that I am working out.  its slow going but I'll be done very soon.

[todd1010]

Thanks, I can't wait to try it out.

BTW, put my ORIGINAL DMS back in the casing and booted to the DMS Rescue Disk and did a complete repair, format & repartion of my Original DMS. So now I can start with fresh OEM DMS. I've already loaded on the lastest firmware and took it out to the car & let that load for about 5 minutes. Selected my correct "Radio Type".

Brought it back inside and loaded all of my plugins. So now its waiting on the Phatpatch CD your making.

Thanks,
Todd

[judb]

Cool.  I know this will work when we are done and release it because I'll have tested it on my unpatched second keg box..

There should hopefully be some progress here soon.. we ran into another kernel problem during testing but im still on it.  RobM and I will get it done ASAP.

[todd1010]

Another thing I did with my "soon to be new DMS" hard drive is I went into Disk Management and Deleted all of the Partitions. So now I'm basically back to a "Unallocated" drive. Is that OK for doing it that way or should I create a partition?

[judb]

The new DMS drive can be completly blank or full of data.. this cd will nuke whatever is or is not on the new dms.  

[judb]

http://forum.phathack.com/cgi-bin/yabb/YaBB.cgi?board=dmshack;action=display;num=1122424315;start=0#0

enjoy!