billdeg
Technician
I will have to come back to this tomorrow. Program is not bombing, but nothing printed screen. Need sleep.
Hope you had a good sleep...
So, I have read the thread and the MAINDEC diagnostic listing and have a few observations:
1) How do you know that the diagnostic software that you have is the same as that described in the listing? Can you post a copy of the diagnostic tape you are using please and I will compare it to the listing.
2) Within the software there seems to be some disagreement as to the state of switch 7. It describes it as both an inhibit and an enable switch. One must be right and the other not.
3) Looking at the code there appears to be three (3) entry points into the diagnostic - 200( 8 ), 204( 8 ) and 210( 8 ). Starting the program at 204( 8 ) instead of 200( 8 ) should prompt you for the memory limits and ask you for "LOW LIMIT?" and "HIGH LIMIT?". The important thing is 'does it ask you for anything at all'? If not, either your console is not working - or the diagnostic software you have doesn't match the documentation (in which case we will get nowhere).
4) The listing implies that it detects if a terminal is present by looking at address 177564 and seeing if it times out or not. If it doesn't timeout - then the software should print "OPT.CP=nnnn" at the start stating what options it has found. I guess it has never done this?
ok.EXAMINE memory location 764( 8 ) which should hold the OPT.CP flags to see what it thinks it is running with. Again, this memory location will only be valid for the same version of the diagnostics as the listing describes.
If you can post the diagnostic tape you are using, I think it should be relatively easy to see if it matches the listing. If not, we will have to look for a consistent diagnostic tape and documentation/listing.
Dave
Starting from here:
http://www.retrocmp.com/images/stories/joerg/pdp11_diagnostic_database////modules/CQKC.html
I took the image CQKCG1.BIC "Extracted from the XXDP+ RL02 disk image"
Could it be that I can't run this without a working disk drive first, chicken and egg problem?
Maybe I should be using the cqkce0_11-45.bin instead.
I checked points in the code with the papertape I switched to, appears to be a match.
sim> load cqkce0_11-45.bin
sim> ex -m 200-1000
200: MOV #5514,PC
204: MOV #5624,PC
210: MOV #5676,PC