• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Sign in to follow this  
Followers 0
serialzs

Guide For Compressed Drivers Unattended Install

215 posts in this topic

@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... :thumbup

Just read the GUIDE inside the ZIP file!

Hope all will like it... :w00t:

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...

Edited by serialzs
0

Share this post


Link to post
Share on other sites

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?

0

Share this post


Link to post
Share on other sites

@swgreed

yes... :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]=-

post-88-1093346401_thumb.png

0

Share this post


Link to post
Share on other sites

I see....

So the folder structure is hardcoded into SetDevicePath.exe?

0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites

@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

0

Share this post


Link to post
Share on other sites

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

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

No words for it... truly amazed :w00t:

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

(Now the OemPnPDriversPath issue is solved! :))

0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites

I didn't realize that this was such a big problem... :blink:

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

0

Share this post


Link to post
Share on other sites

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 :)

0

Share this post


Link to post
Share on other sites
I didn't realize that this was such a big problem... :blink:

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)

0

Share this post


Link to post
Share on other sites
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 :)

@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.

;)

0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites
well stupid me...ya know, I even read that statement, wow i feel REALLY dumb now

:D

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

EDIT:

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

:lol::D

0

Share this post


Link to post
Share on other sites

@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 :D

--

Pyron

0

Share this post


Link to post
Share on other sites

@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]=-

0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites

@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

0

Share this post


Link to post
Share on other sites

@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).

0

Share this post


Link to post
Share on other sites

@Bilou_Gateux

it exactly do is

search the CDROM with *.cab files or *.7z files... (%cdrom%\$OEM$\DRIVERZ) :)

then extract it to your SYSTEMDRIVE... (C:\DRIVERZ)

i really do it with Z for those who are using DRIVERS in there SYSTEMDRIVE...

it will not install if it OVERWRITE the EXISTING FILEs...

and with the help of pyron's SETDEVICEPATH.EXE... it reg. the folders in registry...

that's all... :thumbup

-=[serialzs]=-

0

Share this post


Link to post
Share on other sites

i need help :P i dont understand why its not installing the drivers :S

in c:\driverz\video_vmware (im using vmware drivers 2 test with since its on vmware machine) i have 1 file inside that folder called "INFCACHE.1" is that normal? no drivers r being installed tho

0

Share this post


Link to post
Share on other sites

It should be normal and it means that Windows sees that directory during installation, ie the DevicePath variable is correctly set. I just searched around for it a bit and found one in every singe directory beneath my drivers path, never noticed before however.

But then again I don't know why your drivers are not installed. I have similar problems in vmware, in particular with the mouse driver. On a real world system all neccessary drivers get installed, so I don't care too much.

--

Pyron

0

Share this post


Link to post
Share on other sites

hi this is my chipset driver Structure and i want to know that when archiving this folder do i have to delete the folders that aren t related to winXP such agp95 ....

or could i keep them without having problems ??

Thanx in advance

post-88-1093439396_thumb.jpg

0

Share this post


Link to post
Share on other sites
hi this is my chipset driver Structure and i want to know that when archiving this folder do i have to delete the folders that aren t related to winXP such agp95 ....

or could i keep them without having problems ??

Thanx in advance

You CAN keep them without having trouble, but why would you? Just remove the folders of which you are a 100 percent sure you can remove them. (Like AGP95, etc.)

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.