Re: Microcode, which is a no-go for modern designs

2019-01-03 Thread Eric Smith via cctalk
And the original analysis paper, "It Takes Six Ones to Reach a Flaw":
http://www.acsel-lab.com/arithmetic/arith12/papers/ARITH12_Coe.pdf


Re: Microcode, which is a no-go for modern designs

2019-01-03 Thread Eric Smith via cctalk
Also
http://www-math.mit.edu/~edelman/homepage/papers/pentiumbug.pdf


Re: Microcode, which is a no-go for modern designs

2019-01-03 Thread Eric Smith via cctalk
On Wed, Jan 2, 2019 at 9:12 PM dwight via cctalk 
wrote:

> I believe that is the one. Intel tried to say it wasn't an issue until it
> was shown that the error was significant when using floating point numbers
> near integer values. I suspect that the fellow that forgot to include the
> mask file for that ROM got a bad review.
>

The majority of the ROM contents were present. Apparently five entries were
missing.
http://www.verifsudha.com/2017/09/11/pentium-fdiv-bug-curious-engineer/


Re: music dec tapes? (paper)

2019-01-03 Thread allison via cctalk
On 01/03/2019 05:22 PM, Kyle Owen wrote:
> On Thu, Jan 3, 2019 at 3:29 PM allison via cctech
> mailto:cct...@classiccmp.org>> wrote:
>
> Those were likely with a PDP12 or LAB-8 with DAC board.  The code
> actually is a roughly
> digital version of tones in 10 or 12 bit form by writing sequential
> words (waveforms) to
> the DAC.  
>
>
> Do you have any information on the AA01-A DAC that was used with the
> PDP-12?

No but RICM as a PDP12or two.  Worth contacting them and all.  They
might like a copy of the
tapes if they don't already have them.

> I see in the PDP-12 System Reference Manual that it is capable of
> supporting three channels, 12 bits each. It gives an example of one
> instruction, 6551, which loads the first DAC. Is it safe to assume
> that 6552 and 6554 are the other instructions to load the other two DACs?
>
Unknown.

> I see the AA50-A in the 1972 PDP-8 Small Computer Handbook has
> sequential instructions for updating the DAC channels (up to 8).
>
> AA05-A/AA07 use a more complex address/data method to address more
> total channels, but that is listed in the Laboratory Computer Handbook
> as an option on the Negibus.
>
>
Never played with 8s in any form other than omnibus.

> Of course everyone here forgets the First Philadelphia Computer Music
> Festival on vinyl from '78
> with samples of computer played music.  I run my copy on occasion just
> to remember being there.
>
>
> I don't think this album has been forgotten; I have a copy, and I know
> others with copies, too. It seems as though "Unplayed by Human Hands"
> (both versions) are less well-known. I would like to work on getting
> the original software archived, assuming it's still out there, as it
> ran on a Straight-8.
>
ITs also on line.

Allison


Re: music dec tapes? (paper)

2019-01-03 Thread Kyle Owen via cctalk
On Thu, Jan 3, 2019 at 3:29 PM allison via cctech 
wrote:

> Those were likely with a PDP12 or LAB-8 with DAC board.  The code
> actually is a roughly
> digital version of tones in 10 or 12 bit form by writing sequential
> words (waveforms) to
> the DAC.
>

Do you have any information on the AA01-A DAC that was used with the
PDP-12? I see in the PDP-12 System Reference Manual that it is capable of
supporting three channels, 12 bits each. It gives an example of one
instruction, 6551, which loads the first DAC. Is it safe to assume that
6552 and 6554 are the other instructions to load the other two DACs?

I see the AA50-A in the 1972 PDP-8 Small Computer Handbook has sequential
instructions for updating the DAC channels (up to 8).

AA05-A/AA07 use a more complex address/data method to address more total
channels, but that is listed in the Laboratory Computer Handbook as an
option on the Negibus.

>
> Of course everyone here forgets the First Philadelphia Computer Music
> Festival on vinyl from '78
> with samples of computer played music.  I run my copy on occasion just
> to remember being there.
>

I don't think this album has been forgotten; I have a copy, and I know
others with copies, too. It seems as though "Unplayed by Human Hands" (both
versions) are less well-known. I would like to work on getting the original
software archived, assuming it's still out there, as it ran on a Straight-8.

