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

Pages: [1]
1
@Roman: Thanks for the help. I was looking at this link earlier before I made the post. Must have missed something when I went to make changes to engine.cfg.

@oddi: Thanks for pointing that out. My search skills suck.

2
Keep getting this warning message when I try to load an external MESS ListXML DAT file.



Normally I process MESS ListXML through DatUtil before processing in clrmamepro. Needed to test something out.

Clrmamepro doesn't have a problem with loading external MAME ListXML DAT file.

MESS ListXML included in the attachment below.

3
clrmame Discussion / Re: [MESS Softlist] amiga_a3000.xml
« on: 20 September 2014, 01:04 »
Well, the 0 byte file is added to each set because the "belongs-to-parent-check" is checksum based...guess there is the problem....not the nodump thingie..
as mentioned, a nodump with a given size = 0 becomes a valid dump with size = 0...

when I'm back home later I can double check...

I only tried the parent set...and it correctly added it once...and did not want to remove it...
with clones, I got an idea where the problem is...bet 'there' it sees that the clone files are not needed since they are in the parent already....

as I said...funny scenario...will work on it later tonight

Kinda hard to believe when you can create dummy ROM in a set by using file size of zero and inserting CRC 00000000 in a DAT, which would do the exact same thing.

Code: [Select]
<rom name="dummy" size="0" crc="0000000"/>
That's how I've seen it done in other DAT files.

Never knew you can do it the way MESS did it. I thought that was a bug in clrmamepro, even though you've already stated twice to me that it wasn't the case. Sorry for being so thick headed. I was confused.

ok...the parent/clone relationship is now correctly detected for such zero byte files...problem solved with next release...

Glade the real problem has been solved. :)

4
clrmame Discussion / Re: [MESS Softlist] amiga_a3000.xml
« on: 19 September 2014, 03:06 »
Come to think of it, you maybe dealing with two different issues.

As a test, I've created two different DAT files for you to try out. Both DATs contains one ROM entry with a "no dump" status set. One DAT has a file size of 0 byte and the other DAT with a file size of 1 byte. Readme included with DATs. See attachment below.

As for the second issue, not sure about that one. That may or may not be related to the first issue. Guess that's something you need to explore?

5
clrmame Discussion / Re: [MESS Softlist] amiga_a3000.xml
« on: 19 September 2014, 00:56 »
I'm not using 7zip to archive my sets. I'm using plain ole' ZIP format.

I changed the ROM set to use 7zip instead of ZIP like you asked me to. Same result.

I'm going to include the amiga_a3000 full ROM set for you to test out. See link below.

amiga_a3000.7z (5.38 MB)
http://www6.zippyshare.com/v/73236024/file.html

I've excluded the cass ROM file from 4 of the ROM sets (amix11, amix201, amix203 and amix21) so you can get a better understanding what's going on.

For the first test, make sure split mode is used for these ROM sets. Run new scan. These messages will appear soon after.

1st New Scan (Split)
Quote
Code: [Select]
Set: UNIX System V Release 4 Amiga Version 1.1
Name: amix11
File: I:\MESS\software\amiga_a3000\amix11\cass

Do you want to add the missing ROM?

YES

Code: [Select]
Set: UNIX System V Release 4 Amiga Version 2.01
Name: amix201
File: I:\MESS\software\amiga_a3000\amix201\cass

Do you want to add the missing ROM?

YES

Code: [Select]
Set: UNIX System V Release 4 Amiga Version 2.03
Name: amix203
File: I:\MESS\software\amiga_a3000\amix203\cass

Do you want to add the missing ROM?

YES

Code: [Select]
Set: UNIX System V Release 4 Amiga Version 2.1
Name: amix21
File: I:\MESS\software\amiga_a3000\amix21\cass

Do you want to add the missing ROM?

YES

cass ROMs (dummy files) were added to the following four sets (as mentioned above) with the file size being zero and the CRC being 0000000 as listed in the archives. ROM set complete with nothing to fix.

Now perform a second new scan. The following messages will appear soon after.

2nd New Scan (Split)
Quote
Code: [Select]
Set: UNIX System V Release 4 Amiga Version 2.01
Name: amix201
File: I:\MESS\software\amiga_a3000\amix201\cass

Do you want to remove the file?

YES

Code: [Select]
Set: UNIX System V Release 4 Amiga Version 2.03
Name: amix203
File: I:\MESS\software\amiga_a3000\amix203\cass

