Compaq Chipset Drivers for DL585 Under Windows 2000?

Of most interest to me right now is where do I find the USB drivers for the
DL585.

I download and tried the AMD OPTera 8000 series chipset drivers, but the PCI
hotplug driver from that install hangs the system and corrupts Windows 2000
to boot (blue screen on reboot). If anyone has tips on what subset of AMD
drivers might work, I would appreciate the tip(s).

--
Will


"Will" wrote in message
...
After installed Windows 2000 to a DL585, most of the chipset and system
devices are showing as unknown. I don't see any chipset driver set on
the
HP Windows 2000 driver section for DL585:

http://h18004.www1.hp.com/support/fi...e/20_6016.html

Any ideas on where to find the chipset drivers for this server?

--
Will

I dont supposed you applied the PSP for windows 2000 on that server? It can
be found he

http://h18004.www1.hp.com/support/fi...e/20_6016.html
"Will" wrote in message
...
Of most interest to me right now is where do I find the USB drivers for
the
DL585.

I download and tried the AMD OPTera 8000 series chipset drivers, but the
PCI
hotplug driver from that install hangs the system and corrupts Windows
2000
to boot (blue screen on reboot). If anyone has tips on what subset of
AMD
drivers might work, I would appreciate the tip(s).

--
Will


"Will" wrote in message
...
After installed Windows 2000 to a DL585, most of the chipset and system
devices are showing as unknown. I don't see any chipset driver set on
the
HP Windows 2000 driver section for DL585:

http://h18004.www1.hp.com/support/fi...e/20_6016.html

Any ideas on where to find the chipset drivers for this server?

--
Will

Damn ...

he

http://h18004.www1.hp.com/support/fi...e/20_6016.html

try that ans see what happenes.

- LC


"Will" wrote in message
...
Of most interest to me right now is where do I find the USB drivers for
the
DL585.

I download and tried the AMD OPTera 8000 series chipset drivers, but the
PCI
hotplug driver from that install hangs the system and corrupts Windows
2000
to boot (blue screen on reboot). If anyone has tips on what subset of
AMD
drivers might work, I would appreciate the tip(s).

--
Will


"Will" wrote in message
...
After installed Windows 2000 to a DL585, most of the chipset and system
devices are showing as unknown. I don't see any chipset driver set on
the
HP Windows 2000 driver section for DL585:

http://h18004.www1.hp.com/support/fi...e/20_6016.html

Any ideas on where to find the chipset drivers for this server?

--
Will

NuTCrAcKeR wrote:
http://h18004.www1.hp.com/support/fi...e/20_6016.html

try that ans see what happenes.


I have never played with a DL machine, but this seems similar to
problems that I have experienced with systems that I have installed
hardware on, and NOT run Smartstart on. It fascinates me (I have wanted
to bring this up before) that hardware installed on a ProLiant really
DOES NOT EXIST until SmartStart SAYS it exists. Surely you can see how
this "flies in the face" of modern plug-and-play thinking. I can't
really blame people for thinking that because the system boots, the
chipset should be supported...because Win2K begins to install,
everything should be fine. But, in reality, SmartStart is the tool that
tells the OS that hardware actually exists...and not actual existence
(of the hardware) itself. How strange that must seem to modern computer
professionals who suddenly find a ProLiant dropped into their laps.

Jeff

"Jeffrey Alsip" wrote in message
oups.com...

NuTCrAcKeR wrote:
http://h18004.www1.hp.com/support/fi...e/20_6016.html

try that ans see what happenes.


I have never played with a DL machine, but this seems similar to
problems that I have experienced with systems that I have installed
hardware on, and NOT run Smartstart on. It fascinates me (I have wanted
to bring this up before) that hardware installed on a ProLiant really
DOES NOT EXIST until SmartStart SAYS it exists. Surely you can see how
this "flies in the face" of modern plug-and-play thinking. I can't
really blame people for thinking that because the system boots, the
chipset should be supported...because Win2K begins to install,
everything should be fine. But, in reality, SmartStart is the tool that
tells the OS that hardware actually exists...and not actual existence
(of the hardware) itself. How strange that must seem to modern computer
professionals who suddenly find a ProLiant dropped into their laps.

Jeff


Well ... not exactly. The older proliant servers are quasai PnP. When you
install a new device, you MUST run the SCU so that the device can have the
required resources assinged to it. These are NOT PnP in the sense that you
can reconfigure device resources on the fly within the OS. The OS does its
quasai thing based on what the hardware tells it. And without running the
SCU, its always a crap-shoot as to whether your server will be stable or
not.

