Search options (Page 3 of 7)

Good news! While devcon doesn't actually cause a reboot, when the app that is running as shell closes, the type of reboot that is performed does not have the hang. So devcon makes the reboot a "better" type of reboot and so I don't have to have a sysprep dependency. I'll release a new version later today.

Regards,
Galapo.

Unfortunately, no.

I've also tried PsShutdown, PowerOff, and fdapm.

Regards,
Galapo.

Yes, you get an ntfs.sys error. This doesn't occur with PE because limit is not yet reached as cabbed drivers are supported.

Sorry, I wasn't saying to use more than one. I'm saying if you need to inject all the drivers, then you'll need to replace the default ntldr with one that has a higher memory limit. But this would seem to break licensing agreement, though.

Regards,
Galapo.

Actually, that's not entirely true. OSP can perform much of what sysprep does with running it. That is, it is a "generalisation" process to ready the system/image to be deployed onto different hardward. Drivers may be injected, and "specificity" is basically limited to how many drivers you decide to inject. If you choose to inject all the DP mass storage drivers, then so many are injected that native ntldr cannot cope (have to resort to xp 64-bit version etc.). So in this case, it is not making it "very specific".

In the case of HAL, yes, it is specific to the option chosen. The plan in OSP version 2 is for OSP be able to run from commandline or supplied INI file and be able to do HAL setting on first boot. If I get time, I might be able to add this feature to version 1 perhaps if it's useful.

Regards,
Galapo.

Exactly! And so OfflineSysPrep was born, which allows for sysprepping options but no mass storage injection from sysprep.inf. This is instead accomplished by DP mass storage plugin data because there hwids are tied to unique service names and driver files.

As a minimum you need:
1. CriticalDeviceDatabase entry with a) hwid; b) ClassGUID; c) Service.
2. Serice entry added under current ControlSet with a) DisplayName; b) ErrorControl (00000001); c) Group; Start (00000000). Optional: Tag. Sometimes required: PnpInterface.

Of course, other option is to edit INFs and rename files (as driver manufactures should be releasing them like this in the first place) so that they conform for use with sysprep.

Regards,
Galapo.

The only program I've found which accurately detects both Intel and AMD processors is this: http://crystalmark.info/software/Crysta … dex-e.html. It is scriptable and so can be used for the correct detecting of necessary HAL. Both PantherXP (http://pantherxp.net/) and OfflineSysPrep make use of it now.

Regards,
Galapo.

Note: I have discovered a bug with the 'Install only PE-detected non-IDE Mass Storage Device(s)' option. Only devices with HWIDs with 'PCI\' are injected. So HWIDs like 'SCSI\', 'GenNvRaidDisk', '*NVRAIDBUS' won't be injected with this method (well, until I can do a fix, which seems a bit unlikely at the moment).

So, work-around is to make use of user_settings.ini file and enable desired drivers. Eg:

[disable_drivers]
all=disable

[enable_drivers]
qnvrd325=enable
qnvraid=enable

Regards,
Galapo.

I'm not sure he said he was using pirated OS. Only issue is Longhorn's ntldr. Chinese sites were first to list details of how that version of ntldr can do automatic HAL detection and switch on each boot for XP (instead of using all those boot.ini entries you commonly see). Once Longhorn progressed to Vista, boot manager has developed more so that it is no longer backwards compatible.

EDIT: I see mention of ghost images -- not good...

Regards,
Galapo.

Could also try:

http://www.vnunet.com/vnunet/downloads/ … manager-se
http://kb.paragon-software.com/paragon/ … ct_id=3804

I can supply you with a BartPE plugin or WinBuilder script if you so desire.

Regards,
Galapo.

I'm not sure as I don't have that hardware to test.

But what I do know is that I've been testing for the next release of Driver Import PE and it works well for my SigmaTel audio device. Before there was manual steps necessary such as copying INI files to a particular path (different for different SigmaTel drivers, though) under %ProgramFiles%. Now it is just a one click install, either from offline host, driver INF, or DP .7z pack.

Regards,
Galapo.

Thanks for the report.

Sorry for the delay -- I've been on holidays and away from internet access. The latest BartPE plugin and WinBuilder scripts now contain an updated CreateMassStorageData.exe which should fix the issue (providing Overflow doesn't alter the location of MassStorage.inf again).

Also, I've updated the LiveXP mass storage driver script for the same issue in case a user supplies a newer BASE.

Regards,
Galapo.