I'm using Vegas 5.0 on a machine running Windows 2000 (and all the other machines in the shop, as noted below--except of course for the NAS device) are also running Windows 2000. All of the latest updates are installed, for both Vegas and Win2K.
So being the diligent computer user that I am, I'm backing up my files to my server by dragging the entire project folder over to the Explorer window for the file server/NAS device/other machine on the network (yes, I've tried all variations). I've noticed a pattern--every time Windows gets to [projectname].veg or [projectname].veg.bak in the copy process, I get a dialog box with an error message: "Cannot copy [projectname]: The specified network name is not available."
I've tried it with different [projectname]s, changing the *.veg extention to something else, copying to different machines, cutting and pasting vs. dragging and dropping...same result. If, after the error, I want to copy a different type of file to the network, no problem. It ~appears~ as though ~something~ is blocking these Vegas files ~only~ from travelling on my network. Which would be fine if it were completely consistent.
But here's the wierd thing: If I refresh the network connection, then drag and drop the vegas files one by one, without copying them in a drag and drop 'batch', it works just fine.
Has this ever happened to anyone else out there? Or don't y'all do backups? ;)
Thanks in advance,
dan
So being the diligent computer user that I am, I'm backing up my files to my server by dragging the entire project folder over to the Explorer window for the file server/NAS device/other machine on the network (yes, I've tried all variations). I've noticed a pattern--every time Windows gets to [projectname].veg or [projectname].veg.bak in the copy process, I get a dialog box with an error message: "Cannot copy [projectname]: The specified network name is not available."
I've tried it with different [projectname]s, changing the *.veg extention to something else, copying to different machines, cutting and pasting vs. dragging and dropping...same result. If, after the error, I want to copy a different type of file to the network, no problem. It ~appears~ as though ~something~ is blocking these Vegas files ~only~ from travelling on my network. Which would be fine if it were completely consistent.
But here's the wierd thing: If I refresh the network connection, then drag and drop the vegas files one by one, without copying them in a drag and drop 'batch', it works just fine.
Has this ever happened to anyone else out there? Or don't y'all do backups? ;)
Thanks in advance,
dan