On Sunday, January 3, 2016 at 2:17 PM, Paul Koning wrote: > > On Jan 3, 2016, at 1:46 PM, Christian Gauger-Cosgrove > <[email protected]> wrote: > > > > Well, I was attempting it with RSTS/E since the "XM0: is missing > > ECO's, but will still function." error implies that the DMC11 device > > would still function. I turned on debug for the DMC device using "SET > > DMC DEBUG" and nothing seems to be getting printed even though the > DMC > > device is being "used" by RSTS/E. > > You need to specify a debug output file, for example "set debug stdout". > > With that, I see the following: > > DBG(4762921805)> DMC REG: dmc_rd(DMC0), addr=0x003fe038, SEL0, > data=0x8000 [...] > > > Event type 4.11, Circuit initialization failure - circuit fault > Occurred 20-Dec-28 17:13:27.0 on node 1.43 (SIMH43) > Circuit DMC-1 > Reason = Circuit synchronization lost > Adjacent node address = 0 > > > > Event type 4.11, Circuit initialization failure - circuit fault > Occurred 20-Dec-28 17:13:27.0 on node 1.43 (SIMH43) > Circuit DMC-0 > Reason = Circuit synchronization lost > Adjacent node address = 0 > > DBG(5118754449)> DMC TRACE: dmc_poll_svc() > > > > That is with two DMCs pointing at each other: > > sim> show dmc > DMC lines=2, connectpoll=2, address=17760070-17760107* > vector=300*, 2 units > DMC0 attached to 10143, peer=127.0.0.1:11043, speed=0 (unrestricted) > MicroDiag=enabled, type=DMC > DMC1 attached to 11043, peer=127.0.0.1:10143, speed=0 (unrestricted) > MicroDiag=enabled, type=DMC
This configuration is very odd. You've got DMC0 connecting to itself AND you've got DMC1 also connecting to itself using the exact same ports as DMC0. I wouldn't expect this to ever work... - Mark _______________________________________________ Simh mailing list [email protected] http://mailman.trailing-edge.com/mailman/listinfo/simh
