by admin

Драйвер Mass Storage Device Windows 98

Once installed USB mass storage devices should work within Windows 98. Only install these drivers on Windows 98SE where Mass Storage Devices are not working. Version 3 of the drivers includes generic USB 2.0 controller drivers adding USB 2.0 support for computers that support it.

I need to save some files off of my teacher's old computer, but the computer won't recognize any of my jump drives when I put them in there. It continues to say that it can't locate a driver for it.I can't use a CD to save the info because the CD drive won't open; and since the computer still runs on dial-up for internet, I can't update the driver software.Is there any way to get my USB drive working on a Windows 98 computer without connecting to the Internet? I just want to save the files on the Windows 98 computer to transfer them to my Windows 7 computer. I need to save some files off of my teacher's old computer, but the computer won't recognize any of my jump drives when I put them in there. It continues to say that it can't locate a driver for it.I can't use a CD to save the info because the CD drive won't open; and since the computer still runs on dial-up for internet, I can't update the driver software.Is there any way to get my USB drive working on a Windows 98 computer without connecting to the Internet?

I just want to save the files on the Windows 98 computer to transfer them to my Windows 7 computer. Thanks.You Have A Problem.Unlike Windows XP and later versions of Windows, Windows 98 did not come with drivers for USB mass storage devices.Why can't you use dial-up?

People lived with that for quite a while. It's a lot slower than you may be used to, but that's the most straight-forward way to get a driver for your USB device installed on the Win98 box.If you can't (or are not allowed to) use dial-up and can't use the CD drive, does the Win 98 computer have a floppy drive?

And do you have access to another computer with a floppy drive that can connect to the Internet?If all else fails, and assuming that there is a network adapter in the Win 98 box, set up a network connection between the two computers using a crossover cable (a crossover cable has the connectors on the different ends wired differently).The following article should help: (use TCP/IP rather than NetBEUI)If the Win 98 box has no network adapter, you'll have to use a 'direct cable connection' with a serial or parallel cable. You could buy both the software and a cable from which once upon a time was the standard method of transferringfiles between Windows computers. LemP Volunteer Moderator MS MVP (Windows Desktop Experience) 2006-2009 Microsoft Community Contributor (MCC) 2011-2012.

USB 2.0 - unless there's a working driver this looks very dim.2. Usb device authentication - Haven't figured that one out yet.3. Usb device with specific CB/CBI support - in progress but no time frame set.I am attaching the systray usb removal utility on the next thread for testing on win9x platform.

It is intended for windows 95 but has been tested to work on all win9x system. On windows 95, specific device class ID (usb,diskdrive,cdrom) needs to be added to the registry for it to work (included with the utility). Please report any issues with it.RgdsUSBSTR95.EXE: Usb storage driver pack for windows 95 (Beta 1). Here's the systray usb storage removal utility works on all Windows 9X.

Please make some test runs and report any issues.Note: For windows 95, double-click on the.reg file to add Device Class GUIDRgds. Updates 26-DEC-2007.- Major changes to source code to primarily use cfgmgr32 routines.- Workaround an issue of intermittent setupapi failure on win95. It does not occur on win98 and above.- Workaround an issue with excessive memory usage.

Only occurs on win95 due to how setupapi is managed by windows. Updates 5-JAN-2008.- Bugfix: library unload sequence corrected.- Excessive memory usage solved.EJECTUSB.RAR (0103-for historical record - DO NOT USE)EJECTUSB.RAR (0108-for historical record - stable with dll unload bug)EJECTUSB.RAR (0108b - latest stable with bugfix)Edited January 5, 2008 by PassingBy. I need to know, though: what do I do if this doesn't go well? What files/reg keys to delete/modify?Where it is placed & how to remove:1. The driver pack will add usbstor.inf and patched nodriver.inf to the INF directory.2. Storage drivers will be copied to OPTIONSCABS directory.3.

