Help - Search - Members - Calendar
Full Version: Offlinesysprep BSOD after Sata driver injection?
The CD Forum > Bart's PE Builder > OfflineSysPrep
Yakuzi
Hi Guys

I have compiled a nicely working offlinesysprep'd universal image injected with sata drivers using base etc + Offlinesysprep and thought i was on the money until i tested it today on 2 sata machines and got infinite reboots before it reaches mini setup after deployment.

Here is my full process:

Bartpe Preparation and Driver preparation/Integration

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

1.Downloads:

OfflineSysprep: http://www.911cd.net/forums//index.php?showtopic=22064 - Latest as of 4/11/2010
Driverpacks: http://driverpacks.net/downloads - I am using the latest as of 4/11/2010

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

2. BARTPE Prep

1.Prepare normal Bartpe using any guide on the internet

2.Add Offlinesysprep plugin to Bartpe build

3.Copy Sysprep files to C:\BarttPE\plugin\OfflineSysPrep\sysprep folder. Ensure you use 5.1.2600.0

4.Add Devcon.exe to C:\BarttPE\plugin\OfflineSysPrep\tools

5.Go into C:\BarttPE\plugin\OfflineSysPrep\sysprep and open sysprep.inf. The contents will be different depending on company and requirements but the entries in bold are important to all Hardware Independent situations in this scenario

;SetupMgrTag
[Unattended]
InstallFilesPath=C:\sysprep\i386
UpdateInstalledDrivers=Yes
DriverSigningPolicy=Ignore

[GuiUnattended]
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=85

[UserData]
FullName="Seventeen Group Staff"
OrgName="Seventeen Group Limited"

[TapiLocation]
CountryCode=44

[RegionalSettings]
LanguageGroup=1
SystemLocale=00000809
UserLocale=00000809
InputLocale=0809:00000809

[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=windist

[GuiRunOnce]
Command0="c:\DP_Install_Tool.cmd"
Command0="\\10.1.20.3\klshare\Packages\NetAgent 8.0.2090\lsexec.exe"


[Identification]
JoinDomain=atlgroup

[Networking]
InstallDefaultComponents=Yes

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

3. BASE/MassStorage Plugin preparation/integration

1.Extract contents of DriverPacks Base Program not to your plugins folder C:\DPsBase\

2.Download MassStorage Driver Pack and place this directly in your C:\DPsBase\Driverpacks folder

3.Run c:\DPsBase\DPs_Base.exe and select language and use arrow for next stage

4.Program will detect version of driver packs and look like this

5.Hi the arrow and select BartPE for the platform

6.Browse the plugin folder: C:\BarttPE\plugin

7.Ensure at the next stage that DriverPack MassStorage text mode is selected and hit the next arrow

8.Now chose slipstream

9.Run PEBuilder-Plugins and you will notice 2 new plugins
a.Driverpacks.net base should be set to enabled NO. Press config to finish setup
b.Driverpacks.net MassStorage should be set to yes

10.Now go into C:\BarttPE\plugin\OfflineSysPrep and run:

11.CreateMassStorageData.exe. This will create the folder DriverPacks-MassStorage for offline sysprep to use and inject

12.Now build the bartpe ISO and burn to CD


Source: http://users.telenet.be/jtdoom/basetute/Ba...PE_HelpFile.htm

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

4. SAD Method 1 Driver Pack Preparation/Integration

1.Ensure no other driverpacks are in the C:\DPsBase\DriverPacks folder

2.Copy the CPU driverpack in its original compressed form to the driverpack folder

3.Run C:\DPsBase DPs_BASE.exe

4.This time select Stand Alone Drivers (SAD) as the location and browse to the desired path

5.Select the driverpack to slipstream (CPU and ensure that text mode is not selected this time)

6.Chose method 1 for the slipstream method and then hit slipstream

7.You will now have a folder created in the browse location you identified in step 4.

8.Now go into the D (Drivers) folder. You will see the P folder (Processor – created from slipstream method 1 with CPU driver pack). Also in this folder is DPINST.exe. Simply get all the other driverpacks and extract them into the D folder.

9.Then extract Devpath.exe from DriverPacks BASE\bin\wnt5_x86-32\M2.7z and copy to the DriverPacks.net folder. Esnure the .ini files for each pack are also present.

10.Now copy NTLDR acquired from XP 64 bit SP into the DriverPacks folder. This is necessary to extend the amount of information the file can contain when integrating the drivers to registry.

11.The folder should look like this with D populated with all driver packs:

12.This folder is now ready to copy to sysprep machine

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

5. Final preparation of Workstation being sysprep’d

1.Copy prepared files/folders to route of C of machine to be sysprep’d

2.Overwrite NTLDR previous version. Change view of NTLDR to hidden.

3.Update anti virus with latest signatures and double check nothing is in the admin local temp folder.

4.Now right click – edit - c:\ dp_Inst_tool.cmd.

a.Find line: Echo DPsRootDel = "false" >> %DPFL%
b.Change to: REM Echo DPsRootDel = "false" >> %DPFL% (This will ensure all relevant files are deleted!)

5.Now reboot computer (Not necessary but good practice)

6.Now open command prompt and type the following: c:\devpath.exe C:\D and hit enter. Wait 5 minutes for this to complete. You can look in task manager but be sure not to interrupt the process.

7.Once it is complete go into regedit and check that the following registry key is populated accordingly:

a.HKLM\Software\Microsoft\Windows\CurrentVersion,DevicePath'
b.%SystemRoot%\Inf;C:\D\C\A1;C:\D\C\A2;C:\D\C\AM2;C:\D\C\AM4;C:\D\C\AM5;C:\D………..
8.Once confirmed delete devpath.exe

9.Ensure Show hidden files and folders is turned off in windows.

10.Delete all cache (customize classic start menu) Clear

11.Ensure recycling bin is empty and everything is CLEAN!

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


6. Offline Sysprep and Sysprep finalising

1.Reboot computer with BARTPE CD in and boot from CD (Normally automatic)

2.Fire up Offlinsysprep and ensure the Auto config is set for hal

NOTE: See image for advanced settings
Click to view attachment

3.Now hit apply and click ok to Start Services request

4.OK for Warning! Some modifications……

5.Click OK to Sysprep Start

6.Ensure Sysprep has the final settings and hit reseal

7.Now Ghost the machine whilst still in Bartpe

Can anyone see anything obvious that im doing wrong. Does the 'Inject HWID's setting need to be ticked for massstorage sata injection (The reason i unticked this was because if ticked once the image loaded on a IDE computer, the processor in device manager would show up with a yellow exclamation mark)? Should i still be including MassStorage as a driver pack in Devpath or as they are being injected is it better practice to leave out of devpath?
Galapo
A couple of questions:

1) What is the HWID of the machine? Is it supported by DriverPacks?

2) What happens if you leave out step #3 "BASE/MassStorage Plugin preparation/integration"? Do you still get the BSOD?

