EMULAB Forum

clrmamepro [English] => clrmame Discussion => Topic started by: Terra_Cresta on 01 November 2011, 17:28

Title: Dir2Dat Limitations
Post by: Terra_Cresta on 01 November 2011, 17:28
Hi Roman,

I'm trying to use Dir2Dat to document a folder containing a) Uncompressed data, b) Subfolders containing some uncompressed data and some zipped data (which I want to dat as a zip only). This seems impossible.... I've tried every permutation of options and whilst the subfolders are datted correctly I either find that those files sitting in the root folder either get datted within a subfolder called "Default" or a folder named after the root folder.

Is this a limitation of Dir2Dat? Ideally, I want to be able to point CMPro at a folder and say "dat that" and create a datfile which exactly mirrors that structure/content (just one folder deep would be good!).

Cheers in advance.... ;-)
Title: Re: Dir2Dat Limitations
Post by: Roman on 02 November 2011, 09:20
Since dir2dat tries to follow the mame set loading and placing rules
(rompath\setname\file 1...file n), the only trick you need to follow is most likely to point to the parent folder of the folder you want to get "datted".
..and enable:
Scan Subfolders
Set-Subfolder Mode

So if you want to collect all files to a dat within folder c:\test\bla (and subfolders), let the dir2dat input point to c:\test...and it will create 1 set named "bla"
Title: Re: Dir2Dat Limitations
Post by: Terra_Cresta on 02 November 2011, 15:28
Yeah, that's helped me out, thanks. Just a PITA to have to manually exclude all other paths before scanning....