rvp@cbnewsh.ATT.COM (rob.v.phillips) (12/18/89)
Recently, I have been compiling code on my toshiba 1200 laptop with a cross-assembler and uploading the binary files to my Atari 800 using "BOBTERM" (It's great! - Shareware Check is in the Mail!) Now, I would like to progress to an ATARI DOS that accepts commands and displays prompts over an rs232 interface (using either the 850, 2 joystick ports, or SI0; SIO would be preferable, cause I could use this on my Atari 400, too). Does anyone know of a DOS that does this? Or, would it be a simple matter, for anyone who knows the guts of any DOSes, to just somehow change a part of the DOS to use the R: device in its I/O calls? Mostly what I want from the DOS is to: - accept atari load files from the rs232 interface and put them directly in memory Could be xmodem, kermit, or just a raw, un-error- correcting protocol, as transfers will go on a null modem cable. (19,200 baud would be nice, too!) - option to save the rs232 file in an Atari disk file is nice, but not really necessary. - ideally, I would want to burn this on a cartridge, so when I crash the Atari in program development, I just hit reset for immediate system recovery. Thanks for your thoughts! Rob Phillips homxc!rvp OR cbnewsh!rvp OR ark2!rvp
gdtltr@strawberry.it.udel.edu (Gary Duzan) (12/19/89)
In article <6686@cbnewsh.ATT.COM> you write: =>Now, I would like to progress to an ATARI DOS that accepts commands =>and displays prompts over an rs232 interface (using either the =>850, 2 joystick ports, or SI0; SIO would be preferable, cause I could =>use this on my Atari 400, too). => =>Does anyone know of a DOS that does this? => I have used SpartaDOS 3.2d over an RS232 modem. A "PRINT R:" and "-R:" takes K:/E: input and sends E: output from/to the R: device. You have to be careful not to do anything funky, but it works otherwise. This trick doesn't work with the 400 since you can't run 3.2d on it. It also won't work with the SDX cartridge either unless you can get a COM: handler for it. If you can, you should be able to do a "COMMAND <COM: >COM:" and get the same effect. There may be COM: handlers on the ICD BBS, but I haven't checked lately. =>Or, would it be a simple matter, for anyone who knows the guts of =>any DOSes, to just somehow change a part of the DOS to use the R: =>device in its I/O calls? =>Mostly what I want from the DOS is to: => - accept atari load files from the rs232 interface and put them => directly in memory Could be xmodem, kermit, or just a raw, un-error- => correcting protocol, as transfers will go on a null modem cable. => (19,200 baud would be nice, too!) => - option to save the rs232 file in an Atari disk file is nice, but => not really necessary. => - ideally, I would want to burn this on a cartridge, so when I crash => the Atari in program development, I just hit reset for immediate => system recovery. I haven't tried this, but you might be able to get the effect you want in most DOSes simply by playing with the HATABS vectors. If you want a really simplistic change you might just change the D: vector to point to the R: driver's table. Alternatively, you could write a new device driver that takes D: commands and processes them into cooked R: data, possibly adding an error checking protocol. Why not just port NFS/SLIP to SpartaDOS & we can avoid the whole problem? :-] Gary Duzan Time Lord Third Regeneration _o_ _o_ [|o o|] "Two hearts are better than one." -- Yes [|o o|] |_O_| "Don't listen to me; I never do." -- Doctor Who |_O_|