Search options (Page 32 of 58)

Thanks, OverFlow.

I considered this obvious since it's the ususal way on how to apply the DriverPacks, but this should definately deal with any unclear items

I know it sounds rather unrelated, but have you checked for any dust in your case and verified the ariflow is good?

I've had several cases where BSODs (dunno if it was the IRQ !<= error, but that seems the most common, and I don't get any very often) could be traced to that, so it's definately worth a look.
Also check CPU/mobo temp and voltages.

You never know, esp. if it presumably was working fine before in the same constellation!

No.

Seriously, just create a CD/DVD (including alll your OEM stuff and the DriverPacks) now, if you haven't already.

Then, when you need new drivers, use that disc (or the folder you used for your source if you didn't delete it after ISO creation) and simply slipstream the DriverPacks into it again, just as if you had not done that before.
It will detect and remove the old ones, replacing them with the updated driver files.

As DriverPacks slipstreaming is the last step before ISO creation, none of your OEM settings will be touched and don't have to, either.
Just create a new ISO, re-use the old disc (if RW) and there you go.

Whether you use OEM stuff or not is not relevant in this case (unless I am missing something).

Now, I know I am sounding a bit penetrant and I certainly don't want to talk you into something you do not want.
However, I want to make sure you realize this before clinching on solutions in search of a problem.
IMO, all that efford is not needed if you follow my simple and time-saving steps.

Now, I certainly do not know how it is handled at your work and your boss may require certain protocols and whatnot, so please excuse if I'm omitting that.

This is just a "here's how I would do it" advise

Nice to hear and eagerly awaiting!

Just do take your time, no one wants rushed releases

Want me to take a look at it and extract any necessary files (knowing Acer they probabaly added a lot of useless stuff - I've found DirectX components and Acrobat Reader in their archives *argh*)?

EDIT:
DLing now but at a slow, capped 50KB/s.
Darn their FTP!
45min to go...

Good ole Notepad does splendid job for me ususally.

Using Notepad 2 or Notepad++ if the file become a bit too big for the MS programme to handle, though...

Just mind the encoding options...

I have to admit, I am totally with OverFlow on this one.
Create your new disc when you need it, and include all the stuff up-to-date on that day.

MS patches aren't realeased more frequently than monthly (which is a good pace to create new discs, also, using re-writable media you save a lot of money anyway) and mostly (unless there's a serious bug) DriverPacks are updated in the same way.

Does that equal that (security) patches from MS are not to be applied, too?
Of course, the internet security ones are probabaly not required in this case, however, there are some related to LANs and productivity and you may want to get these, internet access or not.

Why not?
Simple question, really.
Just keep a copy of the disc's content on your HDD and work from that.
I certainly am not going to pull out my XP disc each time I am going to create a new one.
Takes way too long to copy the files and is inconvenient.
That way, you can keep the disc in the safe (or wherever) and it won't get scratched.

Why is that?
You said they don't have inet access.
Are you hence using WSUS for the task?
If not, it's certainly a matter of doing it manually or not doing it at all.

I may be getting this totally wrong but let me give you this old admin saying:
"Never change a running system!"
Why bother with driver updates at all when the machines are up and running?

Granted, I do update my GFX drivers every so often, but purely because of gaming.
If it weren't for that (and I take it yours are office machines?), I wouldn't update any drivers as long as all devices are running satisfactory.
Only if the machine had to e reinstalled I'd use a disc with updated drivers (although that may break some stuff that worked before )

The drivers are being installed during the fake setup phase (if you're using M2), that's right after you've seen the extraction status bars.
The Finisher installs any needed (as in the HW for them is present) GUIs, control panels etc, everything driver-related that is not a driver itself (so anything but INFs or SYSs).

What does help you in this very case is the KTD (which is applied by the Finisher), namely by indexing all the kept driver files so Windows can readily use them as it is being made aware of (otherwise it would be the same as if the driver files would sit in an arbitrary folder - drivers won't get picked up and installed automatically as you probabaly know ).
It creates the PNF files that make Windows access/scan the folders for drivers for your current HW setup.
Just as it does check in the driverc.CAB, on WIndowsupdate.com or the %SOURCE% when you install new, unknown HW.

Maybe, just maybe, it would have been smarter not to tell which slogan is by whom on the voting page (only on results) so folks can vote simply based on the slogan rather than its creator

In any case, it seems you can send multiple vots somehow.
Is this deliberate or an oversight?

If you just want the *.LNG file, you can simply take it from the BASE.
It can be found in the \lng subfolder.

Just open it with an editor of your choice (notepad works fine).

Nice database!

Could come in quite handy, hence stickied

Yeah, but without the ususal different HWIDs for each case...

I wish HW manufacturers would put more efford into the IDs.
It can't be that hard to manage that properly, especially since they already re given unique manufacturer IDs in the first place!