Search options (Page 17 of 213)

the entries are removed from the registry before you are presented the desktop. The the DriverPacks Finisher does this automatically.

you would need to check to see if they are there before the computer reboots to the GUI.
(or disable the finisher)

There isn't a reason that this should fail for you except that the BASE log indicates that your source is not totally clean.

Please try again with a "Clean" source. (Read - fresh copy of original hologramed Microsoft disc)
Additionally most of us slipstream SP3 into our install... but that is not mandatory.

Jeff

Thanks cdob,

that is the same suggestion you made years ago for the same issue we were having with empty card readers in our PreSetup.cmd file that we use for automating the NT5 (XP,  2K and 2K3) installs. I guess mr_smartepants forgot about that.

Of course we use a simpler implementation.

SET TAGFILE=\OEM

FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO DIR %%i: && IF EXIST "%%i:%TAGFILE%" SET CDDRIVE=%%i:& GOTO DPsFound

:DPsFound

The IF EXIST command fails / crashes if an empty card reader is encountered, the DIR command does not.

Thanks for the reminder... and drat you beat me to it .

i wrote a program a couple years ago to pull the hwids out of the infs i spent several weeks on it and never did get 100% success on listing the HWIDs. Some were always missing because of differences in the way the INF files were layed out. especially where variables were used.

the current version of that is used by mr_smartepants when he publishes a new release. It populates the "included drivers" field on the download pages. Kickarse also has a tool for that that is published here on our forum.

you are not allowed to delete duplicate HWIDS... that definitely will fail.

I think you are mistaking a copy for what is actually extraction from the archives.

Method 2 or M2 as we call it extracts the 7zip archives to c:\d that does take a minute.
    (however since i am doing an unattended install
     i don't care if it takes two minutes or four minutes
     since i am not actually there... i am doing something else... 
     (UNATTENDED) .)

Method 1 or M1 as we refer to it is pre-extracted so there is no copy or extraction.
it would simply run straight from the thumb drive.
- Test with an M1 source and see how long it takes...

When we headed down this road before we had many obsticals. not the least of which was exceeding the maximum number of elements in an array. (it would silently truncate input). a couple of other projects have set out on this same mission. They also have space here at DriverPacks.net. What we ended up doing in the short term was to split the stream in the packs themselves. In this way you can extract the inf files as a single stream. (our solid archive is actually two solid archives one with infs and one with all the other stuff). this makes gettitng the infs very fast . the rest is very buggy. your theory is solid, and if our OS was not windows would have easily succeeded years ago.  Again a good idea tried many times by several projects. . .

I think with the onset of cheap fast thumb storage its just easier to run an M1 (pre extracted) SAD off the thumb.

try a different version of mass storage... either older or the release candidate that is floating around in the mass storage forum. *you are here

Remember mass storage text mode is hard coded. no PnP no WHQL, Nothin nada zippo...

whatever HWID you specify for a driver will force that driver to be used. (obviously only if that hwid exists in the system)
Hard coded. you could assign a sound card driver and it would attempt to load it .

very simple in theory. the main point is you only need to pick one that works long enough to partition and transfer files. then the PnP driver will replace it on the reboot.

BartPE and UBCD4Win and other PE based tools are based on windows textmode setup which is more properly referred to as the Preinstallation Environment or simply P.E.

i know it really confused me too when cdob and hilander999 dragged me into the mire. Best advice i can give you is forget everything you know about windows... start there

"THERE CAN BE ONLY ONE"
couldn't have said it any better.

If there are any duplicate HWIDs in there chaos is the result... especially if it conflicts with a native driver

Native drivers require you to use "Replace" tags
you can* only replace a native driver if it is fully backward compliant.

* (read 'should', because you can do that, just not the preferred choice)

of course http://www.adaptivepc.com/DP_MassStorag … -32_901.7z

can we have a link to the known good working driver?

That may help us to help you, we can compare the working driver with which driver is enabled in the DriverPack MassStorage.

Best source is a clean sp2 retail or volume hologram-ed disc. i have been successful with sp3 but not recommended.
Definitely do NOT use a modified source, this will result in fails at different points for an assortment of reasons.

the smoke and the mirrors .
Build it and take a peek at the plugin folders .

Wow lot's to cover...

A Good answer to the question...

well that is not perfect,

you already said you knew there were obstacles to building with an OEM disc.
It is always best to build BartPE with a clean Retail (or VL) Hologramed XP SP2 source.
I have had almost no issues with using SP3 source... but SP2 is recommended.
I trust that you addressed the known issues with your source...

the second two errors should be correctable.

R U building with ubcd4win?
It is unlikely that a UBCD4Win build would have either of those issues logged.
I believe post processing would have corrected both of them before image creation.
I do recommend that you do use UBCD4Win if you are not using it.
MUCH easier for a beginner . It is specifically written to make it "mistake and omission resilient".

An easier way might be to just use an older dpms version that has that older driver... than to edit the current one. But either way it works.

easier still...
your machine should have a restore partition with a factory image on it...
you should be able to launch the restore process from your BartPE disk. (it's just like safemode)
you might also find that you can restore this factory image from the boot menu options.
(lots of manufacturers do this. Check their support site for factory restore or Recovery... you might also try OOBE)

ubcd4win has HWPnP included by default...

The nice thing about UBCD4Win is, it is all done already, it's in there and the bugs all ironed out... .
perfect for testing DriverPacks, if it works on UBCD4Win but not PE then they are missing a plugin (prolly HWPnP) .

no you don't need desk.cpl,
again because UBCD4Win is complete and already includes a tool for setting the screen resolution .