Jump to content
mizapf

New MAME release

Recommended Posts

Yes, I found the E-mail as well, and actually, nothing has changed in the last 8 years:

 

Quote

Some years ago when working on the existing code I tried to fix it according to what the mouse driver does. I never had the exact hardware specs, so things may still be different than what we see with the real mouse.

 

Have a quick look at the comments at the top of the file

http://git.redump.net/mame/tree/src/mess/machine/ti99/mecmouse.c

Edit: This is now https://github.com/mamedev/mame/blob/master/src/devices/bus/ti99/joyport/mecmouse.cpp

 

So there is a way to confuse the mouse, but I don't know whether and how the real mouse prevents that.


 

So my problem is not to fix a bug, but that I generally do not understand how to avoid the axis swap. Do you have a real Mechatronics mouse? (or anyone else?)

 

Edit: I noticed that TI-DOS crashes for the DDCC-1 controller and the BwG controller; it works for the HFDC and the normal TI controller. I saw that a click causes the axis swap, maybe I can do some investigation there. The problem with the mouse is that you actually cannot set anything, as everything is done via the joystick port. The only action you can do is to select stick 1 or stick 2, and by this way, the axes are swapped. If this is not done properly, X and Y remain swapped.

 

Edited by mizapf
  • Like 1

Share this post


Link to post
Share on other sites
2 hours ago, mizapf said:

Yes, I found the E-mail as well, and actually, nothing has changed in the last 8 years:

 


 

So my problem is not to fix a bug, but that I generally do not understand how to avoid the axis swap. Do you have a real Mechatronics mouse? (or anyone else?)

 

Edit: I noticed that TI-DOS crashes for the DDCC-1 controller and the BwG controller; it works for the HFDC and the normal TI controller. I saw that a click causes the axis swap, maybe I can do some investigation there. The problem with the mouse is that you actually cannot set anything, as everything is done via the joystick port. The only action you can do is to select stick 1 or stick 2, and by this way, the axes are swapped. If this is not done properly, X and Y remain swapped.

 

 

I have one. It didn't do that when it worked, it stopped working a while back

 

Greg 

Share this post


Link to post
Share on other sites
Yes, I found the E-mail as well, and actually, nothing has changed in the last 8 years:
 
Some years ago when working on the existing code I tried to fix it according to what the mouse driver does. I never had the exact hardware specs, so things may still be different than what we see with the real mouse.
 
Have a quick look at the comments at the top of the file

http://git.redump.net/mame/tree/src/mess/machine/ti99/mecmouse.c

Edit: This is now https://github.com/mamedev/mame/blob/master/src/devices/bus/ti99/joyport/mecmouse.cpp
 
So there is a way to confuse the mouse, but I don't know whether and how the real mouse prevents that.

 
So my problem is not to fix a bug, but that I generally do not understand how to avoid the axis swap. Do you have a real Mechatronics mouse? (or anyone else?)
 
Edit: I noticed that TI-DOS crashes for the DDCC-1 controller and the BwG controller; it works for the HFDC and the normal TI controller. I saw that a click causes the axis swap, maybe I can do some investigation there. The problem with the mouse is that you actually cannot set anything, as everything is done via the joystick port. The only action you can do is to select stick 1 or stick 2, and by this way, the axes are swapped. If this is not done properly, X and Y remain swapped.
 
I'm using bwg. You can see in my video

Sent from my LM-V600 using Tapatalk

Share this post


Link to post
Share on other sites

Could it depend on single density vs. double density? I'm normally only using double density, of course. But here, I had to prepare another disk for the TI controller with SD.

 

Now I noticed that the SD works with BwG in TI-DOS, but not the DD.

  • Like 1

Share this post


Link to post
Share on other sites

I seem to remember a weird formatting/copy issue between Myarc and CorComp/BwG controllers BITD. It had nothing to do with the Myarc 16-sector double density--but on disk copies, data appeared corrupted on the other controller. I know this one bit me a few times back when I was still in Germany.

Share this post


Link to post
Share on other sites

Since I'm almost only using DD, this seems more like an exception. Here, it smells a bit like a bug in TI-DOS. Yet another entry on my list.

Edited by mizapf
  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

I just uploaded the recent MAME 0.231 release to WHTech:

 

https://ftp.whtech.com/emulators/MAME/ti99/linux/mame0231b_ti99_linux64bit.tar.gz

https://ftp.whtech.com/emulators/MAME/ti99/raspbian/mame0231b_ti99_raspbian32bit.tar.gz