Thanks,

Kyle


Re: music dec tapes? (paper)

2019-01-03 Thread allison via cctalk
On 01/03/2019 09:03 AM, Bill Degnan via cctech wrote:
> I have tapes with labels
>
> 8-152a 8 Music Coding Program Symbolic #1
> 8-152   8 Music Coding Program Symbolic #2
> 8-152   Teddy Bear's Picnic Symbolic
> 8-152a Penny Lane Symbolic
> 8-152 Joy to the World Symbolic
> 8-152 Your Mother Should Know Symbolic
>
> 8-152a Penny Lane 0037-7720, 0170=
>  0171=, 0172=7750,
>  0173=6020 Binary
>
> 8-152  When I'm 64
> 0037=720, 0170=7776
> 0172-7750
>
> 8-162   MUSIC FOR THE PDP-8
>  Load Tunes: 440
>  Play Tunes: 400
>
> "Start 8 Music"  (hand-written, no printed label)
>
> On Tue, Jan 1, 2019 at 9:03 PM Kyle Owen via cctalk 
> wrote:
>
>> On Tue, Jan 1, 2019, 15:18 Adrian Stoness via cctalk <
>> cctalk@classiccmp.org
>> wrote:
>>
>>> anyone seen these music tapes before i grabed  this trays for the oddnes
>> of
>>> the content of these tapes? also apears to have the software to play
>> them?
>>>
>>>
>> https://www.ebay.ca/itm/Lot-of-15-digital-decus-Paper-Tapes-w-Case/273628629483?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2060353.m2749.l2649
>>>
>>>
>> https://www.ebay.ca/itm/Lot-of-8-digital-decus-Paper-Tapes-w-Case/273628539210?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2060353.m2749.l2649
>>> would this be some weird synthy type thing?
>>> control points for the sound boaerd used for automation on some fancy
>> desk?
>>> or somthing els?
>>>
>> Vince has a listing for some version of DECUS 8-152 on his website (
>>
>> http://svn.so-much-stuff.com/svn/trunk/pdp8/src/decus/8-152/decus-8-152-lst.pdf
>> ).
>> I have reverse engineered it enough to have his version play a few songs.
>> However, it seems like there's a difference between the music tapes I have
>> and the listing he has.
>>
>> I don't know what hardware was required of this software, but I suspect it
>> to be a DAC responding on address 055. This seems to match with an AA01
>> option.
>>
>> Did you end up buying these tapes? I have digitized the music tapes I
>> bought from the seller and will post them soon. It would be excellent if
>> the buyer of this lot would do the same.
>>
>> Musically,
>>
>> Kyle
>>

Those were likely with a PDP12 or LAB-8 with DAC board.  The code
actually is a roughly
digital version of tones in 10 or 12 bit form by writing sequential
words (waveforms) to
the DAC.  Before that it was done setting link and clearing link bit
with a timing routine.

There was a version of that also for MINC-11 and I've see variant back
when that used multiple
DAC cards for stereo or multiple voices.

It was also a thing for the S100 8080/z80 set (using a DAC) and many
other systems
(Kim-1, Apple, Cosmac, Commodore).

Of course everyone here forgets the First Philadelphia Computer Music
Festival on vinyl from '78
with samples of computer played music.  I run my copy on occasion just
to remember being there.

Allison



Re: music dec tapes? (paper)

2019-01-03 Thread Kyle Owen via cctalk
On Thu, Jan 3, 2019, 17:48 allison  I don't think this album has been forgotten; I have a copy, and I know
> others with copies, too. It seems as though "Unplayed by Human Hands" (both
> versions) are less well-known. I would like to work on getting the original
> software archived, assuming it's still out there, as it ran on a Straight-8.
>
> ITs also on line.
>

The recordings, or the software? If you're referring to the latter, please
send a link! I know someone has a GitHub repository, but it's missing any
and all PDP-8 files.

Kyle

>


Re: PDP-11/45 RSTS/E boot problem

2019-01-03 Thread Fritz Mueller via cctalk


> On Jan 3, 2019, at 5:17 PM, Paul Koning  wrote:
> 
> So in this example, 55230 is the error logging entry point for the RK11 
> driver. ... If you have a breakpoint at this location, you'll be able to 
> capture the controller CSR contents which -- I hope -- will explain why the 
> system is not happy.
> 
> The way to set the breakpoint is simply to enter control/P for ODT, then 
> 55230;B to set the breakpoint, then P to proceed.

