So after some intensive transcribing work I finally got all files into
source files ready for assembling using PAL11-S.
Assembling under PAL11-S rooted out a bunch of errors and then when side by
side comparing the output listing with the PDF I found a bunch of more
errors.
The next step involved linking and during the first run a number of errors
surfaced again.
On the last run I only had two undefined: $ICO and $ICI. It makes sense
since these two are part of the FPMP-11 package and used for number
conversion. However adding the FPMP-11 object as an extra input in the link
does not resolve these two undefined symbols.
Does anyone have a clue on how to get a proper link with FPMP-11 for these
two symbols?
Here is the repo with PDF files, source PAL files, LST files and OBJ files
as generated by PAL11-S:
https://github.com/MattisLind/SPACEWAR
/Mattis
> From: Mattis Lind
> I cannot figure out which early machine it comes from.
They're called 'System Modules':
http://gunkies.org/wiki/System_Module
and they were used from the PDP-1 through (I think) the PDP-7; at least, this
PDP-7 internals image:
https://www.soemtron.org/images/jpgs/decimages/sn113robertjohnson85680004.j…
seems to show System Modules at the top, and FLIP CHIPs at the bottom. (I'm
pretty sure even the first PDP-8 - the 'straight 8' - uses only early FLIP
CHIPs - transistorized ones.)
The DEC brochure for it (P5141) is a little puzzling; it says (p. 2) that
"INTEGRATED CIRCUITS are basic elements of the low cost, newly designed
silicon FLIP CHIP modules used throughout PDP-7", but AFAIK, the first FLIP
CHIPs (R-series, B-series, etc) were all transistors; the later M-series were
the first ones to have ICs. Maybe this is some old meaning of "integrated
circuits"?
Noel
wanted back issues IEEE ANNALS OF THE HISTORY OF COMPUTING? bound or unbound... dtop us a line off list please.... ed#? SMECC
Sent from AOL Mobile Mail
A friend and I went in on an Amiga 4000T haul last weekend, and with it
were some nice hard binder and box Microware OS-9 68x00 books. I want to
say there are two sets of two, and then some binders with photocopied
style paperwork for BASIC.
Is there any Microware fans that might want these? We were planning to
put most of the Amiga software up on eBay to cut down the cost of the
aquisition since it's mostly boring accounting/word processing stuff.
There are no disks with these manuals, just looking to find them a new
home.
Can get more details if anyone is interested.
--
: Ethan O'Toole
Finally got around to imaging the +/- 80 floppies that came with my ACI-90 Pascal Microengine system.
Disks of general interest can be downloaded on ftp://ftp.dreesen.ch/WD9000/MicroEngine.zip
These are mostly variants of the OS and a set of system selftests.
Image SYSTEM/OS_F0_SingleDensity.IMD might be of particular interest as that is a single-density OS-disk, might be needed for those with very early systems. All others images are for double-density systems.
Sorry for the lack of documentation, I don have anymore than this, and have yet to check the contents...
As a sidenote, all BASF disks were unproblematic, unlike the ControlData and noname parts that were also in the mix.
Jos
On another forum, a JW Early did a lot of magazine scans. ?I'll look to see if I saved any of his descriptions. ?My memory, ?he scanned twice, once for line and text, and again for images.
-------- Original message --------
From: Guy Dunphy via cctalk <cctalk at classiccmp.org>
Date: 01/01/2019 01:29 (GMT-08:00)
To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org>
Subject: On Scanning
This may be a good place to mention a text I began writing some while ago:
On Scanning.
? http://everist.org/temp/__On_scanning.htm
Meant to be a 'how to' about scanning and post-processing techniques, written as I
explored that myself. It's not finished because I was working on a solution to the
'screened images with overlaid sharp text' post-processing problem, when sidetracked.
As often happens with me. Also that project diverged into the whole text encoding
thing. Which I can't discuss, but I *can* discuss scanning issues.
Anyway, any comments, corrections and suggestions for extra material are welcome.
Oh, and those with an interest in Apple history may find this amusing:
? http://everist.org/NobLog/20181001_missing_wave.htm
Guy
Y
> From: Paul Koning
>> I haven't sat down with -C and -D manuals and done a bit-by-bit
>> compare. I just did that (I used the "RK11-C Moving Head Disk Drive
>> Controller Manual", DEC-11-HRKA-D, and the 1976 "Peripherals Handbook"),
>> and found in the following:
>> In the RKDS: bit 7 has changed the definition slightly ("Drive Ready"
>> to "R/W/S Ready"), but seems to be basically the same.
> You mean bit 6? Bit 7 is "drive ready" in both.
@*#$@*$%@&*!!!!! My silverfishionado nature screwed me! I didn't have an
RK11-D manual in paper, so I relied on the "Peripherals Handbook" - and it's
got an error!
In both the 1975 and 1976 edition, the _diagram_ for the RKDS shows bit 7 as
"R/W/S Ready", and bit 6 as "Access ready", but the _table_ shows bit 7 as
"Drive Ready", and bit 6 as "R/W/S Ready"! OK, so let me ditch that, since
it's self-contradictory, and thefore necessarily erroneous.
I'll switch to the RK11-D User's Manual, EK-RK11D-OP-001. It gives bit 7 as
"Drive Ready", and bit 6 as "R/W/S Ready". (The RK11-C manual gave bit 7 as
"Drive Ready", and bit 6 as "Access Ready".)
> Bit 6 has a different name in the two descriptions but the meaning
> appears to be the same.
Yup.
Thanks for catching that for me!
Noel
Very nice book scanner!There is? probably?a? second? career?? ?out there? for? you if? you? chose to? make them!Ed#
In a message dated 1/1/2019 11:01:31 AM US Mountain Standard Time, cctalk at classiccmp.org writes:
On Tue, 1 Jan 2019, Guy Dunphy via cctalk wrote:
> This may be a good place to mention a text I began writing some while ago:
>
> On Scanning.
>? http://everist.org/temp/__On_scanning.htm
>
> Meant to be a 'how to' about scanning and post-processing techniques, written as I
> explored that myself. It's not finished because I was working on a solution to the
> 'screened images with overlaid sharp text' post-processing problem, when sidetracked.
> As often happens with me. Also that project diverged into the whole text encoding
> thing. Which I can't discuss, but I *can* discuss scanning issues.
>
> Anyway, any comments, corrections and suggestions for extra material are welcome.
>
Here's a video on a diy book scanner I built in order to scan all the
Crescent Software documentation I got.? Seems relevant to this. :)
https://www.youtube.com/watch?v=niwLAbgRpDE
(Crescent Software archive is here:
http://annex.retroarchive.org/crescent)
g.
--
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.diy-cockpits.org/coll - Go Collimated or Go Home.
Some people collect things for a hobby.? Geeks collect hobbies.
ScarletDME - The red hot Data Management Environment
A Multi-Value database for the masses, not the classes.
http://scarlet.deltasoft.com - Get it _today_!