The device removal utility will be placed into SYSTEM directory and a startup ejectusb link will be placed into HKLMSoftwareMicrosoftWindowsCurrentVersionRun4. Device class ID will be added to the registry.5.

To remove from using the drivers again, delete usbstor.inf from the INF directory.6. Remove ejectusb startup link as in #3.7. To remove usbstor driver usage comletely, remove all references to the required VID/PID under USB and all in USBSTOR in the HKLMENUMUSB registry section. Do not remove ROOTHUB entries. Those are for usb root hubs.8.

Remove all driver files as listed in the usbtor.infThe eject/removal utility does not write anything to the registry. It is a beta version systray utility with a close/exit option. It will only show usb devices if it is active, else the list is empty.Rgds. I did some testing.I installed with the batch file. When I plugged in the HDD, it still used the SanDisk drivers, so I thought it didn't help. But then, while uninstalling the drivers, I also deleted the key for 'USB Mass Storage Port'. So I tried again, and this time I could specifiy the driver path.

I just pointed at the Program Files directory I had let the extractor put it at before.Weirdly enough it asked me to reboot after identifying it as 'USB Mass Storage Interface'. After reboot there were two entries for it: the previous one and 'USB Mass Storage Device'. But it still didn't work. Unplugged, plugged it back in, now only 'USB Mass Storage Device' appeared. I took a look at the HDD with my brother's laptop, and it's an NTFS drive. Ack.I tried my USB stick, but it got identified as 'USB Mass Storage Port', and no drive appeared in My Computer. Looking at Control Panel System I saw it had a problem.

I don't remember exactly what I did at this point. I think I deleted the entry in the register, and tried again, and asked me to reboot this time. I said No and saw that the device had a problem. I figured that it was because I hadn't rebooted yet. Rebooted, still no drive, still a problem.At this point I uninstalled the whole package and pointed Windows again at the drivers I got from Nathan Lineback. My USB stick works fine again. Hmmm.Thank you for your effort and feedback.

I have made a quick check and found that the 'USB Mass Storage Port' is a reference to the Cruzer drivers from Nathan's pack. That would mean traces of the previous drivers are still being used by windows.If you can/willing to give it another shot, here's what you can do. Remove all references to the cruzer drivers by deleting all refences to SND95.inf in windowsinfothers.

Search and remove all instances of USBIMW95.sys and USBSTW95.pdr. Remove instances of the usb sticks from the registry or hardware control panel. Reboot first to clear any loaded driver for the usb devices.

