| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
I'm writing a small piece of code to exercise the Ethernet controller
on a VAXStation, and this code has worked on a VAX 6000 with VMS
V5.2.
However, on the VAXStation, DECWindows has been installed and I
can't see the device ESA1, only ESA0 which is the "template only
device" for the Ethernet controller. Normally, I would see both
devices (when I do a SHOW DEVICE in DCL) and my program would
communicate with ESA1 (or ETA1 depending on the system).
Question is, did DECWindows have anything to do with this missing
device ? If so, can I remove the problem by not starting DECWindows
in the system startup file ?
I'd appreciate any help.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2193.1 | BOMBE::MOORE | BaN CaSe_sEnSiTiVe iDeNtIfIeRs! | Fri Feb 02 1990 19:34 | 8 | |
Sounds to me like you're not playing by the rules.
Is DECnet running, or LAT, etc? The device units you are looking for
are created on an 'as needed' basis, depending upon what protocols may
be active on the system. There is no guarantee that any unit other
than zero will exits at any given time. You should be creating your
own unit (cloned from unit zero) for your own use, not 'borrowing' one
of unknown origin.
| |||||
| 2193.2 | You're right... | BRADOR::FALARDEAU | Mon Feb 05 1990 14:05 | 3 | |
You're right. Turns out the NETCONFIG command procedure hadn't
been run yet, and that's what defines my device.
| |||||
| 2193.3 | RAMBLR::MORONEY | How do you get this car out of second gear? | Sun Mar 25 1990 13:56 | 5 | |
In case it wasn't clear from .1, you SHOULD be using ESA0: (or ETA0:, or whatever), not ESA1:. I'm suprised you aren't crashing DECnet or some other application. -Mike | |||||