Subject:
|
Re: legOS 0.2.4 working under WinNT 4(SP5) and Win2K
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Thu, 15 Jun 2000 05:31:38 GMT
|
Viewed:
|
1268 times
|
| |
|
|
On Thu, 15 Jun 2000, Gary Mayer wrote:
> Comments 1 - 6 all refer to the LegOS 0.2.4 for Win instructions:
> 1) Your links refer to "LegOS-pre0.2.4.tar.gz". It is now
> "LegOS-0.2.4.tar.gz".
My fault.
> 2) When un-tarring the file, it creates the directory "legOS-0.2.4". This
> must be renamed to "legOS".
Personal choice, here. I keep several versions on my machine, and since I
created the tarballs, it says 0.2.4. If that breaks the cygwin installs,
well, then, I guess I'll change it :(
> 3) Under WinNT 4.0 I tried avoiding modification of the autoexec.bat file
> and just using the modification to /LegOS/Makefile.common described in Step
> 4. It didn't work. I had to enter it into the autoexec.bat PATH.
Paolo? This is your area of expertise...
> 4) In \legOS\Makefile.common, you have an automatic OS detection function to
> determine which setting will be used for TOOLPREFIX. In Win2K, it did not
> work. I had to specifically comment out the Linux line setting.
I'll check and see if this is W2K specific tomorrow. There are some known
issues with the same problem under djgpp, but Paolo may have a patch for
it(?)
> 5) In Step 7, I was unable to find the command firmdl3, firmdl3.exe, dll, or
> dll.exe when using Cygwin. I had to upload the firmware and the .lx file
> using the Command Prompt in order for the system to find the commands.
> Suggest mentioning this.
OK. I think I can clarify that.
> 6) Also in Step 7, when using "firmdl3 ../boot/legos.rec" I received the
> following error:
> firmdl3: no response from rcx
> I had to use the firmdl3 -s option to use the slower speed. Suggest
> mentioning this in the instructions.
I think something about this will probably go into the HOWTO, which I
hope these instructions will shortly be integrated into.
> Comments 7 - 8 are against the \legOS\README file:
> 7) Mention is made to add \legOS\util to the system PATH. Suggest this be
> placed in the instructions so the user need only go there once.
Probably a good idea, though again it might be better suited to be in the
HOWTO since it is a cross-platform suggestion (i.e., not just for cygwin.)
> 8) The user is told to compile the .c program with "make myproject.lx &&
> dll myproject.lx". Running this from either Cygwin or Command Prompt
> resulted in an error. The .lx was created but it choked on the &&.
> It worked fine when the command was split into 2 - "make myproject.lx" and
> then "dll myproject.lx"
Ahh. A Unixism. I'm curious- are you running this all at the Cygwin
prompt or from within bash?
> All are minor but may help the next newbie who comes along.
Feedback is what makes this all work. Thanks for it.
Luis
> Thanks again,
>
> -- Gary Mayer
>
>
-----------------------------------------------------------------------
"Going to California with an aching in my heart.
Someone told me there's a girl out there
with love in her eyes and flowers in her hair."
-Led Zeppelin, "Going to California"
-----------------------------------------------------------------------
|
|
Message has 1 Reply:
Message is in Reply To:
7 Messages in This Thread:
   
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
