21
General / Re: Imame4all + Mame4ios on ipad
« on: 31 January 2013, 09:34 »
Looking at the website. MAME 0.139. All the info that I have.
- 24 April 2024, 22:41
- Welcome, Guest
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.
22
clrmame Discussion / clrmamepro > mess64 > all softwarelist checked > missing n64dd < not listed.
« on: 31 January 2013, 09:15 »
Any reason why this didn't get loaded with the rest? I can load it alone without a problem as a n64dd.xml file.
Uploaded with ImageShack.us
Uploaded with ImageShack.us
23
clrmame Discussion / Re: I have a question on this.
« on: 30 December 2012, 13:24 »
Using the one from the UME. I switch to this. It have MAME and MESS together. I didn't find any issues at all. =)
24
clrmame Discussion / Re: I have a question on this.
« on: 29 December 2012, 21:18 »
OK I found a real problem.
mess64 -listxml >mess64.xml
clrmamepro wasn't able to read it. Ton of 0 popping up saying it is not read able.
But get this. clrmamepro can read the mess64.exe just fine. No errors on this end.
/Edit.
No problem with the mame64.exe and mame64.xml loading.
mess64 -listxml >mess64.xml
clrmamepro wasn't able to read it. Ton of 0 popping up saying it is not read able.
But get this. clrmamepro can read the mess64.exe just fine. No errors on this end.
/Edit.
No problem with the mame64.exe and mame64.xml loading.
25
clrmame Discussion / Re: I have a question on this.
« on: 29 December 2012, 10:07 »
Oh OK. Making sure it doesn't do anything to the ROM. 
26
clrmame Discussion / I have a question on this.
« on: 29 December 2012, 04:19 »
Set: King Derby (bootleg set 2)
Name: kingdrbb2 ROM: sg1_b.e1
Issue: Possible wrong nodump definition found A valid checksum for it within its parent/clone relationship was found though.
Insert found checksum instead of using the 'nodump'?
What do I put? No?
Name: kingdrbb2 ROM: sg1_b.e1
Issue: Possible wrong nodump definition found A valid checksum for it within its parent/clone relationship was found though.
Insert found checksum instead of using the 'nodump'?
What do I put? No?
27
clrmame Discussion / Re: cmpro 4.09a released
« on: 13 December 2012, 10:13 »
I going to check the MESS CHD's that I have to make sure none is corrupted. =)
28
clrmame Discussion / Re: cmpro 4.09 released
« on: 05 December 2012, 02:57 »
I post this at the MAMEWorld just now. =)
29
clrmame Discussion / Re: clrmame is losing or deleting sets
« on: 04 December 2012, 11:04 »
Sure I will post here Roman when I need help or something.
30
clrmame Discussion / Re: clrmame is losing or deleting sets
« on: 04 December 2012, 05:15 »
Maybe it is a mistake on those. Yep the size change after I done the svn update. Maybe I need to talk to them to find out why the size went up.
http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=299982&page=0&view=expanded&sb=5&o=&fpart=1&vc=1
Tafoid said it been fix. It was a typo in the svn source.
http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=299982&page=0&view=expanded&sb=5&o=&fpart=1&vc=1
Tafoid said it been fix. It was a typo in the svn source.
31
clrmame Discussion / Re: clrmame is losing or deleting sets
« on: 04 December 2012, 02:04 »
Roman I'm talking about the tool doesn't removed the useless ROM's when all the boxes are checked on those two. Everything else useless gotten removed without a problem.
ffight -> useless ROM removed. s224b.1a
qtono2j -> useless ROM removed. tn2j_09.12a
sc4gcclb -> useless ROM's removed. 95004252.bin 95004253.bin
Unneeded is checked.
I did removed the useless ROM's by drop in the window. I think the ROM's must've been fix by MAME Team or who ever. Probably missing header or something.
Anyway I wouldn't worry about it Roman.
ffight -> useless ROM removed. s224b.1a
qtono2j -> useless ROM removed. tn2j_09.12a
sc4gcclb -> useless ROM's removed. 95004252.bin 95004253.bin
Unneeded is checked.
I did removed the useless ROM's by drop in the window. I think the ROM's must've been fix by MAME Team or who ever. Probably missing header or something.
Anyway I wouldn't worry about it Roman.
32
clrmame Discussion / Re: clrmame is losing or deleting sets
« on: 03 December 2012, 23:15 »
i going to try that one. Before I do. I want clear this with oxyandy. I didn't do a clean rebuild this time and see what happen here. This is from the svn that I download this morning. Merge the ROM's setting.
Force 10 (JPM) (IMPACT) (set 5) [folder: j6frc10d - parent: j6frc10 - size: 768kb]
wrong size: f1015p2 [wrong: 131072] [right: 131073] [CRC32: 36508a26] [not fixed]
Happy Hour (JPM) (IMPACT) (set 1) [folder: j6hapyhr - size: 768kb]
wrong size: 20427.bin [wrong: 131072] [right: 131073] [CRC32: 3de94b07] [not fixed]
No matter what I do. This will show without doing clean rebuild. Will not removed those because of the same name and different crc? Looking at the same ROM and confused? Unless it swapping in and out with two different sets.
Anyway I took those out and then rebuild those sets. Now fix. Just wouldn't removed those for some reason.
Roman. The new tool did some fixing. I saw it doing some fixing. Just wouldn't fix those above.
Force 10 (JPM) (IMPACT) (set 5) [folder: j6frc10d - parent: j6frc10 - size: 768kb]
wrong size: f1015p2 [wrong: 131072] [right: 131073] [CRC32: 36508a26] [not fixed]
Happy Hour (JPM) (IMPACT) (set 1) [folder: j6hapyhr - size: 768kb]
wrong size: 20427.bin [wrong: 131072] [right: 131073] [CRC32: 3de94b07] [not fixed]
No matter what I do. This will show without doing clean rebuild. Will not removed those because of the same name and different crc? Looking at the same ROM and confused? Unless it swapping in and out with two different sets.
Anyway I took those out and then rebuild those sets. Now fix. Just wouldn't removed those for some reason.
Roman. The new tool did some fixing. I saw it doing some fixing. Just wouldn't fix those above.
33
clrmame Discussion / Re: clrmame is losing or deleting sets
« on: 03 December 2012, 01:44 »
OK I guest I'm wrong about the merge sets. Tested MAME 0.147u3. Merge first and then Split on the Jump to Rebuilder. All I did is switch folders for a test. Only miss 4 because I roll back to released 0.147u3. Newer svn source I wasn't using this time. No ROM's was missing as oxyandy said. But yes rebuild the whole sets will solve the problem on merge. Must make a new folder for rebuild.
Roman is right. Gotta do clean rebuild the sets. Problem solve for me.
Roman is right. Gotta do clean rebuild the sets. Problem solve for me.
34
clrmame Discussion / Re: clrmame is losing or deleting sets
« on: 02 December 2012, 21:15 »
You seeing the problem now. This is the way MAME doing this. Not clrmamepro. clrmamepro only seeing on what MAME telling it. I'm sticking to Split. MESS on the other hand is clean.
35
clrmame Discussion / Re: clrmame is losing or deleting sets
« on: 02 December 2012, 08:19 »
Would be a good idea having the set up to where if a ROM matches the name and having different CRC then don't merge over to the main set. That ROM stay in that clone set. No complains ever. Well this is my last post on this.
See these. Won't be added on Merge. 21 will be miss. From the svn.
I don't why they didn't put alt on the ROM's when there different crc.
oxyandy I going try the dat then.
See these. Won't be added on Merge. 21 will be miss. From the svn.
Code: [Select]
Set: Best League (bootleg of Big Striker, Italian Serie A)
Name: bestleag
ROM: 2.bin
================
Set: Dynamite Duke (Japan)
Name: dyndukej
ROM: 3.e8
================
Set: Trivia (Unsorted question roms)
Name: gt103a1
ROM: nfl_football
================
Set: Trivia (Version 1.03a Sex questions)
Name: gt103asx
ROM: adult_sex_4
================
Set: Invader's Revenge (set 2)
Name: invrvngea
ROM: e.ic33
================
Set: Invader's Revenge (Dutchford, single PCB)
Name: invrvngedu
ROM: ir.1t
================
Set: Ms. Pac-Man Heart Burn
Name: msheartb
ROM: 5e
================
Set: Pleiads (bootleg set 1)
Name: pleiadbl
ROM: ic47.bin
================
Set: Pleiads (Centuri)
Name: pleiadce
ROM: ic47.bin
================
Set: Pleiads (bootleg set 2)
Name: pleiadsb2
ROM: ic47.bin
================
Set: Pool 10 (Italian, set 4)
Name: pool10d
ROM: 1.u20
================
Set: Pool 10 (Italian, Dino 4 hardware, encrypted)
Name: pool10e
ROM: 1.u20
================
Set: Raiden Fighters Jet (Asia)
Name: rfjeta
ROM: prg1.u0212
================
Set: Raiden Fighters Jet (Taiwan)
Name: rfjett
ROM: prg0.u0211
================
Set: Rough Ranger (v2.0, unprotected, bootleg?)
Name: rranger
ROM: 1
================
Set: Rush & Crash (Japan)
Name: rushcrsh
ROM: rc01.11e
================
Set: The Speed Rumbler (set 2)
Name: srumbler2
ROM: rc01.11e
================
Set: The Speed Rumbler (set 3)
Name: srumbler3
ROM: rc01.11e
================
Set: Super ABC (Pac-Man multigame kit, Mar. 08 1999)
Name: superabco
ROM: superabc.u14
================
Set: WEC Le Mans 24 (set 2)
Name: wecleman2
ROM: 602f08.17h
================
Set: Mahjong Yoshimoto Gekijou [BET] (Japan)
Name: yosimotm
ROM: 1.7c I don't why they didn't put alt on the ROM's when there different crc.
oxyandy I going try the dat then.
36
clrmame Discussion / Re: clrmame is losing or deleting sets
« on: 02 December 2012, 06:37 »
I lost some ROM's on merging the MAME ROM's set. Only way actually merge the sets is to edit the Split ROM's dat and then merge the right way. There is a reason to not merge with the clrmamepro without having a good merge dat. The warning on the clrmamepro screen is saying not to do it. A lot of people think it OK to merge but they don't know the ROM's will replace others. If you don't know what your doing then it to be safe to use Split until you find a good merge dat that is been made by a human not clrmamepro.
Example: When there a ROM in a main set or clone set. One of those ROM is going to replace the other ROM with the same name and different crc. You don't want to merge those.
No problem merge MESS ROM's though. No warning screen popping up. MESS seem clean and safe to merge.
Oh I'm using 7-Zip 9.20 (2010-11-18). I will try the beta.
Example: When there a ROM in a main set or clone set. One of those ROM is going to replace the other ROM with the same name and different crc. You don't want to merge those.
No problem merge MESS ROM's though. No warning screen popping up. MESS seem clean and safe to merge.
Oh I'm using 7-Zip 9.20 (2010-11-18). I will try the beta.
37
clrmame Discussion / clrmamepro with torrent7z support?
« on: 29 November 2012, 22:58 »
http://sourceforge.net/projects/t7z/files/t7z/0.9.1/
readme showing this.
I don't see a option in the clrmamepro to choose t7z. Can you add this in the option?
Anyway I had to do t7z --force-recompress A:\MESS\softwarelist\32x\*.7z without the clrmamepro. This program compress better than 7-zip.
Warning: This tool take time to do all sets. =)
readme showing this.
Code: [Select]
--cmpro
compatibility option for clrmamepro. instructs t7z to create non-solid archives to enable adding/deleting
files. those archives are not t7zipped, so execute t7z without this option over the set
after cmpro finished mutilating the set.I don't see a option in the clrmamepro to choose t7z. Can you add this in the option?
Anyway I had to do t7z --force-recompress A:\MESS\softwarelist\32x\*.7z without the clrmamepro. This program compress better than 7-zip.
Warning: This tool take time to do all sets. =)
38
clrmame Discussion / Re: clrmamepro 4.03a issue
« on: 28 February 2012, 21:26 »
Cool. I did a research on Google on the crash. Lucky that report found.
39
clrmame Discussion / Re: clrmamepro 4.03a issue
« on: 28 February 2012, 11:06 »
I tried this out today and the scanning works. http://www.emulab.it/forum/index.php?topic=342.0
The bug is the "Mark disabled set as unneeded" checked. Seem broken here.
OK to everyone that have this problem going have to unchecked that box before scanning. Then enabled it for fixing. =/
Oh ya. Checking disk found nothing wrong on my Windows 7 and hard drive.
The bug is the "Mark disabled set as unneeded" checked. Seem broken here.
OK to everyone that have this problem going have to unchecked that box before scanning. Then enabled it for fixing. =/
Oh ya. Checking disk found nothing wrong on my Windows 7 and hard drive.
40
clrmame Discussion / Re: clrmamepro 4.03a issue
« on: 28 February 2012, 05:32 »
I'm doing checking disk right now. This be done over night.