#DISASM.BAS (Again!)
2 messages in this thread
Dave, I just looked at DISASM in my Model 100, and the TAB's in the xmodem'ed
file were fully expanded into real spaces in my "Read" download yesterday —
hence the long lines when trying to load into Basic.
A thought: If you are doing YOUR read into the T600 and transferring to the
M100 afterward, the result may be different (the Telcom's may treat tabs
differently). Or you may be using X-TEL in the M100 for CIS access, which may
also treat tabs differently than the M100 bare-bones Telcom.
There is clearly a significant problem here, related to a M100 Read download of
DISASM.BAS. I suspect I will be able to transfer the xmodem version into this
box (tonight; disk is at home) and make it work. But files in the DL's should
load direct into un-adorned M100, and DISASM doesn't seem to.
Phil
p.s. — sorry for not building a thread, but I don't have a printout of the
previous messages, or access to my'big" system!
Phil:
Gollee! Wierd and unpleasant woes & unthinkables have surely been after
you over the past few days indeed!
In a nutshell; there is nothing wrong with the program. I've downloaded
the file with <R>ead and XMODEM protocol via the Tandy 1000 and with Mortimer
using both X-TEL (Read & XMODEM) as well as plain Telcom without X-TEL even
present in the Model 100. In each and every case I've been able to convert the
program to Basic with no DS errors and no problems running same. Every download
has been checksummed and all come up with the same figure.
1) #102205; never lost a line number.
2) #102208; correct about 9040 space differential, and yes TABs are in use
through those DATA lines. Does that matter?
3) #102210; Mortimer sees the TAB inside the quotes as TAB.
4) #102228; methunked you had solution to the problem when you
suggested my <R>ead was with Mortie and then transferred to Mor^C