Usually I don't eject the plug until computer is completely down. Whe it was packet out, still it seemed to 'accept' lot of data, but this was late rnot found on the stick and fat32 partitions on the pc had damage. Only w98se tried, that was it, the faked fat is gone, the partiton table or what ever too, it also no mire possible to communicate with it. From the chip size I assume this is 1gb chip and the faked partition table was written into it somehow and present day OS refused to format it. Opening the stick showed only the controller and one mem chip soledred by hand and label filed apparently off. W98se with universal usb driver was the only one able to format such usb stick, but it ended up in the stick being unusable. W2k system finaly crashed and hat to be restored compltely from image file. This damage did not only restricted to the actual files copied, but other parts also. The NTFS partitions survived, but those having fat32 lost files, folders, scandisk found later lot of chk files. Thought I do not understand details fully yet, but recently I had bad experiencies with some 'faked' usb sticks.įriend bought some sticks of 16gb for 74 USD! Well this should be warning enough, but when I tested them on some systems including w2k, w98se, xp, I found that copying larger amouts of data to it, or better say try to copy, did lot of damage on the host system as well. There is a German language forum, in case it might be more comfortable to explain the situation that way. An underpowered USB port or other electronic problem could do the same thing.Īre you able to replicate the file damage with a particular activity - just starting TBP, compacting a folder, sending a message? Or is it a relatively random behavior? I'd guess that pulling the plug while the program is trying to write a file might result in the file being in an indeterminate state doing it while Windows was re-writing a directory entry might result in the directory being messed up. When run on a slower medium, the portable programs take a long time to close down and clean up (compared to faster internal drives). Well, I suppose an obvious question might be, are you waiting for the program to shutdown before ejecting? Are you using an eject script, or just pulling out the plug? Have you enabled write caching? Was journaling enabled when you tried NTFS? Does it happen when the USB drive is plugged into the back of the machine as well as the front ports?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |