Trust me I know. I gave up on XP on dell laptops two years ago, after fighting with the Nvidia Optimus Drivers for two solid weeks. I said screw it, and built a win7 image for them and pitched that to management.
Christopher Catlett Consultant | Detroit [MCTS_2013_small] Sogeti USA Office 248-876-9738 |Fax 877.406.9647 26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456 www.us.sogeti.com<http://www.us.sogeti.com/> From: [email protected] [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Tuesday, October 15, 2013 4:27 PM To: [email protected] Subject: RE: [MDT-OSD] HP 8200 Elite OSD Chris, For an ancient, dying operating system, yep it would be a good topic. I tend to focus my content on forward-thinking concepts, however. Cheers, Trevor Sullivan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Tuesday, October 15, 2013 3:11 PM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] HP 8200 Elite OSD That would be a nice blog post ;) Christopher Catlett Consultant | Detroit [MCTS_2013_small] Sogeti USA Office 248-876-9738 |Fax 877.406.9647 26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456 www.us.sogeti.com<http://www.us.sogeti.com/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Tuesday, October 15, 2013 4:02 PM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] HP 8200 Elite OSD Ron, You need to get the device ID of the SATA controller from a similar computer that is currently running, and configured the same way (from a BIOS/firmware perspective) as the one that you’re testing on. Once you’ve discovered the device ID (eg. PCI\VEN_8086&DEV_1234*************), you’ll need to search through the INF files that are in your driver package for the appropriate device ID. Once you’ve discovered the correct INF file, you’ll have to find the association between the device ID string and the “friendly name” of the device. This can typically be found as a variable in the [Strings] section of the INF file. Once you’ve got the friendly name of the device, you can go back into the Apply Driver Package step, check the box to install the mass storage driver on pre-Vista operating systems, and then find the device’s friendly name in the drop-down boxes. The upper drop-down box represents each mass storage INF file, whereas the bottom box represents each of the unique devices that are controlled by that INF file. You can use PowerShell to search your driver package for the appropriate device ID, once you have it. Here’s a generic example: Get-ChildItem -Path \\sccm01\e$\packages\Driver Packages\Hewlett-Packard\8200 Elite\Windows 7 64-bit<file:///\\sccm01\e$\packages\Driver%20Packages\Hewlett-Packard\8200%20Elite\Windows%207%2064-bit\sccm01\e$\packages\Driver%20Packages\Hewlett-Packard\8200> -Include *.inf -Recurse | ? { (Get-Content $_ -Raw) -match 'VEN_8086&DEV_1234' }; Cheers, Trevor Sullivan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Knight, Ron Sent: Tuesday, October 15, 2013 2:48 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] HP 8200 Elite OSD I am stuck trying to deploy Windows XP on to an 8200 Elite. I know... I know... XP is terrible. I've gone to HP's website and downloaded all the drivers, imported them and then created a driver pack. Next, in my TS I install the driver package and select the mass storage device (here's the problem) so it can load the rest of the drivers. After the image process the machine gives me a 0x0000007b BSOD and goes into a boot loop. I'm selecting the wrong AHCI driver but I can't find the correct one. Any ideas??!? I've called Microsoft but the boys in India are stumped and HP hasn't been any help. ________________________________ The information contained in this message and any attachments is intended only for the use of the individual or entity to which it is addressed, and may contain information that is PRIVILEGED, CONFIDENTIAL, and exempt from disclosure under applicable law. If you are not the intended recipient, you are prohibited from copying, distributing, or using the information. Please contact the sender immediately by return e-mail and delete the original message from your system.
<<inline: image001.jpg>>
