Re[2]: The Bat messing with Dial Up Networking?

[Kevin Boylan]

Hi,

> Yes, it happened to me once after i checked the "no automatic dial
> for periodic checking" Checkbox. The Dialup monitor showed up just
> for a second and vanished again. It left a TapiServer process
> running that I couldn't kill with the Task Manager and i had to
> reboot to use the COM port again. (only shutting down TheBat was not
> enough)

In my case, that box isn't checked and I've never checked it.  But
they could still somehow be related.

Also, it doesn't seem to be the com port itself as I can still use
something like Hyperterminal that uses the port directly (doesn't use
dialup networking) when it gets in this state.

-- 
Thanks,

Kevin

Using The Bat 1.38 Beta/4 on Windows NT4.0 Build 1381 Service Pack 3



-- 
--
View the TBBETA archive at http://tbbeta.thebat.dutaint.com
To send a message to the list moderation team double-click HERE:
   
To Unsubscribe from TBBETA, double-click HERE:
   
--

Re: The Bat messing with Dial Up Networking?

[Peter Steiner]

On Saturday, November 27, 1999, 4:51:43 PM, Kevin Boylan wrote:

> Sometimes I'll click to send and receive and the dialup monitor will
> minimize.  I show it again and it just says disconnected and sits
> there.  If I try manually clicking the dialup networking icon I get an
> error 633 (it thinks the port is busy).  If I shutdown The Bat,
> everything is ok.  However, sometimes it requires a reboot.

Yes, it happened to me once after i checked the "no automatic dial for
periodic checking" Checkbox. The Dialup monitor showed up just for a
second and vanished again. It left a TapiServer process running that I
couldn't kill with the Task Manager and i had to reboot to use the COM
port again. (only shutting down TheBat was not enough)

I'm not sure if it's related to "no automatic dial for periodic
checking", but i had it unchecked again and then the problems stopped.
But then i often just use an existing connection, so i have no
significant statistics that it really stopped, it could be just
coincidence.

Peter
-- 
Peter Steiner <[EMAIL PROTECTED]>
"U dene n ischs i d Chnöde glöötet wie bschüttigs
Chrüzimääl düre Chätschabertrog." - Franz Hohler

-- 
--
View the TBBETA archive at http://tbbeta.thebat.dutaint.com
To send a message to the list moderation team double-click HERE:
   
To Unsubscribe from TBBETA, double-click HERE:
   
--

The Bat messing with Dial Up Networking?

[Kevin Boylan]

Hi,

Has anyone else had noticed The Bat causing Dialup Networking to act a
bit funny ever since the version that added more control over dial up
networking?  I have been going crazy trying to figure out what is
causing it since I did add some other software at the same time.

Sometimes I'll click to send and receive and the dialup monitor will
minimize.  I show it again and it just says disconnected and sits
there.  If I try manually clicking the dialup networking icon I get an
error 633 (it thinks the port is busy).  If I shutdown The Bat,
everything is ok.  However, sometimes it requires a reboot.

The reason I was thinking that it couldn't be The Bat was that
sometimes this will happen when I first boot up.  But then I realized
that sometimes The Bat is still running when I shutdown and maybe NT
tries to start it up again upon boot up?

This keeps happening though, where everything will be fine, I can
connect with The Bat several times and then for no reason (that I know
of) this will happen.

Has anyone else seen any strange behavior with their dialup neworking
since they installed, I think beta 3?  I'm not sure of the version
right now, it was definitely the version that added the dialup
networking stuff though.

-- 
Thanks,

Kevin

Using The Bat 1.38 Beta/4 on Windows NT4.0 Build 1381 Service Pack 3



-- 
--
View the TBBETA archive at http://tbbeta.thebat.dutaint.com
To send a message to the list moderation team double-click HERE:
   
To Unsubscribe from TBBETA, double-click HERE:
   
--