Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Having Windows Keep The Drivers

- - - - -

  • This topic is locked This topic is locked
124 replies to this topic

#1
X-Savior

X-Savior

    Member

  • Member
  • PipPip
  • 124 posts
  • Joined 23-February 05
Hi there,

I have added the drivers to the Winnt.sif with all the directory's and also added the driver packs that way. I used NLite to add a bunch of the smaller stuff but they don't seem to be retained by Windows. Is there any way to add them so in case you make a hardware change the drivers will auto install? :blink:

Thanks! :D
EVGA 680I MB, Intel Core 2 Duo 6600 @ 3.5 Ghz, 2 x EVGA 7800 GTX (256 MB) PCI-E (SLI Configuration), Sound Blaster X-FI Music, 4 GB (4x 1024MB) OCZ PC-2 6400 Gold XTC Memory, 2 x Raptor 74 Gb RAID-0, 2 x Seagate 500 GB SATA (1TB RAID), Dell 24" Widescreen LCD Panel & Dell 22" Widescreen LCD Panel (Dual View), Pioneer DVD-RW, Zalman 9500-Cu CPU Cooler, Antec Sonata II Case.


How to remove advertisement from MSFN

#2
rendrag

rendrag

    grrrrrr

  • Member
  • PipPipPipPip
  • 687 posts
  • Joined 28-October 04
  • OS:Windows 7 x64
  • Country: Country Flag
are you talking about keeping the drivers present so incase you add a piece of hardware the driverpacks support it will auto install?

if that's the case, you wouldn't delete the folder that all your drivers are in, then if you do add a certain piece of supported hardware, when the add new hardware wizard comes up, just point to the folder that the drivers are located.

if you want it automated, the only way I know how is to integrate the drivers into the driver.cab i believe, however if someone else has an alternate method, obviously chime in.

ASUS M4A78T-E | AMD Phenom II X4 905e 2.5GHz | 4x 2GB A-Data DDR3 1600 RAM | Saphire Radeon HD 7950 | 256GB Crucial M4 SSD | 1TB Western Digital Black | 256GB Seagate Barracuda | Samsung DVD Burner SH-S222L | 22" Samsung 226BW LCD | Creative Gigaworks S700 5.1 speakers


#3
X-Savior

X-Savior

    Member

  • Member
  • PipPip
  • 124 posts
  • Joined 23-February 05
Hi,

Yea, I would like to get them in the Driver.cab :thumbup

I want the install fully automated. That way I can TRUELY have an upgraded Driver Database. :D

No, the question goes out.... HOW? :wacko:

I figure it would be like integrating SATA drivers. You need to make entry's into the TXTSETUP.SIF I believe. :blink:

Just not sure where to make the entry's.
EVGA 680I MB, Intel Core 2 Duo 6600 @ 3.5 Ghz, 2 x EVGA 7800 GTX (256 MB) PCI-E (SLI Configuration), Sound Blaster X-FI Music, 4 GB (4x 1024MB) OCZ PC-2 6400 Gold XTC Memory, 2 x Raptor 74 Gb RAID-0, 2 x Seagate 500 GB SATA (1TB RAID), Dell 24" Widescreen LCD Panel & Dell 22" Widescreen LCD Panel (Dual View), Pioneer DVD-RW, Zalman 9500-Cu CPU Cooler, Antec Sonata II Case.

#4
erik_demon

erik_demon

    Master Chief

  • Member
  • PipPip
  • 253 posts
  • Joined 22-August 04
I didn't try to add those files to driver.cab yet. You are right, there will be a problem with the txtsetup.sif

This line is used in txtsetup.sif
driver.cab   = 1,,,,,,_x,39,0,0

The problem is the "X"

the "X" tells setup to look-up this file in LAYOUT.INF

in this file the the orginal filesize is stored. This means that if you added files to the driver.cab, your filesize will be different. When this happens setup will give an error that the file is either modified or corrupt.

I see two solutions here:

1. Change the LAYOUT.INF (not recommended see link below)
2. change the "X" into something else (after reading Gosh's info, I think you can delete the "_X". I'm not sure though)

Maybe a little help from some experts here?? :P

txtsetup.sif info

Gosh explains txtsetup.sif

