I went back to look at it last week for the first time in six years. It
certainly works well enough to run a whole bunch of diagnostics,
according to the notes I left back in 2008.
More documentation on the disk peripherals has surfaced in recent years,
and some of them would need to be implem
As I get ready to restart the Sigma project, I've gone back through the
Sigma disk specs. My notes are attached. The current simulation module
is not accurate, most notably in the way it allows controller/disk
pairings that didn't exist in real life.
Comments are welcome.
/Bob
Notes for the S
it's worth, is to focus on research about the
hardware, on understanding the hardware structure, and on modeling the
hardware with reasonable accuracy. Perhaps some veterans of the original
design team still retain design documents or microcode listings or
maintenance manuals; any or all wou
Bill,
Feel free to ask lots of questions here about the LGP-30. Unfortunately,
I don't have a lot of answers. I wrote it almost ten years ago, more to
work out the timing of a disk/drum memory system than anything else. As
the matrix at the end of one of the SimH documents show, it never
rece
This has been on the wish list for a decade.
The 15/76 Unichannel was a big PDP-15 that used a PDP-11/05 as an IO
processor to get access to inexpensive Unibus peripherals, particularly
the RK11-E/RK05, which supported 18b data, the LP11, the CR11, and
various plotters (not supported in SimH).
the PDP-11 posts an API interrupt back to the PDP-15
via one of the two DR11-C's.
/Bob
On 3/17/2015 11:42 AM, Mark Pizzolato - Info Comm wrote:
On Monday, March 16, 2015 at 2:19 PM, Bob Supnik wrote:
This has been on the wish list for a decade.
The 15/76 Unichannel was a big PDP-15 that used
Memory semantics on the 15/76 were very simple. Neither machine had
cache; neither machine had overlapped instruction execution; and neither
system had locking capabilities. Therefore, the only ordering constraint
is this:
- all memory writes in common memory must be visible (committed) before
simulator that
communicates across the bus just as the RQDX3 did. Would an approach make
sense that implemented the PIREX behaviors in a DR15 simulation (possibly,
internally talking to the various UNIBUS device simulations)?
Just a wild idea...
- Mark
On Tuesday, March 17, 2015 at 1:33 PM,
/semi/j11.html. The chip specifications are
on Bitsavers.
Mentec did produce a J-11 knockoff in other technology, but they have
gone under as well, I believe.
/Bob Supnik
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com
This issue, pointed out by Johnny Billquist, has been hanging fire for
years.
Fixing the FP11's use of MMR1 - implementation proposal
As has been noted, the FP11 does not update MMR1, ever. Instead, on an
abort,
general registers except the PC are unchanged from the values they held
at the
s
out the
logic paths of the actual implementation. I need "black box" tests that
work from the specification, without knowledge of the implementation.
Thanks,
/Bob Supnik
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
25/2015 4:49 PM, Don North wrote:
On 3/25/2015 8:52 AM, Bob Supnik wrote:
I'm looking for suggestions on how to test the revised FP11
efficiently. I wrote it so long ago that all my hand tests have
vanished.
Bitsavers has a set of paper-tapes for the 11/60's FP unit, but no
listi
Two years ago, Bob Armstrong pointed out that the 1620 emulators fails
diagnostic CU01. The failing instruction is a compare that lacks a flag
closing the P field, and the comparison wanders off into territory that
includes a record mark. The simulator stops if an arithmetic operation
is attemp
In the course of debugging the revised FP11, I ran into an interesting
and, as far as I can tell, hitherto undocumented incompatibility in the
various FP11 implementations.
The J11 Programmer's Reference states, and the microcode agrees, that if
enabled, an interrupt on undefined variable occu
A revised FP11 has been uploaded to Github, both the 'supnik source' and
the current branch (eventually). It fixes the long-standing bug reported
by Johnny Billquist that the FP11 never sets MMR1. It passes
diagnostics, modulo the incompatibility I reported in my previous message.
/Bob
__
For the few (any) users of the Eclipse, a serious bug introduced back in
2005(!) was fixed today. DIVS was testing AC0 instead of AC2 for the
divide by zero condition and producing spurious errors. As a result, AOS
hasn't worked for a decade.
It's now running again. See the GitHub issue list #
Does anyone remember the default password for 1,2 on RSTS/E modern versions?
I thought it was SYSTEM, but that doesn't seem to work.
I'm trying to test the PDP-11... thoroughly!
/Bob
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing
Your original calculation is correct. There are 815 cylinders, 19 heads,
20 sectors, and in the simulator, the sectors are 128 64b words (or 1024
bytes).
The the reason for the discrepancy is simple: the last five tracks
haven't been written by software. SimH data files are only as long as
th
RL02 USB drive
Date: Thu, 23 Apr 2015 06:06:25 -0700
From: Jim Gettys
To: Bob Supnik
http://kotaku.com/now-thats-a-large-usb-drive-1699154713/+megneal
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
As preparation for an eventual implementation, I'm writing a paper on
the workings of the UC15, as determined from the schematics. I've
answered the technical questions, but I'm left with a business question:
was it a commercial success? The online census of 18b systems dates from
'72, before t
Normally I'd publish this on the SimH web site, but I'm still locked out
(paging Tim Shoppa!), so I'm circulating it here for comments.
/Bob
The Unichannel.doc
Description: MS-Word document
___
Simh mailing list
Simh@trailing-edge.com
http://mailman
true of the RD52. It is actually 512 cylinders, not 480, and
the visible capacity is a subset of the physical capacity. There were
two different vendor drives used, one with 8 surfaces, one with 7, and
the capacity is limited to what the 7 surface drive could hold.
/Bob Supnik
On 5/7/2015 12
The RSX TPC issue is just one example of numerous timing dependencies
that have cropped up over the years. There's a paper on the SimH web
site about some of my favorites ("Bug, Feature, or Code Rot?"). If I can
ever find Tim Shoppa and get access to the web site again, I'll update
the paper.
t SimH is
getting to the fringes of the DEC world, like the PDP-15/76, and not
many of those experiments were solid commercial successes.
/Bob Supnik
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
les tapes could be read.
Also, Andreas Sandberg had made a somewhat working emulator
_with_ graphics support for the PDP-12. Perhaps his code can be
of some help:
http://www.update.uu.se/projects/greenpea.php
/P
On Fri, Jun 05, 2015 at 09:54:10PM -0400, Bob Supnik wrote:
Al Kossow published a lo
Yeah, PDP-7 (and earlier) DECtapes are different. They use different
checksum algorithms, for one thing, and some early PDP-4 and -7 DECtape
controllers used four-word headers instead of five. The checksum is
probably key; only five "four word header" DECtape controllers escaped
the factory.
It's actually pretty rate for simulators to run DEC diagnostics
correctly, particularly from about 1975 onward.
Initially, DEC wrote 'black box' diagnostics, which tested systems from
the functional spec inward. This is exemplified in the original T1 to
T17 series on the PDP11, which were inst
low-level flow control, meaning
that there was no way to block character transmission (in either
direction) once it started, even if the receiving UART was being overrun
due to heavy I/O traffic at higher interrupt priorities. MRSP solved
this particular issue
First, congratulations to Mark for running the current Ultrix 750
problem to earth.
Second, a brief diatribe about the need for fidelity to the hardware in
the VAX simulators, which is (on the face of it) lacking outside the
3900 and 780 simulators.
I have preached and documented the need fo
Vectors were all the rage at the time (late 80s) because of the success
of the so-called "minisupers" like Convex and Alliant. It was just a
flash in the pan, of course; with the end of the Cold War in the early
90s, funding for HPTC dried up for a decade, and all the minisuper and
VLIW compani
I'm kicking myself because in my days as a microcoder, I had the
microcode for every pre-85 VAX (including the 750 and 730) for reference
checking the MicroVAX II and CVAX microcode implementations. Like many
other people, I threw the listings away in a fit of downsizing because
"I'd never need
cking, the
750's does none.
The 750 simulator is not mine, but I'd like to track this problem down.
The RH750 schematics don't help, because the critical logic is inside
gate arrays. What's needed is an RH750 specification. Does anyone h
ject: Re: [Simh] Needed:
RH750 specification Message-ID: <55c8f558.1060...@ieee.org>
Content-Type: text/plain; charset="utf-8" On 10-Aug-15 14:13, Bob
Supnik wrote:
>Mark Pizzolato sent me a note about a code sequence in the original
>VAX750 bootstrap that fails on the 750
On 8/12/2015 12:00 PM, simh-requ...@trailing-edge.com wrote:
Message: 1
Date: Wed, 12 Aug 2015 09:03:41 -0400
From: Timothe Litt
To:simh@trailing-edge.com
Subject: Re: [Simh] Needed: RH750 specification
Message-ID:<55cb442d.5010...@ieee.org>
Content-Type: text/plain; charset="utf-8"
For the non-
While no RH750 spec has been found, the spec for Emulex's SC/750 is
online. It provides a detailed summary of the RH750 internal registers.
As I suspected, the RH750 is a subset of the RH780, with lots of status
bits and a register or two omitted. It also adds a mode not present in
the RH780 -
When flag REG_VMIO is set, printing/parsing are done through the
user-supplied print/parse routines, a special switch is set, and the
normal UNIT pointer argument is left as null.
For the REG_VMIO case ONLY, scp could fill in the UNIT pointer argument
with a pointer to the register data struct
I haven't forgotten about the project. I've just been busy on other
things, like 35 years of neglected house repairs. ;)
The UC15 is another example of minimization of gates, a consequence of
how expensive gates were at the opening of the TTL era. The DR15C, which
was implemented in Flip Chips
I added my comments as follows:
The four VAX chips differ slightly in their interrupt behavior.
1.
MicroVAX II - and ONLY MicroVAX II - will mask the incoming
interrupt vector down to 10bits. Bit<1> is ignored, and bit<0> is
treated as the 'Qbus' flag; if set, it forces all device inte
The width of the vector read, and potential masking by the processor, is
moot, because the Qbus spec defines vectors as 9b, with two low order
0s. (The Unibus spec does as well.)
For hardware-generated vectors, the controllers provided a 6b or 7b
jumper block (with two implicit low order 0s) t
need a system with a working
9-track magtape, preferably one that treats tapes very gently. Does
anyone know of a working setup?
/Bob Supnik
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
There's nothing conditional about the user documentation. The 1965
reference manual says, "MARS (Memory Address Register Storage) Check
Light. This light is turned on when a digit in MARS has a parity error
or an invalid address. These errors halt the machine immediately."
Now the key question
On 12/24/2015 5:20 PM, Paul Koning wrote:
On Dec 23, 2015, at 4:30 PM, Bob Supnik wrote:
There's nothing conditional about the user documentation. The 1965 reference manual says,
"MARS (Memory Address Register Storage) Check Light. This light is turned on when a
digit in MARS has a p
Bob A is right. I found the MAR checking logic on pp 292-3 of 227-5631-0.
For the low four digits of MAR, there are two circuits: a C-bit checker
and an invalid digit checker.
C-bit checker is: (b4 xor b2) xor (b1 xor b8) xor C
invalid digit checker is: (b4 or b2) and b8 - which picks up 1010
27;t run software on hardware models that it doesn't support.
And compress your disk images before posting them.
/Bob Supnik
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
pectively. You'd get pretty close, with no
possibility of damaging the existing TD.
/Bob Supnik
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
The 11/23 simulator boots the ibiblio image called "xxdp22_with_1123"
correctly. However, the image is XXDP+, not XXDP 2.2:
PDP-11 simulator V3.10-0
sim> set cpu 11/23,64
sim> att -e rl c:\temp\xxdp_with_1123.rl02
sim> boot rl
CHMDLD0 XXDP+ DL MONITOR
BOOTED VIA UNIT 0
28K
DOES THIS SYSTEM HAV
I did a quick hack and removed the clock from the device list,
effectively disabling it. With that done, the 11/23 runs XXDP V2
correctly, with 64KB of memory. I'll add BEVENT DISABLE to formalize this.
So the failing systems are the 03, 04, 05, and 20. Possible common factors:
- no memory man
U. It hangs
just like the 11/03, 04, 05, and 20.
Why it fails is unknown. Mattis' real 11/04 gets further than the
simulator, although it ultimately fails.
/Bob
On 12/30/2015 12:00 PM, simh-requ...@trailing-edge.com wrote:
Message: 1
Date: Wed, 30 Dec 2015 11:28:35 -0500
From: Bob
The "2.2" image on ibibilio is actually XXDP+, the "V1" monitor. It runs
everything, including the 11/03 and 11/23 with BEVENT enabled. The 2.5
image runs on the 03 and 23 with BEVENT disabled, as well as the 04, 05,
20; in effect, everything as well.
So the problem occurs in Mattis' XXDP 2.2
With my current head of line source, I get an 'intermediate result'. You
cannot give the commands in the order specified - attaching prevents
changes in format. However, if you do the corrected order - enable/set
format/attach - then the attach succeeds, without the "read only"
message. Checkin
The short form:
I have no problem setting the default for PDP11 TTO to 7B instead of 7P,
although I'm sure some old software will break. If this is done, though,
I would suggest reverting the previous change to the printable character
mask back to its original settings. The pdp11_dc.c default
The PDP8 simulator does not have any support for any DECmate.
The RX50 works fine on the PDP11 as a data disk, with RT11 v5.3. I do
not have the expertise to set it up as a boot disk. Perhaps one of the
RT11 experts on the mailing list can try that.
/Bob Supnik
On the PDP11 and VAX, RL, RP, and RM drives require bad block formatting
after an initial attach (that is, creation of a new file). After that,
the question should not be asked again.
The PDP10 operating systems did their own bad block management and did
not require a standard bad block table.
You'll miss the late additions to the architecture for NVAX and the 9000.
However, you can get the 1990 version, in its internal DEC form rather
than book form, from
http://bitsavers.trailing-edge.com/pdf/dec/vax/archSpec/EL-00032-00-decStd32_Jan90.pdf.
/Bob Supnik
On 1/28/2016 12:
I agree: documented procedures for working with various operating
systems and software systems are very useful. That's why a number of
simulators include instructions on running diagnostics and the like.
If someone can create a "cookbook" for getting OS32 up and running, it
can be added to the
idual simulator user is supposed to file a license with
Unisys. There is no cost.
/Bob Supnik
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
as some working exhibits (PDP-1, IBM 1401,
IBM RAMAC) too. There are quite a few working minicomputers and
microcomputers in private hands as well.
/Bob Supnik
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
And then there was early computer music...
When Applied Data Research got its PDP-7 in 1966, there was a DECUS
program to get it to play music by toggling the lower order 4 bits of
the MQ (and the MQ lights) to generate square waves. If you wired that
up to an audio player, you got electronic
Okay, I'll bite - what's a VXT1200? I see references to it on Google,
but I can't find a clear description.
Tim Litt said rtVAX was never intended to run VMS, but its history is a
bit more complicated. The original intent of the uVAX chip program,
which kicked off in the spring of 1982, was to
The code path to get to this problem is quite short:
TLBENT fill (uint32 va, int32 lnt, int32 acc, int32 *stat)
{
int32 ptidx = (((uint32) va) >> 7) & ~03;
int32 tlbpte, ptead, pte, tbi, vpn;
static TLBENT zero_pte = { 0, 0 };
if (va & VA_S0) { /* system space? */
if (ptidx >= d_slr) /* syst
When SimH was written, its design assumption was a 32b host simulating
smaller than 32b targets. As a result, all the early simulators play
fast and loose with signed vs unsigned integers, because the data was
always 6b or 8b or 12b or 16b or 24b in a 32b container. Even if the
container was si
m yields P1BR = 0, which is wrong, wrong, wrong.
It indicates that P1BR still has its initial value and has never been
loaded.
Normally, I'd debug this myself, but I don't have a Mac.
/Bob Supnik
On 2/18/2016 7:57 AM, simh-requ...@trailing-edge.com wrote:
Message: 6
Date: Thu, 18 F
The VAX architecture went through several major emendations - including
both extensions and removals - from its initial version in the late 70s
until it was "frozen" in 1990.
The architecture always deliberately excluded a couple of areas, in
particular, IO, error handling, and the console. Al
SimH stores 18b data, whether disk or DECtape, right justified in a 32b
container.
As for ASCII data... "it depends." DEC's own software for the PDP-7 used
a mishmash of character sets, including FioDEC, Baudot, and the early
form of ASCII associated with the KSR-33. The official assembler did
I think the answer is two characters per 18b word, right aligned in a 9b
"byte".
This is based on the assembly code at the end of the first PDF:
a.out:
; ; Clearly it's just two characters per word (; denotes end of statement to
this assembler). 040040 is octal for space-space in ASCII, on
, surprisingly, appear to use the extended memory
function or the protection trap that came with it. EEM (enter extend
mode) isn't even defined. This would seem to imply it ran in 8KW of memory.
/Bob Supnik
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
1. Create an RB09 variant at half size and allow it to be configured in
the PDP7. No need for dynamic size support; Unix v0 supports one size
(8000 sectors), and PDP9 software supports one size (16000 sectors).
2. Create a card reader for the PDP7. With minor mods, the same device
could suppor
Just passing along what Warren and I are discussing.
1. How command parsing worked.
It appears that the command parser generated an argument list and stored
a pointer to it in the last word in addressable memory (01 - another
indicator that Unix v0 used just 8KW). The format was:
c(01777
The RM09 has the same size options and programming model as the Type 24
serial drum on the PDP4 and PDP9. Perhaps the "UD" option referenced in
the services list was a later, larger capacity model, but there's no
documentation one way or another.
It's very easy to add the drum to the PDP-9, an
I thought the full listing was on Bitsavers, but apparently not - maybe
because it's huge (110MB). I've put a copy up temporarily here:
https://mega.nz/#!DB5nTRZI!aMQ_0UN7LfyJvep1_e9dP1RZsZyd5fASOivgPSaqZyk
The listing does raise a lot of questions, like, why are there PDP-9s
with RD10s on the
AFAIK, this is the only surviving fragment of what must have been a
complete systems listing. I found it in the DEC archive when I was
cataloging the archive for shipment to the CHM. The archive was
relatively good on the early machines; for the later ones, the
assumption was that paper was no
Max Burnet gave me a pointer from some old price lists, showing that the
RD10 had very similar specs to the RB09. The RC10 manual confirms it -
same BCD addressing of tracks and sectors, same number of tracks, same
sectors per track, same words per sector (32 x 36b for the RD10, 64 x
18b for th
ndy if a programming
experiment wrecked the disk image.
/Bob Supnik
Analysis of the UNIX v0 disk driver, or,
Why the Unix v0 disk is, in fact, an RB09, or,
The RB09 and the RC09 are the same thing
To start, remember that the Unix v0 disk (and the RB09
and the RC10/RD10) are BCD addressed, with 80
-requ...@trailing-edge.com wrote:
Message: 3
Date: Sat, 27 Feb 2016 09:31:59 -0500
From: Timothe Litt
To:simh@trailing-edge.com
Subject: Re: [Simh] RB09 == RD10
Message-ID:<56d1b35f.3040...@ieee.org>
Content-Type: text/plain; charset="utf-8"
On 27-Feb-16 08:23, Bob Supnik wrote:
MDL sources for Dungeon are online here:
http://simh.trailing-edge.com/games/zork-mdl.zip
/Bob
On 2/29/2016 3:48 PM, simh-requ...@trailing-edge.com wrote:
Message: 3
Date: Mon, 29 Feb 2016 14:48:47 -0500 (EST)
From: Rich Alderson
To:simh@trailing-edge.com
Subject: Re: [Simh] Klh10 vs Simh
Mess
The PDP-10 has networking as well. The H316/516 supports the IMP
(interface message processor) used for ARPAnet.
Network was only implemented on systems that were in active development
past the mid 1970s, when commercial networking stacks like TCP/IP,
DECnet, SNA, BNA, etc emerged. There's an
I've pulled together the hardware pieces for the PDP-15/76 (PDP-15 with
UC15 PDP-11 IO processor), so now it's time to consider what software
can be run.
The most likely candidate is XVM/DOS-15. While vanilla DOS-15 had UC15
support at some point, neither a complete source kit nor the appropri
That would be much appreciated. The following are of particular interest
to me:
XUSMA - XVM Unichannel
LMALA - XVM Macro15
LMLAA - XVM Mac11 (PDP11 assembler)
LFLGA - XVM FOCAL
ULLUA - XVM linking loader
If this is too much, priority is top to bottom.
Thanks,
/Bob Supnik
On 3/15/2016 1:31
While I was digging deeper and deeper into the extent PDP-15 sources, I
found a tantalizing reference: "the RP03 is supported as an RP02." This
was the first time I'd seen any indication that the PDP-15's RP
controller supported the later, double-sized disk. The XVM/MUMPS sources
(which are, al
Yes, their contents might be very useful. You never know what you'll
find, but DECtapes hold their contents extraordinarily well for magnetic
media.
/Bob
On 3/16/2016 4:06 AM, Pontus Pihlgren wrote:
An I have DECtapes from this system. I recall at least one being labled
DOS. Could the content
x "v0" on the PDP7.
The controller, formally an RC07, was probably a one-off built by
Computer Special Systems or Traditional Products for Bell Labs.
/Bob Supnik
On 3/23/2016 12:00 PM, simh-requ...@trailing-edge.com wrote:
Found it. It is an RB09. I didn't realize how
1. Attach a (new) host file to the simulated printer on VMS.
2. Print your VMS text file to file to the simulated printer.
3. Let some time elapse, to make sure the print spooler finishes.
4. Detach file from the simulated printer.
5. VMS text file is now on your host in the host file you specifi
How can I get the macro11 cross-assembler to output absolute binary
format? Or is there a post-processing program that I've forgotten about?
Thanks,
/Bob Supnik
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/ma
It was never added to the SimH manual. I've submitted a new version to
the GitHub editor for merging.
/Bob
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
Bob, this will help me a great deal. A question though,
everything I've read has been for the PDP -8/A. Doesn't simh simulate
the E?
Thanks
Ray
On Apr 9, 2016 2:41 PM, "Bob Supnik" <mailto:b...@supnik.org>> wrote:
It was never added to the SimH manual. I'
to file a bug report.
/Bob Supnik
On 4/11/2016 10:16 AM, simh-requ...@trailing-edge.com wrote:
Message: 1
Date: Mon, 11 Apr 2016 14:33:21 +0200
From: Wilm Boerhout
To: SIMH Mailing List
Subject: [Simh] MicroVAX II time across boots
Message-ID:<570b9991.4050...@gmail.com>
Content-Type:
Sigh... just looked through ka630_* modules.
Anyway, the byte access/word addressing is in the spec. So the code is
allowing writes to bytes that don't exist. Further, it is trying to deal
with lengths other than byte or word, and the access and control paths
don't exist in the hardware.
VMS
Amen!
If you're trying to transfer files to or from a simulator, then think
about how it was done /on the real machine/. There's almost always a
solution, for any given simulator/OS pair.
For systems from the 50s and 60s, it's punched cards, which are usually
simulated as ASCII text files. S
ext
files into IBSYS job decks and turn IBSYS output magtapes into text
files, as well as a generalized command procedure for running jobs.
If the file transfer issue is not addressed to your satisfaction in a
particular simulated environment, then take it up with the developer or
maintainer of
It took some research, but I've regained access to the SimH website.
When I return in mid-May from a trip, I'll be updating the website's
papers and software kits, which have been frozen for a year.
As is the case now, GitHub remains the official source for SimH sources,
whether on the older
define DEV_TTO1051 /* second
console output */
#define DEV_CPU 077 /* CPU control */
For a more extensive list, consult the Nova documentation on
http://bitsavers.org/pdf.
/Bob Supnik
On 4/30/2016 12:49 AM, simh-requ...@tr
With the restoration of PDP7 Unix coming along nicely, how about a PDP7
hardware emulator and front panel so that everyone can have their own
"unix v0"? Dave Conroy did a PDP4 emulator in an FPGA
(http://fpgaretrocomputing.org/pdp4x/) that includes the EAE, so there's
a good starting point. Wha
Upstate Medical Center in Syracuse had a number of PDP-15s, including
XVMs. Some are still be in the hands of a private collector. However,
that person is unwilling to share materials, particularly software kits,
from his collection.
If the RP disks follow normal SimH practice, then they are s
r, and the restoration of Unix "v0" (PDP-7 Unix). But there's always
more to do.
/Bob Supnik
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
There is a proposed card reader library (not mine) in the GitHub
repository, which you could try.
On the 1401, the handling is as follows:
1. The card reader buffer is 2*CBUFSIZE + 1, where CBUFSIZE is an
internal SimH constant for buffer size. The buffer is zeroed before a read.
2. The card i
t it's
supposed to do. I didn't know of any surviving software, either (except
now DoD's), so there was never any real motivation to work on an
emulator. Perhaps DoD would like to sponsor one . ;)
/Bob Supnik
**
___
Simh mailing list
t=utf-8
On 5/26/16 5:29 PM, Al Kossow wrote:
>
>
>On 5/26/16 1:46 PM, Bob Supnik wrote:
>>I didn't know of any surviving software
>
>look on bitsavers for docs and software, unless I forgot to upload it.
>
I just looked, and I haven't put up the floppy images
Please see the SimH web site
(http://simh.trailing-edge.com/software.html) for examples of kits to
run on SimH simulators. This works better for simple, stand-alone
applications that for full operating systems with layered products
installed, some of which (like VMS) require licenses and media
A really valuable tutorial. It's also the first proof that the LGP30
simulator sort-of works; I'm relieved.
Shoehorning the LGP30's operating procedures into SimH's default syntax
was difficult. It might have been better to use the 'simulator-defined
command' capability to create a set of LGP
There are any number of strange-length divide algorithms in SimH. Here
is the PDP-10 code for dividing a 70b unsigned integer by a 35b
(unsigned) integer.
// dvd[0:1] = 70b dividend, high order first (35b in each word)
// dvr = 35b divisor
// rs[0:1] = quotient remainder
// all variables (excep
1 - 100 of 256 matches
Mail list logo
