OfflineSysPrep, Offline sysprepping of Windows XP/2003 Options

[Galapo]

Files are: i8042prt.sys, kbdclass.sys, kbdhid.sys, mouclass.sys, and mouhid.sys.

Here's the registry entries, assuming 'ControlSet001' is selected. Please let me know if anything needs to be added or corrected.

CODE

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Control\CriticalDeviceDatabase\*pnp0303]
"ClassGUID"="{4D36E96B-E325-11CE-BFC1-08002BE10318}"
"Service"="i8042prt"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Control\CriticalDeviceDatabase\*pnp0f03]
"Service"="i8042prt"
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Control\CriticalDeviceDatabase\*pnp0f0b]
"Service"="i8042prt"
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Control\CriticalDeviceDatabase\*pnp0f0e]
"Service"="i8042prt"
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Control\CriticalDeviceDatabase\*pnp0f12]
"Service"="i8042prt"
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Control\CriticalDeviceDatabase\*pnp0f13]
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"
"Service"="i8042prt"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Control\CriticalDeviceDatabase\PS2_KEYBOARD]
"ClassGUID"="{4D36E96B-E325-11CE-BFC1-08002BE10318}"
"Service"="i8042prt"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Control\CriticalDeviceDatabase\PS2_MOUSE]
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"
"Service"="i8042prt"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\i8042prt]
"Type"=dword:00000001
"Start"=dword:00000001
"Group"="Keyboard Port"
"ErrorControl"=dword:00000001
"DisplayName"="i8042 Keyboard and PS/2 Mouse Port Driver"
"ImagePath"="system32\\DRIVERS\\i8042prt.sys"
"Tag"=dword:00000004

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\i8042prt\Parameters]
"PollingIterations"=dword:00002ee0
"PollingIterationsMaximum"=dword:00002ee0
"ResendIterations"=dword:00000003
"LayerDriver JPN"="kbd101.dll"
"LayerDriver KOR"="kbd101a.dll"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\Mouclass]
"ErrorControl"=dword:00000001
"Group"="Pointer Class"
"Start"=dword:00000001
"Tag"=dword:00000001
"Type"=dword:00000001
"DisplayName"="Mouse Class Driver"
"ImagePath"="system32\\DRIVERS\\mouclass.sys"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\Mouclass\Parameters]
"ConnectMultiplePorts"=dword:00000000
"MaximumPortsServiced"=dword:00000003
"MouseDataQueueSize"=dword:00000064
"PointerDeviceBaseName"="PointerClass"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\Kbdclass]
"ErrorControl"=dword:00000001
"Group"="Keyboard Class"
"Start"=dword:00000001
"Tag"=dword:00000001
"Type"=dword:00000001
"DisplayName"="Keyboard Class Driver"
"ImagePath"="system32\\DRIVERS\\kbdclass.sys"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\Kbdclass\Parameters]
"ConnectMultiplePorts"=dword:00000000
"KeyboardDataQueueSize"=dword:00000064
"KeyboardDeviceBaseName"="KeyboardClass"
"MaximumPortsServiced"=dword:00000003
"SendOutputToAllPorts"=dword:00000001

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Control\CriticalDeviceDatabase\hid_device_system_keyboard]
"Service"="kbdhid"
"ClassGUID"="{4D36E96B-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Control\CriticalDeviceDatabase\hid_device_system_mouse]
"Service"="mouhid"
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\kbdhid]
"Type"=dword:00000001
"Start"=dword:00000001
"ErrorControl"=dword:00000000
"Tag"=dword:00000005
"ImagePath"="system32\\DRIVERS\\kbdhid.sys"
"DisplayName"="Keyboard HID Driver"
"Group"="Keyboard Port"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\kbdhid\Parameters]
"WorkNicely"=dword:00000000

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\kbdhid\Security]
"Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\
00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
00,00,02,00,60,00,04,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,\
05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\
20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,\
00,18,00,fd,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,\
00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\mouhid]
"Type"=dword:00000001
"Start"=dword:00000003
"ErrorControl"=dword:00000000
"Tag"=dword:00000005
"ImagePath"="system32\\DRIVERS\\mouhid.sys"
"DisplayName"="Mouse HID Driver"
"Group"="Pointer Port"

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\mouhid\Parameters]
"UseOnlyMice"=dword:00000000
"TreatAbsoluteAsRelative"=dword:00000000
"TreatAbsolutePointerAsAbsolute"=dword:00000000

[HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services\mouhid\Security]
"Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\
00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
00,00,02,00,60,00,04,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,\
05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\
20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,\
00,18,00,fd,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,\
00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

EDIT: Thanks for the edit, ED, but I hate codeboxes!

This post has been edited by Galapo: Mar 10 2008, 07:44 PM

Reason for edit: Switched code tags to codebox tags.

[Oleg_II]

Galapo
Thank you very much! It will save me some precious time

Actually, now that I think about it, possibly cdob's mouse and keyboard plugin could be converted back to registry entries and added also?

Maybe. I'll look for it.

PS I have a dozen notebooks Remember that there was a problem with an old IBM: image from a newer computer was restored on it and loaded fine but I can't enter the system - can't type or use mouse in login window, turned off login in a new image but still can't use the system - after loading the system found new hardware and there is no way to proceed without mouse or keyboard working... If only one of them was working at least... Then I read about this problem and found a couple of methods but was lazy to try it again This time I'm goin to try it after I'm back from my endless business trips

[Galapo]

Yes, please try as I would like to confirm whether this is working.

cdob's plugin I mentioned is here: http://www.911cd.net/forums//index.php?showtopic=20987

Thanks,
Galapo.

[justauser]

Posted to correct subject:

While the first msg is very infomative about using the plugin, I am unable to find a post as to how to install the plugin. The downloaded zip file has several directories and I am unclear as to where within the UBCD folder structure where to place these directories. I know that this is basic knowledge for those who do this all the time, but there are those who lack this particular knowledge. Some hints would be real helpful to get started.

For example the plugin has two folders in the root, called "BartPE" and "UnderWindows". Under the "BartPE" folder, there are three more folders and 5 files. Most plugins have only one folder and you place them in the "plugin" directory. I have no idea where to place the "UnderWindows" contents either.

Any help appreciated.

Thanks

[cdob]

Files are: i8042prt.sys, kbdclass.sys, kbdhid.sys, mouclass.sys, and mouhid.sys.

Here's the registry entries, assuming 'ControlSet001' is selected. Please let me know if anything needs to be added or corrected.

As for HID devices (I excluded PS/2 parts, yes add this too):

Let's assume image was created
without any USB hardware or
without USB HUB 2.0
with usbohci, without usbeci

What about adding more USB services (usbccgp, usbhub, usbuhci, usbohci, usbehci) ?

CODE

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\GENERIC_HID_DEVICE]
"ClassGUID"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"
"Service"="HidUsb"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\HID#IrDevice&COL05]
"ClassGUID"="{4D36E96B-E325-11CE-BFC1-08002BE10318}"
"Service"="kbdhid"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\HID#IrDevice&COL06]
"ClassGUID"="{4D36E96B-E325-11CE-BFC1-08002BE10318}"
"Service"="kbdhid"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\HID#IrDevice&COL07]
"ClassGUID"="{4D36E96B-E325-11CE-BFC1-08002BE10318}"
"Service"="kbdhid"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\HID_DEVICE]
"ClassGUID"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\HID_DEVICE_SYSTEM_GAME]
"ClassGUID"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\HID_DEVICE_SYSTEM_KEYBOARD]
"ClassGUID"="{4D36E96B-E325-11CE-BFC1-08002BE10318}"
"Service"="kbdhid"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\HID_DEVICE_SYSTEM_MOUSE]
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"
"Service"="mouhid"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\HID_DEVICE_UP:000C_U:0001]
"ClassGUID"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\PCI#CC_0C0300]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="usbuhci"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\PCI#CC_0C0310]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="usbohci"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\PCI#CC_0C0320]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="usbehci"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\USB#Class_03]
"ClassGUID"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"
"Service"="HidUsb"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\USB#CLASS_09]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="usbhub"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\USB#COMPOSITE]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="usbccgp"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\USB#ROOT_HUB]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="usbhub"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\USB#ROOT_HUB20]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="usbhub"

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Control\CriticalDeviceDatabase\USB#UNKNOWN]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"


