LoneCrusader

Yes, I think I already ended up with 7 copies of that one. Problem is that version is completely useless, unless the included VOLTRACK.VXD is the last version for 95 RTM. MS apparently issued 1116 for RTM and OSR2, but it does not solve the "Windows Protection Error" on fast CPUs. 1118 was issued for this, once again in packages for both RTM (FLOPUPD5.EXE) and OSR2 (AMDK6UPD.EXE). However, while 1118 and the final 1119 work fine on OSR2, they cause crashes on 95 RTM. EDIT: Incorrect information struck through. 1119 and 1119 work on 95 RTM.

It contains ESDI_506.PDR version 4.00.1112. EDIT: Ugh, who knows how many "updates" REMIDEUP.EXE has gone through. :wacko: This is an earlier copy of a KB article about it. With a different KB number, and references to even earlier versions for 95 RTM, but still listing the 1116 version.

No problem. I have a VM specifically for that. Thanks for the link, on my way to get it and investigate.

Yikes... Even this old copy of the MSKB article references the version I need, but then proceeds to claim the package contains 1116.

Time to resurrect this thread. I'm searching for a specific HotFix file for Windows 95 RTM, ESDI_506.PDR version 4.00.956. It was part of the original REMIDEUP.EXE (and possibly other packages) before it was later edited to include ESDI_506.PDR version 4.00.1116 instead. Anyone out there happen to have this?

I can download the 98FE version without problems. The 98SE version loops back to the page jaclaz linked. This is under XP using FF 3.6.27. Spoofing the User Agent to garbage has no effect.

IMMC WIN98SE - Don't know what this is offhand? MICROSOFT PLUS 98! - I always add this to my systems, just be sure not to install the old McAfee Antivirus that is included in it. (I also don't add the "compressed folders" extension because I use WinRAR, but it's up to you.) MSAA20_RDK WIN98SE - Should be OK, never used it. MSBCKUP 98SE - Should be OK, never used it AVIRA NTFS FOR DOS_H98SE - Paragon NTFS may be a better choice... RP9 98SE - Personal choice. I don't use it. SYSPLG98 - Not needed. Already in NUSB. USB20DRV 98SE - DO NOT! I repeat DO NOT! Install this. NUSB covers this and this package is buggy.

hmmm never get to the page where it actually downloads. Am I clicking the wrong links? Don't know what's going on there. I'm getting the same loop. You can get NUSB from here as well. It's really funny when USB device manufacturers start distributing NUSB as a driver for one of their products from their official website...

As I mentioned in the other thread, MDGx hasn't been answering my messages for over a year. I've sent about 4 emails over that span, and all have gone unanswered. Entire portions of the site; the /spx directory, (other parts linked from the bottom of one of the pages you linked ), and who knows what else have simply vanished, and I don't think we should "expect" it to get fixed at this point.

You're not alone if those "RAM tweaks" for Windows 9x above 512MB given here and elsewhere didn't work for you. They have never worked for me either. I purchased RLoew's RAM Limitation Patch, and have never looked back.

OK. That's finally solved.

Wow, I don't know how I missed that, given the current state of things and my current project. I guess it just goes to show how much we depend on MDGx's site, without even thinking about it. I retrieved most of those links from there, except my own link for Flash Player.

NUSB (version linked is not the newest but it will handle everything), Direct X 9.0c, IE 6 SP1, WMP7 (or WMP9, or even MDGx's Unofficial WMP10, depends on your preference). Firefox 2.0.0.20, Adobe Flash Player 9.0.289.0, Java 6 Update 7 (right click to save). Also take a look at the Adblock Plus, PlainOldFavorites, and User Agent Switcher addons for Firefox. You will probably have to search older versions of those, especially Adblock Plus, to get one that works with FF2. I don't use any AV software myself, but other members here can advise you better than I can on that issue.

No, the HTML documents are just for reference. Have you checked the BIOS settings to verify that the onboard sound, etc is all turned on? Have you already added the other sound card? If so, you should remove it for this... Also if the onboard sound was turned on during your Win98 install, you may have to remove any "unknown devices" from the Device Manager in order for it to be redetected.

Now, after Multi-Quoting myself ... I present another quote from a well-informed member that all of us have somehow overlooked. In the event I have the opportinity to verify this or my earlier guess, I will just update this post with the answer to my original question. Not yet and no plans either ... If my mind is not too hazy, I believe the last that works on w95 out-of-the-box would be 61.76 but that was many moons ago the last I tested ... If I'm not mistaken above 66.94 has cpl api issues ... Apparently ..... but highly probable only the driver sub-system will still work if at all ... The highest that I got to work properly on w95 was 77.72 ... driver sub-system (VxDs) will work fine but certain modules like control panel uses win98 api and those need patching ... However, I do believe 82.69 will also work if we remove cpl modules ... Rgds EDIT: The last version of nVidia drivers FULLY compatible with Windows 95 is version 56.64. Later driver versions (actual display driver itself) including the final 81.98 work but have errors with the nVidia Control Panel.

According to this page, the last 9x drivers have "Support for the GeForce 6 series GPUs" As for the rest of your question, I'm not experienced with nVidia, so maybe someone else can help you.

No problem. But you should have the option somewhere to choose other Operating Systems besides XP... At any rate, the links jaclaz gave will provide the correct packages as well. The only advantage to using the Service Tag over the general download page is that using the Service Tag will filter out packages that do not apply to your machine. For example, sometimes Dell may have produced the same model of computer but used different Video Card manufacturers in some of them, so the general Downloads for that model will give you both video driver packages, while the Service Tag option will only give you the ones for your specific machine.

Now we can have a war about who is "die-hardest!"

Somewhere on the machine there will be a sticker with a letter/number code on it. Usually it is even labeled "Service Tag." This is a unique identifier for each machine. When you enter it at Dell's support site, it will automatically give you all of the downloads for that particular machine. See these: (I know your machine is older and will look different. ) If the sticker is missing, then it is usually encoded in the BIOS as well and can be read at the top of the screen there.

For this one you should be able to go to Dell's website and enter the machine's Service Tag number. I haven't used Dell's site for a machine that old in a very long time though... I actually have a friend who used to use that same machine. I have all of the drivers for it archived somewhere. If you can't get what you need from Dell with the Service Tag, then I'll see if I can find them.

We're just poking fun at one another. There was never a "war" over it, but I once took exception to being "encouraged" to use it along with some other tools I did not care for. Agreed 100%.

Yep. And MSCDEX has yet to fail me, so still I plan to keep it.

Well, I don't see how you can say there is no "disagreement" when we still each recommend the opposite program. However I do agree there is no reason to debate it. But since you "quoted for the record," so must I.

It's not that simple. The old "Dial-Up Networking" updates for Windows 9x contained updates for all "networking" functions in general. So one should install these whether you use dial-up or not.

All those files are included as part of the Dial Up Networking 1.4 Package. You seem to have an inordinate amount of trouble getting these updates to find themselves. Seriously though, I don't know why the installer can't manage to find them itself. Try the advice I gave earlier (below), if that doesn't work, use 7-Zip or whatever to unpack the dun14-95.exe package and you will find those files inside msdun.cab.