19 Apr
2014
19 Apr
'14
9:43 p.m.
At 05:58 PM 4/19/2014, Rick Bensene wrote:
Kyle wrote:
24K isn't enough to run it. FRTS *should* tell you it's not enough,
however.
Here's what I get when I try with 24K:
.R FRTS
*ADVENT$MORE CORE REQUIRED
(the "$" is where I hit escape.)
I tried another version from here:
http://www.rickmurphy.net/adventure.htm land it seemed to work just
fine,
although for whatever reason, typing DIR results
in "No room for
output file."
I'm not sure exactly what it means by that; I
don't get the same
error from
running in simh.
In any event, I can now run Adventure on my 8/M!
I tried the version from the link above on my 8/e. I copied it using
the OS8 Disk Server, from the RK05 image to an actual RK05 and ran it
from there.
My machine has 24K (8K core, 16K MOS), 2 M8650 serial interfaces,
RK8E, PT8E, and RX8E. When I run ADVENT, it loads, but then just sits there
in an apparent
loop. If I type characters, nothing happens, except if I type
CONTROL-C, it does exit back to OS/8. I've let it sit a few minutes,
thinking that maybe it takes a bit to initialize, but that clearly
isn't the case.
I also tried the "R FRTS ADVENT.LD"<ESC> but with this, I get a $
prompt which appears to be coming from FRTS, and don't know what to do
from there. I did try typing "SYS:ADVENT.LD" at the $ prompt, but it
just comes back with another $ prompt.
Hmm. Seems like FRTS doing something bad.
I'd try with a simple FORTRAN program and see if that works. Using
Adventure to debug is a pretty heavy diagnostic. :)
I do note that the INT BUS in is lit. This means that
an interrupt is
pending, but the ION state indicator is off. I have the serial
interfaces set up to use interrupts if they are enabled. To get
CHEKMO-II (which uses interrupts for I/O to the console) to run, I had
to add some code to the interrupt service routine to ignore any
pending interrupt from the second serial interface.
There's a way to add an additional interrupt service routine to FRTS to
handle other devices, or you can run a program that just clears the
flags on that device first.
-Rick