At my wits end!Someone please help!!

[dafamous12]

The manual method still requires using the boot disk and my problem is my machines freezes when I put the dms into the cradle.Let me start over and explain. I can boot to the disk and after the startup script it goes to the main screen. At the bottom before I insert the dms in green letters is "at input device keyboard ".Sorry I will run it again to get it all on what it says.Anyway when I insert the dms it will lock up and I have hold the power button to do a hard restart. If anyone has any clues to what is going on I will be very interested to hear from you. Also, my machine is a toshiba a65-s126 2.8ghz celeron.

[skew]

use this disk insted http://unix.phatnoise.com/bootdisk.php But if your computer won't work on the hack cd chances are it won't work on the phatnoise cd but give it a shot anyway. If it doesn't work then you will have to try a different computer.

[dafamous12]

I'm making the cd as we speak. Also here is the full text in green on the startup screen "input: At Translated Set 2 Keyboard on isa0060/serio0.

[dafamous12]

Nope, machines still freezes when I insert the dms into cradle.I really about to cry!! I don't have access to another machine.I'm a long haul trucker from Ft Worth,Tx and I'm in Oregon at the moment.Can you think of any reason it freezes when I insert the dms??

[judb]

See if there is a bios update for your laptop... perhaps theres something weird with the USB support for that laptop that is causing both discs to freeze your computer.

[skew]

If you can not use another computer then you may try picking up a cheap  pccard
 to usb card and use the pcmica bus insted of your laptops bus

[dafamous12]

Ok, got on another machine everything goes fine until it gets to backing up physys then I get scsi error <0 0 0 0> return code = 0x06000000. What now?!?!?!?!!?!?!??

[judb]

I suggest running a scandisk / chkdsk on the phtsys and phtdta partitions in windows.  sounds like a drive / filesystem error

[dafamous12]

what scan disk program do you suggest?

[judb]

chkdsk (command line program)

chkdsk Z: /f

where z: is your phtsys and pthdata drives.. you'll need to run it twice, one time for each drive.

[dafamous12]

Ok,I did the manual patch because I was ready to pull my hair out and since I shave my head that would prove fruitless. How will I know if the patch took? I did not see a bootload.log file in either sys or data

[dafamous12]

I saw this in one of the log files called patch.log
"backing up drive signature
backing up drive signature
backing up drive signature
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"

And I saw this in phatpatch.log "PhatPatch v0.2 -bushing
first 2 words of flash=c102 0025
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0020, device id=0057
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!

Also saw one that said error.log "CORRUPT_FILE: /dev/null"


So what does it all mean???

[judb]

can you post the full contents of each log between [ code ] and [ / code ]

Just remove the spaces from that..

it should make the post look

Code Select Expand

like this


[dafamous12]

This was in patch.log

Code Select Expand

backing up drive signature
backing up drive signature
backing up drive signature
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
 
This was in error.log

Code Select Expand

CORRUPT_FILE: /dev/null
And this was in phatpach.log

Code Select Expand

PhatPatch v0.2 -bushing
first 2 words of flash=c102 0025
writing auto-id command (AA, 55, 90)
Flash chip reports manufacturer id=0020, device id=0057
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!


[dafamous12]

can anybody tell me based on the logs above if my box was patch?

[dafamous12]

Ok,found out the patch was successful . Now I'm stuck on dd for windows.Can someone take me through it step by step.I would do it with the cd but my laptop is being a jerk about it.

[judb]

Did you download dd yet?

extract the dd.exe to c:\

Do you know the physical drive number for the DMS?

Run Disk Administrator (start menu - run - c:\windows\system32\diskmgmt.msc )

Find the drive that has the phtsys and phtdta on it, and note the drive number listed on the left hand side..  it is important to use this number when running the DD command so you don't screw up your PC.

Do you see a file in phtsys in the backup folder called drive-sig-1mb.bin ?  Copy that file to your c:\ directory as well.

Eject your old DMS.. Put in the new drive in the DMS case and place the new DMS back in the cradle.

run command prompt (start menu - run - cmd.exe)

Type this command but replace the X at the end of physicaldriveX with the number you found in Disk Managment. VERY IMPORTANT TO GET THIS RIGHT!!!
(typing in the wrong disk number could crash / ruin data on other drives so BE CAREFUL AND BE SURE)

dd if=c:\drive-sig-1mb.bin of=\\.\physicaldriveX bs=512 count=2048

Eject the DMS after doing this.. You'll have to reboot and use the format utilty to repartition the DMS and reformat it (this is the NEW DMS) but it should now work great in any phatbox that has been patched.

If you cannot get the Phatnoise version of the Boot CD or our version of the Boot CD to work, I am quite sorry but you are foobared.. theres no real way I can tell you how to simply reparition and reformat the DMS in any other OS than by using one of those bootable CD roms.

I might suggest if you still have issues with the boot cds that you download vmware from www.vmware.com as an evaluation, install it.. configure a guest OS of linux with a 256 meg hard drive on it (this is a fake drive that is really a file on your hard drive not another hard disk for real) and then you can redirect your USB cradle and CD drive into the vmware machine and try using it to get around any usb issues you may be having.

[dafamous12]

how do I get the command line prompt to just say c: . Mine says

Code Select Expand

c:\doucments and settings\dafamous12\desktop

[judb]

type
cd \

[dafamous12]

I'm getting an error code

Code Select Expand

Error opening output file: 2 The system cannot find the file specified