Discussion Locked

Setting up an NT4 OS

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm into the umpteenth setup process of a drive for NT4. I've only got several of these to do. I know the partition size problem, whether to use FAT or NTFS. I'm using 10gb drives, and have even used the setup for large IDE drives with the CDrom drive from SP4. I'm getting 'can't find OS', 'NT Detect failed','corrupted drive'. I need a 4gb C:drive with rest in logical FAT partitions. I've used just about every combination of setup process thinkable, with no consistent results. I've triedpartitioning and formatting prior, during and after. I'm also beginning to wonder why anyone would want NT. Would appreciate some guidance for this process.

14 replies

by mckaytech

I would check the Hardware Compatibility List to make sure the hardware you are trying to use is supported under NT (pay particular attention to the motherboard and CD-ROM drive).

I've done several hundred installs on supported hardware and had only sporadic and solvable problems. But I've had some nightmares when trying to use hardware that is not known to be compatible.

Other possibilities include an unsupported configuration (e.g. Small Business Server on Compaq servers with a system partition) or a corrupted CD or boot disk set.

paul

by barryvg

Did check the listing, was ok. System in use for final setup was already an NT. However, for some reason, it wouldn't do the setup straightforward. Using the SP4 CDrom, telling it to format as NTFS, even though the partition was setup under an NTrunning system, allowed process to continue.

by wildmcp

I had this same problem on a few of the IBM 300PL's. I set up the Primary partition, leaving the rest of the space free - loaded NT with FAT. Then once I booted up successfully the first time, I used NT to set up the rest of the drives.
Sometimesit seems as though you go round and round in circles. Microsoft, who needs 'em?! *smile*

by barryvg

Did check the listing, was ok. System in use for final setup was already an NT. However, for some reason, it wouldn't do the setup straightforward. Using the SP4 CDrom, telling it to format as NTFS, even though the partition was setup under an NTrunning system, allowed process to continue.

by jewright

Often a new drive in an old machine will require the disk to have a small portion of the disk setup to contain a BIOS. If you have either a Western Digital or a Seagate drive, the drive should have come with a floppy disk that will contain the setupprogram for this task (Either EZ-Disk or Data LifeGuard Tools).

I don't think that NT is really to blame here so much as the BIOS of the machine you are trying to setup.

I will be glad to help you. send me an e-mail if you would like. My address is JeWright@Hotmail.com

Good Luck.....Jeremy

by ec364

Your 10GB HD must have drive overlay installed. NT won't work on it. Run the drive utility and remove the drive overlay. Then reinstall Windows NT.

Enjoy!

by barryvg

Did check the listing, was ok. System in use for final setup was already an NT. However, for some reason, it wouldn't do the setup straightforward. Using the SP4 CDrom, telling it to format as NTFS, even though the partition was setup under an NTrunning system, allowed process to continue.

by calves

I have a different approach, if you care to try.
Get a Win98/Win95 Boot disk, boot from it, and run fdisk. Select option 4 and identify all the partitions on the disk. Press Esc and Select 3. Delete all the partitions. Now, boot from the set of diskettes or CD and allow the installation to create the partition. I know you can do that during the installation backup without using the Win9X and fdisk. But trust me, I seen similar problems where NT would not identify all the partitions on thedisk, but fdisk would.

Good luck!

by barryvg

Did check the listing, was ok. System in use for final setup was already an NT. However, for some reason, it wouldn't do the setup straightforward. Using the SP4 CDrom, telling it to format as NTFS, even though the partition was setup under an NTrunning system, allowed process to continue.

by uffe.sommerlund

Hey there !!!

it is a commen thing you are having trouble with you think you have formatted FAT16 but to me it seems like you have formatted with FAT32, to the cause that when you use FDISK and in the beginning say Y to enlarge disk you get FORMAT FAT 32
1 go to FDISK
2. choose N in the first screen
3. check / Display inforamtion
4. Kill the old partitions
5. create new choose default 2047GB
restart / format the drive
install Winnt

Winnt /b
from dospromt

kind regards
Uffe Sommerlund
Denmark

by barryvg

Did check the listing, was ok. System in use for final setup was already an NT. However, for some reason, it wouldn't do the setup straightforward. Using the SP4 CDrom, telling it to format as NTFS, even though the partition was setup under an NTrunning system, allowed process to continue. System was formatting as FAT ,as I oould see the NTFS conversion going on. But for some reason, it wouldn't recognize the new format. Working now and the user is happy.

by fred_e944

If the hard drive has an overlay (EZ-Drive, Drive Manager) remove it. NT puts its own stuff in the MBR, and will not install on an overlayed drive.

Delete any existing partitions

Install NT with a 4.0 GB FAT16 C: drive, no other drives or partitions. Don't worry about the size of your drive being underreported.

Apply service pack (SP4 or above)

Use Disk Administrator to partition freespace of drive into other drive letters.

by barryvg

Hope you saw other comments. Had to use overlay in order for full drive usage. Without, lost 2gb space. Formatted/partitioned in a working NT, used setup with NT-SP4 cdrom driver, when asked to what partition, said use the previoulsy formatted NTFS and reformat as NTFS. System did work that time. However, it was not astraight forward event. Many side steps. But have inmage of drive and will use it for future setups. I've several to do. Thanks.

This discussion is closed to new replies.