Jump to content

mizapf

Members
  • Content Count

    3,758
  • Joined

  • Last visited

  • Days Won

    3

mizapf last won the day on August 31 2016

mizapf had the most liked content!

Community Reputation

2,698 Excellent

About mizapf

  • Rank
    River Patroller
  • Birthday 09/24/1969

Profile Information

  • Gender
    Male
  • Location
    Germany
  • Interests
    MAME, TIImageTool, Ninerpedia
    Linux advocate (openSUSE/KDE)

Recent Profile Visitors

16,250 profile views
  1. Interestingly, while checking this, I found an obviously long-standing typo (6+ years) in MAME which made it impossible to switch the CRU base. You can now (next release) insert two RS232 cards and configure their CRU bases in the OSD. And yes, it proves the mentioned handling of a single card at 1500.
  2. My favorite one is missing: 83C4 = -31804 This is the interrupt hook. You can instantly start a machine language program this way without using the DEF table. You should clear 83C4 as the first action.
  3. This one? http://www.mizapf.eu/files/myxbdoc.pdf (Don't remember where I got it from)
  4. With some affinity to nitpicking, I'd say that "emulate the DSR" is not quite the MAME idea of emulation. The way to go would be to fake a device that runs this DSR.
  5. Yes, MAME tries to guess the interleave and gaps. Check the comments at the beginning of https://github.com/mamedev/mame/blob/master/src/lib/formats/mfm_hd.cpp I'm not sure how you plan to do a byte-by-byte copy. The locations inside the CHD are not as simple to calculate as with a DSK image. The CHD has a lookup table where the hunks are located. Also, you would need a full CHD support in your tool that cares for allocating new hunks etc. The easiest and fastest way would be if I wrote a support for DREM in TIImageTool, but due to my current workload this is not going to happen within the next weeks.
  6. Yes, memory at 6000 has multiplex access low-byte/high-byte with the automatically inserted wait states. Only the SRAM at 8300 has a full 16-bit access without wait states. Caching would only make sense if it is much faster than the normal access, so maybe one could think about using a 16-bit 0WS cache for caching the 8-bit data bus transfer, but this would not gain enough speed to justify the additional efforts to move RAM content in and out. The cartridge port indeed only offers the address bits A3-A15 (for addresses 0000-1FFF), and there is a line ROMG* = A0+A1*+A2* for selecting ROM at that port (and GS* for GROM select).
  7. Yes, when the image has reached the actual capacity, it will not grow further. The CHD file for our hard disks is not compressed, despite its name ("Compressed hunks of data"). In TIImageTool I offer the option (by default) to fill vacant space with 0. This has the effect that those hunks are not stored in the CHD file but will be delivered as 0-filled when being read. The CHD file will be really small (much smaller than a DSK image). When you use MDM to format the hard disk, it will fill the sectors with E5 (I think), which means those hunks will be created, and the CHD expands to the fill size. The CHD file is quite similar to DSK in the sense that only sector contents are stored. There are no headers, gaps, ID marks, CRC (ECC), or interleave. However, I store this information as meta-information in the header of the CHD file. When the CHD is mounted in MAME, and a cylinder is accessed, an MFM image with all gaps and ID marks and so on will be created on the fly. To make this more efficient, 10 cylinders are cached in the emulation by a LRU strategy.
  8. Hmmm... Some people would like to see a Raspi running a TI emulation, but a TI emulation running a Raspi... I mean, if we assume that the emulator host runs at least a 100 times as fast as the emulatee, you should not expect anything useful from emulating that class of hardware.
  9. I seem to remember that KEYCODE_xx is outdated. ESC is not a good choice because there should be one key that allows MAME to exit. I think a good choice could be CapsLock: I don't use it for AlphaLock because I sometimes find it getting out of sync with the PC key; I'm using another key for Alpha Lock instead.
  10. Yes, and it reminds me that I should continue moving and updating the info to my server. 🙂
  11. Just tried it ... seems to work quite well with -uimodekey. You have to use a string from the list on Ninerpedia as argument - and the MAME release that matches this description. I don't know since when this command line argument is available.
  12. Yes, we also have that on Ninerpedia: https://www.ninerpedia.org/wiki/Change_MESS_menu_mode_key 🙂 Actually, were you successful with the command line option? Was this your actual question? (You can put many settings of the command line into the mame.ini file. Call mame64 -createconfig before.)
  13. It takes some time until it is loaded. Do you hear floppy activity?
  14. By DBIN? (Pin 25 in the grom port)
  15. I added a feature to the next MAME release to allow for 8K RAM standard cartridges - which were (almost) already possible, but I had ruled them out by blocking write access. This is now allowed if the cartridge actually has RAM in the socket. The Myarc Extended Basic II cartridge will be available as "-cart myxbii". Until then, using Superspace 2 is safe.
×
×
  • Create New...