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

Pages: 1 2 3 4 [5] 6 7 8 9 10 ... 179
81
clrmame Discussion / Re: clrmame 0.3 released
« on: 14 March 2025, 12:55 »
That would be great. Actually, when fixing is still at 0% it's still in the "fix missing rom" phase so when files are added to a rompath from either backup, addpaths or from a different set....
The fix order is like:

- per machine
  - fix missing roms, fix missing disks
  - fix wrong named roms/samples/disks
- fix wrong named machines
- fix unneeded

so if fixing was at 0% for you I'd assume it was still in the fix missing part...(e.g. that also happens when a sl like the amiga 1000/3000 is renamed, the folders themselves are unneeded but the files are used for fixing/adding them at the correct place.

82
clrmame Discussion / Re: Problem Scanning an SMB Volume
« on: 14 March 2025, 08:09 »
Seems that a std::filesystem::directory_iterator (c++ stl function to run access all files within a folder) throws an exception for "." (the current folder) for whatever reason. I will have a look why it creates that error (since it works on a 'standard' Windows drive :-)). I will check if using "." can be changed or check why it could fail with your setup.

83
clrmame Discussion / Re: clrmame 0.3 released
« on: 13 March 2025, 08:35 »
Hmm...ran some tests with the amiga 274-275 changes but currently I wasn't able to reproduce the problem (or even hit a crash once).

I will double check the backup fixes which came in from .2 to .3 if they can have a sideeffect. The problem back then was that when backuping it created endless subfolders, e.g. if a software list A was unneeded and contained A1 to A100 archives, it created a backup folder A\A1 then A\A1\A2 then A\A1\A2\A3 and so on.....instead of having the files simply stored in A....the fix is like 2 lines of code....and should end in a crash....but again...I will do further checks.

If you are able (or even have time) to reproduce the problem with a small setup, let me know....

84
clrmame Discussion / Re: clrmame 0.3 released
« on: 12 March 2025, 19:36 »
If I remember correctly there were some amiga sl lists which were renamed/merged to a new list in last MAME release....so the original folders became unneeded and should be moved to the backup folder....before they should form the new folder though....I will have a look if I see something obvious when replaying that scenario.
There is a change in .3 which affects building the backups (which was wrong before ;-)) ...maybe that hit something weird....

Thanks for the feedback.

85
clrmame Discussion / Re: clrmame 0.3 released
« on: 12 March 2025, 16:28 »
Hmm..sounds indeed like a crash. However there weren't that many changes from .2 to 3(1) which fall into that time window of starting fixing...

Could be a corrupt archive or something. Do a scan (without fix option enabled) and check the output which machines require fixing. So you may get an idea which files are affected. Maybe only a few are listed so testing would be not so time intensive...

When fixing is enabled, you can also try to enable log level "trace"...but if it simply shuts down it will be hard to see the log...so maybe you can use Windows' Snipping Tool to record a short movie ;-) So you might get an idea where it crashes.

By the way: there is no difference in roms or software lists internally.

Would be really interesting to find out which file is causing the problem. So would be great if you can somehow minimize the problem and contact me / send me the file in question.

86
clrmame Discussion / Re: clrmame 0.3 released
« on: 03 March 2025, 18:03 »
Looks like I broke the showing of empty and complete items in clrmameUI 0.3 ...get a fixed one here: https://mamedev.emulab.it/clrmamepro/binaries/clrmame_v031.zip

87
clrmame Discussion / Re: clrmame 0.3 released
« on: 28 February 2025, 08:51 »
Again: For software lists, you don't need 700+ profiles/xml files.

You can simply run a mame -listsoftware based scan. Specify just one folder as rompath. This folder is the parent of the sl folders (a2600,....)


88
clrmame Discussion / Re: clrmame 0.3 released
« on: 27 February 2025, 07:19 »
Hmm..don't know if I understand your questions correctly...

A batcher is planned for the (far away) future but surely you can write and run a shell script for the commandline version which runs over multiple xml files.
Unique xml files for softwarelist? Either you use a -listsoftware MAME export for all sl data in one file or you simply use the single XML files in MAME's hash folder.
chdlist? What should that be? A standalone datfile for chd files? For what? But most likely such things are floating around in the internet.

89
clrmame Discussion / clrmame 0.3 released
« on: 26 February 2025, 19:26 »
https://mamedev.emulab.it/clrmamepro/binaries/clrmame_v031.zip
https://mamedev.emulab.it/clrmamepro/binaries/readme.html

UI:

added: optionally hide/show roms/disks/samples output via context menu
fixed: remove datasource XML file when hash folder changed (should only happen when XML file was internally created from an exe export)

Core:

