If you see an error like this follow these steps to fix it: That produced an error, but I was not too deterred by this. I downloaded the Windows Server driver from HP and it installed without problem. Doing a compare of these files yields very few differences, and it seems to me they are for the same driver. The main file of the driver is MegaIDE. It is certified for Windows Server and has been happily running that OS for a couple of years now. If you need to install one or more of these drivers on a print server go to the Sharing tab of you printer and hit the Additional Drivers:
|Date Added:||20 March 2012|
|File Size:||39.23 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
It installed successfully and the Spy program, which sits in the system tray and monitors drive health, worked well. I found one on their website. After you have selected which Windows Server edition you want to install the setup process brings up a listing of available drives in your machine.
After the driver loaded, the number winodws items was down to 3, now showing 2 physical drives really the two logical RAID 1 drivers and windowx partitions one on each driveplus the unallocated space. Hit OK twice to return to the Component Service tool.
For those who are interested here are the links to the software I have mentioned in this post: I rebooted the server and went into the controller BIOS and re-initialized the array, figuring that it had somehow been corrupted or altered by me messing about with the old driver.
You can of course use PowerShell to do the searching for you. You can still upload PowerPoint presentations. Windows Server installed successfully and I started configuring the server.
Using this command we can get the clear text data from the error:. I figured it might be a bad floppy so I copied the driver files to a USB key instead and tried again. This site uses Akismet to reduce spam.
Monthly Archives: May 2008
I decided to look for a newer version. HP np drivers are stored in the prnhp. I figured it might be a bad floppy so I copied the driver files to a USB key instead and tried again. It always gives an error and then freezes when I try to start it.
Finally I installed Exchange and moved all the mailboxes wundows the virtual server. Windows could not create a partition. I downloaded the Windows Server driver from HP and it installed without problem. Using this command we can get the clear text data from the error:. I proceeded to hit the Load Driver button and load the HP driver from floppy.
If you require x64 drivers you need to connect to a Vista x64 computer and if you need an x86 driver you connect to Vista x This will echo out the name of the file that contains the text hp deskjetas well as the line in the file that contains the text. This is where Vista keeps its driver store. Information wants to be free! It installed successfully and the Spy program, which sits in the system tray and yp drive health, worked well.
First I installed a virtual Windows Server machine nc760 my desktop computer.
The 0x in front of the error tells us that this is a hex number and we need to translate it into decimal in order to find out what it means. The same problem you had with I had with WHS on a dlg2. So I knew what the problem was, just not how to fix it. The error code is 5 which means Access Denied.
For those who are interested here are the links to the software I have mentioned in this post: Then I could do a search windosw new hardware and install the Broadcom driver. Since it is so old the server is only capable of running an x86 OS, but it has 3 GB of memory so I manages the job for my small network.
I found one on their website.