[HKEY_LOCAL_MACHINE\temp\ControlSet001\Services\HidUsb]
"DisplayName"="Microsoft HID Class Driver"
"Group"="extended base"
"ImagePath"=hex(2):5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,72,\
00,69,00,76,00,65,00,72,00,73,00,5c,00,68,00,69,00,64,00,75,00,73,00,62,00,\
2e,00,73,00,79,00,73,00,00,00
"ErrorControl"=dword:00000000
"Start"=dword:00000003
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Services\kbdhid]
"DisplayName"="Keyboard HID Driver"
"Group"="Keyboard Port"
"ImagePath"=hex(2):5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,72,\
00,69,00,76,00,65,00,72,00,73,00,5c,00,6b,00,62,00,64,00,68,00,69,00,64,00,\
2e,00,73,00,79,00,73,00,00,00
"ErrorControl"=dword:00000000
"Start"=dword:00000001
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Services\kbdhid\Parameters]
"WorkNicely"=dword:00000000

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Services\mouhid]
"DisplayName"="Mouse HID Driver"
"Group"="Pointer Port"
"ImagePath"=hex(2):5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,72,\
00,69,00,76,00,65,00,72,00,73,00,5c,00,6d,00,6f,00,75,00,68,00,69,00,64,00,\
2e,00,73,00,79,00,73,00,00,00
"ErrorControl"=dword:00000000
"Start"=dword:00000003
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Services\mouhid\Parameters]
"UseOnlyMice"=dword:00000000
"TreatAbsoluteAsRelative"=dword:00000000
"TreatAbsolutePointerAsAbsolute"=dword:00000000

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Services\usbccgp]
"DisplayName"="Microsoft USB Generic Parent Driver"
"Group"="Base"
"ImagePath"=hex(2):5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,72,\
00,69,00,76,00,65,00,72,00,73,00,5c,00,75,00,73,00,62,00,63,00,63,00,67,00,\
70,00,2e,00,73,00,79,00,73,00,00,00
"ErrorControl"=dword:00000001
"Start"=dword:00000003
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Services\usbehci]
"DisplayName"="Microsoft USB 2.0 Enhanced Host Controller Miniport Driver"
"Group"="Base"
"ImagePath"=hex(2):5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,72,\
00,69,00,76,00,65,00,72,00,73,00,5c,00,75,00,73,00,62,00,65,00,68,00,63,00,\
69,00,2e,00,73,00,79,00,73,00,00,00
"ErrorControl"=dword:00000001
"Start"=dword:00000003
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Services\usbhub]
"DisplayName"="Microsoft USB Standard Hub Driver"
"Group"="Base"
"ImagePath"=hex(2):5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,72,\
00,69,00,76,00,65,00,72,00,73,00,5c,00,75,00,73,00,62,00,68,00,75,00,62,00,\
2e,00,73,00,79,00,73,00,00,00
"ErrorControl"=dword:00000001
"Start"=dword:00000003
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Services\usbohci]
"DisplayName"="Microsoft USB Open Host Controller Miniport Driver"
"Group"="Base"
"ImagePath"=hex(2):5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,72,\
00,69,00,76,00,65,00,72,00,73,00,5c,00,75,00,73,00,62,00,6f,00,68,00,63,00,\
69,00,2e,00,73,00,79,00,73,00,00,00
"ErrorControl"=dword:00000001
"Start"=dword:00000003
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\temp\ControlSet001\Services\usbuhci]
"DisplayName"="Microsoft USB Universal Host Controller Miniport Driver"
"Group"="Base"
"ImagePath"=hex(2):5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,72,\
00,69,00,76,00,65,00,72,00,73,00,5c,00,75,00,73,00,62,00,75,00,68,00,63,00,\
69,00,2e,00,73,00,79,00,73,00,00,00
"ErrorControl"=dword:00000001
"Start"=dword:00000003
"Type"=dword:00000001

[Galapo]

Any help appreciated.

