xdt99 + Classic99

[+dhe]

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:

 

 

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

 

Thanks!

 

 

 

[+jedimatt42]

So, your object file doesn't look like it is a FIAD, not sure if you are using DIS/FIX options for native files. 

 

Second, your source should have a DEF and label and that sets up the symbol you can use as an entry point. 

 

His tutorial example dump of the object file shows the START near the end in the DEF table. I don't see a hint of that in your dump.

[+dhe]

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

 

 

 

[HOME AUTOMATION]

JMP  START

The jumpstart as the first line, tells a story of wanting to be run as an E/A5 binary. Could add DEF START.

[GDMike]

Yes. No Def defined

[+dhe]

Ok.. That did!

I was being too darn dogmatic following the tutorial.

 

The deeper reason I wanted to get this setup, is now I can use a rich compile/edit environment, use classic99 as the execution engine, and I have a TIPI on that way, after I make sure something passes muster with classic99, I can actually be bothered ? with running on an actually console!

 

Thanks Home Automation!

[GDMike]

That automation dude just keeps chugging..