3) What is the BSOD message you are getting?

Regards,
Galapo.
Yakuzi
Hi Galapo

I have deployed the image to:
Note: I have run Devcon with c:\devcon hwids * > c:\hwids.txt and c:\devcon find* > c:\hwids.txt - I hope this is the correct method. I wasnt sure exactly what i was looking for so i have posted all HWIDS.

1. Old Fujistu Scenic Esprimo P5600 (SIS761 - Sata HD)

c:\devcon hwids * > c:\hwids.txt
CODE
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_47\_0
Name: AMD Athlon™ 64 Processor 3200+
Hardware ID's:
ACPI\AuthenticAMD_-_x86_Family_15_Model_47
*AuthenticAMD_-_x86_Family_15_Model_47
ACPI\AuthenticAMD_-_x86_Family_15
*AuthenticAMD_-_x86_Family_15
ACPI\AuthenticAMD_-_x86
*AuthenticAMD_-_x86
Compatible ID's:
ACPI\Processor
ACPI\FIXEDBUTTON\2&DABA3FF&0
Name: ACPI Fixed Feature Button
Hardware ID's:
ACPI\FixedButton
*FixedButton
ACPI\PNP0000\4&4324562&0
Name: Programmable interrupt controller
Hardware ID's:
ACPI\PNP0000
*PNP0000
ACPI\PNP0100\4&4324562&0
Name: System timer
Hardware ID's:
ACPI\PNP0100
*PNP0100
ACPI\PNP0200\4&4324562&0
Name: Direct memory access controller
Hardware ID's:
ACPI\PNP0200
*PNP0200
ACPI\PNP0303\5&2EB4D01F&0
Name: Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
Hardware ID's:
ACPI\PNP0303
*PNP0303
ACPI\PNP0401\5&2EB4D01F&0
Name: ECP Printer Port (LPT1)
Hardware ID's:
ACPI\PNP0401
*PNP0401
ACPI\PNP0501\1
Name: Communications Port (COM1)
Hardware ID's:
ACPI\PNP0501
*PNP0501
ACPI\PNP0700\5&2EB4D01F&0
Name: Standard floppy disk controller
Hardware ID's:
ACPI\PNP0700
*PNP0700
ACPI\PNP0800\4&4324562&0
Name: System speaker
Hardware ID's:
ACPI\PNP0800
*PNP0800
ACPI\PNP0A03\2&DABA3FF&0
Name: PCI bus
Hardware ID's:
ACPI\PNP0A03
*PNP0A03
ACPI\PNP0A05\4&4324562&0
Name: Generic Bus
Hardware ID's:
ACPI\PNP0A05
*PNP0A05
ACPI\PNP0B00\4&4324562&0
Name: System CMOS/real time clock
Hardware ID's:
ACPI\PNP0B00
*PNP0B00
ACPI\PNP0C02\4&4324562&0
Name: Motherboard resources
Hardware ID's:
ACPI\PNP0C02
*PNP0C02
ACPI\PNP0C04\4&4324562&0
Name: Numeric data processor
Hardware ID's:
ACPI\PNP0C04
*PNP0C04
ACPI\PNP0C0C\2&DABA3FF&0
Name: ACPI Power Button
Hardware ID's:
ACPI\PNP0C0C
*PNP0C0C
ACPI\PNP0F13\5&2EB4D01F&0
Name: PS/2 Compatible Mouse
Hardware ID's:
ACPI\PNP0F13
*PNP0F13
ACPI_HAL\PNP0C08\0
Name: Microsoft ACPI-Compliant System
Hardware ID's:
ACPI_HAL\PNP0C08
*PNP0C08
HID\VID_045E&PID_0084\6&584F0F1&0&0000
Name: HID-compliant mouse
Hardware ID's:
HID\Vid_045e&Pid_0084&Rev_0104
HID\Vid_045e&Pid_0084
HID_DEVICE_SYSTEM_MOUSE
HID_DEVICE_UP:0001_U:0002
HID_DEVICE
HID\VID_045E&PID_00B4&MI_00\7&38B1A4BF&0&0000
Name: HID Keyboard Device
Hardware ID's:
HID\Vid_045e&Pid_00b4&Rev_0143&MI_00
HID\Vid_045e&Pid_00b4&MI_00
HID_DEVICE_SYSTEM_KEYBOARD
HID_DEVICE_UP:0001_U:0006
HID_DEVICE
HID\VID_045E&PID_00B4&MI_01&COL01\7&14DA66FD&0&0000
Name: HID-compliant consumer control device
Hardware ID's:
HID\Vid_045e&Pid_00b4&Rev_0143&MI_01&Col01
HID\Vid_045e&Pid_00b4&MI_01&Col01
HID_DEVICE_SYSTEM_CONSUMER
HID_DEVICE_UP:000C_U:0001
HID_DEVICE
HID\VID_045E&PID_00B4&MI_01&COL02\7&14DA66FD&0&0001
Name: HID-compliant device
Hardware ID's:
HID\Vid_045e&Pid_00b4&Rev_0143&MI_01&Col02
HID\Vid_045e&Pid_00b4&MI_01&Col02
HID_DEVICE_SYSTEM_CONTROL
HID_DEVICE_UP:0001_U:0080
HID_DEVICE
IDE\CDROMHL-DT-ST_DVDRRW_GSA-4164B_______________1.01____\5&1129C222&0&0.0.0
Name: HL-DT-ST DVDRRW GSA-4164B
Hardware ID's:
IDE\CdRomHL-DT-ST_DVDRRW_GSA-4164B_______________1.01____
IDE\HL-DT-ST_DVDRRW_GSA-4164B_______________1.01____
IDE\CdRomHL-DT-ST_DVDRRW_GSA-4164B_______________
HL-DT-ST_DVDRRW_GSA-4164B_______________1.01____
GenCdRom
Compatible ID's:
GenCdRom
IDE\DISKST3160812AS_____________________________3.AAE___\5&1E239195&0&0.0.0
Name: ST3160812AS
Hardware ID's:
IDE\DiskST3160812AS_____________________________3.AAE___
IDE\ST3160812AS_____________________________3.AAE___
IDE\DiskST3160812AS_____________________________
ST3160812AS_____________________________3.AAE___
GenDisk
Compatible ID's:
GenDisk
ISAPNP\READDATAPORT\0
Name: ISAPNP Read Data Port
Hardware ID's:
ISAPNP\ReadDataPort
LPTENUM\MICROSOFTRAWPORT\6&D01A5BA&0&LPT1
Name: Printer Port Logical Interface
Hardware ID's:
LPTENUM\MicrosoftRawPort958A
MicrosoftRawPort958A
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&61AAA01&0&C0
Name: PCI standard host CPU bridge
Hardware ID's:
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00
PCI\VEN_1022&DEV_1100&SUBSYS_00000000
PCI\VEN_1022&DEV_1100&REV_00
PCI\VEN_1022&DEV_1100
PCI\VEN_1022&DEV_1100&CC_060000
PCI\VEN_1022&DEV_1100&CC_0600
Compatible ID's:
PCI\VEN_1022&CC_060000
PCI\VEN_1022&CC_0600
PCI\VEN_1022
PCI\CC_060000
PCI\CC_0600
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&61AAA01&0&C1
Name: PCI standard host CPU bridge
Hardware ID's:
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00
PCI\VEN_1022&DEV_1101&SUBSYS_00000000
PCI\VEN_1022&DEV_1101&REV_00
PCI\VEN_1022&DEV_1101
PCI\VEN_1022&DEV_1101&CC_060000
PCI\VEN_1022&DEV_1101&CC_0600
Compatible ID's:
PCI\VEN_1022&CC_060000
PCI\VEN_1022&CC_0600
PCI\VEN_1022
PCI\CC_060000
PCI\CC_0600
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&61AAA01&0&C2
Name: PCI standard host CPU bridge
Hardware ID's:
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00
PCI\VEN_1022&DEV_1102&SUBSYS_00000000
PCI\VEN_1022&DEV_1102&REV_00
PCI\VEN_1022&DEV_1102
PCI\VEN_1022&DEV_1102&CC_060000
PCI\VEN_1022&DEV_1102&CC_0600
Compatible ID's:
PCI\VEN_1022&CC_060000
PCI\VEN_1022&CC_0600
PCI\VEN_1022
PCI\CC_060000
PCI\CC_0600
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&61AAA01&0&C3
Name: PCI standard host CPU bridge
Hardware ID's:
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00
PCI\VEN_1022&DEV_1103&SUBSYS_00000000
PCI\VEN_1022&DEV_1103&REV_00
PCI\VEN_1022&DEV_1103
PCI\VEN_1022&DEV_1103&CC_060000
PCI\VEN_1022&DEV_1103&CC_0600
Compatible ID's:
PCI\VEN_1022&CC_060000
PCI\VEN_1022&CC_0600
PCI\VEN_1022
PCI\CC_060000
PCI\CC_0600
PCI\VEN_1039&DEV_0002&SUBSYS_00000000&REV_00\3&61AAA01&0&08
Name: SIS Processor to AGP Controller
Hardware ID's:
PCI\VEN_1039&DEV_0002&SUBSYS_00000000&REV_00
PCI\VEN_1039&DEV_0002&SUBSYS_00000000
PCI\VEN_1039&DEV_0002&REV_00
PCI\VEN_1039&DEV_0002
PCI\VEN_1039&DEV_0002&CC_060400
PCI\VEN_1039&DEV_0002&CC_0604
Compatible ID's:
PCI\VEN_1039&CC_060400
PCI\VEN_1039&CC_0604
PCI\VEN_1039
PCI\CC_060400
PCI\CC_0604
PCI\VEN_1039&DEV_0004&SUBSYS_00000000&REV_00\3&61AAA01&0&F8
Name: PCI standard PCI-to-PCI bridge
Hardware ID's:
PCI\VEN_1039&DEV_0004&SUBSYS_00000000&REV_00
PCI\VEN_1039&DEV_0004&SUBSYS_00000000
PCI\VEN_1039&DEV_0004&REV_00
PCI\VEN_1039&DEV_0004
PCI\VEN_1039&DEV_0004&CC_060400
PCI\VEN_1039&DEV_0004&CC_0604
Compatible ID's:
PCI\VEN_1039&CC_060400
PCI\VEN_1039&CC_0604
PCI\VEN_1039
PCI\CC_060400
PCI\CC_0604
PCI\VEN_1039&DEV_000A&SUBSYS_00000000&REV_00\3&61AAA01&0&30
Name: PCI standard PCI-to-PCI bridge
Hardware ID's:
PCI\VEN_1039&DEV_000A&SUBSYS_00000000&REV_00
PCI\VEN_1039&DEV_000A&SUBSYS_00000000
PCI\VEN_1039&DEV_000A&REV_00
PCI\VEN_1039&DEV_000A
PCI\VEN_1039&DEV_000A&CC_060400
PCI\VEN_1039&DEV_000A&CC_0604
Compatible ID's:
PCI\VEN_1039&CC_060400
PCI\VEN_1039&CC_0604
PCI\VEN_1039
PCI\CC_060400
PCI\CC_0604
PCI\VEN_1039&DEV_0182&SUBSYS_10951734&REV_01\3&61AAA01&0&28
Name: Standard Dual Channel PCI IDE Controller
Hardware ID's:
PCI\VEN_1039&DEV_0182&SUBSYS_10951734&REV_01
PCI\VEN_1039&DEV_0182&SUBSYS_10951734
PCI\VEN_1039&DEV_0182&CC_01018A
PCI\VEN_1039&DEV_0182&CC_0101
Compatible ID's:
PCI\VEN_1039&DEV_0182&REV_01
PCI\VEN_1039&DEV_0182
PCI\VEN_1039&CC_01018A
PCI\VEN_1039&CC_0101
PCI\VEN_1039
PCI\CC_01018A
PCI\CC_0101
PCI\VEN_1039&DEV_0761&SUBSYS_00000000&REV_01\3&61AAA01&0&00
Name: PCI standard host CPU bridge
Hardware ID's:
PCI\VEN_1039&DEV_0761&SUBSYS_00000000&REV_01
PCI\VEN_1039&DEV_0761&SUBSYS_00000000
PCI\VEN_1039&DEV_0761&REV_01
PCI\VEN_1039&DEV_0761
PCI\VEN_1039&DEV_0761&CC_060000
PCI\VEN_1039&DEV_0761&CC_0600
Compatible ID's:
PCI\VEN_1039&CC_060000
PCI\VEN_1039&CC_0600
PCI\VEN_1039
PCI\CC_060000
PCI\CC_0600
PCI\VEN_1039&DEV_0965&SUBSYS_00000000&REV_48\3&61AAA01&0&10
Name: PCI standard ISA bridge
Hardware ID's:
PCI\VEN_1039&DEV_0965&SUBSYS_00000000&REV_48
PCI\VEN_1039&DEV_0965&SUBSYS_00000000
PCI\VEN_1039&DEV_0965&REV_48
PCI\VEN_1039&DEV_0965
PCI\VEN_1039&DEV_0965&CC_060100
PCI\VEN_1039&DEV_0965&CC_0601
Compatible ID's:
PCI\VEN_1039&CC_060100
PCI\VEN_1039&CC_0601
PCI\VEN_1039
PCI\CC_060100
PCI\CC_0601
PCI\VEN_1039&DEV_5513&SUBSYS_10951734&REV_01\3&61AAA01&0&15
Name: SiS PCI IDE Controller
Hardware ID's:
PCI\VEN_1039&DEV_5513&SUBSYS_10951734&REV_01
PCI\VEN_1039&DEV_5513&SUBSYS_10951734
PCI\VEN_1039&DEV_5513&CC_01018F
PCI\VEN_1039&DEV_5513&CC_0101
Compatible ID's:
PCI\VEN_1039&DEV_5513&REV_01
PCI\VEN_1039&DEV_5513
PCI\VEN_1039&CC_01018F
PCI\VEN_1039&CC_0101
PCI\VEN_1039
PCI\CC_01018F
PCI\CC_0101
PCI\VEN_1039&DEV_6330&SUBSYS_10991734&REV_03\4&1C526AC9&0&0008
Name: Video Controller (VGA Compatible)
Hardware ID's:
PCI\VEN_1039&DEV_6330&SUBSYS_10991734&REV_03
PCI\VEN_1039&DEV_6330&SUBSYS_10991734
PCI\VEN_1039&DEV_6330&CC_030000
PCI\VEN_1039&DEV_6330&CC_0300
Compatible ID's:
PCI\VEN_1039&DEV_6330&REV_03
PCI\VEN_1039&DEV_6330
PCI\VEN_1039&CC_030000
PCI\VEN_1039&CC_0300
PCI\VEN_1039
PCI\CC_030000
PCI\CC_0300
PCI\VEN_1039&DEV_7001&SUBSYS_10951734&REV_0F\3&61AAA01&0&18
Name: SiS 7001 PCI to USB Open Host Controller
Hardware ID's:
PCI\VEN_1039&DEV_7001&SUBSYS_10951734&REV_0F
PCI\VEN_1039&DEV_7001&SUBSYS_10951734
PCI\VEN_1039&DEV_7001&CC_0C0310
PCI\VEN_1039&DEV_7001&CC_0C03
Compatible ID's:
PCI\VEN_1039&DEV_7001&REV_0F
PCI\VEN_1039&DEV_7001
PCI\VEN_1039&CC_0C0310
PCI\VEN_1039&CC_0C03
PCI\VEN_1039
PCI\CC_0C0310
PCI\CC_0C03
PCI\VEN_1039&DEV_7001&SUBSYS_10951734&REV_0F\3&61AAA01&0&19
Name: SiS 7001 PCI to USB Open Host Controller
Hardware ID's:
PCI\VEN_1039&DEV_7001&SUBSYS_10951734&REV_0F
PCI\VEN_1039&DEV_7001&SUBSYS_10951734
PCI\VEN_1039&DEV_7001&CC_0C0310
PCI\VEN_1039&DEV_7001&CC_0C03
Compatible ID's:
PCI\VEN_1039&DEV_7001&REV_0F
PCI\VEN_1039&DEV_7001
PCI\VEN_1039&CC_0C0310
PCI\VEN_1039&CC_0C03
PCI\VEN_1039
PCI\CC_0C0310
PCI\CC_0C03
PCI\VEN_1039&DEV_7001&SUBSYS_10951734&REV_0F\3&61AAA01&0&1A
Name: SiS 7001 PCI to USB Open Host Controller
Hardware ID's:
PCI\VEN_1039&DEV_7001&SUBSYS_10951734&REV_0F
PCI\VEN_1039&DEV_7001&SUBSYS_10951734
PCI\VEN_1039&DEV_7001&CC_0C0310
PCI\VEN_1039&DEV_7001&CC_0C03
Compatible ID's:
PCI\VEN_1039&DEV_7001&REV_0F
PCI\VEN_1039&DEV_7001
PCI\VEN_1039&CC_0C0310
PCI\VEN_1039&CC_0C03
PCI\VEN_1039
PCI\CC_0C0310
PCI\CC_0C03
PCI\VEN_1039&DEV_7002&SUBSYS_10951734&REV_00\3&61AAA01&0&1B
Name: SiS PCI to USB Enhanced Host Controller
Hardware ID's:
PCI\VEN_1039&DEV_7002&SUBSYS_10951734&REV_00
PCI\VEN_1039&DEV_7002&SUBSYS_10951734
PCI\VEN_1039&DEV_7002&CC_0C0320
PCI\VEN_1039&DEV_7002&CC_0C03
Compatible ID's:
PCI\VEN_1039&DEV_7002&REV_00
PCI\VEN_1039&DEV_7002
PCI\VEN_1039&CC_0C0320
PCI\VEN_1039&CC_0C03
PCI\VEN_1039
PCI\CC_0C0320
PCI\CC_0C03
PCI\VEN_1039&DEV_7012&SUBSYS_109F1734&REV_A0\3&61AAA01&0&17
Name: Multimedia Audio Controller
Hardware ID's:
PCI\VEN_1039&DEV_7012&SUBSYS_109F1734&REV_A0
PCI\VEN_1039&DEV_7012&SUBSYS_109F1734
PCI\VEN_1039&DEV_7012&CC_040100
PCI\VEN_1039&DEV_7012&CC_0401
Compatible ID's:
PCI\VEN_1039&DEV_7012&REV_A0
PCI\VEN_1039&DEV_7012
PCI\VEN_1039&CC_040100
PCI\VEN_1039&CC_0401
PCI\VEN_1039
PCI\CC_040100
PCI\CC_0401
PCI\VEN_10EC&DEV_8169&SUBSYS_10911734&REV_10\3&61AAA01&0&48
Name: Ethernet Controller
Hardware ID's:
PCI\VEN_10EC&DEV_8169&SUBSYS_10911734&REV_10
PCI\VEN_10EC&DEV_8169&SUBSYS_10911734
PCI\VEN_10EC&DEV_8169&CC_020000
PCI\VEN_10EC&DEV_8169&CC_0200
Compatible ID's:
PCI\VEN_10EC&DEV_8169&REV_10
PCI\VEN_10EC&DEV_8169
PCI\VEN_10EC&CC_020000
PCI\VEN_10EC&CC_0200
PCI\VEN_10EC
PCI\CC_020000
PCI\CC_0200
PCI\VEN_14F1&DEV_2F20&SUBSYS_200014F1&REV_00\3&61AAA01&0&50
Name: PCI Simple Communications Controller
Hardware ID's:
PCI\VEN_14F1&DEV_2F20&SUBSYS_200014F1&REV_00
PCI\VEN_14F1&DEV_2F20&SUBSYS_200014F1
PCI\VEN_14F1&DEV_2F20&CC_078000
PCI\VEN_14F1&DEV_2F20&CC_0780
Compatible ID's:
PCI\VEN_14F1&DEV_2F20&REV_00
PCI\VEN_14F1&DEV_2F20
PCI\VEN_14F1&CC_078000
PCI\VEN_14F1&CC_0780
PCI\VEN_14F1
PCI\CC_078000
PCI\CC_0780
PCIIDE\IDECHANNEL\4&296CF31D&0&0
Name: Primary IDE Channel
Hardware ID's:
SiS-0182
Primary_IDE_Channel
*PNP0600
Compatible ID's:
*PNP0600
PCIIDE\IDECHANNEL\4&296CF31D&0&1
Name: Secondary IDE Channel
Hardware ID's:
SiS-0182
Secondary_IDE_Channel
*PNP0600
Compatible ID's:
*PNP0600
PCIIDE\IDECHANNEL\4&332B8C6C&0&0
Name: Primary IDE Channel
Hardware ID's:
SiS-5513
Primary_IDE_Channel
*PNP0600
Compatible ID's:
*PNP0600
PCIIDE\IDECHANNEL\4&332B8C6C&0&1
Name: Secondary IDE Channel
Hardware ID's:
SiS-5513
Secondary_IDE_Channel
*PNP0600
Compatible ID's:
*PNP0600
ROOT\ACPI_HAL\0000
Name: ACPI Uniprocessor PC
Hardware ID's:
acpiapic_up
Compatible ID's:
DETECTEDInternal\ACPI_HAL
DETECTED\ACPI_HAL
ROOT\DMIO\0000
Name: Logical Disk Manager
Hardware ID's:
ROOT\DMIO
Compatible ID's:
DETECTEDInternal\dmio
DETECTED\dmio
ROOT\FTDISK\0000
Name: Volume Manager
Hardware ID's:
ROOT\FTDISK
Compatible ID's:
DETECTEDInternal\ftdisk
DETECTED\ftdisk
ROOT\LEGACY_AFD\0000
Name: AFD
No hardware/compatible ID's available for this device.
ROOT\LEGACY_BEEP\0000
Name: Beep
No hardware/compatible ID's available for this device.
ROOT\LEGACY_DMBOOT\0000
Name: dmboot
No hardware/compatible ID's available for this device.
ROOT\LEGACY_DMLOAD\0000
Name: dmload
No hardware/compatible ID's available for this device.
ROOT\LEGACY_FIPS\0000
Name: Fips
No hardware/compatible ID's available for this device.
ROOT\LEGACY_GPC\0000
Name: Generic Packet Classifier
No hardware/compatible ID's available for this device.
ROOT\LEGACY_HTTP\0000
Name: HTTP
No hardware/compatible ID's available for this device.
ROOT\LEGACY_IPNAT\0000
Name: IP Network Address Translator
No hardware/compatible ID's available for this device.
ROOT\LEGACY_IPSEC\0000
Name: IPSEC driver
No hardware/compatible ID's available for this device.
ROOT\LEGACY_KSECDD\0000
Name: ksecdd
No hardware/compatible ID's available for this device.
ROOT\LEGACY_MNMDD\0000
Name: mnmdd
No hardware/compatible ID's available for this device.
ROOT\LEGACY_MOUNTMGR\0000
Name: mountmgr
No hardware/compatible ID's available for this device.
ROOT\LEGACY_NDIS\0000
Name: NDIS System Driver
No hardware/compatible ID's available for this device.
ROOT\LEGACY_NDISTAPI\0000
Name: Remote Access NDIS TAPI Driver
No hardware/compatible ID's available for this device.
ROOT\LEGACY_NDPROXY\0000
Name: NDProxy
No hardware/compatible ID's available for this device.
ROOT\LEGACY_NETBT\0000
Name: NetBios over Tcpip
No hardware/compatible ID's available for this device.
ROOT\LEGACY_NULL\0000
Name: Null
No hardware/compatible ID's available for this device.
ROOT\LEGACY_PARTMGR\0000
Name: PartMgr
No hardware/compatible ID's available for this device.
ROOT\LEGACY_PARVDM\0000
Name: ParVdm
No hardware/compatible ID's available for this device.
ROOT\LEGACY_TCPIP\0000
Name: TCP/IP Protocol Driver
No hardware/compatible ID's available for this device.
ROOT\LEGACY_VGASAVE\0000
Name: VgaSave
No hardware/compatible ID's available for this device.
ROOT\LEGACY_VOLSNAP\0000
Name: VolSnap
No hardware/compatible ID's available for this device.
ROOT\LEGACY_WANARP\0000
Name: Remote Access IP ARP Driver
No hardware/compatible ID's available for this device.
ROOT\MEDIA\MS_MMACM
Name: Audio Codecs
Hardware ID's:
MS_MMACM
ROOT\MEDIA\MS_MMDRV
Name: Legacy Audio Drivers
Hardware ID's:
MS_MMDRV
ROOT\MEDIA\MS_MMMCI
Name: Media Control Devices
Hardware ID's:
MS_MMMCI
ROOT\MEDIA\MS_MMVCD
Name: Legacy Video Capture Devices
Hardware ID's:
MS_MMVCD
ROOT\MEDIA\MS_MMVID
Name: Video Codecs
Hardware ID's:
MS_MMVID
ROOT\MS_L2TPMINIPORT\0000
Name: WAN Miniport (L2TP)
Hardware ID's:
ms_l2tpminiport
ROOT\MS_NDISWANIP\0000
Name: WAN Miniport (IP)
Hardware ID's:
ms_ndiswanip
ROOT\MS_PPPOEMINIPORT\0000
Name: WAN Miniport (PPPOE)
Hardware ID's:
ms_pppoeminiport
ROOT\MS_PPTPMINIPORT\0000
Name: WAN Miniport (PPTP)
Hardware ID's:
ms_pptpminiport
ROOT\MS_PSCHEDMP\0000
Name: WAN Miniport (IP) - Packet Scheduler Miniport
Hardware ID's:
ms_pschedmp
ROOT\MS_PTIMINIPORT\0000
Name: Direct Parallel
Hardware ID's:
ms_ptiminiport
ROOT\RDPDR\0000
Name: Terminal Server Device Redirector
Hardware ID's:
ROOT\RDPDR
ROOT\RDP_KBD\0000
Name: Terminal Server Keyboard Driver
Hardware ID's:
ROOT\RDP_KBD
ROOT\RDP_MOU\0000
Name: Terminal Server Mouse Driver
Hardware ID's:
ROOT\RDP_MOU
ROOT\SYSTEM\0000
Name: Plug and Play Software Device Enumerator
Hardware ID's:
root\swenum
ROOT\SYSTEM\0001
Name: Microcode Update Device
Hardware ID's:
root\update
ROOT\SYSTEM\0002
Name: Microsoft System Management BIOS Driver
Hardware ID's:
root\mssmbios
STORAGE\REMOVABLEMEDIA\7&96DE062&0&RM
Name: Generic volume
Hardware ID's:
STORAGE\Volume
Compatible ID's:
STORAGE\Volume
STORAGE\VOLUME\1&30A96598&0&SIGNATUREAD71AD71OFFSET7E00LENGTH2542978200
Name: Generic volume
Hardware ID's:
STORAGE\Volume
USB\ROOT_HUB\4&22F7F2C&0
Name: USB Root Hub
Hardware ID's:
USB\ROOT_HUB&VID1039&PID7001&REV000F
USB\ROOT_HUB&VID1039&PID7001
USB\ROOT_HUB
USB\ROOT_HUB\4&2B10988E&0
Name: USB Root Hub
Hardware ID's:
USB\ROOT_HUB&VID1039&PID7001&REV000F
USB\ROOT_HUB&VID1039&PID7001
USB\ROOT_HUB
USB\ROOT_HUB\4&2C6831A5&0
Name: USB Root Hub
Hardware ID's:
USB\ROOT_HUB&VID1039&PID7001&REV000F
USB\ROOT_HUB&VID1039&PID7001
USB\ROOT_HUB
USB\ROOT_HUB20\4&37800789&0
Name: USB Root Hub
Hardware ID's:
USB\ROOT_HUB20&VID1039&PID7002&REV0000
USB\ROOT_HUB20&VID1039&PID7002
USB\ROOT_HUB20
USB\VID_045E&PID_0084\5&7EE5FED&0&3
Name: USB Human Interface Device
Hardware ID's:
USB\Vid_045e&Pid_0084&Rev_0104
USB\Vid_045e&Pid_0084
Compatible ID's:
USB\Class_03&SubClass_01&Prot_02
USB\Class_03&SubClass_01
USB\Class_03
USB\VID_045E&PID_00B4\5&18E526C4&0&3
Name: USB Composite Device
Hardware ID's:
USB\Vid_045e&Pid_00b4&Rev_0143
USB\Vid_045e&Pid_00b4
Compatible ID's:
USB\DevClass_00&SubClass_00&Prot_00
USB\DevClass_00&SubClass_00
USB\DevClass_00
USB\COMPOSITE
USB\VID_045E&PID_00B4&MI_00\6&3AE2CD1A&0&0000
Name: USB Human Interface Device
Hardware ID's:
USB\Vid_045e&Pid_00b4&Rev_0143&MI_00
USB\Vid_045e&Pid_00b4&MI_00
Compatible ID's:
USB\Class_03&SubClass_01&Prot_01
USB\Class_03&SubClass_01
USB\Class_03
USB\VID_045E&PID_00B4&MI_01\6&3AE2CD1A&0&0001
Name: USB Human Interface Device
Hardware ID's:
USB\Vid_045e&Pid_00b4&Rev_0143&MI_01
USB\Vid_045e&Pid_00b4&MI_01
Compatible ID's:
USB\Class_03&SubClass_00&Prot_00
USB\Class_03&SubClass_00
USB\Class_03
USB\VID_0781&PID_5530\200522437013C0E27C0A
Name: USB Mass Storage Device
Hardware ID's:
USB\Vid_0781&Pid_5530&Rev_0100
USB\Vid_0781&Pid_5530
Compatible ID's:
USB\Class_08&SubClass_06&Prot_50
USB\Class_08&SubClass_06
USB\Class_08
USBSTOR\DISK&VEN_SANDISK&PROD_CRUZER&REV_1.00\200522437013C0E27C0A&0
Name: SanDisk Cruzer USB Device
Hardware ID's:
USBSTOR\DiskSanDisk_Cruzer__________1.00
USBSTOR\DiskSanDisk_Cruzer__________
USBSTOR\DiskSanDisk_
USBSTOR\SanDisk_Cruzer__________1
SanDisk_Cruzer__________1
USBSTOR\GenDisk
GenDisk
Compatible ID's:
USBSTOR\Disk
USBSTOR\RAW
104 matching device(s) found.


