One option would be extract the .ISO and run WinBuilder on it, specifically just the DP mass storage script which comes with LiveXP. What I would do is do a first-run creating a normal LiveXP build, then adjust to point to extracted ISO and run the mass storage script against this. Mass storage drivers will be injected, services added, txtsetup.sif entries added, etc.

Regards,
Galapo.

102

(2 replies, posted in Software)

There's scripts available to add mass storage and lan drivers to any nativeEx xp- or 2k3-based WinBuilder project, eg LiveXP: http://winbuilder.net/download.php?view.8

VistaPE can also integrate drivers.

Regards,
Galapo.

The reason is because your hwid -- VEN_8086&DEV_2824 -- does not appear in this release either.

Regards,
Galapo.

104

(8 replies, posted in DriverPack Mass Storage)

Lancelot ran some tests for me and it's confirmed working.

\D\M\I3\iaahci.inf

...
[ControlFlags]
...
ExcludeFromSelect=PCI\VEN_8086&DEV_2824&CC_0106
...
[INTEL_HDC]
...
; ICH8 82801HB
%PCI\VEN_8086&DEV_2824&CC_0106.DeviceDesc% = iaStor_mobl_Inst_RAID, PCI\VEN_8086&DEV_2824&CC_0106
...
[Strings]
...
PCI\VEN_8086&DEV_2824&CC_0106.DeviceDesc	= "Intel(R) 82801HB SATA AHCI Controller"
...

DriverPack_MassStorage_wnt5_x86-32.ini

...
[I3]
ms_count=1
ms_1_deviceName="Intel ESB2/ICH7/ICH8/ICH9/ICH10 SATA AHCI/RAID 7.8.0.1012"
ms_1_tag="iastor78"
ms_1_sysFile="iastor.sys"
ms_1_hwids="PCI\VEN_8086&DEV_2922&CC_0106,PCI\VEN_8086&DEV_282A&CC_0104,PCI\VEN_8086&DEV_2829&CC_0106,PCI\VEN_8086&DEV_2822&CC_0104,PCI\VEN_8086&DEV_2821&CC_0106,PCI\VEN_8086&DEV_2682&CC_0104,PCI\VEN_8086&DEV_2681&CC_0106,PCI\VEN_8086&DEV_27C3&CC_0104,PCI\VEN_8086&DEV_27C6&CC_0104,PCI\VEN_8086&DEV_27C1&CC_0106,PCI\VEN_8086&DEV_27C5&CC_0106,PCI\VEN_8086&DEV_2653&CC_0106,PCI\VEN_8086&DEV_2824&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"
...

Regards,
Galapo.

105

(8 replies, posted in DriverPack Mass Storage)

This is a post following the tests of Lancelot from here: http://www.boot-land.net/forums/index.p … mp;p=39193

hwids of the device are:

PCI\VEN_197B&DEV_2363&SUBSYS_81E41043&REV_03\4&18CD42CE&0&00E4: JMicron JMB36X Controller
PCI\VEN_197B&DEV_2363&SUBSYS_81E41043&REV_03\4&18CD42CE&0&01E4: Standard Dual Channel PCI IDE Controller
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_F2\3&11583659&0&F0: Intel® 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2810&SUBSYS_00000000&REV_02\3&11583659&0&F8: Intel® ICH8/ICH8R Family LPC Interface Controller - 2810
PCI\VEN_8086&DEV_2824&SUBSYS_81EC1043&REV_02\3&11583659&0&FA: Intel® ICH9 SATA AHCI Controller
PCI\VEN_8086&DEV_2830&SUBSYS_81EC1043&REV_02\3&11583659&0&E8: Intel® ICH8 Family USB Universal Host Controller - 2830
PCI\VEN_8086&DEV_2831&SUBSYS_81EC1043&REV_02\3&11583659&0&E9: Intel® ICH8 Family USB Universal Host Controller - 2831
PCI\VEN_8086&DEV_2832&SUBSYS_81EC1043&REV_02\3&11583659&0&EA: Intel® ICH8 Family USB Universal Host Controller - 2832
PCI\VEN_8086&DEV_2834&SUBSYS_81EC1043&REV_02\3&11583659&0&D0: Intel® ICH8 Family USB Universal Host Controller - 2834
PCI\VEN_8086&DEV_2835&SUBSYS_81EC1043&REV_02\3&11583659&0&D1: Intel® ICH8 Family USB Universal Host Controller - 2835
PCI\VEN_8086&DEV_2836&SUBSYS_81EC1043&REV_02\3&11583659&0&EF: Intel® ICH8 Family USB2 Enhanced Host Controller - 2836
PCI\VEN_8086&DEV_283A&SUBSYS_81EC1043&REV_02\3&11583659&0&D7: Intel® ICH8 Family USB2 Enhanced Host Controller - 283A
PCI\VEN_8086&DEV_283E&SUBSYS_81EC1043&REV_02\3&11583659&0&FB: Intel® ICH8 Family SMBus Controller - 283E
PCI\VEN_8086&DEV_283F&SUBSYS_00000000&REV_02\3&11583659&0&E0: Intel® ICH8 Family PCI Express Root Port 1 - 283F
PCI\VEN_8086&DEV_2845&SUBSYS_00000000&REV_02\3&11583659&0&E3: Intel® ICH8 Family PCI Express Root Port 4 - 2845
PCI\VEN_8086&DEV_2847&SUBSYS_00000000&REV_02\3&11583659&0&E4: Intel® ICH8 Family PCI Express Root Port 5 - 2847
PCI\VEN_8086&DEV_284B&SUBSYS_81EC1043&REV_02\3&11583659&0&D8: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_29A0&SUBSYS_00000000&REV_02\3&11583659&0&00: Intel® P965/G965/G35 Processor to I/O Controller - 29A0
PCI\VEN_8086&DEV_29A1&SUBSYS_00000000&REV_02\3&11583659&0&08: Intel® P965/G965/G35 PCI Express Root Port - 29A1

