- 17 May 2024, 06:10
- Welcome, Guest
News:
The new forum is online, hope you enjoy it!
1
on: Today at 06:10
|
||
Started by scuore - Last post by johnsond | ||
You completed certain reliable points there. I did a search on the subject and found nearly all persons will agree with your blog. You can talk to our dedicated team of experts at any time to understand the exact solution to the problems. You interested in video game stores service so contact us.
|
3
on: 15 May 2024, 21:51
|
||
Started by EarBiteR - Last post by EarBiteR | ||
Yeah I see that now. Mame has a -version option as well as the build info in the -listxml but pinmame doesnt provide build info in the xml :-(
I will browse mame's source and see if I can figure it out. |
4
on: 15 May 2024, 21:17
|
||
Started by EarBiteR - Last post by Roman | ||
Cmpro takes version information from the datfile or when using an exe for import it looks for such information in the created xml output (e.g. Mame‘s -listxml output). Most likely pinmame does not provide such info in its output.
|
5
on: 15 May 2024, 15:32
|
||
Started by EarBiteR - Last post by EarBiteR | ||
On CLRMame 4.048d running via wine on linux it shows the version number and sets/roms counts for MAME. It will show the counts for Pinmame but not the version number. (see pic) If I run pinmame with no parms it shows the version:
PinMAME v3.6.0.964 [MAME 0.76] (May 15 2024) Would you know if this is pinmame issue or clrmame? How does clrmame get this detail? If its due to pinmame then please let me know and I will enter an issue on github-pinmame. Thanks. |
6
on: 13 May 2024, 23:36
|
||
Started by Macdek - Last post by Macdek | ||
Grazie! proverò come mi hai detto.
|
7
on: 13 May 2024, 05:38
|
||
Started by Macdek - Last post by AntoPISA | ||
Ciao, benvenuto sul forum.
È sufficente che tu entri nella cartella selezioni tutti i file e li comprimi in un file con lo stesso nome: snap.zip. Ora togli tutti i .png e lascia solo il file zippato. |
8
on: 11 May 2024, 18:08
|
||
Started by Macdek - Last post by Macdek | ||
Salve a tutti!
Per prima cosa un saluto a tutti gli appassionati del forum! E' il mio primo post su questo forum. Avrei bisogno di un consiglio tecnico. Ho scaricato da progetto-SNAPS il full-set delle snapshots (pS_snap_fullset_256.zip) Al suo interno ci sono: snap.7z che sono gli snap zippati, poi una cartella con Year_Snap.ini al suo interno ed un'altra cartella DATs che contiene pS_Snap_NS_20230728_(cm).dat e pS_Snap_20230728_(cm).dat Non sapendo come utilizzarli in questo formato, ho decompresso snap.7z e aggiunto i .png nella cartella snapshot del MAME. In questo modo si vedono correttamente, ma la cartella è passata da 500 MB a 1.8 GB. Come posso utilizzare il primo formato compresso che occupa 1/3 di spazio? Grazie Alessandro |
9
on: 07 May 2024, 05:53
|
||
Started by BlackPredator72 - Last post by Mucci | ||
ARMAX MAME Dats 0.265 https://www.mameguide.info/MAME_(20240425).7z (Sorry too many things in RL)
|
10
on: 02 May 2024, 17:31
|
||
Started by Roman - Last post by Roman | ||
Well, it was pretty quiet the last weeks...so before you might think that nothing is happening, here is a little peak.
While I was indeed pretty busy with real life I can say that the scanner is still alive, so let's write a bit about it. As you might know (https://www.emulab.it/forum/index.php?topic=9199.0), the scanner does already a pretty good job in scanning uncompressed and compressed sets, no matter how you organized them (plain, in multiple rompaths, in pattern styled subpaths (e.g. by year/manufacturer/etc) and scanning MAME -listxml output (or anything which followes this format), -listsoftware collections and single MAME hash files. It can do a 'new scan' or a 'scan' where the latter takes scan results information from a previous scan into account (similar to current cmpro). And now, it also fixes all found problems. - It is able to auto detect possible missing but fixable files (roms/chds) in your rompaths and in your backup path and everything in one (1) scan and it tries to find a best place for it (as long as you're using one rompath you wouldn't care...but there are people who use pattern-like storage or split chds and roms, etc....) - It detects wrong names (machines/roms/chds) and fixes them of course - It detects unneeded files wherever they are and puts them to the backup path before getting rid of them. It does not automatically zip them as cmpro does (see a thread on this forum about it) but takes over the format from the origin and reproduces the rom path structure inside the backup folder. If a file with the same name but different hash already exist there, the scanner will take care of it. Attached are some screenshots: - one showing the context menus which you can use to modify the output or copy data to the clipboard - one showing an example output of scanning a software list collection (no need for multiple profiles or a complex setup...just scan) - one showing an example output of scanning multiple rompaths and showing complete and partly missing but not fully missing ones... So..what's missing for a 0.01 version - doing some more tests with some different scenarios - a handful of minor nice to haves (still not wanting to add all kind of requests though) - I'm not yet fully satisfied with writing the scanresults file and fix dat file..it works fine but I think I can speed it up a bit - need to write a documentation (yikes) So what's next then after the scanner runs fine? - most likely people will complain about everything, find bugs and have tons of ideas/requests...so I will look into it - next major step then would be to combine rebuilder and scanner and have some kind of profiler |