Do you want to remove the file?

YES

Code: [Select]
Set: UNIX System V Release 4 Amiga Version 2.1
Name: amix21
File: I:\MESS\software\amiga_a3000\amix21\cass

Do you want to remove the file?

YES

Code: [Select]
Set: UNIX System V Release 4 Amiga Version 2.01
Name: amix201
File: I:\MESS\software\amiga_a3000\amix201\cass

Do you want to add the missing ROM?

YES

Code: [Select]
Set: UNIX System V Release 4 Amiga Version 2.01
Name: amix201
File: I:\MESS\software\amiga_a3000\amix201\cass

Do you want to remove the file?

YES

Code: [Select]
Set: UNIX System V Release 4 Amiga Version 2.03
Name: amix203
File: I:\MESS\software\amiga_a3000\amix203\cass

Do you want to add the missing ROM?

YES

Code: [Select]
Set: UNIX System V Release 4 Amiga Version 2.03
Name: amix203
File: I:\MESS\software\amiga_a3000\amix203\cass

Do you want to remove the file?

YES

Code: [Select]
Set: UNIX System V Release 4 Amiga Version 2.1
Name: amix21
File: I:\MESS\software\amiga_a3000\amix21\cass

Do you want to add the missing ROM?

YES

Code: [Select]
Set: UNIX System V Release 4 Amiga Version 2.1
Name: amix21
File: I:\MESS\software\amiga_a3000\amix21\cass

Do you want to remove the file?

YES

If I had chosen to keep the cass ROM file instead of removing them, clrmamepro will now show the cass ROM file as being unneeded for amix201, amix203 and  amix21 set. Strange how clrmamepro doesn't mark cass ROM file as unneeded for amix11 set.

For the second test, I used merge mode instead of split mode (without the cass ROM file), clrmamepro will add the cass ROM file to amix11 set only (amix201, amix203 and amix21 clone set is now consolidated into amix11 parent). Performing a second new scan, nothing needs to be fixed.

Is this parent/clone bug in clrmamepro?

6
clrmame Discussion / Re: [MESS Softlist] amiga_a3000.xml
« on: 18 September 2014, 16:32 »
Great. :)

7
clrmame Discussion / Re: [MESS Softlist] amiga_a3000.xml
« on: 18 September 2014, 15:07 »
I would also like to add, this may have been done intentionally. Data area of this ROM, shows the size being zero as well.

Code: [Select]
<dataarea name="cass" size="0">
Guess this is something that needs to fixed on your end?

8
clrmame Discussion / [MESS Softlist] amiga_a3000.xml
« on: 18 September 2014, 14:59 »
Source: http://git.redump.net/mame/commit/hash?id=bc221ccf56d54239d7e4b0bd9aab2275417c5bbe

New amiga_a3000.xml softlist is causing problems.
Direct Link: http://git.redump.net/mame/plain/hash/amiga_a3000.xml

Problem: Clrmamepro is constantly adding/deleting/re-adding cass ROM file when a new scan is performed.

amiga_a3000.xml
Code: [Select]
<?xml version="1.0"?>
<!DOCTYPE softwarelist SYSTEM "softwarelist.dtd">

<!-- This list contains the system software specific to the Amiga 3000: -->
<!-- SuperKickstart disks, SCSI installation disks and AMIX -->

<softwarelist name="amiga_a3000" description="Amiga 3000 System disks">

<!-- SuperKickstart -->

<software name="sk201">
<description>Kickstart 2.01</description>
<year>1990</year>
<publisher>Commodore</publisher>
<part name="flop1" interface="floppy_3_5">
<feature name="part_id" value="Kickstart 2.01" />
<dataarea name="flop" size="901120">
<rom name="367245-03_kickstart.adf" size="901120" crc="79c58ce8" sha1="8e738fb5a9d293c8321cf5055c06f368d43a6e2b" offset="0"/>
</dataarea>
</part>
</software>

<software name="sk204">
<description>Kickstart 2.04</description>
<year>1991</year>
<publisher>Commodore</publisher>
<part name="flop1" interface="floppy_3_5">
<feature name="part_id" value="Kickstart 2.04" />
<dataarea name="flop" size="901120">
<rom name="367245-06_kickstart.adf" size="901120" crc="87ad0c5b" sha1="922ec2776766a6568f3e2de37101c497067948e4" offset="0"/>
</dataarea>
</part>
</software>

