If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Problem with writing/updating to a 32 GB USB stick.
Hello all,
I've got a problem with accessing a 32GB FAT32-formatted USB stick. Although reading from it seems to go fine, either writing big or many files to it causes the computer to freeze hard (forcing a hard reset). 8GB sticks have always worked fine (never had or used 16GB sticks). Does anyone know why this happens and how to fix it. Extra info: Some years ago I did install some generic USB device driver (NUSB 3.3). Regards, Rudy Wieser P.s. I just saw "98 Guy" mention NUSB 3.6 which I'm willing to try _if_ there is an indication that it would solve the described problem. |
#2
|
|||
|
|||
Problem with writing/updating to a 32 GB USB stick.
"R.Wieser" wrote:
I've got a problem with accessing a 32GB FAT32-formatted USB stick. Although reading from it seems to go fine, either writing big or many files to it causes the computer to freeze hard (forcing a hard reset). 8GB sticks have always worked fine (never had or used 16GB sticks). Does anyone know why this happens and how to fix it. If you have access to a win-7 machine, then the first thing to try is plug the stick into the win-7 machine and see if you get any messages like "the drive is messed up" or need to be repaired. If not, then get the properties on the stick and make sure its formatted as FAT32 and not Exfat or ntfs. Beyond that, I know I have issues sometimes plugging in a thumb drive into the chassis-mounted USB port on my win-98 system. This looks like a bad or intermittent contact issue. Sometimes plugging in the stick half way (or just short of all-the-way) makes the difference between Win-98 seeing or not seeing the stick. |
#3
|
|||
|
|||
Problem with writing/updating to a 32 GB USB stick.
98 Guy,
then the first thing to try is plug the stick into the win-7 machine and see if you get any messages like "the drive is messed up" or need to be repaired Not an idea I will follow easily. I've got a small (2GB) stick here which has _served me for years without a problem_, but a friends Win7 machine always wants to "repair" it. It does not think its in any way necessary to tell us _what_ is wrong, so I always decline. make sure its formatted as FAT32 Well, I could read from it without a problem. And althoug I did not explicitily mention it, it also had no problem when I copied a few smaller files onto it (or when I created a number of folders and subfolders). I also (re-)formatted it on an XP machine (tried to create multiple partitions. But although I've got an USB-attached PATA drive (yep, old) which works that way, it refuses when I try to do that with the stick), making sure I did chose FAT32. Just checked again. Yup, properties shows its FAT32 alright. Beyond that, I know I have issues sometimes plugging in a thumb drive into the chassis-mounted USB port on my win-98 system. I was always able to read from it, never noticed a hitch. But I can try a few other ports I guess. Maybe even the USB v1.1 ones. :-) I would rather not use those to fill up the stick though ... Regards, Rudy Wieser -- Origional message: 98 Guy schreef in berichtnieuws ... "R.Wieser" wrote: I've got a problem with accessing a 32GB FAT32-formatted USB stick. Although reading from it seems to go fine, either writing big or many files to it causes the computer to freeze hard (forcing a hard reset). 8GB sticks have always worked fine (never had or used 16GB sticks). Does anyone know why this happens and how to fix it. If you have access to a win-7 machine, then the first thing to try is plug the stick into the win-7 machine and see if you get any messages like "the drive is messed up" or need to be repaired. If not, then get the properties on the stick and make sure its formatted as FAT32 and not Exfat or ntfs. Beyond that, I know I have issues sometimes plugging in a thumb drive into the chassis-mounted USB port on my win-98 system. This looks like a bad or intermittent contact issue. Sometimes plugging in the stick half way (or just short of all-the-way) makes the difference between Win-98 seeing or not seeing the stick. |
#4
|
|||
|
|||
Problem with writing/updating to a 32 GB USB stick.
What I've discovered on 98 is that NUSB 3.6 is stuck in non-support mode and for the most part can't even be found anymore for download. Some evidence that 3.3 was better anyway, I have nothing to say that it is. What I do have to say is that 3.6 failed to install the most important part.. That would be the part that shows up in the system tray when you insert a USB drive and just like in XP, it does not go away until you click on it and make it OK to remove the drive. If this process isn't followed you have just borked your USB drive most likely. And all it takes is one unauthorized removal. Of course YMMV here, best of luck there too. R Loew has some USB files for free and in his method one places the tray app in the system folder and a shortcut to it in the startup folder manually so that it runs every time windows does. THIS is what 3.6 fails to do, it fails to run the overlord app. The one that makes it OK to remove the drive. The one that smells your USB port and fires up when you do insert a USB drive, just like in XP. I would far more trust Win7's opinion on a flash drive's health than a seat of the pants evaluation such as 'works fine'. Thanks 98 guy, I'll put that tip to work the very next time I use a USB drive. |
#5
|
|||
|
|||
Problem with writing/updating to a 32 GB USB stick.
Lee,
I would far more trust Win7's opinion on a flash drive's health than a seat of the pants evaluation such as 'works fine'. Well, that "seat of the pants" evaluation is exactly that: an _evaluation_ of it having worked well for years . Win7's "opinion" is based on ... what exactly ? If a mechanic tells you your car needs to be repaired, but does not bother to inform you what the problem is or what the end result would be, would you allow him to just do it ? I certainly would not (heck, I would instantly distrust the guy). Some day I might just backup that stick, let Win7 "have its way" and than do a compare to see what it actually "repaired". Regards, Rudy Wieser |
#6
|
|||
|
|||
Problem with writing/updating to a 32 GB USB stick.
Lee wrote:
What I've discovered on 98 is that NUSB 3.6 is stuck in non-support mode and for the most part can't even be found anymore for download. Are you knocking 3.6 because it's "not supported" ? And 3.3 IS supported? One of the files installed by NUSB 3.6 is usbccgp.sys, which is the "USB Common Class Generic Parent Driver" and comes from Win-XP SP3. I posted the following here in 2014. Maybe it provides some answers or new information. I don't know if any of the links work. If anyone wants any of these files - ask me. And remember, you need to wipe quite a bit of your existing USB stuff out of your device manager before you install NUSB. You might even have to start your computer in safe mode when you go into device manager - you typically see stuff in Device Manager when you're in safe mode that you don't see when you've booted normally. ------------------------- Maximus-Decim Native USB Driver (also known as NUSB). Last version is 3.6. Can be downloaded from he http://www.tmeeco.eu/Fileden/nusb36e.exe NUSB 3.6 supports only mass storage devices, but some composite devices were added since version 3.3. No scanners or printers are supported. The "native" in this name of this driver means that a "generic/universal" driver is provided for Mass Storage Devices, as opposed to original win-98SE which requires each USB Storage device to have it's own manufacturer-provided driver. To install NUSB 3.6, you should remove ALL entries for ALL USB connected devices (including entries under "Universal Serial Bus controllers," "Disk drives," "Storage devices," and any others, including Printers in your case) while running win-98 in Safe Mode. Order of their removal is not important, just be sure you remove them all. Then reboot the machine. Unpon rebooting, Bypass/Cancel any driver installation requests, and when the Desktop has loaded, check the Device Manager to see that none of the USB devices have returned. If they have, remove them, then install NUSB 3.6. You will be prompted to reboot for the new drivers to be installed. ----------------- If you have a VIA chipset (or otherwise have a USB controller made by VIA) on your motherboard, then you might benefit from a driver install package distributed as VIAUSB2.ZIP, which contains these files: USBEHCI.SYS VIA EHCI Miniport Driver USBHUB20.SYS VIA USB 2.0 HUB Driver USBPORT.SYS VIA USB 2.0 Port Driver This is a VIA USB 2.0 driver stack which replaces the Microsoft Windows 2000 USB 2.0 stack that is installed by Maximus-Decim NUSB and the Unofficial Service Pack on systems that have VIA chipsets and have problems using the Microsoft files. It will overwrite the Microsoft files installed by NUSB in C:\WINDOWS\SYSTEM32\DRIVERS and C:\WINDOWS\OPTIONS\CABS without prompting. This package is intended for use with NUSB and the USP ONLY. It can be downloaded from he http://filepost.com/files/7e69334a/VIAUSB2.ZIP/ ------------------- The previous version (3.3) of NUSB contained two "Driver Stacks." One driver stack is for USB Mass Storage Devices. The other was for USB 2.0 hardware (controllers/ports/hubs). Windows 98SE does not have a "Driver Stack" for either of these types of hardware "out of the box." USB Storage Drivers, USB2.0 Hardware Drivers, and the USB 1.1 Hardware drivers that do come with 98SE are three separate entities. Each of these does a different job. The difference with NUSB 3.6 is that it also updates the USB 1.1 Hardware drivers to the Windows ME versions. The "USB Storage Drivers" and the USB 2.0 Hardware Drivers are all the same as before. Updating the USB 1.1 files allows for the use of more "USB Composite Devices" on some machines and in certain configurations. USB composite devices are ones that have more than one function but use a single USB port. The most common USB composite devices are printer/scanner/copier/FAX machines that also include a Type A USB port and/or a memory card reader. NUSB should support memory cards and USB Mass Storage devices connected through such multifunction devices or MFD's. USB keyboards that have built-in hubs and/or card-readers are also composite devices. And they get even more "composite" when one connects a USB mouse through such a hub. Win 98SE and ME support both USB mice and keyboards natively, as "HID" devices, and cooperates nicely with NUSB, so that those input devices (or Human Interface Devices) are also supported, but that's not due to NUSB. NUSB 3.6 also expands the compatibility with some types of HID devices So NUSB 3.6 contains THREE "Driver Stacks," each independent and for different hardware devices. Drivers for USB 1.1 and USB 2.0 ONLY provide support for devices INSIDE your machine, not External devices. The only External Devices supported are USB Mass Storage Devices. |
#7
|
|||
|
|||
Problem with writing/updating to a 32 GB USB stick.
"R.Wieser" wrote:
plug the stick into the win-7 machine and see if you get any messages like "the drive is messed up" or need to be repaired Not an idea I will follow easily. I've got a small (2GB) stick here which has _served me for years without a problem_, but a friends Win7 machine always wants to "repair" it. It does not think its in any way necessary to tell us _what_ is wrong, so I always decline. A few things can go screwy with drive volumes, descriptor tables, MBR, etc. One thing that gets messed up is the tally of free space. It wouldn't hurt to format the drive once in a while. Thumb drives have limited number of write-cycles (the flash ram cells can burn out). Formatting might tell you that the drive has some "bad sectors". Let win-7 fix it. Take a copy of all the important stuff on it first if you must. |
#8
|
|||
|
|||
Problem with writing/updating to a 32 GB USB stick.
98 Guy,
And remember, you need to wipe quite a bit of your existing USB stuff out of your device manager before you install NUSB. I read, but never understood that. Do you know any *reason* for that ? I mean, if other USB drivers can be installed at the same time, why can't NUSB also be ? To be honest, I just took that as a "if you want our driver to service all your USB devices, you need to remove the old ones". But than what is the need to do that *before* NUSB, and not just delete a driver when you want, and have NUSB detect the device the next time. Drivers for USB 1.1 and USB 2.0 ONLY provide support for devices INSIDE your machine, not External devices. The only External Devices supported are USB Mass Storage Devices. Huh ?? How would NUSB be able to tell if it would be talking to an internal or external device (like an USB HUB)? ... I get the feeling you ment something a bit different than "internal" vs "external", but am not sure how ... Regards, Rudy Wieser -- Origional message: 98 Guy schreef in berichtnieuws ... Lee wrote: What I've discovered on 98 is that NUSB 3.6 is stuck in non-support mode and for the most part can't even be found anymore for download. Are you knocking 3.6 because it's "not supported" ? And 3.3 IS supported? One of the files installed by NUSB 3.6 is usbccgp.sys, which is the "USB Common Class Generic Parent Driver" and comes from Win-XP SP3. I posted the following here in 2014. Maybe it provides some answers or new information. I don't know if any of the links work. If anyone wants any of these files - ask me. And remember, you need to wipe quite a bit of your existing USB stuff out of your device manager before you install NUSB. You might even have to start your computer in safe mode when you go into device manager - you typically see stuff in Device Manager when you're in safe mode that you don't see when you've booted normally. ------------------------- Maximus-Decim Native USB Driver (also known as NUSB). Last version is 3.6. Can be downloaded from he http://www.tmeeco.eu/Fileden/nusb36e.exe NUSB 3.6 supports only mass storage devices, but some composite devices were added since version 3.3. No scanners or printers are supported. The "native" in this name of this driver means that a "generic/universal" driver is provided for Mass Storage Devices, as opposed to original win-98SE which requires each USB Storage device to have it's own manufacturer-provided driver. To install NUSB 3.6, you should remove ALL entries for ALL USB connected devices (including entries under "Universal Serial Bus controllers," "Disk drives," "Storage devices," and any others, including Printers in your case) while running win-98 in Safe Mode. Order of their removal is not important, just be sure you remove them all. Then reboot the machine. Unpon rebooting, Bypass/Cancel any driver installation requests, and when the Desktop has loaded, check the Device Manager to see that none of the USB devices have returned. If they have, remove them, then install NUSB 3.6. You will be prompted to reboot for the new drivers to be installed. ----------------- If you have a VIA chipset (or otherwise have a USB controller made by VIA) on your motherboard, then you might benefit from a driver install package distributed as VIAUSB2.ZIP, which contains these files: USBEHCI.SYS VIA EHCI Miniport Driver USBHUB20.SYS VIA USB 2.0 HUB Driver USBPORT.SYS VIA USB 2.0 Port Driver This is a VIA USB 2.0 driver stack which replaces the Microsoft Windows 2000 USB 2.0 stack that is installed by Maximus-Decim NUSB and the Unofficial Service Pack on systems that have VIA chipsets and have problems using the Microsoft files. It will overwrite the Microsoft files installed by NUSB in C:\WINDOWS\SYSTEM32\DRIVERS and C:\WINDOWS\OPTIONS\CABS without prompting. This package is intended for use with NUSB and the USP ONLY. It can be downloaded from he http://filepost.com/files/7e69334a/VIAUSB2.ZIP/ ------------------- The previous version (3.3) of NUSB contained two "Driver Stacks." One driver stack is for USB Mass Storage Devices. The other was for USB 2.0 hardware (controllers/ports/hubs). Windows 98SE does not have a "Driver Stack" for either of these types of hardware "out of the box." USB Storage Drivers, USB2.0 Hardware Drivers, and the USB 1.1 Hardware drivers that do come with 98SE are three separate entities. Each of these does a different job. The difference with NUSB 3.6 is that it also updates the USB 1.1 Hardware drivers to the Windows ME versions. The "USB Storage Drivers" and the USB 2.0 Hardware Drivers are all the same as before. Updating the USB 1.1 files allows for the use of more "USB Composite Devices" on some machines and in certain configurations. USB composite devices are ones that have more than one function but use a single USB port. The most common USB composite devices are printer/scanner/copier/FAX machines that also include a Type A USB port and/or a memory card reader. NUSB should support memory cards and USB Mass Storage devices connected through such multifunction devices or MFD's. USB keyboards that have built-in hubs and/or card-readers are also composite devices. And they get even more "composite" when one connects a USB mouse through such a hub. Win 98SE and ME support both USB mice and keyboards natively, as "HID" devices, and cooperates nicely with NUSB, so that those input devices (or Human Interface Devices) are also supported, but that's not due to NUSB. NUSB 3.6 also expands the compatibility with some types of HID devices So NUSB 3.6 contains THREE "Driver Stacks," each independent and for different hardware devices. Drivers for USB 1.1 and USB 2.0 ONLY provide support for devices INSIDE your machine, not External devices. The only External Devices supported are USB Mass Storage Devices. |
#9
|
|||
|
|||
Problem with writing/updating to a 32 GB USB stick.
98 Guy,
A few things can go screwy with drive volumes, descriptor tables, MBR, etc. True. But those would cause rather obvious problems, like getting garbage back when browsing the stick. And as that does not seem to happen ... One thing that gets messed up is the tally of free space. Agreed. But its also nothing that will cause a problem (and thus *most* be repaired) if you leave it as it is (should get re-calculated / gets messed-up the next time you add or delete something anyway). Let win-7 fix it. Nope. I have *no* idea what Win7 thinks "fixing" means, and it refuses to inform me. For all I know it could muck-up the stick so bad that it won't function properly anymore, or not properly under Win98se. Hmmm... Now I think of it, after the last time the stick caused trouble on my W98se machine I thought it better to reformat it (had to do a few scandisks and repairs on the stick). And yes, I did that on the XP machine. :-) And by the way, this night I had my W98se machine copy a series of files to the reformatted, empty stick, using USB 1.1 . It was able to copy over 3500 files and folders before the machine froze hard -- nice sight, a fully black screen with only the mousepointer visible on it. (a quick shows a few randomly-selected files to be alright). Regards, Rudy Wieser -- Origional message: 98 Guy schreef in berichtnieuws ... "R.Wieser" wrote: plug the stick into the win-7 machine and see if you get any messages like "the drive is messed up" or need to be repaired Not an idea I will follow easily. I've got a small (2GB) stick here which has _served me for years without a problem_, but a friends Win7 machine always wants to "repair" it. It does not think its in any way necessary to tell us _what_ is wrong, so I always decline. A few things can go screwy with drive volumes, descriptor tables, MBR, etc. One thing that gets messed up is the tally of free space. It wouldn't hurt to format the drive once in a while. Thumb drives have limited number of write-cycles (the flash ram cells can burn out). Formatting might tell you that the drive has some "bad sectors". Let win-7 fix it. Take a copy of all the important stuff on it first if you must. |
#10
|
|||
|
|||
Problem with writing/updating to a 32 GB USB stick.
On Wed, 25 Jan 2017 09:44:11 +0100, "R.Wieser"
wrote: I read, but never understood that. Do you know any *reason* for that ? I mean, if other USB drivers can be installed at the same time, why can't NUSB also be ? To be honest, I just took that as a "if you want our driver to service all your USB devices, you need to remove the old ones". But than what is the need to do that *before* NUSB, and not just delete a driver when you want, and have NUSB detect the device the next time. This is the reason I have never tried NUSB. I have years of drivers installed into Win98, and I am not about to screw up my whole system to satisfy NUSB. (Yea, I know I could clone 98 to a spare HDD and screw up the clone), but it just seems like a lot of trouble for nothing. If NUSB did not develop their software to be compatible with other drivers, then it's poorly written crap, which I want no part of. |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Booting Problem....Stick on an Update trying to finish | Bubey | Software & Applications | 3 | April 24th 07 11:47 AM |
Error writing to lpt | S.Forest | Printing | 0 | October 20th 05 12:55 AM |
Something keeps writing to the disk? | Family Man | Setup & Installation | 7 | February 26th 05 06:05 PM |
How to Change Writing on a CD | Jo Wright | Software & Applications | 1 | August 18th 04 06:16 PM |
cd writing | General | 4 | July 1st 04 06:05 PM |