 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows NT / Setup / January 2006NT installation problems
Hello My hard drive has the following hard drive structure: Primary Partition 1 - FAT32 (1 GB) Primary partition 2 - NTFS (Windows 2000) - 3.5 GB I would like to install Windows NT 4.0 Workstation onto partition 1. After logically formatting partition 1 as FAT32, i set it as the active parttion and reboot to the NT setup disks I select partition 1 as the installation partition and i get the message: "Setup was unable to format the partition. The disk may be damaged. Make sure the drive is switched on and properly connected to your computer. If the disk is a SCSI disk, make sure your SCSI devices are properly terminated. Consult your computer or SCSI adapter documentation for more information. You will have to select a different partition for Windows NT. Press ENTER to continue. " I tried deleting partition 1 and creating an identical one in its place, but i got this message: " Setup has encountered a fatal error that prevents it from continuing. Contact your prodct support representative for assistance. The follwoing status codes will assist them for diagnosing the problem <0x5, 0, 0x1> " What am I doing wrong? Any advice would be appreciated. Martin Not possible. Your choices are fat16 or NTFS  SignatureRegards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect | Hello | [quoted text clipped - 31 lines] | | Martin Hi Dave I've tried FAT16 and got the same error message. Any other suggestions? Martin > Not possible. Your choices are fat16 or NTFS > [quoted text clipped - 35 lines] > | > | Martin What drive controller are you using? If the drive controller is not natively supported then you'll want to boot the Windows NT setup disks or CD-Rom. Then *F6* very early and very important (at setup is inspecting your system) in the setup to prevent drive controller detection, and select S to specify additional drivers. Then later you'll be prompted to insert the manufacturer supplied Windows NT driver for your drive's controller in drive "A" If you wait and then S to specify additional drivers, then it may be too late as Windows NT Setup at this point may have already assigned the resources your drive's controller is wanting to use. SignatureRegards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect | Hi Dave | | I've tried FAT16 and got the same error message. Any other suggestions? | | Martin Hi Dave I've got a Maxtor 2B020H1 20GB IDE Disk. Does this mean i need to follow your advice? > What drive controller are you using? If the drive controller is not natively > supported then you'll want to boot the Windows NT setup disks or CD-Rom. [quoted text clipped - 12 lines] > | > | Martin The drive probably doesn't matter whereas the drive controller does matter. SignatureRegards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect | Hi Dave | I've got a Maxtor 2B020H1 20GB IDE Disk. Does this mean i need to follow | your advice? Oh......i'll do some research and follow your advice. Thanks again. Martin Placek > The drive probably doesn't matter whereas the drive controller does matter. > > | Hi Dave > | I've got a Maxtor 2B020H1 20GB IDE Disk. Does this mean i need to follow > | your advice? You're welcome. SignatureRegards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect | Oh......i'll do some research and follow your advice. Thanks again. | Martin Placek he said: " Primary partition 2 - NTFS (Windows 2000) - 3.5 GB " might be problem since 2000 has Newer version of NTFS that NT-4 cannot recognize Until Service Pack 6a is installed ... ?? he said: "Maxtor 2B020H1 20GB IDE Disk" oops forgot about that Gotcha until in earlier post, Dave-P said: "You'll need atapi.sys from SP4 or later for Windows NT to be able to recognize a drive larger than ~ 8 gB" It won't matter until sometime later since the partition presumably will be created by Windows NT setup. The OP should apply SP6A and rollup before starting up Windows 2000 SignatureRegards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect | he said: | " Primary partition 2 - NTFS (Windows 2000) - 3.5 GB " | | might be problem since 2000 has Newer version | of NTFS that NT-4 cannot recognize Until | Service Pack 6a is installed ... ?? Hi Placek, Since your drive is over 7.8GB in size the problems associated with large I.D.E. hard disks and NT4 will probably surface. Read http://nt4ref.zcm.com.au/bigdisk.htm for further details. Calvin. >Read http://nt4ref.zcm.com.au/bigdisk.htm for further details. > >Calvin. Calvin, Thanks kindly for the link and the excellent set of pages. I just read the USB page and the IONetworks release allows me to use my flash drive in NT4. Previously I had to boot to W98 or W2k for this. Amazing !!! Thanks again, Steven Hi Steven, Glad the IONetworks code helped you - it is a first class coding effort from people who obviously KNOW what they are doing !! It just goes to prove conclusively what a crock Microsoft's claims that USB couldn't (read we couldn't be bothered) be added to NT4 :-( Calvin. Calvin, >Glad the IONetworks code helped you - it is a first class coding effort from >people who obviously KNOW what they are doing !! Yes, I read their webpage after I installed the drivers. The detail is impressive and they even allowed for users migrating to NT5. Another good feature (compared to W98) is that I don't need drivers for each different flash drive. I have a 430TX chipset and have previously tried the R62200 package and the code from Woodhead. I couldn't get the R62200 code to do anything. The Woodhead code just caused a system halt when I connected any device. I assumed the problem was due to my old chipset. -- Steven > I have a 430TX chipset and have previously tried the R62200 package and > the code from Woodhead. I couldn't get the R62200 code to do anything. > The Woodhead code just caused a system halt when I connected any device. > I assumed the problem was due to my old chipset. Hi, the older chipsets were known to cause problems on a lot of the NT4 USB solutions offered. The R62200 Dell solution is in fact an earlier build of the IONetworks stuff. I have the opposite problem here - which I believe is caused by compatibility problems with my video card or sound card drivers - the older IONetwork drivers work perfectly, the newer builds, which have changed the driver structure and introduced a new system level driver (ionpnp.sys) don't work here and blue screen the system :-( Oh well, you can't have everything - I'll stick to the older drivers ! Calvin. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.