LoneCrusader

Microsoft issued basic USB Controller driver support for 95 OSR2. The package also included some files for using USB cameras, but no other USB devices were supported by Microsoft at that time. There were a handful of USB devices that did work with Windows 95, but each had to provide their own driver stack rather than having a generic stack built into the OS (such as USB storage, USB-HID, USB printers/scanners) as began with 2K/ME/XP. Specific USB devices that do work with 95 and had their own drivers are extremely scarce; most manufacturers couldn't be bothered to create WDM drivers for 95 since 98's WDM capability was so much more advanced. So, in all reality, unless you already had a specific USB device with a driver designed for use with 95 you gained nothing from the Microsoft USBSUPP package. The XUSBSUPP package rloew and I put together combines the Microsoft USBSUPP update (and all of the later HotFixes that were issued to fix broken things in it) with a generic USB Storage driver stack, a safe unplug/eject utility, and a special driver to reset USB2 controllers into USB1 mode so they can be used under 95. This is virtually the extent of USB device capability under 95 without the specialized hybrid setups I mentioned before. Side note - in order to be able to use a Scroll Wheel under 95 you must install IntelliPoint 3.1, 3.2, or 4.0, or a third-party mouse driver that supports the wheel. I recommend IntelliPoint 3.2 as 4.0 doesn't seem to add anything new for 95 and has silly requirements such as IE5 being installed, and, it calls home for updates without asking permission.

Hello again! Glad to hear everything is still working! As rloew has already pointed out, there are no existing USB-HID (Mice\Keyboards\Joysticks) drivers that work under Windows 95. We have been able to graft Windows 98 NTKERN + the Windows ME USB Stack + Windows 98SE USB-HID stack onto a Windows 95 system. USB2 drivers can be loaded as well but may suffer issues depending on the hardware. This of course requires several specialized files designed by rloew and some patches to NTKERN, along with a file from a Beta version of Windows 98. It won't help with your USB Mouse, but a replacement package is now available that replaces all of the Microsoft USBSUPP packages and also replaces USBSTR95. The provided USB Storage driver is much more robust and handles basically every USB Storage type of device that could be obtained for testing. HDDs, optical drives (including Blu-Ray), ZIP drives, flash drives, flash card readers, FDDs, etc etc. Even U3 devices. It is as close to NUSB as you can get for 95 now, unless you have the hybrid system rloew and I have described.

You can disable the login box when using Client for Microsoft Networks by deleting the "PrimaryProvider" key under HKLM\Network in the Registry. I'm not in front of my 98SE machine at the moment so the path may be slightly different, it's been a while since I looked at that specific issue.

I didn't mean that Dave-H should deviate from the DOS avenue; this has many possibilities in and of itself that may be more extensible to a wider variety of hardware. I just didn't want to see the other avenue so quickly dismissed since it may enable the use of the Windows drivers.

This is a possibility that should not be quickly dismissed though. If the driver farfigs11 mentions only lacks one WDM function under 98SE, then there is a chance that it could be made to load with WDMSTUB or a more advanced approach such as rloew's WDMEX. The real question is what other dependencies might that specific file have, and is it deeply intertwined with some other part of the Windows driver package that requires NT; or, will it "just work" as a substitute for the 9x file when placed with the rest of the last driver package for 9x provided the missing function is satisfied.

Check the jumper setting on the HDD. If it is the only drive on the cable just remove the jumper, as this can cause a delay during POST and possibly other delays later.

I have seen issues before when trying to run 98SE on a "prefab" (i.e. Compaq, Dell, HP) system that originally came from the manufacturer with XP installed. I have no explanation for the issues, other than maybe the PC manufacturers make small tweaks to the systems that make them unstable under 9x. These issues can manifest themselves even when all of the necessary drivers can be found for the hardware. A couple of examples; a friend of mine had a similar Compaq that I never was able to get 98SE to run stably on, and I once tried to set up 98SE on a Dell Dimension 2400 that had an Intel 865 Chipset motherboard (a chipset fully supported for 98SE and one that works perfectly under most circumstances) that never seemed to run smoothly. The best thing you can do is choose a motherboard that has 9x drivers and build a system from scratch; but I know in some cases this is not possible... Good luck...

