Nas001

Thanks for the info. I don't pretend to understand any of Microsoft's licensing practices. Everytime I think I do, it changes. In any case, I'm looking at AIO this morning. It looks pretty cool so far.

What are the licensing implications of using the PE 2005 bootloader files? I recently found out that my company isn't licensed for WinPE (3 weeks after I was told we were). My first thought is that using the PE 2005 bootlader = using PE 2005. If that's the case, it's not valid for those of us that aren't licensed for WinPE. Are there any other methods for booting BartPE from a ramdisk?

I have booted from CD and USB Hard drive, with the same results. Chknic.exe reports no nic found or installed. Devcon reports no network adapters installed. If I try to map a network drive, it tells me the workstation service is not started. Starting the workstation service doesn't help. IPconfig reports nothing at all. However, the B57 drivers do work on my D620's and GX520's.

No. Are vista specific drivers available at this point? I've installed vista manually and I was able to use XP drivers on the machines I tested with, however, the GX260 wasn't one of the models I tested. I guess I'll try that next.

Has anyone had any luck integrating the Optiplex GX260 Nic drivers into PE 2.0? I've tried to add them using drvload.exe (online) and peimg.exe (offline) with no success. I have tried the drivers that originally shipped with the GX260 as well as newer drivers from both Dell and Intel's websites. I have copied the files manually to their respective diretories (.inf --> %windir%\inf, etc..) Still nada. I currently don't have access to an older version of PE, but I have a call into our Microsoft rep to see how I can get the previous version. Any help with 2.0 would be greatly appreciated. Thanx!

An impatient fellow considering you've probably automated 90% of the setup process to begin with. <{POST_SNAPBACK}> Maybe, but I like receiving my paycheck. The process is 99% automated, however it is quite lengthy (2-3 hours per machine) and used globally. They told me to resolve the issue, and I did. IMO, that's how employee/employer relationships are supposed to work. Besides, it wasn't difficult to contact Microsoft for the patch, once I realized there was a patch out there.

Actually, that's what was happening with the setup I use. It prompted for the driver, and after about 4 minutes (yes, I timed it) it would continue on. It did pause setup during that time, which was unacceptable to my employer.

I was installing all my patches from svcpack.inf, but I used the /integrate switch to slipstream this one patch into my unattended install. It worked great and solved the monitor issue. My company is now moving ahead with an SP2 rollout, so I will likely /integrate all of the patches in our next image. Just an FYI,

Here it is.... KB883667

I tried to upload it and got the following message: "The total filespace required to upload all the attached files is greater than your per post or global limit. Please reduce the number of attachments or the size of the attachments." I don't have any place to host it either.

KB883667 solved the issue for me (XPSP1 on a Dell Lattitude D610). The D610 I was using would not detect its own LCD display. Patch link: KB883667 The down side is, you have to contact Microsoft to get the patch.