https://ftp.whtech.com/emulators/MAME/ti99/windows/mame0231b_ti99_win64bit.zip

https://ftp.whtech.com/emulators/MAME/full/macos/mame0231b_macos64bit.zip

 

The only interesting change to previous releases is that I changed the default setting of the floppy drive step rate to 6 or 8 ms on all disk controllers (that allow setting the rate). The previous default of 20ms led to a failure on the Corcomp controller, in conjunction with a too short motor-on time. That is, if you had problems with the Corcomp controllers, you should download this release and just copy it over your existing installation.

 

Edit: Apart from the Corcomp problem, you will also generally notice a slightly faster floppy operation, since the floppy heads move faster now (unless you already chose a shorter step time by yourself).

Edited by mizapf
  • Like 3

Share this post


Link to post
Share on other sites

MAME 231 (and earlier versions) doesn't play nice with my new machine (using an Nvidia graphics card and the proprietary driver) in that starting MAME completely locks up the machine -- I had to log into a virtual console and kill -9 the MAME process.

 

I saw some error messages about ALSA in the terminal window after killing MAME (not sure if they're responsible for locking up). 

Value 1 not supported for option sound - falling back to auto
ALSA lib confmisc.c:767:(parse_card) cannot find card '1'
ALSA lib conf.c:4732:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4732:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4732:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5220:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2642:(snd_pcm_open_noupdate) Unknown PCM default
ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: Permission denied

Is there a way to reset or even auto-detect the mame.ini file?  Can MAME deal with pulseaudio?  Do I need additional permissions?  (I already added my user to the video group, which seems to be necessary for Nvidia.)

 

Share this post


Link to post
Share on other sites

Yes, pulseaudio is now available (-sound pulse). You can delete the mame.ini file and let it be created by -createconfig.

Share this post


Link to post
Share on other sites
6 minutes ago, mizapf said:

Yes, pulseaudio is now available (-sound pulse). You can delete the mame.ini file and let it be created by -createconfig.

Thanks, that option really helped.  I also deleted my mame.ini.  But now I got this error (after a black screen):

cassiopeia ~ > mame -sound pulse
Error opening translation file English
fpa_connect: Access denied

What is fpa?

 

Share this post


Link to post
Share on other sites
Posted (edited)

By the way, mame -showusage lists the options for command line and mame.ini with valid values. Did you recreate the mame.ini?

 

As for the translation file, do you have a folder "language" in your MAME home?

 

I searched the MAME source code, but I cannot find a "fpa_connect". It seems as if this error message is not created inside MAME.

 

(Hast du eventuell Signal, dann können wir das vielleicht schneller abhandeln?)

Edited by mizapf

Share this post


Link to post
Share on other sites

Well, funnily enough, if I omit -sound pulse, the error message is gone, and I still have sound.  (So, OF COURSE, the problem is with pulse.)

 

I re-generated a mame.init file, and everything seems to be working now.  Thanks for your guidance!

Share this post


Link to post
Share on other sites

Hi:

 

If you have access, you might want to make a slight change to the "mameprepcygwin" file on whtech.  The MAME developers no longer use "mame64.exe" as the executable name--they just use "mame.exe".  Not a big deal, and most of us know how to change it. but, thought I'd mention it.

 

Thanks!

  • Like 1

Share this post


Link to post
Share on other sites

That should be covered in the mameprep_cygwin file. The older version is mameprep_cygwin.pre229 (for mame64.exe).

You think of the directory /emulators/MAME/ti99/windows, right?

 

wait ... you probably referred to /emulators/MAME/full/windows. I'll update that.

 

Update: Done.

  • Like 1

Share this post


Link to post
Share on other sites

New release MAME 0.234 has been uploaded to WHTech.

 

There are no changes for the TI emulations, but I took that opportunity to update the genhd01.hd image file for the Geneve boot hard disk so that it contains GeneveOS 7.30.

 

Also, I updated the mameprep scripts to use "mame" instead of "mame64"; I noticed that the mameprep versions that were packed into the tar.gz files for Linux and Raspbian were not updated yet. The 0.234 release should be fixed in that respect.

 

Installation in Linux:

- Don't use the packaged MAME of your Linux distribution; if installed, I recommend to uninstall it.

- Unpack the mame0234b_ti99_linux64bit.tar.gz file in an empty folder

- Run ./mameprep in that folder. It downloads all ROMs, some cartridges, and disks, and prepares start scripts.

- Ready to go, try ./ti99

 

For Windows users, if you have Cygwin installed, you can use mameprep_cygwin for an initial installation.

  • Like 4

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.

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...