Unfortunately, I discovered that the change from auto to vfat was not the solution to the problem. I don't like **magic** or things that seem to happen for no reason. There's always a reason - we just have to find it.
After my previous message (about an hour ago), I decided to play with the device again before returning it to my friend tomorrow. I was again not able to save data. In fact, the situation was even worse. I could no longer even mount the device. I checked fstab and found that the /dev/sda1 entry was gone. I can only guess that kudzu periodically checks and updates fstab (maybe a cron job - I didn't check). I added the /dev/sda1 entry manually and was able to mount and read data but again couldn't save data (using auto or vfat). I then went to the **extreme** of re-booting and spoiling my uptime ;-) a few times with and without the device in the USB plug. What I discovered is that the device seems to work as expected **out-of-the-box** the first time only, regardless of whether I boot with the device in the plug or plug it in after booting. What I mean is that without changing from auto to vfat, I can read and write on the device. But if I umount, remove the device from the plug and them plug it in and try again, I can no longer save data. BTW - I have no idea why the change from auto to vfat worked yesterday. I didn't boot and it obviously wasn't the first time I'd plugged in the device, since as you all know, I'd been trying several suggestions that didn't work before making the auto to vfat change :-( -- Shlomo Solomon http://come.to/shlomo.solomon Sent by KMail (KDE 3.1) on LINUX Mandrake 9.1 ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
