General discussion


The old "won't boot" problem

By dlturman ·
Ladies and Gentlemen, this is my first post and it should be a doozie. I was tryimg to upgrade an old 500mH Pentium 2 computer to Win2000Pro. I went with an upgrade even thogh I had the full version to save from copying every file to zip disk and reinstalling them. Everything seemed to be going fine until the system rebooted for the last time. It just kept rebooting in an endless loop where it tries to install devices etc. To make a long story shorter now all I get is a stop screen with the errors:c0000s6c unable to load device driver and 0xc0000221 system root\system32\drivers\ks.sys. I've gone through all the online fixes I can find and the MS Knowledge base, but all I get are the blue death screens. I can't even get to a comand prompt to look at the disk contents. Boot to Safe Mode and boot with Comand Prompt leads me back to the BSOD. Booting with a floppy won't show the C: drive therefore FDISK won't work. Is there a magic "bullet" I can try before I resort to the real bullet? To pull this off sure would make my benefactor happy.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by mjd420nova In reply to The old "won't boot" prob ...

It seems that you may have an incompatability
with the hard drive formats between your previous
OS and the new WIN2KPro. That's why the floppy
boot routine can't see the hard drive.

Collapse -

by Bear531 In reply to The old "won't boot" prob ...

I never had much lick with doing the upgrade from Win2000 pro try reinstalling this time using the full install.

Collapse -

by CG IT In reply to The old "won't boot" prob ...

some older BIOSs and Chipsets on older motherboards aren't compatible with W2K. You'll get a stop message that indicates a system error with a memory dump and a notice to reboot the computer or contact the system administrator. check to see if there is a BIOS update for the motherboard that provides W2K compatibility and/or newer chipsets.

Collapse -

by HAL 9000 Moderator In reply to The old "won't boot" prob ...

I think that you'll find FDISK does actually work but if isn't reconsigning the NTFS Partition if you run FDISK can it see a HDD with a Non DOD partition? Option 4 or 5 from memory can delete non DOS partitions I use this all the time when wanting to delete Nix HDD's.

If you can not see a HDD at all with FDISK your HDD has died but it is quite common with NTFS partitions that you get a message that there is no HDD in the computer and you could have a Virus Infection or that some 3rd Party Disk Managers may make the drive unreadable that is the way it should be.

I've never had much joy with Upgrades either they always seem not to work properly when there is a copy of Windows already on the drive. The only time I now use an Upgrade is when that's all that the customer has so I wipe the HDD and reinstall the OS from the Upgrade CD, it reaches a point where it asks for a copy of the Older Windows CD so I just pop in a Win 98 SE CD and then allow the setup to continue with the Upgrade CD.

Whenever you are doing anything big to Windows like applying a Service Pack or an Upgrade you should always BACKUP your critical Data and then proceed with a clean blank HDD.

If you have not done that in this case you may be able to recover your data by removing the HDD from the existing computer and fitting it into another computer as a Slave or even in a USB Caddy and see if you can read it buy that computer that you use for this will have to be able to read NTFS Partitions so that means NT Y2k or an XP unit. I actually prefer a USB Caddy as these are simple to use and don't require any work at all to fit a drive to and see if it's readable.

Collapse -

by HAL 9000 Moderator In reply to

If you can recover your data don't forget the E-Mail as with changes to the Anti Terror Laws it is vital to keep every sent E-Mail just in case someone changes the content of one of your e-mail to something nasty and forward it on, without the original you are in for a world of hurt and it is impossible to prove that you didn't send the modified e-mail.


Collapse -

by dmiles In reply to The old "won't boot" prob ...

It seems that you have an hardware file that is corrupt,so try the following
This procedure can be used to replace any Windows NT system file. In this example we replace the file \WINNT\system32\drivers\beep.sys.
NOTE: To use the NT V4.0 Emergency Repair Disk utility, you must have the updated version of Setupdd.sys. The updated version is contained in NT v4.0 Service Pack 2 or later.

For more information, please see the following article(s) in the Microsoft Knowledge Base:
ARTICLE-I 168015 (
TITLE : Files Not Replaced When Running Emergency Repair.
1. The Emergency Repair Disk is created during the initial Setup of Windows NT, or by running the Windows NT RDISK.EXE program. Copy the contents of the original ERD onto another diskette or subdirectory on another machine as a backup. The original ERD information saved should be restored unmodified to the original ERD in case this procedure is unsuccessful or there is ever a need to return to the configuration that was originally saved.
2. Remove the read only attribute on the Setup.log file. This is a hidden, system file on the ERD that can be edited with a text editor. Alter the Setup.log file as in the sample below, replacing the entire [Files.WinNt] section with an entry like the last line in the example. Additional lines can be included if more than one file needs to be copied. The [Files.WinNt] section of Setup.log contains an entry for every Windows NT operating system file. When creating or modifying the entry make sure the target folder for the file is the same as the TargetDirectory value in line one of the [Paths] section. The target folder corresponds to the Windows NT systemroot.

This can easily be done by finding and modifying the original line for the target file in the [Files.WinNT] section.

If this does not work you will need a Windows 98 startup disk to perfor fdisk on the partition for a fresh install

Collapse -

by dlturman In reply to The old "won't boot" prob ...

Thanks everyone for the suggestions. I think I will try and set it up in an XP machine and see what happens first. I let you know the results soon. DT

Collapse -

by Neil Cotton In reply to The old "won't boot" prob ...

What OS was it running originally, was it FAT32 by anychance, with 2k now needing NTFS.

Collapse -

by Neil Cotton In reply to The old "won't boot" prob ...

What OS was it running originally, was it FAT32 by anychance, with 2k now needing NTFS.

Collapse -

by sgt_shultz In reply to The old "won't boot" prob ...

did you see this?
Setup from the 16-Bit Winnt.exe File Continues in an Endless Loop;en-us;282296

Related Discussions

Related Forums