• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 175
  • Last Modified:

NT4 Floppyless Install

I'm trying to upgrade 3.51 to 4 using setup files from a directory on the Servers E: drive. Everything appears to go OK until trhe server reboots and tries to locate the SCSI controller (Advansys Universal) when the system hangs with 'Inaccesible boot device' . I believe the problem may be that the NT4 setup doesn't know about the Advansys SCSI controller but the setup procedure doesn't give me a chance to specify the SCSI OEM setup disk like it does from a floppy based install. Can I put the driver somewhere in the intall directory so that setup picks it up on reboot?
1 Solution
You can add the driver so that NT automatically recognises it. But this can be more difficult. You must edit dosnet.inf, textsetup.sif and some more (I think there are articles in the knowledgebase). Just placing he driver somewhere is not enough.
But it must be possible to add a device driver from disk during setup. NT tells you which controllers were found. This is at least your IDE controller. Then you have to press a key to continue or to install additionell drivers.
If you use unattended setup, you need to integrate the driver in the setup procedure. See "unattend install" in knowledgebase at www.microsoft.com

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now