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 ... 172
1
https://mamedev.emulab.it/clrmamepro/binaries/clrmame_007_014.zip

https://mamedev.emulab.it/clrmamepro/binaries/readme.html

UI:

misc: scanner, contextmenu option to sort by name instead of description
misc: Linux/Wine, users can get data from a (linux) mame binary. A wrapper script is included (requires a chmod +x ./wrapper.sh once though)
misc: Linux/Wine, minor changes regarding line breaks or layout

Core:

misc: in case of a -listsoftware data basis (either exe export or dat), additional sl hashes are added from either the used exe's hash folder (prio 1) or HashFolder specified in the settings xml file (prio 2).
fixed: some absolute paths aren't made 32k path length aware, this can lead to sideeffects, e.g. when doing backups (esp. in Linux/Wine)
fixed: scanner, removal of matched files from addPath/backup only works when at least one file was missing
fixed: scanner, removal of unneeded files stopped after first error during a delete process so that other files in the queue were skipped
fixed: scanner, fixing wrong named files/folders which only differ by a character case change fails
fixed: scanner, unneeded sample files are detected but not reported or fixed
fixed: scanner, (rare) "can't read" error message when accidently testing a folder for being a chd
fixed: scanner, (rare) fixing wrong named files/folders which only differ by a character case but map to multiple machines keeps only 1 instance (e.g. 3DO->3do & 3dobios)
fixed: scanner, circular renames inside a machine throw rename errors and only get resolved in a second run

2
clrmame Discussion / Re: Nightly.....
« on: 31 October 2024, 06:15 »
Already on my list for a long time since I miss it too. It‘s not in yet since it would require also loading the datfile because I don‘t keep information about good machines and all the meta information like year, manufacturer and so on in the scan file. It only holds the issues. Also depending on how many issues are shown, bullding up the tree can be slow.
So I kept the request for „when the profiler is ready“. It will come….will see what I can do

3
clrmame Discussion / Nightly.....
« on: 27 October 2024, 18:32 »
While playing around with the Linux MAME export I totally forgot to say what else is new in the nightly build:

https://mamedev.emulab.it/clrmamepro/binaries/clrmame_006_013_20241027.zip

UI:
- misc: scanner, contextmenu option to sort by name instead of description
- misc: Linux/Wine, users can get data from a (linux) mame binary. For this, a wrapper script is included. You need to do a chmod +x ./wrapper.sh once though
- misc: Linux/Wine, minor changes regaring line breaks or layout

Core:
- fixed: scanner, unneeded sample files are detected but not reported or fixed
- fixed: scanner, rare "can't read" error message when accidently testing a folder for being a chd
- misc:  in case of a -listsoftware data basis (either exe export or dat), additional sl hashes are added from either the
used exe's hash folder (prio 1) or HashFolder specified in the settings xml file (prio 2).

A big "thank you" goes out to Shoegazer for the linux testing and finally pointing me in the right direction to fix the (hopefully) last outstanding problem.

So what's next?
Well...the upcoming week will most likely bring a new MAME version. As usual, I will check the scanner/rebuilder core with it to see if something weird pops up. So expect a new 'official' release after the MAME release.

After that I hope I finally find time to start with the profiler....that's the short view...on the long view I was also thinking about a batcher (currently I wonder if there is something which a profiler can already do, i.e. loading and scanning multiple dats, but I also have some ideas for a batcher which would act like a scheduler where you add your scan/rebuild jobs in a queue like thing....time will tell...profiler comes first).
And yes....I'm still sure to release the source :-)

4
clrmame Discussion / Re: clrmame first-run questions
« on: 23 October 2024, 19:34 »
ok here we go, a new round of Linux/Wine testing

https://mamedev.emulab.it/clrmamepro/binaries/clrmame_006_013_4.zip

after unpacking you need to do a "chmod +x ./wrapper.sh" to make the wrapper script executable.
Basically that's it...after that you should be able to import from a linux mame binary (at least it works for me on Ubuntu / Wine running on a virtualBox ;-))


Update (since a virtualbox seems to react a bit more differently than a real one....)

https://mamedev.emulab.it/clrmamepro/binaries/clrmame_006_013_5.zip
https://mamedev.emulab.it/clrmamepro/binaries/clrmame_006_013_6.zip

Played a bit with export timing and added some information on trace log level....Shoegazer, please let me know if this leads to something, if not, trace level output would be interesting to see....

