pgc@csadfa.cs.adfa.oz.au (Phil Clark) (02/14/91)
Many thanks to all of you that have replied to my plea for help!!
Because so many of you replied, I will not reply to each individually, but
please accept my thanks collectively. I must apologise for the multiple
posting of the original message. There was a problem somewhere in postnews
and it kept telling me that the message was not posted. (It LIED!!!)
For those of you that have had the problem I had and have not delved into
PRODOS, the answer to the problem lies in between BASIC and PRODOS and the
interpretation or trapping as the instructions pass through the various
firmware and software filters for execution.
The solution is to use only PRODOS commands and not the direct BASIC commands
for the input and output instructions as shown here. (In fact this applies to
any instruction/command that BASIC has to filter through PRODOS).
Examples:
PRINT CHR$(4);"PR#2"
NOT:
PR#2: PRINT"STRING"
Hope this helps someone else and thanks to all those who replied.
Phil Clark [VK1PC] Department of Computer Science, Phone:
Australian Defence Force Academy, +61 6 268 8157
Email: Northcott Drive, Campbell, Fax:
pgc@csadfa.cs.adfa.oz.au Canberra, Australia, 2600. +61 6 268 8581