c:\devcon find* > c:\hwids.txt
CODE
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_47\_0 : AMD Athlon™ 64 Processor 3200+
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI Fixed Feature Button
ACPI\PNP0000\4&4324562&0 : Programmable interrupt controller
ACPI\PNP0100\4&4324562&0 : System timer
ACPI\PNP0200\4&4324562&0 : Direct memory access controller
ACPI\PNP0303\5&2EB4D01F&0 : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0401\5&2EB4D01F&0 : ECP Printer Port (LPT1)
ACPI\PNP0501\1 : Communications Port (COM1)
ACPI\PNP0700\5&2EB4D01F&0 : Standard floppy disk controller
ACPI\PNP0800\4&4324562&0 : System speaker
ACPI\PNP0A03\2&DABA3FF&0 : PCI bus
ACPI\PNP0A05\4&4324562&0 : Generic Bus
ACPI\PNP0B00\4&4324562&0 : System CMOS/real time clock
ACPI\PNP0C02\4&4324562&0 : Motherboard resources
ACPI\PNP0C04\4&4324562&0 : Numeric data processor
ACPI\PNP0C0C\2&DABA3FF&0 : ACPI Power Button
ACPI\PNP0F13\5&2EB4D01F&0 : PS/2 Compatible Mouse
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
HID\VID_045E&PID_0084\6&584F0F1&0&0000 : HID-compliant mouse
HID\VID_045E&PID_00B4&MI_00\7&38B1A4BF&0&0000 : HID Keyboard Device
HID\VID_045E&PID_00B4&MI_01&COL01\7&14DA66FD&0&0000 : HID-compliant consumer control device
HID\VID_045E&PID_00B4&MI_01&COL02\7&14DA66FD&0&0001 : HID-compliant device
IDE\CDROMHL-DT-ST_DVDRRW_GSA-4164B_______________1.01____\5&1129C222&0&0.0.0: HL-DT-ST DVDRRW GSA-4164B
IDE\DISKST3160812AS_____________________________3.AAE___\5&1E239195&0&0.0.0: ST3160812AS
ISAPNP\READDATAPORT\0 : ISAPNP Read Data Port
LPTENUM\MICROSOFTRAWPORT\6&D01A5BA&0&LPT1 : Printer Port Logical Interface
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&61AAA01&0&C0 : PCI standard host CPU bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&61AAA01&0&C1 : PCI standard host CPU bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&61AAA01&0&C2 : PCI standard host CPU bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&61AAA01&0&C3 : PCI standard host CPU bridge
PCI\VEN_1039&DEV_0002&SUBSYS_00000000&REV_00\3&61AAA01&0&08 : SIS Processor to AGP Controller
PCI\VEN_1039&DEV_0004&SUBSYS_00000000&REV_00\3&61AAA01&0&F8 : PCI standard PCI-to-PCI bridge
PCI\VEN_1039&DEV_000A&SUBSYS_00000000&REV_00\3&61AAA01&0&30 : PCI standard PCI-to-PCI bridge
PCI\VEN_1039&DEV_0182&SUBSYS_10951734&REV_01\3&61AAA01&0&28 : Standard Dual Channel PCI IDE Controller
PCI\VEN_1039&DEV_0761&SUBSYS_00000000&REV_01\3&61AAA01&0&00 : PCI standard host CPU bridge
PCI\VEN_1039&DEV_0965&SUBSYS_00000000&REV_48\3&61AAA01&0&10 : PCI standard ISA bridge
PCI\VEN_1039&DEV_5513&SUBSYS_10951734&REV_01\3&61AAA01&0&15 : SiS PCI IDE Controller
PCI\VEN_1039&DEV_6330&SUBSYS_10991734&REV_03\4&1C526AC9&0&0008: Video Controller (VGA Compatible)
PCI\VEN_1039&DEV_7001&SUBSYS_10951734&REV_0F\3&61AAA01&0&18 : SiS 7001 PCI to USB Open Host Controller
PCI\VEN_1039&DEV_7001&SUBSYS_10951734&REV_0F\3&61AAA01&0&19 : SiS 7001 PCI to USB Open Host Controller
PCI\VEN_1039&DEV_7001&SUBSYS_10951734&REV_0F\3&61AAA01&0&1A : SiS 7001 PCI to USB Open Host Controller
PCI\VEN_1039&DEV_7002&SUBSYS_10951734&REV_00\3&61AAA01&0&1B : SiS PCI to USB Enhanced Host Controller
PCI\VEN_1039&DEV_7012&SUBSYS_109F1734&REV_A0\3&61AAA01&0&17 : Multimedia Audio Controller
PCI\VEN_10EC&DEV_8169&SUBSYS_10911734&REV_10\3&61AAA01&0&48 : Ethernet Controller
PCI\VEN_14F1&DEV_2F20&SUBSYS_200014F1&REV_00\3&61AAA01&0&50 : PCI Simple Communications Controller
PCIIDE\IDECHANNEL\4&296CF31D&0&0 : Primary IDE Channel
PCIIDE\IDECHANNEL\4&296CF31D&0&1 : Secondary IDE Channel
PCIIDE\IDECHANNEL\4&332B8C6C&0&0 : Primary IDE Channel
PCIIDE\IDECHANNEL\4&332B8C6C&0&1 : Secondary IDE Channel
ROOT\ACPI_HAL\0000 : ACPI Uniprocessor PC
ROOT\DMIO\0000 : Logical Disk Manager
ROOT\FTDISK\0000 : Volume Manager
ROOT\LEGACY_AFD\0000 : AFD
ROOT\LEGACY_BEEP\0000 : Beep
ROOT\LEGACY_DMBOOT\0000 : dmboot
ROOT\LEGACY_DMLOAD\0000 : dmload
ROOT\LEGACY_FIPS\0000 : Fips
ROOT\LEGACY_GPC\0000 : Generic Packet Classifier
ROOT\LEGACY_HTTP\0000 : HTTP
ROOT\LEGACY_IPNAT\0000 : IP Network Address Translator
ROOT\LEGACY_IPSEC\0000 : IPSEC driver
ROOT\LEGACY_KSECDD\0000 : ksecdd
ROOT\LEGACY_MNMDD\0000 : mnmdd
ROOT\LEGACY_MOUNTMGR\0000 : mountmgr
ROOT\LEGACY_NDIS\0000 : NDIS System Driver
ROOT\LEGACY_NDISTAPI\0000 : Remote Access NDIS TAPI Driver
ROOT\LEGACY_NDPROXY\0000 : NDProxy
ROOT\LEGACY_NETBT\0000 : NetBios over Tcpip
ROOT\LEGACY_NULL\0000 : Null
ROOT\LEGACY_PARTMGR\0000 : PartMgr
ROOT\LEGACY_PARVDM\0000 : ParVdm
ROOT\LEGACY_TCPIP\0000 : TCP/IP Protocol Driver
ROOT\LEGACY_VGASAVE\0000 : VgaSave
ROOT\LEGACY_VOLSNAP\0000 : VolSnap
ROOT\LEGACY_WANARP\0000 : Remote Access IP ARP Driver
ROOT\MEDIA\MS_MMACM : Audio Codecs
ROOT\MEDIA\MS_MMDRV : Legacy Audio Drivers
ROOT\MEDIA\MS_MMMCI : Media Control Devices
ROOT\MEDIA\MS_MMVCD : Legacy Video Capture Devices
ROOT\MEDIA\MS_MMVID : Video Codecs
ROOT\MS_L2TPMINIPORT\0000 : WAN Miniport (L2TP)
ROOT\MS_NDISWANIP\0000 : WAN Miniport (IP)
ROOT\MS_PPPOEMINIPORT\0000 : WAN Miniport (PPPOE)
ROOT\MS_PPTPMINIPORT\0000 : WAN Miniport (PPTP)
ROOT\MS_PSCHEDMP\0000 : WAN Miniport (IP) - Packet Scheduler Miniport
ROOT\MS_PTIMINIPORT\0000 : Direct Parallel
ROOT\RDPDR\0000 : Terminal Server Device Redirector
ROOT\RDP_KBD\0000 : Terminal Server Keyboard Driver
ROOT\RDP_MOU\0000 : Terminal Server Mouse Driver
ROOT\SYSTEM\0000 : Plug and Play Software Device Enumerator
ROOT\SYSTEM\0001 : Microcode Update Device
ROOT\SYSTEM\0002 : Microsoft System Management BIOS Driver
STORAGE\REMOVABLEMEDIA\7&96DE062&0&RM : Generic volume
STORAGE\VOLUME\1&30A96598&0&SIGNATUREAD71AD71OFFSET7E00LENGTH2542978200: Generic volume
USB\ROOT_HUB\4&22F7F2C&0 : USB Root Hub
USB\ROOT_HUB\4&2B10988E&0 : USB Root Hub
USB\ROOT_HUB\4&2C6831A5&0 : USB Root Hub
USB\ROOT_HUB20\4&37800789&0 : USB Root Hub
USB\VID_045E&PID_0084\5&7EE5FED&0&3 : USB Human Interface Device
USB\VID_045E&PID_00B4\5&18E526C4&0&3 : USB Composite Device
USB\VID_045E&PID_00B4&MI_00\6&3AE2CD1A&0&0000 : USB Human Interface Device
USB\VID_045E&PID_00B4&MI_01\6&3AE2CD1A&0&0001 : USB Human Interface Device
USB\VID_0781&PID_5530\200522437013C0E27C0A : USB Mass Storage Device
USBSTOR\DISK&VEN_SANDISK&PROD_CRUZER&REV_1.00\200522437013C0E27C0A&0: SanDisk Cruzer USB Device
104 matching device(s) found.