No to mention the fact that a VM seems to be involved somehow...

Glad to hear you got everything working!

The various RAM tweaks for using more than 512MB never worked for me, so I'm surprised you got as far as you have with 2GB, congrats. Installing NUSB should take care of the USB issue (a USB2 controller driver is lacking in Windows 98, NUSB provides one along with a Mass Storage Driver). Did you install the TCP/IP protocol when you set up 98? Do you have the LAN card set to Obtain an IP address automatically? (assuming you are using DHCP) Also be sure to check an see if IE is in "Work Offline" mode,if so, turn it off. Anything else, we will probably need more detailed specs for your machine.

Try setting up your system without the Unofficial Service Pack and see if the problems still exist. Unless you have a hardware problem, I'll wager it is the source of your issues.

Mass Storage Controller driver stacks and USB2.0 driver stacks are two completely different entities. NUSB provides both for 98 simply because 98 lacks both and it made sense to bundle the USB updates. USB2 drivers were produced for 98. None were ever produced for 95, and the 98 versions will not work under 95. There is no solution to this unless a method to substantially update or expand NTKERN under 95 can be achieved.

What does the BSOD say specifically? USB Keyboards, Mice, Joysticks, and no doubt many other devices are not supported under 95, PERIOD. Just because it works under 98 or ME does not mean it will work under 95. In fact you can safely assume that NO WDM driver designed for Windows 98 or later will work under 95. This includes the HID driver stack. If you really want something to test and occupy your time, download the Windows NT4 DDK and extract the contents of the \win9x\usb\ddk\hid\bin folder. This HID driver stack was designed for Windows 95. That should keep you busy for a while. If you can get it to work, please let us know.

Limiting RAM on a system with the various "tweaks" floating around the net never worked for me, not even to run anything over 512MB much less 4GB. The RAM Limitation Patch is the way to go, I purchased it, installed it, and never looked back. RLoew is very prompt and helpful in his responses. As far as I know you are right about the 6800 Ultra, it should work. I have virtually all ATI brand video cards myself but I always planned to try to get a 6800 Ultra at some point so I would have the "top of the line" in both brands for 9x.

Glad to hear you're working on it. Thanks!

For that specific DLL you can simply copy the 98SE version to 95. As for others it depends... you'll have to be more specific.

Your best hope is to wait for MDGx's website to come back up; it has been up and down intermittently as of late. It contains the largest assortment of Windows 9x updates still available. If you cannot find them there, you may try searching for the MSKB article numbers through his HotFix Request Form... but in either case you still need MDGx.com...

Or, you could simply spend $11 for rloew's SATA Patch and fix the issue the right way, and have full functionality without any drawbacks.

I believe the Unofficial Service Pack installs the original USBSUPP packages by default, which could definitely cause issues when combined with XUSBSUPP. I have not tested the packages together, but I wouldn't advise using both on the same system. I had trouble with the Unofficial Service Pack before; it seems to be incompatible with my FIX95CPU package and it rendered one of my 95 test setups unbootable... Thanks for testing! EDIT: Added some screenshots to the first post.

I have never used any PCMCIA devices so I'm not familiar with them... A driver is provided; they can't work "without" one, but the one provided is superior to all of the previously available drivers which all had some serious limitation (only worked with some devices and not others) or another.

