Re: [MSX] communication between msx tux
I think www.msx.ch Not sure though, and too lazy to check. ~Grauw - Original Message - From: Ricardo Jurczyk Pinheiro [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, November 09, 2002 3:18 PM Subject: Re: [MSX] communication between msx tux Em Ter, 05 Nov 2002, Laurens Holst escreveu: It's very easy to do from a DOS environment aswell. Just use a BBS program like HyperTerminal in Windows (I don't know one on Linux, but it should definately be there), and use the terminal program Erix on your MSX. If you set the same baudrate on both sides, and connect both computers using a so-called 'crosscable' or 'null modem link cable', then you can simply use YMODEM transfers to send files from the one computer to the other. Hmmm... Everytime I tried to use Erix, my MSX hang up (I've got a Sunrise RS-232). But Adriano and I tested it into Uzix, and works nicely. Maybe it's my copy of Erix. Does anyone knows where I can find a working copy? Thankx, -- Ricardo Jurczyk Pinheiro - M. Sc. Numerical Modelling - [EMAIL PROTECTED] Anime, ABUB, MSX, Linux, Gospel, ST, Rock, Math... Fudeba! - ICQ: 3635907 Sola Scriptura - Sola Gratia - Sola Fide - Solo Christi - Soli Deo Gloria I am a man more sinned against than sinning. - King Lear. ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] communication between msx tux
I hope you can solve it. Keep us updated :). Victory at last. Futher meddling with all kinds of settings and switching serial ports seemd to do the trick (my modem works fine on ttyS1 (COM2) by the way. Strange...) I didn't try windows anymore, minicom works fine. Xmodem and Ymodem protocols, both ways, and ASCII of course, flowcontrol by software. Both programs hanged however when I tried the Zmodem, just before finishing the file. Does someone have any idea why? I used an archive called INS-B5.LZH I downloaded recently from the Internet to send from the PC to the MSX and back, and testing the archive on both computers returned no errors. Every time it unpacked nicely, even with a baud rate of 115200 bps, but I do have a 7Mhz MSX. Thanks all of you for the advice. Diederick de Vries ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] communication between msx tux
Both programs hanged however when I tried the Zmodem, just before finishing the file. Does someone have any idea why? Probably a bit buggy zmodem implementation on either part. ZModem specs have never been really standardized I believe. Anyways, YModem is all you need. I used an archive called INS-B5.LZH I downloaded recently from the Internet to send from the PC to the MSX and back, and testing the archive on both computers returned no errors. Every time it unpacked nicely, even with a baud rate of 115200 bps, but I do have a 7Mhz MSX. As I said, a higher bitrate shouldn't cause any errors. I can clarify this a bit, first of all, the RS232 has a 15-byte buffer. So if its bytes are not immediately read out (for example because the interrupts are disabled for a short while), it can receive up to 15 bytes until it drops one. That's the first ensurance. Second one is in the Fossil driver. The fossil driver itself is fast enough to keep up with the RS232, even on 3.5MHz. However, it has a (larger) internal buffer, which can get full if bytes aren't read out by the user program fast enough. If that's the case, the Fossil driver tells the RS232 to temporarily stall receiving bytes (hence, flow control). That is the limitation you run in to on MSX, because since the driver is already keeping the Z80 so busy with receiving the bytes from the RS232, there is very little time left for the program itself to read them from the Fossil driver's internal buffer (which by the way has to be done, very inefficiently, byte by byte, the major disadvantage of the Fossil driver) (let's not mention the bug :)). Anyways, that's why it can't keep up, so it slows down. You can perhaps imagine this fast receiving and temporarily pausing the receive process is putting a bit of an additional load on your MSX, so that's why it's better to set the connection bitrate as low as possible without slowing down the actual transfer. So if your transfer isn't going faster than 5.6 kb/s, don't bother setting a bitrate higher than 56k. This results in a slight speedup (compared to 115k). To be complete, last but not least, Erix manually tells the driver to set 'do not receive' status when it accesses the disk drives. This because during that process the interrupts are prolongedly disabled, which *would* cause an overflow of the 15-byte RS232 buffer. Thanks all of you for the advice. No prob ^_^. ~Grauw ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] communication between msx tux
Hi people, Laurens Holst: It's very easy to do from a DOS environment aswell. Just use a BBS program like HyperTerminal in Windows (I don't know one on Linux, but it should definately be there), and use the terminal program Erix on your MSX. If you set the same baudrate on both sides, and connect both computers using a so-called 'crosscable' or 'null modem link cable', then you can simply use YMODEM transfers to send files from the one computer to the other. This option sounded as the most simple one. In Win98se (using Hyperterminal) as well as in Linux (using minicom) I got exactly the same (unsatisfactory) result: when I type some characters on the MSX keyboard, they show up on the PC, but not vice versa. I can also let Erix send an ASCII file which also shows up on the PC terminal window, again in Linux as well as in Win98. But that's all. In Erix I use default/MSX/ANSI as terminal parameters, and I use 115200-8N1 as interface parameters in every com program mentioned. I have tried every protocol. Should I specify modem commands? And if so, which? And if not, what could I be doing wrong? Greetings, Diederick de Vries, Groningen (Netherlands) ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] communication between msx tux
In Erix I use default/MSX/ANSI as terminal parameters, and I use 115200-8N1 as interface parameters in every com program mentioned. Try 19200-8N1 first (115kbps is suitable only for TR in R800 mode, or you will loose data when sending from PC to MSX). Also, check if you enabled RTS/CTS, because Erix Fossil Driver uses these control lines. With Z80 3.5MHz I got a maximum of 33k6bps on UZIX with Sunrise RS232. Greater speeds causes data loss. Adriano Camargo Rodrigues da Cunha ([EMAIL PROTECTED]) Diretor Executivo - AL Software http://www.alsoftware.com.br http://www.alsoftware.com.br/adrianpage ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] communication between msx tux
In Erix I use default/MSX/ANSI as terminal parameters, and I use 115200-8N1 as interface parameters in every com program mentioned. Try 19200-8N1 first (115kbps is suitable only for TR in R800 mode, or you will loose data when sending from PC to MSX). Also, check if you enabled RTS/CTS, because Erix Fossil Driver uses these control lines. With Z80 3.5MHz I got a maximum of 33k6bps on UZIX with Sunrise RS232. Greater speeds causes data loss. That data loss should be corrected by the error control I think, although I indeed disadvise against using 115kbps it should not lead to corrupted data but only to slower downloads. In Erix, a 56k download (@7MHz) is indeed faster than a 115k one. My own YModem download program I wrote though is ofcourse a lot faster, and therefor is limited by the 56k. So, in that case, setting 115k is the best choice. Anyways, it's not publicly available (yet), so just make do with Erix :). As for the problem you have with one-way transmissions... Somehow they sound familiar, at the Bussum fair I think I had pretty much the same problem. When I was typing on my PC, it didn't appear on my MSX. However, the good thing would be if I had solved it then, but I don't really recall anymore whether I did. Or wait, as a matter of fact I did, yes, I remember showing my download program's speed to someone (Patriek perhaps). Problem still is, I don't recall HOW I solved it ;p. I *think* one of the connectors came a bit loose, but I'm not sure about that. Anyways, here at home I have never had any problems with it, although for some reason Erix doesn't transfer files to HyperTerminal with YModem very well (read: not at all)... XModem does work, but it sucks! But that's beside the point. Something what perhaps your problem might be, is that your nullmodem cable is not really ok. As far as I know, the concept of 'nullmodem cable' is a bit tricky and not fully RS232-standard (at least, not the simple crosscables). I even believe I read that there are three different types of nullmodem links. And er, no, I don't know the URL of that page anymore. In any case, the differences were mainly related to the hardware flow control, so indeed using software flow control or meddling a little with the other settings might make it work. Also there is the possibility of a loose wire in the cable, did you test it? You can connect one side to the first COM port of your PC, and the other side to the other, and then open two instances of HyperTerminal. I hope you can solve it. Keep us updated :). ~Grauw ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] communication between msx tux
Hi, Hi Diederick, I have a linux computer and an msx with a Sunrise RS232C interface and a cable and now I want to send files to and from them. What programs should I use on either computer? Greetings, Diederick de Vries, Groningen (Netherlands) Maybe you should try Uzix (http://uzix.sourceforge.net/). I don't know exactly how to do that but I've good reasons to believe that it works. If I remember very well, Adriano Camargo (Uzix author) have been doing that so long... ADRIANO!!! Can you explain how to do that? ;) (I'm curious too) :P Best regards, Julio Marchi ___ Yahoo! GeoCities Tudo para criar o seu site: ferramentas fáceis de usar, espaço de sobra e acessórios. http://br.geocities.yahoo.com/ ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] communication between msx tux
It's very easy to do from a DOS environment aswell. Just use a BBS program like HyperTerminal in Windows (I don't know one on Linux, but it should definately be there), and use the terminal program Erix on your MSX. If you set the same baudrate on both sides, and connect both computers using a so-called 'crosscable' or 'null modem link cable', then you can simply use YMODEM transfers to send files from the one computer to the other. Using Uzix is in this case not really very useful. First off, Uzix is still alpha, so I don't know how well everything will work, and second, you'll most likely be transferring files for DOS, etc. Going to Uzix and back to MSXDOS more or less requires you to reboot, and the files aren't stored on the same drive (Uzix uses another partitioning format), so you've got to copy them with some kind of FTP-like program to your DOS HD first aswell. A more interesting application of Uzix is to browse the internet with it, by setting up your PC as some kind of 'PPP dial in server' (a PPP daemon). For more information, take a look at http://uzix.sf.net/. It has detailed instructions. ~Grauw - Original Message - From: Julio Marchi [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, November 05, 2002 8:25 PM Subject: Re: [MSX] communication between msx tux Hi, Hi Diederick, I have a linux computer and an msx with a Sunrise RS232C interface and a cable and now I want to send files to and from them. What programs should I use on either computer? Greetings, Diederick de Vries, Groningen (Netherlands) Maybe you should try Uzix (http://uzix.sourceforge.net/). I don't know exactly how to do that but I've good reasons to believe that it works. If I remember very well, Adriano Camargo (Uzix author) have been doing that so long... ADRIANO!!! Can you explain how to do that? ;) (I'm curious too) :P Best regards, Julio Marchi ___ Yahoo! GeoCities Tudo para criar o seu site: ferramentas fáceis de usar, espaço de sobra e acessórios. http://br.geocities.yahoo.com/ ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] communication between msx tux
Using Uzix is in this case not really very useful. First off, Uzix is still alpha, so I don't know how well everything will work, and second, you'll most likely be transferring files for DOS, etc. Going to Uzix and back to MSXDOS more or less requires you to reboot, and the files aren't stored on the same drive (Uzix uses another partitioning format), so you've got to copy them with some kind of FTP-like program to your DOS HD first aswell. Even if not very practical, you can use UZIX to get files from your Linux box using FTP. Altought UZIX is alfa, FTP works very nicely. You get get the files you want without needing to prepare them for transmission (just browse your PC HD with the FTP client). The connection between MSX/UZIX and PC/Linux can be done using pppd (preferable) or slip. As Grauw said, detailed instructions are available at UZIX page. And about moving the files from UZIX FS to FAT partitions: just use doswrite. FAT16 is supported. Ex.: doswrite /tmp/uzix.dsk /dev/hda32 BTW, if I'm not mistaken, INS has a full working FTP client. I don't know if INS supports direct pppd connections using RS232 (I just tested it with a modem), but I think it deserves a try if you don't want to use UZIX, but want the facilities of FTPing. Adriano Camargo Rodrigues da Cunha ([EMAIL PROTECTED]) Diretor Executivo - AL Software http://www.alsoftware.com.br http://www.alsoftware.com.br/adrianpage ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
