• Please review our updated Terms and Rules here

Problems using tu58em with VAX-11/725 / VAX-11/730

Thanks and you're welcome in equal parts, tingo! I've certainly been inspired!

Diagnostics are running now. Turns out, the diagnostics required that CRDPACK.

My own fork (including Don's original code on the master branch) is up on GitHub:

https://github.com/NF6X/tu58em
 
All diagnostics pass! Still not booting VMS, but it's time to take a break... the computer room is getting too hot!

IMG_3321.jpg IMG_3322.jpg IMG_3323.jpg
 
Hello Mark,

congratulations on your progress with TU58 emulation. My question is if the diagnostics make use of MRSP.

As to TU58 response delays, I encountered, that RT11 requires interpacket delays about 1ms during read command and the initial delay after read command has been received must be more than 400ms. Although the RT11 system itself may run with 100ms, there are some problems with applications which are trying to reload another part from tape cartridge. I observed this behaviour with Balzers sputtering system which was written in Fortran. What I do not know is if VAX-11/725 (or 730) can accept these delays too. But my TU58 controller responds by most with longer delay (depends on tape position and the seek time) independently on protocol used.

Jiri
 
Thanks, Jiri!

I don't know for sure whether the diagnostics make use of MRSP, but I have had MRSP enabled in the emulator in all of my testing.

Thank you for sharing your experience regarding delays. I would expect that the VAX console code should be tolerant of any delays involving tape motion, so it would probably tolerate a 400ms delay after sending a read command. The specific delay that it appears to be very sensitive to is the turn-around time between sending two INIT flag chars (0x04) and receiving a CONTINUE response (0x10) from the drive. That doesn't require any tape motion, so the drive controller would probably easily respond quickly enough. I would imagine that RT11 systems could tolerate that quick response since they only need to digest one response character, and the drive doesn't send anything else until it receives a new command.

When I eventually make my own little embedded emulator, I guess I'll need to spend some time tuning configurable delays in order to see how fast I can get away with on some systems, how much I need to slow things down on others, and so forth.
 
Conversation about my VAX has mostly been on cctalk and Twitter recently, but I though I should update this thread:

With a new version 58 console tape image and my patched version of tu58em, I am now successfully booting up my VAX-11/730. It has OpenVMS 7.3 on the R80, and I have an RL02 pack with VMS 5.3 on it. I can boot either of them, and I've made magtape backups of both of them which I will hopefully be able to extract to my modern machines before too long. I obtained a new OpenVMS license pak through the hobbyist program, good for one year. Version 5.3 doesn't implement license termination dates, so it runs fine as-is.

Edit: Almost forgot to share this:

 
Hi Mark,

it's me again after a very long break ...

I now do have one of Jiris TU58 hardware emulators (and I try to do some testing for him), but my 11/725 fails nearly all microdiagnostics. Sometimes not even the MICMON (Mircrodiagnostic Monitor) starts :-(.

Do you have the Diagnostic Listings for the 11/725 resp. 11/730? I must make some more sense out of the error messages to get any further. And I'm afraid I will probably need another WCS and DAP board (which nearly makes the complete cpu).

Wish me luck!

Regards,

Ulli
 
I am not aware that I have any diagnostic listings, but I have not tried looking at that diagnostics RL02 pack under VMS yet. I'll try mounting it later today.
 
The CRDPACK disk is a FILES-11 volume. Here's what is on it:

Code:
$ mount /nowrite /over=id dqa1:
%MOUNT-I-MOUNTED, CRDPACK mounted on _PIKE$DQA1:
$ dir dqa1:[000000...]

Directory DQA1:[000000]

000000.DIR;1        100100.DIR;1        BACKUP.SYS;1        BADBLK.SYS;1
BADLOG.SYS;1        BITMAP.SYS;1        CONTIN.SYS;1        CORIMG.SYS;1
INDEXF.SYS;1        SYS0.DIR;1          SYSMAINT.DIR;1      VOLSET.SYS;1

Total of 12 files.

Directory DQA1:[100100]

SYMBOLS.DAT;2       SYMBOLS.DAT;1       SYMBOLS.DMP;2       SYMBOLS.DMP;1

Total of 4 files.

Directory DQA1:[SYS0]

SYS$LDR.DIR;1       SYSEXE.DIR;1

Total of 2 files.

Directory DQA1:[SYS0.SYS$LDR]

CPULOA.EXE;1        CVDRIVER.EXE;1      CWDRIVER.EXE;1      DBDRIVER.EXE;1
DDDRIVER.EXE;1      DKDRIVER.EXE;1      DLDRIVER.EXE;1      DMDRIVER.EXE;1
DQDRIVER.EXE;1      DRDRIVER.EXE;1      DUDRIVER.EXE;1      DVDRIVER.EXE;1
DYDRIVER.EXE;1      ERRORLOG.EXE;1      ESS$DADDRIVER.EXE;1 ESS$LASTDRIVER.EXE;1
ETDRIVER.EXE;1      EVENT_FLAGS_AND_ASTS.EXE;1              EXCEPTION.EXE;1
EXDRIVER.EXE;1      EXEC_INIT.EXE;1     FPEMUL.EXE;1        GDDRIVER.EXE;1
IMAGE_MANAGEMENT.EXE;1                  IO_ROUTINES.EXE;1   LCDRIVER.EXE;1
LIDRIVER.EXE;1      LOCKING.EXE;1       LOGICAL_NAMES.EXE;1 LPDRIVER.EXE;1
MESSAGE_ROUTINES.EXE;1                  MKDRIVER.EXE;1      PADRIVER.EXE;1
PAGE_MANAGEMENT.EXE;1                   PBDRIVER.EXE;1      PIDRIVER.EXE;1
PKIDRIVER.EXE;1     PKNDRIVER.EXE;1     PKSDRIVER.EXE;1     PKXDRIVER.EXE;1
PRIMITIVE_IO.EXE;1  PROCESS_MANAGEMENT.EXE;1                PUDRIVER.EXE;1
PWDRIVER.EXE;1      SECURITY.EXE;1      SYS$SCS.EXE;1       SYS.EXE;1
SYSDEVICE.EXE;1     SYSGETSYI.EXE;1     SYSLICENSE.EXE;1    SYSLOA1202.EXE;1
SYSLOA410.EXE;1     SYSLOA41D.EXE;1     SYSLOA41W.EXE;1     SYSLOA420.EXE;1
SYSLOA42D.EXE;1     SYSLOA42S.EXE;1     SYSLOA42W.EXE;1     SYSLOA43.EXE;1
SYSLOA43D.EXE;1     SYSLOA43S.EXE;1     SYSLOA43W.EXE;1     SYSLOA520.EXE;1
SYSLOA60.EXE;1      SYSLOA640.EXE;1     SYSLOA64D.EXE;1     SYSLOA650.EXE;1
SYSLOA65D.EXE;1     SYSLOA660.EXE;1     SYSLOA66D.EXE;1     SYSLOA670.EXE;1
SYSLOA67D.EXE;1     SYSLOA730.EXE;1     SYSLOA750.EXE;1     SYSLOA780.EXE;1
SYSLOA790.EXE;1     SYSLOA8NN.EXE;1     SYSLOA8PS.EXE;1     SYSLOA8SS.EXE;1
SYSLOA9AQ.EXE;1     SYSLOA9CC.EXE;1     SYSLOA9RR.EXE;1     SYSLOAUV1.EXE;1
SYSLOAUV2.EXE;1     SYSLOAWS1.EXE;1     SYSLOAWS2.EXE;1     SYSLOAWSD.EXE;1
SYSTEM_DEBUG.EXE;1  SYSTEM_PRIMITIVES.EXE;1                 SYSTEM_SYNCHRONIZATION_UNI.EXE;1
TFDRIVER.EXE;1      TMDRIVER.EXE;1      TSDRIVER.EXE;1      TTDRIVER.EXE;1
TUDRIVER.EXE;1      TVDRIVER.EXE;1      VAXEMUL.EXE;1       WORKING_SET_MANAGEMENT.EXE;1

Total of 98 files.

Directory DQA1:[SYS0.SYSEXE]

ISL_LVAX.SYS;1      STANDALON.EXE;1     STANDCONF.EXE;1     SYSBOOT.EXE;1
SYSINIT.EXE;1       VAXVMSSYS.PAR;1     VMB.EXE;2

Total of 7 files.

Directory DQA1:[SYSMAINT]

DIAGBOOT.EXE;1      DNDRIVER.EXE;1      DUCT.EXE;17         DVDRIVER.EXE;1
EBSAA.EXE;772       ECSAA.EXE;727       EMDRIVER.EXE;1      ENKAX.EXE;1
ENKAX.HLP;1         ENKAZ.EXE;1         ENLAA.SUP;1         ENRKA.EXE;1
ENRKA.HLP;1         ENSAA.DOC;1         ENSAA.EXE;1         ENSAB.EXE;1
ENSAB.HLP;1         ENWCA.BIN;1         ENWCA.EXE;1         ENWCA.HLP;1
EVAAA.EXE;1         EVAAA.HLP;1         EVAAB.EXE;1         EVAAB.HLP;1
EVABA.EXE;1         EVABA.HLP;1         EVALA.EXE;1         EVALA.HLP;1
EVALB.EXE;1         EVALC.EXE;1         EVALC.HLP;1         EVALD.EXE;1
EVALE.EXE;1         EVALF.EXE;1         EVCDA.EXE;1         EVCDA.HLP;1
EVCDB.;1            EVCDB.EXE;1         EVCDB.HLP;1         EVCDC.;1
EVCDC.EXE;1         EVCDC.HLP;1         EVCEA.EXE;1         EVCEA.HLP;1
EVDAA.EXE;1         EVDAA.HLP;1         EVDAB.EXE;1         EVDAB.HLP;1
EVDAC.EXE;1         EVDAC.HLP;1         EVDAD.EXE;1         EVDAD.HLP;1
EVDBB.EXE;1         EVDBB.HLP;1         EVDCA.EXE;1         EVDCA.HLP;1
EVDDA.;1            EVDDA.EXE;1         EVDDB.;1            EVDDB.EXE;1
EVDDB.HLP;1         EVDEA.EXE;1         EVDEA.HLP;1         EVDEB.EXE;1
EVDEB.HLP;1         EVDEC.EXE;1         EVDEC.HLP;1         EVDED.EXE;1
EVDED.HLP;1         EVDEE.EXE;1         EVDEE.HLP;1         EVDEF.EXE;1
EVDEF.HLP;1         EVDEG.EXE;1         EVDEG.HLP;1         EVDFI.EXE;1
EVDFI.HLP;1         EVDFJ.EXE;1         EVDFJ.HLP;1         EVDHA.EXE;1
EVDHA.HLP;1         EVDHB.EXE;1         EVDHB.HLP;1         EVDIA.;1
EVDIA.EXE;1         EVDIA.HLP;1         EVDIB.;1            EVDIB.EXE;1
EVDIB.HLP;1         EVDIE.EXE;1         EVDIE.HLP;1         EVDIG.EXE;1
EVDIG.HLP;1         EVDJA.EXE;1         EVDJA.HLP;1         EVDKA.EXE;1
EVDKA.HLP;1         EVDLA.EXE;1         EVDLA.HLP;1         EVDLB.EXE;1
EVDLB.HLP;1         EVDLC.EXE;1         EVDLC.HLP;1         EVDLD.EXE;1
EVDLD.HLP;1         EVDLF.EXE;1         EVDLF.HLP;1         EVDMB.EXE;1
EVDMB.HLP;1         EVDMC.EXE;1         EVDMC.HLP;1         EVDMD.EXE;1
EVDMD.HLP;1         EVDNA.EXE;1         EVDNA.HLP;1         EVDNB.EXE;1
EVDNB.HLP;1         EVDPC.EXE;1         EVDPC.HLP;1         EVDPD.EXE;1
EVDPD.HLP;1         EVDPE.EXE;1         EVDPE.HLP;1         EVDRB.EXE;1
EVDRB.HLP;1         EVDRE.EXE;1         EVDRE.HLP;1         EVDRF.COM;1
EVDRF.EXE;1         EVDRF.HLP;1         EVDRG.;1            EVDRG.EXE;1
EVDRG.HLP;1         EVDSA.;1            EVDSA.EXE;1         EVDSA.HLP;1
EVDTA.EXE;1         EVDTA.HLP;1         EVDTA.MIC;1         EVDTB.EXE;1
EVDTB.HLP;1         EVDTB.MIC;1         EVDUP.EXE;1         EVDUQ.EXE;1
EVDUQ.HLP;1         EVDWA.EXE;1         EVDWA.HLP;1         EVDWB.EXE;1
EVDWB.HLP;1         EVDWC.EXE;1         EVDWC.HLP;1         EVDXA.EXE;1
EVKAA.EXE;1         EVKAB.EXE;1         EVKAB.HLP;1         EVKAC.EXE;1
EVKAC.HLP;1         EVKAD.EXE;1         EVKAD.HLP;1         EVKAE.EXE;1
EVKAE.HLP;1         EVKAM.EXE;1         EVKAM.HLP;1         EVLBA.SUP;1
EVMAA.EXE;1         EVMAA.HLP;1         EVMAD.EXE;1         EVMBD.EXE;1
EVMBD.HLP;1         EVMBE.EXE;1         EVMBE.HLP;1         EVNDX.SEQ;1
EVQBL.EXE;1         EVQDD.EXE;1         EVQDL.EXE;1         EVQDM.EXE;1
EVQDN.EXE;1         EVQDQ.EXE;1         EVQDV.EXE;1         EVQDY.EXE;1
EVQEM.EXE;1         EVQIB.EXE;1         EVQIE.EXE;1         EVQKM.EXE;1
EVQOA.EXE;1         EVQOB.EXE;1         EVQSB.EXE;1         EVQTS.EXE;1
EVQUE.EXE;1         EVQVS.EXE;1         EVQXA.EXE;1         EVQXC.EXE;1
EVQXD.EXE;1         EVQXM.EXE;1         EVRAA.EXE;1         EVRAC.EXE;15
EVRAC.EXE;1         EVRAC.HLP;16        EVRAD.EXE;1         EVRAD.HLP;1
EVREA.EXE;1         EVREB.EXE;1         EVREC.EXE;1         EVRED.EXE;1
EVREE.EXE;1         EVREF.EXE;1         EVREG.EXE;1         EVRFA.EXE;1
EVRGA.EXE;1         EVRGA.HLP;1         EVRIA.EXE;1         EVRJA.EXE;1
EVRJA.HLP;1         EVRJB.EXE;1         EVRJB.HLP;1         EVRLA.DAT;1
EVRLA.EXE;1         EVRLA.HLP;1         EVRLB.EXE;1         EVRLB.HLP;1
EVRMA.EXE;1         EVRMA.HLP;1         EVRMB.EXE;1         EVRMB.HLP;1
EVRMB.USD;1         EVRMC.EXE;1         EVRMC.HLP;1         EVRMD.EXE;1
EVRMD.HLP;1         EVSAA.HLP;1         EVSBA.EXE;1         EVSBA.HLP;1
EVSCA.COM;1         EVSCA.HLB;1         EVSCA.OLB;1         EVSCAD.BIN;1
EVSCAI.BIN;1        EVSCAM.BIN;1        EVTAA.EXE;1         EVTAA.HLP;1
EVTBA.EXE;1         EVTBA.HLP;1         EVTCA.EXE;1         EVTCA.HLP;1
EVTCB.EXE;1         EVTDA.EXE;1         EVTDA.HLP;1         EVWAA.BIN;1
EVWAA.EXE;1         EVWAA.HLP;1         EVWAB.EXE;1         EVWAB.HLP;1
EVXBA.EXE;1         EVXBB.COM;1         EVXBB.EXE;1         EVXBB.HLP;1
RCDRIVER.EXE;1      RCLOAD.COM;1        TTDRIVER.DIA;1      UETML1100.EXE;1
UKDRIVER.EXE;1      UKLOAD.COM;1        VBDRIVER.EXE;1      VMB.EXE;2
VSDP.COM;1          VSDRIVER.EXE;1      VSLOAD.COM;1        XDDRIVER.EXE;1
XPDRIVER.EXE;1      XPLOAD.COM;1        YODRIVER.EXE;1      YOLOAD.COM;1
YYDRIVER.EXE;1

Total of 273 files.

Grand total of 6 directories, 396 files.

I looked at the first of the .HLP files to see what is in it:

Code:
$ type dqa1:[sysmaint]enkax.hlp
1 ATTACH
 The CPU must be attached with the following command:

        DS> ATTACH KA730 PHAD KA0 toy wcsla fpa msiz uswcs sbe

 where:
        toy   is time-of-year clock? <YES or NO>
        wcsla is WCS last address? <hex address>
        fpa   is Floating Point Accelerator Type? <hex type>
        msiz  is the size of memory in kbytes? <decimal size>
        uswcs is user WCS loaded? <YES or NO>
        sbe   is single-bit memory error reporting? <YES or NO>

 If UBE's are installed they are attached with the following
 command:

        DS> ATTACH UBE DWn UBx 77yyyy zzz

 where n is the Adapter Number, x is any arbitrary unit number,
 yyyy is the CSR of the device, and zzz is the vector of the
 device.  Type HELP ATTACH UBE for more information.

 If testing of the TU58 Console Load Device is desired they should
 be attached as follows:

        DS> ATTACH TU58 PHAD DDAn

 where n is the drive number to be tested (0 or 1).  Both drives
 may be attached using two separate attach commands.

2 UBE
 Valid UBE CSR's are: 770006, 770026, 770046, 770066.
 Valid UBE Vector's are: 510, 514, 520, 524.
1 HELP
 This program tests portions of the VAX 11/730 CPU cluster
 hardware which are not specified by the VAX architecture, or
 which require manual intervention.  This program must run
 in a standalone environment under control of the Diagnostic
 Supervisor.

 Tests 8 and 9 will only be executed if a Unibus Exerciser (UBE)
 has been attached and selected.  Type HELP ENKAX ATTACH for attach
 details.
1 SECTIONS
 By default, all tests are run except the manual intervention tests,
 which are tests 2, 3, and 4.
2 TU58
 Runs tests 6 and 7, which exercise the TU58 tape controller to
 assure basic functionality.  The drive(s) to be tested must be
 attached and selected.  A scratch tape must be loaded in the drive(s)
 for test 7 to execute.
2 POWER
 Runs test 2, which tests that the power failure and recovery
 mechanism functions properly.
2 HALT
 Runs tests 3 and 4, which check the various ways the processor can
 be halted, in both architecturally defined and undefined manners.
2 MCHK
 Runs test 5, which tests some of the possible ways in which a
 machine check exception may occcur.
2 WCS
 Not Implemented
2 MEM
 Runs test 10, which does a quick test of main memory.
2 UBI
 Runs tests 8 and 9, which test the Unibus Interface.
2 IPR
 Runs test 1, which tests that all processor register numbers
 not implemented on the VAX-11/730 will cause a reserved
 operand fault for a MTPR or MFPR instruction and that all read-only
 or write-only processor registers will cause a reserved operand
 fault when the wrong type access is attempted and respond proplerly
 when the correct access is attempted.
2 LDPCTX
 Runs test 11, which tests the reserved operand abort checks made
 made by the processor during a LDPCTX instruction operation.
1 DEVICE
 The diagnostic supports the following devices:

   The VAX-11/730 CPU (KA730)
   Up to 4 UBE's (Unibus Exercisers)
   Dual TU58 drive (KA730 Console Load Device)

1 EVENT
 On Test 7 (TU58) ,if event flag 3 set will override protection, i.e.,
 go ahead and write on tape.

 If run under APT and event flag 3 is clear snd tape is not scratch
 report an error.
1 QUICK
 On Test 7(TU58), if quick flag is set will skip subtest 4 through 11.
1 SUMMARY
 Not Implemented
1 MANUAL
 Manual test sections include tests 2, 3, and 4.  Test 2 is Power
 Fail test, and it requires the operator to turn the keyswitch to
 the Standby position.  Tests 3 and 4 are Halt tests, and require
 the operator to type >>> D/G F 100 <CR>, then >>> C <CR> to
 continue to testing after the machine has halted at various times.

So, I don't think I have the diagnostic listings in question; just the diagnostics themselves. I'll dump that CRDPACK disk when I have a way to do that, but I'm not there quite yet.
 
Thanks a lot for looking at your CRD (Customer Runnable Diagnostics) Pack. Would be very helpful for me (and of course others) to have an image of it available. I can image RL02s, but sending the pack to me savely (I live in Germany) would be to complicated I think. But wait - you can read the RL02 under VMS - then you can image it; it's easy with VMS:

MOUNT/FOREIGN (device name of your RL02)
COPY/LOG (device name of your RL02) CRD.IMG
DISMOUNT (device name of your RL02)

If you get an error message at the end of the COPY, don't mind - it's o.k.

That's all, now you have your disk image in file CRD.IMG! All that's left is to transfer that image file to your PC (or MAC or whatever). I usually use UCX (TCP/IP for VAXen) or DECnet-Linux (on the PC side) to exchange files between my VAXen and my PC.

Yes, there are no diagnostic listings on the CRD (they were distributed on microfiche only), but the HELP files would be a very good start.

The image would be really great, thanks a lot in advance!

Regards

Ulli
 
I do plan to image that pack and include the image with the matching TU58 diagnostic tape image that I've already shared on GitHub. I just haven't worked out a way to get images on/off my VAX yet, but it shouldn't be too much longer before I get to that stage. I haven't gotten networking up and running yet.
 
TU-58 and VAX-11/730 console info

TU-58 and VAX-11/730 console info

Hi! Just found this forum. I am the author of the VAX-11/730 console firmware, which I wrote a long, long time ago.

If anyone cares I can post some info that may be of interest about the console, the console firmware, and the TU-58.

John M.
 
Hi! Just found this forum. I am the author of the VAX-11/730 console firmware, which I wrote a long, long time ago.

If anyone cares I can post some info that may be of interest about the console, the console firmware, and the TU-58.

John M.

WOW!! I would LOVE to hear anything about that! Thank you for finding this forum and introducing yourself!

If you have any notes, documents, etc. on the topic that you are willing and able and allowed to share, I'm sure that the Bitsavers folks and Archive.org would both love to preserve them for posterity.
 
Hi All;

JMiddleton, Welcome to the Forum!!
I would Agree with NF6X, and add that the rest of Us would Love to have Anything that You are able to Share, here on the Forum, as well.. And yes on BitSavers as well..

THANK YOU Marty
 
Last edited:
Hi! Just found this forum. I am the author of the VAX-11/730 console firmware, which I wrote a long, long time ago.

If anyone cares I can post some info that may be of interest about the console, the console firmware, and the TU-58.

John M.

Hello John Middleton ... been a while (like 35 yrs or so)! Hope you are well. Any info on the subject would be greatly appreciated.

Don North
ex-DEC 1975-1982
ex-APPLE 1982-1997
ex-CISCO 1997-2014

Proud owner of an 11/34, 11/44, a couple of PDP-8m, all restored and working, and author of the TU58EM emulator.
 
Last edited:
Hello Don North. I remember your name but not whether I actually knew you back at DEC. Where did you work and what did you work on?

ex-DEC 1973-1996
ex-PictureTel 1996-1999
ex-Axent Corp. 1999-2001
ex-Symantec Corp. 2001-2006
ex-retired 2006-2011
ex-F4W 2011-2013 (contract, Android)
ex-Silent Circle 2013-2013 (contract, a very short Android project)
retired again 2013-now

Toward the end of my time at DEC I went strictly PC and all the software I worked on from then on was for the PC. From 1999 on it was all Java, and the contract jobs were Android/Java.

I do miss the DEC stuff (the first computer I worked on was a PDP-11/20, and my first computer language was PDP-11 machine language followed by the PAL-11 assembler), but we live in a high-rise condo and don't have the room or the power.

I am currently creating a document for this forum about the VAX-11/730 console and the TU-58. Unfortunately all I have is my memories, no actual documentation. If anyone out there finds a source code listing I'd love a copy.
 
Last edited:
Hello Don North. I remember your name but not whether I actually knew you back at DEC. Where did you work and what did you work on?

ex-DEC 1973-1996
ex-PictureTel 1996-1999
ex-Axent Corp. 1999-2001
ex-Symantec Corp. 2001-2006
ex-retired 2006-2011
ex-F4W 2011-2013 (contract, Android)
ex-Silent Circle 2013-2013 (contract, a very short Android project)
retired again 2013-now

Toward the end of my time at DEC I went strictly PC and all the software I worked on from then on was for the PC. From 1999 on it was all Java, and the contract jobs were Android/Java.

I do miss the DEC stuff (the first computer I worked on was a PDP-11/20, and my first computer language was PDP-11 machine language followed by the PAL-11 assembler), but we live in a high-rise condo and don't have the room or the power.

I am currently creating a document for this forum about the VAX-11/730 console and the TU-58. Unfortunately all I have is my memories, no actual documentation. If anyone out there finds a source code listing I'd love a copy.

Tried to send you a PM, does not work. Either you need to enable private messages or maybe your account is too new.

In any event, I'll keep it short. Worked on 11/60 diagnostics (floating point FP11-E and the microcode diagnostic DCS module). Then worked on the 11/74 commercial instruction set CISP processor microcode. Lastly moved into the graphics research advanced development group, SuVAX project.

Don
 
Don,

OK, now I remember. I was part of the debug team for the 11/60 microcode and hardware (3rd shift for 3 months, then 2nd shift for about 9 months) on 5-5, then 11/74 CIS hardware on 3-4 (I think, or maybe 3-5), then moved up to Tewksbury to work on same until it was cancelled. After that I transitioned from being technician to software when I took the job writing the VAX-11/730 console code.

I've just been looking through my profile and settings to see how to enable private messages but didn't see anything. Is it something I have to enable?

Thanks,

John
 
Back
Top