Well, here it is folks. USB Support for Windows 95 - simplified. This is essentially "NUSB for Windows 95" except for the fact that no USB 2.0 drivers exist for Windows 95. No hoops to jump through. No multiple packages to install. No endless searching for USB storage drivers that work. This package has been a long time in the making, and would not be possible without our good friend rloew, who has created a universal USB storage driver that is Windows 95 compatible. Click here to download: XUSBSUPP.ZIP So without repeating myself, here is the "ReadMe" for the package, which will provide further details. ========================================================= XUSBSUPP - eXtended USB Supplement for Windows 95 OSR 2.x Version 1.0 July 15, 2014 Copyright © 2014 Conner McCoy (LoneCrusader) & Rudolph Loew (rloew) ========================================================= OVERVIEW: This unofficial update package for Windows 95 OSR 2.x (95B and 95C) combines all of the original Microsoft USB Supplement packages and HotFixes ever issued for USB support under Windows 95 along with a universal USB Mass Storage Device driver solution for Windows 95 into one stand alone installer. This package is similar in function and intent to "NUSB" - a popular unofficial update for Windows 98 Second Edition. Once installed, no other third-party drivers will be required for USB Mass Storage devices and they will simply "plug and play" as they do under Windows ME, 2000, or XP. A "Safe Disconnect & Removal" utility is also provided that will appear in the System Tray when a device is connected and functions like Windows ME, 2000, or XP. This package is intended to be used on a new, clean installation of Windows 95 OSR2. It is not recommended for use under other circumstances or conditions and has not been tested under other circumstances or conditions. Do NOT install this package on a system where the original Microsoft USB Supplement (USBSUPP.EXE) has already been installed, as it will DESTROY the backups created for uninstalling the original Microsoft package. ========================================================= INSTALLATION: WITH A NEW INSTALLATION OF WINDOWS: 1.) Install your new Windows 95 OSR2 system. 2.) When Windows 95 SETUP is complete, reboot your system. 3.) When your system has rebooted, open Control Panel, System, Device Manager. 4.) Remove all unknown "Other devices" from the list of hardware. 5.) Run XUSBSUPP.EXE and follow the prompts. 6.) As the system reboots, follow the prompts to install drivers for USB devices. 7.) When the Desktop has loaded, connect a USB Storage Device and proceed as you would with any later version of Windows. WITH AN EXISTING INSTALLATION OF WINDOWS: ***NOTE that this package must not be used with USBSUPP.EXE already installed.*** 1.) If USBSUPP.EXE or any other package that provides USB drivers has been installed, each must be uninstalled and you must reboot before proceeding. 2.) Start with a clean boot of your system. Do not perform any other tasks prior to beginning this installation. 3.) Open Control Panel, System, Device Manager. 4.) Remove all remaining USB devices (if any) and all unknown "Other devices" from the list of hardware. 5.) Run XUSBSUPP.EXE and follow the prompts. 6.) As the system reboots, follow the prompts to install drivers for USB devices. 7.) When the Desktop has loaded, connect a USB Storage Device and proceed as you would with any later version of Windows. ========================================================= UNINSTALLATION: 1.) Open Control Panel, Add/Remove Programs. 2.) Select "eXtended USB Supplement to Windows 95 OSR 2.x" and click "Add/Remove." 3.) Follow the prompts and reboot your system. 4.) Be aware that two empty folders will remain inside your Windows directory, namely \SYSTEM32 and \SYSTEM32\DRIVERS. If these folders are empty they may be safely deleted. 5.) Be aware that copies of USB.INF, RLUSB95.INF, or other INFs contained in this package may exist in the \INF\OTHER folder if placed there by Windows 95. They should be removed manually to prevent confusion if other drivers are used. ========================================================= CONTENTS: This unofficial package contains the following files, listed by the original official update or third-party package that contained them. The file name will be followed by its corresponding version number or in cases where no version number is available the original timestamp will be used. Files that were included in an earlier update and later superseded by a HotFix will be listed under the latest HotFix. Files that have been modified from their original version will be denoted by a "*MODIFIED FOR XUSBSUPP" notation. -Files included in original USB Supplement and files later superseded: USBSUPP.EXE Original Microsoft Package v.4.03.1214 - Windows 95 C CD-ROM AUTOEXEC.BAT Thursday, April 10, 1997 12:14:00 PM CONAGENT.EXE Thursday, April 10, 1997 12:14:00 PM DETROIT.INF *MODIFIED FOR XUSBSUPP DEVLIB.EXE Thursday, April 10, 1997 12:14:00 PM IMAGE.INF *MODIFIED FOR XUSBSUPP IMAGECLS.SYS 4.03.1212 KRNL386.EXE 4.03.1212 LICENSE.TXT *MODIFIED FOR XUSBSUPP NODRIVER.INF *MODIFIED FOR XUSBSUPP REDIRECT.MOD Thursday, April 10, 1997 12:14:00 PM RPLCLDR.EXE Thursday, April 10, 1997 12:14:00 PM SPOOLSS.DLL 4.03.1212 USB.INF *MODIFIED FOR XUSBSUPP USBCAMD.SYS 4.03.1212 USBD.SYS 4.03.1214 VCOND.VXD 4.03.1212 VFWWDM.DRV 4.03.1214 VFWWDM32.DLL 4.03.1214 VMCPD.VXD 4.03.1212 VPICD.VXD 4.03.1212 VTD.VXD 4.03.1212 VWIN32.VXD 4.03.1212 VXDLDR.VXD 4.03.1212 WINOA386.MOD 4.03.1212 USBUPD2.EXE Original Microsoft Package - Windows 95 C CD-ROM *ALL FILES IN THIS ORIGINAL UPDATE ARE SUPERSEDED AMDK6UPD.EXE Original Microsoft HotFix - MSKB Q192841 & Q234259 NTKERN.VXD 4.03.1213 247965USA5.EXE Original Microsoft HotFix - MSKB Q247965 VMM.VXD 4.03.1217 USBUP.EXE Original Microsoft HotFix - MSKB Q181499 OPENHCI.SYS 4.03.1217 HUBUPD.EXE Original Microsoft HotFix - MSKB Q189284 USBHUB.SYS 4.03.1218 e7kusb9p.exe OEM Update Package from Toshiba UHCD.SYS 4.03.1218 175086US5.EXE Original Microsoft HotFix - MSKB Q175086 KERNEL32.DLL 4.03.1216 *SUPERSEDED BELOW BY UNOFFICIAL BUG PATCH -Files added to correct known bugs and to expand functionality: 249070USA5.EXE Original Microsoft HotFix - MSKB Q188803 & Q245583 & Q249070 MSGSRV32.EXE 4.00.1112 Solves Plug & Play lockups on some systems DISKUPD.EXE Original Microsoft HotFix - MSKB Q214522 DISKVSD.VXD 4.00.1114 Solves misreported sizes for USB disks W95Y2K.EXE Original Microsoft Update - MSKB Q225050 & Q225053 CFGMGR32.DLL 4.10.1422 SETUPAPI.DLL 4.00 CFGMGR32.DLL required by HOTPLUG.EXE These two DLL's are usually paired so both included KERNEL32.ZIP KERNEL32 2GiB BUG PATCH FOR WINDOWS 95B/95C KERNEL32.DLL 4.03.1217 RRL This patch corrects file copy errors with files larger than 2GB and is provided as free software from Rudolph R. Loew. RLUSB.ZIP RLUSB9X USB Mass Storage Driver for Windows 95+ HOTPLUG.EXE 1.0.0.0 RLUSB95.INF *MODIFIED FOR XUSBSUPP RLUSB9X.SYS 1.0.0.0 RLUSBPDR.PDR 1.0.0.0 USB2STOP.VXD 1.0.0.0 This universal USB Storage Driver package is provided as free software from Rudolph R. Loew. ========================================================= KNOWN LIMITATIONS: This package does not provide a driver for USB 2.0, as no such drivers exist for Windows 95. Many hours were spent by the authors searching for a compatible driver, and many hours were spent in experimentation trying to get Windows 98-compatible USB 2.0 drivers to load with no success. This package does not provide a driver for USB 3.0, as no such drivers exist for any version of Windows 9x. This package does not provide a driver for USB-HID or USB peripheral devices such as keyboards, mice, or joysticks. While some very early ("embryonic" shall we say) and incomplete work was done in this area by Microsoft (see the Windows NT4 DDK), unfortunately none of the sample driver files provided actually work. If anyone knows how to make the Microsoft files from the DDK work and can successfully demonstrate this, or knows of any working third-party USB peripheral drivers for Windows 95, please inform the authors of this package. This package enables the use of USB-connected optical drives, but does not provide a driver for the UDF filesystem frequently used on CD\DVD\Blu-Ray discs. Visit Rudolph R. Loew's homepage at http://rloew1.no-ip.com for a suitable driver. When unistalling this package, two nested folders will remain in your Windows directory, specifically the folders \SYSTEM32 and \SYSTEM32\DRIVERS. If these folders are empty, they may be safely deleted. This package does not remove them due to a limitation in the Windows 95 version of WININIT.EXE. ========================================================= LICENSE AGREEMENT AND LEGAL ISSUES: This package is provided as free software by Conner McCoy and Rudolph Loew, hereinafter referred to as "authors." By using this software, you agree to accept the various license agreements denoted here in this text and included inside the installation package. By using this software, you assume all responsibility for its use or misuse and agree that the authors provide no warranty or guarantee of any kind as to the usefulness of this software for your purpose; and that the authors will not be liable for any damages resulting from the use or misuse of this software. This package may NOT be distributed without this document attached and intact. This package may NOT be disassembled, reverse engineered, used in a manner other than its intended purpose, or otherwise altered or tampered with without the express permission of the authors. ========================================================= Here are some screenshots: 6 USB Devices connected - (4-Slot Card Reader, Flash Drive, Floppy Drive, Hard Drive [sATA/IDE to USB bridge], ZIP Drive, SATA Blu-Ray Optical Drive) Device Manager Click here to download: XUSBSUPP.ZIP

