 | | legos.sourceforge.net - Problems with SSL logon
|
|
Does anybody have problems logging on via HTTPS to legos.sourceforge.net? My browser do not connect at all. I'm using IE 5.01 with latest patches (also for SSL) but I continue to get errors. Note that before this problem, with the same browser & (...) (25 years ago, 5-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: CVS and SourceForge
|
|
(...) used (...) a (...) line (...) I did it without problems (for download) using command line version. But I'm using NT... I think I've read something about problems with Win95... What OS are you using? I have no success for now with wincvs, but I (...) (25 years ago, 5-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | CVS and SourceForge
|
|
I downloaded the necessary software to gain access to the legOS project in SourceForge, but have been unable to get the files to download. When I used the GUI version of cvs (wincvs), I get the error message "you must specify a module name" (isn't (...) (25 years ago, 5-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | New Windows HOWTO
|
|
This is a little premature since I have not yet made the compiler tools available, but I thought I would post this information now. Luis, would you like these instructions converted to HTML with all the proper links? ---...--- legOS on Windows HOWTO (...) (25 years ago, 4-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) I'm afraid this made no difference for me. I still get dll crashes. My particular symptom is that if I make a 1 line change to legOS then download it, it crashes straight away at the next dll. Even if I undo the change, then rebuild & download (...) (25 years ago, 3-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Recommended change to MAKEFILE
|
|
(...) Martin, Rossz, you guys both now are registered and have CVS write access. Be aware that sourceforge changes those things with a cron job that runs every six hours or so, so it may be a few hours before you /actually/ have write access. Enjoy (...) (25 years ago, 3-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Recommended change to MAKEFILE
|
|
(...) Rossz didn't have CVS access until about... oh... 3 minutes from now? -Luis ###...### Profanity is the one language that all programmers understand. -Anonymous ###...### (25 years ago, 3-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Recommended change to MAKEFILE
|
|
(...) imho, a very good idea. Perhaps you should check that in to CVS ? -- Martin (25 years ago, 3-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Recommended change to MAKEFILE
|
|
Currently, legOS uses this in the makefile: # for the kernel .depend makedepend $(LEGOS_ROOT)kernel/*.c -Y $(CINC) -f- | $(FIXDEPS) $(LEGOS_ROOT)kernel/ > .depend # for a typical program .depend: makedepend *.c -Y $(CINC) -f- | $(FIXDEPS) (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Windows/DOS Cross-Compiler - Finally!
|
|
After two months of struggling, I have finally been able to build a complete set of h8/300 cross compiler tools that work natively in a Window's DOS box. So what does this mean? If you don't run Windows 9x/NT/2k, absolutely nothing. What this means (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Memory
|
|
I intend to implement some reinforcement learning algorithms with the RCX. My program is running big. Im using legOS 0.2.3 how many memory does it uses? Im using all sensors. How many is left for me. THe size of the *.lx file is the size I should (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | LNP-Packets
|
|
I need to use the comunications with VC++ and Im going to do that. Can anyone tell the exact meaning of the following blocks. |F0|LEN| IDATA |CHK| |F1|LEN|DEST|SRC| ADATA |CHK| F0 and F1 is just a simple bit like 0 for F0 and 1 for F1? CHK is (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
Great! Well done, Martin! Toni "Martin Cornelius" <Martin.Cornelius@t-online.de> wrote in message news:38BDC2FD.85668C...line.de... (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) My hangups are gone too! Danke! Jürgen (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) Great! (...) This has always been a problem- it was an issue with firmdl before dll. Nothing serious, so it was never fixed. (...) You've actually had programs that large? Wow. -Luis (trying to make this more than a one-sided conversation...) (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: malloc() bug found -- BAD MEMORY REGION :-(
|
|
(...) made some tests, and - Yep, it works ! I'd strongly encourage everybody experiencing strange hangups to apply the little fix to mm_init() i suggested. For me, it makes malloc() and dll work perfectly. BTW, there are some minor flaws in dll[x], (...) (25 years ago, 2-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | malloc() bug found -- BAD MEMORY REGION :-(
|
|
It looks like it's not a bug in legOS, but in the RCX hardware: Memory from 0xfb80 to 0xfd7f is simply NOT WRITEABLE, or more exactly, always read as 0xff, at least on my RCX ! Try the following little test: // // memory test // #include <conio.h> (...) (25 years ago, 1-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | malloc() bug haunt: getting closer..
|
|
Yesterday evening i found something, that might be the reason for some of the crashes reported lately: The chain of memory blocks used by malloc() has a broken entry, say: the reserved block at 0xfd7c has a length word of 0xfffe. This will cause (...) (25 years ago, 1-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Odd behavior
|
|
(...) afaik, with vanilla legOS-0.2.3, lnp_addressing_write and lnp_integrity_write are not thread-safe, there is a little patch fixing this in the lnpd tarball. (25 years ago, 29-Feb-00, to lugnet.robotics.rcx.legos)
|
| |
| | Never mind
|
|
Well, my so-called "working" program crashed again, after adding two sleep statements and two sound calls, neither of which my program actually got to. So, I guess there are other causes behind my hangs as well. Ah the joys. :) -- "Though I am not (...) (25 years ago, 29-Feb-00, to lugnet.robotics.rcx.legos)
|
