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 - Terra_Cresta

Pages: [1]
1
clrmame Discussion / Re: Dir2Dat
« on: 09 July 2014, 19:04 »
Quick question: do you know why Dir2Dat randomly seems to choose either Windows or Unix line endings? I can't figure out the pattern of why it does this, though it does seem to favour Unix.

Any idea why? Or it is possible to add option to choose which every time?

Thanks!
@Cass, I know we've gone round the houses several times regarding scene releases and their line feeds changing when people move their NFO/SFVs from server to server (x0d0a/0d) but is there any value in maintaining consistent line feeds for DAT files?

2
clrmame Discussion / Modification Request
« on: 29 April 2012, 11:57 »
Very often when using the batch mode rebuilder I forget to set the "Rebuilder Run Before Scan". Would it be possible to grey out the fields on the rebuilder tab when "No Rebuilder Run" is selected as a visual cue that no rebuilding would be done.

Also, wouldn't it be better to have the "Don't remove rebuilt source" and "Always remove rebuilt source" checkboxes as just a single "Remove rebult source files" checkbox as per the single dat rebuilder window - just for consistency.

Thanks in advance ;D

3
clrmame Discussion / Re: A couple of random requests...
« on: 28 March 2012, 18:26 »
Even reverting the "Missing Sets" and "Missing ROMs" field to "-not scanned yet-" as a way to identify them would be a start.

4
clrmame Discussion / Re: cmpro 4.05 released
« on: 23 March 2012, 15:40 »
fixed: batch rebuilding doesn't care about forcepacking attributes in dats
Yay, cheers Roman!

5
clrmame Discussion / Re: Rebuilder options - batch mode
« on: 16 March 2012, 13:02 »
Yes, that seems to do the trick... no more spurious zip files appearing amongst uncompressed sets! Thanks for the fix....  ;D

6
clrmame Discussion / Rebuilder options - batch mode
« on: 14 March 2012, 22:30 »
Hi Roman,

It would appear that when rebuilding in batch mode that sets are created as zip files regardless of what is specified in the datfile (<clrmamepro forcepacking="unzip"/>) and when no specific rebuild compression settings are applied via the rebuilder tab.

7
clrmame Discussion / Re: Exclude-Paths question ?
« on: 28 November 2011, 12:47 »
Wow! You learn something everyday!

8
clrmame Discussion / Re: Dir2Dat Limitations
« 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....

9
clrmame Discussion / Dir2Dat Limitations
« 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.... ;-)

10
clrmame Discussion / Re: Enhancement request ;-)
« on: 30 July 2011, 11:09 »
Thank you kind sir :)

11
clrmame Discussion / Enhancement request ;-)
« on: 29 July 2011, 23:48 »
Roman,

I've long been a fan of your "Generate HTML Report" option and I reckon not that many people actually use it. In its current form it's not much use as there's no mechanism for getting the .htm file up and out there to the masses.

What I'd like to see is the possibility to specify an FTP target for the function (and have that target saved for future use) or just to set a single target for all generate requests. Also (yeah, yeah!) maybe a single click batch mode to create .htm files for all profiles seperately (not the "All Profiles" option) but to create an .htm file for every profile folder.

Well, you said you had no enhancement requests!

Cheers,
TC

12
clrmame Discussion / Re: Profiler slow to load
« on: 30 November 2010, 21:40 »
If it can help anyone AV software seemed to be the cause. Once the CMPro folder was excluded from scans profiler loads in just a few seconds. :)

Cheers Boss.

13
clrmame Discussion / Re: Profiler slow to load
« on: 29 November 2010, 22:06 »
Hang in there :) I'll post tomorrow morning GMT. It's a 264Mb RAR... just uploading to a file sharing host.

http://www.sendspace.com/file/ynhy3a

14
clrmame Discussion / Profiler slow to load
« on: 27 November 2010, 17:53 »
On initial application start-up and periodically during use the profiler takes an inordinate amount of time to complete the "looking for datfiles" process. Admittedly, I have quite a few datfiles but for the most part this seems to be cached and seems to complete quite quickly.

It was pretty slow pre 3.137 but I thought it was just due to the sheer number of datfiles present. 3.137 seems to *add* something which makes the process slower taking up to four minutes to complete the "looking for datfiles" bit.

Is it a case of - to quote Bruce Hornsby - "That's just the way it is"?

15
clrmame Discussion / Dir2Dat Problem
« on: 13 September 2010, 07:36 »
Moin Roman,

Seems that whenever I use dir2dat I end up with "<manufacturer></manufacturer>" beside every game regardless of whether "Add Manufacturer" is checked or not.

Cheers ;-)

16
Ah, I assume you're speaking of "Adv_AllowRestart = on" which did the trick. Many thanks.

17
Roman,

I'm using the latest version under Windows 7 64 bit and often when I quit the application it remains active. Any attempt to relaunch causes a "The program is still running!" error message. Nothing shows up in Task Manager and a reboot is the only solution.

I suspect as no one else has reported this it might not actually be CMPro at fault.

Thanks in advance.

Pages: [1]

Page created in 0.085 seconds with 20 queries.