Subject:
|
Re: BricxCC on Win XP how
|
Newsgroups:
|
lugnet.robotics.rcx
|
Date:
|
Fri, 21 Feb 2003 15:09:33 GMT
|
Viewed:
|
3254 times
|
| |
|
|
In lugnet.robotics.rcx, Pat LaVarre writes:
> > Does the tower light come on at all?
>
> It never goes off, sorry. I'm the one who posted:
> http://news.lugnet.com/robotics/rcx/?n=1947&t=i&v=a
> Date: Thu, 6 Feb 2003 12:29:35 GMT
> Subject: constant green light
>
> In short, here in Win XP SP1, the green LED light of my serial/IR tower stays
> On unless I open a COM port and then I don't speak for about five seconds.
> Merely closing the COM port turns the light back On, reopening the COM port >waiting turns the light back Off. I don't know how to fix this, except by
> booting Linux in place of Win XP SP1.
If your green light is on all the time I am amazed that you are successful
with any communication. Do you need to do the "open the port and wait 5
seconds" procedure to get RIS, javax.comm, and nqc to work?
Something BIOS or hardware-related seems to be badly interacting with WinXP
on your laptop. I can add a registry setting/command-line switch to BricxCC
that makes it wait N seconds each time it opens the port. Unfortunately, it
has to close the port on occasion and reopen it - to compile and download
NQC, MindScript, LASM, and brickOS code for instance. Better, I think, to
solve your hardware/BIOS/WinXP issue (which I think is eminently solvable).
I'd look at your BIOS configuration for anything related to the serial port
and its settings. I'd check for BIOS anti-virus settings that might involve
your serial port. I'd check for BIOS settings related to power saving
settings (it might be monitoring your serial ports for activity).
I'd check the Control Panel/Power Options for any signs of COM port stuff
(on W2K the UPS tab lets you select which COM port the UPS will signal a
shutdown via, for instance). Mine has a note saying "the UPS service is
currently stopped". Maybe your UPS service is running and doing odd things
with your serial port?
You might try fiddling your COM port(s) via the control
panel/system/hardware/device manager. Check the resources being used by
your COM1 device. See if it lists any conflicts. I don't have XP in front
of me to verify that it is nearly identical to W2K, but here's how I would
do it via W2K. Try unchecking the "use automatic settings" checkbox. Try
choosing a different option in the Settings based on combo-box. On my
system I see a "Current configuration" and "Basic configuration" 0-4.
Different selections will result in different I/O ranges and different IRQs.
In any case, I'd check these sorts of things to see if they affect the
constant green light situation. That is almost definitely the source of
your problems with BricxCC.
John Hansen
|
|
Message has 1 Reply:
 | | Re: BricxCC on Win XP how
|
| I have a nasty feeling this a "facility" in windows at work here. I have noted that the "classic" ports (serial i/o and parallel) "jabber" when windows doesn't think they are in use. My suspicion is that there is some kind of a legacy port plug and (...) (21 years ago, 21-Feb-03, to lugnet.robotics.rcx)
|
Message is in Reply To:
| | Re: BricxCC on Win XP how
|
| Again intriguing, again I thank you. /// BricxCC Without Firmware /// (...) Yes, does BricxCC COM1 fail for anyone else when firmware is erased? Anyone? /// Versions /// BricxCC Help About tells me I have "3.3.7.2" of "2/12/2003". Bundled with (...) (21 years ago, 21-Feb-03, to lugnet.robotics.rcx)
|
9 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
|
|
|
|