The other machine is a Acer Power M8. I can post the hwids if you think it might help? The interesting thing is i can see the Sata HD with BARTPE (i used the driverpacks integrated into bartpe) so from that aspect i think the driverpacks are working and therefore the HD hardware is support by driverpacks.

2. Step 3: BASE/MassStorage Plugin preparation/integration. What are you getting me to test. Removal of massstorage plugin from bartpe or massstorage folder in offlinesysprep or both? If i remove plugin from BARTPE wont this stop me being able to see HD when booting from BARTPE?


3. See image for BSOD error below
Click to view attachment

Thanks
cdob
How do you create your offline image?
Do you use a Intel CPU?
Read http://support.microsoft.com/kb/953356

Try use advaned options, disable intelppm if present.
Yakuzi
Im just re-imaging now this time using the Stop Intelppm AMDk7 and agp440 services feature in offinesysprep. Fingers crossed. Will let you know as soon as im done.
Yakuzi
Hi Guys

Ok. Excellent news. I disabled the AMDk7, agp440 and Intelppm services in offlinesysprep and deployed the new image on a sata machine. It worked!

- Base Image sysprep'd machine is Intel, Unicore IDE Harddrive
- Deployed to AMD, ulti processor, SATA Harddive

GOOD TIMES!!!!!! and obviously not to do with injecting SATA drivers so I appologies for jumping to the wrong conclusion

