The async DDCMP driver is a whole new driver, and it depends on the terminal driver structure that exists in the later versions of RSTS. I don't remember when that was put in place, but I'm pretty sure it wasn't there in V8.0. I did the original work for RSTS V9.6, but that was just a private prototype. paul -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark Abene Sent: Thursday, August 20, 2009 6:05 PM To: hecnet at Update.UU.SE Subject: Re: [HECnet] Who's emulating? Unfortunately, given my preference to using RSTS/E v8, I must use DECnet/E v2.0. Those DECnet drivers only support a DMC or DMR device (seen as "XM" in RSTS), or a DMP or DMV device (seen as "XD" in RSTS). Based on what you're saying, the patch would not solve this problem? Paul Koning wrote: Excerpt of message (sent 20 August 2009) by Mark Abene: Serious? Are you actually emulating a DMC11? I'm intrigued... Yes. Or rather, the terminal driver contains an implementation of the DDCMP protocol. So it can talk to async DDCMP devices -- just as RSX did for years. Until V10, DECnet/E only did DMC/DMR type DDCMP devices. On a Pro, which has a USART (not UART) console port, it even speaks sync DDCMP if you want so it can talk to a DMC or DMR (and that works, I tested it). On other PDP-11s it will use any of the async lines and speak async DDCMP. paul