5
clrmame Discussion / Re: loveber3cn Missing Set ARXMAX
« on: 23 October 2024, 16:20 »
EXPECTED: CRC(9e519dc6) SHA1(69a1efc81c9dc44fcb8fc9c17bd7f879d3259950)
       FOUND: CRC(60f56bf2) SHA1(35e697aca7213e3fb1ebe75bb8991b1b992af6d9)

Clearly says you don't have the right rom for the mentioned one.

But it doesn't matter since the game is not emulated in a way in MAME that you can use it.
So even if you have the right rom, it won't won't.

Besides of this, MAME emulation issues or Flycast or DEMUL topics do not belong to this forum.

6
clrmame Discussion / Re: clrmame first-run questions
« on: 22 October 2024, 19:27 »
Erm….you cant do anything at the moment…you need to wait for a new (test) version which makes use of the wrapper script…

7
clrmame Discussion / Re: clrmame first-run questions
« on: 22 October 2024, 09:16 »
Forget about what I said regarding settings.xml...it will work out of the box since I can detect if I run under Wine or native Windows. So it's either using the wrapper script or not.

Currently I only have 2 1 issue:

- running the script returns too early (so mame is still exporting the xml data but the script already signals a run completion) (technical background: in Windows you'd have the same problem, but there I can use PipeObjects to grab the data......but no worries...I'm playing around....)
- the script file needs to get a one time chmod +x....actually it should be possible to already add that in the zipfile somehow...will see

8
clrmame Discussion / Re: clrmame first-run questions
« on: 21 October 2024, 18:58 »
well, actually I made a little bit of success....I wrote a wrapper script file which is able to convert given wine paths to real linux paths, changes to the folder, runs the export. Yippie....this can be triggered from the wine clrmame executable.

Current problem is that the process is returned as being finished too early, so clrmame says that it can't read the export (which is still exporting). Another click on scan will then find the now finished export...

Close...but not fully there...but I guess it can be done....


Interested in the script?

w2l() {
  wine_path="$1"
  if [[ "$wine_path" =~ ^([A-Z]):\\ ]]; then
    drive="${BASH_REMATCH[1]}"
    linux_drive=$(readlink "$HOME/.wine/dosdevices/${drive}:")
    linux_path="${wine_path/${drive}:\\/$linux_drive/}"
    linux_path="${linux_path//\\//}"
  else
    echo "no valid wine path"
    return 1
  fi
  echo "$linux_path"
}
linuxExeFile="$(w2l "$1")"
linuxOutFile="$(w2l "$3")"
folder="$(dirname "$linuxExeFile")"
base="$(basename "$linuxExeFile")"
cd "$folder"
$base "$2" > "$linuxOutFile"

so you give in z:\home\vboxuser\something\mame -listxml z:\home\vboxuser\somewhereelse\blaexport.xml
...and it should work in Linux :-)



....well...and you'd need to tell clrmame to use the wrapper...guess that'll be a simple entry in its settings.xml then

9
clrmame Discussion / Re: clrmame first-run questions
« on: 18 October 2024, 07:46 »
well...I ran some tests with the wrapper script but it didn't lead to anything useful yet.....
...and then real life came back and kept me busy this week.

10
You're most likely not using the correct storing method

rompath\setname\file 1...file n for decompressed sets
rompath\setname.zip (.7z/.rar) for compressed sets

An example: the set pacman consists of various files, pacman.6e, pacman.6f and so on....let's assume c:\temp\mame\roms is your rompath (which would be listed in clrmamer, too) you need to store the files:

c:\temp\mame\roms\pacman\pacman.6e, c:\temp\mame\roms\pacman\pacman.6f etc...or
c:\temp\mame\roms\pacman.zip where the zipfile holds the single pacman files.


The same rules apply for any datfile. So look at your used datfile, check how the sets are organized. Most likley you have individual sets with 1 iso file each....and since I assume you don't want to compress the isos, you'd need a subfolder per set.
....or you modify the datfile to keep all isos in 1 set....

11
clrmame Discussion / Re: clrmame first-run questions
« on: 04 October 2024, 06:51 »
Ok....I think I've found something about the problem behind it. After running my test builds on a virtual box in wine, I see that the process handle is invalid and so waiting for it fails.... Searching the internet gives me "Native *NIX processes won't have process handle - they are run outside Wine."
Asking an AI gives me a workaround by using a wrapper script....

