EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - RainyShadow

Pages: [1]
1
clrmame Discussion / Re: Runtime error
« on: 28 June 2013, 22:09 »
This build works fine. Thanks.

2
clrmame Discussion / Re: Runtime error
« on: 28 June 2013, 21:26 »
Sure.
I forgot that this dat uses header skipping, now it makes sense.
I just tried with your header xml - same issue.

3
clrmame Discussion / Runtime error
« on: 28 June 2013, 18:46 »
I get a MS VC++ runtime error when rebuilding with the attached dat file and the source folder contains a zipped zero-size file.

4
This build handles junctions fine according to my quick test.
I created two junctions - one pointing to an empty folder and one pointing to a non-empty folder. Then i used their parent as a rebuilder source and tried all combinations of the above mentioned two options.
The result - only the junction pointing to the empty folder was deleted, and it required both options enabled. The other junction remained after all three rebuilds.
Success!

Thank You!

P.S. i could test only the 32bit binary as my system doesn't support x64.

5
Junctions???? What do you mean exactly?
Junctions are the NTFS equivalent of symbolic links. With these you can have i.e. a folder containing all roms/movies/etc. from all your hard drives in a single place; or you can replace a non-movable folder (Quicktime cache, browser cache, etc.) with a junction to a folder on another drive... You can find some information on http://en.wikipedia.org/wiki/NTFS_junction_point
I use KillCopy to create them as WinXP comes with only a command line utility (fsutil.exe) to manipulate such links. There are some other alternative programs available as well - NTFSLink, Junction Link Magic and others.
The rebuilder reads files (or files within an archive) from a given source, checks the hash values against the database and creates any found match of it in the destination and uses the correct naming. If you got "remove rebuilt files" enabled, it deletes the file from the source (archive) and if the archive or folder is empty after this it gets removed, too (however there is a rebuilder advanced option which allows you to remove empty folders or not).
I am aware of the "Remove Matched Sourcefiles" and "Remove empty sourcefolders" options, and i use them when appropriate. The issue surfaces if there are junctions in the source - they get removed regardless if they point to an empty folder or to a folder full of roms. So, if i go through several CMP profiles and rebuild from that source, only the first one would receive the matched roms from the junction folder.
I noticed something which may be related - the properties of a folder containing a junction don't count the junction target in size calculation. Here is an example folder structure:
C:\ROMs
C:\ROMS\FBA_roms   < a junction to D:\FBA\ROMs
Now, if you right-click C:\ROMs and select "Properties", it would show 0 in the "Size" field (Windows Explorer bug?).
If you do the same for C:\ROMS\FBA_roms it would properly show the size of the D:\FBA\ROMs folder.
Maybe Clrmamepro is affected by the same bug and considers the junction as an empty folder, so it is removed when the above two options are enabled.

HTH

6
I have several HDDs in my system, so i make heavy use of junction points to organize my files.
Also, i usually dump various roms in my backup (junk) folder and use it as source for rebuilding.
What i noticed is that, when i create a junction to a roms folder  in my backup folder, it gets deleted after a rebuild as if it was an empty folder.
I think the proper handling would be to delete the junction only when its target folder is really empty.

CMP v4.09a
WinXP SP3

Pages: [1]

Page created in 0.17 seconds with 20 queries.