| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 952.1 | | CLOUD::SHIRRON | Stephen F. Shirron, 223-3198 | Thu Jun 15 1989 13:09 | 19 |
| $ MCR SYSGEN
SYSGEN> CONF
DEVICE> vcb02,8
DEVICE> ^Z
Device: VCB02 Name: VAA CSR: 777400 Vector: 300* Support: yes
Device: VCB02 Name: VAB CSR: 777402 Vector: 314* Support: yes
Device: VCB02 Name: VAC CSR: 777404 Vector: 334* Support: yes
Device: VCB02 Name: VAD CSR: 777406 Vector: 354* Support: yes
Device: VCB02 Name: VAE CSR: 777410 Vector: 374* Support: yes
Device: VCB02 Name: VAF CSR: 777412 Vector: 414* Support: yes
Device: VCB02 Name: VAG CSR: 777414 Vector: 434* Support: yes
Device: VCB02 Name: VAH CSR: 777416 Vector: 454* Support: yes
SYSGEN> ^Z
A device at 777414 or 777416 will be seen as a VCB02, and the driver (assuming
DECwindows) is GAxDRIVER, so this explains what you're seeing.
stephen
|
| 952.2 | Old problem | MUNCSS::KARI | | Fri Jun 16 1989 04:26 | 8 |
|
The solution is to configure manually those "exotic" interfaces
before SYSGEN does the AUTOCONFIG.
Edit your STARTUP command file to load/connect the proper driver(s)
and interface(s).
Kari
|
| 952.3 | Ok, buglet in DECW$DEVICE.COM | COMICS::BELL | Champion of the Lost Cause | Fri Jun 16 1989 08:10 | 19 |
| Thanks for the help.
1) The device causing the problem was the controller for a Versatec
36" plotter : different vector so no VECINUSE error, just stopped
it from working.
2) It *was* configured in manually (and presumably the global symbol
STARTUP$AUTOCONFIGURE_ALL set up accordingly) but unfortunately
DECW$DEVICE.COM decides to do a SYSGEN AUTOCONFIGURE ALL for itself,
regardless of the state of the above flag.
The workaround I've provided is to hack DECW$DEVICE.COM to bypass
that line when executing on the 785. Does the appropriate developer
have this noted or do you want an SPR along the lines of "please
make DECW$DEVICE a bit more considerate" to get this fixed ?
[ It's sitting here, waiting to pounce ! :-) ]
Frank
|
| 952.4 | Something To Try: SYCONFIG CONNECT | VOX::SIMM | Steve, MLO, 223-7186 | Fri Jun 16 1989 09:47 | 5 |
| Try connecting your unusual beasties from commands placed SYCONFIG.COM;
executed long before DECwindows gets around to doing an autoconfigure
for itself. By the time it does, your devices and drivers are already
in place.
|
| 952.5 | Sorry. | COMICS::BELL | Champion of the Lost Cause | Fri Jun 23 1989 09:32 | 13 |
| Re : .4
Turns out he was only loading the 3rd party devices in SYSTARTUP_V5
so the offending AUTOCONFIG ALL was the ordinary one in VMS$SYSFILES,
nothing to do with the DECW$DEVICE one.
I apologise for jumping in with both feet.
Frank
[ Ever want to put your hand down the phone and throttle the guy at the
other end ? Or were you thinking of doing the same to me ? :-) ]
|