One final question. On the newly imaged machine I get left with this in device manager:

Click to view attachment

Ive read that i need to re-enable it using this command: enable intelppm SERVICE_SYSTEM_START. This doesnt seem to work though sad.gif - Also is there a way of automating this on the newly deployed image?

Thanks again for all help guys!!!!
pwagner9999
QUOTE (Yakuzi @ Nov 8 2010, 11:15 AM) *
Hi Guys
Ive read that i need to re-enable it using this command: enable intelppm SERVICE_SYSTEM_START. This doesnt seem to work though sad.gif - Also is there a way of automating this on the newly deployed image?




I just uninstall the cpu from the device manager and reboot.
cdob
QUOTE
I disabled the AMDk7, agp440 and Intelppm services in offlinesysprep and deployed the new image on a sata machine. It worked!

Main difference is not sata, it's cpu.
Even big OEM created broken sysprep images in the past.

QUOTE
enable intelppm SERVICE_SYSTEM_START. This doesnt seem to work though sad.gif - Also is there a way of automating this on the newly deployed image?

Use another approach:
Don't disable amdk7, agp440, intelppm. Set demand start: start=3
Load offline registry and change settings manually.
jaclaz
QUOTE (Yakuzi @ Nov 8 2010, 05:15 PM) *
GOOD TIMES!!!!!! and obviously not to do with injecting SATA drivers so I appologies for jumping to the wrong conclusion

As a general rule of the thumb, a Mass Storage device gives BSOD 0x0000007b - Inaccessible Boot Device.

0x0000007E is more likely to be *another* driver, often (but not always) the processor one.

http://kadaitcha.cx/xp/stop_error.html
http://kadaitcha.cx/xp/stop_error.html#0x0000007E

jaclaz
Yakuzi
Thanks for everyones input. I'm going to stick with what pwagner9999 and uninstall the device and reboot. Going to test some more machines tomorrow for deployment!
Galapo
Hi cdob,

Thanks for clearing things up!

I'd asked for the bsod message as I was beginning to think it was less a mass storage driver issue and more a processor driver issue. I'm glas things are now working.

QUOTE (cdob @ Nov 9 2010, 02:37 AM) *
Don't disable amdk7, agp440, intelppm. Set demand start: start=3

Do you think I should have OfflineSysPrep set these drivers to demand start rather than disable?

Thanks,
Galapo.
Yakuzi
QUOTE (Galapo @ Nov 8 2010, 07:07 PM) *
Hi cdob,

Thanks for clearing things up!

I'd asked for the bsod message as I was beginning to think it was less a mass storage driver issue and more a processor driver issue. I'm glas things are now working.


Do you think I should have OfflineSysPrep set these drivers to demand start rather than disable?