Thanks, Paul!  Tried but no luck:

177404 113000 002010 05
$DK


RSTS V06C-03 FRITZTS (DK0)


Option:

Disk is being cleaned - wait …


You currently have: JOB MAX = 10, SWAP MAX = 28K.

You currently have crash dump enabled.

DD-MMM-YY? 03-JAN-89
12:00 PM? 6:46 PM

(...system starts looping error behavior; type ^P...)

BE125652
_55230/004537
_55230;B
_P

(...system resumes looping error behavior without hitting breakpoint; sadness)

Any additional or different recommended breakpoints to try?  Or did I miss 
setting this up (I’m new to ODT.)

thanks much,
  --FritzM.



Re: PDP-11/45 RSTS/E boot problem

2019-01-03 Thread Paul Koning via cctalk



> On Jan 3, 2019, at 11:51 AM, Fritz Mueller via cctalk  
> wrote:
> 
> Hi Paul,
> 
>> On Jan 3, 2019, at 7:01 AM, Paul Koning  wrote:
>> 
>> I have a Monitor ODT manual from RSTS V4, I should find a way to make that 
>> available.  It's pretty nearly standard ODT, there are a few extensions for 
>> mapping addresses
> 
> Bitsavers has some docs for ODT from contemporaneous versions of RSX-11, 
> which have seemed close enough to get me going with some experimentation.
> 
>> To find LOG$DK, you can either look in the link map (RSTS.MAP) from the 
>> SYSGEN, or ask the init PATCH option to tell you
> 
> So, I don’t see a LOG$DK in my V06C RSTS.MAP (though I do have LOG$KB and 
> LOG$TM).  PA returns “address above module bounds” when looking for it, which 
> I assume means it searched without finding it. 

What we have here is a confusion on my part.  The LOG$xx symbols are for the 
most part defined in the kernel definitions file KERNEL.MAC.  They are EMT 
instructions with a device code in the low byte; in the kernel an EMT is 
handled as a request to invoke the error logging machinery.

Dispatching for that goes through a table indexed by the EMT code, so what you 
actually need is to look in the correct entry of that table to find the RK11 
driver logging entry point.  A breakpoint set there should trigger when a disk 
error is reported by the driver.  Here's how:

RSTS V06C-03 FRITZTS (DK0)


Option: PA
File to patch? ERRTBL
Illegal file name
File to patch? 
Module name? ^C

Option: PA
File to patch? 
Module name? 
Base address? ERRTBL
Offset address? LOG$DK-104000
 Base   Offset  Old New?
030162  30  055230  ? ^Z
Offset address? ^Z
Base address? 55230
Offset address? 0
 Base   Offset  Old New?
055230  00  004537  ? ^C

Option: 

So in this example, 55230 is the error logging entry point for the RK11 driver. 
 In V10.1, that code looks like this; I suspect the V6C code is the same or 
nearly so:

.SBTTL  ERROR LOGGING

ERRENT  LOG$DK

CALLX   ERLDSK,R5   ;;;USE COMMON ROUTINE
  .BYTE ERC$DK  ;;;ERROR CODE
  .BYTE -1  ;;;OVERLAPPED SEEK
  .BYTE RKDS,6  ;;;OFFSET, 6 REGISTERS
  .BYTE 0,0 ;;;THAT'S ALL
RETURN  ;;; AND BACK

In any case, that doesn't really matter.  If you have a breakpoint at this 
location, you'll be able to capture the controller CSR contents which -- I hope 
-- will explain why the system is not happy.

The way to set the breakpoint is simply to enter control/P for ODT, then 
55230;B to set the breakpoint, then P to proceed.

paul



Re: SPACE WAR for PDP-11 - link issues

2019-01-03 Thread Paul Koning via cctalk



> On Jan 3, 2019, at 3:49 PM, Mattis Lind via cctalk  
> wrote:
> 
> Success sort off!
> 
> ...
> 
> HALT instruction, PC: 42 (BIC R4,SP)
> 
> sim>
> 
> So it does run! I would guess that the lack of proper AD01 and AA11
> hardware in SimH is the reason for the HALT, but it remain to be
> investigated!
> 
> Next step is to adapt the code to the AR11 hardware in place for AD01 and
> AA11.

