drac030 Posted March 8, 2015 Share Posted March 8, 2015 Yes, the issue has been recorded in our bugtracker, but has not been yet fixed, sorry. There are about 20 issues there which are still to be taken care of, and this one is one of them. As always, not everything has been done that had been planned. Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted March 8, 2015 Share Posted March 8, 2015 That was fast Konrad: thanks. I hadn't really expected a fix in 4.47, but it's good to hear it's still on the list. Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted March 8, 2015 Share Posted March 8, 2015 Hi Konrad, I should have asked you about this: http://atariage.com/forums/topic/235991-slim-version-of-carina-ii-moe-source-code-for-sdx/ instead of burying it in the Programming section... Some kind of simple R: / K: / E: I/O redirector for SDX that enables remote access. I have searched and so far not found any good info on the subect. Thanks for your time. Quote Link to comment Share on other sites More sharing options...
drac030 Posted March 9, 2015 Share Posted March 9, 2015 Hi. Could you describe in more detail, what that "redirector" is suppoed to do? The I/O redirection in SDX basically requires the use of the I/O library. There are stdin and stdout handles in COMTAB, but these are not OS' IOCB numbers, rather SDX kernel's handles. Quote Link to comment Share on other sites More sharing options...
kogden Posted March 9, 2015 Share Posted March 9, 2015 Hi. Could you describe in more detail, what that "redirector" is suppoed to do? The I/O redirection in SDX basically requires the use of the I/O library. There are stdin and stdout handles in COMTAB, but these are not OS' IOCB numbers, rather SDX kernel's handles. I think he's looking for the ability to redirect console I/O to a serial port similar to the way you would do it in CP/M. Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted March 9, 2015 Share Posted March 9, 2015 Thanks for the reply, Konrad, What I'm looking for is a way to combine RS232 data with the screen and keyboard. Switchable (without dropping carrier) for file xfers. I didn't know if anyone had ever done something like this or not. I'm working on a BBS program, and all the existing software out there is big and clumsy to use, most of them don't work with SDX. I have a TurboBASIC program compiled to an exe, and that would be so nice (if it was even possible) to have a simple 3 step batch file such as: RS232.COM REDIRECT.COM BBS.EXE I hope you get the idea about what I am thinking of. I'm not even sure I know what I'm thinking of Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted March 9, 2015 Share Posted March 9, 2015 I think he's looking for the ability to redirect console I/O to a serial port similar to the way you would do it in CP/M. Yes, but with a few additions. File xfer protocol, etc. Quote Link to comment Share on other sites More sharing options...
drac030 Posted March 9, 2015 Share Posted March 9, 2015 I'm working on a BBS program, ... most of them don't work with SDX. Can I ask why they do not work? Has the reason been determined? RS232.COM REDIRECT.COM BBS.EXE I hope you get the idea about what I am thinking of. I would get the idea better if I had an idea what exactly the REDIRECT.COM does Anyway, what about: RS232.COM BBS.EXE <<COM: >>COM: ? Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted March 9, 2015 Share Posted March 9, 2015 Can I ask why they do not work? Has the reason been determined? I would get the idea better if I had an idea what exactly the REDIRECT.COM does Anyway, what about: RS232.COM BBS.EXE <<COM: >>COM: ? REDIRECT.COM is the program that may or may not exist yet... It's the "missing link" we need, a small version of Carina's MOE (modem operating environment). I'll try the <<COM: >>COM: thing and see what happens. Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted March 10, 2015 Share Posted March 10, 2015 Can I ask why they do not work? Has the reason been determined? Memory use (conflicts), mostly. Hard coded paths are a problem with some. Quote Link to comment Share on other sites More sharing options...
drac030 Posted March 10, 2015 Share Posted March 10, 2015 Could you be a little bit more specific? F.e. what conflicts, and why a hard coded path is a problem under SDX and is not under e.g. SD 3.2? Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted March 10, 2015 Share Posted March 10, 2015 Could you be a little bit more specific? F.e. what conflicts, and why a hard coded path is a problem under SDX and is not under e.g. SD 3.2? Well, here's a screenshot of BBS Express user editor. always garbage is inserted in the data. BBS Express is nice about the pathnames, though. I have tested so many, it's difficult to remember which ones have what problems. Carina either just freezes, or corrupts the screen, then freezes. This is why I want to make something different, modular, easy to understand, and above all, compatible. Sorry to pollute the SDX 4.47 thread... Anyone interested in BBS stuff, please join in here: http://atariage.com/forums/topic/149119-atardis-bbs-beta-version/ Quote Link to comment Share on other sites More sharing options...
drac030 Posted March 11, 2015 Share Posted March 11, 2015 It would be interesting to trace the problem down. Does this software run without an RS-232 interface attached (or R: handler loaded)? Quote Link to comment Share on other sites More sharing options...
w1k Posted March 11, 2015 Author Share Posted March 11, 2015 U1MB: 1mb hi-speed stereo: on vbxe: off spartados X: on SIDE: on, w/o button then i push black button on SIDE II, Q, and nothing happened.. only: ULTIMATE PBI V.1.0. Quote Link to comment Share on other sites More sharing options...
drac030 Posted March 11, 2015 Share Posted March 11, 2015 (edited) @w1k: I do not even know what is supposed to happen. Anyway, this problem probably belongs to a SIDE/U1MB thread rather than SDX. @Kyle22: my wild guess is that the problems with the BBS software may be caused by the fact that the VPRINT function of SD 3.2 is not implemented in SDX. The corresponding vector at $FFD8 does exist, but the only thing it contains is SEC/RTS. I admit that this should have been done in a more intelligent way, because the way they had done it (at ICD) will indeed cause a crash, if a program calls the vector. So this is something to be solved. For now, please try the attached program and see if it makes things any better. This is a quick TSR which should provide the VPRINT function in question to SDX. If its presence helps, the program will be put onto the Toolkit disk. PS. Note that TBXL itself for sure, and TBXL runtime library most probably, destroy these vectors. vprint.arc Edited March 11, 2015 by drac030 1 Quote Link to comment Share on other sites More sharing options...
drac030 Posted April 8, 2015 Share Posted April 8, 2015 Does the vprint.sys improve anything in that respect? I want to know if the program is worth further development. Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted April 8, 2015 Share Posted April 8, 2015 Well Konrad, it's difficult to say. The first time I tried vprint.sys, it seemed to help. I have since tried the program again without vprint.sys and it worked. This may be due to running under a new version of Altirra. I'll try it on real hardware when I get my 800 Incognito set up again. Quote Link to comment Share on other sites More sharing options...
drac030 Posted April 12, 2015 Share Posted April 12, 2015 So what about picking the most representative program of these which make problems, packing it nicely and sending to me, so that I could unpack it onto my hard disk and then try to find out what is wrong? 1 Quote Link to comment Share on other sites More sharing options...
morelenmir Posted May 8, 2015 Share Posted May 8, 2015 Hey guys! Not a bug but a feature suggestion. At some point could one of you take a look at making "SDXImager" work directly with the 'Ultimate1MB' ROM? It is an awesome tool and currently can indeed load the ROM and correctly identify its SDX segment. However, after making changes to the user-area and then saving - for instance to modify config.sys - the ROM as a whole will no longer boot. I guess this is probably the case when directly editing the other cartridge ROMs like SIDE2 or SIC within which SDX can reside, although I have not experimented with those. It would be a real time-saver but is obviously not critical. Quote Link to comment Share on other sites More sharing options...
fujidude Posted May 12, 2015 Share Posted May 12, 2015 Somewhere along the line I have a problem with 80 column mode creep up. Using: Altirra 2.70t12 U1MB SDX 4.47 S_VBXE.SYS CON.SYS (both this and S_VBXE.SYS are supplied by the newest (as far as I can tell) SDX Toolkit disk) For some reason the right margin is at 39 instead of 79. Even if I issue a poke command to change it, it does not change! Any ideas? Anything else I can tell you about to help figure this out? Quote Link to comment Share on other sites More sharing options...
fujidude Posted May 12, 2015 Share Posted May 12, 2015 Update: it was PEBCAK. I had defined the environment variable SCRDEV and put a right margin of 39 on it. Quote Link to comment Share on other sites More sharing options...
drac030 Posted May 23, 2015 Share Posted May 23, 2015 At http://spartados.com there is an updated version of SDX Tolkit available. A list of files changed and added below: bootld>inidos.syscompat>vprint.arcdrivers>pclink>pclink.arcdrivers>scrdrv>svbxe104.arcshells>sc095.arcutils>mkatr.arc All of this are rather minor improvements and bugfixes, except svbxe104.arc, where a major bug has been fixed, which caused problems (incl. crashes) after the Reset key was pressed. Thanks for Pinokio/TRS for repeatedly reporting that. And in inidos.sys the SIDE2 support has been added. 2 Quote Link to comment Share on other sites More sharing options...
fujidude Posted May 23, 2015 Share Posted May 23, 2015 (edited) Thank you so much for your continued efforts! I don't know why exactly, given all the modern computing resources I have to play with, but I get excited about new developments like this for the A8. As soon as I'm done going through new posts here on AA, I'm going to dive into that new TK! Edited May 23, 2015 by fujidude Quote Link to comment Share on other sites More sharing options...
fujidude Posted June 13, 2015 Share Posted June 13, 2015 (edited) Dumb? question: Where can I get the so called symbol list for SDX? I was reading the 4.47 programmer's guide and it mentions all these symbols and routines. I was thinking about using a couple of the built in routines rather than write something from scratch but can't seem to find where these named routines "live." I thought the SDX source code might enlighten me, but then I realized I couldn't find that either. Okay, I see that it is closed source. I'm surprised a bit at that, but okay. Anyway, what about the symbols and is there a list of equates for them or the DOS as a whole? Edited June 13, 2015 by fujidude Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted June 13, 2015 Share Posted June 13, 2015 It doesn't make sense to have an equate list for a symbol, since the symbol is by its nature relocatable, but many of the common symbols are documented right there in the programming guide. You'll look in vain for their "address", though (although some page 7 kernel functions have fixed vectors). Check out the MADS assembler's SDX programming examples for hints on how to write SDX applications which access external symbols. You can also obtain symbol addresses using a kernel call; this is how a standard Atari executable can get the address of a relocatable routine. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.