Subject:
|
Re: legOS 0.2.4 working under WinNT 4(SP5) and Win2K
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Sat, 17 Jun 2000 11:40:04 GMT
|
Viewed:
|
1340 times
|
| |
|
|
"Luis Villa" <liv@duke.edu> wrote in message
news:Pine.SOL.3.91.1000615012634.538G-100000@teer13.acpub.duke.edu...
> > 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 :(
It's a must, Luis... ;-)
> > 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...
Strange (famous programming quotation)... ;-) Can I have your modification
to test them on my machine?
> > 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(?)
??? I have Win2k. No problem here with TOOLPREFIX.
> > 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.
More alse the E-Mails I've sent to you today.
> > 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.
IR Tower battery low and light contitions can broke fast upload... I'm now
with a low battery, I'll try to make it more error-insensitive.
> > 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?
It works on my Win2k-cygnwin platform, but I need to put path for dll
because I've not util in my bash path:
$ make helloworld.lx && ../util/dll helloworld.lx
Bye,
Paolo.
---
Maier's Law: If the facts do not conform to the theory, they must be
disposed of.
|
|
Message is in Reply To:
7 Messages in This Thread:
   
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