Specifically, the drivers under \D\M\I3\*.* support the hwid VEN_8086&DEV_2824, so it would seem an easy modification to offically support an additional device.

Regards,
Galapo.

Options:

1. peimg.exe
http://www.911cd.net/forums//index.php? … p;p=141825
http://www.911cd.net/forums//index.php? … p;p=144098

2. OfflineSysPrep
http://www.911cd.net/forums//index.php?showtopic=19397

3. TeraByte OS Deployment Tool Suite
http://www.terabyteunlimited.com/tbosdt.htm

Regards,
Galapo.

cdob wrote:

@Galapo
Boot regular windows or PE: add driver and settings to \cmdcons.

Hmmm, never thought of doing that. But then, I never really actually use recovery console (I make frequent backups).

Wish I had more time...

Regards,
Galapo.

cdob wrote:
McStarfighter wrote:

You can install the recovery console to HD with the command "...\I386\winnt32.exe" /CMDCONS /UNATTENDED.

OfflineSysprep and fix_hdc could be enhanced: add required drivers only from a offline system.

Hi cdob,

Not quite sure what you mean: did you intend "from an offline system" or "to an offline system"?

Thanks,
Galapo.

Creating a Recovery Console CD with sata is indeed possible. You need to use WinBuilder and the nativeEx_BSOR project: http://www.boot-land.net/forums/?showtopic=3720

To get sata drivers into the project, you need to add my DriverPacks-Build_MassStorageDrivers script: http://galapo.boot-land.net/scripts/dri … ers.script

Outputted ISO has Recovery Console with DriverPacks mass storage drivers integrated.

Regards,
Galapo.

Phyxx wrote:

Acronis UR (I believe) does not scan for drivers outside of %windir%/inf,

If drivers are already located in '%windir%/inf', that would suggest they have already been integrated into the image. It's been a while since I've used UR, but from memory, you are presented the option of optionally selecting a path to scan for additional mass storage drivers.

Regards,
Galapo.

Is burning to DVD an option?

Regards,
Galapo.

DeTard wrote:

Edit:  Galapo, another thought since you're on the subject of revisions to OSP - any chance you could make it so that some features will still work on a running install?  I'm sure some functions shouldn't be ran on a running partition, but things like injecting the drivers would be nice to not have to boot into a BartPE ISO (Yes, I'm being lazy here, just humor me and say THAT'S UNPOSSIBLE, thanks smile)

Of course! Version 2 is going to offer this as an option. From memory, I think the coding for this has been done. But note: driver injection into a RUNNING system is not as neat as for an offline one. So to inject drivers into a running system, the conventional way of using sysprep.inf must be used.

Regards,
Galapo.

JakeLD wrote:

