| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 168.1 | Not a VT1000 / DECmcc V1.1 problem! | BSYBEE::EGOLF | John C. Egolf LKG2-2/T02 x226-7874 | Fri Jul 06 1990 01:04 | 19 |
| Come on Kandha,... jumping the conclusions a little!!??!!
You're starting a rumor here that isn't necessarilly true!
Look at your error message. It says you don't have the MCC$TDF
logical not defined. What does that have to do with VT1000 or
DECmcc V1.1? This message indicates that you haven't set the
time offset. Do the following:
$ DEFINE/SYSTEM MCC$TDF "-4:00"
from a priv account. I guarentee this will get you further
along. Now, you have an obligation to get back to us with the
results of your VT1000 testing, ok?
Check your MCC documentation of the MCC$TDF and if you can't
find any reference to it, submit a QAR on the documentation.
JCE
|
| 168.2 | mcc$tdf | GOSTE::CALLANDER | | Sun Jul 08 1990 19:50 | 3 |
| You should find what you need on MCC$TDF in the installation guide.
This logical is set-up as part of the installation procedures.
|
| 168.3 | MCC$TDF has been set up..but still.... | FELICE::SYSTEM | | Mon Jul 09 1990 12:16 | 16 |
| John,
Following is the same error message that was generated after
setting the logical MCC$TDF to "-4:00".
"X Toolkit Error: Can't Open display" did appear before setting the
MCC$TDF logical and was missed in my original note. I could not
capture that line into an output file while issuing the following
command before invoking MCCIMPM. So I had to type that line on my own.
ASSIGN OUTPUTFILE_NAME SYS$OUTPUT
%MCC-E-REVECTCONFLICT, Revectoring conflict
-SYSTEM-F-DEBUG, command interpreter debugger signal at PC=001059A7, PSL=03C00000
X Toolkit Error: Can't Open display
%DWT-F-DWTABORT, xtoolkit fatal error
%DWT-E-DWTABORT, xtoolkit fatal error
|
| 168.4 | try setting display | TOOK::HAO | | Mon Jul 09 1990 15:49 | 9 |
| This looks like your display isn't set correctly. For example, if
you did a Sethost from your workstation to another node in order to
run the Iconic Map, you need to set the display to your workstation
in order to run.
The command is: set display/node=<yournode>/perm/create
Christine
|
| 168.5 | is the problem MCC, or is it figuring out how to run a DECwindows application on a VT100? | TOOK::DITMARS | Pete | Mon Jul 09 1990 17:57 | 24 |
| Can you get any DECwindows application to run on your VT1000?
I have yet to see anyone successfully invoke a native DECwindows application
on a VT1000. I'm not saying it can't be done, it's just no one that I know
knows how to do it yet.
Christine's suggestion in 168.3 is a good one... except that I have no idea how
to specify the /NODE= argument. What's your VT1000's node name?
According to the VT1000 documentation (and this is coming to me seond-hand,
as I've never seen the documentation myself) in order to run a native DECwindows
application on a VT1000 you need a special driver loaded on the system that
the client (application) is going to run on prior to starting DECnet on that
system, and you need a special logical defined to get that special driver
loaded.
So try running a very simple and stable DECwindows application on your VT1000,
such as DECW$CLOCK. If you can get that, and every other native DECwindows
application to run on your VT1000, but MCC still doesn't run, then we need to
do some digging.
regards,
Pete
|
| 168.6 | VT1000 hints | TOOK::MCPHERSON | I'm an ADULT now. | Mon Jul 09 1990 19:16 | 40 |
| Here's a lot of data:
Assuming you're using a VT1000 that's using LAT to speak to the DECwindows
application, the node name for the VT1000 will be LAT_08002Bnnnnnn, which is
simply the ethernet address of the VT10000 with the characters "LAT_" prepended
to it.
You'll have to do the following command
$ SET DISPLAY/CREATE/NODE=LAT_08002Bnnnnnn/TRANSPORT=LAT
at the $ prompt before running any DECwindows application you want displayed to
your VT1000.
You will also have to make sure that your VT1000
1) has enough memory to keep from croaking on you (They *really* suck w/only 1
MB memory; they'll crash every time.)
2) has the correct grou p codes enabled for the DECwindows clients with which
you wish to communicate.
3) has the proper "session security" enabled in the pull-down menu in the
VT1000 session manager
Additionally, the VMS hosts running the application must have the logical
DECW$INSTALL_XTERMINAL defined as "TRUE" in the system startup procedures
somewhere before DECwindows gets started. This will allow the system to use
LAT as a transport for DECwindows and some other stuff.
If you're running LAT-Master on the DECwindows client instead of plain ol' LAT
as supplied w/VMS you'll also need to install a SEPARATE piece of code that I
forget the name of (look in the VT1000 notes file) I think it's XTERMINAL or
something like that.
That should keep you busy for a while. Hope you don't have to waste as much
time getting your VT1000 to work as I did! ;^) I'm waiting for the new,
improved firmware for these guys, hoping that that will improve some of the
performance....these things really bark (my own un-professional opinion).
/doug
|