For me, those errors showed up most recently after syprep after installing WMP11 or 1 or more of the .NET installs. Hope that helps.
1 2008-04-09 10:58:24
Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04) (204 replies, posted in Universal Imaging)
2 2007-09-25 07:01:36
Re: How do you use DriverPacks? (17 replies, posted in Universal Imaging)
kickarse wrote:
My images can image from a Intel BX, VIA, SIS chipsets all the way up to the new ICH7's so far. I haven't had to do a 8 or 9 yet.
Are any of them SATA with AHCI enabled?
3 2007-09-25 05:30:05
Re: How do you use DriverPacks? (17 replies, posted in Universal Imaging)
From another thread I started, others who were working on sysprep/driverpack problems said that the new Intel drivers cause an issue with some older Intel hardware. Are you sure that your method doesn't have a problem with older Intel hardware? Regarding other hardware, I understand that Intel is the majority of the market, but we do occassionally have to install Windows on some more exotic hardware and could certainly use a way to modify Sysprep.inf automatically. The script that someone made here had some issues with it, but it seemed to be a good start.
4 2007-09-24 05:14:49
Topic: Decompressed driverpack integration (3 replies, posted in Feature Requests)
Since I need to burn my DriverPacked XP installation discs to DVD, I was hoping to find a way to integrate the DriverPacks without compression since the DVD should have enough room on it and I believe that it would take less time for the DriverPack software to copy the decompressed drivers from the DVD rather than go through the lengthy decompression during Windows install. I searched the forums and surprisingly didn't find any mention about others interested in this possibility. Has anyone else done any work on this? Is it a faster method? If it is faster, I would think it would be a relatively simple matter to implement this in DriverPack BASE. Is anyone else interested in this possibility?
5 2007-09-23 16:27:14
Re: How do you use DriverPacks? (17 replies, posted in Universal Imaging)
If you simply sysprep a Windows install using DriverPacks with KTD, the only two things lacking in order to make a universal image are the x0...07b/mass storage controller problem and the HAL problem. Some relatively minor things break that way (HD audio), but are easy to fix. There are several methods for resolving the HAL issue. I haven't found any satisfactory solution to the x0...07b error; manually adding lines to the sysprepmassstorage section has problems with Intel drivers in particular and is tedious in general, and I haven't found a FixIDE script newer than September 2006. This method doesn't seem to solve the mass storage problem either. What are the advantages to using this method over the aformentioned method?
6 2007-07-19 19:30:15
Re: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
7 2007-07-19 19:29:00
Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04) (204 replies, posted in Universal Imaging)
8 2007-06-15 00:59:45
Re: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
The -bmsd switch is only used to create the sysprepmassstorage section in the sysprep.inf. It would probably be best to use that switch first, then add the additional entries that your script creates, then run sysprep without the -bmsd switch.
9 2007-06-14 04:16:09
Re: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
Thank you, gentleman, I think this is the info that I need. It would be nice if it were easier, but at least now it seems I can do what I set out to do.
Thanks again.
10 2007-06-13 11:31:28
Re: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
Am I the only one looking for a solution for this? Is this something already in the works? Did I post this in an improper manner or in the wrong section?
11 2007-06-07 09:42:56
Topic: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
When making a generic Windows image, it is easiest to use the -bmsd switch in order to make Sysprep automatically populate the sysprepmassstorage section of the sysprep.inf in order for Windows to boot the first time after the drive being imaged on a computer that uses a mass storage controller different than the on used by the computer used to create the reference image. The purpose of this section is to force sysprep to install all of the available mass storage controller drivers. My problem is that this section is exectly the same when run from a Windows installation done with or without DriverPacks, and therefore, Windows reboots during the initial boot after the drive (or array) has been imaged unless the controller was already included with Windows. One way around this, if the computer has another controller that is supported (like the IDE controller on a computer that has a separate RAID controller), is to image a drive attached to the IDE controller, allow it to go through the mini-setup and detect all of the drivers, then clone that drive to a drive or array on the other controller. This is just an annoyance when it can be done, but isn't always an option. Another, and probably separate issue is AHCI support. When an image is used that was created with a computer without AHCI support (IDE, for example) on a computer that has a SATA contoller with AHCI support, a blue screen 7E error is displayed on the initial boot.
Here is a snip from the Sysprep mass storage section:
[sysprepmassstorage]
*pnp0a00=c:\windows\inf\machine.inf
*pnp0a01=c:\windows\inf\machine.inf
*pnp0a04=c:\windows\inf\machine.inf
*pnp0a03=c:\windows\inf\machine.inf
pci\cc_0604=c:\windows\inf\machine.inf
pci\cc_0601=c:\windows\inf\machine.inf
pci\cc_0602=c:\windows\inf\machine.inf
pci\cc_0600=c:\windows\inf\machine.inf
pci\cc_0500=c:\windows\inf\machine.inf
root\ftdisk=c:\windows\inf\machine.inf
root\swenum=c:\windows\inf\machine.inf
root\update=c:\windows\inf\machine.inf
root\mssmbios=c:\windows\inf\machine.inf
root\dmio=c:\windows\inf\machine.inf
lptenum\microsoftrawport958a=c:\windows\inf\machine.inf
root\rdpdr=c:\windows\inf\machine.inf
root\rdp_mou=c:\windows\inf\machine.inf
root\rdp_kbd=c:\windows\inf\machine.inf
*pnp0000=c:\windows\inf\machine.inf
*pnp0001=c:\windows\inf\machine.inf
*pnp0003=c:\windows\inf\machine.inf
*pnp0004=c:\windows\inf\machine.inf
*pnp0100=c:\windows\inf\machine.inf
*pnp0101=c:\windows\inf\machine.inf
*pnp0103=c:\windows\inf\machine.inf
*pnp0200=c:\windows\inf\machine.inf
*pnp0201=c:\windows\inf\machine.inf
*pnp0800=c:\windows\inf\machine.inf
*pnp0b00=c:\windows\inf\machine.inf
*pnp0a05=c:\windows\inf\machine.inf
*pnp0a06=c:\windows\inf\machine.inf
*pnp0c00=c:\windows\inf\machine.inf
*pnp0c01=c:\windows\inf\machine.inf
*pnp0c02=c:\windows\inf\machine.inf
*pnp0c04=c:\windows\inf\machine.inf
*pnp0c0b=c:\windows\inf\machine.inf
*pnp0c0c=c:\windows\inf\machine.inf
*pnp0c0d=c:\windows\inf\machine.inf
*pnp0c0e=c:\windows\inf\machine.inf
*pnp0c15=c:\windows\inf\machine.inf
acpi\dockdevice=c:\windows\inf\machine.inf
acpi\dockdevice&_sb_.pci_.oak_=c:\windows\inf\machine.inf
acpi\dockdevice&_sb_.pci_.isa_.slce=c:\windows\inf\machine.inf
acpi\fixedbutton=c:\windows\inf\machine.inf
acpi\thermalzone=c:\windows\inf\machine.inf
isapnp\readdataport=c:\windows\inf\machine.inf
pci\ven_10aa&dev_0000=c:\windows\inf\machine.inf
pci\ven_1025&dev_1435=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1445=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1489=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1449=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1533=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1451=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1521=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1621=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1647=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1651=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1523=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1531=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1541=c:\windows\inf\machine.inf
pci\ven_10b9&dev_5243=c:\windows\inf\machine.inf
pci\ven_10b9&dev_5247=c:\windows\inf\machine.inf
pci\ven_10b9&dev_7101=c:\windows\inf\machine.inf
pci\ven_1022&dev_7007=c:\windows\inf\machine.inf
pci\ven_1022&dev_700d=c:\windows\inf\machine.inf
pci\ven_1022&dev_700f=c:\windows\inf\machine.inf
pci\ven_1022&dev_740b=c:\windows\inf\machine.inf
pci\ven_1022&dev_7413=c:\windows\inf\machine.inf
pci\ven_1022&dev_7443=c:\windows\inf\machine.inf
pci\ven_1022&dev_7451=c:\windows\inf\machine.inf
pci\ven_1022&dev_746a=c:\windows\inf\machine.inf
pci\ven_1022&dev_746b=c:\windows\inf\machine.inf
pci\ven_0e11&dev_0001=c:\windows\inf\machine.inf
pci\ven_0e11&dev_0002=c:\windows\inf\machine.inf
pci\ven_0e11&dev_1000=c:\windows\inf\machine.inf
pci\ven_0e11&dev_2000=c:\windows\inf\machine.inf
pci\ven_0e11&dev_ae29=c:\windows\inf\machine.inf
pci\ven_0e11&dev_ae2b=c:\windows\inf\machine.inf
pci\ven_0e11&dev_a0f0=c:\windows\inf\machine.inf
pci\ven_0e11&dev_a0f3=c:\windows\inf\machine.inf
pci\ven_0e11&dev_a0f7=c:\windows\inf\machine.inf
pci\ven_0e11&dev_ae2a=c:\windows\inf\machine.inf
pci\ven_0e11&dev_ae31=c:\windows\inf\machine.inf
pci\ven_0e11&dev_ae69=c:\windows\inf\machine.inf
pci\ven_0e11&dev_ae6c&cc_0600=c:\windows\inf\machine.inf
pci\ven_0e11&dev_ae6c&cc_0604=c:\windows\inf\machine.inf
pci\ven_0e11&dev_ae6d=c:\windows\inf\machine.inf
*cpqa0ef=c:\windows\inf\machine.inf
*cpqae08=c:\windows\inf\machine.inf
*cpqae30=c:\windows\inf\machine.inf
*cpqae3b=c:\windows\inf\machine.inf
*cpqae3c=c:\windows\inf\machine.inf
*cpqae4a=c:\windows\inf\machine.inf
*cpqae4b=c:\windows\inf\machine.inf
*cpqae4c=c:\windows\inf\machine.inf
*cpqae4d=c:\windows\inf\machine.inf
*cpqae53=c:\windows\inf\machine.inf
*cpqae54=c:\windows\inf\machine.inf
*cpqae55=c:\windows\inf\machine.inf
*cpqb05f=c:\windows\inf\machine.inf
*cpqb118=c:\windows\inf\machine.inf
*cpqb119=c:\windows\inf\machine.inf
*cpqb11a=c:\windows\inf\machine.inf
*cpqfa1b=c:\windows\inf\machine.inf
pci\ven_1080&dev_0600=c:\windows\inf\machine.inf
pci\ven_1078&dev_0000=c:\windows\inf\machine.inf
pci\ven_1078&dev_0002=c:\windows\inf\machine.inf
pci\ven_1011&dev_0001=c:\windows\inf\machine.inf
pci\ven_1011&dev_0021=c:\windows\inf\machine.inf
pci\ven_1011&dev_0022=c:\windows\inf\machine.inf
pci\ven_1011&dev_0024=c:\windows\inf\machine.inf
Can anyone think of a way to create the text necessary to add the drivers from DriverPacks either to this Sysprep section or perhaps to this machine.inf?