• 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

my drivers Inf files to drivers.cab?

51 posts in this topic

@alexey

1st of all im sorrie im busy this last few days...

@ your first post:

examples: :)

inside c:\nvidia

drive.exe

must have a *.cab

inside c:\nvidia\files

drive.sys

drive.inf

must have another *.cab

nvdia.cab ---------> files in c:\nvidia compressed

nvfiles.CAB ---------> files in c:\nvidia\files compressed

you have to make a new *.cab for the folders then add command to your

TXTSETUP.SIF

[WinntDirectories]

45 = Temp -------> is for %systemroot%\TEMP

add this:

999 = "temp\files" -------> is for %systemroot%\TEMP\FILES

note: always remember dont overwrite the other numbers

i think you can use Nos. 200 - 999 for assigning where to extract.

[sourceDisksFiles]

; Drivers for my PC

nvidia.cab = 100

drive.exe = 100,,,,,,,45,0,0

nvfile.cab = 100

drive.sys = 100,,,,,,,999,0,0

you must organize your files to extract without a problem

@ 2nd post

NVIDIA.CAB = 100

100 -->is the folder location in CD, 100 means i386\ folder

i dont test it in w2k, WinXP only but you can try it and you can add a post what you did to install...

-=[serialzs]=-

0

Share this post


Link to post
Share on other sites

I did exactly the same as you adviced but it doesn't work!

Maybe I'm stupid but I got the message during process the txtsetup.sif by install script: - error in 3rd string in SIF file - zero equal or wrong argument in 3rd string (I inserted driver's strings at the beginning of [sourceDisksFiles]). I tried to add direct direction what the .CAB is in [sourceDisksNames.x86] - I got error again, than I tried to copy .CAB file to hard disk via dosnet.inf - I got other error and I tired to repeat it.

I started from simple package (folders didn't included) and I was fail. But I believe if you did it, I should make it as well. I suspect user error. Do you want to see changed files for having look where error is? I know it is not simple and unpleasant to search for error made by someone but I can't find it by myself...

Sorry that I'm disturbing you...

:)

0

Share this post


Link to post
Share on other sites

where does this go?

[Cabs]
driver=driver.cab
SP1=SP1.cab
mydrivers=mydrive.cab

in the textsetup.sif or the drvindex.inf?

0

Share this post


Link to post
Share on other sites

@alexey

i want to help you out!!! :rolleyes:

PLEASE post here your TXTSETUP.SIF and DRVINDEX.INF

and the names of drivers that you want to extract...

also include the name of CAB files...

what OS are you using???

i want to know the bugs in here too... :)

0

Share this post


Link to post
Share on other sites

@Serialz

Thank you in advance.

Here they are (files).

I'm using Windoes 200 Pro SP4 Russian localized OEM.

For more simplicity lets consider NVIDIA WinXP/W2k 56.64 driver.

I cut distributive a bit (language files and IIS files) and got the set wich I packed using iexpress (SED file included). Please check integrity of idea.

During installation attemp it stops on first string, contains 100 value. Maybe W2k doesn't understand it...

DRVINDEX.INF

0

Share this post


Link to post
Share on other sites

@alexey

i see it right now!! :D

it is not working because the TXTSETUP.SIF have different VALUES...

change the 100 to 1

let see if it works!!! :rolleyes:

NOTE: edit the WINNT.SIF

[unattended]

OemPnPDriversPath="Windows\TEMP"

to install your drivers unattended!!! :)

-=[serialzs]=-

0

Share this post


Link to post
Share on other sites

Right. It seems to me that I can now install W2k at least :))

The reason of fail is definitely code that means "copy from CD \I386 to...". For your OS it is "100" and "1" for mine W2k. Thus here is solution. Unfortunately I can't check it right now but I'll do it as soon as I can and revert to you on this board. Also it is not possible to check driver installation using WMWare Workstation, I have to do it on real system.

Also there is difference in our winnt.sif - I mentioned in it that place for system folder location is winnt and you are using windows folder.

Thank you VERY MUCH!!!

Your idea should work for installation of some apps f.i. JRE by the same way - you can make cab file, include it into list of cab files, make direction where to copy it during installation and run it using RunOnceEx, huh?

Thank you once again and promiser to report about result,

Alexey

0

Share this post


Link to post
Share on other sites