EDIT: Same problem with SP2.cab
sp2.cab      = 100,,,,,,_x,39,0,0

Posted Image

#5
RogueSpear

RogueSpear

    OS: SimplyMEPIS

  • MSFN Sponsor
  • 1,529 posts
  • Joined 18-September 04
Or you would need a batch method to add all of the appropriate lines into the LAYOUT.INF file. Certainly not a task for the weak. Ultimately a batch or script that would recursively go through all of the BTS DPs, adding the lines to the inf and making the new HUGE drivers.cab file.

#6
erik_demon

erik_demon

    Master Chief

  • Member
  • PipPip
  • 253 posts
  • Joined 22-August 04
@ RogueSpear

Thank you for your response.
I don't think that you have to add all the lines to LAYOUT.INF. This file is only Necessary if you want to use the "_x" in on of the lines.

Example: Bashrat's pack (method 2) uses SETUPORG.EXE Bashrat adds the following lines:

TXTSETUP.SIF
setupORG.exe= 1,,,,,,,2,0,0

DOSNET.INF (important if you install with WINNT.EXE or WINNT32.EXE)
d1,setuporg.exe

He doesn't add a line to LAYOUT.INF. But it works like a charm.

The line in TXTSETUP.SIF could have also been like this (correct me if I am wrong):

setupORG.exe= 1,,_x,,,,,2,0,0
Now setup looks for this line in LAYOUT.inf, and there will be an error message (since the line is not present.)

So I guesse that if you don't use the "_x" in the TXTSETUP.SIF file, you don't have to add all the lines to LAYOUT.INF. You do however need to add all the lines to TXTSETUP.SIF and DOSNET.INF (which is a hell of a job :P )

Ultimately a batch or script that would recursively go through all of the BTS DPs, adding the lines to the inf and making the new HUGE drivers.cab file.


Yes, I agree. This would result in the ultimate drivers slipstreaming method.
Posted Image

#7
RyanVM

RyanVM

    Like a big surly teddy bear.

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,661 posts
  • Joined 31-August 03
If you add them to driver.cab, you're almost certainly going to have to edit layout.inf. If you look at the driver INF files in i386, you'll notice that they basically use layout.inf as their [SourceDisksFiles] section. Unfortunately, layout.inf is digitally signed and, unless you hack syssetup.dll, setup will throw up a signature verification error very early into the GUI portion.
RyanVM MSFN Files | RyanVM Forums
Please do not link directly to files on my site or modify/redistribute them without getting my permission first. Link to the above URL instead.
Current Update Pack Release: 2.2.2
(Released April 28, 2008)

BTW, 90% of what I say is kidding around. Don't take things so personally ;)

#8
erik_demon

erik_demon

    Master Chief

  • Member
  • PipPip
  • 253 posts
  • Joined 22-August 04
@RyanVM

Ok, I didn't know that, thnx.

Maybe we don't want to add the drivers to driver.cab

We do however want to do this:

are you talking about keeping the drivers present so incase you add a piece of hardware the driverpacks support it will auto install?


Now I found another interesting file called DRVINDEX.INF. this is some info I found about this file:

A new device requires corresponding driver files in order to work. Setup reads the Drvindex.inf file to find entries for the device. If an entry exists, Setup searches the following paths:

systemroot\Driver Cache\Platform\Driver.cab 
systemroot\Driver Cache\Platform 
The original Windows XP Professional installation source, such as a network share or a local CD-ROM drive. The Windows XP Professional source location is stored in the registry entry SourcePath in the subkey HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup.
If the required files do not exist in any of the preceding locations, or if references are not located in the Drvindex.inf file, Setup prompts the user to supply the required files.

Click here to visit the site

When we take a look to this file. We see 3 important area's

[Version]
signature="$Windows NT$"
CabFiles=SP2,driver


[driver]
1394vdbg.sys
2gmgsmt.sf2
;alot of drivers :P 

[SP2]
1394bus.sys
4mmdat.sys
;again a lot of drivers :P 

[Cabs]
driver=driver.cab
SP2=SP2.cab

Would it be possible to modify this file like this:

[Version]
signature="$Windows NT$"
CabFiles=SP2,driver,BTS

[driver]
1394vdbg.sys
2gmgsmt.sf2
;alot of drivers :P 

