Sorry I never responded earlier.  I got around the error somehow and have documented my process in a post here http://forum.driverpacks.net/viewtopic. … 258#p39258

Thanks for responding anyways Galapo.

2

(7 replies, posted in Universal Imaging)

Hi,

I just wanted to let everyone know the process I took to get a pretty much universal image created that works on almost every make and model computer I've put it on so far.  I'll try my best to make it as simple to follow as possible and hopefully some will find it useful as I spent many days getting this to work as well as it does.  Some tweaking can likely be done to make it better but I haven't had anymore time to test many other options/methods.

I will try to update each step as needed with more detail when I get a chance in case you are not familiar with programs like sysprep driver scanner, mysysprep or offlinesysprep.

1.  Download all the driverpacks that you require.  Put these in the c:\d folder
2.  Download the sysprep driver scanner software http://www.vernalex.com/tools/spdrvscn/index.shtml  (put in a c:\sysprep folder)
3.  Download sysprep (put in a c:\sysprep folder)
4.  Download mysysprep from http://www.tsaysoft.com/mysysprep/ (put in a c:\sysprep folder)
5.  Create a LiveXP cd with Offline Sysprep integrated into it
6.  Find a 64-bit copy of an ntldr file and copy it to the root of C: replacing the existing ntldr
7.  Get your system setup the way you want (If you're using VMware make sure to remove the tools, make sure to use an IDE disk, and switch the HAL to Advanced Configuration and Power Interface (ACPI) PC.  I also remove the IDE controller and install a "Standard Dual Channel..." controller.
8.  Run the sysprep driver scanner and have it integrate all the driver paths into the registry
9.  Run Mysysprep.exe. I choose mini-setup and reseal.
10.  Once the computer shuts down boot from the livexp cd and run offline sysprep.
11. I choose to "do nothing" with the hal detection.  leave the extra drivers section blank.  In advanced, check "stop Intel PPM...", "supress driver...", "Inject HWID's...", "Install standard IDE...", choose to install all driver packs MSD's, and complete OLSP without running sysprep.
12.  Let OLSP do its thing and then shut down the computer.
13.  Take an image at this point to be used on most computers.

I have found so far that using the old driverpacks (v9 I believe) the image has worked on over 20 different makes and models that I am aware of.  With the old driver packs however it does not appear to work on a toshiba A10 but the new driver packs appear to fix that, but I'm not sure if the new driver packs break any other systems yet.  I did try using OLSP only but ran into some issues (although I cannot remember what they were at this point)  What I stated above may not be the "best" way but it works for me.

If you have any questions about the process or suggestions on how it could be done better please let me know. Couldn't have done it without everyone.

3

(41 replies, posted in Universal Imaging)

Galapo, I'm hoping you can help me with this issue that I've been having with Offlinesysprep.  I guess I posted it in the wrong area the first time so here is a link to details on the issue. 

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

Any thoughts you can give me on what I might be doing wrong would be much appreciated.

Thanks

When I use offlinesysprep from a livexp cd I do not get any errors during the offlinesysprep process until the computer is rebooted.  Upon first boot I get a "Loader 3 error"

The options I chose when performing the OLSP were:

AUTO configuration at first boot
Pointed to C:\D for the location of the driverpack files
Suppress driver signing warnings
Inject HWID's supported out of the box
Install standard IDE mass storage devices
     Install all DriverPacks non-IDE Mass Storage Devices

The version of OLSP is 1.11.0.7 and I built the livexp cd using the recommended options if that makes any difference.

Anyone have any ideas on what the problem is or how to resolve it?

In the end what I want to be able to do is use OLSP to integrate the driverpacks, the mass storage drivers and complete sysprep using a custom sysprep.inf file.  I have been trying with and without a custom sysprep file but always seem to be running into issues either with this loader 3 error, an error occurred while trying to update your registry or it'll work but I don't have my sysprep configuration settings.  I believe I have been trying versions 1.11.0.3 and 1.11.0.7 today with no luck.

I hope that all makes sense as my brain is a little scrambled after working on trying to get this to work all day.

Thanks

Update: I spent some more time trying to narrow down what exactly might be causing  the error 3 message.  So far as long as I do not choose the option "Install all DriverPacks non-IDE Mass Storage Devices" things seem to work without getting the error. I'm currently working on trying to test it again with my customized sysprep.inf.

Might there be an issue with the mass storage driverpacks?

Update 2: Using my own custom sysprep.inf I cannot get offlinesysprep to work at all.  It always shows the loader error 3 when using the inf.

5

(41 replies, posted in Universal Imaging)

Hi,

What is the difference between choosing "Auto Configuration" and choosing "Auto Configuration at First Boot" under the HAL update option in OfflineSysprep?

Thanks