 | | Re: reliability of quad speed LNP
|
|
(...) Probably depends on the make-up of the data you're transferring. ROSCO (23 years ago, 28-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: reliability of quad speed LNP
|
|
So with inverting every other message byte were you able to work at 4x? Were you then also able to work at close range at 4x? It would seem easy to patch LNP to automatically do this inversion. I'll have to give this a try. thanks, mark (23 years ago, 28-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RFC: Creation of Version 0.2.6
|
|
(...) We asked our lawyers about this many months ago, when the whole issue first came up. It's okay with them if the name "legOS" is used in a "formerly known as" context. Just like what you describe, basically - to make sure people understand that (...) (23 years ago, 27-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: reliability of quad speed LNP
|
|
"Mark Falco" <falcom@onebox.com> wrote in message news:Gs44C0.MGL@lugnet.com... (...) <<snip>> I'm not familiar with LNP but I have also experienced similar messaging problems. I have an old RCX 1.0 (S/N 22751) with serial tower and a newer RCX 2.0 (...) (23 years ago, 27-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: reliability of quad speed LNP
|
|
I have found that between a rather old PC and a RCX I cannot use quad speed transfer of data as the RCX cannot keep up. When a different (faster) PC and the same RCX I can use quad speed transfer. I guess it comes down to protocol timing. LNP does (...) (23 years ago, 26-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | reliability of quad speed LNP
|
|
Does anyone have any data on the reliability of quad speed LNP? I've been using quad speed LNP for downloading programs to my 1.0 RCX for some time, and never had a problem. Recently I'd bowored a friends 1.0 RCX so that my bot could have two RCXs. (...) (23 years ago, 25-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RCX as a PGP engine
|
|
(...) IIRC, the algorithm doesn't need floating point ops, only very very large primes. (...) yah - I don't think the RCX will have a good generator of random numbers. cool idea, I'd be interested to see if it works :) Dan (23 years ago, 24-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RCX as a PGP engine
|
|
Looked at some of the source code involved. Have a look at the "Gnu Privacy Guard" variant's source at: (URL) I was just thinking, would the RCX be able to implement a PGP or RSA (...) I don't think there is enough room for the WHOLE PGP package in (...) (23 years ago, 23-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | RCX as a PGP engine
|
|
So I'm a bit behind on my reading list and I'm finally working through Steven Levy's fascinating book "Crypto" on the history and development of Public Key Incription and such. Great stuff. I was just thinking, would the RCX be able to implement a (...) (23 years ago, 23-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: problems using firmdl3 and dll on Red Hat 6.2
|
|
(...) The proper way to manage the /etc/rc.d scripts with RedHat at least is chkconfig. So the proper command (as root) after moving the link back from /unused would be: chkconfig --level 0123456 gpm off More info is at the man page for chkconfig. (...) (23 years ago, 20-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: problems using firmdl3 and dll on Red Hat 6.2
|
|
(...) That file should just be a soft link to /etc/rc/init.d/gpm (or ../init.d/gpm), so there's no need to keep it. ROSCO (23 years ago, 19-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: problems using firmdl3 and dll on Red Hat 6.2
|
|
(...) Oh, on the console you might have gpm running, which allows copy-paste on the console with the mouse. As root, run '/etc/rc.d/init.d/gpm stop' and see if it gets better. To turn that off completely edit /etc/sysconfig/mouse and set (...) (23 years ago, 19-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: problems using firmdl3 and dll on Red Hat 6.2
|
|
It is working! In case anyone else encounters this issue... here is the solution. Per Geoff Gerrietts: (...) I just moved the file to /unused (in case I wanted it back) and reboot'd. IR communication is working perfect. Thank You Geoff! <snip> (next (...) (23 years ago, 19-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: problems using firmdl3 and dll on Red Hat 6.2
|
|
"Joseph Woolley" <jwoolley@spamblock....ht.rr.com> wrote in message news:GrqxJG.Cwq@lugnet.com... (...) to (...) Also, when I installed RH, I had a mouse connected to the same serial port. I am wondering if the mouse driver is still loading and (...) (23 years ago, 18-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | problems using firmdl3 and dll on Red Hat 6.2
|
|
I recently cleared off my laptop HD and installed Red Hat 6.2, then downloaded and installed all the packages listed in the legOS HOWTO... but have run into a couple snags. 1st and most important, I am not able to send anything via the IR Tower. (...) (23 years ago, 18-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: multiplexor and legOS
|
|
I'm not sure if anyone is trying out my multiplexor patch, but thought I'd let you all know that I posted a new version which works better and solves some problems in the earlier revision. The patch is available in the legOS patch section on (...) (23 years ago, 17-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: linux USB driver.
|
|
Hi Hans, I think 2.4.9 is too old, but you may try to just remove the MODULE_LICENSE stuff. Jürgen (...) (23 years ago, 13-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RFC: Creation of Version 0.2.6
|
|
(...) You could also try BricxOS (in a similar fashion to BricxCC), which also happens to have RCX in it. Martin (23 years ago, 12-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RFC: Creation of Version 0.2.6
|
|
(...) me, (...) written, (...) and/or (...) Well, even though it has a few Unix-ie functions, I don't really see it as a -nix. My personal favourite is NogOS (for Marcus), but BrickOS is good, too. ROSCO (23 years ago, 12-Feb-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RFC: Creation of Version 0.2.6
|
|
(...) Basically four things: 1) Getting a sourceforge account and having me designate the person a maintainer. 2) Using sourceforge CVS to maintain the canonical CVS tree for legOS; this is basically very typical CVS stuff- committing the incoming (...) (23 years ago, 12-Feb-02, to lugnet.robotics.rcx.legos)
|
