Remember me

Lost Password?

Register now!
Who's Online
42 user(s) are online (10 user(s) are browsing Forums)

Members: 0
Guests: 42

Support us!
Recent OS4 Files
Report message:*

Re: usb 16go key copy problem on SAM and AOS4.1 U1 (now)

Subject: Re: usb 16go key copy problem on SAM and AOS4.1 U1 (now)
by robo-ant on 2010/2/25 17:05:45


What mean your before AOS4.1, FAT95 failed allways ??? I don't understand really the before and after AOS4.1U1 explanation.

FAT32 USB volumes used to get read errors for me, with the OS4.1 beta (SAM). It was dangerous to copy files _from_ a USB stick. Now with OS4.1u1 I have successfully copied many, and large, files from USB media, with no errors.

With either version of the OS, it seems dangerous to copy files _to_ a FAT32 USB device.

Note that the small file I copied last night was named simply "files.md5", so no special characters or long filenames were involved.


What look like the write error requester ???

Um, a normal system requester, I guess. I didn't pay that much attention to what it looked like, and I couldn't get a grab of it because Workbench was locked-up.

It said there was a write error on some block with a big number that I didn't write down.


You copied things with a filemanager (dopus4) ???

Nope. I dragged the file to the volume using Workbench.


The USB reset during the copy (USB mouse and keyboard) ???

I don't know if USB reset during the copy. I have a SAM440EP so I have to use USB mouse and keyboard. The mouse was still working after the error. Workbench was locked-up and I didn't have anything I could type into, so I don't know if the keyboard was still working.

Also, I don't have any USB hubs connected, or anything like that. Apart from the mouse and keyboard, the USB stick was the only USB device connected to the SAM.

I use this same USB stick with Windows all the time, and occasionally with Linux, and I haven't experienced a problem with it on those operating systems.
Powered by XOOPS 2.0 © 2001-2014 The XOOPS Project