Or add AA11/AD01 emulation?  They are simple devices.

I wonder if I still have my lab extensions to RT11 BASIC, which include code 
for those peripherals (as well as DR-11 and KW11-P).

paul



RE: Which DEC machine made use of th pre Flip-Chip board?

2019-01-03 Thread Rich Alderson via cctalk
From: Noel Chiappa
Sent: Friday, December 21, 2018 5:19 AM

>> 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.jpg

> 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.)

Noel,

The PDP-7 was the first system produced by DEC which used Flip Chip(TM)
technology, as well as the first to be built using a Gardiner-Denver wirewrap
machine instead of hand soldering.

The System Modules(TM) in the PDP-7 chassis at LCM+L make up the 550 DECtape
control for the 555 DECtape drives.  The controller was common to the PDP-7 and
the earlier PDP-4 (which was of course all System Modules).  They appear in
exactly one place in the entire system.

Rich

Rich Alderson
Vintage Computing Sr. Systems Engineer
Living Computers: Museum + Labs
2245 1st Avenue S
Seattle, WA 98134

mailto:ri...@livingcomputers.org

http://www.LivingComputers.org/


Re: SPACE WAR for PDP-11 - link issues

2019-01-03 Thread Mattis Lind via cctalk
Success sort off!


>
> the source paper tapes for fpmp are at
> http://bitsavers.org/bits/DEC/pdp11/papertapeimages/20040101/tray07
>
> TRAY07
>
> dec-11-nfpma-a-pr1 8/72; fpmp-11 single precision package; replaces:
> dec-11-yqpc-pb; (c)1971,72
> dec-11-nfpma-a-pr2 8/72; fpmp-11 double precision package; replaces:
> dec-11-yqpc-pb; (c)1971,72
> dec-11-nfpma-a-pa1 8/72; fpmp-11 source; tape 1 of 6; replaces:
> dec-11-yqpc-pa; (c)1971,72
> dec-11-nfpma-a-pa2 8/72; fpmp-11 source; tape 2 of 6; replaces:
> dec-11-yqpc-pa; (c)1971,72
> dec-11-nfpma-a-pa3 8/72; fpmp-11 source; tape 3 of 6; replaces:
> dec-11-yqpc-pa; (c)1971,72
> dec-11-nfpma-a-pa4 8/72; fpmp-11 source; tape 4 of 6; replaces:
> dec-11-yqpc-pa; (c)1971,72
> dec-11-nfpma-a-pa5 8/72; fpmp-11 source; tape 5 of 6; replaces:
> dec-11-yqpc-pa; (c)1971,72
> dec-11-nfpma-a-pa6 8/72; fpmp-11 source; tape 6 of 6; replaces:
> dec-11-yqpc-pa; (c)1971,72
>


I did download those. But I linked with the pre made single precision
package. Reading the manual more carefully reveal that there is not  the
complete FPMP-11 package in those pre made object files. So one have to
assemble ones own version by specifying exactly which modules to include in
a short file and then feed the six source file into PAL11-S. And voila a
tailor made version of FPMP-11 made for SPACE WAR is produced.

I then fed this object into LINK11-S followed by the 19 object files of
SPACE WAR. Finishing with the POINT module. And after doing this twice I
was greeted by a MODULE MAP and a 7323 byte absolute binary file!

* U

* E

LOAD MAP

