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

Pages: [1]
1
clrmame Discussion / Re: Immediately close in linux
« on: 03 January 2014, 20:56 »
you know what, i just realized i made the dat when wine was broken, looking at it now it's a 0 byte file :)

2
clrmame Discussion / Re: Immediately close in linux
« on: 02 January 2014, 19:20 »
Upgrading to Fedora 20 worked (must have been a wine issue)

However, i'm still seeing an issue i saw in windows with 4.12a.  When i load a datfile (on a completely clean cmp install), the datfile loads but i cannot see it.  When i try to add it again it asks if i want to overwrite.  If i make a profile that has the same name as the dat it says name in use.

Where is the datfile?  why is it hidden?

3
clrmame Discussion / Re: Immediately close in linux
« on: 02 January 2014, 16:48 »
Yeah that was the upgrade path, not sure what happened.  i'm upgrading to Fedora 20 right now so we'll see if that changes things, with a newer/different version of wine and all.

4
clrmame Discussion / Re: Immediately close in linux
« on: 02 January 2014, 16:01 »
i can try it in a VM.  BTW this all started with the latest update, all was working fine until then..  I've uninstalled and reinstalled cmp but same issue.

5
clrmame Discussion / Immediately close in linux
« on: 01 January 2014, 23:02 »
Running Fedora 19 32-bit, wine 1.7.5

upon running the cmpro.exe it immediately closes.  only output i get on the screen from running wine ~/.wine/drive_c/Program\ Files\clrmamepro/cmpro.exe is:

Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.

running cmpro.exe 4.012a

Strace file is attached if that helps.

6
News & Communication / Re: clrmamepro 4.05 released
« on: 25 March 2012, 14:36 »
There seems to be an issue with scanning settings.  On the scanner screen, I UN-check CHD, and when I click Scan (not New Scan, so this may be the issue), When the scan starts, CHD is then automatically checked again, thus forcing a CHD scan.

Is this expected behavior?

7
clrmame Discussion / Re: ddr2mla chd placement
« on: 12 May 2011, 21:18 »
Well that did the trick.

Any chance I can submit a feature request to have this as an available action by cmpro?

It already does that with roms,  all it has to do is copy the existing chd to the right spot.

8
clrmame Discussion / Re: ddr2mla chd placement
« on: 10 May 2011, 15:12 »
I agree, but it's in ddr2mla, and i've tried putting it in ddr2ml, and it just moves it back to ddr2mla.  here's an ls output

# ls ddr2*
ddr2mc2.zip  ddr2mc.zip  ddr2mla.zip  ddr2ml.zip  ddr2m.zip

ddr2m:
895jaa02.chd

ddr2mc:
896jaa01.chd

ddr2mc2:
984jaa01.chd

ddr2ml:
885jab01.chd

ddr2mla:
885jaa02.chd


I'm pretty sure this is how it should be, just keep getting the mesage.

9
clrmame Discussion / ddr2mla chd placement
« on: 09 May 2011, 16:18 »
So, for a couple of version now, 142u1 at least till 142u3, clrmame keeps telling me that ddr2mla chd 885jaa02 is missing but fixable.

right now it is in roms/ddr2mla/ and it's not removing it, but I still get the message.

I've tried moving it to roms/ddr2ml/ and roms/ddr2/ but everytime I do it moves it back to roms/ddr2mla/ and still gives me the message.

Please help, thanks in advance.

10
clrmame Discussion / Re: clrmamepro 3.132 released
« on: 12 December 2009, 18:56 »
Alright, well not sure what happened on my end (cause I was using cmpro before the update), but a reboot seemed to fix it.  (also rebooted into a new kernel but i highly doubt that had anything to do with it).

sorry to waste your time.

11
clrmame Discussion / Re: clrmamepro 3.132 released
« on: 12 December 2009, 07:46 »
Not sure what happened but completely dies in wine for version 3.132.   Just updated via the internal update function, .exe fails to run.  Removed via wine and deleted ~/.wine/drive_c/Program Files/clrmame and re-installed via 32-bit .exe and same problem.  winedbg is not working for me for some reason, but otherwise wine with the executable gives no output, just dies. 

Wine version is 1.1.32-1.fc12

Was working before update, same version of wine.

Pages: [1]

Page created in 0.311 seconds with 20 queries.