[SP2]
1394bus.sys
4mmdat.sys
;again a lot of drivers :P 

[BTS]
;our new drivers

[Cabs]
driver=driver.cab
SP2=SP2.cab
BTS=BTS.cab

Would this work??

EDIT: Maybe a stupid question, but where can you see if a file (like layout.inf) is digitally signed :blushing:
Posted Image

#9
X-Savior

X-Savior

    Member

  • Member
  • PipPip
  • 124 posts
  • Joined 23-February 05
Wow.... :blink:

I Didn't think it was going to be this difficult to figure out.

Thanks everyone pitching to figure this out. I agree with Erik. Is it possible to create your own CAB and just have Windows reference it prior to asking for drivers. You would think this system should be modular to allow future expansions and additions. :)

I am tempted to try the above method if someone else thinks this might possibly work. :rolleyes:

I might try playing around with DRVINDEX.INF on my latest DVD with a USB Linksys LAN card. I know Windows does not include it and when I plug it in AFTER OS install it does not recognise it. This will provide definitive proof the integration works. :thumbup

Anyone else have further info or experience on the matter?
EVGA 680I MB, Intel Core 2 Duo 6600 @ 3.5 Ghz, 2 x EVGA 7800 GTX (256 MB) PCI-E (SLI Configuration), Sound Blaster X-FI Music, 4 GB (4x 1024MB) OCZ PC-2 6400 Gold XTC Memory, 2 x Raptor 74 Gb RAID-0, 2 x Seagate 500 GB SATA (1TB RAID), Dell 24" Widescreen LCD Panel & Dell 22" Widescreen LCD Panel (Dual View), Pioneer DVD-RW, Zalman 9500-Cu CPU Cooler, Antec Sonata II Case.

#10
ZileXa

ZileXa

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 767 posts
  • Joined 27-May 04
Perhaps it is a lot easier than you think! check this topic:
http://www.msfn.org/...showtopic=35869
Driver Compressor Tool

#11
erik_demon

erik_demon

    Master Chief

  • Member
  • PipPip
  • 253 posts
  • Joined 22-August 04
@ZileXa

Yes, this program by hp38guser is indeed an amazing peace of art. It has proven to be very usefull (I believe Bashrat already uses this method in his pack (method1)). Altough I like the program, it will not help here.

Our goal is to find a way to let windows autodetect drivers after the installation (when you plug and play a new device which isn't recognised by windows at this moment.)

@X-Savior

Don't forgot to add the LAN-card files to TXTSETUP.SIF and DOSNET.INF. If you don't windows setup will give you a copy error. I am very curiouse to see if this works. Good luck!

@All

What happens when you uninstall drivers that are used in DRVINDEX.INF? If you reboot, will windows auto detect and autoinstall them again? this could be a problem when you want to install newer drivers.
Posted Image

#12
djbe

djbe

    Member

  • Member
  • PipPip
  • 169 posts
  • Joined 20-October 04

@ZileXa

Yes, this program by hp38guser is indeed an amazing peace of art. It has proven to be very usefull (I believe Bashrat already uses this method in his pack (method1)). Altough I like the program, it will not help here.


Do you mean that part when it compresses all drivers (cabbing them all)? nope, that's being done through a quite simple batch program (I wrote it :whistle: ) :P.
AMD 3500+ (Winchester) @ 2.64Ghz :: 4 x 512 MB PC3200 @ 2-8-3-3-2
Asus GeForce 6800GT 256MB :: Asus A8N-SLI Motherboard
Maxtor 160GB x 2 Raid 0 :: DVD Writer + DVD Reader

#13
Bâshrat the Sneaky

Bâshrat the Sneaky

    aka Wim Leers

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,214 posts
  • Joined 29-October 03
  • OS:none specified
  • Country: Country Flag
Yep, erik_demon, djbe wrote that.

But djbe: I wasn't sure if it would work, and hp38guser confirmed that cabbed files are also recognised by Windows!

#14
X-Savior

X-Savior

    Member

  • Member
  • PipPip
  • 124 posts
  • Joined 23-February 05
Ok,

Well, I have been very bust lately :whistle: (So Have we all!)

I should have a chance in the next few days to experiment and see what the end result is. :)
EVGA 680I MB, Intel Core 2 Duo 6600 @ 3.5 Ghz, 2 x EVGA 7800 GTX (256 MB) PCI-E (SLI Configuration), Sound Blaster X-FI Music, 4 GB (4x 1024MB) OCZ PC-2 6400 Gold XTC Memory, 2 x Raptor 74 Gb RAID-0, 2 x Seagate 500 GB SATA (1TB RAID), Dell 24" Widescreen LCD Panel & Dell 22" Widescreen LCD Panel (Dual View), Pioneer DVD-RW, Zalman 9500-Cu CPU Cooler, Antec Sonata II Case.

