|
PureBytes Links
Trading Reference Links
|
Carroll:
My experience has been that the box has no problem connecting. This is with
satellite. I believe that if the channels become unlocked on cable, it is
possible for it to scan through a particular channel, trying to nail down
the right band. It should be solid once it does this. Apparently yours is
not. You also should be able to see that this behavior is underway from
looking at the LCD.
#2 rarely happens for me. My server usually picks up the date right away.
In regards to #3 in your list, this is a behavior that I have had, although
it has mostly been on Win95 due to "Plug and Pray". The problem for me was
Windows detecting a mouse where my BMI signal was coming through the com
port. The solution: disconnect the serial port into the computer. Boot up.
After Windows comes up, reconnect the BMI signal to the serial port. It
doesn't happen very often for me with Win98, and different computers are
more/ less susceptible to this kind of baloney from my past experience.
Than again, it could be something totally different.
In regards to #4, you may have a bad box on your hands. But I'm no expert.
Patrick White
----- Original Message -----
From: Carroll Slemaker <cslemaker1@xxxxxxxx>
To: <omega-list@xxxxxxxxxx>
Cc: Johnson, Scott <SJohnson@xxxxxxx>
Sent: Wednesday, August 25, 1999 7:09 PM
Subject: Normal Operation for BMI/cable receiver???
> I have just switched from Signal/cable to BMI/cable and need some info
from
> other BMI/cable subscribers.
>
> 1. During receiver "profiling", the BMI tech told me that when the
software
> (TS4.0 in my case) which interfaces with the receiver is shut down, the
> receiver often becomes confused and "locks up" (his phrase). If this
> happens, it is necessary, he said, to power the box down, wait about 15
> seconds, then reapply power.
>
> 2. With the box powered up I terminated the BMI server to do some data
> converting using the offline servers, then later reinitiated the on-line
BMI
> server. It failed to connect to the box, continually looping through the
> various baud settings. I went through the recommended procedure -
> terminated the server, powered the box down, waited, reapplied power,
> re-executed the server, and all was OK.
>
> 3. Later, after more offline converting, etc., I rebooted my computer
with
> the BMI box still up and running. As the desktop came up (Win NT 4, SP5),
> the cursor behaved strangely, moving in a very jerky fashion and often
> jumping around the screen without my touching the mouse. Also, pop-up
menus
> would occasionally appear spontaneously, selection rectangles would
appear,
> etc. etc.
>
> I killed the BMI box and behavior returned to normal. I rebooted again
(to
> be safe), repowered the box, reinitiated TS, and all is now well - so far.
>
> 4. I spoke with another BMI tech and recounted my experiences and also
what
> the earlier tech had told me. This tech said he was unaware of any such
> problem with BMI boxes in general and that perhaps I had a bad box (this
is
> my second - the first one wouldn't lock onto the channel).
>
> So here's my question: Are the rest of you experiencing the same bizarre
> behavior by your BMI/cable receivers, or do I in fact have a bad one?
>
> Thanks.
>
> Carroll Slemaker
>
>
>
|