Search options (Page 26 of 58)

Works now...

You can simply disable the Signed Drivers Policy so Win won't bother you with that again (it's unly of limited use if any, anyhow... Haven't seen someone "accidentially" installing a driver. If you do that, you most likely want to do it; and the WHQL logo doesn't even guarrantee no BSODs or anything like that so it's pretty useless).

I'm using nLite to get rid of that but you can also do it manually (I just don't know how off the top of my head...).

There should be a couple of posts about this already, try searching for them

Well, in case I didn't make that clear enough already, you won't have to make a new version for each PC (that would be insane and totaly contradictionary to the maxime of the DriverPacks anyway!) if you report the problems and our team fixes them

That's the best of both worlds, really!

I'm not sure where you want to have seen that because it certainly is not officially supported.
What you can do (and that has already been discussed numerous times on this forum) is simply deleteing specific dirs from the DriverPacks which contain the drivers you do not want/cause problems for you.
Then simply repack them as 7-Zip (see the tut link) and there you go.

If you know what driver it is causing the trouble you can simply unpack the DP, delete the driectory it's in and repack (for instructions see the links in my sig!).

Still, as I said, it's better to report the "faulty" drivers so our Team can fix them for the next release.
That way, you will also help others that may have the same problem.

A new version of the DH Mobility Modder has just been released (v0.8.8.0).
You can find it, as always, at http://www.driverheaven.net/modtool/

PS: 1000th post, YAY!

No, it's not.
The HWID (Hardware Identification) number is composed of the manufacturer and the HW model number.
It is only unique as in being assigned to products of the same model range (unless your name is nVidia...).
This is not to be confused with the MAC address of NIC's, which, in theory, are really unique, as no number is assigned twice on any other device.

You sure you aren't referring to the unique identifier numbers of Windows?
Those get assigned to each user account you create and even when you rename it (the account), the number stays the same.
Since the number is taken from a random number generator (with seeds based on your HW config as well as current time and date of the creation IIRC), it can be regarded as de-facto unique.
I'm not sure whether or how you can change that (why would you want to, Windows is using this to properly recognize user accounts); in any case, that question is certainly not related to drivers or HW so you may find better help at a Windows-centered forum.

Don't delete them!

The DriverPacks were created as being an addition to the drivers already delivered on your Win disc and hence do not contain those that are already present (unless there's an updated version available).
For a lot of old HW, there probabaly won't be any newer drivers than thos already on the disc so removing them will drop support for these.
Bad idea.

Also, nLite may be capable of removing fundamental drivers (IDE, USB, LPT and whatnot), which are NOT covered by the DriverPacks!

The only reason I can think of you may want to delete these drivers anyway is to save space on the disc.
If you are really that desparate (there's a lot of other, unnecessary stuff you can delete with nLite), you'd have to check whether DriverPacks contain updated drivers of these you plan to remove by checking out the device listing for each pack.
Don't think it's worth the trouble, though...

Yeah, from what you read on the net and other fora, both AVG and AntiVir, while being free, are somewhat useless due to their high rate of false positives.

Using NOD32, I only had a FP myself once (and that was in a file that got corrupted during the DL).
Also, I haven't really read much about users of other anti virus software than the two mentioned above reporting FPs.

I can't remember the correct address ATM but there are sites to which you can upload the suspected file and they will scan it with ~20 or so commecial anti-virus engines and then report you en détail which one reported what.
Most of the time, none of commercial engines will report any positives on these files.
That is not to say there never is a chance of them all missing it, but the likelyhood of catching a FP with AVG and AntiVir is rather high...

Anyway, not complaining about your post here.
It's better to be save than sorry and it also helps other users if you spotted something before it spreads even further.
Also, the fact that several folks are working on this project also means an infected file could accidentially slip in.

Heck, even big HW companies such as HP had offered infected drivers on their homepage and Acer was recently blamed to deliver notebooks with a virus pre-installed...

Definately.

If you stick to only the official DriverPacks (those you can find on the main page; you can also get additional 3rd party DriverPack in the sub-forum of the same name) it should easily be possible to fit them onto a 700MB CD-R/W if you're using nLite.
Even with SP2 and even post-SP2 updates slipstreamed, this should work.
In fact, slipstreaming any update packs takes up very little space because it directly replaces the files on the disc.

Also, be sure to check out the Tutorial and FAQs on the forum (mostly the stickies to be found here and there )!

You can use your old disc, copy it to HDD and re-slipstream.
The BASE will recognize that is has been run on that source already, undo all the previous steps and re-slipstream, leaving you with an updated disc.

I have done that a couple of times already and it always turned out well.

However, should you for some reason run into problems, I'd recommend starting off with a fresh source just so you can troubleshoot problems better

It certainly depends on your HW, but I'm with Erik on this one.

It's just like using UPX to compress your EXE files.
It takes a little more CPu time and RAM to extract them during runtime but you gain from the compression because the file is read much faster from the HDD.

Unless you were using a very fast DVD drive with a fast controller but a very slow CPU and slow or little RAM (192 MB is AT THE VERY LEAST recommended, I urge you not to install on less than 256 MB to make sure the extraction does not need to swap to the HDD, which will be extra slow, I guess, because it cannot yet use DMA), the method currently should actually be faster.

You could try for yourself (though it's not totally scientific):
Copy the DVD with extracted files (just extract all DriverPacks and burn them on an RW medium) to the HDD and compare that to the time it took to extract all DriverPacks onto the HDD (preferably again using an RW as the source of the archives).

Of course, this time, there will be DMA support and also better page file caching support, but still...