Step2. Run OfflineSysprep with predefined settings silently (possible in version 2.0, correct me if i'm wrong Galapo big_smile)

Yes, the plan definitely is to move to offering the option of being able to run silently from predefined settings via commandline. Whether we'll be able to offer this straight up with 2.0 is a good question and one I can't answer just yet. I'm, awaiting alpha code from thecharliec still to know myself just what will be on offer in the next major version.

I was just thinking: maybe it would even be good to offer the option of running OfflineSysPrep but selecting to DELAY running the selected options but instead run them on next start via 'HKLM\SYSTEM\Setup,CmdLine' entry? This way HAL for example is not set until first boot as with MySysprep.

Tip Of the Day: Use VmWare to make your image and then convert the machine to your favorite image format (ex: Acronis) You can use VMWare Converter. So you don't need to boot in PE emuling an ISO and then take your image and save it to a network share.

VMWare Converter can come in handy. Which reminds me also: I really should get around to uploading my script for it for use in LiveXP. Converter from PE is a useful option.

Regards,
Galapo.

DeTard wrote:

Edit:  Blah, downloading Server 2003 SP3 64-bit right now to get the NTLDR file for use with it.

Is sp3 for 2k3 out is it?

Injecting drivers ONLY is indeed one intended function of OfflineSysPrep. Hope you have success! Note, though: a full pnp after first boot is definitely recommended. Which reminds me: I should allow for the possibility of running spdrvscn not just in conjunction with sysprep mini-setup as in your scenario it is probably preferrable to using SetupCopyOEMInf.

Regards,
Galapo.

DeTard wrote:

If it's still available, I'd be very surprised... I've been looking for it for like 8 months now without success.

http://www.computeractive.co.uk/hdmanager8/index
http://registry.paragon-software.com/hdm8pers/

ilko wrote:

Not quite sure if you can deploy the image and make the new contents visible to PE and OFSP without restart, but should be doable.

Might depend on the imaging software used perhaps. I use DriveSnapshot myself and can run OSP after imaging without a reboot.

ilko wrote:

Or if you have already your generic image, and lets say buy a new hardware, or replace a motherboard with different one.

This is my own personal reason for creating this little tool. Sometimes I don't want to install from scratch when replacing a motherboard etc. This at least provides the option of not having to. At the requests of others, the usefulness of the tool has been extended beyond this now.

Regards,
Galapo.

DeTard wrote:

So is there a way to do this so that I can deploy it and have it run OFSP on it's own without me having to sit at each individual computer, or no?

No yet, but in version two we're working towards being able to have it automated.

Regards,
Galapo.

That's OK. No particular rush. I'm just curious is all.

Regards,
Galapo.

ilko wrote:

Just tried it with NTLDR from i386 SP3 and x64 SP2, switched to standard HAL and added /detecthal- no result, neither error messages, nor HAL changed.

Did you follow the steps provided by Oleg: http://www.911cd.net/forums//index.php? … ntry144100

Hi Ilko,

Good to hear from you -- and thanks for continuing to test!

I hadn't yet gotten to testing ntldr from sp3 today as planned. I guess now I have a reason to download the x64 sp.

By the way, do you know if the newer ntldr allows for "dynamic" HAL via boot.ini /detecthal entry etc as per Longhorn?

Regards,
Galapo.

OverFlow wrote:

I suppose that the dup file name prob still exists...

Yes, but it's only an issue if injecting DP mass storage drivers "directly" via peimg rather than the current OfflineSysPrep method of injecting based upon the BartPE plugin.

With version 2 of OfflineSysPrep both of these two methods of injecting drivers into an offline system will be offered.

Regards,
Galapo.

Wow, that's good to hear! Does sp3 replace ntldr?

Thanks,
Galapo.

OverFlow wrote:

Then you are in violation of the MS Licensing agreement. (unless you want to buy a 2003 license for your XP)
So we cannot recomend that people do that.

Yes, that's right.

Is that also the case with Longhorn files?

Regards,
Galapo.

Galapo wrote:

Yes, with this method whatever drivers get injected all get loaded. With the injection method internal to OfflineSysPrep it is only the main driver files, no secondary drivers. Full PNP after first boot is probably mandatory. Injecting with peimg is a different matter as the installation is directly via the .inf, so whatever drivers there that are references get injected and consequently loaded. With the setup routine there will be far less services running so that no memory limit is currently breached, but it seems injecting drivers into an already installed system that limit can be reached, at least under the conditions and methods I've tested here.

Turns out that it is very likely to be a memory limit rather than a buggy driver. Testing the suggestion posted here

http://forum.driverpacks.net/viewtopic. … 576#p18576

of replacing ntldr from longhorn (I tried 4053) results in a booting system and no longer the 'ntfs.sys' error. Memory limits seem to have been increased.

Regards,
Galapo.

Note, though:

1. You are limited by memory limits:
http://forum.driverpacks.net/viewtopic. … 932#p17932
http://www.911cd.net/forums//index.php? … p;p=142720

2. You are limited to drivers which maintain separate driver names and service names.

Regards,
Galapo.