[tnx]

Well after a few failed attemts I am no further to solving this.
What ever i put in the TXTSETUP my .inf file always ends up in Sytem32,

After an install I look in Windows\inf and I selected Battey.inf. on the install cd this file lives in I386 and its TXTSETUP entry is battery.inf 100,,,,,,,20,0,0 and fter the install completes thats where it lives.

When I write the same for my file it does not work neither does 1980,,,,,,,20,0,0

I have my source folder set as 1980.

Getting realy stumped.

[tnx]

Hi...

Update...

Well been messing for the last couple of days and still coming up short. Buttttttt. Well the last install I have had just done got me thinking. I Told the drivers to update. I had to manually browse to find my .inf file.....I stopped...

I manually copies the .inf into Windows\INF. Then I went back to update the drivers,this time I had to browse to find the containing folder but I did notice it was trying to find them in System32. I stopped..

I manually copied the rest of the files into Sytem32. I then went back to update the drivers. I did not have to browse for any files,the PC found them all by it's self. This tells me thats where they should live. I now think the .inf file should be copied from the cd and installed into Windows\inf and the rest of the files should be copied into System32.
I should forget all about my "New Drivers" destination folder. It is clearly not working and concentrate on installing all my files to where i just spoke about.

One way of installing the .inf file could be $OEM$\$$\INF.

Well I already install to Sytem32 my OEMINFO.ini and OEMLOGO.bmp via $OEM$\$$\System32 so would it be just has easy to sling my driver files,uncompressed into the same folder....

Only one way to test this out i suppose......

Gunna do it right now. Will report back.

[tnx]

That was interesting.

It sort of worked. The PC picked up my .inf and started to install the drivers but I stll had to manually browse for them..

obviously it was never going to be so easy but a fun little experiment none the less.

Been reading all sorts of posts here there and every where,with some conflicting ideas too.
I am thinking i am nearly there. I am playing all the right notes but not in the right order....Yet ! ( Little reference to Morcambe and Wise there. )

[Geej]

Just a thought...

You might need to change the path of [SourceDisksNames] within the .inf so that it knows where to find the files...
Just take a look what is the current string. Here is one site for a general description of SourceDisksNames.

To be frank, I don't really know much how to go about it but it is good you are trying to see what works. Keep us posted.

An idea comes to my mind. How about use 3rd party program to save, then restore later.
I come to know of this program from Seven forum because someone mention it there. DriverBackup! 2.1
It requires .Net 2 framework to run
Support commandline restore operation. (maybe this is what you want)
Personally, I have not tested it so can't say if it works as stated.

This post has been edited by Geej: 30 July 2012 - 09:51 PM

[tnx]

Geej, on 30 July 2012 - 09:50 PM, said:

Just a thought...

You might need to change the path of [SourceDisksNames] within the .inf so that it knows where to find the files...
Just take a look what is the current string. Here is one site for a general description of SourceDisksNames.

To be frank, I don't really know much how to go about it but it is good you are trying to see what works. Keep us posted.

Thanks for the link there. Not seen that one before,logged it. my list of sites is getting really long now. In there somwhere is the answer...

Gunna definatly have a look inside my .inf file. this is summet new so hopefully helpful..

Cheers...

[tnx]

yesssssssss... Summet interesting in my .inf file. I have not looked at it till now.

It has this

Quote

[SourceDisksFiles]
Rtenic.sys = 1
Rtenicxp.sys = 1
Rtenic64.sys = 1
RTNicProp32.dll = 1
RTNicProp64.dll = 1
RTNUninst32.dll = 1
RTNUninst64.dll = 1

So if i am thinking right if i chanege the values and make them point to my particular folder when the PC picks up the .inf inside of Windows\INF then i should not have to browse.....

Sounds very interesting.....Need to read more i think regarding this....

My next test was going to be a bit simpler and something I have not yet tried.

Making my new folders. having the driver files copied there at install. Not worry about the .inf being in Windows\INF but adding to WINNT.sif

