1,176

(10 replies, posted in DriverPack WLAN)

And which ones are 'none'? wink

I've just counted, and there are 25 Linksys WLAN drivers included. So please tell me on what exact device this happened...

I already thought I had not seen such reports...

All I need at the moment are your hwids. And indeed, please post it in the correct forum: DriverPack Graphics.

benners wrote:

Well, tested and it works fine, drivers got copied and when I plugged my scanner in the drivers were loaded, thanks again Bashrat.

The 3 directory makes it better for me as I don't want all of the drivers in my packs copied over, I have an exe in my 3rd party pack that is copied to C:\D\A\1 and deletes all the ATI files and folders leaving only the exes, I had to do this because I always got BSOD due to the ATI2mtag.sys in the Graphics Pack A drivers. I tried adding the Radeon 8500 drivers to my pack but the the ones in Graphics Pack A always got selected, even Microsofts updated driver blue screened. I also had probs with the NVIDIA drivers for my Go5700 so this was a less hassle free way.

I can put any drivers for scanners and printers in the 3 dir and leave the rest in D. :-), saving space.

We can solve these issues. Did you report them in the past?

1,179

(11 replies, posted in Other)

Floppy wrote:

Thank's for your quick replies!!!

Iam now a DriverPack Donor!

Thanks for your big donation! Much appreciated! smile

1,180

(15 replies, posted in 3rd Party DriverPacks)

Hmmm in that case, please send me the setup.exe.

1,181

(11 replies, posted in Other)

http://driverpacks.net/DriverPacks/Driv … ed_devices

wink

I know the current site sucks. It's hard to find everything. That will be improved over the next few months wink

1,182

(9 replies, posted in Feature Requests)

If you want to, I'll create you a script to easily do this. But I won't include it in the DriverPack Sound B, as it is totally NOT related to its purpose: slipstreaming the DriverPacks. I don't want to add options that are completely out of the target of the DriverPack Sound B: I want to keep it simple. This is not meant as a complete solution for creating your installation disc.

1,183

(11 replies, posted in Other)

Floppy wrote:
Bâshrat the Sneaky wrote:

aha smile

But why would you need/want such a file?

Because; Sometimes people ask me;
"Wow,that must be a lot of driver's on that DVD, how many driver's exactly?"

And I want to answer! wink

haha big_smile You know what? Print the readme's of the DriverPacks... then you've got ALL directories, driver versions and of course, drivers. You can count them there, if you want to (or if you're extremely bored tongue). Although some include drivers within drivers, but that's only a few.

1,184

(9 replies, posted in Feature Requests)

RogueSpear wrote:

If you ever do something that requires your install CD, it's all on the hard drive and you aren't even asked for the CD.  It usually only happens when to try to add/remove windows components.

Aha ok. I translate that to: "very few people need this feature". But...

BigBrit wrote:

As you have the GUI interface, how about an option to copy the I386 folder to the \root or \windows (user option) and set a registry entry to point to that folder (if files are needed for drivers etc.)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SourcePath

... that is the reason why BigBrit wants it.

BigBrit, the drivers that are included in Windows XP are ALWAYS copied to the HDD by default. You don't have to do this trickery to accomplish that! wink Or am I missing your point?

1,185

(11 replies, posted in Other)

aha smile

But why would you need/want such a file?

1,186

(9 replies, posted in Feature Requests)

RogueSpear wrote:

I believe what he wants to do is copy the i386 folder to the hard disk and have it set as the install source.  One the scripts in my ScriptPack does this.

And the effect would be that ... ?

1,187

(15 replies, posted in 3rd Party DriverPacks)

I thought this driver was specific to your DVD RAM drive?

Nope. But I'll fix the automatical cleanup of that.

It's the same as for the OemPnpDriversPath entry: you don't put a semi-colon at the end of that either. It's not a terminator, but it's a separator! wink

The current Control Panel can be used, since it's no longer been updated anyway. The Catalyst Control Center will probably also be backwards compatible. That's not the issue wink It's just the driver.

It's SET. That means it's read from the settings file and SET in the program. It does not say it is CREATED. I'd be interested to see your DPsFnshr.ini though, since no KTD has been applied. Your value has tricked my filtering mechanism...

1,191

(9 replies, posted in Feature Requests)

'and saw the RyanVM integration'?

I've seen this before once, but can you remember me what the goal of copying the I386 dir was again?

ricktendo64 wrote:

Thank You Bâshrat the Sneaky

That was fast... yikes

You can see it when you can select your partition. You'll see what I mean wink You cannot overlook it (now you know what you're looking for at least).

@ricktendo64: check out my updated tutorial. Now you must use this directory structure:

D\3\X\...

instead of

D\X\...

Where D is the DriverPacks root directory, 3 the 3rd party DriverPacks root directory (NEW, to make KTD doable for 3pdps) and X the root directory of your 3rd party DriverPack.

If that doesn't work, you may also want to comment out the JMicron drivers. They've created a conflict in the past, so...

EDIT: also look WHICH driver is loaded. If you boot from a regular IDE controller, it will say 'atapi' for example. You should see 'iastrold', nothing else.

1,196

(11 replies, posted in Other)

What is your point? Don't forget that each manufacturer has MANY devices and therefore multiple (but less than the 'MANY') drivers! wink

LOL

Then there's only one thing left to do. Please send me that setup. You can upload it to the 3rd party DriverPacks FTP. Check the 'HOSTING' topic in the 3rd party DriverPacks forum for more info about that.

Try this: open your txtsetup.sif file, do a search for "SCSI.Load" and now find the line that references "iastor" (i.e. the newer driver, not the old one) and put a semi-colon in front of it. That will prevent this driver from loading. Now retry.

1,199

(12 replies, posted in DriverPack LAN)

Your sound drivers weren't installed. You did use DriverPack Sound A, right? I've never had any problems with nVidia's sound drivers, nor have they been updated the past 6 months.

But your ethernet driver IS installed:

PCI\VEN_10DE&DEV_00DF&SUBSYS_A5511297&REV_A2\3&13C0B0C5&0&28: NVIDIA Network Bus Enumerator

Just export the

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce

key BEFORE you reboot the system and you'll see if it's there or not. You've rebooted it already, I suppose?