As for things not existing until "smarstart" says they do, I assume you are
referring to the SSD/PSP software installation tools. Yes, this is true to a
point. By default there are MS provided drivers and software for most of the
vendor's devices, but these are provided so that you can get the server up
and running. Nobody expects that an HPaq server will be run without the
application of the vendor software to get all the latest supported features
and fixes that come from the OEM.

Any compentent system builder will get the OEM versions of drivers and
utilities up to date as one of the first things they do to a new server. The
old assisted/integrated system building methods used the OEM versions right
out of the box, so that when you logged on for the first time, your machine
was already reasonably up to date.

I dont believe that smartstart works in the way that you describe above.
SmartStart in its truest form is used to configure the base machine and
prepare it for an OS installation. The older versions had the
then-up-to-date SSD packages that could be applied to existing machines.

- LC

Nut Cracker wrote:
I dont believe that smartstart works in the way that you describe above.
SmartStart in its truest form is used to configure the base machine and
prepare it for an OS installation. The older versions had the
then-up-to-date SSD packages that could be applied to existing machines.

- LC

Let me try to illustrate my contention:

Say you had a 1600 with dual CPU's installed. If you wipe the CMOS
(doing the dip switch thing) and power it up with the 2000Server
install disk in the drive, then the OS will proceed to install (note
that I have NEVER booted to Smartstart, at this point). It seems like
the very most basic hardware (CPU, mem, CD, first SCSI drive) are
automatically enabled. If you allow the installation to finish, the
system will reboot and seem to function...but only one CPU will be
present, and your video will only be 640x480 @ 16colors (the most
fundamental VGA driver that Win has) and any other drives (other than
the very first one) that you have chained on the bus will not seem to
exist at all. In addition, any cards that you have installed in PCI
slots will also be invisable.

