On Thu, 12 Aug 1999 20:44:27 +0200, Bernie wrote:
> I have never had any (16-bit) version of Netscape or Opera work
> if they aren't started with a connection. If I start one of them
> then and then try to log in I will NOT be able to use them (closing
> them down doesn't help - that will just stop me from relaunching
> them).
If you have WINSOCK.DLL in a directory searchable through PATH env
variable, virtually all 16-bit winsock apps will use it to open a
connection automatically when launched. The calling apps will wait
patiently in background, and will only open it's window when TCP/IP
connection established. If for some reason WINSOCK.DLL failed, the
calling apps will remain stagnant -- the same also happen to any
other winsock apps launched after it (including it's own new
instances when relaunched).
On Thu, 12 Aug 1999 11:56:30 -0700, Carl Wheeley wrote:
> 1. I have taken out the path=c:\trumpwsk from the autoexec.bat
> file, and indeed it seems to make no difference when it is
> removed. No, I don't use the same Winsock.dll with Opera/Trumpet
> as I do with IE. (I re-name Winsock.dll in IE when I'm trying
> Opera/Trumpet and the opposite when I'm running IE.)
Did you said before that you have no trouble connecting with IE?
This means that you already have a well-configured winsock in your
IE directory. If this also Trumpet winsock (same version), you
could simply copying it's script files (*.CMD) and TRUMPWSK.INI
to c:\trumpwsk, then put back path=c:\trumpwsk. If not, just add
IE directory (where the working WINSOCK.DLL resides) to your path=
line, and rename all WINSOCK.DLL in another directories.
--Eko
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
