Hello David, What type of network do you use? David C. Rankin wrote:
Dev, all;Since 2.0 was released, we have been battling a file save/copy problem from XP guest OS to any Linux/Samba network server. The problem has been a horribly slow data transfer rate XP guest --> Samba Server. The transfer the other way has been perfect. Today I downloaded 2.2 eager to see if the problem was solved. First I tried to download the clamwin update (6 Meg.) from within the XP guest to the samba share. The download finished (to the local windows temp file), then the file copy dialog appeared for copy of the file from XP guest to the samba share. The file copy dialog *stalled*, as it has since 2.0 was released and after several minutes reported that the samba drive was no longer available and died. I then re-downloaded the file to a directory on the XP guest and installed. I then modified the samba server to re-enable comm over port 443 to see if that made any difference. I attempted the copy again and was presented with the "File Already Exists" dialog -- Huh? WTF? Checking the destination -- sure enough, the first download and copy had been successful, but it was just something with XP running as a guest that thought the transfer was stalled or had failed. I then tried another test copying the same file from the XP guest back to another directory on the server to test if enabling port 443 helped. Nope, XP as a guest bombed saying the transfer failed and that the drive was no longer available. I then checked the file location on the server and confirmed that the transfer really had taken place just fine?? So --- I hope this helps narrow down where the bug in VB is concerning copy/save to a smb share. Now I can confirm that it isn't with the actual copy, but in VB's perceived response to the copy.
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
