Search options (Page 31 of 58)

So, you could do an MD5 now, eh?

I will add your pack to the list.
Please supply the missing info if you can!

I added your pack to the big sticky.
Please always also post updates in that very thread so the first post of it can be updated accordingly.

Also, always post the MD5 sum whenever you release something!
So far, I will add it myself based on what I have downloaded hoping it did not get corrupted, but the ideal solution is if the checksum is supplied by the creator.

I was talking from a home user's POV, but yeah

No, you won't even have to press anything at all.
Just make sure the floppy is in the drive, and it will be picked upautomatically (could be a problem if you are installing from floppies but I seriously doubt anyone is - although you can request a floppy edition of XP at MS!).

In any case, if you are already using the DriverPacks there simply should not be any need for this procedure at all!
If a driver is missing in DPMS, your best solution is to simply request it to have it added.
No more FDDs, no more worries, and it serves us all to have the driver in!

No, not at all!
Of course it does RAIDs, that is the point of TM, to install drivers for these controllers.
Apart from SATA, what other need would there be for TM?

Are you sure about the filename?

I have never heared of this one and a quick search also does not reveal any results on my HDD.

There is, however, a file called svchost.exe, however, that is an internal Windows component and not related to the DriverPacks.

If you haven't noticed already, you can find it in our sigs
It's also part of the BASE, anyhow, so you can take it from there as well.

Err, which one?
Don't remember having created one lately

Have you slipstreamed an Update Pack, such as RyanVM?
Or, if not, have you manually added the HDA Hotfix (KB888111) by chance?
Please also post DPs_BASE.log and DPsFnshr.log!

Yes, save the nice audio capabilities (24bit/96kHz recording/playback), it doesn't really offer anything over AC'97 (7.1 works with that, too).
The predecessor also behaves much nicer in terms of easy installability and driver support (no KB888111 and all that stuff *sigh*).

The only reason we're seeing it pushed so much nowadays is because of the "better" copy protection by alowing secured (as in non-recordable) audio stream playback.

The customer, once again, does not profit from this, but the big media companies do!

That's because X2500 is not an official ATi designation.
They only have 2400 and 2600 with nothing inbetween.
This is typical for OEMs to relabel the cards with a similar name to the current manufacturer's line suggesting a performance that it ususally doesn't give.

My bet is that it probabaly is an X1700 with the same features including core/mem clock as well as shaders.
I'd say go ahead and keep the entry for the X1700 and let's see how that will work for this "X2500".

Better requested once too much than not at all, IMO

Anyway, yes, you better use your resources to make us aware of less prominent driver updates if you come across them

As I wrote in the other thread, my personal experience with the 7.7s on two different machines was far from bad.
While the article does not show any performance gains (which is fine, IMO, you don't need a gain with every release), I cannot share their negativity about the driver set.

I have experienced much worse in the past.
A reason why I stuck to the 5.13 (yes, one of the rare occasions where ATi released more than a dozen a year) for quite a long time, I think until 6.6 or so.

Also, it's not only about game performance, I'm sure you will all agree.

You also have to take a look at the changelog:

For any non-hardcore gamer (and that's what I consider the majority of the DriverPacks as - pure gamers perfer "modded" drivers anyway, or so I heared...), these fixes are probabaly more important than a 3% gain in some game.

Ususally, XP driver should work.
2003 really is a XP64 kernel in 32bit mode so the difference is probabaly even less than from 2000 to XP (in which case many drivers are also cross-compatible).

Just give it a try and see if they work.

You should not use Vista drivers, at least not without doing a backup first.
Vista's driver architechture is quite different and while XP drivers for some less critical (eg. not kernel) drivers may work, I doubt the opposite is true, too...