The "BartPE" folder contains the files for the BartPE plugin. Place them in a folder in your "plugins" folder, perhaps by the name "OfflineSysPrep". You will then need to add your sysprep files to the "sysprep" folder.

Regards,
Galapo.

[Galapo]

What about adding more USB services (usbccgp, usbhub, usbuhci, usbohci, usbehci) ?

Thanks cdob for that. I'll add this to the next release.

Regards,
Galapo.

BTW: Do you perhaps know the answer to my questions raised here:
http://www.911cd.net/forums//index.php?sho...st&p=143495
http://www.boot-land.net/forums/index.php?...ost&p=30650

[cdob]

@Galapo
Be aware, HID OfflineSysPrep settings are not tested in real life.
However I'm convinced, this should work in real life. No promise.

No, I've no explanation about MassStorage drivers at CriticalDeviceDatabase within setupldr.bin PE.
I've the same experience: MassStorage drivers dosn't work at CriticalDeviceDatabase within setupldr.bin PE.
MassStorage drivers can be loaded at txtsetup.sif, winpeoem.sif or winnt.sif.

[Oleg_II]

I excluded PS/2 parts, yes add this too

Just to confirm: you mean that there should be some regestry settings for PS/2 mouse and keyboard too?

[Galapo]

Just to confirm: you mean that there should be some regestry settings for PS/2 mouse and keyboard too?

I think cdob means he didn't include these entries in his posting. But they're already included in what's written by OfflineSysPrep currently anyway.

Regards,
Galapo.

[Oleg_II]

Ok! I see now Thanks!

[Galapo]

I tested the suggestion posted here: http://forum.driverpacks.net/viewtopic.php?pid=18576#p18576

That is, using ntldr from Longhorn. I tested ntldr from version 4053 on a machine which I injected all DP mass storage drivers into. Formerly this would result in the 'ntfs.sys' error. Replacing ntldr resulted in a successful boot! Memory limits must have been increased.

Regards,
Galapo.

[ilko]

Good, that means nothing is wrong with the registry entries injected or drivers load order

[Oleg_II]

Galapo
A lot of Chinese Ghost "universal" images are using Longhorn ntldr. At least for detecting HAL. I wrote about it in this topic before and it really works, I tried it numerous times

But I didn't understand about PEIMG from WAIK - what is it? Is it a command line tool that can inject mass storage drivers into off line system? Which files are needed and what are the steps (commands)? That's interesting. Could you please give us some instructions?

This post has been edited by Oleg_II: Mar 16 2008, 10:01 AM

[Galapo]

A lot of Chinese Ghost "universal" images are using Longhorn ntldr. At least for detecting HAL. I wrote about it in this topic before and it really works, I tried it numerous times

Yes, I remember you mentioning this. Is it simply automatic? That is, just overwrite ntldr and no more worries about HAL?

But I didn't understand about PEIMG from WAIK - what is it? Is it a command line tool that can inject mass storage drivers into off line system?

Yes, it is a commandline tool which can inject mass storage drivers into an offline system. But not limited to mass storage drivers I don't think. It has some advantages over msdinst: 1) you just supply INF files, and not INF file + hwid; and 2) services aren't entered into the running registry, so it is able to be used from normal OS and not just PE.

Which files are needed and what are the steps (commands)? That's interesting. Could you please give us some instructions?

Files needed are:

CbsCore.dll
Cmiadapter.dll
CMIv2.dll
Dpx.dll
drvstore.dll
msxml6.dll
msxml6r.dll
peimg.exe
SmiEngine.dll
smipi.dll
Wcp.dll
xmllite.dll

Steps:
1. If 'windows' directory is not named 'windows' rename it as such
2. Create a dummy folder in root of the drive called 'users'
3. Run peimg on the desired INF: 'peimg.exe /inf=INF_FILE [drive]\windows'
4. Delete 'users' if created as step #2
5. Rename 'windows' back to what it was if renamed at step #1

If your driver has the 'include' directive, you will need to follow additional steps: http://www.911cd.net/forums//index.php?sho...st&p=141825

Regards,
Galapo.

This post has been edited by Galapo: Mar 16 2008, 05:17 PM

