suggestions for table of Available CIO Operations by device?

[tschak909]

Subject says it all, am looking for a good reference of the available operations for a given device. I know I can just read the OS manual and listing worst case, but was wondering if there was something more concise?

-Thom

[Rybags]

I recall reading a list of extended Dos command codes (for Doses more advanced than 2.x) but don't remember where.

 

In fact D: handlers are probably by far the most complex of the commonly used ones. You have Fill for the S: device (for what that's worth, ie little) but I don't think there's any other "Special" commands for the built in devices.

 

With the more advanced Doses we have the likes of the binary load command which in Dos 2.x is performed by DUP and AFAIK not able to be externally called.

[+MrFish]

About 1/4 of the way down this page, there are several tables under the heading "Details of the Bytes in an IOCB": Assembly Language Programming for Atari Computers: Chapt. 9

 

Here's the XIO table you're talking about, Rybags: XIO Command Codes for DOS's.doc

Edited April 14, 2017 by MrFish

[Rybags]

The info I saw was presented differently. Possibly it could have just been a thread here or maybe even documentation for MyDos or SpartaDos.

Nice that you found that table though, it at least gives a decent starting point.

[tschak909]

I'm putting together a very streamlined programmer's text editor that only uses the OS routines for output, so I'm immersing myself into the CIO. Now before some of you puke, I'm doing this explicitly beause I want something that will actually work on not only the standard Atari screen, but will also work on the myriad of 64 and 80 column displays, as currently, very curiously, nothing like what I'm looking for actually exists...

 

-Thom

[+MrFish]

Here's the table itself:

[spacer]

              ICAX1
Device        Byte   Function 
------        ----   --------                                       
Screen editor    8   Output to the screen
                12   Input from the keyboard and output to screen
                13   Forced screen input and output
Screen display   8   Screen is cleared; no TW; RD
                12   Screen is cleared; no TW; RE
                24   Screen is cleared; TW; RD
                28   Screen is cleared; TW; RE
                40   Screen is not cleared; no TW; RD
                44   Screen is not cleared; no TW; RE
                56   Screen is not cleared; TW; RD
                60   Screen is not cleared; TW; RE
Keyboard         4   Read – note: no output is possible
Printer          8   Write – note: no input is possible
Tape recorder    4   Read
                 8   Write
RS-232 port      5   Concurrent read
                 8   Block write
                 9   Concurrent write
                13   Concurrent read and write
Disk drive       4   Read
                 6   Read disk directory
                 8   Write new file
                 9   Write – append
                12   Read and write – update mode

[tschak909]

what is "forced screen input/output" ?

 

-Thom

[+Stephen]

what is "forced screen input/output" ?

 

-Thom

Could it be used via BASIC so that self modifying code is possible? Like when the program is running, force the cursor over the line and hit enter?

[+JAC!]

Could it be used via BASIC so that self modifying code is possible? Like when the program is running, force the cursor over the line and hit enter?

Correct. The E: handler automatically completes every GET RECORD automatically.

It was ofen used to start BASIC programs by putting "RUN D:XYZ.BAS" on the E: after it was set to mode 13 and the RTS, so the BASIC kicks in.

You can see the cursor running down the screen magically.