Search options (Page 36 of 58)

Rgr.
Where do you want it?
DPMS, I guess...

Yeah, what lightsout said.

Generally, I consider it a very foolish idea to use 9x in a productive environment WITH inet access.
9x is no longer supported by MSFT which means it will not receive any critical (or non-critical for that matter) security patches, meaning your system is likely to get compromised through one of the numerous security holes.

If you are using it for an offline machine, that's fine, however, you may consider switching to Linux if you are just using 9x for the lower hardware performance footprint.

Is there any specific task you want to use 9x at?
I'm sure there's alternatives to be found.

Just FYI, jaak, the legacy drivers do not use the CCC at all but merely the CP (and probabaly an outdated version of that, too).

It would indeed have to go into a seperate folder, IMO, and should definately NOT be in DriverPack Graphics A (they aren't going to get updated anyway, hence legacy...).

I can't speak from personal experience because I do not use floppies anymore for years already, however, my (oldish) testing rig still features a 5.25" floppy drive (where floppies were still floppy!) and a 3.5" one and I can clearly hear and see them being accessed during the "F6" message in setup, so, appararently, there must be some access check going on even though I do not press F6 (for the lack of floppies and the need for additional drivers).

I hence expect this to work just as muiz says:
Put the floppy in before setup commences and it should find them (why else the access?).

Also, this is not the access during POST, which I have disabled in the BIOS anyway...

Symantec, it's their false alert.
(I haven't had any reports with NOD32, btw, so it doesn't appear to be "common" to false detect these files).

Then again, that hide CMD (or what it was called) the DriverPacks used was replaced by Bâshrat the Sneaky when it caused about the same rucus.
At least it wasn't so much a "false" detection because the AVS comlplained about it hiding the CMD window (which is exactly what it does, meh)...

That's true.
However, how many home users (not counting any of you (semi-)pros here, obviously) will make use of that feature?
For the ususal guy, port forwarding will do.
Of course, then there's a certain risk with this one port, but if you want total security, unplug from the net

Hahaha, that's fine, I know we have already lost you to the dark side of Mac

Ah, ok, then it's probabaly a matter of terminology.

To me, a virus always requires user input (unless you have autostart on... ), be it in form of an EXE or a corrupted multimedia file that causes a buffer overflow.

What attacks your PC through the net on unsecured ports is a worm in my book.
This is what NAT will protect you from, of course

The user input thing is certainly debatable (using your idiot reference), however, the only way to properly protect you from that is to only open/execute files you created yourself on a system that 100% wasn't infected at that time.
That means, w/o a scanner, you could even use the DriverPacks as they could potentially (from someone on the team who is unknowlingly compromised - I am not assuming anyone would deliberately do this!) be infected...
Of course, that doesn't mean you won't get false positives - but that is what common sense is for to sort them out.

Yeah, I'll give that a try and incorporate into the DPMS when I get around and no other team member gets to it before

It's just that I cannot test it so we'd need someone with appropriate HW to verify it really works.

So, any news on this?
So the 7.05.2 on the server is really just a 7.04 in disguise now or what?

Just asking because I am about to create a new disc and want to know whether I should use that or rather hold out a little for a fixed version

For some reason the HDA hotfix seems to be missing.
You need that one before you can even install the real drivers for your SC.

The driver setup is probabaly applying that hotfix prior to the driver installation, so it works then.

Are you using any Windows update packs before (hopefully not after!) BASE?

Yeah, I'm with Jaak on this one.

Basically, you should only ever be using M2.
There's virtually no reason for M1 anymore (unless you're troubleshooting a problem with M2 maybe), the amount of drivers is simply too vast as if M1 could cope with that.

Is there actually a specific reason why you switched to M1 (seeing as M2 is default anyway)?
Just curious...

Search and thee shall find!

http://forum.driverpacks.net/viewtopic.php?id=354

(dunno if the file is still up. If not, leave a note and I will upload it to the official webspace).

Yeah, my feelings exactly.

Only use links coming from the manufacturer's official website.
Firstly, that makes sure you can actually get support for that very version should you ever need it and secondly, this also gives some guarrantee it's a proper archive.
Now, we've all read the stories about HP and ASUS actually hosting virus-infected files on their servers and I can only hope everyone involved in thsi project uses an up-to-date scanner, but still, the risk is smaller if they are hosted officially.

Only when the latest final driver doers not work properly we will revert to some beta version if avilable, and if that cannot be found on the official page but is desperately needed (ususally, we will revert back to an older, working version), only THEN I support the use of such unofficial "fan" pages.