EMULAB Forum

clrmamepro [English] => clrmame Discussion => Topic started by: darkfalz on 30 March 2012, 17:33

Title: Weird rebuilder / NTFS bug
Post by: darkfalz on 30 March 2012, 17:33
My ClrMame is kept in a NTFS compressed folder on a portable HD

My MAME ROMs folder is not compressed.

Since going to 7z, when I rebuild, rebuit files (7z) appear in my ROMs folder with NTFS compression on. Is this because they are temp created in the ClrMame folder and then moved to the ROMs folder?
Title: Re: Weird rebuilder / NTFS bug
Post by: Roman on 30 March 2012, 19:18
Ask Windows :)
No joking, cmpro doesn't have any influence on that.
Title: Re: Weird rebuilder / NTFS bug
Post by: darkfalz on 11 April 2012, 15:51
It's definitely due to the temp folder in ClrMamePro being compressed. I tried to make it uncompressed, but it appears that ClrMamePro removes and recreates the folder so it re-inherits the compressed attribute. I can probably monkey around with the security on it so that it can't be deleted, this might fix it.
Title: Re: Weird rebuilder / NTFS bug
Post by: Roman on 11 April 2012, 17:01
why do you actually have a problem with ntfs compression? it does not affect the files within the archives or mame in general...just wondering...
Title: Re: Weird rebuilder / NTFS bug
Post by: Zandro on 13 April 2012, 17:50
Speaking of this temp folder, might there be a way to relocate it, instead of needing to use a junction point? This improves the scan speed a noticeable amount when a ramdisk is used. This of course leads to the argument that I should copy the entire install to the ramdisk, but that is impractical in that not every dat is used in each session, and dangerous because of risk for loss of contents due to forgetfulness and/or powerloss.

Edit: Meh, cmpro deletes and recreates the folder on startup, which makes it manual labor to maintain a junction point. Or a batchfile situation:P

Edit 2: sorry for the edits, thanks for the consideration  :P
Title: Re: Weird rebuilder / NTFS bug
Post by: Roman on 13 April 2012, 19:17
maybe in a future version. I add it to my list
Title: Re: Weird rebuilder / NTFS bug
Post by: darkfalz on 24 April 2012, 22:27
why do you actually have a problem with ntfs compression? it does not affect the files within the archives or mame in general...just wondering...

NTFS compressing already compressed files icurs a small overhead with no actual compression benefit.
Title: Re: Weird rebuilder / NTFS bug
Post by: darkfalz on 24 April 2012, 22:29
Speaking of this temp folder, might there be a way to relocate it, instead of needing to use a junction point?

That would be cool. I keep my collection on an external USB disk, so any extra reading/writing that could be done on the local disk instead would give a marginal speed boost.
Title: Re: Weird rebuilder / NTFS bug
Post by: Roman on 25 April 2012, 15:56
why do you actually have a problem with ntfs compression? it does not affect the files within the archives or mame in general...just wondering...

NTFS compressing already compressed files icurs a small overhead with no actual compression benefit.

But that doesn't play a role when the final zip/7z/rar romset is copied to a drive which is not set to ntfs compression. You may have a minimum overhead in cmpro's temp folder, but the final archive file in its final place is the one we have to care about...and if your partition is not ntfs-compressed, then you don't have this overhead.
Title: Re: Weird rebuilder / NTFS bug
Post by: Roman on 02 May 2012, 20:33
ok...next version got an option to select the temp folder (in cmpro.ini) and decide if it gets initially cleaned.