Thanks,
Galapo.


What is the difference between demand start and disable? Upon first boot what would be happening?

Thanks again!
jaclaz
QUOTE (Yakuzi @ Nov 9 2010, 11:02 AM) *
What is the difference between demand start and disable? Upon first boot what would be happening?

Thanks again!


If *something* asks (politely) a service set "on demand" to start, the Service will reply:
QUOTE (Service_asked_to_start)
Sure smile.gif, I wish to thank you for this question (and will start thumbsup.gif ).


If *something* asks (politely or not) a service set "disabled" to start, the Service will reply:
QUOTE (Service_asked_to_start)
Sorry dude sad.gif , I am disabled and CANNOT start, no matter how nicely you ask for it (and won't start thumbdown.gif ).


wink.gif

happy71.gif

jaclaz

Yakuzi
QUOTE (jaclaz @ Nov 9 2010, 06:20 AM) *
If *something* asks (politely) a service set "on demand" to start, the Service will reply:


If *something* asks (politely or not) a service set "disabled" to start, the Service will reply:


wink.gif

happy71.gif

jaclaz


Excellent. Thanks Jaclaz. You can probably tell this is a learning curve for me:) So my understanding is that if I set demand start to 3, upon reboot the service wont start until i go into device manager (or from command prompt) and restart it manually. If set to disabled I would not be able to do this and would have to use one of CDbob's alternatives or uninstall device and reboot.

