for the xp cd: I used to have problems with the fonts too. I used to just copy the fonts to sysprerp/i386. I later found out that if you remove the installfilespath from the sysprep.inf, there won't be anymore font issues.
for ktd: I think to be safe you need to list every folder individually. Overflow would know if that bug was fixed.
for offlinesysprep: create bartpe with offline sysprep, run it and choose autoconfig hal on first boot, click on advanced, click the check box next to complete offline sysprep without running sysprep.exe, click apply, then on the first screen click apply. It should only take a few seconds. Then image.
76 2010-03-27 09:55:20
Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04) (204 replies, posted in Universal Imaging)
77 2010-03-26 10:40:03
Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04) (204 replies, posted in Universal Imaging)
I use offlinesysprep to change the hal. the latest version works great. I haven't had any yet that it wouldn't work on.
as for your process, I have a couple of questions.
step 5: why do you copy the xp cd to sysprep/i386?
you sysprep.bat:
devpath is for adding drivers to the registry. You should be executing devpath on the drivepacks folder not on c:
you don't need the enabling image for amd/intel. you are building in vmware which doesn't even have intelppm.
for -bmsd
The drivers for bmsd never change so you only need to run it once. As for scanning the drivepacks for mass storage, are you only choosing certain ones? like ide only. If you try to add them all you will definitely run in to memory issues.
78 2010-03-26 10:15:04
Re: Audio works on one model, but not the other (18 replies, posted in Universal Imaging)
sigmatel drivers from boot camp
1.Download the boot camp 3.1 update from here (http://support.apple.com/kb/DL996)
2. Use universal extract to extract that file to suddir
3. Use universal extract or 7zip to extract BootCampUpdate32.msp to folder
4. There should be a folder that was extracted called BootCamp30ToBootCamp305. Look inside that folder for Binary.Sigmatel_Bin
5. Use 7zip to extract that file to folder. This should be the sigmatel driver.
From your setupapi.txt, it shows that you used makepnf. It was determined later on the sysprep sticky that make pnf is bad. Don't use it.
79 2010-03-24 09:08:03
Re: S.A.D sound driver problems (18 replies, posted in Universal Imaging)
http://pubs.logicalexpressions.com/Pub0 … asp?ID=361
16k limit for 95/98/me
64k limit for 2k and above
80 2010-03-23 16:04:40
Re: S.A.D sound driver problems (18 replies, posted in Universal Imaging)
You might try using Vernalex Sysprep Driver scanner. Its much easier to use than trying to populate the OemPnPDriversPath by hand.
http://www.vernalex.com/tools/spdrvscn/index.shtml
81 2010-03-16 10:38:33
Re: 2k3 native supported IDE controllers (10 replies, posted in Universal Imaging)
yes, the sysprep inf for xp and 2k3 should be all of the controllers that are natively supported. If you need it, I can make a more complete mergeide for both.
82 2010-03-14 14:38:30
Re: 2k3 native supported IDE controllers (10 replies, posted in Universal Imaging)
http://www.mediafire.com/?zz0yymjtynw
I created a mergeide from a windows 2003 install. I would note there are more default ide controllers that are standard than what microsoft has posted for xp.
83 2010-02-04 10:09:16
Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04) (204 replies, posted in Universal Imaging)
post your sysprep.inf and maybe we can help.
84 2010-01-29 15:31:17
Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04) (204 replies, posted in Universal Imaging)
Are you sure you followed the directions for Offline Sysprep? I was able to make it work with BartPe without any problems.
Attached below is my sysprep; it's to big to post. It works for the gx520, haven't tested it on the 620. It works for many others that i couldn't get working before.
85 2009-09-28 06:40:13
Re: Multi Computer Image: Sysprep + findHWID (5 replies, posted in Universal Imaging)
Not all the drivers in the mass storage pack are sysprep compatible, some aren't even xp compatible.
There is also a memory limit with xp on how many drivers you can load. You can get around this limit by using the ntldr from higher os's, but i don't think this is legal.
Also, the detect non plug and play option is for ISA hardware. Microsoft hasn't recommended this setting for some time. It also adds a few minutes to the sysprep process. I haven't used it in a long time with no ill effects.
86 2009-08-05 09:46:33
Re: "Uni" Image wont boot (cycles) but not a HAL issue. (8 replies, posted in Universal Imaging)
Mup.sys is network related not video related. See http://www.microsoft.com/technet/securi … 2-017.mspx under technical details for more information.
87 2009-08-03 05:42:22
Re: Sysprep issue (7 replies, posted in Universal Imaging)
Sounds like a driver issue. What are the error messages on the blue screens? What Hal are you using for the image? also you can get rid of the -pnp switch for sysprep; its only used if you have non plug and play devices.
88 2009-08-03 05:15:07
Re: "Uni" Image wont boot (cycles) but not a HAL issue. (8 replies, posted in Universal Imaging)
Can you post your mass storage section of your sysprep file?
89 2009-07-11 09:49:54
Re: Sysprep issue (7 replies, posted in Universal Imaging)
I'm going to assume you are using windows xp since the 20+ mins is what xp usually takes on older hardware. If have xp and are using sp3, make sure you upgrade to the sp3 sysprep version. If its completing in 15secs, then it might mean that your sysprep.inf file is corrupt or missing, or you are missing the mass storage drivers section in the inf file.
When it completes in 15 secs, does it popup any error messages and does the computer shutdown? What options of sysprep are you using, ie minisetup, reseal, factory, etc.
90 2008-06-26 19:13:31
Re: Dell D610/Mobility X300 Problems (33 replies, posted in Universal Imaging)
The ati2mtag.sys doesn't appear to be referenced or copied during the manaul Dell Install.
91 2008-06-25 08:53:30
Re: Dell D610/Mobility X300 Problems (33 replies, posted in Universal Imaging)
Check here: http://blogs.msdn.com/robgruen/
Under the topic installing 5th and 6th display. Maybe that will help.
I also notice you are using the test packs for your drivers. Have you tried with the 804 final driverpacks?
There is also an error 1307 about security permissions.Maybe that is causing the problems.
92 2008-06-23 15:29:29
Re: Dell D610/Mobility X300 Problems (33 replies, posted in Universal Imaging)
yeah mine is around 8k. I calculate his to be around 30k.
93 2008-06-22 13:58:57
Re: Dell D610/Mobility X300 Problems (33 replies, posted in Universal Imaging)
Do you have Net Framework installed in your image?
WOW, your device path key must be humongous.
94 2007-10-23 15:53:17
Re: [Final] Mass Storage 711 (36 replies, posted in DriverPack Mass Storage)
This is from the latest tagged pack, 7109X. If you dont understand, I will post a more elaborate explaination.
Also I have not tested anything after sysprep yet, I havent got that far yet.:P
Location:C\D\M\3\2
Problem: Driver not extracted- 2.exe
Fix: Extract driver
Location: C:\D\M\A\3\AEC6280.INF
Problem: Hardware id not formated correctly
Fix: Remove semicolon from hardware id
Location: C:\D\M\A\3\AEC6290.INF
Problem: Hardware id not formated correctly
Fix: Remove semicolon from hardware id
Location: C:\D\M\E\
Problem: Driver is for windows 2003
Fix: Possibly rename folders to k3.
Location:C:\D\M\I\3
Problem:Same driver as in C:\D\M\I\2 just for windows 2003
Fix: Add folder under C:\D\M\I\2 named k3 and add driver to it.
Location:C:\D\M\I\5
Problem: Same driver as in C:\D\M\I\4 just for windows 2003
Fix: Add folder under C:\D\M\I\4 named k3 and add driver to it.
Location: C:\D\M\V\4
Problem: Folder contains 64bit drivers.
Fix: Remove drivers.
Location:C:\D\M\Q\3
Problem: Prompts user to find file during sysprep.
Fix: Change qlsdm.dll=2 to qlsdm.dll=1
Location:C:\D\M\Q\
Problem: Folder contains all 2000 drivers
Fix: Possibly rename folders to K or 2k.
95 2007-09-27 18:31:43
Topic: Trident, SIS, Rage ultra additions to graphics packs (0 replies, posted in DriverPack Graphics)
Trident Blade XP
http://www.jetway.com.tw/evisn/download … /index.htm
PCI\VEN_1023&DEV_9910&SUBSYS_99101023
SIS 630 Video driver 2.09
http://www.softwarepatch.com/utilities/sis630.html
PCI\VEN_1039&DEV_6300&SUBSYS""
32MB ATI Rage 128 Ultra
http://support.us.dell.com/support/down … leid=35636
PCI\VEN_1002&DEV_5446&SUBSYS_04091002&REV_00\4&21093523&0&0008
96 2007-09-21 23:46:37
Re: Sysprep image (9 replies, posted in Universal Imaging)
Assuming that the Dpsfnshr completes corectly, the devpath is changed in the registry from c:\D to whatever directory in the KTD location. see below. So anything that you add to the system will find the drivers in the right place.
2007-09-19 07:23:16 : <KTD> KTD cache location set: "C:\WINNT\Drivers".
2007-09-19 07:23:16 : <KTD> System sound muted (to prevent annoying beeping when unsigned driver warnings pop up).
2007-09-19 07:23:16 : <KTD> KTD is enabled, in PATHS mode.
2007-09-19 07:23:25 : <KTD> Moved drivers inside "C:\D\3" to "C:\WINNT\Drivers\D".
2007-09-19 07:23:29 : <KTD> Moved drivers inside "C:\D\C" to "C:\WINNT\Drivers\D".
2007-09-19 07:23:29 : <KTD> Moved drivers inside "C:\D\CPU" to "C:\WINNT\Drivers\D".
2007-09-19 07:23:40 : <KTD> Moved drivers inside "C:\D\G" to "C:\WINNT\Drivers\D".
2007-09-19 07:23:45 : <KTD> Moved drivers inside "C:\D\L" to "C:\WINNT\Drivers\D".
2007-09-19 07:23:53 : <KTD> Moved drivers inside "C:\D\S" to "C:\WINNT\Drivers\D".
2007-09-19 07:23:53 : <KTD> Successfully created the "%KTD%" environment variable, it has been set to "C:\WINNT\Drivers". It will be available after the next reboot.
2007-09-19 07:23:58 : <KTD> Successfully updated the DevicePath registry value!
2007-09-19 07:29:47 : <KTD> Successfully created the .pnf files. KTD has been applied! It will be available after the next reboot.
2007-09-19 07:29:48 : <KTD> System sound enabled again (mute cancelled).
2007-09-19 07:29:48 : <CLNP> Deleted the DriverPacks, which were located in "C:\D".
97 2007-09-20 00:11:44
Re: Sysprep image (9 replies, posted in Universal Imaging)
Well I've tried a ton of different ways to get it to keep the drivers in c:\d and still can't seem to figure out anywork around. I ge the same errors as jakeld does or it just simply deletes the folder.
If Bâshrat the Sneaky has any other suggestions, that would be great.
If this is not implemented in Dpsbase, could this be implemented sometime in the future?
In case anyone is wondering the reason that I dont want to move the files is that moving all the files (1.4GB) takes about 6 mins to move on the current hardware that I am supporting. I need to keep the image deployment time down as low as possible.
As always thanks for any insights.
98 2007-09-18 21:47:27
Re: Sysprep: -bmsd and machine.inf (3 replies, posted in Universal Imaging)
Well I finished testing the images. Removing the entries had no effect on the time. It appears that it just ignores entries from machine.inf Oh well, back testing other things.
99 2007-09-18 14:09:16
Re: Sysprep: -bmsd and machine.inf (3 replies, posted in Universal Imaging)
Scsi has non plug and play cards. Pnpscsi has Plug and play scsi cards. Mshdc has ide and pcmcia cards.
100 2007-09-18 01:48:34
Topic: Sysprep: -bmsd and machine.inf (3 replies, posted in Universal Imaging)
According to Microsoft's Technet, the bmsd switch "Populates a pre-existing [SysprepMassStorage] section with the hardware IDs specified in the Machine.inf, Scsi.inf, Pnpscsi.inf, and Mshdc.inf files, and installs those mass-storage controllers."
Upon further examination of machine.inf, there appears to be no mass storage controllers contained in it. The items in the file seem to be bridges, agp filters , mice , sensors power management controllers, and other misc hardware.
So my question is : After running -bmsd, should all references to drivers in machine .inf be removed?
I am going to try it later on to see if it makes a difference in the sysprep time in my images. Any thoughts would be appreciated.