<!-- A3000 Installation disks -->

<software name="a3kin203">
<description>A3000 Install Disk 2.03</description>
<year>1991</year>
<publisher>Commodore</publisher>
<part name="flop1" interface="floppy_3_5">
<feature name="part_id" value="A3000 Install Disk 2.03" />
<dataarea name="flop" size="901120">
<rom name="335603-04_install.adf" size="901120" crc="9a3cc466" sha1="b12a225890a3957bb01dcbfba44c046c19e19c8f" offset="0"/>
</dataarea>
</part>
</software>

<!-- Amiga UNIX System V Release 4 -->
<!-- TODO: Part numbers -->

<software name="amix11">
<description>UNIX System V Release 4 Amiga Version 1.1</description>
<year>1990</year>
<publisher>Commodore</publisher>
<part name="flop1" interface="floppy_3_5">
<feature name="part_id" value="Installation Disk 1 (Boot)"/>
<dataarea name="flop" size="901120">
<rom name="amix_11_boot.adf" size="901120" crc="83a9c798" sha1="7b530cb8ff39933c7cef2ee6349a9b2d147e6a6d" offset="0" />
</dataarea>
</part>
<part name="flop2" interface="floppy_3_5">
<feature name="part_id" value="Installation Disk 2 (Root file system)"/>
<dataarea name="flop" size="901120">
<rom name="amix_11_root.adf" size="901120" crc="9ac8c76e" sha1="61f06cf47c12930ff9677c57a8464c549c5fb839" offset="0" />
</dataarea>
</part>
<part name="tape" interface="a3000_cass">
<feature name="part_id" value="Installation Tape"/>
<dataarea name="cass" size="0">
<rom name="cass" size="0" status="nodump" offset="0" />
</dataarea>
</part>
</software>

<software name="amix201" cloneof="amix11">
<description>UNIX System V Release 4 Amiga Version 2.01</description>
<year>199?</year>
<publisher>Commodore</publisher>
<part name="flop1" interface="floppy_3_5">
<feature name="part_id" value="Installation Disk 1 (Boot)"/>
<dataarea name="flop" size="901120">
<rom name="amix_201_boot.adf" size="901120" crc="7e3ecc6b" sha1="63d0144296e63b8ea09e4c1b2a85d1e09dc111e5" offset="0" />
</dataarea>
</part>
<part name="flop2" interface="floppy_3_5">
<feature name="part_id" value="Installation Disk 2 (Root file system)"/>
<dataarea name="flop" size="901120">
<rom name="amix_201_root.adf" size="901120" crc="c8fef4fd" sha1="840a23a93329b4f68113515f9bf466bb15af1bc7" offset="0" />
</dataarea>
</part>
<part name="tape" interface="a3000_cass">
<feature name="part_id" value="Installation Tape"/>
<dataarea name="cass" size="0">
<rom name="cass" size="0" status="nodump" offset="0" />
</dataarea>
</part>
</software>

<software name="amix203" cloneof="amix11">
<description>UNIX System V Release 4 Amiga Version 2.03</description>
<year>199?</year>
<publisher>Commodore</publisher>
<part name="flop1" interface="floppy_3_5">
<feature name="part_id" value="Installation Disk 1 (Boot)"/>
<dataarea name="flop" size="901120">
<rom name="amix_203_boot.adf" size="901120" crc="a10249c1" sha1="5c62519528d92a6e8a7b88d9879d9d0903e90ad2" offset="0" />
</dataarea>
</part>
<part name="flop2" interface="floppy_3_5">
<feature name="part_id" value="Installation Disk 2 (Root file system)"/>
<dataarea name="flop" size="901120">
<rom name="amix_203_root.adf" size="901120" crc="6859ae85" sha1="ed38709d4f9b7a1cfc42112038e74b75587de73f" offset="0" />
</dataarea>
</part>
<part name="tape" interface="a3000_cass">
<feature name="part_id" value="Installation Tape"/>
<dataarea name="cass" size="0">
<rom name="cass" size="0" status="nodump" offset="0" />
</dataarea>
</part>
</software>