#15
X-Savior

X-Savior

    Member

  • Member
  • PipPip
  • 124 posts
  • Joined 23-February 05
Ok, I have been playing around. I compressed and added the single file USB100M.SYS (USB100M.SY_) to TXTSETUP.SIF along side other device drivers and also added 2 lines to DOSNET.INF

Sorry, at a different machine so I can't paste exactly what I added but there was a spot where I did it under D1 (Disc 1) near the top and then also

D1,USB100M.SYS

down a little further as well.

In the TXTSETUP.SIF I used directory 4 (\System32\Drivers)

No Errors during Install. After the install I looked and the driver was there, uncompressed. Everything looked fine but when I plugged in the USB LAN Card it did not find the driver when I searched for it. :thumbup

When you add a device, where does windows search FIRST to see if there is a match? This might be the key to adding them. I assume there must be a reference somewhere else to the drivers. :no:

I Did not add anything to DRVINDEX.INF though. I will try adding to it as well and see if it makes any difference. :)
EVGA 680I MB, Intel Core 2 Duo 6600 @ 3.5 Ghz, 2 x EVGA 7800 GTX (256 MB) PCI-E (SLI Configuration), Sound Blaster X-FI Music, 4 GB (4x 1024MB) OCZ PC-2 6400 Gold XTC Memory, 2 x Raptor 74 Gb RAID-0, 2 x Seagate 500 GB SATA (1TB RAID), Dell 24" Widescreen LCD Panel & Dell 22" Widescreen LCD Panel (Dual View), Pioneer DVD-RW, Zalman 9500-Cu CPU Cooler, Antec Sonata II Case.

#16
Bâshrat the Sneaky

Bâshrat the Sneaky

    aka Wim Leers

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,214 posts
  • Joined 29-October 03
  • OS:none specified
  • Country: Country Flag
You guys really want to do it the hard way... But of course it's the better way. As soon as anyone can outline it DETAILED, I'll add it to the DriverPacks as an option.

As much as I'm interested, I don't have the time to figure it out.

#17
erik_demon

erik_demon

    Master Chief

  • Member
  • PipPip
  • 253 posts
  • Joined 22-August 04
@X-Savior

Nice job, this is a really good start.

The key here is indeed DRVINDEX.INF
You don't have to Re-install you OS to test this.

The file DRVINDEX.INF can be found in your %systemroot%\inf folder

I read somewhere that the file was not digitily signed (I thought RyanVM mentioned that somewhere) so it should be easy to modify the file.

I don't have much time this week, but next week I will test the following:

- I will create a CAB file called DP_Erik.cab and put it in my systemroot\Driver Cache\i386 folder.

- I will add/modify the following lines in the DRVINDEX.INF file:
[Version]
signature="$Windows NT$"
CabFiles=SP2,driver,DP_Erik

[DP_Erik]
;driver files (I think I will test in on my monitor drivers)

[Cabs]
driver=driver.cab
SP2=SP2.cab
DP_Erik=DP_Erik.cab

- Uninstall my monitor drivers

- Reboot, and hope for the best :P

I will report back somewhere next week.

@Bâshrat:

When we got this working and well, either X-Savior or myself will write a detailed "how-to". It would be very cool to contribute something to your Driverpacks B) .

EDIT:
@X-Savior

In the TXTSETUP.SIF I used directory 4 (\System32\Drivers)


DRVINDEX.INF looks for it's drivers in the following folder:
%systemroot%\Driver Cache\i386

that is number: 39
Posted Image

#18
RogueSpear

RogueSpear

    OS: SimplyMEPIS

  • MSFN Sponsor
  • 1,529 posts
  • Joined 18-September 04
