Search options (Page 209 of 213)

you will have to cut and paste the contents into your post

use the code tags to keep it clean  [ code]  your pasted file contents here [ /code]

dont use spaces between the [ ] and you will get this

  your pasted file contents here

post your finisher log ? ? ?

It should take the better match even though its not first.

Nice job on the workaround too!

can we see your finisher log please?

The Goal is to support All Hardware for x86 5.x 32 bit OS's.

if you

then there must be a reason you "HAVE to install  new drivers on top of them "
(Just because they exist  does not require you to HAVE to update them)
(if somebody came out with an updated floppy disk driver I doubt i'd install it)
As I said because it's newer - does not mean - it's better.  there is this thing they call BUGs!

hey look here! new drivers! doesnt help you or us.

It might be better - if it is it will be added.  The only way we know if its better is if we see problems, or lack there of.
If New HWID's exist then it's guaranteed.

The goal is to have the best driverpacks, meaning the most compatable and reliable drivers.
Those may not necessarily be the newest,  but,  they just might be!
We need the research of users to prove new drivers. 
what are your HWID's and your issue - that is how we decide.
If there is no benefit, then a new driver is not needed?

(Your driver got tested and is ready for release isn't it?)

the winnt.sif must exist or you will fail

this file is modified by base and will need no attention from you.

make sure your DPs_base slipstream is the last step in your process!

Looks like it worked perfect.  What was the question????

i am not sure if there's no error either.

how much free space on C: ? 
I keep asking about space because the full DP set is almost 2 gig uncompressed.

Is D: a mapped network drive?
Does the destination folder contain a dptio file already? is it read only?
DPTI2O.SY_ is a native driver for XP we update. IF for some reason we didnt have the correct permissions to the drive it wouldn't get removed and replaced (IE it's readonly and we're not an admin)

It's probably better to add the driverpacks to a fresh source after a faild slipstream if you didn't.

Noone else has reported this and I was not able to reproduce it here either. try running base with the /debug switch. the log may be to large to post here you can email it to me if so.

I checked the inf and there are no errors or extra spaces that would cause this.

As I have been writing the code for BartPE I have learned a great deal about the workings of the Base.
Bâshrat the Sneaky is still the only one who knows all, and he may have things to add or correct here.  BUT...

The main two differences between M1 and M2 are compression method and availability to setup.

M1
Uses standard windows CAB compression and puts the driver files in the $OEM$\$1\ folder on the installation CD/DVD.
The $OEM$\$1\ folder is copied to the root folder of the drive windows will be installed on by windows Text-Mode setup.
- IE They are copied from the installation media to %SystemRoot%\D  (Usually C:\D\[selected pack contents here] )
The path to every driver folder is then added to WINNT.SIF [unnattended] section OemPnpDriversPath=
This is where you can tell Setup to search driver folders to find a better match than what's in the existing drivers.cab on the Windows CD. If it finds a better match it will install those instead.

cmdlines.txt sets the finisher to run based on user selection GUIRunOnce or RunOnceExe

Disadvantage: The current driverpacks folder structure is over 6000 characters long so only the first 4096 will be used by setup  
Advantage:     The drivers are available for the entire GUI portion of setup.

I find this personaly useful because I use VMWare and the VMWare sound card emulates a SoundBlaster 128 which is natively supported by windows XP. Useing  M2 The included XP driver will be loaded during setup instead of the one in the pack. The XP SB128 driver fails in VMWare (yellow exclamation point). The DriverPacks include the updated SB128 driver which works wonderfully but only if M1 is used. I use WPI with background music. If I use method two I get no sound when WPI runs and I must go into device manger and update the device manualy. Sometimes when I use M2 I will launch vmware tools installer previous to WPI when i set the runonce entries from txtsetup.cmd (it will not install and exit silently if not in a VMWare shell)

M2
Uses the awesome power of 7-Zip to achive near solid compression of the packs and copy them to a folder named OEM on the CD/DVD. PRESETUP.CMD is called from DOSNET.INF and used to decompress the drivers from the installation media to %SystemRoot%\D  (Usually C:\D\[selected pack contents here] ) then DevPath.exe is used to update the path windows searches to find drivers. (setup is not affected by the 4096 limit now) then GUIRunOnce or RunOnceexe is set with "%SystemDrive%\DPsFnshr.exe"

Both methods
when the first logon occurs the finisher will either;
    Keep The Driver (KTD) and then run DevPath.exe to update the path windows searches to find drivers
    or Delete the files

there is more but that should invite good questions

That solution was posted - October 4 2006?

i guess you mean your glad you finally found it.

method one uses cab compression and is about 500 meg on the disk it also uses an oempnppath statment to point to the drivers.
the path statment with the full set of packs exceeds the 4096 allowed path length and will not make all the drivers available to the install.
so method one is becomeing more and more obsolite as we add more drivers.
(ANSWER TO "A") it does still copy the files to the disk IF KTD is enabled. 
Advantage here is the drivers are available to setup earlier in the install and this might be helpful in very rare cases.

(ANSWER TO "B") Hardware Installation Wizard will scan a cd/dvd for drivers. and find and use the M1 drivers, but M2 drivers are 7-zippped and it won't see them at all.

Method two uses 7-zip compression and has a 300 meg footprint.
the files are extracted to the HDD first and then made avalable to Plug and play by the driverpack finisher.

try this out http://siginetsoftware.com/forum/showthread.php?t=151

Power packer by Signet (who is a good friend of the driverpacks) does exactly whst you want

HWID's available for the hardware?