Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-unix!hplabs!ucbvax!YALE.ARPA!LEICHTER-JERRY
From: LEICHTER-JERRY@YALE.ARPA
Newsgroups: mod.computers.vax
Subject: Re: sysgen connect vta0 does not work from syconfig.com
Message-ID: <8611241638.AA10744@ucbvax.Berkeley.EDU>
Date: Mon, 24-Nov-86 11:38:26 EST
Article-I.D.: ucbvax.8611241638.AA10744
Posted: Mon Nov 24 11:38:26 1986
Date-Received: Mon, 24-Nov-86 23:32:15 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: <LEICHTER-JERRY@YALE.ARPA>
Organization: The ARPA Internet
Lines: 22
Approved: info-vax@sri-kl.arpa


    I can get sysgen to connect vta0 when used interactively, but when it is
    run at startup from syconfig.com the same command fails with the message
    `sysgen-e-nounload, driver not unloadable'....  The only unusual thing on
    this system is that I've redefined sys$system to be a path with
    sys$sysroot:[sysexe] and a local software directory, but I dont' see how
    that could affect this.
I've seen connect's of vta0 work fine in system startup files, so there's
nothing generically wrong here.  I'll make a guess:  Somehow or another, you
are trying to connect the driver twice, and the second try is crapping out.
One way this MIGHT happen is if you somewhere have a loop that looks for all
command files that match some spec and execute them.  If you had copies of
the same command file in both SYS$SYSROOT:[SYSEXE] and the local software
directory, you might find some file twice...but this is guesses on top of
guesses.

Note that F$GETDVI("VTA0:","EXISTS") will be TRUE if and only if the VT driver
has already been connected.  Have the command file where the problem occurs
check and tell you if it finds the device already there; then you'll know if
my guess was right.
							-- Jerry
-------