[HECnet] native Dup sync line revisited --> preliminary tests reveals problems --> test setup?

[Johnny Billquist]

Certainly sounds like Paul was doing M+ to PyDECnet. Not sure what more 
combinations he might have been playing with.

   Johnny

On 2021-12-23 10:14, R. Voorhorst wrote:
> Hi Paul,
> 
> How was this tested: 11M+ to 11M+ or 11M+ to PyDecnet?
> 
> 
> Reindert
> 
> -----Original Message-----
> From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf
> Of Paul Koning
> Sent: Thursday, 23 December, 2021 02:36
> To: hecnet at update.uu.se
> Subject: Re: [HECnet] native Dup sync line revisited --> preliminary tests
> reveals problems
> 
> 
> 
>> On Dec 13, 2021, at 9:15 AM, Paul Koning <paulkoning at comcast.net> wrote:
>>
>> ...
>> So if the plain sync device emulation were to do the above, that would
> give us an emulation that interoperates with the DMC emulation if the
> software controlling the device is running DDCMP.
> 
> More on this...
> 
> I built an M+ system with DUP lines, and unlike what was reported in this
> thread, I did NOT see problems talking to other things (like PyDECnet or DMC
> emulation) that expect plain data without frame length fields.  I don't see
> frame lengths in the trace.
> 
> I don't understand this because the code is clearly there in the emulator,
> so apparently it's not being hit.  Not by DECnet/RSX anyway.  More to be
> studied.
> 
> 	paul
> 

-- 
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