| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 715.1 | more info | QUIVER::ORSHAW | | Wed Feb 09 1994 16:34 | 8 |
| Basically, the FTP stack would need to be "Winsock 1.1 Compliant". If FTP
shipped a file called "winsock.dll", chances are good it is compliant.
Check the FTP documentation for details. Be sure winsock.dll is in the
path somewhere.
We haven't had time to try this yet but it's in the works.
Jim
|
| 715.2 | Its ready for Token Ring | WOTVAX::STUS::Stuart Hatto | ACB actually means A Cold Beer | Thu Feb 10 1994 05:53 | 7 |
| Colin the 4M/b Ethernet is actually greyed out in the VMS version.
This is for Token Ring. I think it is a small bug in the Windows version
to allow this to be seen. The speed qualifier actually has no effect when
setting up an Ethernet LAN.
Stuart
|
| 715.3 | FTP stack trial | WOTVAX::CLOWESC | Colin Clowes | Tue Feb 15 1994 05:07 | 11 |
| Hi,
The FTP stack does have WINSOCK.DLL and I modified the path to point to it, I
also tried copying it to the \HUBWATCH\IPSTACK directory but I cant get it to
work !
Any suggestions would be realy appreciated
Thanks
Colin
|
| 715.4 | WINSOCK-->\WINDOWS | WOTVAX::HATTOS | I think, Therefore I'm paid less | Tue Feb 15 1994 05:55 | 10 |
| Col,
WINSOCK.DLL should be in the \WINDOWS directory.
Have you changed Windows setup to use the FTP Network?
I am back in on Thursday if it can wait that long, I will try and help
more then!
Stuart
|
| 715.5 | Hubwatch and Wollongong Pathway ? | HLDE01::BLOM_R | | Mon Feb 28 1994 13:10 | 8 |
| Has anyone tried to get Hubwatch for Windows T2.x to run on top of
Wollongong Pathway Runtime 1.2.0.1 or 2.0 ? It includes a windows
socket DLL, but I have no idea to which standard it conforms.
I will have to try it anyway, but at the moment I am just plain lazy :-)
Rudi Blom @APD
WGS / DECadvantage support
|
| 715.6 | Hubwatch and ftp | MSE1::TOBIN | | Tue Mar 15 1994 15:38 | 11 |
| Has anyone been able to get hubwatch to work on top of the ftp tcp/ip stack? I
have installed FTP's PC/TCP Network Software for DOS version 2.2. I had Hubwatch
running on the stack that it comes with, but once I installed the FTP stack,
windows hangs when I click on the Hubwatch icon. I am also running Mosiac on the
same PC, which uses the IP stack, and it runs. I am also running Windows for
Workgroups with the LAN MANAGER protocol. If anyone has gotten Hubwatch to work
with FTP please post how to set it up. Any help would be great.
Thanks
John Tobin
|
| 715.7 | TCP/IP stack must be WINSOCK compliant | NAC::FORREST | | Wed Mar 16 1994 08:55 | 7 |
|
> FTP's PC/TCP Network Software for DOS version 2.2.
My first guess is that this stack was developed for DOS not Windows.
Do you know if this version claims to be WINSOCK compliant?
Look for a file called WINSOCK.DLL
|
| 715.8 | Winsock.ini | MSE1::TOBIN | | Fri Mar 18 1994 08:12 | 5 |
| Yes, it does have a winsock.dll file. I am able to run windows mosaic
which uses the winsock interface. Hubwatch is the only TCP/IP application that
I am having a problem.
John
|
| 715.9 | vendors can implement the spec slightly differently... | NAC::FORREST | | Wed Mar 23 1994 17:19 | 14 |
|
I heard of another product that worked unchanged on a couple of
vendors' WINSOCK implementations, but wouldn't work on FTP's.
Just a data point - I'm not saying there's anything wrong with
FTP's implementation.
One of the things we want to do before V3.0 ships is test with
the leading stacks. We didn't have time to do that for V2.0, so
it's only guaranteed to work with the included Pathworks stack.
If you want to send me mail with the error message that you're
getting, we'll try to take a look.
jack
|
| 715.10 | Installation suggestions. | CGOS01::DMARLOWE | Have you been HUBbed lately? | Thu May 12 1994 01:52 | 23 |
| I'm not a PC or TCP person so any assistance would be greatly
appreciated.
I've been trying to configure HUBWATCH and PC with other than DEPCA's,
etc. and running into problems. One customer I have is running
Windows for Workgroups V 3.1.1 with PATHWORKS integration. We finnally
got things more or less straightened out. There is a WINSOCK.DLL
so thought meybe we're getting close. No TCP errors on boot and
the initial screen comes up for HUBWATCH. When enter a IP address
and click ok an error message, "SOCKET CAN'T BE CREATED" error message
comes up. What does this error mean? Areas to look at to fix?
They are using a 3C503 card.
Also the installation manual is not helpful at all. It just echos
what the PC screens say. No examples as to what could be entered
in on any lines. For example when setting up the network it asks
for PATH and DRIVER? I assume the TCP driver. What are some example
file names and what directory would they normally reside in?
Thanks in advance.
dave
PS. What do you mean this thing doesn't have VMSINSTAL! 8^(
|
| 715.11 | Any suggestions on installation? | CGOS01::DMARLOWE | Have you been HUBbed lately? | Wed May 18 1994 02:14 | 1 |
| dave
|
| 715.12 | Same problem with DEFEA | LEVERS::KIRK | tis a gift to be simple | Wed May 18 1994 08:45 | 5 |
| I am having this same problem with a DEFEA FDDI NIC and Hubwatch.
Is there a solution?
Dick Kirk
|
| 715.13 | fix on the way, hopefully | NAC::FORREST | | Wed Jul 06 1994 19:11 | 4 |
|
Our plan is to use whatever the PATHWORKS install supports in our
next release. Whatever they support, we will support. If we run
our of time, then look for a fix in V4, rather than V3.1.
|