 | | Re: LegOS 0.2.2 on Win95 (almost)
|
|
No! No! I mean, yes, do try it again (someone), just not with 2.9.5- there have been reported problems with 2.9.5's treatment of assembler. Rebuild it with 1.1.2 + patch- that is known to work. Then let me know- I'll host it for you. -Luis (...) (...) (25 years ago, 10-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.2 on Win95
|
|
Well, in the meantime, i built one on WinNT. The build always failed on Win95. Tried Canadian cross on Linux and i too gave up in frustration. But now that i have one built, i'll put it up on a webpage tomorrow. First, i'm gonna check the files it (...) (25 years ago, 10-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | chaning the host address in LNP
|
|
OK. The initial stuff I have done with the Java interface to LNP just addresses different "ports" to the host address 0. Each of the RCX's on the Lego Network Protocol network had host addredss 0 and port 1,2,3,4 depending on which brick they were (...) (25 years ago, 10-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.2 on Win95 (almost)
|
|
Peter Van der Beken wrote in message ... [snip] (...) from (...) . Yes, the compiler I built doesn't have the patch - it's also egcs 1.1.2 rather than gcc-2.95.2. This isn't going to change quickly because unfortunately I don't have access to a (...) (25 years ago, 10-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP collision detection Bug found and fixed
|
|
(...) it is already defined this way... indeed it looks like egcs for h8300 treats char as unsigned by default. look at the following test proggy... char ch; void showbug(void) { if (ch < 1) ch=-2; } ... and the disassembled code (...) (...) (25 years ago, 10-Dec-99, to lugnet.robotics.rcx.legos)
|