Ok I'm following all of this without too much difficulties because I looked into myself a number of months ago. At that time I decided it was simply too much for me to tackle. What I remember though was wondering about layout.inf, which I believe IS digitally signed.

If true integration can be achieved without breaking (editing) layout.inf, then what is the true purpose of this file? It almost seems to be redudant to me.

Second. Does the driver index file map out the drivers contained within drivers.cab? I know that when you slipstream SP2 over Gold, you end up with drivers.cab and sp2.cab (unless you merge with nLite or manually). Both of these contain drivers as I understand it. Soooo.. can we make say DP_MS.cab, DP_LAN.cab, etc? Because without any compression, the collection of BTS DriverPacks is enormous to just keep around the hard drive. Especially when I have my unattendeds copy over the i386 directory and install basic apps, a 30 gig laptop drive starts to look pretty small pretty fast.

#19
RyanVM

RyanVM

    Like a big surly teddy bear.

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,661 posts
  • Joined 31-August 03
I know that the driver INFs in i386 basically use layout.inf as their [SourceDisksFiles] section, which is why adding files to driver.cab is extraordinarily difficult.
RyanVM MSFN Files | RyanVM Forums
Please do not link directly to files on my site or modify/redistribute them without getting my permission first. Link to the above URL instead.
Current Update Pack Release: 2.2.2
(Released April 28, 2008)

BTW, 90% of what I say is kidding around. Don't take things so personally ;)

#20
X-Savior

X-Savior

    Member

  • Member
  • PipPip
  • 124 posts
  • Joined 23-February 05
Ok, I GOT IT!

:thumbup

I tested all afternoon and made some headway but the results will surprise most of you I think.


Here is what I have done... :D

I had 2 Files I was working with...
USB100M.SYS
USB100M.INF

All you need is the *.SYS too be in the "%Systemroot%\Windows\Driver Cache" folder
and the *.INF in the "%Systemroot%\Windows\INF".

THATS IT!

So here is what I did,

1) I compressed the USB100M.SYS into the I386 folder on the DVD.
2) Edited the DOSNET.INF and added the following...

[FLOPPYFILES.1]
D1,USB100M.SYS

[FILES]
D1,USB100M.SYS

3) Next I added to the TXTSETUP.SIF

241 = "DRIVER CACHE"

USB100M.SYS = 1,,,,,,,241,0,0

4) Lastly on the Windows DVD I placed the USB100M.INF into the
"$OEM$\$$\INF " Folder.

Done.

After I re-installed the OS I plugged in the USB Card, it detected it, asked if I wanted to look online, said no... Then Selected Search and it found it and installed it.

This is not QUITE as perfect as I would like. I want it to just do it without asking anything but none the less it works just fine. :unsure:

Something I noticed is that after the first time it installs it created a USB100M.PNF
Not sure what that is about. :wacko:
EVGA 680I MB, Intel Core 2 Duo 6600 @ 3.5 Ghz, 2 x EVGA 7800 GTX (256 MB) PCI-E (SLI Configuration), Sound Blaster X-FI Music, 4 GB (4x 1024MB) OCZ PC-2 6400 Gold XTC Memory, 2 x Raptor 74 Gb RAID-0, 2 x Seagate 500 GB SATA (1TB RAID), Dell 24" Widescreen LCD Panel & Dell 22" Widescreen LCD Panel (Dual View), Pioneer DVD-RW, Zalman 9500-Cu CPU Cooler, Antec Sonata II Case.

#21
RogueSpear

RogueSpear

    OS: SimplyMEPIS

  • MSFN Sponsor
  • 1,529 posts
  • Joined 18-September 04
Well for what it's worth, when I do a fresh install of XP SP2 for a client and then later deploy the unit and plug in their MS Optical mouse (USB), I get that same dialog box about the drivers. And I KNOW that these are built in drivers. All I do is click on search and away it goes. Annoying at best for sure.

If you look in your i386 folder you should see a ton of pnf files compressed. Each inf file needs a corresponding pnf. I forget what it stands for at the moment, but I remember researching it in regards to RIS installations.

#22
X-Savior

X-Savior

    Member

  • Member
  • PipPip
  • 124 posts
  • Joined 23-February 05