TRANSFER ADDRESS: 01
LOW LIMIT: 025562
HIGH LIMIT: 037460
**
MODULE  FPMP11
SECTION ENTRY   ADDRESS SIZE
<. ABS.>00  00
<  >025562  000640
$ERR026364
$ERRA   026374
$ERVEC  026414
$ICI025570
$ICO026074
$OCI025562
$OCO026066
$POLSH  026360
$V20A   026360
**
MODULE  CHAR
SECTION ENTRY   ADDRESS SIZE
<  >026422  000246
CHAR026422
**
MODULE  CHRTAB
SECTION ENTRY   ADDRESS SIZE
<  >026670  000606
CHRTAB  026670
**
MODULE  COMPAR
SECTION ENTRY   ADDRESS SIZE
<  >027476  000444
COMPAR  027476
**
MODULE  EXPLOD
SECTION ENTRY   ADDRESS SIZE
<  >030142  000330
EXPLOD  030142
EXPREP  030260
EXPX030266
EXPY030270
**
MODULE  GRAVTY
SECTION ENTRY   ADDRESS SIZE
<  >030472  000450
GRAVTY  030472
**
MODULE  MULPLY
SECTION ENTRY   ADDRESS SIZE
<  >031142  000304
MULPLY  031142
**
MODULE  PARM
SECTION ENTRY   ADDRESS SIZE
<  >031446  001214
PARM031446
**
MODULE  PWRUP
SECTION ENTRY   ADDRESS SIZE
<  >032662  000106
**
MODULE  RESET
SECTION ENTRY   ADDRESS SIZE
<  >032770  000206
CENTER  04
ORBIT   000400
RESET   032770
RES01   033156
**
MODULE  RKT1
SECTION ENTRY   ADDRESS SIZE
<  >033176  000160
RKT1033176
**
MODULE  RKT2
SECTION ENTRY   ADDRESS SIZE
<  >033356  000142
RKT2033356
**
MODULE  SCORE
SECTION ENTRY   ADDRESS SIZE
<  >033520  000266
SCORE   033520
**
MODULE  SINCOS
SECTION ENTRY   ADDRESS SIZE
<  >034006  000462
SINCOS  034006
**
MODULE  SLINE
SECTION ENTRY   ADDRESS SIZE
<  >034470  000114
SLINE   034470
**
MODULE  SPCWAR
SECTION ENTRY   ADDRESS SIZE
<  >034604  000232
ADBR176772
ADCS176770
AMMO035022
ANGH1   034760
ANGH2   035006
ANGL1   034756
ANGL2   035004
ANGMID  000702
DAC0176750
DAC1176752
DAC2176754
FIRE001440
FLAG1   034736
FLAG2   034764
GAME1   035026
GAME2   035030
GRVFLG  035032
HIT1035010
HIT2035012
MASK002100
PTREP   035034
RKTSIZ  007000
SHOTS1  035014
SHOTS2  035016
SPCRST  034624
SPCWAR  034604
SUNSZ   004000
TSPEED  035024
WIN 035020
XDISP1  034754
XDISP2  035002
XSIZE1  034746
XSIZE2  034774
XVELH1  034752
XVELH2  035000
XVELL1  034750
XVELL2  034776
YDISP1  034744
YDISP2  034772
YSIZE1  034734
YSIZE2  034762
YVELH1  034742
YVELH2  034770
YVELL1  034740
YVELL2  034766
**
MODULE  SUN
SECTION ENTRY   ADDRESS SIZE
<  >035036  000304
SUN 035036
**
MODULE  UPDAT1
SECTION ENTRY   ADDRESS SIZE
<  >035342  000356
UPDAT1  035342
**
MODULE  UPDAT2
SECTION ENTRY   ADDRESS SIZE
<  > 

Re: PDP-11/45 RSTS/E boot problem

2019-01-03 Thread Fritz Mueller via cctalk
Hi Paul,

> On Jan 3, 2019, at 7:01 AM, Paul Koning  wrote:
> 
> I have a Monitor ODT manual from RSTS V4, I should find a way to make that 
> available.  It's pretty nearly standard ODT, there are a few extensions for 
> mapping addresses

Bitsavers has some docs for ODT from contemporaneous versions of RSX-11, which 
have seemed close enough to get me going with some experimentation.

> To find LOG$DK, you can either look in the link map (RSTS.MAP) from the 
> SYSGEN, or ask the init PATCH option to tell you

So, I don’t see a LOG$DK in my V06C RSTS.MAP (though I do have LOG$KB and 
LOG$TM).  PA returns “address above module bounds” when looking for it, which I 
assume means it searched without finding it.  Perhaps I missed a sysgen option 
for device logging or some such?  I’ll go back and take a look…

Thanks again for the help and tips!

  —-FritzM.




Re: PDP-11/45 RSTS/E boot problem

2019-01-03 Thread Paul Koning via cctalk



