• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

chkdsk /f from boot disk?

mcveigh

mcveigh

Diamond Member
I recently had my old KT266a motherboard due with win2k on it. I had an old P4 1.9 layinh around so I got a new 845 based motherboard. I hooked up everything expecting to bootinto safe mode uninstall the via drivers and install the new intel ones but I get a blue screen saying inacessable boot device and to do chkdsk /f on it.


is there a way to use a bootable disk to run fdisk /f? everything I've tried has failed.

tonight i'm going to try removing it and mountin another computer and doing a chdsk there.
 
Originally posted by: mcveigh
I recently had my old KT266a motherboard due with win2k on it. I had an old P4 1.9 layinh around so I got a new 845 based motherboard. I hooked up everything expecting to bootinto safe mode uninstall the via drivers and install the new intel ones but I get a blue screen saying inacessable boot device and to do chkdsk /f on it.
is there a way to use a bootable disk to run fdisk /f? everything I've tried has failed.
tonight i'm going to try removing it and mountin another computer and doing a chdsk there.
Click to expand...

Chkdsk isn't going to matter, you don't have the right drivers for the drive installed (at least it sure sounds that way). I'd boot the 2k cd and do a install ontop of the current config, should redetect the HW and fix it.

Bill
 
boot to a 2k cd, select R for repair and C for recovery console. Run a chkdsk /p from recovery console.
U can do it with a xp or 2k3 cd as well.

 
Originally posted by: Smilin
boot to a 2k cd, select R for repair and C for recovery console. Run a chkdsk /p from recovery console.
U can do it with a xp or 2k3 cd as well.
Click to expand...

Chkdsk isnt' going to matter....
 
It might very well.

Depends on where the Stop 7B is occuring. If immediate he has a hardware or incorrect driver problem. If it happens partially through the splash screen it's likely a disk corruption or filter driver problem. He's jumping from a via to an intel ide driver so the cards are stacked against him for sure.
 
Originally posted by: mcveigh
I know I have switched hard drives and motherboards before but I don't think I've gone amd to intel before.

I took my driv eout and attached it as a usb drive to another pc and ran chkdsk /f still no luck so I guess I have to reinstall.

smilin:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/proddocs/bootcons_chkdsk.asp

chkdsk /p only looks for bad areas, the /f command isn't available don't know why, and /r is supposed to repair but no luck.
Click to expand...

The /f switches forces the drive to be locked (or ask for a reboot if it can't be). Since your booting from the recovery console, there are no locking issues so the /f switch is pointless (thats why it's missing). It wasn't for some additoinal test that you might have otherwise needed.

Bill
 
This can be fixed without doing repair or reinstall did it the other day on an xp hd.
U just have to add the correct drivers to the disk . give me a few min. and I will find the page that describes how to do it.

Boot up the old machine to Windows 2000.
Extract the driver files Atapi.sys, Intelide.sys, Pciide.sys, and Pciidex.sys from %SystemRoot%\Driver Cache\i386\Driver.cab on a machine running Service Pack 1, or from the Service Pack 1 installation disc, and copy them to '%systemroot%\system32\drivers' on the problem machine. You can download these drivers, and the REG file required in the next step, from here. drivers and reg file
Apply the registry file IDEdrivers.reg
Close down the machine.
Replace the new motherboard.
The machine should now boot past the Stop 7B error previously experienced.
 
Originally posted by: mcveigh
I know I have switched hard drives and motherboards before but I don't think I've gone amd to intel before.

I took my driv eout and attached it as a usb drive to another pc and ran chkdsk /f still no luck so I guess I have to reinstall.

smilin:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/proddocs/bootcons_chkdsk.asp

chkdsk /p only looks for bad areas, the /f command isn't available don't know why, and /r is supposed to repair but no luck.
Click to expand...

Chkdsk /p from the recovery console is the command used in place of chkdsk /r from within the OS. In both cases, /F is implied.
 
haha. Sh1t.

I just read that link. It's WRONG. I'll have to look into that. D'oh!!!
See my last post for correct answer.
 
If you are still having the problem, what are the parameters to the stop code? There are several reasons you could get a stop 0x7b.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top