Sign in to follow this  
Followers 0
serialzs

my drivers Inf files to drivers.cab?

51 posts in this topic

@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

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.