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

Windows 2000 on the Dell r900

We have a new Dell r900 server with Dell Perc6I controller.  Dell does not have a Windows 2000 server driver for the Perc 6, but the ERP system only runs on Windows 2000 sp4 (at the moment, we do plan an upgarde later that will run on later OS's, thats why we have this box).

In the meantime we want to see if we can use it with the current version.  While not supported officially, a number of people have supposedly had great results by using the Win 2003 driver.  I am looking to try this but have hit a snag I haven't seen mentioned (so I am hoping its something I am doing).
 
I have the server booting off the Windows 2000 CD and have a USB Floppy (since it has none internal) plugged in.  When its starts up I select F6 to specify a third party driver.  When prompted to hit Enter it sees the floppy and brings up the screen where I select the Perc Driver.  It says it will load the driver.  (I created the disk by downloading the Windows Server 2003 Perc 6I driver from the downloads page when using the system ID  at Dell)

A bit later as its loading the drivers I get a message that says percsas.sys file not found and the install fails.  The file percsas.sys is on the floppy; so I am not sure whats up.  Ive tried two different floppys to test.

Any suggestions what may be the issue?
 
0
DLHamblin
Asked:
DLHamblin
  • 3
  • 2
  • 2
1 Solution
 
aligigiCommented:
It doesn't see the USB floppy later in the install process. Since you cannot use an internal floppy, you should integrate the driver with nLite (you can get it here: http://www.nliteos.com/download.html ) or some similar program. nlite is free and pretty easy to use.
0
 
sifueditionCommented:
Aliqiqi is right.  The problem is that when you use a usb floppy like this, the driver is "pre-loaded" into memory.  Due to the raid driver not being specific to W2K, this is apparently not being placed in a location where the OS can find it again.  Slipstreaming the driver is the best option to supply the driver to the OS during install.
0
 
DLHamblinAuthor Commented:
I will try that and see if it works.  Will post back.
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
DLHamblinAuthor Commented:
The slipstreaming did get rid of the "percsas.sys" not found error, but it still does not see the drives on the server; I am checking to verify which 2003 driver we are supposed to use to make sure thats not now the issue, will post back once I find that out.
0
 
aligigiCommented:
Maybe you did not do the slipstreaming correctly. Did you choose "textmode driver" when you integrated the driver?
0
 
sifueditionCommented:
Also, make sure that the raid array is set up correctly.  With hardware raid, the OS will see the array as if it is a single physical drive.  If it is not set up correctly, that can cause drive not found type errors.
0
 
DLHamblinAuthor Commented:
The nLite worked, the the reason it still did not see the drives was the driver.  I was given a link to a second driver to use and it slipstreamed fine and installed, and it sees the drives.
0
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

Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

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