Search options (Page 2 of 2)

I very well may not have this problem solved by then! haha.

Ok well I did actually get it to work from a GX745 to a C610 this afternoon... but that presents a problem of it's own.

I have been building on the latest model and, and modifying the PC to work on all older models.  When we began buying dual core machines this introduced machines that would not longer work on the ACPI HAL.

My process has been to build on the GX745 with a Core 2 Duo, when complete change the HAL driver to "Advanced Computer and Power Interface (ACPI)" prior to syspreping.

In my Sysprep.inf I included the line " UpdateUPHAL = "ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf" ", in order to change the HAL back to a Multiprocessor HAL when it was detected by SYSPREP.  This was working on all of my Desktop PC's, but not on my laptops.

Deleting the " UpdateUPHAL = "ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf" ", line in Sysprep corrected the issue on my single core laptops, but has now broke the image for my multi-core machines.

So I need to find a better way to reliably correct the HALs.

I am about to try another method from here, called "My Sysprep".
http://jimtsay.googlepages.com/mysysprep

It has two methods for changing the HAL.  The first I am going to try uses CPUID to detect the processor type, and change the HAL accordingly.  I tried this process a couple of days ago, but I had mistakenly left the " UpdateUPHAL = "ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf" ", line in SYSPREP when I ran it, and it failed.

The other method is scripting specific HAL's for each PC model, which will take more work, but if it works correctly it will be worth it.

Anyone have any other suggestions?

I have created images using this process on a Dell Optiplex GX745, and a GX620.   These images load and go through the initial configuration (computer name, domain join) but after reboot, they lockup booting on a Dell Latitude C610 and D600.

Has anyone gotten images created on new desktops to work on these laptops?

I have not yet attempted it yet, but...

http://forum.driverpacks.net/viewtopic.php?id=768

http://forum.driverpacks.net/viewtopic.php?id=1291

I'm really curious if this will fix my HAL issues, because I think "My_Sysprep" only compounded them.

Understood, Thank you

------------------

I was not attempting to brag or impress with my references, only to show my receptiveness to new ideas, and to illustrate my situation.  If my wording / tone caused offense it was not my intention.

It sounds like an impressive tool, but those are areas I have already conquered.  It does sound like it could be a good reference in the future, thank you.

I really wanted to utilize RIS but again, it's a bandwidth constraint.  Our technicians have the unfortunate need to be able to walk on site with %90 of what they need to load on hand, and automated as possible.  Since I have not been able to find a solution faster, or more automated than Ghost images, I continue to use this method for our OS distribution / large app preload.  But as I said before I'm always looking for a better solution

I have been doing this a long time, though not quite as long as yourself.  These tools I have found in your forums are new to me and I am thankful to you, your staff, and the community for providing them and maintaining them. 

I'm sorry if I have hijacked this thread and having taking it in a direction outside of your forums normal subject matter, but I thank you for everyone's very helpful and speedy replies.

My goal is to have a universal Win2K and WinXP image for all of my Dell Optiplex and Latitude systems.  From the GX110 through GX745, and C600 though D620.

When I began this process I was attempting to extract the drivers from Dell's setup.exe files and having a horrible time with it.  Some of the EXE's would not extract.  Through this forum I recently discovered this Driver Backup programs.  These are definately a better alternative, but will still require that I install my OS on every model... install the drivers.. then back them up with these programs.

So to farm what was already provided by deleting the the stuff I didn't need seemed like a good idea.

Understood... then I won't be tampering with this one.

Well no... problem was the OemPnPDriversPath limitation being exceeded.  I am using this method not for an XP install CD but to facilitate the Sysprep process.  Not that it would not be nice to have a Method 2 disk for begining my builds.

Looks like I have some more experimenting and reasearch to do then, thank you

Thank you for your reply.

Unfortunately I need drivers from each and every driver pack except for Sound A.   So limiting the packs is not an option.

It there anything special to creating a 3rd party pack?  Or am I simply moving my file structure into 7-Zip files?

Is your only concearn with hacking the driver packs the time required?  Or is there potentional for added failure? (other than the mass storage pack which I likely won't change).

I am actually using nLite to integrate the windows updates, but was told to use this tool for drivers.  Will I run into any problems with Mass Storage Device drivers with nLite?

On and one final question.   This process works for Windows 2000 as well correct?  (concearned with the mass storage section especially).