OemPnpDriversPath="Windows\NuDrvrs|Lan" ( not sure if the inverted commas are needed )

This is like a mixture of the simple $OEM$\$1\Drivers and the more complicated TXTSETUP editing and new folder srtucture...if that makes sence.....It sort of does in my head but to bee honest there is that much whirling round in there i could be mixing myself right up...

mmmmmmmmmmmm tnx thinks......

[tomasz86]

I'm looking at it right now. Integrating drivers in a way that they will be automatically detected and installed is more complicated Just give me some time. I hope I'll be able to accomplish it today.

[tnx]

tomasz86, on 31 July 2012 - 05:04 AM, said:

I'm looking at it right now. Integrating drivers in a way that they will be automatically detected and installed is more complicated Just give me some time. I hope I'll be able to accomplish it today.

Ohhhhhhhhhhhhhhh...Sounds great.

Time hey.....take all the time you need.

Foor me this has become one of those problems which does not really need getting over. What i mean is nLite does a pretty good job,but summet about it bugs me. Then installing the drivers after an install is no big deal really either..Butttttttttttttttttt,welllllllllllllll..

It's got to the stage where I NEED to do it or i wont be happy with my self,if you know what I mean and to get extra help,well thats fantastic....

[tnx]

Geej, on 30 July 2012 - 09:50 PM, said:

Just a thought...

You might need to change the path of [SourceDisksNames] within the .inf so that it knows where to find the files...
Just take a look what is the current string. Here is one site for a general description of SourceDisksNames.

To be frank, I don't really know much how to go about it but it is good you are trying to see what works. Keep us posted.

been thinking a lot about what you put in your post. I have spent all this time trawling the net looking for info. Found a lot of stuff but I dont really undersatnd it.....

What i am just about to do now is install a fresh XP OS onto my test drive but one I added the drivers to using nLite. What i am hoping to find is where all the files are located. Is the driver.inf actually in Windows\INF and if so as nLite altered the driver.inf file at all
What i will do is copy all the files that nLite installed and compare them using "Beyhond Compare 3" This will show all,any differences in the files after install.

But here is what is in my driver.inf file

Quote

[SourceDisksNames]
1=%DISKNAME%,,,

[SourceDisksFiles]
Rtenic.sys = 1
Rtenicxp.sys = 1
Rtenic64.sys = 1
RTNicProp32.dll = 1
RTNicProp64.dll = 1
RTNUninst32.dll = 1
RTNUninst64.dll = 1

At first I was confusing my self thinking the "= 1" was a reference to the TXTSETUP [WinntDirectories] 1 = "\" ( what ever "\" means )

But is is obvious to me now.....So it gets me to thinking that my driver.inf file

[SourceDisksNames]
1=%SystemRoot%\NuDrvs\LAN ----- This is my folder which is created at install and all the driver files are copied to......

This then should point the .inf file right to all the other driver files enabling them to be installed.......I have to test this. To me it does sound like it could be the missing piece in my puzzle...

That is,if I have %SystemRoot%\NuDrvs\LAN correct being my foler which is in Windows\NuDrvs|LAN

Time will only tell..

[tnx]

Well not learnt much after install XP with intergrated LAN drivers using nLite.
It makes a folder structure similar to mine and does NOT install the driver.inf file into Windows|INF.

All I found out is it made a file called

Quote

INFCACHE.1

and I have no idea what this does.

Off to read up on this

[tnx]

Right,another test is on the way.

What I have done.

Using my set up which copies all the drivers onto the system into Windows\NuDrvs\LAN. Edited DOSNET + edited TXTSETUP + my WINNT file I have added to $OEM$\$$\INF and inside here I have placed my driver.inf file.

The driver.inf file will be copied into Windows\INF nicely and I have edited the file,

Quote

[SourceDisksNames]
1=%systemroot%\NuDrvs\LAN,,,

[SourceDisksFiles]
Rtenic.sys = 1
Rtenicxp.sys = 1
Rtenic64.sys = 1
RTNicProp32.dll = 1
RTNicProp64.dll = 1
RTNUninst32.dll = 1
RTNUninst64.dll = 1

