Hi... I've been trying all week to install NT4 workstation on an old Pentuim 2 server. It currently has a 9gb Seagate SCSI hard disk running through a Symbios Logic SDMS v4.0 SCSI adapter. I get to the screen just before beginning install and get a warning saying that 'Your hard disk drive has over 1024 cylinders...' and then shows a screen with my HDD shown but 'unable to access device' written beneath it. I've tried disabling the SCSI adapter, tried all the Symbios drivers I can find and nothing seems to work. Any help appreciated...

Hi Tom, I assume the SCSI is your only drive. Someone here posted a tidbit saying that NT would not work on FAT32. Only FAT16 or NTFS. Try this: Boot on a DOS floppy. Partition and format a FAT16. copy the CD:\i386 to c:\i386 run c:\i386\winnt M2 If at first you don't succeed, you're about average.

Thanks, i'll give it a try

If trying to install NT to the whole 9Gig as a single (Primary) partition - you get the error your describing... NT can only create a Primary partition upto 4Gig max (fat16 or ntfs) during setup. It cannot create anything larger. If NT is to be installed as ntfs it will first install itself as fat16 (4Gig max) and then convert that fat16 to ntfs later... If you were to preconfigure/preformat the drive as a 9Gig ntfs single Primary partition - via another NT system - and then install NT to that preconfigure/preformatted partition it would probably go in with a little luck (and the scsi drivers and an updated atapi.sys...), however it's path to problems... If the system partition (where the boot/start-up files reside) exceeds 8Gig there is serious risk of those critical boot/start-up files migrating across the 8Gig marker - and then NT won't boot... It is not wise to install NT to a partition in excess of 8Gig (if a Primary partition) for that reason. But you could preconfigure the drive in another NT system to have Primary upto 8Gig max and then install NT there... The remaining 1Gig would become available via Disk Addmion tools for whatever? Again - do not put both system and boot-files into a Primary partition in excess of 8Gig (ntfs) and also physically further into the drive than 4Gig... However the system files (the OS itself) can go into a partition over 8Gig if it's an Extended partition/logical-drive, and the required boot/start-up files are in a primary that is within the first 4Gig of the drive (physically). So either accept the 4Gig Partition limit created during setup, or... Preconfigure/preformat (as ntfs) a Primary over 4Gig but upto 8Gig max etc. and install NT etc... (with the updated atapi.sys and SP etc.) or... Create a small fat16 Primary (250Meg is adequate) and install NT there - apply the updated atapi.sys and also the SP you intend to use; also the scsi driver required in the early part of setup... Then use NT Disk Admin tools to configure balance of drive as Extended and preformat as ntfs if you want a single ntfs NT installation (and no separate data area). Then install NT again to the extended partition area. Apply atapi.sys and SP as before. You get a dual-boot NT/NT. You can keep or delete the version in the fat16 Primary - personally I'd keep it - useful recovery route... Do NOT delete the NT boot/start-up files from the 250Meg fat16 Primary... Make an ERD for each version; keep safe/current. Basic job done; you have possibly an NT installation to a drive "a smidgeon" under 9Gig (as ntfs); or a have decided to split the Extended partition into at least two logical-drives - the first for the OS, t'other for data???? (Separate data area is a wise way to go...). The issue of fat32 and NT is really a none even here; NT does not use fat32. It uses fat16 to 4Gig max or ntfs4. NT can be installed via a CD boot, or the 3 floppies and the CD, or by copying the i386 to the Primary partition (as per mechanix2go) and then running the winnt from that i386 location. Personally I'd use either the CD boot or the three floppies + CD approach on this occasion. The updated atapi.sys enables NT to access the (whole of the) drive beyond the 8Gig marker (presuming/provided the bios also see it). Remember too the scsi drivers go in very early in setup sequence...; without them you get no access to the drive... A few useful references: http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=13886 http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=13876 http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=13894 http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=13922 The last link/reference is one of Wanderer's offerings from the days of NT4... (to his credit). Need more input - post back?

http://support.microsoft.com/kb/119497/EN-US/ http://support.microsoft.com/kb/224526/EN-US/ DO NOT SHOOT THE MESSENGER

ooopppss... ...error your describing... should read: ...error you're describing...

Hi trvlr, Maybe the forum software could be updated so that it not only bleeps out naughty words, but does some syntax checking. ;) M2 If at first you don't succeed, you're about average.