#!/bin/bash
"$@" &
echo $! > /tmp/myprocess.pid
wait $!
rm /tmp/myprocess.pid

so my createProcess call runs the wrapper script and passing the actual command to it and waits for its completion. The script itself then runs my given commandline...

hmm....surely this would only needed on Linux/Wine (i.e. it would take some option/mechanism to activate it and is deactivated by default for normal windows users).
I will play around with it a bit


hmm...no luck yet.....seems that Wine users need to use datfiles ;-)
But maybe somebody has an idea

12
clrmame Discussion / Re: clrmame first-run questions
« on: 03 October 2024, 20:21 »
Thanks for testing, the info and the files. Actually the log tells me a lot.
Looks like WaitForSingleObject (https://learn.microsoft.com/en-us/windows/win32/api/synchapi/nf-synchapi-waitforsingleobject) (the function used to wait that the export process finishes) returns something which isn't WAIT_TIMEOUT or WAIT_OBJECT_0 (which both would have triggered a different log output and would be normal during the export) but WAIT_ABANDONED or WAIT_FAILED. The exception about the remove:sharing violation is also clear then since if that WaitForSingleObject  fails it tries to remove the already created output file which is blocked.

So I will look a bit more deeply into the return values of WaitForSingleObject and I will try to run it on linux/wine....

thanks for your help...I will come back when I got something new to test ;-) ....unlikely to be this week/weekend...

by the way, the spam bot (which isn't mine by the way) usually can be beaten by login/relogin

13
clrmame Discussion / Re: clrmame first-run questions
« on: 03 October 2024, 12:56 »
Shoegazer,
https://mamedev.emulab.it/clrmamepro/binaries/clrmame_006_013_debug.zip

this simply prints out some more logger infos when the export is done...to find out where it runs into the exception.



On a side note, I plan to install an Ubuntu or whatever on a virtual box....so...what are you using and which MAME version do you use (maybe you can simply zip up your mame folder so I can quickly start testing it under Wine.....

14
clrmame Discussion / Re: clrmame first-run questions
« on: 03 October 2024, 11:22 »
and it works when you don't specify a parameter like -listxml ???

This is weird since it automatically adds "-listxml" when no parameter is given. So no matter if you specify -listxml in the XML/EXE box or not, it will always run mame -listxml.

15
clrmame Discussion / Re: clrmame first-run questions
« on: 02 October 2024, 20:27 »
Hmmm failed due to remove:sharing violation.
I‘ve also added the print out of the exception ‚what‘ string…..
Will check if this helps me…

But -listxml is working for you???

16
clrmame Discussion / Re: clrmame first-run questions
« on: 02 October 2024, 19:45 »
ok..here we go again

https://mamedev.emulab.it/clrmamepro/binaries/clrmame_006_013_3.zip

I do change into the folder which holds mame but I now run it as ".\mame ..." ...let's see if this brings up some softwarelists in Linux....guess you need to remove that 0 byte file first

17
clrmame Discussion / Re: clrmame first-run questions
« on: 02 October 2024, 18:39 »
Hmm actually I do change the current dir to the mame folder before running the export….I will do some tests/double check that.
Mame needs its hashfolder to create a listsoftware output. For listxml nothing is needed.

18
clrmame Discussion / Re: clrmame first-run questions
« on: 02 October 2024, 16:22 »
hmmm...looks like the export created a non valid file "661de8ad-listsoftware.xml" in the exports folder.
Can you check the file? Does it exist? Is it > 0 byte? Is it a valid XML....
(the filename is the crc32 of the used mame executable plus the used command by the way)

"can't run: Z:\home\testing\Emulation\Emulators\MAME\mame -listsoftware" indicates that executing this fails...wonder what's happening there since -listxml does work for you, doesn't it?


I mean...can you run a mame -listsoftware on your own or does it simply fail without clrmame involved, too?

...or maybe an access right issue?....I blame Linux :)

20
clrmame Discussion / Re: clrmame first-run questions
« on: 02 October 2024, 06:31 »
gimme some minutes...the regular expression which parses the path/exe and command uses a ".exe" to split application from parameter....

shouldn't be too hard to fix for Linux...

If no param is given, it doesn't split and internally takes -listxml :)

Pages: [1] 2 3 4 5 6 ... 172

Page created in 0.059 seconds with 14 queries.