So you need to run SmartStart FIRST, just for the devices to even exist
to the OS. Not just the expansion cards...but also the fact that a
second CPU is even installed, or that you have a Rage II Video card
(even though it's onboard) with 2M of RAM.

The OP stated that he had OS installed but could not get USB to even
appear. That sounded, to me, like the very scenario that I have just
illustrated. Now I have never tried this, but I would speculate that if
you installed PSP on the system that I described above you would STILL
not get all of the functions. I believe that PSP will only try to
install updated drivers for devices that Server 2000 can tell the PSP
install routine are actually in place. If you can open Device Manager
and see devices actually listed, but with a bunch of yellow exclamation
marks...THEN PSP can help you. If the devices are not even listed in
Device Manager, then PSP will do you no good.

You and I have been down this road in past threads that start with
somebody wanting to get more video resolution and asking if they can
install another (non-Compaq branded) PCI video card. You usually
suggest that they install an RILOE card, because it has greater video
memory. I usually respond that they can use almost any card they wish,
if they do the install in the proper sequence...including using
SmartStart to tell the system that the new card even exists.

Of course, I could be wrong.

Jeffrey Alsip

"Jeffrey Alsip" wrote in message
oups.com...

Nut Cracker wrote:
I dont believe that smartstart works in the way that you describe above.
SmartStart in its truest form is used to configure the base machine and
prepare it for an OS installation. The older versions had the
then-up-to-date SSD packages that could be applied to existing machines.

- LC

Let me try to illustrate my contention:

Say you had a 1600 with dual CPU's installed. If you wipe the CMOS
(doing the dip switch thing) and power it up with the 2000Server
install disk in the drive, then the OS will proceed to install (note
that I have NEVER booted to Smartstart, at this point). It seems like
the very most basic hardware (CPU, mem, CD, first SCSI drive) are
automatically enabled. If you allow the installation to finish, the
system will reboot and seem to function...but only one CPU will be
present, and your video will only be 640x480 @ 16colors (the most
fundamental VGA driver that Win has) and any other drives (other than
the very first one) that you have chained on the bus will not seem to
exist at all. In addition, any cards that you have installed in PCI
slots will also be invisable.

So you need to run SmartStart FIRST, just for the devices to even exist
to the OS. Not just the expansion cards...but also the fact that a
second CPU is even installed, or that you have a Rage II Video card
(even though it's onboard) with 2M of RAM.

The OP stated that he had OS installed but could not get USB to even
appear. That sounded, to me, like the very scenario that I have just
illustrated. Now I have never tried this, but I would speculate that if
you installed PSP on the system that I described above you would STILL
not get all of the functions. I believe that PSP will only try to
install updated drivers for devices that Server 2000 can tell the PSP
install routine are actually in place. If you can open Device Manager
and see devices actually listed, but with a bunch of yellow exclamation
marks...THEN PSP can help you. If the devices are not even listed in
Device Manager, then PSP will do you no good.

You and I have been down this road in past threads that start with
somebody wanting to get more video resolution and asking if they can
install another (non-Compaq branded) PCI video card. You usually
suggest that they install an RILOE card, because it has greater video
memory. I usually respond that they can use almost any card they wish,
if they do the install in the proper sequence...including using
SmartStart to tell the system that the new card even exists.

Of course, I could be wrong.

Jeffrey Alsip


You information perfectly supports what I had posted earlier. You must run
the SCU before the server is truely aware of the components it has. For
example, the processor mapping table needs to be enumerated, determined, and
writted to the NVRAM which then tells the OS what devices are available to
it. Another example of this is running linux on one of these boxes. if you
were to take your 1600 that had windows running on it with 2 CPU's, and
formatted your drives, and then installed linux you would only get 1 CPU.
You would have to go into the SCU and change your OS type to Other, Unix,
Linux before the detection mechanism in linux would see both CPU's and
configure your SMP Kernel. Of course, that pertains to G1 machines ....

Now, it is also possible that some device support (the 585 uses a RBSU, not
an EISA partition with SCU) has not be enabled within the system setup (F10,
or something). It is also possible that the systemboard is faulty. I just
did the run around with Dell getting a replacement board for a PowerEdge
2650. There were devices with bangs that would not accept drivers, and
frimwares that could not be updated because no supported devices could be
found. We cold booted the machine and it died. Dell sent a guy with a board
out, but that board was DOA. They sent another part out and it was fixed up.

I have worked with several x85's, but not enough to make any general
comments as to how reliable they are. They are mind-melting fast ... havent
seen any problems like this one.

You information perfectly supports what I had posted earlier. You must run
the SCU before the server is truely aware of the components it has.

Since you and I are in total agreement, I am curious if we were able to
answer the original posters question. Assuming that he is still
reading, here is my summary:

If the devices, that are not working for you (chipset or otherwise)
actually appear in Control Panel / System / Device Manager, but have
yellow exclamation points beside them...then you need to install the
PSP from the link that NutCracker provided.

If they do not show up in Device manager AT ALL...then you need to boot
to SmartStart and run the Hardware Configuration Utility. After you run
the HCU and save the settings, don't be surprised if win2k sees most of
them and installs them the next time you boot.

Oh, by the way LC...thanks for not top-posting!

Jeffrey Alsip

"Jeffrey Alsip" wrote in message
oups.com...
You information perfectly supports what I had posted earlier. You must
run
the SCU before the server is truely aware of the components it has.

Since you and I are in total agreement, I am curious if we were able to
answer the original posters question. Assuming that he is still
reading, here is my summary:

If the devices, that are not working for you (chipset or otherwise)
actually appear in Control Panel / System / Device Manager, but have
yellow exclamation points beside them...then you need to install the
PSP from the link that NutCracker provided.

If they do not show up in Device manager AT ALL...then you need to boot
to SmartStart and run the Hardware Configuration Utility. After you run
the HCU and save the settings, don't be surprised if win2k sees most of
them and installs them the next time you boot.

Oh, by the way LC...thanks for not top-posting!

Jeffrey Alsip


top posting ... BAH !!!!

I usually do that when people fail to trim.

Just remember, the convetional SS/HCU/SCU does not exist for the 585. Its a
rom based setup with some intimidating settings.

- LC

top posting ... BAH !!!!

I usually do that when people fail to trim.

Just remember, the convetional SS/HCU/SCU does not exist for the 585. Its a
rom based setup with some intimidating settings.

- LC

As you say. Remember that I am still old school (increasingly VERY old
school). I have never had a DL system (of any type) in my hands.
Perhaps I really am a dinosaur. I suspect that I will never have one of
these (relatively) newer systems until they are so cheap that I can get
them free for the hauling.

You do realize, I hope, that I make pretty good money by keeping the
old PIII systems running in a 6 workstation environment...doing basic
networking and email. I remind you that I am on the FAR north
side...this is the Chicago area frontier. My biggest client is a
charity with 50 workstations, and they rely on donations...so I pride
myself on keeping the older stuff running, and even making it exceed
its originally estimated lifetime and usefullness. The ProLiants fit
this criteria perfectly...when you get one working, it just keeps on
working. The customers are happy with their service, and I am happy to
have the stack of toys...so I guess I am relatively successful.

Jeffrey Alsip