Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge branch 'master' into gh-pages, and fix a few issues related to autoStart

Browse source 
# Conflicts:
#	_posts/2016-12-02-the-pdp-11-and-vt100-revisited.md
#	docs/pcx86/examples/pcx86-dbg.js
#	docs/pcx86/examples/pcx86.js
This commit is contained in:
Jeff Parsons 2016-12-04 11:26:10 -08:00 • committed by Jeff Parsons
commit 9ed580066c
33 changed files with 348 additions and 321 deletions
Download patch file Download diff file Expand all files Collapse all files

6
_posts/2016-12-02-debugging-pdp-11-issues.md
View file

@ -10,13 +10,13 @@ I'm still trying to flush out lingering bugs in PDPjs. I'll give you an example
![Image of PDP-11/70 with 256Kb, Front Panel and Debugger](/blog/images/pdp-1170-panel-debugger.png)
After loading the "MD-11 11/70 CPU EXERCISER" paper tape image directly into memory using the "Load" button
(*not* "Attach"), and then loading the "RT-11 v4.0" disk image into drive RK0, and then finally issuing a few
After loading the "MD-11 11/70 CPU EXERCISER" paper tape image directly into memory using the **Read** button
(*not* **Load**), and then loading the "RT-11 v4.0" disk image into drive RK0, and then finally issuing a few
preliminary Debugger commands:
m rk11 on; bp 005254
we're ready to "let 'er rip," either by using the Debugger `g` command or clicking the "Run" button.
we're ready to "let 'er rip," either by using the Debugger `g` command or clicking the **Run** button.
You'll see a variety of disk-related messages from the RK11 component in the Control Panel window, which serves
both as the Debugger's output window and as the 11/70's terminal window. The output begins with: