New MAME release

[pjduplooy]

Successfully built on my system.

 

I used ooeygui as base, got 0.265, and overwritten that version with 0.269.

 

Thank you for the very nice instructions on Ninermame!!!.

 

It took a while though as I did not pass -j8 to the compile...

[+dhe]

4 hours ago, mizapf said:

Originally, I designed the HFE image format as generic, usable by all MAME systems,

Thank you for the detailed explanation.

 

Mostly I use TI Image Tool to move disk in to the MAME environment. I do very little file creation within the MAME environment.

[+mizapf]

Yes, I'm using TIImageTool as well 🙂 , but other MAME users do not, especially when they are not using MAME for the TI emulation. My fault ... or, let's say, the suboptimal decision ... was to offer HFE as a generic MAME format. Had I kept it as a TI-only format, the issue would have probably never shown up.

 

On the other hand, HFE *is* a format for a wide range of systems, so it should make sense to go for the generic use.

 

Adding to my previous explanation: We do have some cell-precise formats in MAME like MFI (MAME floppy image) which work for all systems. But these images are only useful inside MAME. HFE, in contrast, is a format that is primarily used for the Lotharek/GoTek floppy emulation. This emulation relies on many parameters, like the floppy interface and other metadata. However, these metadata are not relevant for MAME, and they cannot be guessed from the actual recording. So I have to preserve these data from the given HFE image, or, if the image is created from scratch inside MAME, these data must be correctly created. Otherwise, the image will not be usable in Lotharek.

 

As I said, the solution could be to create several versions of HFE where these metadata are preset. For a TI system, it would be set to "GENERIC_SHUGART_DD_FLOPPYMODE", while for an Amiga, it would be "AMIGA_DD_FLOPPYMODE" and so on.

[JL]

On 8/18/2024 at 7:51 PM, mizapf said:

You're in the wrong command line window. It should read "Admin@DellXPS MINGW64 ~".

 

When you search in the Windows menu, look out for "MINGW64", not for "MSYS2". The point is that there are several variants of the MSYS2 shell with different environment settings, including the PATH.

 

Edit: I shall add that note to my recipe on Ninermame.

@mizapf Huge, Huge Thanks for https://www.ninermame.org/setup/building/winbuild and for all your many posts here on the subject.

I've been using my old custom self-compiled MESS64UI .172 build, yep MESS, (mine includes "No delay" Colecovision Bios ) , since 2016. But wanted to try out many of the changes you've added to TI 99/4a since then. I'd not compiled Mame (or Mess) in 8+ years and had little recollection of how nor knowledge of the new processes and associated requirements. you made it sooooo easy for me.

First did a standard Ninerman build compiled as per your directions all was Perfect   I then added Coleco, Intellivison, Vectrex and some others, again all perfect

 

Taking it further in prepare script I swapped out/changed  "git clone https://github.com/mamedev/mame.git"  to  git "clone https://github.com/Robbbert/mameui.git" then replaced all references of "mame" to "mameui" as needed in all scripts , altered maketi adding "PTR64=1 OSD=messui" to make  command, and compiled it as the UI version. Perfect again 🎉

Please accept my sincere gratitude for all your TI-99/4a development efforts and time !!!


P.S. was my first computer as a child. was crushed when they discontinued it abruptly.

 

Edited September 3 by JL

[RickyDean]

6 minutes ago, JL said:

@mizapf Huge, Huge Thanks for https://www.ninermame.org/setup/building/winbuild and for all your many posts here on the subject.

I've been using my old custom self-compiled MESS64UI .172 build, yep MESS, (mine includes "No delay" Colecovision Bios ) , since 2016. But wanted to try out many of the changes you've added to TI 99/4a since then. I'd not compiled Mame (or Mess) in 8+ years and had little recollection of how nor knowledge of the new processes and associated requirements. you made it sooooo easy for me.

First did a standard Ninerman build compiled as per your directions all was Perfect   I then added Coleco, Intellivison, Vectrex and some others, again all perfect

 

Taking it further in prepare script I swapped out/changed  "git clone https://github.com/mamedev/mame.git"  to  git "clone https://github.com/Robbbert/mameui.git" then replaced all references of "mame" to "mameui" as needed in all scripts , altered makeuiti adding "PTR64=1 OSD=messui" to make  command, and compiled it as the UI version. Perfect again 🎉

Please accept my sincere gratitude for all your TI-99/4a development efforts and time !!!

 

Just be aware that you can still get Mess too. https://www.progettosnaps.net/index.php

This is a site that is listed by Mame. I usually grab all the new one like MameUI and Mess from here.

[JL]

3 minutes ago, RickyDean said:

Just be aware that you can still get Mess too. https://www.progettosnaps.net/index.php

