[Simh] PIP10

[Timothe Litt]

The logic doesn't seem to be in PIP10; PIP10 uses the DCB devtype field 
to decide if it has a DECtape, and if so, which controller.

See 
ftp://sunsite.unc.edu/pub/academic/computer-science/history/pdp-8/os8/os8.v3d/sources/system/dectapes/dectape7/pip10.pa 
for PIP10, and table 33 
inhttp://www.grc.com/pdp-8/docs/OS8_System_Reference_Manual.pdf 
<http://www.grc.com/pdp-8/docs/OS8_System_Reference_Manual.pdf>for the 
DCB breakdown.  I'm not an OS8 expert, but I think the DCB is setup by 
CONFIG.

Relevant snippets:

DCB=7760 /DEVICE CONTROL BLOCK (FIELD 1)

DVTYPE, 0 /DEVICE TYPE HOLDER

JMS GTDVTP /COMPARE DCB ENTRY WITH TC08 OR TD8E
SZA CLA
JMP CDIN3 /NOT DECTAPE

GTDVTP, 0
TAD (DCB-1
DCA TEMP1
CDF 10
TAD I TEMP1 /GET DCB ENTRY
CDF
DCA DVTYPE
TAD DVTYPE
AND (770
TAD (-210
SZA
TAD (30
JMP I GTDVTP



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
> Simh at trailing-edge.com
> http://mailman.trailing-edge.com/mailman/listinfo/simh

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20130320/6f0e8951/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5159 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20130320/6f0e8951/attachment-0002.bin>