Search options (Page 23 of 58)

Not everyone uses MSN, plus it's proprietary.
Jabber would probably be the better protocol, IMO.

I think we (the team members) do have some Google groups stuff going thanks to the @driverpacks.net email addresses which are powered by gmail.
I haven't really used/looked into that, though.

If anything, I am idling in ICQ once and again (old time inet user as well as ICQ - there was not much else around back then and I really don't feel like ever switching. I did dump that bloody ICQ client, though and am using Miranda on Windows and Pidgin on Linux. Yes, I know I could also use MSN through that but I really don't feel like having to remember another login data set Anyway, my contacts should be in my profile. I you want me to authorize you, make sure I know who it i´s or you will be denied!)

If you wish to (and have enough space left on the disc), you can safely go ahead and also include the rest of the 3rd party DriverPack.
Does no harm but provides a lot of drivers in case you may need them.

They are only unofficial because we do not maintain them as closely as we do with the official ones.
They also do not include instructions for the Finisher (but they could, if added) and are mostly contributed to by the community rather than team members (although others as well as me have done quite some additions already).

Just FYI

I don't see any links?!

Anyway, yes, the Driver Signing Policy is a real pain in the arse if you are using unsigned drivers.
The problem here is a) not every manufacturer offers signed drivers and b) that Windows will always pick a singed driver over an unsigned one, even if it is (way) older.
So, if there is a signed driver supplied with Windows (as found on the RTM disc) but the DriverPacks deliver a newer (presumably better) unsigned driver, then Win will still pick the old one.

The solution here is to simply disable Driver Signing Policy in the winnt.SIF by setting the entry under

[Unattended]
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore

.

That way, Win will pick whichever driver is newer regardless of signed status.

Not sure if this really fixes this very problem, though.
You speak of a bug in SP2, I have not heared of this before (not saying it doesn't exist, just didn't come across it yet).
You could also try to go ahead and use SP3, seeing as the final is already out (albeit inofficially, check thehotfixshare.net). Might fix that bug if it's a known one.

Thirdly, we offer a Monitor DP as a 3rd party DriverPack.
It contains quite a lot of monitor drivers, maybe your is included.
That should eliminate the need for an online search.

Satellite broadband probably does require a fixed proxy to work (from what I've heared/read, never had that myself) so that may be your problem.
Maybe check with your ISP.

Do you have any proxy set up in IE settings?
Does it require you to run a tool/programme to dial in?
98 doesn't have native BB support anyway so you'd at least need a PPoE driver or somesuch, IIRC.

Me, neither, so it took me quite a while to find this out.
Even more surprising when this was working great for months if not years before so I was puzzled very much when it stopped working.
Only though coincidence I happended to remember my ISP's proxy which I last used some +5 years ago.

The even funnier thing was that all the nightly downloads worked fine (so I could test them packs alright) but I couldn't get any of the official ones
Well, as long as I grabbed the latest nightly before finalization (which usually is just a rename anyway), I was fine...

For me, several months ago it wouldn't work UNLESS I set up my ISP's HTTP proxy (which I usually never use because I'd get referrer errors from other sites then).
Because this is the largest ISP of Germany and basically affected all their customers, I think Bâshrat the Sneaky changed something in the referrer code to make it work again without the proxy.

As for your case, I can only give you the advise to fiddle with your browser's HTTP proxy settings seeing as you've tried virtually all the other options already...

I haven't been using any of the Norton/Symantec programs for a couple of years now but I am a bit puzzled what blocking HTTP referrers (that are part of the HTTP specification if I'm not mistaken) has to do with firewall measures.
Probabaly nothing...

OTOH, having to disable your PFW simply to download a file seems to be a rather unadequate measure for such a simple task.
Firstly, if you really NEED a PFW (i.e. no router or other means of HW protection) then it's probably not the best idea to disable it AT ALL.

Secondly, if you do not need a PFW (mainly because you do have HW in use for the task) then the question remains why you are using one in the first place.
No harm done here apart from the fact that it will use up a little system resources and seems to be quite bothersome seeing as you actually have to fiddle with it in order to simply download a file (and we certainly aren't the only site using HTTP referrers).

Thirdly, even if there was spyware involved (h*ll NO!), a firewall wouldn't be the proper tool to protect from it - a virus or malware scanner (most AV solutions include the latter one) is what it would take to uncover this.

PS: Yeah, I know I'm quite anti-PFW and I'm sure I am repeating myself here one or the other way.
No need to tell me this - again (you can though, if you really wish ;P)

Sure do, that was just meant as an FYI post to provide a little more info for the intrigued user

Basically, it's good to use AHCI if you can but not too bad to not use it if you can't

AHCI does not only offer hot-plugability.

Basically, the idea was to create a unified driver architecture for HDDs so you actually wouldn't need to feed a manufaturer-specific driver during installation (just as it was in the good old dasy with standard IDE controllers).

Of course, this requires the OS to supply the unified driver, something which has not been implemented in XP, of course, due to its age (dunno if SP3 would bring such a driver if slipstreamed, haven't tried that myself).

IDK about nVidia in this case, but theoretically, this should solve our driver woes with them.
Seeing as AHCI is an invention by Intel, it may be that nVidia does not support it 100% by the book, though

Also, AHCI will ususally be needed to make NQC work with SATA drives.
Run them on a controller that uses the legacy setting in the BIOS and they will behave just like their IDE brethren so you gain nothing by using SATA (save the fragile plugs maybe...).

All in all, if possible, one should run in AHCI mode for best performance and compatibility (with up-to-date OSs that is), however, if not possible, reverting back to legacy mode in the BIOS is not that huge a loss to the ordinary user.
Just make sure to set the BIOS properly before you commence installation and do not switch it when an OS is installed unless you take precautious measures!
The HWID of the controller will change if you switch so you will have to have the proper drivers already installed on the OS or you get a BSOD.

No, it appears it was only the WAIK (which I already got before but in a smaller version containing only German language support).

The lone SP1 should sport around 434 MB from what I have gathered.
So far, there only seem to be torrent sources for the ISO and thehotfixshare.net hasn't got the installer file, yet.

Oh well, it's not as if I'm in a hurry, just a bit curious since I already tested RC1.
I'm not using Vista myself anyway (but know enough folks that have serious issues with and could make good use of SP1; I just don't want to install a non-final version on their rigs...).

It is possible, you can unpack all the packs into one directory and then repack them as you please.
However, IDK how the Finisher works if not all packs are being detected by BASE (since there's only one file and detection works via file names it cannot work).
I would think it would be treated as a 3rd party DriverPack mostly.

The real question is what would be the gain of this and do you want to setup the torrent yourself?