Hello Maurice!

04 Oct 03 20:08, you wrote to me:

 BS>> Sorry, for beeing abit away, but I changed ISP, so there has been
 BS>> a bit networking work.

 MK> That can happen.  With me I am trying to switch over to a new
 MK> partition but want to build up a few libraries first.

Okay.. A bigger one?

 MK>>> Beats me.  I don't use OS/2.  I just thought it might be simular
 MK>>> to the UNIX fix.

 BS>> Okay, oh well, I see :-)

 MK> I don't but just threw out a guess.

Heh okay.

 MK>>> Yep.  I grepped it in one of the c files.  I'll get back to you
 MK>>> on it as soon as I figure out how Maximus calls it.  That might
 MK>>> be an eye opener.

 BS>> I can't see why it's calling it?

 MK> It's the waiting for caller screen that's calling it.  I think it
 MK> might need proper initialization but then it'll be different for
 MK> glibc-2.3.x then for earlier versions.

Ofcause. I know there is a sleep() vs usleep() issue, especially on Win32 vs. Linux.

 MK> If I have a say in this I vote
 MK> the Linux port just forget the waiting for caller screen altogether.
 MK> I don't think it is needed or wanted in Linux.  Just my two cents.

No that's right, because it's running in the background.. Maybe the caller
screen should be in some seperate program, which is doing some IPC with the
BBS processes.. We gotta remember this is a Multi line BBS system :-)

Regards,
Bo

--- GoldED+/LNX 1.1.4.7