Jump to content
Have You Played Atari Today?
2600|5200|7800|Lynx|Jaguar|Forums|Store  

mizapf

Members
 View Profile  See their activity

  • Content Count

    5,351

  • Joined

  • Last visited

  • Days Won

    3

Posts posted by mizapf

  1. Posted · Edited by mizapf

    Yes, I think I remember that the outermost columns were sometimes too close to the edge of the visible screen, and I had two knobs at the rear of the TV set to control the width and height of the picture - of course, for all programs, not for single ones. So if you reduced the width, other programs may not have filled the screen.

     

    P.S.: Still remember when you moved your hand over the CRT to collect static electricity, and then give someone else a shock? ;-) Feels like decades ago. OK, it was some decades ago.

    • Like 4
    • Haha 2
    • Sad 1

  2. Posted

    54 minutes ago, arcadeshopper said:
    My next question, if I may.. I scooped up GROM 0, 1, and 2 from my console (which has a TIM and SOB) and XMODEM'd them over my UDS-10 to my PC. I have them working just fine in Fred Kaal's Ti994w, but I was wondering if it could be shoehorned into MESS/MAME?

     

    To the person on Discord:

     

    1. We have all required ROM dumps on WHtech, so possibly no need to dump by yourself. Check out https://ftp.whtech.com/System%20ROMs/MAME/ti99_4a.zip

    2. If you really want to use your own dumps:

    a) You need GROM 0, 1, 2 *and* the two 4K ROMs in the console.

    b) To create the GROM dumps for MAME, store the 6 KiB of GROM 0 in file 994a_grom0.u500, the 6 KiB of GROM 1 in 994a_grom1.u501, the 6 KiB of GROM 2 in 994a_grom2.u502, and all bytes from even addresses of 0000-1FFF in 994a_rom_hb.u610, and all bytes from odd addresses of 0000-1FFF in 994a_rom_lb.u611.

    c) Zip all five files into a file ti99_4a.zip and put it in the rompath.

     

  3. Posted

    Yes, it takes quite a lot more processing power than the TI-99/4A because the 9995 does much more in fewer cycles. If you take the HX5102 floppy with the 99/8 or 99/2, this is really extreme.

     

    The 74% are reached without graphic output, which takes off a heavy load. This raw performance says how fast it may become if the graphics bottleneck is gone and all real-time pauses are removed. So the 64% is the number that applies for normal usage.

     

    Let's see how far some future Raspi generation brings us.

  4. Posted

    56 minutes ago, hloberg said:

    @mizapf have you heard anything about if the latest MAME will run at full speed on the new Ras Pi 4 without over clocking?

    There are no changes in the architecture, so I would not expect any performance increase or decrease. The current release does run at full speed without overclocking on a Raspi 4 for the 9900-based systems. The TI-99/4A can be emulated at 100% on my own Raspi 4 (see https://www.mizapf.de/ti99/mame/mamereq), and I'm not doing any overclocking.

    • Like 3

  6. Posted

    Hehe ... see what I mean? I wondered why the Windows zip file for 0.229 was 20 MiB larger than for 0.228, and guess why ... My pack script found the older mame64.exe (which was not overwritten) and put it inside the zip, next to the newer mame.exe. 🙂

     

    I re-uploaded the 0.229 Windows release to WHTech now.

     

    (By the way, I did not know about this change when it was committed, and I was doing some work in MAME right then, but none of my edits seem to have an effect - started tearing my hair ... until I noticed that I was simply using the older version, and all changes went into the new executable.)

    • Like 4
    • Thanks 1

  7. Posted

    I just uploaded MAME 0.229 (restricted to the TI-99 family) to WHTech for Windows, Raspbian, and Linux. See https://ftp.whtech.com/emulators/MAME/ti99/

     

    As I already mentioned, the executable file is from now on mame (Raspbian, Linux) and mame.exe (Windows). The "64" suffix has been dropped. Please make sure to update your launch scripts and to remove the old mame64(.exe) in your installation. Otherwise, you may unintentionally run the 0.228 (or earlier) version. In doubt, check the title bar of the window or look inside the OSD menu, option "About MAME". You should see "0.229".

     

    There is one thing that is interesting for us: For the Geneve, the debugger did not allow the user to write values into memory (using the memory view); this is now fixed.

    • Like 5

  10. Posted

    No, I don't want to suggest removing "MDOS". It is perfectly OK to have both names. Geneve OS does not appear on Beery's site, so this would be at least helpful to find it mentioned.

     

    My suggestion would be to include Beery's URL in the welcome message ("For more information visit ...").

    • Like 1

  11. Posted

    Just some more comments; I know this is a first sketch.

     

    a) Maybe you should explain on your website who is (or was) 9640News ("About").

    b) The name "GeneveOS" should appear somewhere near "MDOS", maybe just as "aka", to avoid confusion whether this is the same or not.

     

    The suggestion about the URL goes to Tim who may consider to add this to the welcome message.

    • Like 2

  12. Posted

    Should we include a link to your website in the standard GeneveOS installations, maybe directly in the greeting message?

     

    Currently, in the standard installation that can be set up by TIImageTool, a link to whtech is put into the AUTOEXEC. It would definitely be helpful for new users to have a link to go to when searching for information, FAQs, manuals etc.

     

  13. Posted

    If people need a DSK image - like MAME users - here is one I quickly created. I imported all the TIFILES from the ISABELLA99 subdirectory and some more from the root of the ZIP file. I don't know if there are particular reasons why it should not run on MAME, but at first sight, everything seems OK.

    isabella7.dsk

    • Like 3

  17. Posted

    By the way, here is a fixed version of TASM 3.4 (which I renamed to 3.41). I found two flaws in TASM:

     

    - Assembly aborted before pass 2; reason was an uninitialized variable which led to a wrong memory location access

    - COC mnemonic not recognized; reason was an error in the opcode table.

     

    I tried to contact Alan Beard who was active for a short time last October and November, but it seems he has not yet visited our forum again, and I could not reach him by E-Mail.

    tasm341.dsk

    • Like 1
    • Thanks 1

  20. Posted

    13 hours ago, GDMike said:

    If you enjoy programming, yes. There's always a curve to overcome, 16 bit programming and an 8 bit data bus AND little memory to use.

    However, the multiplexed 8-bit data bus is nothing that bothers you in programming, unless execution speed is important.

    • Like 2

  24. Posted

    Crazy weather here ... a week ago, I nearly froze my fingers scratching ice off the windshield. Today, I was comfortably walking outside without a coat. Last week there were -20°C in parts of Germany (too cold for February), while now we have +20°C at some places (too warm for February). This is a delta of 40K, or 72°F.

AtariAge
Forums
Store
General
Follow AtariAge

Copyright ©1998-2021 AtariAge

×
×
  • Create New...