INTERACT FORUM

More => Old Versions => Media Center 11 (Development Ended) => Topic started by: sail121j on December 29, 2005, 09:44:52 am

Title: Slow tagging fixed by switching to NTFS on external drive
Post by: sail121j on December 29, 2005, 09:44:52 am
It is taking about 1 minute or longer to do a tag change on a file.  When I add an image to an album and have the option to file the image inside the file checked, the image file location should quickly go from C:\Documents..... to Inside File.  Instead it takes forever to do the tagging.
Title: Slow tagging fixed by switching to NTFS on external drive
Post by: sail121j on December 29, 2005, 12:44:37 pm
UPDATE:

The slow taging is on my second library - the first (default) updates tags quickly - the second library is very slow to update the image tag.
Title: Slow tagging fixed by switching to NTFS on external drive
Post by: sail121j on December 29, 2005, 03:13:13 pm
Final update:
Found the reason for the slow taging - the new library was contained on an external hard drive that was formated in FAT32 - the rest of my computer was NTFS.. Converted the external USB drive to NTFS - problem solved.

Jack
Title: Re: Slow tagging fixed by switching to NTFS on external drive
Post by: JimH on December 29, 2005, 04:49:04 pm
Thanks for reporting the fix.
Title: Re: Slow tagging fixed by switching to NTFS on external drive
Post by: hit_ny on December 30, 2005, 01:58:09 am
Why would NTFS be faster than FAT32 ?

i have both types but don't notice any difference.
Title: Re: Slow tagging fixed by switching to NTFS on external drive
Post by: dNj on December 30, 2005, 05:02:27 pm
Final update:
Found the reason for the slow taging - the new library was contained on an external hard drive that was formated in FAT32 - the rest of my computer was NTFS.. Converted the external USB drive to NTFS - problem solved.

Not sure if that was the true fix.  I have an external that is Fat32 and internal that is NTFS.  My slow tagging problem occured immediately with the new MC11 release, but was fixed with the 11.1 update (sorry don't know exact build #, but it was about 3 updates ago)