[W] Winsock files and directories

Matthew Sanderson (matthews@noc.tor.hookup.net)
Thu, 12 Oct 1995 23:42:43 -0400 (EDT)

Several recent posts discuss what Winsock/CU files
should be in which directory. Here's what I use:

D:\WFW <-- see note #1
CUSEEME INI 2,474 10-10-95 11:56p

D:\WINTCP <-- see note #2
SERVICES 2,840 10-09-93 5:12p
PROTOCOL 441 07-07-93 7:46p
HOSTS 96 10-07-94 5:26p
LOGIN CMD 1,472 06-13-95 10:59p
BYE CMD 65 12-29-94 10:34a
WINSOCK DLL 145,152 11-03-94 2:57p
TCPMAN EXE 119,040 11-03-94 2:57p
TRUMPWSK INI 1,187 10-12-95 10:18p

CTL3D DLL 21,008 11-24-93 9:38a
IVSLIDER DLL 37,828 08-03-95 8:58a
MSVIDEO DLL 39,600 10-28-92 12:00a
CUSEEME EXE 299,900 08-25-95 9:15a
CUSEEME HLP 33,418 08-02-95 10:15p

#1 For most PC's, this would be C:\WINDOWS. But I need/want to
have Win 3.1 and WfWG 3.11 on the same drive and thus name
them \WIN and \WFW respectively (on the D: of a 33/43/5
partitioned 80MB drive).
#2 So as not to have two instances of the Trumpet Winsock,
I keep it "up out of" the "Windows" directory by installing
it in \WINTCP. Winsock applications get their own directory
below \WINTCP eg \CU70B1, \NETSCAPE: incidentally allowing
two or more versions to be kept available for tests. Note that
CU-SeeMe insists on having its .ini in the "Win" directory.

I like to keep .dll's with the application -- both Trumpet and
CU allow this (notwithstanding the developers documentation that
says to put them in the "Win" or "Win/SYSTEM" directory).
File sizes, dates and times have been left in the listing to
aid in identifying modified vs original.

PS: If you find this useful, reply mail to me (NOT TO THE LIST)
with "Yes useful" and I'll put more detailed docs on my home page.

/ Matthew Sanderson CS: 70733,2700 'net: matthews@hookup.net \
\ http://www.hookup.net/~matthews /