|
clrmamepro 4.00
#263455 - 08/31/11 12:22 AM
|
|
|
clrmamepro 4.0
misc: full unicode build
misc: full support for UTF8 characters in file/folder names, files within
archives (7z/rar/zip) and datfiles (XML and old format)
The default encoding of xml datfiles is UTF8. The default storing method
in archives is UTF8 (for zip, with no extra field usage). Current versions
of Winrar, Winzip, 7z (just to name a few) support UF8 stored names. There
might be other 3rd party tools (which some people use to rezip/share  )
which might fail (they only work with local page encoding). Tough luck...
All textfiles in the clrmamepro environment are now saved as UTF8. You
can use your old setup, since it loads them in ASCII and saves them as
UTF8. XML files are stored without a BOM (byte ordered mark), non-xml
files with a BOM. You should not use newly written files with old
versions of clrmamepro. I recommend a good texteditor to work with UF8
datfiles, e.g. notepad++, available here http://notepad-plus-plus.org/
misc: completely switched to latest ziparchive library for all zip related
operations. This includes reading, in-place renaming and no-recompress
copy. This results in a faster rebuilder (no recompress) and faster
rename operations (scanner). Actual scanning speed is roughly the same.
added: devices support, devices and device_ref elements are parsed, exported,
an own system default path for devices can be added, select sets
supports filtering by devices and device_refs
removed: included doucmentation, switching to online pdf docs soon
removed: Settings->Compressor->Zip, obsolete due to ziparchive usage
removed: Settings->Compressor->Oem/Ansi conversion, obsolete due to UTF8 switch
removed: Scanner->Advanced->
detect sets in wrong sysdefpaths
move sets to correct sysdefpath
chd use sysdefault assignments
use sysdefault paths for fix missing
Such options are automatically enabled internally now if sysdefpaths
are setup. The first two ones require an unneeded check+fix though.
misc: aligned "allow not separated bios sets" & "split bios sets"
misc: directly jump to profiler or settings instead of prompting
fixed: xml parser doesn't handle multiple comments on the same line correctly
fixed: dat resource tag export for non-xml datfiles is broken
|
|
|
|
Re: clrmamepro 4.00
[Re: Roman]
#263466 - 08/31/11 02:12 AM
|
|
|
Just updated, I'm getting crashes whenever I use the Add DatFile function.
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: clrmamepro 4.00
[Re: incog]
#263471 - 08/31/11 02:38 AM
|
|
|
I can confirm and even extracting everything in new directory it happens.
Problem signature:
Problem Event Name: APPCRASH
Application Name: cmpro64.exe
Application Version: 3.19.9.0
Application Timestamp: 4e5d591d
Fault Module Name: cmpro64.exe
Fault Module Version: 3.19.9.0
Fault Module Timestamp: 4e5d591d
Exception Code: c0000005
Exception Offset: 000000000028b323
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: e73f
Additional Information 2: e73f481544e6e8f6c9351f2a26038e11
Additional Information 3: 8f62
Additional Information 4: 8f62b898b216df8972b1542a7ec7ad6e
|
|
|
|
Re: clrmamepro 4.00
[Re: incog]
#263489 - 08/31/11 07:22 AM
|
|
|
Use drag'n drop to add datfiles (simply move xml/dat/zip/rar/7z) into the profiler window.
I can confirm the issue when using the add button (funnily noone from the testers seems to use it for years). Please report issues either on the cmpro forum or msg me.
|
|
|
|
Re: clrmamepro 4.00
[Re: Roman]
#263491 - 08/31/11 07:31 AM
|
|
|
Nope,
I always drag n' drop dats.
So I didn't catch that one.
|
|
|
|
Re: clrmamepro 4.00
[Re: oxyandy]
#263492 - 08/31/11 07:33 AM
|
|
|
shame on you  Actually I don't know anyone who uses the add button....now I do....I will fix it soon.
|
|
|
|
Re: clrmamepro 4.00
[Re: Roman]
#263495 - 08/31/11 07:52 AM
|
|
|
> shame on you Actually I don't know anyone who uses the add button....now I do....I
> will fix it soon.
Actually Roman.. I do - a fix would be cool.
Cheers.
|
|
|
|
Re: clrmamepro 4.00
[Re: Scooby]
#263496 - 08/31/11 07:57 AM
|
|
|
I already found the cause (one Windows Filedialog attribute still pointed to a char instead of a TCHAR buffer)....assume a fixed version tomorrow...till then, please use drag'n drop.
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: clrmamepro 4.00
[Re: Roman]
#263497 - 08/31/11 08:00 AM
|
|
|
> I already found the cause (one Windows Filedialog attribute still pointed to a char
> instead of a TCHAR buffer)....assume a fixed version tomorrow...till then, please use
> drag'n drop.
No problem. Drag and drop very easy
Thanks very much for you're work.
|
|
|
|
Re: clrmamepro 4.00
[Re: Roman]
#263499 - 08/31/11 08:05 AM
|
|
|
anyone using cmpro through wine or crossover
|
|
|
|
Re: clrmamepro 4.00
[Re: B2K24]
#263500 - 08/31/11 08:07 AM
|
|
|
> > I already found the cause (one Windows Filedialog attribute still pointed to a char
> > instead of a TCHAR buffer)....assume a fixed version tomorrow...till then, please
> use
> > drag'n drop.
>
> No problem. Drag and drop very easy
>
> Thanks very much for you're work.
Absolutely... nice one Roman. Those ol' TCHAR buffers 
|
|
|
|
Re: clrmamepro 4.00
[Re: Roman]
#263547 - 08/31/11 08:36 PM
|
|
|
strange thing - current CMP thinks some bioses is not bioses, for example naomi's epr-21577d.ic27 and epr-21577e.ic27, and places it to game's sets.
maybe bios count limited to 16 ?
|
|
|
|
Re: clrmamepro 4.00
[Re: MetalliC]
#263550 - 08/31/11 08:47 PM
|
|
|
or because their checksum is same as an existing one?
Code:
ROM_SYSTEM_BIOS( 13, "bios13", "epr-21577e (USA)" ) \
ROM_LOAD16_WORD_SWAP_BIOS( 13, "epr-21577e.ic27", 0x000000, 0x200000, CRC(cf36e97b) SHA1(b085305982e7572e58b03a9d35f17ae319c3bbc6) ) \
ROM_SYSTEM_BIOS( 14, "bios14", "epr-21577d (USA)" ) \
ROM_LOAD16_WORD_SWAP_BIOS( 14, "epr-21577d.ic27", 0x000000, 0x200000, CRC(60ddcbbe) SHA1(58b15096d269d6df617ca1810b66b47deb184958) ) \
ROM_SYSTEM_BIOS( 15, "bios15", "epr-21579d (Korea)" ) \
ROM_LOAD16_WORD_SWAP_BIOS( 15, "epr-21579d.ic27", 0x000000, 0x200000, CRC(cf36e97b) SHA1(b085305982e7572e58b03a9d35f17ae319c3bbc6) ) \
ROM_SYSTEM_BIOS( 16, "bios16", "epr-21579 (Korea)" ) \
ROM_LOAD16_WORD_SWAP_BIOS( 16, "epr-21579.ic27", 0x000000, 0x200000, CRC(60ddcbbe) SHA1(58b15096d269d6df617ca1810b66b47deb184958) ) \
|
|
|
|
|
> or because their checksum is same as an existing one?
yes, CRC's the same
here is screenshot with 18 Wheeler DX set as example
[ATTACHED IMAGE]
|
|
|
|
Re: clrmamepro 4.00
[Re: MetalliC]
#263576 - 09/01/11 01:09 AM
|
|
|
haha...there is no limit....I will check why it is interpreted differently...
...and please use the cmpro forum or msg me...
|
|
|
|
Re: clrmamepro 4.00
[Re: MetalliC]
#263578 - 09/01/11 01:15 AM
|
|
|
It doesn't do that here (split-merged).
Maybe it's related to Scanner Advanced/Separate BIOS sets...which should be enabled. SO check that setting.
|
|
|
|
Re: clrmamepro 4.00
[Re: Roman]
#263580 - 09/01/11 01:24 AM
|
|
|
Those bioses were recently added, post-u4, maybe you can obtain a mame svn snapshot from someone?
|
|
|
Tafoid |
|
I keep on testing.. testing.. testing... into the future!
|
|
|
|
|
Reged: 04/19/06
|
|
Posts: 3137
|
|
Loc: USA
|
|
|
|
Send PM
|
|
|
Re: clrmamepro 4.00
[Re: MetalliC]
#263591 - 09/01/11 03:39 AM
|
|
|
The issue is resolved for the next release. Newly added bios pieces were not given proper checksums - resulting in the double entries.
|
|
|
| R. Belmont |
|
Cuckoo for IGAvania
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 9716
|
|
Loc: ECV-197 The Orville
|
|
|
|
Send PM
|
|
|
Re: clrmamepro 4.00
[Re: etabeta]
#263607 - 09/01/11 06:15 AM
|
|
|
> anyone using cmpro through wine or crossover
cmpro through wine tends to destroy your roms instead of rebuilding them, especially if they're over an NFS or SMB mount. (To be fair, I've also had it destroy my roms running on real Windows in a VMWare instance). Accept your minority platform status and give up on cmpro.
|
|
|
|
Re: clrmamepro 4.00
[Re: R. Belmont]
#263608 - 09/01/11 07:29 AM
|
|
|
eh? Last time I used it under Wine it works flawlessly (besides some Windows UI flaws maybe)...
|
|
|
|
Re: clrmamepro 4.00
[Re: Tafoid]
#263609 - 09/01/11 09:23 AM
|
|
|
|
|
|
Re: clrmamepro 4.00
[Re: R. Belmont]
#263618 - 09/01/11 11:04 AM
|
|
|
> > anyone using cmpro through wine or crossover
>
> cmpro through wine tends to destroy your roms instead of rebuilding them, especially
> if they're over an NFS or SMB mount.
given that MacOSX cannot even write to NFS drives (without external programs to handle the filesystem), I store my roms on FAT32 drives and cmpro deals with them flawlessy under both WinXP and MacOSX. never got a single byte destroyed by it.
the only issue I have encountered is that sometimes rebuild does stop before completing a directory scan so that I have to run it twice or three times if I have to rebuild large chunks of files (but I never managed to reproduce it consistently, so I can simply live with it)
|
|
|
| R. Belmont |
|
Cuckoo for IGAvania
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 9716
|
|
Loc: ECV-197 The Orville
|
|
|
|
Send PM
|
|
|
Re: clrmamepro 4.00
[Re: etabeta]
#263633 - 09/01/11 06:46 PM
|
|
|
> given that MacOSX cannot even write to NFS drives (without external programs to
> handle the filesystem), I store my roms on FAT32 drives and cmpro deals with them
> flawlessy under both WinXP and MacOSX. never got a single byte destroyed by it.
What? OS X has had full read/write NFS support since the preview beta. You can't be considered Unix without that functionality (And in fact all of my Macs have always been able to see my NFS server just fine).
|
|
|
|
Re: clrmamepro 4.00
[Re: R. Belmont]
#263634 - 09/01/11 06:58 PM
|
|
|
> > given that MacOSX cannot even write to NFS drives (without external programs to
> > handle the filesystem), I store my roms on FAT32 drives and cmpro deals with them
> > flawlessy under both WinXP and MacOSX. never got a single byte destroyed by it.
>
> What? OS X has had full read/write NFS support since the preview beta. You can't be
> considered Unix without that functionality (And in fact all of my Macs have always
> been able to see my NFS server just fine).
to my knowledge, OSX 10.6 (which is what I have here) only allows to read from NTFS. If you want to write to a NTFS drive you need to rely on NTFSX or NTFS-3G... a short google search seems to confirm it, but I might be wrong...
|
|
|
| Stiletto |
|
They're always after me Lucky ROMS!
|
|
|
|
|
|
Reged: 03/07/04
|
|
Posts: 6472
|
|
|
|
|
|
Send PM
|
|
|
Re: clrmamepro 4.00
[Re: etabeta]
#263640 - 09/01/11 07:44 PM
|
|
|
> > > given that MacOSX cannot even write to NFS drives (without external programs to
> > > handle the filesystem), I store my roms on FAT32 drives and cmpro deals with them
> > > flawlessy under both WinXP and MacOSX. never got a single byte destroyed by it.
> >
> > What? OS X has had full read/write NFS support since the preview beta. You can't be
> > considered Unix without that functionality (And in fact all of my Macs have always
> > been able to see my NFS server just fine).
>
> to my knowledge, OSX 10.6 (which is what I have here) only allows to read from NTFS.
> If you want to write to a NTFS drive you need to rely on NTFSX or NTFS-3G... a short
> google search seems to confirm it, but I might be wrong...
Ah. NFS != NTFS. Typo? 
- Stiletto
|
|
|
|
Re: clrmamepro 4.00
[Re: MetalliC]
#263652 - 09/01/11 09:52 PM
|
|
|
well, yes...it gets a bit confused due to the checksum. Actually I now made the check a bit smarter and the next version will handle it correctly.
|
|
|
|
Re: clrmamepro 4.00
[Re: Roman]
#263667 - 09/01/11 11:39 PM
|
|
|
clrmamepro 4.0a
fixed: crash in filedialog of "add Profile"
misc: smarter is-bios-rom check if bios definitions hold identical checksums
misc: fixed homepage and forum link in installer
|
|
|
|
Re: clrmamepro 4.00
[Re: etabeta]
#263702 - 09/02/11 07:44 AM
|
|
|
> > > given that MacOSX cannot even write to NFS drives (without external programs to
> > > handle the filesystem), I store my roms on FAT32 drives and cmpro deals with them
> > > flawlessy under both WinXP and MacOSX. never got a single byte destroyed by it.
> >
> > What? OS X has had full read/write NFS support since the preview beta. You can't be
> > considered Unix without that functionality (And in fact all of my Macs have always
> > been able to see my NFS server just fine).
>
> to my knowledge, OSX 10.6 (which is what I have here) only allows to read from NTFS.
> If you want to write to a NTFS drive you need to rely on NTFSX or NTFS-3G... a short
> google search seems to confirm it, but I might be wrong...
_Network_ File System, remote file system created by Sun ages ago, latest version described in http://www.ietf.org/rfc/rfc3530.txt. And pretty much the standard way under unix to do remote filesystems (there are others, but they're not used as much).
OG.
|
|
|
|
|
I was pretty sure to have read NTFS... of course NFS is supported on any *nix OS...
this mostly means I need either to sleep more or to drink more coffee
|
|
|
|
Re: clrmamepro 4.00
[Re: Roman]
#263739 - 09/02/11 05:33 PM
|
|
|
> clrmamepro 4.0a
>
> fixed: crash in filedialog of "add Profile"
> misc: smarter is-bios-rom check if bios definitions hold identical checksums
> misc: fixed homepage and forum link in installer
Thanks ! ((:
|
|
|
|
Re: clrmamepro 4.00
[Re: Roman]
#263995 - 09/05/11 07:54 PM
|
|
|
I see 60 bios system files listed and the statistcs also say 60.
Shouldn't it be 62. I'm missing Brave Fire Fighters "braveff" and System 1 with sound board "gts1s".
There is a small misspelling in the Systems window: (Un-)Check
sytems you...
cu
|
|
|
|
Re: clrmamepro 4.00
[Re: Canim]
#264001 - 09/05/11 08:53 PM
|
|
|
I will check later this week when Im back from holiday.
|
|
|
|
Re: clrmamepro 4.00
[Re: Roman]
#264017 - 09/06/11 05:59 AM
|
|
|
Just got done downloading the sets to go from 0.137 to 0.143. Now I just go to figure out how to make a complete set.
|
|
|
|
Re: clrmamepro 4.00
[Re: Canim]
#264191 - 09/08/11 12:12 AM
|
|
|
thanks...it's fixed now....4.00b
|
|
|
Previous 
Index 
Next 
Threaded 
clrmamepro 4.00
Reply
)
[Re: 
Actually I don't know anyone who uses the add button....now I do....I will fix it soon.
