[Hp Compaq 8200 Elite Pci Serial Port Driver Win7
Vida Hubbert
Hello, I have a JOB Compaq 8200 elite convertible mini tower. It needs PCI Serial port drivers, PCI Communication Controller drivers and SM Bus drivers. I tried to download them but it says my computer doesn't meet the minimum requirements...
If that link does not work for you, since you are not in the ISA, you can get the Support site from the one in your region by clicking on the Support heading at the top of the forum and then inputting the HP Compaq 8200 Elite Convertible Minitower PC in the model box and selecting the Windows 7 OS.
With activated on-board graphics and the Nvidia Card as primary device, Windows freezes everytime I try to install the Intel HD graphics driver. I tried the lasted Win 8.1 driver from the Intel website as well as the one MS offers via Windows update.
Could this be a hardware failure? Would It help to replace the CPU (which incorporates the on-board graphics). Or is this a normal behaviour or a known incompatibility between Nvidia and Intel graphics?
Just finished up a project where the user needed to run 4 total monitors off a single PCIe x16 video card slot. Two that I worked with were the Quadro P620 and the Quadro M2000. That P620 version is a short "small form factor" and it had the full-height metal backplane adapter at its rear end. It uses up to 4 mini Display Port ports which have the same bandwidth as a full size DP port. The M2000 version is a full height form factor card, and uses up to 4 full size Display Port ports.
I was able to run 4 monitors with each of those cards, using only 1 PCIe x16 slot. However, when I looked up the specs on the 8200 Elite CMT it states there are two PCIe x16 slots.... so my advice with that PC would be to just use two identical cards, one in each of the PCIe x16 slots.
Inexpensive ones we like (with current actively updated W10 drivers) are the Quadro K2000, and you can get those used off eBay for about $50.00 each. Those have a bottom DVI port and two DP ports right above that. You can't use all 3 of those at the same time, however. A DVI plus the next up DP port, or the two DP ports only.
The PCIe x16 slots will be marked primary and secondary on the motherboard or in the technical manual... at least in all the HP Z workstations the upper of the two is the primary slot and the lower is the secondary. Plug the monitor you want to see the boot screen on into the bottom (DVI) port on the primary PCIe x16 slot card. Or, if you'd rather use the two DP ports the boot screen will show on the monitor plugged into the lower of the two. We run many workstations with 4 monitors this way...
W10 best likes identical cards/drivers for it to run two cards. W7 was more forgiving. Mixing and matching is a bad idea unless you are skilled in the black art of W10 display driver work. You also want to stay ahead of Microsoft Windows Update video card drivers by installing the latest W10 version released by nVidia about once/6 months.
Thanks Paul... I did not know of the close slot issue for 2 cards. I'd be happy to advise on the DP adapters we ended up using, both the mini and the regular size types. For the mini ones... some slide in and out and some others actually lock into place quite strongly in the P620 card. The regular size DP adapters for the M2000 card have the normal two metal locking spurs. We used the locking type for the P620 card... did not want accidental disconnects.
We ran a bunch of the Elite 8200 SFF and Elite 8300 SFF versions of these business class PCs from HP (and I believe they used the same motherboards as the CMT versions). I always put in a video card instead of using the built-in video for best speed and user experience, and I always turned off the built-in video in BIOS for stability. A card I settled on for the SFF version Elite 8200 and Elite 8300 boxes is the Quadro K620, a small form factor card that fits nicely in those thinner boxes and which has W10 active driver support still ongoing.
Tobias, my guess is that some of the issue with getting your monitors to work like they did with W7 under W10 is that issue of W10 not liking different video hardware and different drivers running simultaneously in the same box. W7 let you do that to a much greater degree.
I have upgraded 3 home computers (laptops and desktops) to WIN 10 since launch and have been part of the Windows Insider program for 8 months - (identifying problems with NVIDIA drivers and the like). All family computers have upgraded with minimal fuss apart from HP Elite 8200 SFF - core i5 vpro.
Be aware that this PC passes all hardware diagnostics and has new hard drive and compatible memory and works 100% without error on Win 7 Home - motherboard and processor are out of the box two weeks ago. The PC has been reset to Win 7 since.
My question is:- Will there be updates to the HP Driver Support site in the near future to include Windows 10 64bit drivers for relevant machines? Or links included for Intel Chipset drivers when available for Win10?
Before you physically remove the card, go to the device manager, click to expand the display adapters category, right click on the nVidia graphics card, select uninstall, check the uninstall driver box, and instead of rebooting, shut down the PC and remove the card.
If you give that a try, and W10 works fine, then you have isolated the issue to the video card, and you can then replace it with the AMD Radeon HD 6450 low profile with low profile brackets (or 6350 if you need a dual head card).
The problem could be a multitude of things and I am happy with the way my PC currently runs on windows 7 and want to use my computer for work after an extended period of fault finding on other laptops and PCs with windows 10.
I suspect given that the computer has a new processor, motherboard, latest bios, new paired compatible memory modules, new 1TB WD Hard drive, new DVD combi drive with compatible firmware and that no other PC I have tested with either NVidia, AMD or Intel graphics hardware display similar errors that there is an issue with the way that Win10 accesses memory with this machine and that an update from Intel regarding the Intel(R) Q67 Express Chipset Family is required specifically for Win10 (although it appears that support for Intel(R) HD 2000 graphics for anything above win8 is being phased out). I could spend hours trying to upgrade again and look through windows fault logs but I am happy just using windows 7 and getting on with office related tasks that I placed on the back burner for far too long! Thanks again.
Thanks, will leave it a while before re-installing windows 10. Reading your posts I fear it may also be Windows 10 / Intel's drivers for Intel(R) HD2000 graphics chip. I may try with a SFF ATI card in the near future when I have found one that is compatible with this system's low power output psu.
The more I read Intel's discussion forums the more issues I see with Intel(R) HD 2000 graphics on 2nd gen processor systems. It does look like they have stopped support for this graphics chip at Windows 8. The No below being support for Win 10.... Just a quick supplementary question... should installing an ATI graphics card solve the error messages I am getting if the new card supports Win 10 or is the HD 2000 graphics chip so integrated with the processor that I am likely to experience similar error messages? Thanks again! (Maybe I should enquire on Intel site also!).
Make sure before you install the video card that you go to the device manager, click to expand the display adapters device category, right click on the Intel graphics adapter, select uninstall, and check the uninstall driver box.
But I can assure you that with the AMD graphics card in my 8200 Elite, W10 works perfectly. I have not had any crashes, blue screens, etc., and I know there are W10 drivers for the HD 6450. You can either get them from the AMD website, or the W10 windows update tool will automatically download and install the AMD graphics driver.
My particular build 8200 Elite had come with a Radeon HD 6350 dual head graphics card, so I have never run this thing without a graphics card installed. I removed the card it came with, and upgraded to the HD 6670, because my son wanted a graphics card that powered dual monitors (which the 6350 did), and I wanted a graphics card with HDMI and DVI ports, so that is why I replaced the card. Then I gave him the original one from this machine.
Hello, we have an 8200 elite sff with WIN 7 x64 but we aren`t able to get sound from the display port. How can we solve this?! We only have one option in the sound control. We get the picture over display port, but no sound... According to this post (LINK) it should work!
@agentx007 I tried to watch through your video with "scan-pass"; however, your version is old and for windows 7. It is not the same as windows 10. I skipped your video and search for the cause. I found the problem. Somehow the new version of BDU downloads and extracts clover into USB then manages to boot from CD/DVD ! NOT from USB. After searching the cause, I found one person suggested to use command from the Shell> fs0:\EFI\boot\bootx64.efi (or fs1:\EFI\boot\bootx64.efi depends on which is your USB installation)
Finally, I have SUCCESSFULLY installed windows 10 into nvme sdd and made nvme 970 evo boot into windows 10.
For now, every time I boot my computer, it goes into clover first. I have to manually choose nvme ssd hd to boot into windows 10. I remembered some member configured plist to auto boot into windows.
Hi, guys!
Very interesting theme and forum. Several times I re-read it. And here the same I did all necessary with Clover and it turned out on my 6th summer computer with Legacy BIOS to make my NVMe SSD as a boot drive.
Thanks to all who took part.
p.s. Sorry for my english.
Good evening and sorry for my English but I use a translator because I do not know him.
After months and months of searching by mistake I found this forum, and this page, I have a 2008 workstation with a UEFI embryonic bios, but following this guide I managed to install NVMe with boot, thanks for your work.
Soon I will take pictures.
I have a problem, my is a PCI-e 2.0 but it is revealed as 1.1, and I have not automate the start yet, but I have no hurry.