Sadly, noone seems to be interested in setting up Multinet link. Apart
from the one to LEGATO, not a single one have been set up from MIM so
far. I was hoping for at least SG1 as well.
Meanwhile I've added TCP tunneling in RSX as well, which now works.
I have a question on how Multinet on VMS works, though. When you have
passive TCP connections, are they all sharing the same port number, or
do you configure each with a different number? Right now I did it with
separate port numbers under TCP for each connection, but for incoming
connections, I could change the code to use a common port number.
Any opinions from anyone?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Ok. I now have my Multinet circuits set up on MIM. Only UDP at the
moment, but who would like to peer with me, and reduce the size of the
bridge?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Well, about a month since my last announcement, and some improvements
have been done, so I figured I should do another one.
I've cut a new release of TCP/IP for RSX, and I encourage everyone to
update to this latest release.
A short list of changes since my last release:
TCP:
. Added functionality for future DECnet tunnels.
UDP:
. Bugfix in write. The second word of the IOSB was always zero, but
should be the number of bytes written. Fixed now.
. Added functionality for DECnet tunnels.
. Improved user AST generation to use less resources.
FTP/FTPD:
. Bugfix in RSX transfer mode, which could become corrupted under some
circumstances.
. Added some more error checking and messages.
TELNET:
. Changed code so that it can properly managed the number of devices to
create. Now controlled by a logical name.
DECnet over IP:
. This is the big change that comes with this release. It is now
possible to have DECnet over IP, in a Multinet-compatible
implementation. Right now, this only works over UDP, but TCP will come
later. There are still probably a couple of rough corners to improve,
but this should be possible to use by anyone, and I have written
documentation for this. I'm very interested to hear someone else try to
install and use it, to find any issues with the installation.
If someone wants to use this, I'm happy to act as a peer for them. Just
let me know.
As usual, the distribution is available from:
ftp://mim.update.uu.se/bqtcp.dsk
ftp://mim.update.uu.se/bqtcp.tap
ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk
The documentation is also available through ftp on Mim, or also at
http://mim.update.uu.se/tcpipdoc
Note! I've realized that BQTCP/IP do not work right if you have a
PDP-11/74 with multiple processors online. I'll fix that at some point,
as it's probably just a case of affinity not being set on devices, nor
relevant processes. This might only be a problem with telnet in fact. I
know for sure that the IP and TCP drivers works ok in multiprocessor
systems.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Just FYI. It is slightly interesting and informing:
15-JAN-16 03:44:30 Node: MIM (1.13) "RSX system at Update, Sweden"
RSX-11M-Plus, Area Routing Node, DECnet V4.6
Area Circuit Hop/Cst Next Node Area Circuit Hop/Cst Next Node
2 IP-0-0 1/1 LEGATO( 2.1)
3 IP-0-0 2/3 LEGATO( 2.1)
7 UNA-0 2/7 SG1 (19.41)
8 UNA-0 1/3 GORVAX( 8.400)
12 UNA-0 2/13 ( 1.1023)
14 UNA-0 1/3 SKHNGW(14.4)
18 IP-0-0 2/3 LEGATO( 2.1)
19 UNA-0 1/3 SG1 (19.41)
22 UNA-0 2/23 HUB (42.1022)
23 UNA-0 2/13 ( 1.1023)
33 IP-0-0 2/3 LEGATO( 2.1)
39 IP-0-0 2/3 LEGATO( 2.1)
42 UNA-0 1/3 HUB (42.1022)
44 UNA-0 1/3 A44RTR(44.1023)
59 IP-0-0 2/3 LEGATO( 2.1)
61 UNA-0 2/23 HUB (42.1022)
62 UNA-0 1/3 CTAKAH(62.637)
- Total areas: 17-
Notice the number of areas that MIM now decided should go over IP-0-0,
which is the link to LEGATO. Since I set the cost for that link to 1,
while ethernet is at 3, it is rather favored. Not sure it really makes
sense to route packets to area 59 that way, since going over ethernet, I
would have a direct ptp to area 59 through a Cisco router sitting right
next to MIM, but that then becomes a question of what the cost of the
link between 1.1023 and area 59 is set to.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
I'm looking for data sheet, shematics, SW, etc for MicroNova and the
Mn601 and MN602 chip.
Also looking for register programming of Fairchild F9443, F9444, F9446, F9447
F9448 and F9449.
-P
I would like to test my multnet link against some VMS machine. Anyone
around that could enable UDP multinet to me?
(I tried Paul's python implementation, but I have some issues with it,
so I'd like to test against something else.)
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Is anyone running Phase-V of DECnet? I am looking to convert SGC:: to run it. I will definitely need help. I am way out of practice!!!
-Steve
Sent from my iPhone
I have a small request:
On nodes that run Multinet tunnels AND talks to Johnnys bridge with a
ethernet interface put the cost of 5 on the Multinet link and cost
20 on their Ethernet facing the bridge?
What hopfullt hapens is that traffic becomes symetric inside each domain..
-P
Hey folks. All traffic on all of my DECnet tunnels seems to have
dropped dead around 3PM yesterday. I've been dicking around with my
router's configuration all week, but in an unrelated area (IP NAT
configuration) so I'm pretty sure I didn't break it. Any thoughts as to
what might be going on?
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Hey Johnny, have you thought about adding lpr/lpd support to your IP
stack? In particular I'd love to have the ability to print from an RSX
system to a networked printer.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
I know this seems a bit...odd but uh...does anyone know if dynamips +
dynagen will build and run on mips?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Well, about two months since my last announcement, and some improvements
have been done, so I figured I should do another one.
I've cut a new release of TCP/IP for RSX, and I encourage everyone to
update to this latest release.
A short list of changes since my last release:
TCP:
. Performance improvements. TCP timers have been redesigned for better
performance. This gave FTP a performance increase of about 15$.
. TCP negative ACK detection has been improved.
, TCP receive packet handling have been redesigned for better
performance, and better code structure.
. Added guards against data received after FIN.
. Bugfix in SPOOF hostname printouts when filter was cleared.
. Bugfix in tcp timers that could cause a close to take a very
long time to clean up.
FTP:
. Bugfix in user verification code which could cause program
to crash. This affected ftpd.
. Changed ftp and ftpd to create files without max record length when
dealing with binary files.
TELNET:
. Added exit handler to telnetd, so that telnetd cannot be aborted
while active sessions exist.
HTTPD:
. Improved webserver handling of binary files.
As usual, the distribution is available from:
ftp://mim.update.uu.se/bqtcp.dsk
ftp://mim.update.uu.se/bqtcp.tap
ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk
The documentation is also available through ftp on Mim, or also at
http://mim.update.uu.se/tcpipdoc
Note! I've realized that BQTCP/IP do not work right if you have a
PDP-11/74 with multiple processors online. I'll fix that at some point,
as it's probably just a case of affinity not being set on devices, nor
relevant processes. This might only be a problem with telnet in fact. I
know for sure that the IP and TCP drivers works ok in multiprocessor
systems.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Guys,
I've got an Integrity (rx2660) box but the install ISO file I have seems to be corrupt - does anyone happen to have a working ISO I could build the box from (I have the hobbyist licenses)?
Sampsa
I think this topic was up once before, but I can't find it right now, so
I figured I'd ask.
Do anyone have some idea/documentation on how the Multinet capsulates
DECnet traffic over IP. I seem to remember it pretended it was like
ethernet, but I'd like to have all the details.
The reason is that since my TCP/IP for RSX is now at a stage where the
basic functionality is pretty stable and good, I might try something
new. Implementing a line that uses IP for transport would be useful, and
it would also be useful if it was compatible with the Multinet
implementation. I wouldn't mind also doing something compatible with
Cisco. Anyone have the details of that one?
I could also do a very RSX specific implementation, but that would be
less useful, I think.
Anyone else feel like hacking on TCP/IP on PDP-11s? I have lots of
things that could be nice to have under RSX... ;-)
Johnny
Here's the previous message.
paul
> Begin forwarded message:
>
> From: Paul Koning <paul_koning at dell.com>
> Subject: Multinet over TCP -- protocol and observations
> Date: May 30, 2014 at 1:55:37 PM EDT
> To: "<hecnet at Update.UU.SE>" <hecnet at Update.UU.SE>
>
> With help from Bob Armstrong and Peter Lothberg, I have a reverse engineered Python implementation of the Multinet tunnel over TCP working now.
>
> Peter forwarded an old HECnet message that roughly describes the protocol, but some details were missing and some were not quite accurate. For the benefit of anyone else who wants to implement this, here is the protocol description plus some implementation notes.
>
> paul
>
> ?????????????
>
> Multinet protocol for DECnet
>
> A Multinet tunnel runs the Point to Point mode of the DECnet protocol. Traffic may be carried over a TCP connection, or over UDP packets. The operation is nearly the same for both.
>
> In TCP mode, one end is designated the connecting end and the other the listening end. In UDP mode, operation is symmetric since there are no connections. In either case, the port number may be configured; the default is 700.
>
> Multinet puts a 4 byte header on each DECnet packet. For TCP, the first two bytes are the DECnet packet length, little endian. The TCP data stream consists of these packets with headers.
>
> For UDP, the first two byte are a sequence number, little endian. The next two bytes appear to be unused and were observed to contain zero. Each DECnet packet, with its header, is sent as a separate UDP packet. Some Multinet implementations can be configured to check the sequence number in UDP mode; it is not clear how this works (in particular, how it is initialized). Linux does not, and things seem to work fine without this extra check.
>
> Multinet tunneling does not obey many of the requirements that the DECnet Routing architecture imposes on point to point datalinks. The most obvious issue is that routing layer point to point init messages (control packet, type code 0) may appear unexpectedly. This happens even in TCP mode where it might be expected that the TCP connection would be closed and re-established before the init message.
>
> A conforming DECnet implementation reacts to such an unexpected init message by restarting the circuit, sending an init message, and expecting one in return. Multinet does not expect this, and if the peer operates according to the standard, initialization may require many cycles before it finally succeeds. As a workaround, the response to an unexpected init should be to set the routing initialization sublayer state machine to the DS state (without restarting the TCP connection, if any), and processing the unexpected init message as if it had been received in that state.
>
> In testing with a DECnet/VMS system, it was observed to send an Init message requesting verification even though verification was not called for in the circuit parameters. It may be that this was due to the routing architecture requirement to use verification in areas other than area 1. A null verification message (empty FCNVAL field) was accepted by the VMS system in that test.
>
Just thought I'd try and pick the brains of the collective wisdom if
possible.
I had a networking performance issue with AlphaVM-Free (poor ping rates and
sluggish network performance) that has kindly been solved by Artem in the
latest release and therefore my attention turns to the issue with a VAX
satellite node network booting off the AlphaVM-Free instances (which I can
no longer attribute to the same performance issue).
Back in the 'real world' the boxes that supported this configuration were
an AlphaServer 1000/A and a VAXstation 4000/60. In the emulated world they
are now an AlphaVM-Free instance and a SIMH instance, both running on an HP
DL380 Gen 5 with 6 x GB network adapters. Each of the emulated instances is
mapped to a different physical network card.
When I attempt to boot the emulated VAX from its' network adapter I get the
following console messages. Boot appears to proceed but it is glacial. In
the past I've given up long before ever receiving a login prompt on the VAX
instance.
Does anyone have experience with this kind of issue? It doesn't look like
the emulated Alpha network adapter on the AlphaVM instance thinks that it
is experiencing errors based on the output below.
Thanks, Mark.
%<------------------------- VAX console log
Connected to the MicroVAX 3900 simulator CON-TEL device
KA655X-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot
(BOOT/R5:0 XQA0
2..
-XQA0
1..0..
%VAXcluster, system loaded from node SLAVE (AA-00-04-00-F9-10)
%VAXcluster, no connection to disk server
%VAXcluster, no connection to disk server
%VAXcluster, no connection to disk server
%VAXcluster, no connection to disk server
%VAXcluster, no connection to disk server
%VAXcluster, no connection to disk server
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
%SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id
= 0
%VAXcluster, no connection to disk server
%VAXcluster, no connection to disk server SLAVE
%VAXcluster, attempting to reconnect to a disk server
%VAXcluster, no connection to disk server
%VAXcluster, attempting to reconnect to a disk server
%VAXcluster, connected to disk server SLAVE
%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
%<------------------------- Alpha console log
%%%%%%%%%%% OPCOM 11-DEC-2015 17:45:34.47 %%%%%%%%%%%
Message from user DECNET on SLAVE
DECnet event 0.3, automatic line service
>From node 4.249 (SLAVE), 11-DEC-2015 17:45:34.47
Circuit EWA-0, Load, Requested, Node = 4.259 (ALEPH)
File = ALEPHSYSTEM$:[SYS0.], Operating system, Ethernet address =
08-00-2B-2C-20
-6E
%%%%%%%%%%% OPCOM 11-DEC-2015 17:46:01.70 %%%%%%%%%%%
Message from user DECNET on SLAVE
DECnet event 0.3, automatic line service
>From node 4.249 (SLAVE), 11-DEC-2015 17:46:01.70
Circuit EWA-0, Load, Successful, Node = 4.259 (ALEPH)
File = ALEPHSYSTEM$:[SYS0.], Operating system, Ethernet address =
08-00-2B-2C-20
-6E
Username:
%PEA0, Port has Closed Virtual Circuit - REMOTE NODE ALEPH
Username:
%PEA0, Port has Closed Virtual Circuit - REMOTE NODE ALEPH
Username:
%PEA0, Port has Closed Virtual Circuit - REMOTE NODE ALEPH
Username: system
Password:
01010011 01001100 01000001 01010110 01000101
+-+-+-+-+-+
|S|L|A|V|E|
+-+-+-+-+-+
Welcome to SLAVE running OpenVMS AXP 8.3
SLAVE is a member of the HALO Cluster
Strictly non-commercial use only
Documentation is available at http://hpm.hecnet.eu/wiki/
Last interactive login on Friday, 11-DEC-2015 17:38:17.57
Last non-interactive login on Friday, 11-DEC-2015 17:44:08.37
SLAVE$$ show device pea0:/full
Device PEA0:, device type NI_SCA, is online, shareable, error logging is
enabled.
Error count 576 Operations completed
0
Owner process "" Owner UIC
[SYSTEM]
Owner process ID 00000000 Dev Prot
S:RWPL,O:RWPL,G,W
Reference count 0 Default buffer size
0
Current preferred CPU Id 0 Fastpath
1
SLAVE$$ mcr ncp show known lines count
Known Line Counters as of 11-DEC-2015 17:51:28
Line = EWA-0
654 Seconds since last zeroed
6522 Data blocks received
2589 Multicast blocks received
0 Receive failure
655620 Bytes received
372627 Multicast bytes received
0 Data overrun
3341 Data blocks sent
335 Multicast blocks sent
0 Blocks sent, multiple collisions
0 Blocks sent, single collision
0 Blocks sent, initially deferred
1529780 Bytes sent
42723 Multicast bytes sent
0 Send failure
0 Collision detect check failure
0 Unrecognized frame destination
0 System buffer unavailable
5 User buffer unavailable
SLAVE$$
You don't mention the host OS??
On Dec 11, 2015 10:04 AM, Mark Wickens <mark at wickensonline.co.uk> wrote:
Just thought I'd try and pick the brains of the collective wisdom if possible.
I had a networking performance issue with AlphaVM-Free (poor ping rates and sluggish network performance) that has kindly been solved by Artem in the latest release and therefore my attention turns to the issue with a VAX satellite node network booting off the AlphaVM-Free instances (which I can no longer attribute to the same performance issue).
Back in the 'real world' the boxes that supported this configuration were an AlphaServer 1000/A and a VAXstation 4000/60. In the emulated world they are now an AlphaVM-Free instance and a SIMH instance, both running on an HP DL380 Gen 5 with 6 x GB network adapters. Each of the emulated instances is mapped to a different physical network card.
When I attempt to boot the emulated VAX from its' network adapter I get the following console messages. Boot appears to proceed but it is glacial. In the past I've given up long before ever receiving a login prompt on the VAX instance.
Does anyone have experience with this kind of issue? It doesn't look like the emulated Alpha network adapter on the AlphaVM instance thinks that it is experiencing errors based on the output below.
Thanks, Mark.
%<------------------------- VAX console log
Connected to the MicroVAX 3900 simulator CON-TEL device
KA655X-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot
(BOOT/R5:0 XQA0
2..
-XQA0
1..0..
%VAXcluster, system loaded from node SLAVE (AA-00-04-00-F9-10)
%VAXcluster, no connection to disk server
%VAXcluster, no connection to disk server
%VAXcluster, no connection to disk server
%VAXcluster, no connection to disk server
%VAXcluster, no connection to disk server
%VAXcluster, no connection to disk server
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
%SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0
%VAXcluster, no connection to disk server
%VAXcluster, no connection to disk server SLAVE
%VAXcluster, attempting to reconnect to a disk server
%VAXcluster, no connection to disk server
%VAXcluster, attempting to reconnect to a disk server
%VAXcluster, connected to disk server SLAVE
%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
%<------------------------- Alpha console log
%%%%%%%%%%% OPCOM 11-DEC-2015 17:45:34.47 %%%%%%%%%%%
Message from user DECNET on SLAVE
DECnet event 0.3, automatic line service
>From node 4.249 (SLAVE), 11-DEC-2015 17:45:34.47
Circuit EWA-0, Load, Requested, Node = 4.259 (ALEPH)
File = ALEPHSYSTEM$:[SYS0.], Operating system, Ethernet address = 08-00-2B-2C-20
-6E
%%%%%%%%%%% OPCOM 11-DEC-2015 17:46:01.70 %%%%%%%%%%%
Message from user DECNET on SLAVE
DECnet event 0.3, automatic line service
>From node 4.249 (SLAVE), 11-DEC-2015 17:46:01.70
Circuit EWA-0, Load, Successful, Node = 4.259 (ALEPH)
File = ALEPHSYSTEM$:[SYS0.], Operating system, Ethernet address = 08-00-2B-2C-20
-6E
Username:
%PEA0, Port has Closed Virtual Circuit - REMOTE NODE ALEPH
Username:
%PEA0, Port has Closed Virtual Circuit - REMOTE NODE ALEPH
Username:
%PEA0, Port has Closed Virtual Circuit - REMOTE NODE ALEPH
Username: system
Password:
01010011 01001100 01000001 01010110 01000101
+-+-+-+-+-+
|S|L|A|V|E|
+-+-+-+-+-+
Welcome to SLAVE running OpenVMS AXP 8.3
SLAVE is a member of the HALO Cluster
Strictly non-commercial use only
Documentation is available at http://hpm.hecnet.eu/wiki/
Last interactive login on Friday, 11-DEC-2015 17:38:17.57
Last non-interactive login on Friday, 11-DEC-2015 17:44:08.37
SLAVE$$ show device pea0:/full
Device PEA0:, device type NI_SCA, is online, shareable, error logging is
enabled.
Error count 576 Operations completed 0
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G,W
Reference count 0 Default buffer size 0
Current preferred CPU Id 0 Fastpath 1
SLAVE$$ mcr ncp show known lines count
Known Line Counters as of 11-DEC-2015 17:51:28
Line = EWA-0
654 Seconds since last zeroed
6522 Data blocks received
2589 Multicast blocks received
0 Receive failure
655620 Bytes received
372627 Multicast bytes received
0 Data overrun
3341 Data blocks sent
335 Multicast blocks sent
0 Blocks sent, multiple collisions
0 Blocks sent, single collision
0 Blocks sent, initially deferred
1529780 Bytes sent
42723 Multicast bytes sent
0 Send failure
0 Collision detect check failure
0 Unrecognized frame destination
0 System buffer unavailable
5 User buffer unavailable
SLAVE$$
Michael Holmes <mholmes10 at hotmail.com> writes:
>Gurus,
>
>
>I'm looking for your advice.
>
>
>My DEC 3000 gave me a POST NVR error and after trying all the steps to fix =
>it (reseating boards, memory, etc...) it looks like the RTC (DALLAS DS12871=
>A) has died.
>
>
>Searching on line I found some places marketing a replacement for DS1287 fo=
>r old PC's but not sure if any would work for DEC given it had an A at the =
>end in the model number (different pins etc...)
>
>
>Given that this sounds like a common problem on early VAXen, I was wonderin=
>g if of you have some recommendations on a good source to purchase a replac=
>ement RTC that will work with DEC equipment.
>
>
>Thanks much!
You can replace it with the newer DS12887 available from various electronics
parts resellers. Several listed below:
http://www.mouser.com/ProductDetail/Maxim-Integrated/DS12887A+/?qs=0Y9aZN%2…http://www.digikey.com/product-detail/en/DS12887A%2B/DS12887A%2B-ND/956873http://store.batteryspecialists.com/ds12887a.htmlhttp://www.interstatebatteries.com/1/1/5018-ds12887a-lit2695.html
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
Gurus,
I'm looking for your advice.
My DEC 3000 gave me a POST NVR error and after trying all the steps to fix it (reseating boards, memory, etc...) it looks like the RTC (DALLAS DS12871A) has died.
Searching on line I found some places marketing a replacement for DS1287 for old PC's but not sure if any would work for DEC given it had an A at the end in the model number (different pins etc...)
Given that this sounds like a common problem on early VAXen, I was wondering if of you have some recommendations on a good source to purchase a replacement RTC that will work with DEC equipment.
Thanks much!
Mike
. one more time. This time should be the last time, I hope.
108.65.195.50
As always, decnet.jfcl.com points to the correct address, so if your end is
using that you just need to restart the link.
Bob
Indeed. I haven't been up to that much just lately, been doing other stuff.
But I keep coming back to my failed H7864 PSU (from an rtVAX 1000), trying
to find the fault. Right now I have a little DEC Venturis PC onto which I am
just installing Windows NT 3.1 as I type. It isn't VAX or any kind of PDP,
but it is still a DEC machine!
Regards
Rob
> -----Original Message-----
> From: DECtec [mailto:dectec-bounces at dectec.info] On Behalf Of Mark
> Wickens
> Sent: 14 November 2015 18:14
> To: DEC discussion list.; hecnet at Update.UU.SE
> Subject: [DECtec] It's oh so quiet...
>
> It's very quiet - anyone up to anything interesting (on or off topic)?
>
> I'm starting to ramp up for Retrochallenge January 2015.
>
> I've bought an ESP8266 NodeMCU wifi board with a view to hooking up a
Tandy
> Model 102 to the internet. It's effectively a serial->tcp/ip converter.
Very cool
> and 10 quid delivered off eBay.
>
> I also created a character map for the Tandy 100/102/200 with a view to
using
> it to convert Tandy-format files to Unicode, so I can write my
Retrochallenge
> blog using the Tandy 200.
>
> http://wickensonline.co.uk/static/files/tandy/Tandy%20Model%20T%20Code%2
> 0to%20Unicode%20Generated%20V1.8.html
>
> Mark.
>
> --
>
> DECtec mailing list
> http://dectec.info
>
> To unsubscribe from this list see page at:
> http://dectec.info/mailman/listinfo/dectec_dectec.info