| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3230.1 | | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Mon Feb 03 1997 15:19 | 8 |
|
It sounds like you're attempting to use decnet on W95. That requires
careful installation, and in fact may temporarily not be available. Please
see the pertinent notes in the Pathworks 32 Release notes for details.
I suggest that for now you use tcp instead of decnet for your apps.
/Eric
|
| 3230.2 | | SYSTEM::newdial_4.reo.dec.com::JOHNSON | Richard Johnson , http://samedi.reo.dec.com | Tue Feb 04 1997 05:29 | 27 |
|
I am using TCP/IP (rexec) to access my apps.
I did not state use of any particular protocol at
installation time. Should I have done?
My apps now do appear to be ok but:
When X server starts up I get:
04/02/97 10:24:50 X Server Information eXcursion T3.0.551
(Windows95) logging enabled.
04/02/97 10:24:51 Network Warning socket(12) failed,
error=EAFNOSUPPORT
04/02/97 10:24:51 Network Warning socket(12) failed,
error=EAFNOSUPPORT
04/02/97 10:24:51 Network Warning getnodeadd() failed,
error=EAFNOSUPPORT
The with each app I get:
04/02/97 10:26:11 Network Warning socket(12) failed,
error=EAFNOSUPPORT
04/02/97 10:26:17 X Application Startup Information rexec:
connection succeeded
04/02/97 10:26:20 X Application Startup Information OK
|
| 3230.3 | | PEACHS::GHEFF | Got a head with wings | Tue Feb 04 1997 08:43 | 20 |
| Hmm. Looks to me like you should be looking elsewhere for information.
My guess is that you have turned on the "Log Network Warnings" check
box on the Logging control panel. And you're getting a display of all
the checks that eXcursion goes through when it starts. It looks like
it's testing for DECnet and not finding it. Then it looks like its
testing for an serial type connection and not finding it. I don't
think that either of those is causeing a problem. If you still can't
get your apps to appear you need to look for information on the remote
host since the rexec connection is being made:
>04/02/97 10:26:17 X Application Startup Information rexec:
> connection succeeded
Socket(12), if I recall, is DECnet which you will not have on a Win95
system. Not yet, at any rate. (Actually, I could be wrong, 12 might
be LAT. Eric, did the LAT support get ripped out of the 3.0 code
stream when Multia went bye-bye?)
#Gary
|
| 3230.4 | | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Tue Feb 11 1997 15:58 | 8 |
|
It sounds like the customer's apps are appearing o.k. but that he's
just curious about the diagnostics that appear in the log window.
As for lat, I don't think we ripped it out, but of course one would need
to purchase Meridian Lat in order to use it.
/Eric
|
| 3230.5 | | SYSTEM::newdial_6.reo.dec.com::JOHNSON | Richard Johnson , http://samedi.reo.dec.com | Fri Feb 28 1997 07:06 | 10 |
| 28/02/97 11:13:04 Network Warning Async select failure detected
in wxwnproc.c, error = 10054
It is the above error I am curious about.
When ever that error is logged the application
(bookreader) freezes, though I can start another up.
Thanks
Richard
|
| 3230.6 | | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Fri Mar 14 1997 09:59 | 12 |
|
The 10054 code has symbol WSAECONNRESET.
The winsock 1.1 documentation, in the RECV section, describes that
error as
The virtual circuit was reset by the remote side
Does this fit with your situation ?
/Eric
|