@Serialzs

I have doubt again regarding PnPOemDriverPath.

Dear Serialzs, please chech your winnt.sif and replay what did you use for parameter OemPreimstall - YES or NO???

I suppose that if I'll use YES Windows will search for drivers directory $OEM$.

Am I right?

0

Share this post


Link to post
Share on other sites
@Serialzs

what did you use for parameter OemPreimstall - YES or NO???

I suppose that if I'll use YES Windows will search for drivers directory $OEM$.

Am I right?

@alexey

your spelling is wrong :rolleyes:

yup it must be YES :)

OemPreinstall=YES

-=[serialzs]=-

0

Share this post


Link to post
Share on other sites

I want to know

I add some unsigned driver to the xp cd

Could it be setup automatically??

0

Share this post


Link to post
Share on other sites

I want to know

I add some unsigned driver to the xp cd

Could it be setup automatically??

0

Share this post


Link to post
Share on other sites

@weihuisheng

i think it will setup automatically...

to know if it work go to DEVICE MANAGER...

then Right click the DEVICE then press Update Driver...

then search the *.inf in unsigned driver...

if it install it will setup automatically...

and if not tell me what's happening... :)

0

Share this post


Link to post
Share on other sites

thanks ,@serialzs

but I think you dno't understand what I mean

I want to know

Will it be installed automatically while I install my xp??

I check Ignore in my xp drivers install selection

0

Share this post


Link to post
Share on other sites

yes it will if you follow the instruction...

-=[serialzs]=-

0

Share this post


Link to post
Share on other sites
@all

for those who want to compressed their driver and install it unattended...

(alternative method for $OEM$\$1\Drivers folder)

1. make a *.cab files:

      type > iexpress in RUN

      select > Create compressed files only

      add > Add all your Driver Files

      browse > where you want to put your *.cab files

      select > Save SED file

COPY the *.CAB file to i386 folder

now You have a compressed Driver Files.

Example i have mydriver.cab

2.  inside i386 folder edit DRVINDEX.INF(dont delete anything)

add the bold text:

[Version]
signature="$Windows NT$"
CabFiles=SP1,driver,[B]mydrivers[/B]

add all the files in the mydriver.cab like this:

*to make it easy open SED file with Notepad then COPY all the files you ADDED

Example:

FILE0="sm56hlpr.exe"
FILE1="sm56co.dll"
FILE2="domestic.chm"
FILE3="sm56.reg"
FILE4="IntelH51.cat"
FILE5="sm56nt5.cat"
FILE6="IntelH51.inf"
FILE7="Nehcd.inf"
FILE8="smserial.inf"
FILE9="IntelH51.sys"
FILE10="nehcd.sys"
FILE11="nusb2hub.sys"
FILE12="nusbd.sys"
FILE13="SmSerial.sys"

if you paste it in DRVINDEX.INF delete the FILE##="" and it should be like this:

[mydrivers]
sm56hlpr.exe
sm56co.dll
domestic.chm
sm56.reg
IntelH51.cat
sm56nt5.cat
IntelH51.inf
Nehcd.inf
smserial.inf
IntelH51.sys
nehcd.sys
nusb2hub.sys
nusbd.sys
SmSerial.sys

add the bold text

[Cabs]

driver=driver.cab

SP1=SP1.cab

mydrivers=mydrive.cab

3.  edit TXTSETUP.SIF

[SourceDisksFiles]
; Drivers for my PC
mydrive.cab = 100
sm56hlpr.exe = 100,,,,,,,45,0,0
sm56co.dll = 100,,,,,,,45,0,0
domestic.chm = 100,,,,,,,45,0,0
sm56.reg = 100,,,,,,,45,0,0
IntelH51.cat = 100,,,,,,,45,0,0
sm56nt5.cat = 100,,,,,,,45,0,0
IntelH51.inf = 100,,,,,,,45,0,0
Nehcd.inf = 100,,,,,,,45,0,0
smserial.inf = 100,,,,,,,45,0,0
IntelH51.sys = 100,,,,,,,45,0,0
nehcd.sys = 100,,,,,,,45,0,0
nusb2hub.sys = 100,,,,,,,45,0,0
nusbd.sys = 100,,,,,,,45,0,0
SmSerial.sys = 100,,,,,,,45,0,0

45 means where you want to extract your files...

