 | | Re: PC -RCX comunication
|
|
(...) please, don't take my little attacks against MS too serious, it's just -- i really dislike their FUD way of making business, and i like to have a choice. However, i feel we shouldn't discuss this too much in this place. (...) Well, imho the (...) (25 years ago, 3-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Addressing Schemes
|
|
(...) It's quite simple: Currently, there are two kinds of LNP-Packets: the first one is called the integrity packet (switch your mail-reader to fixed font now): +--+---+---...---+---+ |F0|LEN| IDATA |CHK| +--+---+---...---+---+ F0 : identifies an (...) (25 years ago, 3-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: PC -RCX comunication
|
|
(...) OK. I agree with you about open-source OS. I like linux, but I prefer using visual programing in the PC side (Visual C++ o Visual Basic). (...) What about the QC examples? I've seen a easy interface IROn, IROff, IRReady, IRSend IRReceive .... (...) (25 years ago, 3-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Setting a different com port w/ frmdl3 and dll
|
|
The easiest way is to set the environment variable RCXTTY to the com port you want to use. Type the command set RCXTTY=com4 before you run firmdl3 or dll, or add the line to autoexec.bat Cheers Philip -----Original Message----- From: David Chen (...) (25 years ago, 3-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: HELP - LegOS for Windows
|
|
"Rossz Vámos-Wentworth" <rossw@jps.net> wrote in message news:38989DC8.62ED27...jps.net... (...) of (...) (COMMAND.COM & (...) The problems that you are mentioning generally only occur after running 16-bit programs (and thus ending up with a 16-bit (...) (25 years ago, 3-Feb-00, to lugnet.robotics.rcx.legos)
|
