[serialzs]

@all

I modified this from my old topic my drivers Inf files to drivers.cab?

Here is the new guide, a more EASY to USE...

Just read the GUIDE inside the ZIP file!
Hope all will like it...

If you're having any trouble I am willing to help...

NEW batch files and guide NOT UPDATE...
Click to Download Last Modified 9/11/2004

-=[serialzs]=-

im really sorry for the DRVZ.EXE... i dont know the rules of scanning hardware that tym... NOW Heres the new Guide try it...

This post has been edited by serialzs: 12 September 2004 - 11:34 AM

[swgreed]

I like that idea, if I understood it right...

You create a 7z-compressed exe, containing the drivers and compress them again with makecab, so XP can expand them during installation?

But what will happen here?
DetachedProgram="%SystemRoot%\system32\DRVZ.EXE"

How did you compress this (selfextracting?) file, so XP installs the content correctly?

[serialzs]

@swgreed

yes...
it is for the compressed files of your drivers...
it expand *.cab files or *.7z files...
i see many people here using the 7z compression to compress there files...
it is a great application...

@all

im sorry here is the folder structure....
just follow the instructions and im sure it will install your drivers unattended...

special thanks:
Pyron for the SetDevicePath.exe
big_gie for giving me an idea that 7zip application is a great software to use...

-=[serialzs]=-

Attached File(s)

•  folders.gif (9.5K)
  Number of downloads: 240

[swgreed]

I see....

So the folder structure is hardcoded into SetDevicePath.exe?

[gmx]

great guide thanx now all we got to do is add Bashrat the Sneaky's driver packs

[Pyron]

@swgreed:
No, nothing is hardcoded in SetDevicePath.exe. It just takes a directory as first parameter, scans its structure and adds all found directories to the DevicePath regkey. So you don't have to have a specific directory layout.

--
Pyron

[Bâshrat the Sneaky]

Hmmm... an alike guide is already included in Driver Pack LAN, see the Installation instructions.

BUT... yours is ALOT better! No need to enter those stupid OemPnPDriverPaths anymore!

No words for it... truly amazed

Can I add this to my DriverPacks? All credits will of course go to you!

(Now the OemPnPDriversPath issue is solved! )

[evilvoice]

VERY NICE!!! have been waiting for a way to bypass the oemdrivers thing since there is a limitation.

[Bâshrat the Sneaky]

Topic is pinned!

[Pyron]

I didn't realize that this was such a big problem...
I am doing it this way for a long time now (well, with my own setup.exe), since I came to the conclusion that uncompressed drivers take too much space on my CD.

--
Pyron

[evilvoice]

here is a question i didnt see an answer to, when cab/7z ing your drivers, should you compress the sound folder that contains all folder for your sound...

Sound\Creative\SBAWE32
Sound\Creative\Live

so forth and so on

or should you compress the creative folder, or compress the Live folder...I just dont know how the autoit script is going to do all this, so I ask questions, I guess I could get autoit and look, but since you are already doing this, I figured Id ask

[Bâshrat the Sneaky]

Pyron, on Aug 24 2004, 04:24 PM, said:

I didn't realize that this was such a big problem...
I am doing it this way for a long time now (well, with my own setup.exe), since I came to the conclusion that uncompressed drivers take too much space on my CD.

--
Pyron

True, but your method doesn't support archives (which save alot of space)

No offense! Your method is also very good (but slightly different purposes)

[Bâshrat the Sneaky]

evilvoice, on Aug 24 2004, 04:30 PM, said:

here is a question i didnt see an answer to, when cab/7z ing your drivers, should you compress the sound folder that contains all folder for your sound...

Sound\Creative\SBAWE32
Sound\Creative\Live

so forth and so on

or should you compress the creative folder, or compress the Live folder...I just dont know how the autoit script is going to do all this, so I ask questions, I guess I could get autoit and look, but since you are already doing this, I figured Id ask

pyron said:

@swgreed:
No, nothing is hardcoded in SetDevicePath.exe. It just takes a directory as first parameter, scans its structure and adds all found directories to the DevicePath regkey. So you don't have to have a specific directory layout.

[evilvoice]

well stupid me...ya know, I even read that statement, wow i feel REALLY dum now

[Bâshrat the Sneaky]

evilvoice, on Aug 24 2004, 04:37 PM, said:

well stupid me...ya know, I even read that statement, wow i feel REALLY dumb now

No need to feel dumb... nobody is perfect...

EDIT:

PM from evilvoice said:

the missing b was in relation to me feeling dumb lol ...I didnt wanna post this useless thing in there

Now Im teh one whose feelin dum

[Pyron]

@Bâshrat the Sneaky
You are right, but I modified my method for compressed drivers since, but didn't write about it here, so maybe you see the irony...
But it's good to see that my SetDevicePath.exe has its uses after all

--
Pyron

[serialzs]

@pyron

can you give me what environment have the presetup.cmd...
if we can execute this command in your presetup.cmd it much great...

-=[sereialzs]=-

[bonedaddy]

well I preset my video settings (takes place @ 34min mark) using this

in winnsif;

QUOTE
[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768
Vrefresh=70


and that doesn't happen and I get BSOD prior to app install.

I tried raid drivers (works with oempnp...) started install ok,

then BSOD. I tried one at a time, raid then video, BSOD, with either one.

nVidia signed drivers, also work from oempnp...

bonedaddy

[Pyron]

@serialzs:
I don't know anything specific, but you can test by yourself: As soon as the GUI-mode installation starts, press shift F10 and enter taskmgr. It will not work and give you an error message. Wait for a few seconds and try again, it will work eventually. So the environment is not fully operational at that point, but I cannot say in which way exactly.

BTW, I noticed you are using AutoIt v3, did you try v2? Because I am using v2, not a compiled script, but nevertheless v2 and it works in presetup.cmd.

--
Pyron

[Bilou_Gateux]

@serialzs

I would like to know what does exactly drvz.exe.
If it's an autoit script, could you make the code public (turn back the compiled exe to script code) we can alter it to best fit our needs (change the default folder name for drivers).