Thanks, Tim. That means the OS/8 image Ian and I are using is configured
for a TD8E, so I'll debug that code path. It's more difficult, because
the DECtape emulator has to provide an accurate emulation of the mark
track, and I could easily have it wrong in 16b- or 18b- mode. (The TD8E
does run OS/8, so it's probably okay in 12b mode.)
/Bob
On 3/20/2013 8:03 PM, Timothe Litt wrote:
Meant to include the code that uses DVTYPE and actually picks the type
in my earlier note. Sorry.
If I had to make a random guess, look at the microprogrammed operate
codes, e.g SNA CLA; CLL CML RTR;
SETUNT, 0
STL
TAD (-7607
SZA /IF IT IS 7607,
TAD (7 /ITS UNIT 0
AND (7
CLL CML RTR
RTR
DCA UNIT10
TAD DVTYPE
AND (10
SNA CLA
JMP I SETUNT /TC08 - FINISHED
CLL
TAD UNIT10
AND (7000 /TD8E ENTRY POINTS ARE STRANGE -
TAD UNIT10 /MUST ROTATE UNIT NUMBER LEFT 1
SZL
TAD (1000
DCA UNIT10
JMS I (TDUSET /SET UP TD8E OPCODES
JMP I SETUNT
This communication may not represent my employer's views,
if any, on the matters discussed.
On 20-Mar-13 18:05, Bob Supnik wrote:
I tried running PIP10 from the image Ian was using.
If the simulator is configured for a TC08, it hangs. It is in a loop
doing IOT 773/JMP .-1, which is a TD8E IOT.
If the simulator is configured for a TD8E, it returns an error. I
tried DTA0:/Z and got OUTPUT FILE OPEN ERROR.
So the first issue is that PIP10's logic for telling which DECtape
controller is present uses some feature that the simulator is doing
incorrectly.
The second issue is what happens beyond that point.
/Bob
_______________________________________________
Simh mailing list
[email protected]
http://mailman.trailing-edge.com/mailman/listinfo/simh
_______________________________________________
Simh mailing list
[email protected]
http://mailman.trailing-edge.com/mailman/listinfo/simh