Yea, I saw what it was but I forget too. So, with the method I outlined you should be able to include ANY drivers. I am most concerned with Peripheral's and stuff like that.

I would still like to persue creating an additional cab... something like Extra.cab and integrate it. I think Windows checks the cabs before asking to search for the drivers I think. :}

Now, can you use Winrar to create a Cab file or are they SPECIAL Microsoft files. I know WinRAR can look into them an extract the files. Do I just create a new file and start adding drivers to it and then reference it like Drivers.cab and on XP Pro I think there is SP2.cab and something else. I am taking what I have learned about my MCE 2005 DVD and making a XP Pro DVD re-done from the ground up. That way I will be ready to go for 64-Bit when it arrives... YAAAAAA!!!! :thumbup

Anyone have any suggestions to improve on my methods? :)
EVGA 680I MB, Intel Core 2 Duo 6600 @ 3.5 Ghz, 2 x EVGA 7800 GTX (256 MB) PCI-E (SLI Configuration), Sound Blaster X-FI Music, 4 GB (4x 1024MB) OCZ PC-2 6400 Gold XTC Memory, 2 x Raptor 74 Gb RAID-0, 2 x Seagate 500 GB SATA (1TB RAID), Dell 24" Widescreen LCD Panel & Dell 22" Widescreen LCD Panel (Dual View), Pioneer DVD-RW, Zalman 9500-Cu CPU Cooler, Antec Sonata II Case.

#23
erik_demon

erik_demon

    Master Chief

  • Member
  • PipPip
  • 253 posts
  • Joined 22-August 04
Some bits and peaces of information about .PNF files

Most confusion issues happen because of the way Win32 retains device driver information. When it first detects a Plug & Play device, it uses the matching INF file to build a PNF database file.

Site 1

The PNF file gets created by the system when the inf file is used to
install the device. You don't need to create them.


Site 2

EDIT:

@X-Savior

There is a special program to creat .CAB files

It is Cabarc.exe

You can download it here

You can use this link to learn all about the Cabarc commands

EDIT 2:
cabarc -r -p N  DP-Erik.cab *

This command makes DP-Erik.cab in with:

-r = Used to recurse into subdirectories when adding files
-p= Used to preserve path names (so that you can use sub dirs)
Posted Image

#24
erik_demon

erik_demon

    Master Chief

  • Member
  • PipPip
  • 253 posts
  • Joined 22-August 04
Okay, I now created a DP-Erik.cab file

But it has a lot of subfolders inside.

A few line from the DRVINDEX.INF file

[driver]
1394vdbg.sys
2gmgsmt.sf2
3145pcl.gpd
3155pcl.gpd
3165pcl.gpd
31x5hc01.cnt
31x5hc01.hlp
31x5hs01.cnt

As we take a look at the files above, we can see that these files are on the root of the driver.cab file

Now I want to know if I can also use subfolder in the DRVINDEX.INF file

Is this possible:
[DP-Erik]
DP\000_chipset\intel_inf_drivers\815.cat
DP\000_chipset\intel_inf_drivers\815.inf
DP\000_chipset\Via\VIAHyperion4in1455v\WinXP\viaagp1.cat
DP\003_display\samsung710T\SM710T.inf

See the image below for an overview of my DP-Erik.cab

Attached Files

  • Attached File  DP.JPG   58.91KB   56 downloads

Posted Image

#25
Bâshrat the Sneaky

Bâshrat the Sneaky

    aka Wim Leers

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,214 posts
  • Joined 29-October 03
  • OS:none specified
  • Country: Country Flag
That was exactly the main problem... it's impossible to put them all in one folder because of many identical filenames...


I wonder if it's possible to do it a way similar to this:

[Directories]
d4 = DP\C
d5 = DP\G
d6 = DP\L
d7 = DP\M
d8 = DP\S
d9 = DP\W

EDIT:

and then of course:
[BTS_DriverPacks
d4,landriver.sys,
d5,atidriver.sys
d5,nvidiadriver.sys

But even THEN we'd have LOTS of identical filenames... and I strongly doubt we could ever do it that way (or anything similar)...

I think we need the knowledge of an insider to get this done properly... (and without needing weeks/months to find it out)

Edited by Bâshrat the Sneaky, 31 March 2005 - 06:36 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users