 | | Robolab conflicts with PC Duo NetSupport
|
|
Robolab 2.0 fails to load when used on a Win2000 PC running several recent v5.x and v6.x versions of PC Duo NetSupport network monitoring package. This has been confirmed by several schools here in the UK. It is a NetSupport problem due to a non MS (...) (25 years ago, 9-Sep-01, to lugnet.robotics.rcx.robolab)
|
| |
 | | Re: LegOS forced to use another name?
|
|
(...) In the US, at least, a trademark *must* be defended, or the company loses it. If legOS does, in fact, infringe on their trademark, they would have had to defend it pretty quickly or that usage would pass into the public domain. Or something (...) (25 years ago, 10-Sep-01, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: LegOS forced to use another name?
|
|
(...) This has all come as quite the surprise to me! As has been pointed out, TLC must have known about the LegOS name for quite a while! Now I am getting slightly worried whether we (hitechnicstuff.com) might come under closer scrutiny since the (...) (25 years ago, 10-Sep-01, to lugnet.robotics)
|
| |
 | | Re: LegOS forced to use another name?
|
|
(...) I concur. If I manufactured a new extra-cushiony disk storage system that used *really* tiny sponges for support, and I called it Micro-Soft, I'm sure I'd get a letter. This particular case has the added spin of stepping soundly into the "LEGO (...) (25 years ago, 10-Sep-01, to lugnet.robotics.rcx.legos, lugnet.general, lugnet.mediawatch)
|
| |
 | | Re: LegOS forced to use another name?
|
|
(...) So, if they had sued him 2.5 years ago, you would have supported them? Just wondering. It's because of thinking like this that most companies would have sued him long ago... Troy PS: I thought it was just common sense, atleast around here, (...) (25 years ago, 10-Sep-01, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: LegOS forced to use another name?
|
|
The way I read the article it didn't seem that they were so much upset that he had come up with the new OS, but rather that he had named it legOS. No matter how you look at it, or what excuse he can come up for choosing that name, it is pushing the (...) (25 years ago, 10-Sep-01, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.general, lugnet.mediawatch)
|
| |
 | | RE: Instructions for LegOS USB support (*nix)
|
|
(I mention this in the context of Mindstorms, but this info is useful for many other applications) If your machine is fairly large (lots of memory, fast cpu) there's a way I'm almost positive it could be done with *nix, but not for free: VMWare ( (...) (25 years ago, 10-Sep-01, to lugnet.robotics)
|
| |
 | | Re: LegOS forced to use another name?
|
|
(...) I agree with you, Jürgen. It seems that we have to contend with taht viewpoint though. Hopefully if any of tyhe new product line doesn't do as well as expected, we will not see some genius in the company decide to go after people who add value (...) (25 years ago, 10-Sep-01, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.general, lugnet.mediawatch)
|
| |
 | | Re: RCX 1.5, 2.0 firmware, and remote control
|
|
(...) Hi Steve I don't think so. I downloaded the 2.0 firmware (3.28) to my RCX 1.0 and 1.5, and all of them respond properly to the remote control. I'm sorry I cannot help more. Mario (25 years ago, 10-Sep-01, to lugnet.robotics)
|
| |
 | | RCX 1.5, 2.0 firmware, and remote control
|
|
I've got an RCX 1.5, into which I've downloaded the 2.0 firmware. I've just got an Ultimate Accessory Set, and I can't get the RCX to respond to the remote control. I know the RC is definitely transmitting, but the RCX ignores it. Could this be an (...) (25 years ago, 10-Sep-01, to lugnet.robotics)
|