I have no idea if this is right or wrong. i have found nothing detailing this on the web at all. Which probebly inidicates it's wrong. Like all good experiments it comes down to trial and error....

What I ahve just thought about. Before i go to install I will remove the compressed driver.inf from the install source. Two of the same file might cause problems...

[tnx]

Well test done...

Result.....

ohhhhhhhhhhhhhhhhhhhhhhhh soooooooooooooo close.

The install picked up the .inf file. It brought up "Found New Hardware" wizzard and I had to browse to my folder....C:\Windows\NuDrvs\lan

I had in my driver.inf

Quote

[SourceDisksNames]
1=%systemroot%\NuDrvs\LAN,,,

I had wrote it wrong...

Going to try again and ammend it to

Quote

[SourceDisksNames]
1=%systemroot%\NuDrvs\lan,,,

If that fails i will try

Quote

[SourceDisksNames]
1=C:\Windows\NuDrvs\lan,,,

[cdob]

Compare http://www.msfn.org/...to-txtsetupsif/

Drivers are copied to hard disk at a new directory
And HIVESFT.INF DevicePath is adjusted to this new directory.

Be aware: default txtsetup.sif used 8.3 file´names.
Longer names are expanded. Read txtsetup.sif for examples.

Try folder $OEM$\$1\Drivers\ and adjust DevicePath.

[tnx]

cdob, on 31 July 2012 - 03:11 PM, said:

Compare http://www.msfn.org/...to-txtsetupsif/

Drivers are copied to hard disk at a new directory
And HIVESFT.INF DevicePath is adjusted to this new directory.

Be aware: default txtsetup.sif used 8.3 file´names.
Longer names are expanded. Read txtsetup.sif for examples.

Try folder $OEM$\$1\Drivers\ and adjust DevicePath.

that link is interesting. I have actually seen it before but this time around i understand more of this process. The

Quote

c) HIVESFT.INF
I. open c:\XPCD\content\I386\HIVESFT.INF and search for %SYSTEMROOT%\inf. the line should be
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","DevicePath",0x00020002,"%SYSTEMROOT%\inf"
II. add the custom driver path to this setting. this is the same path we used in 5.a.II. (%SYSTEMROOT%\nvidia\raid\). the line should look like
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","DevicePath",0x00020002,"%SYSTEMROOT%\inf;%SYSTEMROOT%\nvidia\raid"
III. save and close the file

is very interesting indeed... That could hold the key.....

The $OEM$\$1\Drivers........ i know of this way and i have tested it a couple of times and it works. I just dont want my drivers sat on the root of C: drive....... I know it's a small thing,but i am too far into this just to give up...

I have copying my files from sourc to destination locked down now. using etited DOSNET and TXTSETUP......I understand what changes to make and file system to use...

As for my latest tests.....Nope......Very close !!

With my edited driver.inf I still get the found new hardware wizzard popping up. It tells me that the files are in C:\Windows\NuDrvs\lan and that is exactly where they are but I still have to browse for them...

So it's not the missing piece..

I think my next test will be to forget about my driver.inf being copied into Windows\INF. Going to look at the "HIVESFT.INF" and add my folder path to that which contains ALL my driver files...

My destination folder path is "C:\Windows\NuDrvs\lan" So Looking at the "HIVESFT.inf" I should be looking at

Quote

HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","DevicePath",0x00020002,"%SYSTEMROOT%\inf;%SYSTEMROOT%\NuDrvs\lan"

Definatly summet new to try....So I will....

Cheers for this new info "cdob"

[Geej]

Your [SourceDisksNames] does not conform to it's syntax.
Try something like this

[SourceDisksNames]
1="NuDrvs LAN Files from current dir of this .inf sub dir",,,NuDrvs\LAN

and put your source file in C:\windows\inf\NuDrvs\LAN instead of C:\windows\NuDrvs\LAN
I think it will not prompt to browse for file.
Unfortunately I couldn't get the inf to pick up file from C:\windows\NuDrvs\LAN. It has to be from the '"installation root", which is where the inf resides.
Unless your driver.inf is located in C:\windows dir...

[tnx]

Geej, on 01 August 2012 - 04:25 AM, said:

Your [SourceDisksNames] does not conform to it's syntax.
Try something like this

[SourceDisksNames]
1="NuDrvs LAN Files from current dir of this .inf sub dir",,,NuDrvs\LAN

and put your source file in C:\windows\inf\NuDrvs\LAN instead of C:\windows\NuDrvs\LAN
I think it will not prompt to browse for file.
Unfortunately I couldn't get the inf to pick up file from C:\windows\NuDrvs\LAN. It has to be from the '"installation root", which is where the inf resides.
Unless your driver.inf is located in C:\windows dir...

Thanks for that. very interesting.......

I left things last night,too much buzzing round my head....

Picking it up again today And I am just about to test with the ammended HIVESFT file......This points to Windows\inf and my folders.....

Cheers for the extra info.......

[tnx]

DONE IT...

DONE IT ...

I have done it......

OHhhhhhhhhhhhhhhhhhhhhhhhhh yipeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee...

Just gunna write it up now........

[tnx]

Right this is what i have done.

I'm sure you all know the simple things,obtaining the OS files,downloading the drivers,compressing the drivers. that sort of thing. But if you do need more info,just ask...

I compressed all my driver files and copied them to the source disc,

i386\NuDrvs\lan

I have amended four files

DOSNET.inf
TXTSETUP.sif
HIVESFT.inf
WINNT.sif

Quote

DOSNET.inf

[Directories]
d11 = "\i386\MyDrvs\lan"

[OptionalSrcDirs]
MyDrvs

[Files];LAN Drivers
d11,netrtle.cat
d11,netrtle.inf
d11,rtenic64.sys
d11,rtenic.sys
d11,rtenicxp.sys
d11,rtnicprop32.dll
d11,rtnicprop64.dll
d11,rtnuninst32.dll
d11,rtnuninst64.dll

Quote

TXTSETUP.sif

[SourceDisksNames]
500 = %cdname%,%cdtagfilei%,,"\i386\MyDrvs\lan"

[WinntDirectories]
600 = NuDrvs\lan

[SourceDisksFiles];LAN Drivers
netrtle.cat = 500,,,,,,,600,0,0
Netrtle.inf = 500,,,,,,,600,0,0
Rtenic.sys = 500,,,,,,,600,0,0
Rtenic64.sys = 500,,,,,,,600,0,0
Rtenicxp.sys = 500,,,,,,,600,0,0
RtNicprop32.DLL = 500,,,,,,,600,0,0
RtNicprop64.DLL = 500,,,,,,,600,0,0
RTNUninst32.dll = 500,,,,,,,600,0,0
RTNUninst64.dll = 500,,,,,,,600,0,0

Quote

HIVESFT.inf

HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","DevicePath",0x00020002,"%SYSTEMROOT%\inf;%SYSTEMROOT%\NuDrvs\lan"

Quote

WINNT.sif

DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore

Amend all these files and copy them back into the source disk i386 folder.

This worked a treat.....And I can not express how happy this had made me feel....

I want to thank each person who has helped me with this project. Each person has held a piece of the puzzle and now they all fit perfectly.....

Well what I have to do now is ttry with more than one driver abd see what happens...

Thanks evry body...



Any questions just ask....

This post has been edited by tnx: 01 August 2012 - 08:06 AM

[tomasz86]

Good job

I've almost managed to do it too but using a different approach. I'm trying to add the drivers using exactly the same way as Micro$oft used. It's actually very simple but I still need to go through the last step.

[tnx]

tomasz86, on 01 August 2012 - 08:21 AM, said:

Good job

I've almost managed to do it too but using a different approach. I'm trying to add the drivers using exactly the same way as Micro$oft used. It's actually very simple but I still need to go through the last step.

Sounds interesting....

Do tell please...