LoneCrusader

It's probably been updated since dencorso made that post. The new version should be fine. You actually do not NEED that file. MSCDEX.EXE is provided with Windows and should work for your CDROM. There is some disagreement about MSCDEX vs. SHSUCDX among myself, dencorso, and jaclaz. I prefer to use MSCDEX, they prefer SHSUCDX. But either will work for your project, so it's for you to decide.

Sounds like a hardware issue, rather than a software issue since neither NUSB or USP3 are making any difference. Check in your BIOS settings and be sure that no USB devices settings are disabled. Also be sure that when you first connect a header to the onboard ports that you do not have anything plugged into the header. Do a reboot after connecting the header and before you attempt to connect anything to it.

The more the merrier. Thanks!

Still getting these various errors, and they are getting more frequent...

You mean... like this? Yeah something to that effect.. lol. Thanks! Although from a quick glance it seems to be "long on the Vista/XP/2K files, short on the 9x files." I will investigate further as soon as I can find the time. I will have to "decode" some of the file names, looks much messier than the nVidia packages.

Probably this depends heavily on the system configuration where it is used, and how "old" the card is... note that M()zart is referring to performance of the older official driver version vs. a newer unofficial driver version for an "older" card. Personally, I see no reason (other than a bugfix of some sort) to use a later unofficial driver with a card that was already officially supported... I would only use the unofficial driver if it added support for a card which isn't supported by the official release. But, different strokes for different folks. I just finished archiving all of the packages and documentation from the nVidia page I linked. You don't happen to know of any such repositories for ATI Radeon driver packages, do you?

I don't think you would need to go back that far to find a 95 compatible driver package. Windows 95 OSR2.x was supported by most drivers even after the official end of Microsoft support (12/31/01). Granted, not nearly as long as 98SE and ME, but it's not like one would have to go all the way back to 1997 to find compatible drivers. If this page is a reliable source, it looks like the place to begin is 66.94. (Noted this version specifically says "95/98/Me" whereas later versions say "9x/Me.")

I think (hope? ) that one would not have to go back that far, but it is always a possibility. I would run such experiments myself, but I would have to disassemble and/or modify existing machines to do it. I don't have any extra nVidia cards lying around, and for that matter only have 2 in my whole arsenal. Maybe if no one knows then I will find time to investigate someday...

Quotes from another thread, but my question fits better here. Both the 82.69 and the 81.98 drivers do not work OK with a a GeForce 2 MX (I shoulld know... I use an MX 400). You can get the 77.72 and/or even earlier drivers either here or here. Regarding nVidia drivers - does anyone know which package version was the last to be 100% compatible with Windows 95 OSR2.x? By 100% compatible I mean a version where the nVidia Control Panel still worked as well.

So it would have to be run from a floppy? A floppy would work, provided there is enough room on the floppy for the files it will create. Better to just run it from the HDD as I suggested before.

Get a full IE 5.5 SP2 package from here. Official WMP 7.1 (mp71.exe) will not install on 95. MDGx had an unofficial version that fixed this, but it has vanished from his site. I have it archived on another machine but not here. Go here to get version 7.0, which will complain, but install anyway. Not sure about the Winsock2 issue. Never had problems with it...

Probably springs from this post and my responses.

I actually do not have much experience with this. I know generally HOW to do it, but I have never needed to do it manually or add it to Windows. Boot Disks are already automated for it. So I hope some other members will chime in. Take a look at these pages, which are directed more at your situation rather than directed at use on Boot Disks. (And there are no weird references to "tomatoes" or "bananas" ) MSKB Article on the subject. General CONFIG.SYS and AUTOEXEC.BAT instructions. (Many of the examples given on the second one are not really necessary, just depends on the machine and user preference.) You will need to load OAKCDROM.SYS in CONFIG.SYS, and MSCDEX.EXE in AUTOEXEC.BAT.

No. Name of the package should be "W95ws2setup.exe." I don't have a link for it handy at the moment, but if you can't find it I will upload it somewhere. Try looking on MDGx.com under the 95/95OSR2 Updates sections.

EXPLORER is probably set to "Hide filename extensions for known file types." In this case the .BAT would be hidden. I always disable that setting, and always turn on "Show All Files."

Links already given. I doubt you would be able to "easily" find it on Microsoft's site these days...

Hmm.. I don't think I've ever seen that before, but maybe TCP/IP was already installed on all of the systems I installed the Winsock2 update on. Windows 95 supports TCP/IP, but does not install it by default. It has to be manually selected during install or added afterward. The TCP/IP protocol can be installed by going to: Start>Settings>Control Panel>Network stay on the Configuration tab click Add choose Protocol click Add again choose Microsoft choose TCP/IP click OK you will have to restart at this point.

You can just leave them sitting there. If they are compressed, they will not be detected.

Well... It's not so easy as you make it sound. The Windows 9x CAB files are all "linked" together like a split RAR archive, etc. You can't rebuild ONE of them without breaking the chain of links. Also, there is a major "learning curve" about how Windows 9x SETUP works and how to add things to it. You have 3 options - 1.)Copy the \WIN98 folder from the CD to your HDD and fully unpack/extract (no .EXE or .ZIP, etc, must break down all the way to .INF's and SYS/VXD/whatever) the drivers you want into it, then create a new CD. SETUP will use any drivers or any newer files it finds in the \WIN98 folder. 2.)Read up on, and use this. 3.)Purchase RLoew's slipstreaming tools.

"Root" means the "Root folder," or in other words just in C:\ without being inside another folder. The "\" without any "named" folder after it stands for the root folder. You'll have to read up on basic DOS commands and PATH. It's essential to really knowing how your computer works, not just with Windows 9x, but with any system. A drive must be partitioned and formatted. Then the entire file and folder(directory) structure is built from the "root" folder C:\. So, in other words, WINDOWS\ is a subfolder of the root folder, and \SYSTEM is a subfolder of the WINDOWS folder. The PATH to this location would be C:\WINDOWS\SYSTEM\ and you get there by typing CD\WINDOWS\SYSTEM. "CD" is "Change Directory" and the backslashes \ denote deeper folder(directory) levels. In order to run a program, you must first navigate to the folder(directory) where it resides before you issue the command to run it. Take a look at the "Properties" of some of the Shortcuts in the Start Menu, say for Notepad or the Calculator for example. Notice the paths given to each program and how Windows automates this.

No DOS CDROM driver is loaded. You will have to load a DOS CDROM driver or copy the DETECT.EXE to your hard drive (C:\). Since you have no DOS experience, the easiest way to get a DOS CDROM driver loaded would be to use a Windows 9x Boot Disk... But the best thing to do for now is place DETECT.EXE in the root of the C:\ drive. When you get the C:\WINDOWS> prompt, type "cd\" and press ENTER. Then type "DETECT" and press ENTER.

So if I restart Win95 in MS-DOS mode, I can run it from there? Yes, or press F8 while the machine is first booting up and choose "Command Prompt only" from the Startup Menu. Ok, I am at the command prompt with the detect program on cd. I'm trying D>setup, D>detect, not sure what to do here. Never ran DOS programs. I assume you are at the "C:\>" prompt? If so type "D:" (or the letter of the CD drive if not D) without the quotes and press ENTER. Should get a "D:\>" prompt. Then type "DETECT" and press ENTER.

Yes, but be certain you have a backup of those drivers in case they are needed again. NUSB provides a generic driver that should work for all such devices, but keep a copy of the original in case your devices don't play well with NUSB.

So if I restart Win95 in MS-DOS mode, I can run it from there? Yes, or press F8 while the machine is first booting up and choose "Command Prompt only" from the Startup Menu.

No problem