> On Jan 2, 2019, at 8:50 PM, Mueller, Fritz via cctalk  
> wrote:
> 
> 
> 
>> On Jan 2, 2019, at 4:40 PM, Paul Koning  wrote:
>> 
>> I'm pretty sure it was there for a long time.  It's under memory layout 
>> suboptions.  When it says "any memory layout changes" say yes, then when it 
>> asks what, say ODT.
> 
> Oh, I see, it's not listed as a valid sub option, but it is accepted when 
> typed.  It looks like I subsequently type “ODT” at the “Option:” prompt, 
> then?  And I suppose I get the value of “LOG$DK” for setting the breakpoint 
> from the listings generated when I sysgen?
> 
> I’ll go read up a bit on ODT...
> 
>   thanks,
> --FritzM.

I have a Monitor ODT manual from RSTS V4, I should find a way to make that 
available.  It's pretty nearly standard ODT, there are a few extensions for 
mapping addresses -- essentially a "software MMU".  But for the moment you 
should not need that.

Yes, ODT is an undocumented option.  Enter that and give the start address (for 
example "51K").  You can use the memory LIST option to see what is free.  Right 
after the kernel is a good spot.  It needs to be below 124K.  You may have XBUF 
in the way; if so move it first.

Once it's set, ODT will be loaded with RSTS at startup.  It will be entered on 
a crash, or if you enter control-P at the console.  That gives you a "BE" 
message ("breakpoint error") because entry is with the BPT instruction but 
there isn't an ODT breakpoint at that address.  

The ODT prompt is _ (underline) rather than *.  You can examine stuff or do all 
the usual ODT things, then enter P to proceed.

To find LOG$DK, you can either look in the link map (RSTS.MAP) from the SYSGEN, 
or ask the init PATCH option to tell you:

RSTS V7.0-07 V7dm (DM0)


Option: PA
File to patch? 
Module name? 
Base address? LOG$DK
Offset address? 0
 Base   Offset  Old New?
104030  00  016104  ? ^C

Those empty entries are Line Feed to accept the default.  This is a simple way 
to query the RSTS symbol table.

Re: music dec tapes? (paper)

2019-01-03 Thread Bill Degnan via cctalk
I have tapes with labels

8-152a 8 Music Coding Program Symbolic #1
8-152   8 Music Coding Program Symbolic #2
8-152   Teddy Bear's Picnic Symbolic
8-152a Penny Lane Symbolic
8-152 Joy to the World Symbolic
8-152 Your Mother Should Know Symbolic

8-152a Penny Lane 0037-7720, 0170=
 0171=, 0172=7750,
 0173=6020 Binary

8-152  When I'm 64
0037=720, 0170=7776
0172-7750

8-162   MUSIC FOR THE PDP-8
 Load Tunes: 440
 Play Tunes: 400

"Start 8 Music"  (hand-written, no printed label)

On Tue, Jan 1, 2019 at 9:03 PM Kyle Owen via cctalk 
wrote:

> On Tue, Jan 1, 2019, 15:18 Adrian Stoness via cctalk <
> cctalk@classiccmp.org
> wrote:
>
> > anyone seen these music tapes before i grabed  this trays for the oddnes
> of
> > the content of these tapes? also apears to have the software to play
> them?
> >
> >
> >
> https://www.ebay.ca/itm/Lot-of-15-digital-decus-Paper-Tapes-w-Case/273628629483?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2060353.m2749.l2649
> >
> >
> >
> https://www.ebay.ca/itm/Lot-of-8-digital-decus-Paper-Tapes-w-Case/273628539210?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2060353.m2749.l2649
> >
> > would this be some weird synthy type thing?
> > control points for the sound boaerd used for automation on some fancy
> desk?
> > or somthing els?
> >
>
> Vince has a listing for some version of DECUS 8-152 on his website (
>
> http://svn.so-much-stuff.com/svn/trunk/pdp8/src/decus/8-152/decus-8-152-lst.pdf
> ).
> I have reverse engineered it enough to have his version play a few songs.
> However, it seems like there's a difference between the music tapes I have
> and the listing he has.
>
> I don't know what hardware was required of this software, but I suspect it
> to be a DAC responding on address 055. This seems to match with an AA01
> option.
>
> Did you end up buying these tapes? I have digitized the music tapes I
> bought from the seller and will post them soon. It would be excellent if
> the buyer of this lot would do the same.
>
> Musically,
>
> Kyle
>
> >
>