Jump to content
mizapf

New MAME release

Recommended Posts

Here are the ROM's I have in my Geneve.zip - Which lives in the rom directory.

When I boot, I get the original swan boot eprom. Have you 'certified' the new version 2.0 boot eprom?

 

 

 

 

image.png

Share this post


Link to post
Share on other sites

No, I did not yet include 2.0. I'll try to get it into the next release, but I can't promise.

Share this post


Link to post
Share on other sites

Delivered as ordered. However, I'm not sure whether this appears in 0.238 or 0.239; there is already a branch for 0.238 on Github, so I may be too late. 😞 But then you'll have it shortly after Christmas (if that counts).

 

0041.png

  • Like 2
  • Thanks 2

Share this post


Link to post
Share on other sites
19 hours ago, dhe said:

Here are the ROM's I have in my Geneve.zip - Which lives in the rom directory.

By the way, it seems as if you re-packed the geneve.zip file. I suggest not to re-pack the zips. You just drop the respective zip files in your rompath (ti99_bwg.zip, ti99_fdc.zip, ..., ti99_speech.zip). I'm not sure whether the MAME core actually searches e.g. the floppy controller ROMs in geneve.zip; I don't think so.

Share this post


Link to post
Share on other sites

Does mame deal with just the bin files, or does it need them to be zipped, to be happy?

Share this post


Link to post
Share on other sites

It can handle both. You can put the contained dumps in the rompath, and you can keep then in the ZIP files. I'm not sure about the order of searching when it finds e.g. bwg_dsr.u15 as a file in the rompath, but also inside the file ti99_bwg.zip.
 

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

OK, I had a closer look, doing a test with ti99_ddcc1.zip which only contains ddcc1.u3. I started ti99_4ae, the 50Hz variant.

 

Rompath is mame/roms/

 

This is the search order where the MAME core looks for the file ddcc1.u3. It also means that the occurrance in a lower number shadows the occurance in a higher number.

 

0. mame/roms/ddcc1.u3: not found

1. mame/roms/ti99_ddcc1/ddcc1.u3

2. mame/roms/ti99_ddcc1.zip

3. mame/roms/ti99_4ae.zip

4. mame/roms/ti99_4a.zip

 

So it eventually searches the dump in the driver file (ti99_4a.zip), but the search will stop in a lower number when the file is found there.

  • Like 1

Share this post


Link to post
Share on other sites

Usually names matter.

You say: bwg_dsr.u15

I have: bwg.bin

 

How does mame know what ROM is to be used for what? (ie.. wouldn't want to try to boot the geneve with the BWG ROM) 😃

 I'm guessing .u15 is the chip designation on the board, which is a concept I really like.

Share this post


Link to post
Share on other sites

In MAME, hashes matter more (CRC and SHA1). The socket designation is a MAME standard that I adopted a while ago when I reorganized the dumps.

 

Remember that the end user shall be able to dump the own ROMs to use them in MAME. So the file names give you a hint which circuit you have to dump.

  • Like 2

Share this post


Link to post
Share on other sites

Hi,

 According to this page: https://docs.mamedev.org/usingmame/defaultkeys.html

`~ should get my back to the system menu.

 

But.. That doesn't seem to work for me? (It's captured by the emulator).

 

image.thumb.png.8473b77853373f068418ab95a4ef167d.png

 

Here is the bat file, I'm using to call up the geneve emulation.

D:\mame>mame geneve -peb:slot4 memex -peb:slot3 horizon -peb:slot5 tirs232 -peb:slot8 hfdc -peb:slot8:hfdc:h1 generic -peb:slot8:hfdc:h2 generic -peb:slot8:hfdc:h3 generic -peb:slot8:hfdc:f3 525dd -peb:slot8:hfdc:f4 525dd -hard1 genos7boot.HD -hard2 Bootdisk2.HD -hard3 Bootdisk3.HD -flop1 DSDD1.dsk -flop2 DSDD2.hfe -flop3 DSDD3.dsk -flop4 DSDD4.dsk -serl1 socket.localhost:10000

 

I would also like to thank the romgods for updating geneve.zip today.

 

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, dhe said:

Hi,

 According to this page: https://docs.mamedev.org/usingmame/defaultkeys.html

`~ should get my back to the system menu.

 

But.. That doesn't seem to work for me? (It's captured by the emulator).

You seem to be in full keyboard mode, try to switch to partial mode first. ("UI controls enabled", this is ScrlLock for me).

Share this post


Link to post
Share on other sites

Much closer, but I still can't figure out the magic incantation to soft power down the machine (F2?)

Left-Alt - to go from Full Screen (my startup mode) to Windowed.

ScrLock - Enables UI Control.

 

image.thumb.png.0d57650b5830a05a7a32eae983fe862e.png

Share this post


Link to post
Share on other sites

Believe it or not, I never used this on-screen mini display at the bottom of the page that pops up with that tilde key... I did not even know about it.

 

I guess by "soft power off" you mean "F2: Power the machine off for machines that have specific power button behavior." (I did not know about this feature either.) This is not defined for the Geneve.

 

When I want to stop the emulation, I usually close the window or press Esc in partial mode.

 

If you add "-window" in your command line you can launch the emulation in a window right from the start.

Share this post


Link to post
Share on other sites

>When I want to stop the emulation, I usually close the window or press Esc in partial mode.

Ok.

I'm just used to:

   Ejecting USB Drives before pulling them.

   sync, sync shutdown -h now <- on Linux

   Or shutdown and wait till the machine powers of in Windows.

 

I guess on the geneve emulation, as long as I don't shut it down while it's actively writing to the HD image, I don't have to worry about 'cached' writes - not getting flushed to disk. 😃

 

 

  • Like 1

Share this post


Link to post
Share on other sites

Your caution is certainly good. For MAME there is no need, actually: Closing the window or stopping the emulation by ESC is specifically handled, in particular with floppy or hard drives being written back. During runtime, floppy images are only accessed in memory, and on termination of the emulator they are written back.

 

MAME cannot guarantee for data integrity within the emulation (it cannot know whether all operations are complete), so this F2 key may be used to trigger a shutdown to be handled by the emulated system. Again, this is not necessary for the Geneve, as it does not use write-back caches. All operations are done synchronously.

  • Like 1

Share this post


Link to post
Share on other sites

Sorry, too late indeed; today is the last Wednesday of November - release date of 0.238.

 

SCSI will be included in the next release, 0.239, due Dec 29. You can, of course, build from sources. I can - if desired - upload an interim build on WHTech. In the meantime I can figure out how to get block DMA working.

  • Like 3

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...