Search options (Page 15 of 58)

Firstly, this is quite contrary to our main policy, to provide drivers for as much HW as possible.
The idea is to create a Universal Installation Disc, not one limited to a specific system or HW.

If you only want to include drivers for HW that's in your system, I'd recommend the opposite approach as stripping all the drivers you do not need will take considerably more efford than just including the ones you do need.
You could either use nLite to add specific drivers (just extract them and point in to the INF dir).
Or, you could create your own custom pack containing just the drivers you needed.
Of course, you'd have to keep those up-to-date yourself, then.

Utilities such as "Driver Genius" (not freeware, though checking for new drivers works even on trial) can help with that.
If you just want to create a pack of your current drivers, you can use Siginet's Driver Grabber. You can then pack them all in one archive for use with BASE.

As to a selection screen in BASE, I think this is quite a difficult act to achive.
It would need to list every single driver contained in the DriverPacks. Those would also need to be displayed in a manner that makes it easy to navigate (no use in having a loooong list of thousands of drivers in the BASE that totally messed up the GUI).
Also, you'd need a database file for these drivers that constantly gets updated with each release as some are added, others removed or renamed.
This would also mean that your proposed INI file becomes worthless after each update and you'd have to redo the selection each time.

I do not code BASE, but I'm sure this would be a major effort, all while the intended use is contrary to our main policy as described above.
May take a lot of work to convince Jeff to take on this task, IMO

Yeah, no problem with your "hotfix", was just about to slipstream drivers and thought, I checked by here before

So no harm done on my side!

Well, well...

Mysteriously enough, the non-deletion of the D folder in root is now fixed without em doing anything, however, a folder called "BT61010" remains and something tells me this is directly related to your pack...

In fact, I checked the folder structure and you missed inlcluding the D folder in the archive layout.
Please add it as otherwise the finisher will not work on the pack and neither will KTD if one uses it.
Second concern is (still) the program files folder.
It only contains some INIs and I doubt the driver needs these files, and if it did, it wouldn't find them anyway, as they aren't being copied to the system's program files folder anyway.
So either incorporate them into the main dir of your pack or delete them altogether.

I cannot test the pack myself any further as I lack any BT devices on this system so I can just hope you tested it and it worked for you

So, where do you run into problems?
I take it extracting the driver files did work properly?

Problem with this pack is the paths are totally messed up.
It contains some "Documents & Settings/Desktop" lines within the ususal D\BT\ kind of structure that simply asks for trouble (space chars within the path etc).
Possibly more, that's all I could catch when fake setup ran (was coincidentially using the member-provider supposedly faster 7z-exe, otherwise the CMD window would not have shown...

Please correct that and repack, there's a guide how to properly do your own 3rd party DriverPack around here

As long as it's not two left ones...

(Funny how bidexterity literally means two right hands...)

Heh, not that I'd shed them a tear, but honestly, this is the second rumor of a chipset maker quitting business (after nVidia) that you post about...
Not saying that I ming keeping informed but I prefer solid news over vague rumors any day

Besides, it would be nice if you could link to your source and use quote tags, I think that's something Fair Use would or should require.

That's honourable but inevitable.
We all do it all the time and it usually only takes about three posts to get it done.

Unfortunately not, or we'd all use and recommend it.
Guess, another forum limitation...

(other than that, it's fine)

You can of course chose to upload the files elsewhere and link to them

PS: Please make use of the accepted standard of posting below a quote, not above.
Also, only use foll-quotes if needed.
Thanks!

Yeah, emailing will not make that error vanish.
It's not so much an error, btw, but more a forum limitation.

You can try splitting up the file to smaller pieces and posting each in a new post to make it fit.
Just use a proper editor (Notepad++ or Notepad 2) and keep the character count below 64000 [^=64KB].

In case you were referring to me, my name's not Hans, despite being German

Martin will do fine, but basically everyone calls me Helmi IRL, anyway

If you did not refer to me (though that leaves me clueless as to who this Hans guy is...), I sincerely beg your pardon!

Yeah, never said it did, just thought this was a excellent example to prove it once again!

Nice to see how it made WHQL even with these glaring bugs...!

It's a farce, I'm tellin' you!