Have you installed any other Updates, Software, etc to your VM besides NUSB? If so, there is a possibility it could affect the joystick. If not, unfortunately I don't have any more advice to give... Hopefully some other member may have some insight...

You're welcome! Glad you solved part of the problem at least... Now, as for the rest of your problem, hopefully some other members here can add something now that we have gotten this far... I would try removing the joystick from the Device Manager, then rename the SW13W98.INF file to something else, say SW13W98.OFF, disconnect the joystick, and reboot. Then reconnect the joystick and try installing your updated drivers for it. Those would be "Software specs" not Hardware specs. I meant what motherboard & processor are you using, how much RAM, what type of drives, etc etc. But it may be irrelevant now that the USB2 controller driver is working as expected.

You did remove the "PCI USB" device that has the Yellow Exclamation Mark from your system with the Device Manager BEFORE you installed NUSB, correct? You need to remove ALL USB devices and ALL "Other devices" with a Yellow Question Mark before you run the .EXE and then when you reboot a driver should have been installed for the USB2 controller. NUSB contains both drivers for Storage Devices and a USB 2.0 controller driver. If it did not work in this case, then something is "abnormal" about your "PCI USB" device - either it does not behave like most USB2 controllers or it is in fact the USB3 controller being detected. What are the specs of the hardware you are using; both your real hardware and the hardware being emulated by VMware?

I have no experience with the particular scenario you are attempting, but I have an idea... Chances are the joystick is attempting to connect to the USB3 or USB2 controller rather than the USB1 controller. First, you need to be sure that you have disabled USB3.0 support to the VM itself, as no USB3.0 drivers exist for Windows 98. Second, it appears you do not have a driver installed for USB2.0 under 98SE. These do exist; download and install NUSB to your Windows 98 VM (BE SURE TO FOLLOW THE INSTRUCTIONS!) and try again. (Or, alternately disable USB2 support to the VM as well and let the system revert to USB1 only.) Then try to install your joystick again. Let us know what happens.