Search options (Page 33 of 58)

How about instead of telling us the file name you rather provide a link to the file (manufacturer homepage, or ,if not possible, upload it yourself somehwere)?
That really helps us indefinately more than having to google for the filename or similar.
I can tell you that most likely the outcome of that would be far less than optimal...

That entirely depends on the type of CR used, I would say
The one from my desktop system simply needs a USB mass storage driver which Windows provides by default.
The one for my laptop, however, also because it is combined with the smartcard reader, requires special drivers indeed.

Well, that greatly depends on the kind of GIF you use.
If unoptimized, they can indeed take up quite a lot of space, however, you can slim them down a lot if you're doing it properly.
Unless you were to put an entire movie sequence into GIF, it can be quite efficient.
Especially banners; if the only changing element is text (the slogan), the only information you'd need to save to each frame is the difference to the previous one.
With text, that isn't so much as you can gather, hence the resulting file size is merely that of the banner graphic (which you would have anyway) plus that little text info.

Anyway, when the time comes, I'm more than willing to create and trying to slim down such an animation.
Wouldn't be the first one I'm doing

Got the path to the file so we can quickly verify?

Also, did you check whether it is referenced by any INF file?

On my PC?
Thanks, but I will do that on my own

That entirely depends on the tools you use, I would think

If you do not want to use CABs for the (added by BASE) drivers, then simply use Method 2.

If you do want to use CABbed drivers, Method 1 is for you (but carries some restrictions on the amount of drivers possible to add).

That said, you can edit your posts for clarity instead of creating a new one and not helping with confusion much

Well, call it pure magic or whatever, but I just happened to stumble across this yesterday (and immediately had to think of your problem, too ):

http://www.ryanvm.net/forum/viewtopic.php?t=4068

Actually, I'm planning on using this myself the next time I come across a HDA system because I had problems with that in the past.

As you are in fact using the RVM Update Pack (I would have posted this regardless), I would definately give this a try - apparently it is a well-known problem (i.e. not isolated to you); and this would also mean it's probabaly really not us to blame but rather Ryan (not to diss his otherwise outstanding work, heh Probabaly MS to blame anyway).

HTH and hoping for you to report back (seeing as I cannot test this myself current for the lack of any affected systems).

Just a shot in the dark, but...

Maybe try enabling QSC for a chance.
In the past, some users had problems with it disabled for w/e reason and it worked when they used it...

I see, you mean you are searching inside the file rather than for the file.
My mistake.

Have you tried adding a wildcard (*) at the end of VMS (--> VMS*)?
Generally, search should not just search for the lone phrase you entered, but who knows.
Maybe another bug to be reported to Redmond

Definately, and I'm not doubting that, however, I had similar issues with the sort-of German version of Ryan's Pack, Sereby's (which, unfortunately is on halt now thanks to some "nice" letters from MS, desperately searching for a German-based (no translation for Ryan's available as I can see) Update Pack, btw!).

What I am trying to say is, this one is not in our hands to fix, I guess, but rather the Update Pack creator's.
(provided the DriverPack Sound B did as it told and not re-applied KB888111)

Better take it over to Ryan's forum, IMO, or at least make them aware of this thread.

Apart from what Erik said, I fail to see how any "tweak" (w/e that means in the end) would help laptop users apart from simply modding device support into the INFs.

We also prefer original, manufacturer-supplied drivers in about all cases (unless they are known to be bugged and the only way around to this is using 3rd party drivers).

IMO, both NGO nor Omega really offer any feature over the official drivers that helps anyone but gamers, and even for those, only in a handful cases.

If you have encountered a specific issue with your hardware and the current DriverPacks, feel free to post a thread about that so it can get ironed out.

Yes, it is.
Hence, you will have to look into Ryan's Update Pack for a possible solution to this.

No, but probably not properly applied by Ryan's.

DriverPacks BASE does not re-apply the fix because that could break some stuff and trusts in the Update Pack to have properly applied it already.

Hello and welcome to the DriverPacks!
May In introduce you to KTD (Keep The Drivers)?

If you did not modify the default path, it should be %systemroot%\DriverPacks

The driver installation routine won't allow you to install, that is correct.
This does not mean, however, the HW is not actually supported by the drivers.
As we do not call the original setup.EXE to install the drivers, this "problem" can be circumvented.

I experienced the same with a GF4MX400, and from what I can tell, it does not have any problems running on these newer drivers (granted, I don't do much 3D with it but the DXconfig test runs through as well as 3DMark and Google Earth).

I suppose if you were to manually install these drivers by right-clicking on the INF file, hence not using the setup.EXE, it would also work.

Give it a try sometime!

Yeah, it's definately better to fix the problem at its root rather than trying to just avoid the symptoms.

Even if you want to go that route, it would still be smarter to just find out which drivers in DPMS cause the problem for you and kick these out of your CD rather than creating a whole new installation for this case.

And should you still want to do that for w/e reason, I'd suggest creating one with all DriverPacks and one with all but DPMS, then you get at least all the other drivers installed instead of having a totally blank system.