<software name="amix21" cloneof="amix11">
<description>UNIX System V Release 4 Amiga Version 2.1</description>
<year>199?</year>
<publisher>Commodore</publisher>
<part name="flop1" interface="floppy_3_5">
<feature name="part_id" value="Installation Disk 1 (Boot)"/>
<dataarea name="flop" size="901120">
<rom name="amix_21_boot.adf" size="901120" crc="99a92138" sha1="c3c444fdf00275b8a1d57d3da8556267977d940a" offset="0" />
</dataarea>
</part>
<part name="flop2" interface="floppy_3_5">
<feature name="part_id" value="Installation Disk 2 (Root file system)"/>
<dataarea name="flop" size="901120">
<rom name="amix_21_root.adf" size="901120" crc="7c134fcd" sha1="586cba2c40e007d09f634647e15e33a5ac4ba069" offset="0" />
</dataarea>
</part>
<part name="flop3" interface="floppy_3_5">
<feature name="part_id" value="Patch Disk"/>
<dataarea name="flop" size="901120">
<rom name="amix_patch_21.adf" size="901120" crc="6b401165" sha1="325df79e3ca52709d47512227d187c87ed4c9472" offset="0" />
</dataarea>
</part>
<part name="tape" interface="a3000_cass">
<feature name="part_id" value="Installation Tape"/>
<dataarea name="cass" size="0">
<rom name="cass" size="0" status="nodump" offset="0" />
</dataarea>
</part>
</software>

</softwarelist>

After looking over the amiga_a3000 softlist, I noticed this ROM file has a "nodump" status.

Code: [Select]
rom name="cass" size="0" status="nodump" offset="0" />
This ROM appears under the software name amix11, amix201, amix203 and amix21.

Solution: The only way to alleviate the problem is by changing the size of the ROM to another number besides 0.

Code: [Select]
rom name="cass" size="1" status="nodump" offset="0" />
Clrmamepro no longer has the need to constantly re-add/delete cass ROM file.

I'm including the softlist in the attachment below, in case something changes with the SVN link that was pointed out at the beginning of the post.

9
clrmame Discussion / Re: clrmamepro 4.02 released
« on: 01 December 2011, 01:42 »
I forgot to mention I'm using clrmamepro 4.02. The most recent version.

10
clrmame Discussion / Re: clrmamepro 4.02 released
« on: 01 December 2011, 01:41 »
Hello Roman,

Whenever I use "BatchMode" to rebuild my rom files (mostly fixdats), the roms are always rebult in zip archives even when "Always Compress Files" is unticked under "Rebuilder" tab. I know for a fact the "force package tag" are not present in these DAT files. Any help would be appreciated. Thank you for your time.

11
News & Communication / Re: DatWorshop Pro 2.3.0
« on: 01 December 2011, 01:25 »
Hello Simone,

I've left you a bug report (assuming it is a bug) at the link below.
http://www.emulab.it/forum/index.php?topic=713.0

12
DatWorkshop Pro / DWP 2.3.0 "RealDiff" Freezing Up
« on: 01 December 2011, 01:20 »
No matter what I do, RealDiff freezes up on my system when I try to compare two generic DAT files. Windows Task Manager is reporting 85% to 97% CPU usage when this occurs. I have no choice but to end the process. Not sure what's going on here. The previous version (DWP 2.24) doesn't experience this freeze when I compare those two generic DAT files.

Operating System: Windows 7
Edition: Ultimate
Service Pack: SP1
Windows Update: Up-to-Date

If you need any other information regarding my system or the two DAT files I'm trying to compare, let me know. I'll provide them for you.

Edit: Typo.

13
clrmame Discussion / Re: clrmamepro 4.00 released
« on: 01 September 2011, 09:48 »
ok...I will check later this evening..Thanks for providing the information.

By the way, if you're working with Vista or Windows7, any drag'n drop won't work if the application and the dropped files belong to different levels of UAC. So for such OSes, be sure to not install cmpro in an uac controlled folder. But that also happened with cmpro 3.x already (and other software ;))
Anyway...I will check the drag'n drop...

ok, I've downloaded the Casio - PV-1000 (20100525_cm).zip datfile from the dat-o-matic on my system. Drag'n drop worked fine on my Win7 with 32 and 64 bit versions.

Soo...which OS do you have? Maybe you should send me a zip which doesn't work for you.
In case of VISTA/Win7 be sure that cmpro is NOT installed (and you seem to use the installer version....) in an UAC controlled folder (e.g. NOT in c:\programs).
If you do install it there, you need to run it with "run as administrator"...

Operating System
OS: Windows 7
Edition: Ultimate
Architecture: 32-bit
Service Pack: SP1