My next stupid question is where is the reg key/binary value for Demand Start or is this the same start binary value in HKLM - System - ControlSet001 - Services - Intelppm - Start?

Thank you very much
cdob
QUOTE (Galapo @ Nov 9 2010, 12:07 AM) *
Do you think I should have OfflineSysPrep set these drivers to demand start rather than disable?

I'm not shure yet. Hopefully a user can verify this.

Anyway service starts, if CriticalDeviceDatabase or ENUM match a current HardwareID.
Example: intelppm won't start at a AMD machine.

QUOTE (Yakuzi @ Nov 9 2010, 12:05 PM) *
So my understanding is that if I set demand start to 3, upon reboot the service wont start until i go into device manager (or from command prompt) and restart it manually.

Service start and device manager are different.
A service may run, despide device manager view.

Demand start services run at existing registry settings and given hardware.

At a new machine PNP may load drivers at boot, read device mangager list device or not.
Try and report.

QUOTE
My next stupid question is where is the reg key/binary value for Demand Start or is this the same start binary value in HKLM - System - ControlSet001 - Services - Intelppm - Start?
Yes, it's often ControlSet001 - Services - Intelppm - Start.
May be another ControlSetNNN.

QUOTE (Yakuzi @ Nov 5 2010, 06:34 PM) *
Here is my full process:
A major condition is missing: how do you create the image file?
Which hardware do you use to install windows?
jaclaz

QUOTE
... until i go into device manager (or from command prompt) and restart it manually

Yep, UNLESS *something* ELSE asks the Service to start (like Plug'nPlay, boot-time detection, installer or co-installer of something, etc.)

Values given here:
http://www.boot-land.net/forums/index.php?...=8804&st=28

jaclaz
Yakuzi
QUOTE (cdob @ Nov 9 2010, 07:32 AM) *
A major condition is missing: how do you create the image file?
Which hardware do you use to install windows?


How do i create the image file - I have an SOE build which I follow. When it comes to Image creation after sysprep I use ghost from BARTPE and then immediately capture the image using WDS. That way i have 2 deployment methods (.GHO and .WIM)

Hardware for Windows - I use an old Fujitsu Scenic P300 as my base machine. IDE, Intel Celeron uni, ACPI.

Both these procedures i have documented in detail incase any more detail is required.
Galapo
Hi cdob,

Thanks for your comments. I think I may make a change and see what happens. But when I'm less busy. This isn't really that important.

Thanks,
Galapo.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2013 Invision Power Services, Inc.