You can change 45 = windows\temp folder

4.  edit WINNT.SIF

[Unattended]
OemPnPDriversPath="WINDOWS\TEMP"

and thats all it works great to me hope to others too...

-=[serialzs]=-

do you think that method works also for installing sata/raid drivers and bypass the f6 pressing + the disk you need for the driver to install? i could imagine it would work when you add the hardware ids to txtsetup.sif ([HardwareIdsDatabase]), but im not sure.

0

Share this post


Link to post
Share on other sites

@Tribble

sorrie i dont have sata/raid devices, i dont know if it works...

tell me how sata/raid drivers installs??? so that i can help you... :)

-=[serialzs]=-

0

Share this post


Link to post
Share on other sites

Not to downplay what has occured in this thred, but i think serialz wanted to achive something different. all that has occured here is to change the source path for the oem pnp drivers.. Still requires unattended. Do it without unattended and i would both be impressed and excited. I have done it for ide controllers. But the driver can only be access during install of windows. If you add hardware after windows boots the first time, it doesnt see the added drivers correctly so you have to point it to the driver files.

0

Share this post


Link to post
Share on other sites

The method described should work fine, although i think OemPnPDriversPath should be removed. The only reason you would need OemPnPDriversPath is to avoid duplicate files. What i would suggest is once your make your mydriver.cab, remove any duplicate files from driver.cab or sp1.cab. Also, i would think you would want any .inf's copied to the inf folder (11) during install so setup can see them. I don't think setup would extract an inf to install drivers.

See what happens is at the 32 min mark of setup, setup does the PNP detection and enumeration. Setup also installs the infs from syssetup under [DeviceInfsToInstall]. Once setup finds some hardware, it tries to find the right inf in the windows\inf folder. I would think the inf would need to be there rather than in the .cab file. Once setup finds the right inf it reads it and extracts the needed files from the .cab you made.

As far as the 1 and 100, 1=original media, 100=updated file (service pack). With slipstreamed media this shouldn't matter whether you use a 1 or 100.

-gosh

0

Share this post


Link to post
Share on other sites

@gosh

I think I've just noticed a mistake in your last post :)

The method described should work fine, although i think OemPnPDriversPath should be removed. The only reason you would need OemPnPDriversPath is to avoid duplicate files. What i would suggest is once your make your mydriver.cab, remove any duplicate files from driver.cab or sp1.cab. Also, i would think you would want any .inf's copied to the inf folder (11) during install so setup can see them. I don't think setup would extract an inf to install drivers.

Shouldn't that (11) actually be (20)

10 = system32\spool\drivers
11 = system32\spool\drivers\w32x86\3
12 = system32\spool\prtprocs
13 = system32\spool\prtprocs\w32x86
14 = system32\wins
15 = system32\dhcp
16 = repair
17 = system32\drivers\etc
18 = system32\spool\drivers\w32x86
19 = system32\drivers\disdn
20 = inf
21 = Help
22 = Fonts

I'm a Newbie, so please feel free to correct me if I'm wrong :rolleyes:

0

Share this post


Link to post
Share on other sites

@ Serialzs

I have a major problem getting cab(ified) drivers to install.

I have done exactly as you have described earlier except that I placed the drivers in "\windows\driver cache\i386" and offcourse have my WINNT.SIF/OemPnPDriversPath point to OemPnPDriversPath="WINDOWS\Driver Cache\i386"

Now to the installation:

WinXP sliped SP2 installs fine and identifies the modem (the device I'm trying to install) since the modem.inf file is copied to "\windows\inf" dir during installation.

The problem arraises when windows tries to copy the files designated by the modem.inf file, windows cant find them and prompts me for a location of a modem.sys file.

Am I doing something wrong? (Stupid question, offcorse I am, since it does not work)

What am I doing wrong, annyone? :blink:

0

Share this post


Link to post
Share on other sites

@Mattias

Sorry i am busy... I reprogramming it for the new and easier way to do it...

i think your folder destination is not in the *.inf file of your driver thats why it is not working great...

just try it again if it didn't work... wait for MY new tips about COMPRESSION of DRIVERS... i think i will finish this soon... :lol:

-=[serialzs]=-

0

Share this post


Link to post
Share on other sites

Hi ;

How can i backup my drivers using WMI or any think else ?

can you help me please ?

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.