sgordon777
-
Posts
24 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by sgordon777
-
-
Even better, I can use a windows shortcut (ie M1.lnk) rather than a copy of the exectuable and achieve the same result
-
Mame has both checked
M1 has neither checked
-
-
First huge thanks to everybody for the ideas,
I got it working by zipping the individual games and add the ROMs folder to the path. -Hope this won't break other emulators, which share the same atari2600 archive.
However, I think I'm going to be in big trouble when I try to get LB to use MAME with Apple2e, where I just have a bunch of disk and caassete images that Mame surely isn;'t going to recognize, as it does with atari2600 files. Mame fully supports this usage pattern:
mame apple2e -floppydisk1 {path_to_my_disk_image_binary} # works perfectly fine
Is there simply no way to have LB start mame as a system and not try to interpret the image it's loading?
What if I renamed mame.exe to something else?
-
30 minutes ago, Kiinkyfoxx said:
Have you tried using that in an external command line? I "think" you are basically passing
yes, also tried just puttibg
a2600 -cart
in the dialog, -same thing
My gut feeling is LB is trying to treat this like an arcade game and put the game name on n commandline. But i cant proove it until i can see the generated commandline.
-
I still cant get it to work...
1-Used "bulk wizard" to change all games in atari 2600 platform to use MAME
2-configured Mame platform as instructed in commandlines page (see below)
However, when I click on a game, say pitfall, it seems like MAME is being started but returns immediately without loading the cart.
I can run all the atari2600 games form MAME commaline, ala:
mame a2600 -cart r:\atari2600\PITFALL.BIN
Any ideas?
Is there some logfile or something so I can try to troubleshoot?
-
Ok, understood and applied. Thanks to everyone for setting me straight!
-
Yep, looks like I was taking the wrong files, I thought I just needed the "bios-devices" set, not the full set (which I now see is much, much larger).
Thanks so much for setting me straight on this, much appreicated!
-
>> ALL the files needed to do so are available in,,,
Very happy to hear that. However, they're not in the .246 full sets *I* have. I've dumped the name of every single archived file in every zip in each full set to a text file so I can search and the files mame is complaining about simply aren't there. I must have a bad copy or somehow am still confused about which sets I'm downloading. I'm using *that* site and qBitTorrent for downloads.
>> And of course you will need the MAME 0.246 executable. Note: mame64.exe is now simply mame.exe
Yes, I am using 246. I use it successfuly for arcade games and some consoles (eg a2600). Your right it is mame.exe, not mame64.exe
Question about how Mame searches for files because I am having trouble with that too, even on the arcade side:
Each fullset is a folder or zip file (depending on how you download it) containing a million other zip files, each containing a bunch of ROM images. What level do I have to unzip these? Where (relative to my /rom folder) do I have to put the files?
-
11 hours ago, Headrush69 said:
your still missing the BIOS/Device roms MAME needs.
I'm still trying to come up to speed on this and likely confused by the terminology, but I thought there were ROMS and SL ROM sets both for "content" and BIOS. I downloaded Both the Romset and SL Romset for "Bios/Devices":
MAME 0.246 ROMs (bios-devices).zip
MAME 0.246 Software List ROMs (machines-bios-devices).zip
I dumped all the zip file from these zips s into two folders, and added the folders to the Mame "rom folders"
When I try to run mame64 apple2e, I get this:
C:\util\mame246>mame apple2e
342-0133-a.chr NOT FOUND (tried in apple2e)
342-0133-a.chr NOT FOUND (tried in apple2e)
342-0135-b.64 NOT FOUND (tried in apple2e)
342-0134-a.64 NOT FOUND (tried in apple2e)
342-0132-c.e12 NOT FOUND (tried in apple2e)
Fatal error: Required files are missing, the machine cannot be run.
(Note, some systems do run, ie a2600 works fine)
When I searched the above files recusively, I still didn't find the required files to emulate apple2e (mame is telling me what files it needs when I try to run it, ie: mame64 apple2e)
I *was* able to finally get the emulated apple2e booting, but not util after manually collecting the required files from over the internet and my old collection of MESS zips to piece together the BIOS files needed and sticking them into rom/apple2e folder. I did NOT find the required BIOS files in either my Merged
Another issue I had is that the core is really stupid about looking in zip files... I had to literally take individual files out of .zip archives and stick these files directly in the rom/apple2e folder. SOmetimes the system would look in .zip files, sometimes it wouldnt, it seemed to depend if the .zip files had the name "apple2" in it?
-
I was told to do this and downloaded the "SL" ROMset, but ie seems that support for computers is a joke. For Apple2e more than half the required files are missing.
I managed to get it to work for apple2e by searching google for the missing files and going on a wile goose chase to a bunch of random trashy sites to download the files one by one, but what a mess and I'm afraid to even try it for the other 10 or so computers and consoles I want to emulate.
Does anyone else use MAME for emulating computers like apple2, c64, amiga, and consoles like atari2600, atari800 and others
Is there another ROMSET I can try (I got 246 SL)
-
I was told to do this and downloaded the "SL" ROMset, but the support for computers, like Apple2e is a joke, half the required files are missing. I'm asking in case maybe I'm doing something wrong or downloaded the wrong files. As someone who used MAME a while back, the whole situation now just seems confusing and frustrating. I can't find consistent information about anything anywhere but I want to give it a chance if it can work.
-
12 minutes ago, sgordon777 said:
Thanks for your reply. I use MAME for arcade games and my intention was to use it for the computer emulations too, but I simply cannot get it to work reliably with any computer BIOS without running into tons of problems, It's extremely stupid about where to look for files, won't even look in zips. Even if I unzip everything and put it in the root "roms" folder it still doesn't work.
Do people actually use MAME for Home computer and console emulation? If so, I'll take another look
Also, even if I could get MAME to work without pulling all my hair out first, won't I run into the same problems once I want to use MAME64.exe to be the emulator for more than one platform?
-
15 minutes ago, neil9000 said:
First of all i would recommend using MAME, mess and mame were merged into one program some years ago. As for the actual issue that is what the "associated platforms" tab we are discussing in your other thread is for, you can add as many platforms as you want to your mame emulator entry there, and each can have its own command line parameter, to load the actual core/bios that platform requires.
Thanks for your reply. I use MAME for arcade games and my intention was to use it for the computer emulations too, but I simply cannot get it to work reliably with any computer BIOS without running into tons of problems, It's extremely stupid about where to look for files, won't even look in zips. Even if I unzip everything and put it in the root "roms" folder it still doesn't work.
Do people actually use MAME for Home computer and console emulation? If so, I'll take another look
-
Just now, neil9000 said:
You can literally type anything you like into the box with your keyboard.
Hmm. I tried that but it didn't "take". It only would allow me to pick existing emulators.
-
I've worked around this insane problem by finishing the platform creation without adding an emulator, then going back later and adding/associating the emulator later.
-
Ok, let's say I want to use the same emulator for different platforms (ie MESS).
This requires that I pass different arguments for different platforms to the same emulator.
An example is MESS, which requires per-platform arguments:
mess a800
mess c64
mess a5200
The problem is, I seem to only be allowed *ONE* commandline argument per emulator in the Tools/Mange emulators/Configure emulator menu.
The only workaround I can find for this would be to have multiple copies of mess, and treat it as different emulators. I hope there's a better solution.
-
>> SImply clock on the associated platform tab and add the platform there
There's no option to "add" a platform, only to choose an existing one, which I can't do because I am literally part-way through creating the platform. It's mind-numbingly insane...
-
>> In the Associated Platforms tab you have to enter the name of the platform. It must match how the name is displayed in LB/BB.
The platform isn't there yet, Im creating it!!!!
-
Trying to add ROMs for a new platform, and get this confusing message after I type in my emulator name, and path to my emulator's exe (WinUAE)
Same emulator, multiple platforms
in Noobs
Posted
Thanks again for the help