Jump to content

dhe

+AtariAge Subscriber
  • Content Count

    517
  • Joined

  • Last visited

Posts posted by dhe


  1. I agree with the lack of DEF, but I'm trying to work via the example as given, and the ashello.asm is what is in the example folder on github.

     

    D:\classic99_vm\classic99_asm\mydisks\dsk1>type ashello.asm
    *  HELLO WORLD
    
           IDT 'ASHELLO'
    
           REF VSBW,VMBW,VWTR
           REF KSCAN
    
           JMP  START
    
    WRKSP  EQU  >8300
    KMODE  EQU  >8374
    KCODE  EQU  >8375
    GPLST  EQU  >837C
    
    MESSG  TEXT 'HELLO WORLD'
           TEXT '   hit any key!'
    MESSGL EQU  $-MESSG
    
    START  LIMI 0
           LWPI WRKSP
    
    * CLEAR SCREEN
    
           CLR  R0
           LI   R1,'* '
           LI   R2,24*32
    
    CLS    BLWP @VSBW
           INC  R0
           DEC  R2
           JNE  CLS
    
    * WRITE WELCOME MESSAGE
    
           LI   R0,2*32+3
           LI   R1,MESSG
           LI   R2,MESSGL
           BLWP @VMBW
    
    * CHECK KEY PRESSES
    
           LI   R8,>FF00
           CLR  R9
    NEXT   LIMI 2
           NOP
           LIMI 0
           MOVB R9,@GPLST
    KEYSC  MOVB R9,@KMODE
           BLWP @KSCAN
           CB   @KCODE,R8
           JEQ  KEYSC
    
           MOVB @KCODE,R0
           SRL  R0,8
           ANDI R0,>000F
           ORI  R0,>0700
           BLWP @VWTR
    
           JMP  NEXT
    
           END
    
    D:\classic99_vm\classic99_asm\mydisks\dsk1>

     

    I did not compile with the DF80 option, but checking the debugger, I didn't see it give any errors on load, or compile. Type: FIAD.

     

    Compiler command used was:

    D:\classic99_vm\classic99_asm>python ..\xdt99-3.0.0\xas99.py -R .\mydisks\dsk1\ashello.asm -L .\mydisks\dsk1\ashello.lis -o .\mydisks\dsk2\
    > --- <L> **** -
    ***** Warning: Unresolved references: VSBW, VMBW, KSCAN, VWTR

     

     

     


  2. Sure, I'm just missing something simple here, I have installed xasm99 and classic99.

     

    I'm working through the tutorial found here: https://endlos99.github.io/xdt99/

     

    I think I'm doing everything right, here is the object file I have in dsk2:

       

    D:\classic99_vm\classic99_asm\mydisks\dsk2>type ashello_o
    0007EASHELLO A0000B100DB4845B4C4CB4F20B574FB524CB4420B2020B68697F19FF       0001A0012B7420B616EB7920B6B65B7921B0300B0000B02E0B8300B04C0B02017F2F9F          0002A0028B2A20B0202B0300B0420B0000B0580B0602B16FBB0200B0043B02017F336F          0003A003EC0002B0202B001AB0420B0000B0208BFF00B04C9B0300B0002B10007F31FF          0004A0054B0300B0000BD809B837CBD809B8374B0420B0000B9220B8375B13F97F2D4F          0005A006ABD020B8375B0980B0240B000FB0260B0700B0420B0000B10E87F410F               000630030VSBW  30046VMBW  3007AVWTR  30062KSCAN 7F5AFF                          0007:       xdt99 xas                                                           0008

     

     I'm able to use E/A option 3, to load ashello_o - no complaints from the loader.

     I then enter through to PROGRAM NAME?

       I've tried leaving program name blank, I've also tried START.

     

     In any case, I'm always rewarded with:

     

    image.png.8f8fb03a3085508bf637a2c05de1caf9.png

     

    The tutorial seems solid, so I'm pretty sure, it's something I'm missing!

     

    Thanks!

     

     

     


  3.  

    This is an 'article' by Anne Dhein, which did a really good survey of many of the graphics programs and utilities available for the 99/4a.

    I believe this was 'serialized' in newsletters.

     Unfortunately, my copy is from the cyc, and it says 'missing part 4' does anyone have the whole thing, or part 4?

     

    • Like 1

  4. What is Geneve compatibility?

     

    I mean, yes, you want to run MDOS, but, so what if you have you have to make a 200 byte addition to MDOS, to use a much better clock chip?

     

    Lou Phillips, had to do that with the Geneve. Everyone wanted a TI compatibility layer + more (primarily a DOS like environment).

     

    We are gifted in that MDOS source is freely available, primarily thanks to Beery.

    • Like 2

  5. Maybe way off base. But from what I know, reasons for QI:

       1) Cheaper to make (a real selling point, when your paying everyone a $100 rebate on a $100 dollar computer, cause you'll make it up selling software).

       2) Lock out 3rd party modules.

               The was done in the firmware, and also apparently from what this thread says, locking out of the side port.

       3) Some of the side port modules sold had really hard teeth (fingers?), and TI issued a particular warning, that they would NOT be responsible for damage to the side port, if 3rd party modules were used.

     


  6. I received a shipment of 10 boards, I'll pull the package open this weekend, and try to eye ball them for being "right" - since I don't have one, I'll just have to see if the keys are in the right place. Boarding house rules - everyone gets firsts before anyone gets seconds.

    If you interested, message me your address, if they seem right, I'll mail you a board. It will probably be in the 12-15 dollar range. When / If I mail you a board I'll let you know, if it meets you need your needs, once you get it, you can send me some money...

    Probably be at least next weekend before any boards go out.

     

    • Like 2

  7. If you have to put in new voltage regs, you should use the new uber cool ones Tim found. I think found earlier in this thread. While the advice is a bit late, many people that add a holder for the clock battery, used a band saw or grinding wheel to remove a bit of the battery holder along the top of the card so there was the potential for a hit, when putting it back in a case.

    • Like 1

  8. SAMS memory access isn't supported by MDOS/Geneve.

     

    For memory expansion, you can add and additional 32K static chip (stacked) - if not already done.

    Heavily Modify a Myarc 512K Card.

    Or if you are luck enough to find one a Horizon Memex Card.

     

     

    • Like 1

  9. FWIW - I had this exact same problem when I was playing with Fortran99, about ever other time, I'd open the source file for editing and I'd have to delete a bunch of garbage at the end of the file.... I wasn't doing anything crazy like running multiple copies of Classic99 or closing the application in the editor, and it wasn't always consistent. I don't blame Classic99 because Tursi has said many times, don't use disk images.... and that MAME is a fine option! 😃

    • Like 2
    • Haha 1

  10. HexBus Interface, I purchased one of the two from the CB Wilson Estate. I've ALWAYS wanted one of these. I thought I was close, I visited Michael's Becker's Magical Basement, and he had made about 20 cases for HexBus interfaces, but he never made them. I'm hoping the HexBus Interface works and I can get it to work the Arduino based HexBus drive that Vorticon has been using and debugging.

    • Like 2
    • Thanks 1

  11. Bump for poor Dan:

    First Question - What's the latest release of MDOS (GeneveOS)?

        Looking on WHTech.com - I see a directory called Geneve and Geneve.new.

             Geneve.new has MDOS - now recommended to be called GeneveOS - to remove association with MyARC. -

                      6.50

             Geneve has also MDOS 6.7RC2 - Was MDOS 6.7 ever released?


  12.  

    First Question - What's the latest release of MDOS (GeneveOS)?

        Looking on WHTech.com - I see a directory called Geneve and Geneve.new.

             Geneve.new has MDOS - now recommended to be called GeneveOS - to remove association with MyARC. -

                      6.50

             Geneve has also MDOS 6.7RC2 - Was MDOS 6.7 ever released?

     

    Question #2 - Forth for MDOS (GeneveOS)

         Bill Sullivan (FDOS) (BRS Consulting?) worked for many years on a native Forth for the Geneve - I know John Carver was a serious user.

         I vaguely recall FDOS selling some of his TI Stuff to down size.

         Did anyone get Bill's Forth Source code?

    • Thanks 1
×
×
  • Create New...