INTERACT FORUM

More => Old Versions => Media Center 11 (Development Ended) => Topic started by: jgourd on October 14, 2003, 08:22:34 am

Title: Renaming Files to a new location messes up sharing.
Post by: jgourd on October 14, 2003, 08:22:34 am

After ripping I use the Library tool "Rename Files From Properties". I often times change the drive letter thus forcing the file to move from one drive to another. The location where I place these files has a share so I can access them from anywhere in the house.

The problem is that the files are corrupt in some very subtle way. If I try to access the renamed files from a remote computer I am told that the files are locked and in use. If I go to the machine where they reside all is good. I have been able to fix the problem by removing the offending files and then copying them back using explorer instead of MC9.

Weird huh?

Title: Re:Renaming Files to a new location messes up sharing.
Post by: Matt on October 14, 2003, 08:42:15 am

That's strange.  If you restart the computer, are they still "locked or in use"?

Can anyone else recreate this?

Thanks!

Title: Re:Renaming Files to a new location messes up sharing.
Post by: jgourd on October 14, 2003, 10:32:48 am

No, restarting doesn't help. It happened last week. I was dumbfounded as to why it was happening. When I used the XP Eplorer to move my collection to a temp location and back again all problems were fixed.

This morning I got the same problem again, only it was only on files that I had used the Rename tool on. I'll try and experiment where I rename to the same location and then use the "Copy/Move" file option.

I recall seeing in a Java Article that renaming files to new locations was considered bad form and was not recommended on the Win32 platform. I know that my company rewrote their file move methods to not use the rename function a whole bunch of weird file system issues went away.

Title: Re:Renaming Files to a new location messes up sharing.
Post by: Matt on October 14, 2003, 10:48:12 am

All move / copy operations in MC use the standard SHFileOperation, which should be the same system that Window Explorer is using.

Can anyone else reproduce this or is anyone aware of hitches with SHFileOperation in this case?

Thanks for any help.

Title: Re:Renaming Files to a new location messes up sharing.
Post by: jgourd on October 14, 2003, 11:07:37 am

Here may be the wrench. My music is located on E:\Music\ogg. I download tunes to E:\downloads\alt.binaries.Sounds ogg. The wrench may be coming from the fact that I SUBST E:\Music to Z:.

I rename from the E:\down... location to Z:\ogg. It is possible that the files being on the same physical disc but a different logical path is part of the problem.

I share the E:\Music folder and connect to it as mapped drive Z: on remote machines. The idea behind the subst is that I want the master DB to use the same driver letter and path as the clients. This way I can backup my db and restore it on other machines and all the paths point to the correct files.

I know, why not just use the Media Server? Because my kid can't burn CDs from Media Server tracks.