Search options (Page 57 of 99)

I don't get this at all.
2007/05/30 update?
yet, it has same old files we have in the Pack?

edit.
I see.
for vista and X64 is newer, but we do not support that..

Oh
the reason all these files got triplicated, and that the old ones got added to new ones, was this.
the current drivers are good for all OSes.

the OLD drivers the newest had dropped were good for all OSes, and all these OLD files came from fresh downloads (the intel archved drivers) so the three OS have all available drivers and yes, one folder would support all three OS. (but, I can't do that. M1 would NOT work.) .
(The SP folder could also go, far as I know, but once again, method 1 stops me from doing this. )

hi

at the moment, the folder structure for INTEL will have to stay as it is.
I would delete the triplicated intel folders if I could do so without causing an error in method 1
(yes... they have exact same content right now.)

if somebody updates these, please do NOT toss away the OLD files, because the newer drivers have FEWER files, and support a LOT less hardware.
When you update, overwrite the INTEL files.

Hi

I looked at your archive, and must say the way you did that cannot work for txtmode.

If you could upload the complete driver from the CD to bobbyzorg (all files, you included only TWO..) I can properly compare.
The supermicro was in my 'to-do" folder.

Wow.. This guy works fast.

We'll need some details for a changelog.
( It cannot go to to release when we have no details )

Hi
a not so subtle hint about reading the tutorial in my signature is in order.

The tute in my sig is quite different then what we first had in the topic, as I added some worthwhile tidbits of information which can help avoid mistakes like this.

this got into the release.

With the catalog files.

erm... distribution share from DVD?

hmmm

fini.cmd proved to be a no good useless bit of experimental work.

I think that a true unified driver is not going to happen.
I do not have the magic in me, but the latest Nvidia could purportedly have us reduce the set by a few folders.

(note; I downloaded all that stuff because I wanted to look/compare what DriverPacks has with what that stuff has in it.)

Carpe_zoom
can you link to the driver?

Sieze the day. zoom thru it.

Hi

We have a problem with QSC.
one should, at the moment, ALWAYS use it.

However, when you replace a file with a modified file (a reduced pack), then you must first delete the QSC folder before you run Base.

a CRITICAL error can still happen if you modify CHIPSET (reduce it), and it can happen whether you use QSC or not.
A few folders were hardcoded in the method one slipstream module, and if you touch the affected folders, whammo, you get a CRIT.

Mass storage and Chipset are very small 7zips, and method 1 will uncab only the OS specific files, so you had better left these two packs alone. (until the time Base is recoded)

recommended action.
use mass chipset unaltered,
do whatever you want to whittle down other packs.
Repack. (make sure that when they expand, that you do not get wrong folder-structures)
delete QSC folder.
copy modified packs.

(one good tactic is to give the mod-packs a higher version number. If orig ends with 7072, rename to 7073.. Update checker will say where did you get that, but you know how that got to be so, so what...)

run Base.
use QSC.