Then try out the usb storage drivers.If windows requires a reboot after detection then it can mean one of two below:1. Driver conflict/mismatch.2. Device using unsupported/specific protocol (CB/CBI/Authentication etc etc).(.

I'm still looking for suitable drivers for these protocols.)I have also made changes to the ejectusb utility above. Please use the updated version instead.Rgds. I did some testing.I installed with the batch file. When I plugged in the HDD, it still used the SanDisk drivers, so I thought it didn't help. But then, while uninstalling the drivers, I also deleted the key for 'USB Mass Storage Port'.

So I tried again, and this time I could specifiy the driver path. I just pointed at the Program Files directory I had let the extractor put it at before.Weirdly enough it asked me to reboot after identifying it as 'USB Mass Storage Interface'. After reboot there were two entries for it: the previous one and 'USB Mass Storage Device'. But it still didn't work.

Unplugged, plugged it back in, now only 'USB Mass Storage Device' appeared. I took a look at the HDD with my brother's laptop, and it's an NTFS drive.

Ack.I tried my USB stick, but it got identified as 'USB Mass Storage Port', and no drive appeared in My Computer. Looking at Control Panel System I saw it had a problem.

I don't remember exactly what I did at this point. I think I deleted the entry in the register, and tried again, and asked me to reboot this time.

I said No and saw that the device had a problem. I figured that it was because I hadn't rebooted yet. Rebooted, still no drive, still a problem.At this point I uninstalled the whole package and pointed Windows again at the drivers I got from Nathan Lineback.

My USB stick works fine again.I think you are much better off using for Win95 and ditching PassingBy's USB Storage driver pack, BenoitRen. I've tried using PassingBy's USBSTR95 pack with a Sony Microvault 4GB USB Flash drive I bought back in late July and the drivers won't recognize it. So I remove them and used Nathan's usb storage drivers and those drivers worked with the Sony Microvault 4Gb USB Flash stick. Still, the IOMagic datastation device which is a multi-card reader usb device doesn't work with either Nathan's USB Flash driver or PassingBy's USB Storage driver pack. No big loss though.So I now give PassingBy's Win95 USB Storage Driver pack a grade of D+. NO uninstall option to remove those drivers is another reason why I gave it a low grade.

Universal Mass Storage Driver Windows 98

Lexar usb windows 98 driver

Windows 98 Drivers Download

Edited September 12, 2008 by erpdude8. I have made some preliminary tests of the safely-remove-utility EjectUSB0108b with SDHC card readers and have up to now a positive impression.I have tested EjectUSB0108b together with 4 manufacturer-provided Win98SE drivers for SDHC card readers (for Genesys, Myson Century, Alcor and US Best chips).

2 of these drivers (Genesys and Myson Century) come with their own safely-eject-utilities, and 2 don't (Alcor and US Best).EjectUSB0108b works fine (except for Bug 2, see below) under Win98SE as safely-remove-utility for SDHC card readers with US Best chips.EjectUSB0108b works fine together with other safely-remove-icons in the system tray (i.e. With safely-remove-utilities of drivers of USB mass storage devices which install their own safely-remove-utility): EjectUSB0108b only added a USB mass storage device to its menu list if that device didn't have its own safely-remove-utility. I have tested this with altogether 4 safely-remove-icons in the system tray: the Genesys icon (USB card reader, USB HDD and USB CD/DVD drive), the Systray.exe icon (used by a Myson Century card reader), the JMicron icon (used by a switchable eSATA-USB enclosure for external 750GB HDD with 4 partitions) and the icon of EjectUSB0108b (used by a US Best single-card reader and a US Best multi-card reader at the same time).BUG 1: EjectUSB0108b did not work for an SDHC card reader with an Alcor chip inside, EjectUSB0108b just didn't add the Alcor card reader to its removal menu. Whether this is the fault of EjectUSB0108b or of the Alcor driver, I don't know.BUG 2: When a multi-card reader (4 slots) with a US Best chip inside is connected, the removal menu of the icon in the system tray displays 4 selectable entries:Disconnect i.e. Without a drive letterDisconnectDisconnect N: =last slot/drive letter of multi-card readerDisconnectwhile an SDHC card was inserted into L:, for example.

No cards were inserted in the other slots K,M,N. Clicking on one of the 3 selections without a drive letter will produce the msg: 'Usb storage device cannot be removed'. Clicking on the selection 'Disconnect N:' works ok, with the msg: 'Usb storage device successfully removed'.For multi-card readers there should be only a single menu selection, like 'Disconnect K,L,M,N', as the Genesys safely-remove-utility has (but Genesys has a problem of multiple-drive-letters with multi-card readers). Nusb 3.3 has a very inconvenient menu for multi-card readers: there are 4 entries, one for each slot, and you have to go thru the remove cycle 4 times before you can safely remove a multi-card reader.BUG 3: EjectUSB0108b does not work properly when an SDHC card with multiple partitions is inserted in the card reader: The partitions of the SDHC appear, for example, as K: and L: in My Computer, but the removal menu of EjectUSB0108b only displays one partition (Disconnect K:) Disconnect K:,L: would have been correct. Upon trying to safely-remove K: a msg appears: 'Usb storage device cannot be removed'I hope PassingBy will continue to develop this program; this is the only detached safely-remove-utility for Win98 I know of, for WinXP there are lots.

Edited November 23, 2008 by Multibooter.