Termlite on Win98 Problem

[Mike]

I have a problem with connecting SCO Termlite on a Win98 machine to SCO
Openserver via TCP/IP. Everything was great until I tried installing
Frontpage and PWS, now I can't connect to the host machine via termlite.
Any ideas? All other Win95 and 98 terminals are ok, it's just mine that
"cannot connect to host".

I've already 1) uninstalled the FP97 and PWS. 2) Removed Termlite and
reinstalled it, several times. 3) Rebooted the host machine (just in case).

I have downloaded Tera Term and Ipswitch's VT320 emulator but would really
like to get Termlite functioning again. Any suggestions would be greatly
appreciated. Thanks!

Mike

[Grant Walters]

> Any ideas? All other Win95 and 98 terminals are ok, it's just mine that
> "cannot connect to host".
>
> I've already 1) uninstalled the FP97 and PWS. 2) Removed Termlite and
> reinstalled it, several times. 3) Rebooted the host machine (just in
case).
>
> I have downloaded Tera Term and Ipswitch's VT320 emulator but would really
> like to get Termlite functioning again. Any suggestions would be greatly
> appreciated. Thanks!
>

Try deleting the Termlite.cfg file from the Windows directory, all of
Termlite and then reinstall.

Regards
GRANT WALTERS

[Roberto Zini]

A shot in the dark; try by grabbing the winsock.dll library from
a working machine and place it on the "offending" one (same
path, of course - it should either be C:\WINDOWS\ or C:\WINDOWS\SYSTEM,
not quite sure).

Does it work now ?

Best,
Roberto
--
---------------------------------------------------------------------
Roberto Zini email : fr...@strhold.it
Technical Support Manager -- Strhold Sistemi EDP Reggio Emilia(ITALY)
---------------------------------------------------------------------
"Has anybody around here seen an aircraft carrier?"
(Pete "Maverick" Mitchell - Top Gun)

[Mike]

Roberto,

You are the MAN!! I did what you suggested and it looks like it worked. I
also restored (extracted) wsock32.dll, explorer.exe, and rundll32.exe from
the cabs directory. But I think your suggestion did the trick.

Thanks for the input!

Mike

--

Michael Whatley
Hoffman Distributing Co, Inc.
http://hoffmandis.com
mi...@hoffmandis.com

"Roberto Zini" <fr...@strhold.it> wrote in message
news:3A02B627...@strhold.it...

[Roberto Zini]

Mike wrote:
>
> Roberto,
>
> You are the MAN!! I did what you suggested and it looks like it worked. I
> also restored (extracted) wsock32.dll, explorer.exe, and rundll32.exe from
> the cabs directory. But I think your suggestion did the trick.

Honestly, I'm not that kind of MAN; the above workaround was suggested
by a SCO techie to whom I raised a similar problem. After a couple of
weeks of testing, he/she was able to solve this issue by replacing the
"offending" winsock.dll library with a working copy from a "good"
machine.

You can now perform a "kudos add" to the above path (the long blasted
SCO's tech support :-)

>
> Thanks for the input!
>

Thanks for the feedback !