-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parts wanted #4
Comments
|
DDT and DECtape. The Monitor (TOPS-10) was only used for staging. As per josinit.mac: "; INITIALIZATION DIALOG FOR JOSS STARTUP. ; THIS CODE MUST BE LOADED LAST, DIRECTLY The designers' guide mentions that the Monitor was stored on a separate DECtape but was only used as a way to develop the system. JOSS had its own DECtape. |
The official answer: 32K DECDMP with DDT. Stanford has a copy of the JOSS: Scheduling and Resource Allocation memo on their library's website. Appendix A contains the operating instructions. |
Good find, that's a very useful document. |
@larsbrinkhoff You're welcome. Although, I still have two more things to add now. There is a version of DECDMP on SAILDART but it looks like it was mangled to support the KL and I don't know if that will work. The other is DDT. Outside of ITS and TOPS-20, were there any other standalone versions of DDT? |
@rcornwell, do you have any old (close to PDP-6) versions of DDT and DECDMP? |
I have DDT for TSExec 1.9 and there is also DDT for 3.4, and 4.5. All of these will run on PDP6. I need a copy of DECDMP that has the directory block at block 1 instead of 110. I might find a copy in some of the Saildart tapes... I will keep you posted. |
I have macro V37 that I am working on converting back to source. |
JOSS: Console Service Routines says:
|
Correct. We likely have the Interpreter and arithmetic modules. If you look through the TOPS-10/20 CUSPs, they're similar to the coding style of the RAND monitor and refer to themselves as JOSS. In kmon.mac from @rcornwell's files for AID, there are a few very interesting lines of code: "SUXRET: DPB C,1(E)
... ";SIMULATION OF JOSS DISK ROUTINES DCONT: HRRZ B,ACTION ;GET REQUEST .... "ENTSW: JRST SU ;SWITCH TO USER " CALLI B,27 ;MAKE RUN TIME ONLY FOR AID kmon.mac appears to simulate both the distributor and the online disc processor parts. interp.mac just calls itself: arith.mac's only reference to JOSS is this: "P82.50: JUMPE ASF,P82.52; SF=0 |
I'm copying this comment.
|
Chapter 4 is about AID. |
Regarding DECDMP commands, here are some hints:
|
I found a copy of DECDMP without the KL10 additions. I will submit it to this repository: https://github.com/PashPaw/DECDMP |
I took a look at the Saildart version of DECDMP. I don't see that it has any file directory at all. It's just a linear core image starting from block 4. @rcornwell, why do you need a DECDMP with directory in block 1? |
I think, from my understanding, is that DECDMP is meant to load and start into DDT. From what RAND sent us in page 66 of RM-5216.pdf:
If I'm reading the PDP-6 Monitor manual right though (see pg. 75), it was possible to start a version of DECDMP from DECtape directly. That may explain why it needed to look for data at block 1 and not block 0. But, there was also a version that JOSS-II used that was bootstrapped with the RIM loader and paper tape. Again, see pg. 65 in RM-5216.pdf. |
@Epigenetic got (the first) JOSS running on an emulator. It occurs to me that JOSS II may well have a similar structure, so maybe missing parts can be modeled on the earlier version. Here's a series of articles well worth looking into: https://epigeneticslab.net/ |
I’ll take a look. I do have the last document that was not available on RAND’s site and it looks like it describes the file structures. I’m away ATM but I’ll figure out how to scan it later.On Jul 6, 2024, at 12:11 PM, Lars Brinkhoff ***@***.***> wrote:
@Epigenetic got (the first) JOSS running on an emulator. It occurs to me that JOSS II may well have a similar structure, so maybe missing parts can be modeled on the earlier version. Here's a series of articles well worth looking into: https://epigeneticslab.net/
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
The text was updated successfully, but these errors were encountered: