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!

Pages: [1]   Go Down

Author Topic: Sysdef Paths  (Read 4351 times)

zitz

  • Member
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 32
  • Operating System:
  • Linux Linux
  • Browser:
  • Firefox 38.0 Firefox 38.0
    • View Profile
Sysdef Paths
« on: 04 August 2017, 15:01 »

Can the sysdef paths be made to auto assign a subfolder for each set ? right now it only assigns a root folder and we have to do it all the hard way manually and its a tedious job
Logged


Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 112
  • Offline Offline
  • Posts: 3287
  • Operating System:
  • Mac OS X Mac OS X
  • Browser:
  • Safari 10.0 Safari 10.0
    • View Profile
Re: Sysdef Paths
« Reply #1 on: 04 August 2017, 15:12 »

the auto assign button action looks in each rompath and mtches the files in there against the database. highest count of files per system wins otherwise first rompath is used. so put some sets in the rompaths and hit autoassign.

iirc this should also work with unpacked sets.
« Last Edit: 04 August 2017, 15:38 by Roman »
Logged

zitz

  • Member
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 32
  • Operating System:
  • Linux Linux
  • Browser:
  • Firefox 38.0 Firefox 38.0
    • View Profile
Re: Sysdef Paths
« Reply #2 on: 04 August 2017, 15:57 »

I made a temp mame folder and dumped some neogeo roms in there. Then i selected neogeo only and clicked auto assign. Only the root folder was assigned, no subfolders were created or added to the rom paths. I tried the move sets options and it did a scan but nothing is created or moved

If i assign my own path to neogeo i came across 2 different results. The first result everything got deleted. The second result when i tried again, it created dozens of cascading subfolders called neogeo and the files were in the very last folder

I have never used this before so i am probably doing something wrong
« Last Edit: 04 August 2017, 15:59 by zitz »
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 112
  • Offline Offline
  • Posts: 3287
  • Operating System:
  • Mac OS X Mac OS X
  • Browser:
  • Safari 10.0 Safari 10.0
    • View Profile
Re: Sysdef Paths
« Reply #3 on: 04 August 2017, 16:22 »

what do you mean with subfolders?
usually you got one rompath per system when using sysdefpaths.
so in settings you have eg setup e:/roms/neogeo as a rompath and in that path you keep the single neogeo sets eg kof.zip, mslug.zip etc.
that rompath can then be assigned to the neogeo system in the systems dialog.

when scanning mame you usually dont work with subfolders.
Logged

zitz

  • Member
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 32
  • Operating System:
  • Linux Linux
  • Browser:
  • Firefox 38.0 Firefox 38.0
    • View Profile
Re: Sysdef Paths
« Reply #4 on: 04 August 2017, 16:25 »

what do you mean with subfolders?

I am trying to get the result from my first question
When i select the set(s) i want and then click auto assign i get eg. e:\roms\mame
I want auto assign to be eg. e:\roms\mame\neogeo   but it will only make the root folder
Otherwise i have to click every single set and make my own subfolder
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 112
  • Offline Offline
  • Posts: 3287
  • Operating System:
  • Mac OS X Mac OS X
  • Browser:
  • Safari 10.0 Safari 10.0
    • View Profile
Re: Sysdef Paths
« Reply #5 on: 04 August 2017, 16:58 »

add e:/mame/roms/neogeo as an active rompath
put a neogeo set eg neogeo.zip in this folder
go to systems and hit autoassign. the neogeo system will be assigned to that path.
for other systems do it accordingly.
cmpro cannot magically guess which rompath belongs to which system. you gotta provide some clues by putting a set into the single paths.

what I wonder is if you need to use sysdefpaths at all. pretty uncommon thing for standard mame.

since Im on holiday with nearly no wlan my answers will be short from now on. maybe other forum readers can help out or you check some of the tutorials.
Logged

zitz

  • Member
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 32
  • Operating System:
  • Linux Linux
  • Browser:
  • Firefox 38.0 Firefox 38.0
    • View Profile
Re: Sysdef Paths
« Reply #6 on: 04 August 2017, 17:21 »

I followed your instructions. The neogeo folder gets deleted and so do the roms when i click "Move Sets"
If i put some neogeo zip files inside the neogeo folder, they still get deleted. Bug ?
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 112
  • Offline Offline
  • Posts: 3287
  • Operating System:
  • Mac OS X Mac OS X
  • Browser:
  • Safari 10.0 Safari 10.0
    • View Profile
Re: Sysdef Paths
« Reply #7 on: 04 August 2017, 18:33 »

as I sad I cannot check your setup for correctness until end of holiday.
I think you somehow setup some paths wrong. On the other hand I wonder what you want to achieve by using the move operation. it will take each file from the rompaths and moves them to the assigned sysdefpaths. so it sounds a bit odd when the neogeo biosset is mived to somewhwre else than the assigned neogeo system path. sounds like a wrong setup.
but anyway.....so is your final goal to split up your collection by systems? if not, you dont need to touch sysdefpaths at all.

so.... to check your setup, you can post or send some screenshots in a week. a mobile phone aint something  for detailed forum explanaition posts
« Last Edit: 04 August 2017, 19:59 by Roman »
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 112
  • Offline Offline
  • Posts: 3287
  • Operating System:
  • Windows NT 10.0 Windows NT 10.0
  • Browser:
  • Chrome 60.0.3112.90 Chrome 60.0.3112.90
    • View Profile
Re: Sysdef Paths
« Reply #8 on: 13 August 2017, 19:34 »

So...back from holiday and made a quick test environment:

1) created 2 folders e:\test1, e:\test2 and put neogeo.zip into e:\test2
2) started cmpro, created a profile for MAME via profiler->create
3) after importing the data I've added the 2 folders as rompaths in the settings dialog
4) Scanner->Systems->Auto Assign

Now all but one systems are assigned to e:\test1 and e:\test2 is assigned to Neogeo Bios set.
This is as expected since cmpro detected the neogeo.zip file in e:\test2 and so took this best fit for the neogeo bios assignment, for the rest nothing was matched, so the 1st rompath (e:\test1) was assinged.

Next step: Hit Move Sets....neogeo.zip stays in e:\test2, as expected. Nothing is removed.
Next step: Manually moved neogeo.zip from e:\test2 to e:\test1 and hit "move sets" again...now, neogeo.zip was moved from e:\test1 to e:\test2 as expected.


So from my side, I don't see any wrong behaviour.
Logged
Pages: [1]   Go Up
 

Page created in 0.115 seconds with 19 queries.

anything