Jump to content


+AtariAge Subscriber
  • Content Count

  • Joined

  • Last visited

  • Days Won


mizapf last won the day on August 31 2016

mizapf had the most liked content!

Community Reputation

5,035 Excellent


About mizapf

  • Rank
  • Birthday 09/24/1969

Profile Information

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

Recent Profile Visitors

18,384 profile views
  1. Thank you for your feedback. This is a bit difficult for me to formulate without sounding like bragging. But honestly, for me the floppy sound emulation in MAME is one of the top things that I mastered to get going in the emulation, and I am particularly proud of that. I could not imagine how to significantly improve it. It's not that I could say, well, the sound is just as good as I was able to achieve it, sorry if it sounds a bit off; to my ears, it is in fact very close to the real device (while it is only one particular floppy drive, of course) and absolutely believable. And it does a very useful job at the same time: You stay informed what your system is doing right now (unless you want to use floppies at unrealistic high speeds, but then you don't bother about sounds anyway). I'm already considering doing a similar sound emulation for the hard disks, but this is low priority. I think that you are putting up some very strict requirements that may be overly hard or impossible to realize, maybe to disguise that you just don't like floppy sounds - like "If you can't do it 105% correctly, just leave it."
  2. This is a 1.4 MiB disk image; the only chance to use it is the HFDC, setting to 1.4 MiB and 80 tracks. I strongly recommend not to use these "ultra-density" disks. However, I was able to copy the contents into a HD image using TIImageTool (create new directory, mark all, copy, paste).
  3. Did you include "-colorbus busmouse" in your command line?
  4. (-: ooO (And when I emulate floppy sounds, people go crazy and want to turn them off immediately)
  5. Yes, this is one of those recent discoveries that I wished I had back in those days.
  6. Have a look at Heiner Martin's TI INTERN. We should even have the PDF somewhere.
  7. Back in those days when I played Infocom adventures on my Geneve with the 80-column interpreter for the TI, I had to swap the game files in and out of the DSK1 directory, and the problem was in fact that the game files had the same names. Hence, I wrote two scripts "INST" and "DINST" for installation and uninstallation of the files for each Infocom adventure (including the savegames). So I had directories like \GAMES\ADVENT\DEADLINE, \GAMES\ADVENT\ZORK1, \GAMES\ADVENT\ZORK2, ... and each one had a copy of those INST/DINST scripts.
  8. If you use the HFDC (real or on the MAME Geneve emulation), you can put the files in the E:\DSK1 directory (or whatever drive letter you use). File searches on DSK1. will start in E:\DSK1 before falling back to the drive DSK1.
  9. On the disk image that I posted above. Let me guess: You defined the Joystick as keys on the keyboard (like 8_PAD for "P1 up") but you did not disable the setting for the key "KP 8". In this case, every time you press keypad 8 for up, you will also send the key to the emulated keyboard, and this makes you teleport somewhere else. I was using a real joystick with a joystick-USB adapter, as I already mentioned above.
  10. I think I'm not able to formulate it less ambiguously. 🙂 defender-2021-09-22_21.09.06.mp4
  11. Defender is running on both emulation and real Geneve. As for Moon Patrol, I don't get past the "PRESS ENTER" screen, but this is obviously due to direct CRU scanning. In that sense, Moon Patrol does not crash either, but it gets stuck in the entry screen. 6A98: SETO R1 6A9A: LI R0,>0003 6A9E: LI R12,>0024 6AA2: CLR R2 6AA4: MOVB *R11+,R2 6AA6: CI R2,>0600 6AAA: JNE >6ABC 6AAC: SWPB R2 6AAE: MOVB @>830C,R2 6AB2: CI R2,>0200 6AB6: JLT >6ABA 6AB8: INC R2 6ABA: SWPB R2 6ABC: LDCR R2,3 6ABE: MOVB *R11+,R12 6AC0: SRL R12,8 6AC2: JEQ >6AD0 6AC4: CLR R2 6AC6: STCR R2,1 6AC8: JNE >6ACC 6ACA: CLR R1 6ACC: DEC R0 6ACE: JNE >6A9E 6AD0: MOV R1,R1 6AD2: RT 0024 is the address for setting the keyboard row. The three bits of the row are set in 6abc, the column is checked in 6ac6 and 6ac8. The Geneve executes this portion of code repeatedly; it will certainly fail its purpose because the keyboard is not connected to the 9901. If you are interested, launch MAME with -debug to see what happens.
  12. If you suspect invalid opcodes, you can run MAME with -oslog or -log, logging messages to the console or to error.log, respectively. Bad opcodes are always reported, no need to recompile.
  13. Defender is working for me, on both real iron and MAME. However, I have to play with Joysticks, not with the keyboard. When you press some key, you teleport away to a different location, and it may happen that you jump right into an alien ship. Maybe Defender uses direct CRU keyboard scan, not the keyscan routine. Note that games using direct CRU access for the keyboard won't work.
  14. How would we remember Apollo 13's message if the crew would have been women? Aquarius: "Houston, we have a problem." Houston: "What is your problem?" Aquarius: "Just OK, never mind."
  15. These cartridges are dumps of my own cartridges, and I am quite sure they work on the real iron (not tested right now, but I would not have kept them otherwise). games.dsk
  • Create New...