added: "available:" filter which limits the machine selection to files you have. You might notice a count difference in total vs filtered even when you got all files. This is based on the fact that a) empty sets are excluded and b) there are clones which are totally included in their parent, so -in split mode- you don't have a standalone file/folder for it. So don't worry about the count.
misc: "file:" filter, in case you work with softwarelist collections, you'd need to prefix single entries with sl-name#pacman (e.g. a2600#pacman) to specify which set you're refering to. Not needed for single sl files or standard dats though.
misc: some earlier cancel returns in fix wrong named disk/sample/rom/machine
misc: dupe output now shows all found paths belonging to a machine
misc: updated spdlog to 1.15.1
misc: limited AUTO thread switch to 25 threads as max (or less depending on your hardware). You can still manually select more or less if you like
fixed: dupes can be listed multiple times
fixed: backups for unneeded folders can create wrong and very long folders due to wrong encapsuling
fixed: backup can miss empty unneeded folders at first scan
fixed: fill-in file from addpath/backup path was removed (when requested) even when fill-in copy failed and you might had a 0 byte new archive
fixed: log pattern in commandline mode

90
well...of course you could create an xpath filter which does not include "NOT WORKING" machines which contain disk files....if there is a good indicator for it...which I somehow doubt.....

91
I've added it some time ago already since you requested it some time ago, didn't you :-)
No workaround at the moment
Next version with the next MAME version I guess.....

92
The next version will have context menu options to show/hide roms/disks/samples.

93
clrmame Discussion / Re: Old samples dat needed
« on: 24 February 2025, 10:23 »
That won't work for sample since MAME's XML does not hold any size/crc32/sha1 information for the samples. The created fix dat won't list them with hashes, just with their names.

You can use dir2dat on an existing folder...but then you need to be sure that the folder contains correct files.

94
clrmame Discussion / Re: ClrMAMEPro / MAME 0.274 Issue
« on: 20 February 2025, 06:49 »
clrmame uses the temp folder only when it needs to decompress data temporarily.

This is done when
a) an archive is in an archive
b) adding files to an archive to another where the archive types differ (e.g. 7z to zip, rar to 7z) or when copying data from 7z to 7z archives. A direct zip to zip operation does not require a decompress (unless you don't force it in rebuilder->recopress), so that's one of the main reasons why people should think about using zip...in 2025 multi terabyte hds are cheap, so getting some gb extra by using soldid 7z is  -in my opinion- pretty obsolete. The wasted time is more expensive :)

By default the system's temporary folder is used (%TEMP%, which usually points to "C:\Users\your_user_name\AppData\Local\Temp").

To quote the readme file: "You can alter the temporary folder by modifying the "TempFolder" entry in settings.xml". So open the settings.xml file with an editor and look out for <TempFolder></TempFolder> and insert your prefered one.


....and all created temporary files will be removed on exit

95
clrmame Discussion / forum posting problems
« on: 14 February 2025, 11:36 »
This forum uses some spam protection for some time which can cause problems when you try to post.
Since I'm not the operator of the forum, I can't do anything about it, but here are some hints which might help you:

When you see a "session timed out while posting" message, you can simply hit the post button again which usually refreshes the session and pushes your message.

When seeing a "CleanTalk: *** Forbidden. Please enable JavaScript. Browser seems to be spambot. Anti-Spam by CleanTalk. ***" message, you can either try to change your text or copy your written text, logout, clean cookies and relogin and add your text again. Usually your post is accepted then.

96
clrmame Discussion / Re: Site Problems
« on: 14 February 2025, 07:10 »
If you get a session timeout you can simply hit post again....it usually accepts it then.

97
clrmame Discussion / Re: ClrMAMEPro / MAME 0.274 Issue
« on: 14 February 2025, 07:09 »
hmm..interesting...but if you say a mame.exe -listxml doesn't work on your system, well, there is your answer.
It shouldn't be a problem to find such redirected outputs in the internet which then can be used as datfiles in clrmame/clrmamepro

98
clrmame Discussion / Re: Site Problems
« on: 13 February 2025, 12:28 »
logout, relogin and try again.....and what error do you get....and Edge works fine (just using it at the moment)

100
clrmame Discussion / Re: ClrMAMEPro / MAME 0.274 Issue
« on: 12 February 2025, 08:05 »
Well, the screenshots actually describe what is happening. Your MAME executable file produces a bad or no XML output when it is called. clrmamepro calls it either with -listxml or -listsoftware and redirect its output to a temporary folder.
You can check what was exported by looking at the mentioned temporary place if the file is there or cut off. You can try to delete it if it's there and try again. Check access rights etc. Are you using the official MAME binary or a 3rd party built one? You can test the output yourself by running mame.exe -listxml > test.xml and check it.
And of course you can use such an exported xml file as input for clrmamepro, too.

This does not happen with the official mame binary on a let's call it 'standard PC'.

Pages: 1 2 3 4 [5] 6 7 8 9 10 ... 179

Page created in 0.071 seconds with 21 queries.