User Account
Account Name: ****
Account Type: Administrator
UAC ON or OFF: On
UAC Settings: Default - Notify me only when programs try to make changes to the computer

clrmamepro (Compatibility Tab)

Compatibility Mode Section
Run this program in compatibility for: Unticked (N/A)

Settings Section
Run in 256 colors: Unticked
Run in 640x480 screen resolution: Unticked
Disable visual themes: Unticked
Disable desktop composition: Unticked
Disable display scaling on high DPI settings: Unticked

Privilege Level Section
Run this program as an administrator: Ticked

Installation Location: C:\Program Files\clrmamepro

Note: Since I didn't want to go through the trouble of uninstalling clrmamepro under "Program Files" just yet, I tried the portable version of clrmamepro under a non-UAC protected folder per your instruction. Sure enough, drag'n drop feature worked as it should along with my dat/xml files. No need to send them to you at this point.

Additional Note: Just for kicks, I disabled UAC altogether under my administrator account just to test the drag'n drop feature of clrmampro, where the original installation location is: "Program Files". Sure enough, drag'n drop worked. If I try "Run as administrator" (right click) with UAC turned on, drag'n drop didn't work.

Conclusion: Before I installed clrmamepro, I read this note under the download section.

Quote
Vista/Windows7 user note:

If you install cmpro to a protected folder like C:\program files\, you have to set the compatibility properties of cmpro.exe to 'run this program as administrator' to work correctly or you have to disable UAC. In other folders it should work fine without setting this property and without the need of disabling UAC.

Although I knew what I was getting myself into when I installed clrmamepro under "Program Files", It doesn't state in the note that drag'n drop would not work even with, "Run this program as an administrator" ticked with UAC turned on. I thought this whole time I discovered a bug (well technically it is). Sorry for rambling on.

14
clrmame Discussion / Re: clrmamepro 4.00 released
« on: 01 September 2011, 00:39 »
Also, I found couple minor issues (more like an observation) regarding your windows installer. This doesn't affect clrmamepro in any way. This was probably overlooked.

Post-Installation of clrmamepro
Executable Name: cmp400_32.exe
Issue: Two shortcut links (Forum and Webpage) under clrmamepro start menu folder, point to invalid web links.

Forum Shortcut
Current Link: http://www.clrmame.com/cgi-bin/wwwthreads/wwwthreads.pl?action=list&Board=clrmame
Should Be: http://www.emulab.it/forum/index.php?board=6.0

Homepage Shortcut
Current Link: http://www.clrmame.com/
Should Be: http://www.emulab.it/clrmamepro/ or http://mamedev.emulab.it/clrmamepro/

Like I said, this is very minor. Nothing to sweat over about. I didn't test this with cmp400_64.exe. I'm assuming it has the same issue. This shouldn't be to hard to fix in your NSIS script. :)

15
clrmame Discussion / Re: clrmamepro 4.00 released
« on: 31 August 2011, 23:43 »
if drag'n drop doesn't work for you, your dropped file most likely isn't readable...please provide the zip/xml in question

MESS Softlist Hash Files (GIT Repository)
DAT or XML: XML
Link: http://git.redump.net/cgit.cgi/mess/plain/hash/
Note: Doesn't matter which one you pick.

No-Intro DAT-o-MATIC
DAT or XML: DAT (Archived in Zip File)
Link: http://datomatic.no-intro.org/
Note: To download, click the "floppy" icon corresponding to that dat file. Doesn't matter which one you pick.

I'm using clrmamepro 4.0 (32-bit) version.

16
clrmame Discussion / Re: clrmamepro 4.00 released
« on: 31 August 2011, 21:10 »
ehe...looks like all testers did not see the crash when pressing the add button in the profiler window :)
....well...till it gets fixed simply use drag'n drop to add profiles.
Drag'n drop single/multiply xml and dat (bundled in zip) into the profiler windows does not work for me. I do see the plus sign symbol when I drag something into the profiler window. Strange.

I would like to give clrmamepro 4.0 a spin, but with the "Add DatFile..." button crash happening on my end, I can't do anything else other then create EXE based profiles.

Should I create detailed bug report (here or create a new post) regarding this issue or should I wait till the next version comes out? Event viewer did show something. I will get detailed if necessary to get this bug ironed out. :)

Pages: [1]

Page created in 0.188 seconds with 21 queries.

anything