[Oleg_II]

Galapo
Thanks!

About Longhorn NTLDR. I mentioned it here but didn't provide clear instructiones. At that time I found instructions in Chinese only. But recently I found a discussion with mentionning about it on MSFN.ORG too It's here.

Short instructions:
1. Replace NTLDR file on system disk with one from Longhorn beta 1.
2. Create a txt file and save it as a DTECTHAL.INF:

CODE

[Version]
signature="$Windows NT$"
DriverVer=07/01/2001

[hal]
MPS_MP         = halmps.dll
MPS_UP         = halapic.dll
E_ISA_UP       = halstnd.dll
ACPIPIC_UP     = halacpi.dll
ACPIAPIC_UP    = halaacpi.dll
ACPIAPIC_MP    = halmacpi.dll

[ACPIOptions]
ACPIEnable = 2
ACPIBiosDate = 01,01,1999

3. Extract all HAL files and kernels into system32 and rename them according the names in DTECTHAL.INF. For Windows 2000 take files from SP4.CAB, for Windows XP SP2 from SP2.CAB, for WINDOWS 2003 from SP*.CAB. Files:
halacpi.dll
halapic.dll
halmps.dll
halaacpi.dll
halmacpi.dll
hal.dll----> change to halstnd.dll
ntkrnlmp.exe
ntkrnlpa.exe
ntkrpamp.exe
ntoskrnl.exe----> change to ntkrnlup.exe
4. Add a switch to BOOT.INI:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /detecthal

This post has been edited by Oleg_II: Mar 16 2008, 06:33 PM

[Galapo]

Great, thanks for the details as this is really helpful!

Regards,
Galapo.

[jtdoom]

Good, that means nothing is wrong with the registry entries injected or drivers load order

Hi
I am not so sure about load order in driverpacks mass storage INI.
The biggest offenders there are Silicon Image (and Via too?) for the different "modi" a hard disk can be used in.
The latest testpacks have actually split INI sections into three "blocks" because I want it to make it easy for a user to either move them around, or to facilitate a simple 'block" delete.
The sections are, of course, not in alphanumerica order now. They are per MODE.
So, if a user does not need raid5, they do not need raid 5 sections but they can then either move it above "base IDE" or "RAID", or delete the entire "raid5" block from INI..

I think we have approx 30 drivers which can not really load together, but when one uses TXTmode, the one that is read last (sometimes it is the wrong one) is what willl load.
A user deleted ALL silicon drivers, and when I asked he reported he had seen A01250.. An adaptec which has a single Silicon HWID in it.
Had the megaIDE by LSI (another bugger with a Silicon HWID) been placed below that adaptec, it could have been that one that was used.
(EDIT; fortunate coincidence, the adaptec was wrong, but I recall it did not interfere with standard IDE mode?)

Anyway, TXTmode in driverpacks may apparently work, and it won't use two sets for one HWID, but some of these drivers will (unfortunately) load when they SHOULD NOT..

This post has been edited by jtdoom: Mar 16 2008, 08:40 PM

[jtdoom]

Have any of you considered testing something I want tested?

I asked ruudboek what he thought about the following.
In dps txtmode, rather than have all those specific sub-hwids, why not use the VEN\DEV\CC_010* specification, which uses the generic for drivers in that modi and forget about the sub specification alltogether.
When PnP comes on, the driver INF file still has all info, and windows can sort it out.

That would make writing the txtmode (mass storage INI) a LOT easier, but I am not at all sure that will solve the load order "issue" I see happening.
Them dang buggers could still load a "wrong mode" for a mode the user does not want. (depending on order placement in the INI. Which, as you all know, can later be seen in txtsetup.sif.)
It's an idea, I would like thet tested, but if my little theory is right, the tests will only prove the issue is not fixable.

This post has been edited by jtdoom: Mar 16 2008, 08:57 PM

[VASKO]

About PEImg:

It has some advantages over msdinst: 1) you just supply INF files, and not INF file + hwid; and 2) services aren't entered into the running registry, so it is able to be used from normal OS and not just PE.

So, what about using PEImg over network from normal OS on remote machine?