 | | Re: (Failed) Getting LegOS 0.2.2 working on Windows
|
|
Well, i'm still looking to find out what might go wrong. Fixing the sigio handler is of no use as cygwin doesn't send sigio's when data arrives at a serial port. Peter (...) (25 years ago, 22-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Transmission Problems
|
|
(...) After doing a bit of debugging, I have determined it's all characters between 127-255, most often 127 or 255. If anyone has any ideas on what's causing this, please reply... (25 years ago, 22-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: (Failed) Getting LegOS 0.2.2 working on Windows
|
|
(...) I hadn't fixed that - but it doesn't appear to make a difference. I patched both the original sources and the post-WINNT-specific-patches, but no change in behavior: the RCX answers are never heard using the original sources, and the (...) (25 years ago, 22-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: (Failed) Getting LegOS 0.2.2 working on Windows
|
|
(...) i dont´t know if you have already fixed this, anyways, there is a bug in sigio_handler. The struct timeval last is used uninitialized and should be static. Today i sent the following little patch to Markus. ------- schnips schnips -------- --- (...) (25 years ago, 22-Dec-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: (Failed) Getting LegOS 0.2.2 working on Windows
|
|
(...) Hey -- More info about this odd bug. Installed 0.2.3, and the bug is still there. A bit more tweaking revealed: * Compiling with the original (.orig, pre-patch versions of loader, lx, and rcxtty) yielded - after changing O_ASYNC to FASYNC - (...) (25 years ago, 21-Dec-99, to lugnet.robotics.rcx.legos)
|
