From: jayjwa@atr2.ath.cx.invalid

Arne Vajhøj  writes:

>> I doubt VAXELN will run MACRO-11 or that it will run on a PDP-11.
This is what the ICP claims to support:

Do you want to build an ICP for an rtVAX 1000 or MicroVAX I, II, 3200,
3300, 3400, 35NN, 36NN, 3800, 3900, 4000 [NO] ? yes
Do you want to build an ICP for MicroVAX 3100 Model 30,40,80 [NO] ?
Do you want to build an ICP for MicroVAX 2000, MicroVAX 3100 [NO] ?
Do you want to build an ICP for KAV30 [NO] ?
Do you want to build an ICP for 6000-2NN, 6000-3NN [NO] ?
Do you want to build an ICP for 6000-4NN [NO] ?
Do you want to build an ICP for 6000-5NN [NO] ?
Do you want to build an ICP for 6000-6NN [NO] ?
Do you want to build an ICP for 9000 [NO] ?
Do you want to build an ICP for VAXstation II/GPX, VAXstation 3200 [NO] ?
Do you want to build an ICP for VAXstation II [NO] ?
Do you want to build an ICP for GPX VAXstation 2000, VAXstation 3100 [NO] ?
Do you want to build an ICP for monochrome VAXstation 2000, VAXstation 3100
[NO] ?
Do you want to build an ICP for SPX VAXstation 3100 [NO] ?
Do you want to build an ICP for VAXstation 4000 Model 60,VLC [NO] ?

> My understanding about VAXELN (based on what I have been told - no
> personal experience) is that you link the OS into the application
> and deploy the application (with embedded OS) directly on
> the VAX.
It's an SDK but no one calls it that. It would be much easier to
understand if they did. One creates an application in C or Pascal. Then
you compile/link it with ELN libraries. Maybe it supports other
languages but the docs mention C and Pascal.

$ cc program.c + ELN$:VAXELNC/LIB
$ link program.obj + ELN$:RTLSHARE/LIB + RTL/LIB
Then a .SYS gets create with ebuild.
$ ebuild program

This .SYS is then downline loaded on a supported system from the VMS
node ELN is on.

$ copy SAMPLE.SYS SYS$COMMON:[MOM$SYSTEM]
$ dir SYS$COMMON:[MOM$SYSTEM]

Directory SYS$COMMON:[MOM$SYSTEM]

READ_ADDR.SYS;10    SAMPLE.SYS;5

Total of 2 files.

Set the node to load this file on the target. SIMH has an rtvax1000 that
will work. Note that it is diskless and boots off the network.

$ ncp set node 1.16 load file SAMPLE.SYS

$ ncp show node 1.16 char
Node Volatile Characteristics as of 18-DEC-2023 20:35:21
Remote node =   1.16
Service circuit          = QNA-0
Hardware address         = AA-00-04-00-10-04
Load file                = SAMPLE.SYS

...
set xq mac=aa:00:04:00:10:04
set xq ena
att xq tap:tap6
boot cpu

rtVAX1000 (KA620) simulator V4.0-0 Current        git commit id: f4f30298
Logging to file "/opt/simulations/rtvax1000/install_rtvax1000.log"
./rtvax1000.ini-66> att xq tap:tap6
%SIM-INFO: Eth: opened OS device tap6
./rtvax1000.ini-70> boot cpu
%SIM-INFO: Loading boot code from internal ka620.bin

KA620-A.V1.1

Performing normal system tests.

  5..4..3..

Tests completed.


>>> boot xqa0

  2..1..0..



%VAXELN system initializing

       VAXELN V4.6  QBUS


Hello!

From the host side (one year is wrong for some reason):

$
%%%%%%%%%%%  OPCOM  18-DEC-2023 20:35:32.35  %%%%%%%%%%%
Message from user DECNET on KUSHAL
DECnet event 0.3, automatic line service
From node 1.12 (KUSHAL),  1-JAN-2041 00:00:00.00
Circuit QNA-0, Load, Requested, Node = 1.16, File = SAMPLE.SYS
Operating system, Ethernet address = AA-00-04-00-10-04

$
%%%%%%%%%%%  OPCOM  18-DEC-2023 20:35:37.33  %%%%%%%%%%%
Message from user DECNET on KUSHAL
DECnet event 0.3, automatic line service
From node 1.12 (KUSHAL),  1-JAN-2041 00:00:00.00
Circuit QNA-0, Load, Successful, Node = 1.16, File = SAMPLE.SYS
Operating system, Ethernet address = AA-00-04-00-10-04

--
PGP Key ID: 781C A3E2 C6ED 70A6 B356  7AF5 B510 542E D460 5CAE
       "The Internet should always be the Wild West!"

--- SoupGate-Win32 v1.05
 * Origin: you cannot sedate... all the things you hate (1:229/2)