This is a site that is listed by Mame. I usually grab all the new one like MameUI and Mess from here.

Thanks! forget all about them. glad to see they are still there after all these years.

 

I compile my own to use the Coleco no-delay BIOS as well as several other tweaks I did not go into.

[JL]

Folk - how do I get TI-99/4a disk drive to be seen?  Tab menu only showing cassette
 

I did the complete download using mameprep_msys2

[RickyDean]

This is a sample configuration for Mame  from a few pages back, and there are many examples in the thread. D:\mame>mame genmod -window -oslog -bios 1.00 -peb:slot3 horizon -peb:slot5 tirs232 -peb:slot6 tipi -conn rpi.192.168.2.213 -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 DM1000SRC.dsk -flop2 DSDD2.hfe -flop3 DSDD3.dsk -flop4 DSDD4.dsk -serl1 socket.localhost:10000

 

Here's one on mine created by using mameprep in my mame folder 

mame64.exe ti99_4a -ioport peb -ioport:peb:slot2 32kmem -ioport:peb:slot4 pcode -ioport:peb:slot8 hfdc -flop1 disks/ucsd_pascal_editor_filer_1.dsk

[JL]

59 minutes ago, RickyDean said:

This is a sample configuration for Mame  from a few pages back, and there are many examples in the thread. D:\mame>mame genmod -window -oslog -bios 1.00 -peb:slot3 horizon -peb:slot5 tirs232 -peb:slot6 tipi -conn rpi.192.168.2.213 -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 DM1000SRC.dsk -flop2 DSDD2.hfe -flop3 DSDD3.dsk -flop4 DSDD4.dsk -serl1 socket.localhost:10000

 

Here's one on mine created by using mameprep in my mame folder 

mame64.exe ti99_4a -ioport peb -ioport:peb:slot2 32kmem -ioport:peb:slot4 pcode -ioport:peb:slot8 hfdc -flop1 disks/ucsd_pascal_editor_filer_1.dsk

Thanks will give it a try

 

Was able to get it to display in ui tab-io-then setting slots. but get io.error (io 50) when trying to load from ti console command line have not tried via other methods.  will post my caps and other info tomorrow night...

Edited September 4 by JL

[+mizapf]

The easiest way to get floppy access is to connect the Peripheral Expansion Box (peb), then plug in a disk controller (tifdc, hfdc, ccfdc, bwg, or ddcc1).

 

./mame ti99_4a -ioport peb -ioport:peb:slot8 ddcc1 -flop1 mydisk.dsk

 

 

[JL]

^ Thanks!

from "Tab" Menu, this worked.  All good via UI now as well

[+mizapf]

Just a caveat: The TI Floppy Disk Controller (tifdc) is the simplest one and can only read FM (single density) and has no software enhancements. All other controllers can read MFM as well (double density); the Myarc controllers (hfdc, ddcc1) also offer a catalog tool via CALL DIR(<driveNo>) in BASIC.

 

The disk drives 525dd are also useful for single density controllers and have 40 tracks. The 35dd drives are 80-track drives and will turn your disk image to an 80-track image once you write on them.

 

P.S.: Always remember to press ScrlLock again when you are done, since the UI mode reserves some keys for itself, and you would not be able to use them in the emulation. It may have been changed by now, but in earlier releases, the P key was "Pause" in the UI mode, and there were some people who thought MAME had crashed, while it was simply paused.

 

Edit: It was changed to F5. I should update my keyboard map on Ninermame.

[+dhe]

I seem to remember my MAME image (Geneve Genmod) booting to white foreground and blue background (default) - no change in autoexec.

 

Somewhere between updating MAME and updating MDOS to 7.45, I'm getting white foreground on greyish background.

 

Anyone notice this, or just me?

 

Does anyone remember the MDOS command to change foreground and background?

 

 

[+dhe]

Interestingly, the command listed in Myarc's manual,

  Found here: https://ftp.whtech.com/Geneve/GMANUALnoads.pdf

    Show the command to change foreground and background to be:

      

 

 

 

   So compared to the black border the background looks grey not blue?

 

   Any thoughts @mizapf @9640News @InsaneMultitasker

 

 

 

[+jedimatt42]

Screen capture that was posted looks blue on my phone. 

[+dhe]

@jedimatt42 mystery solved, thanks to you.

 

I remotedesktop (windows to windows) to a machine running MAME.  The machine I use to view the remote host had nightlight on.

 

The background in your photo icon was darker than it is with nightlight off, but still very recognizable as blue.

The color blue of the background (kind of a purplish blue) rendered was severally effected to the point of rendering as grey - not a bit of blue shinning through.

 

 Thanks!

 

[+mizapf]

Still AFK. Sitting in the hotel room, awkwardly hacking a few words in my tablet does not count.