To get Autodesk’s recommended drivers for its products, use this tool:
In case they move the URL, this is the “Find Recommended Hardware” page, which is very different than the “AutoCAD Hardware Advisor”.
New versions of the HP Universal Printer Drivers are actually working well for such difficult situations as an older USB laser printer shared from an XP box to Windows 7 ×64. Here are elements:
- The HP web page for your printer, may list only HPU PCL 5 or PCL 6. That’s the version you will need to have.
- Copy the appropriate downloadable to both the host PC and the client PC. If the host is 32-bit and the guest is 64-bit, put the 32-bit downloadable on the host and the 64-bit downloadable on the guest. If different, do accordingly :-)
- Do NOT run the downloadable. Install 7zip or equivalent, and unpack to a folder.
- Make sure simple file sharing is off, and make sure both host and client have identical logins set up if this is not a domain network.
- If you are running a non-universal driver on the host, you can keep it if you want; but you do need to install an instance (or a second instance) of the printer using the appropriate HP Universal driver. Use the Windows printer add dialogue, not the HP Universal’s application. Share it to the network.
- On the client, again unpack, don’t run the downloadable.
- Don’t use the printer add dialogue on the client! Browse to the host, e.g., by putting “\\HOSTNAME” in the Explorer address area. Your printer will be visible. Right-click on it and choose “Connect”. If you chose to keep an original non-HP-Universal driver object, there will be two printer objects, and be sure to pick the right one!
- Eventually Windows will ask you for a driver if it needs one. Browse to the location at which you have unpacked the appropriate HP Universal driver, and tell it to go.
bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
bcdedit /deletevalue loadoptions
bcdedit -set TESTSIGNING OFF
The download page for Sharp products (MFPs and other things) used to be easy to find. Now it’s not. Here it is:
If a NIC disappears altogether, try an actual unplug of the PC for 10-15 seconds, and then fire it up again. It worked for me, recommended by a vendor’s tech support. Realtek gigabit NIC. The recommended fix was to update all drivers.
Sometimes hidden devices can exist as objects in the Device Manager. When these are NICs, and sometimes monitors and other things, problems can occur. To see these, do this:
- Open Command Prompt. Then enter:
- When the Device Manager comes up as requested by #3, there will be a “View” menu. Open the View menu, and choose “Show Hidden Devices”.
The problem can be especially significant in Server 2003, after a devirtualization; the NIC
devices used during virtualization are probably still there, and very possibly, still active in the OS to a startling extent. One server we saw was exhibiting an IP conflict until removal, presumably through the 127.0.0.* subnet.
Somewhat mysteriously, performance of Intel software RAID appears to increase a lot if one restarts the service twice or more per day. I am using these two commands:
NET STOP IAStorDataMgrSvc
NET START IAStorDataMgrSvc
The name of the service may need to be changed, depending on multiple factors. The names can be obtained using the properties of the services within ‘services.msc’.
We have three stages so far.
- Go to support.dell.com, and hunt around for the SUU with items for your particular server model. “SUU” is what Dell is calling it, it stands for “Server Update Utility”. You’ll be able to build a complete ISO of a DVD.
- The “Dell OpenManage Server Administrator” is often the only source of chipset drivers, and it is sometimes not visible on the drivers page for the server. At this writing, the best method to find the current version appears to be this Google search.
- Check the individual downloads for your server, too.
A bit out of date, but still quite useful to help us figure out what to do, is this page: