subject:"\[Simh\] Largest VAX \/ PDP disk sizes"

Re: [Simh] Largest VAX / PDP disk sizes

2010-03-27 Thread Jason Stevens

Ok, I replaced the 'ra72' with my guessed 'ra73'  I just mounted the
miniroot on a rq1 (as a ra81 it doesn't matter)


% cat x.ini
set rq0 ra73
att rq0 ra73.disk
set rq1 ra81
att rq1 mini
set rq2 dis
set rq3 dis
% ./vax x.ini

VAX simulator V3.8-1
sim> show rq
RQ, address=20001468-2000146B*, no vector, 2 units
  RQ0, 2007MB, attached to ra73.disk, write enabled, RA73
  RQ1, 456MB, attached to mini, write enabled, RA81
sim> boot cpu
Loading boot code from ka655x.bin


KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>show dev
UQSSP Disk Controller 0 (772150)
-DUA0 (RA73)
-DUA1 (RA81)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)
-MUA1 (TK50)
-MUA2 (TK50)
-MUA3 (TK50)

RLV12 Controller 0 (774400)
-DLA0 (RL01)
-DLA1 (RL01)
-DLA2 (RL01)
-DLA3 (RL01)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-AA-BB-CC)
>>>boot dua1:
(BOOT/R5:0 DUA1



  2..
-DUA1
  1..0..


>> NetBSD/vax boot [1.11 Sat Feb  6 22:37:47 UTC 2010] <<
>> Press any key to abort autoboot 0
getdisklabel: no disk label
nfs_open: must mount first.
open netbsd.vax: Device not configured
> boot netbsd
getdisklabel: no disk label
2388172+308476 [193664+183590]=0x2eea9c
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009
The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.

NetBSD 5.0.2 (GENERIC) #0: Sat Feb  6 22:45:58 UTC 2010
bui...@b8.netbsd.org:
/home/builds/ab/netbsd-5-0-2-RELEASE/vax/2010020618
51Z-obj/home/builds/ab/netbsd-5-0-2-RELEASE/src/sys/arch/vax/compile/GENERIC
MicroVAX 3800/3900
total memory = 16328 KB
avail memory = 12480 KB
mainbus0 (root)
cpu0 at mainbus0: KA655, CVAX microcode rev 6 Firmware rev 83
lance at mainbus0 not configured
uba0 at mainbus0: Q22
dz1 at uba0 csr 160100 vec 304 ipl 17
mtc0 at uba0 csr 174500 vec 774 ipl 17
mscpbus0 at mtc0: version 5 model 3
mscpbus0: DMA burst size set to 4
mt0 at mscpbus0 drive 0: TK50
mt1 at mscpbus0 drive 1: TK50
mt2 at mscpbus0 drive 2: TK50
mt3 at mscpbus0 drive 3: TK50
uda0 at uba0 csr 172150 vec 770 ipl 17
mscpbus1 at uda0: version 3 model 3
mscpbus1: DMA burst size set to 4
ra0 at mscpbus1 drive 0: RA73
ra1 at mscpbus1 drive 1: RA81
qe0 at uba0 csr 174440 vec 764 ipl 17: delqa, hardware address
08:00:2b:aa:bb:cc

rlc0 at uba0 csr 174400 vec 160 ipl 17
rl0 at rlc0 drive 0: RL01, drive not loaded
rl1 at rlc0 drive 1: RL01, drive not loaded
rl2 at rlc0 drive 2: RL01, drive not loaded
rl3 at rlc0 drive 3: RL01, drive not loaded
ts0 at uba0 csr 172520 vec 224 ipl 17: TS11
ts0: rev 0, extended features enabled, transport offline
Kernelized RAIDframe activated
ra0: size 3920490 sectors
ra1label: 0
: no disk label: size 891072 sectors
boot device: ra1
root on ra1a dumps on ra1b
root file system type: ffs
WARNING: clock gained 47 days
WARNING: CHECK AND RESET THE DATE!
erase ^H, werase ^W, kill ^U, intr ^C
Terminal type? [sun]

(bla bla me breaking the install shell)


# dd if=zero bs=524288 of=rra0c
dd: rra0c: short write on character device
dd: rra0c: end of device
3829+0 records in
3828+1 records out
2007290880 bytes transferred in 96.270 secs (20850637 bytes/sec)

And on my native machine (x64 windows)...


03/27/2010  03:01 PM  .
03/27/2010  03:01 PM  ..
03/27/2010  02:43 PM   131,072 ka655x.bin
03/27/2010  03:01 PM 7,340,032 mini
03/27/2010  02:46 PM 2,825,091 miniroot-netbsd-vax.fs.gz
03/27/2010  04:51 PM 2,007,289,856 ra73.disk
03/27/2010  02:57 PM   846,724 vax
03/27/2010  03:01 PM81 x.ini
   6 File(s)  2,018,432,856 bytes
   2 Dir(s)  641,506,033,664 bytes free

this would be about right, right?

Also disklabel on NetBSD said this about making a disklabel

disk: RA73
label:
flags:
bytes/sector: 512
sectors/track: 70
tracks/cylinder: 21
sectors/cylinder: 1470
cylinders: 2667
total sectors: 3920490
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 1   # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0

Oh well FWIW it seems easy enough to stomp an existing drive, and
rebuilding...
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

Re: [Simh] Largest VAX / PDP disk sizes

2010-03-27 Thread Jason Stevens

Well I slapped together this...

#define RA73_DTYPE  16
#define RA73_SECT   70
#define RA73_SURF   21
#define RA73_CYL3000
#define RA73_TPGRA73_SURF
#define RA73_GPC1
#define RA73_XBN2980
#define RA73_DBN2980
#define RA73_LBN3920490
#define RA73_RCTS   2980
#define RA73_RCTC   1
#define RA73_RBN63000
#define RA73_MOD40
#define RA73_MED0x25641049
#define RA73_FLGS   RQDF_SDI

I slapped it together but it's coming up as an RX50 for some reason..  I
have to run out, but I think I'll just stomp on top of the RA72 and see how
that goes

I'm also assuming the latest NetBSD will support the ra73.

% cat x.ini
set rq0 ra73
att rq0 ra73.disk


VAX simulator V3.8-1
sim> show rq0
RQ0, 2007MB, attached to ra73.disk, write enabled, RX50
sim> boot cpu
Loading boot code from ka655x.bin


KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>show dev
UQSSP Disk Controller 0 (772150)
-DUA0 (RX50)
-DUA1 (RD54)
-DUA2 (RD54)
-DUA3 (RX50)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)
-MUA1 (TK50)
-MUA2 (TK50)
-MUA3 (TK50)

RLV12 Controller 0 (774400)
-DLA0 (RL01)
-DLA1 (RL01)
-DLA2 (RL01)
-DLA3 (RL01)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-AA-BB-CC)
>>>boot dua0:
(BOOT/R5:0 DUA0



  2..
-DUA0
  1..0..


>> NetBSD/vax boot [1.11 Sat Feb  6 22:37:47 UTC 2010] <<
>> Press any key to abort autoboot 0
getdisklabel: no disk label
nfs_open: must mount first.
open netbsd.vax: Device not configured
> boot netbsd
getdisklabel: no disk label
2388172+308476 [193664+183590]=0x2eea9c
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009
The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.

NetBSD 5.0.2 (GENERIC) #0: Sat Feb  6 22:45:58 UTC 2010
bui...@b8.netbsd.org:
/home/builds/ab/netbsd-5-0-2-RELEASE/vax/2010020618
51Z-obj/home/builds/ab/netbsd-5-0-2-RELEASE/src/sys/arch/vax/compile/GENERIC
MicroVAX 3800/3900
total memory = 16328 KB
avail memory = 12480 KB
mainbus0 (root)
cpu0 at mainbus0: KA655, CVAX microcode rev 6 Firmware rev 83
lance at mainbus0 not configured
uba0 at mainbus0: Q22
dz1 at uba0 csr 160100 vec 304 ipl 17
mtc0 at uba0 csr 174500 vec 774 ipl 17
mscpbus0 at mtc0: version 5 model 3
mscpbus0: DMA burst size set to 4
mt0 at mscpbus0 drive 0: TK50
mt1 at mscpbus0 drive 1: TK50
mt2 at mscpbus0 drive 2: TK50
mt3 at mscpbus0 drive 3: TK50
uda0 at uba0 csr 172150 vec 770 ipl 17
mscpbus1 at uda0: version 3 model 3
mscpbus1: DMA burst size set to 4
rx0 at mscpbus1 drive 0: RX50
ra0 at mscpbus1 drive 1: RD54
ra1 at mscpbus1 drive 2: RD54
rx1 at mscpbus1 drive 3: RX50
qe0 at uba0 csr 174440 vec 764 ipl 17: delqa, hardware address
08:00:2b:aa:bb:cc

rlc0 at uba0 csr 174400 vec 160 ipl 17
rl0 at rlc0 drive 0: RL01, drive not loaded
rl1 at rlc0 drive 1: RL01, drive not loaded
rl2 at rlc0 drive 2: RL01, drive not loaded
rl3 at rlc0 drive 3: RL01, drive not loaded
ts0 at uba0 csr 172520 vec 224 ipl 17: TS11
ts0: rev 0, extended features enabled, transport offline
Kernelized RAIDframe activated
ra0: attempt to bring on line failed:  unit offline (not mounted) (code 3,
subcode 1)
ra1: attempt to bring on line failed:  unit offline (not mounted) (code 3,
subcode 1)
rx1: attempt to bring on line failed:  unit offline (not mounted) (code 3,
subcode 1)
boot device: 
root device: ra0*
dump device (default ra0b):
file system (default generic):
root on ra0b dumps on ra0b
ra0: attempt to bring on line failed:  unit offline (not mounted) (code 3,
subcode 1)
ra0: attempt to bring on line failed:  unit offline (not mounted) (code 3,
subcode 1)
vfs_mountroot: can't open root device
cannot mount root, error = 6
root device (default ra0b): rx0*
dump device (default rx0b):
file system (default generic):
root on rx0b dumps on rx0b
panic: Segv in kernel mode: pc 88d3 addr 1
Stopped in pid 0.1 (system) at  netbsd:upcallret:   function
"upcallret()",
e
ntry-mask 0x7c0
remqhi  *0x4ac(r0), r6
db>



On Sat, Mar 27, 2010 at 1:56 PM, Tim Shoppa wrote:

> Jason Stevens  wrote:
> > Hmm what is weird is that when I look at the disktab from any BSD and
> > compare it to the table in pdp11_rq.c they don't agree
>
> Doesn't matter for MSCP disks. They're "just a bunch of blocks" and
> accessed by block number.
>
> Unless the device driver has to do host-side bad block replacement, which
> you do not want to get into, and do not have to get into in the
> emulator world!
>
> > While looking up the RP06 I find this:
> >
> > pdp11_rp.c
> >
> > #define RP06_DTYPE  3
> > #define RP06_SECT   22
> > #define RP06_SURF   19
> > #define RP06_CYL815
> > #define RP06_DEV0200

Re: [Simh] Largest VAX / PDP disk sizes

2010-03-27 Thread Tim Shoppa

Jason Stevens  wrote:
> Hmm what is weird is that when I look at the disktab from any BSD and
> compare it to the table in pdp11_rq.c they don't agree

Doesn't matter for MSCP disks. They're "just a bunch of blocks" and
accessed by block number.

Unless the device driver has to do host-side bad block replacement, which
you do not want to get into, and do not have to get into in the
emulator world!

> While looking up the RP06 I find this:
>
> pdp11_rp.c
>
> #define RP06_DTYPE  3
> #define RP06_SECT   22
> #define RP06_SURF   19
> #define RP06_CYL815
> #define RP06_DEV020022
> #define RP06_SIZE   (RP06_SECT * RP06_SURF * RP06_CYL * RP_NUMWD)
>
> and in the disktab:
>
> rp06|RP06|DEC RP06:\
>   :ty=removable:ns#22:nt#19:nc#815:\
>
> Which do agree

For SMD/Massbus drives, the physical geometry does matter to the driver.
I/O requests are issued based on physical track/cylinder/sector.

Tim.
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

Re: [Simh] Largest VAX / PDP disk sizes

2010-03-27 Thread Jason Stevens

Hmm what is weird is that when I look at the disktab from any BSD and
compare it to the table in pdp11_rq.c they don't agree

Take something like the RA60

in pdp11_rq we have:


#define RA60_DTYPE  13  /* SDI drive */
#define RA60_SECT   42  /* +1 spare/track */
#define RA60_SURF   6
#define RA60_CYL1600/* 0-1587 user */
#define RA60_TPGRA60_SURF
#define RA60_GPC1
#define RA60_XBN1032/* cyl 1592-1595 */
#define RA60_DBN1032/* cyl 1596-1599 */
#define RA60_LBN400176  /* 42*6*1588 */
#define RA60_RCTS   1008/* cyl 1588-1591 */
#define RA60_RCTC   1
#define RA60_RBN9528/* 1 *6*1588 */
#define RA60_MOD4
#define RA60_MED0x22A4103C
#define RA60_FLGS   (RQDF_RMV | RQDF_SDI)

and in Ultrix...

ra60|RA60|DEC RA60 Removable:\
:ty=removable:ns#42:nt#4:nc#2382:\

it specifies 2382 cylinders...  Although they both agree to 42 sectors..

Looking at the ra80:

ra81|RA81|DEC RA81 Winchester:\
:ty=winchester:ns#51:nt#14:nc#1248:\

  type sec surfcyl tpg gpc RCT LBNs
  RA81 51(+1)  14  125814  1   2856891072

Which is 'closer'


While looking up the RP06 I find this:

pdp11_rp.c

#define RP06_DTYPE  3
#define RP06_SECT   22
#define RP06_SURF   19
#define RP06_CYL815
#define RP06_DEV020022
#define RP06_SIZE   (RP06_SECT * RP06_SURF * RP06_CYL * RP_NUMWD)

and in the disktab:

rp06|RP06|DEC RP06:\
:ty=removable:ns#22:nt#19:nc#815:\

Which do agree


I suspect I'm missing a *LOT* when it comes to how these are mapping...?


FWIW they list a ra73 disktab here:

ra73|RA73|DEC RA73 Winchester:\
:ty=winchester:ns#70:nt#21:nc#2667:\
:pa#32768:ba#8192:fa#1024:\
:pb#190464:bb#4096:fb#1024:\
:pc#3920490:bc#8192:fc#1024:\
:pd#536260:bd#8192:fd#1024:\
:pe#536260:be#8192:fe#1024:\
:pf#536262:bf#8192:ff#1024:\
:pg#2088476:bg#8192:fg#1024:\
:ph#1608782:bh#8192:fh#1024:


I don't know if you could even trust it's 70 sectors, 21 tracks, 2667 cylinders.


On a whim google pulls this:

http://groups.google.com/group/comp.sys.dec/browse_thread/thread/1db2c05e66a47320/efa324f0ce533455?hl=en&ie=UTF-8&q="RA73"#efa324f0ce533455



it's some usenet thing from 2001... I suppose you could email everyone
in the thread asking if they still have an ra73, and if they can find
the geometry...?



On Sat, Mar 27, 2010 at 12:09 AM, Bruce Claremont <
bruce.clarem...@migrationspecialties.com> wrote:

>  Take a look at the RAUSER option.  That should resolve your drive size
> issues.
>
>
> At 09:40 AM 3/26/2010, Armistead, Jason wrote:
>
> Content-class: urn:content-classes:message
> Content-Type: multipart/alternative;
>  boundary="_=_NextPart_001_01CACCFA.B37AC702"
>
> According to
>
> * http://simh.trailing-edge.com/vax.html
> *
> and
>
> * http://simh.trailing-edge.com/pdp11.html
> *
> Both mention the RA73, which is a 2Gb drive (that I’d really love to use
> with SIMH !)
>
> I am trying to run the MicroVAX 3900 flavor of SIMH, but when I try to put SET
> RQ2 RA73 in my VAX.INI file I get an error
>
> parameter
>
> vax.ini> set rq2 ra73
>
> Non-existent parameter
>
> And I end up with a 159 Mb RD54 drive instead when I boot VMS and do a SHOW
> DEVICE DUA2: /FULL
>
> According to both the VAX and PDP11 pages on the SIMH site, the RA73 is
> listed as supported, but when I dig into the SIMH source code and look at
> PDP11_RQ.C, in the it has an X next to it which means not implemented.
>
> What’s this all mean ?
>
> Is it just a documentation bug, and those web pages shouldn’t mention
> RA73s ?
>
> Is there a technical/software reason why SIMH doesn’t support these drives
> ?
>
> Is no-one able to fill in the question marks in the RCT column of the table
> in PDP11_RQ.C which also has blanks for RD32, RD33 and RA70 drives ?  I
> managed to figure out that RCT stands for replacement and caching table (a
> reference in the VMS I/O User’s Reference Manual to DEV$M_RCT).  We ought to
> strive to improve the comments in the code to expand this (I found no
>
> On a side-note, the PDP11 web page shows the capacities of these drives as
> a range.  The VAX page lists the capacities as 12KB for VAX 780 and
> 200-1960MB for VAX 3900.  The 12KB entry for VAX 780 seems like a typo
> perhaps.
>
> Regards,
>
> Jason
> ___
> Simh mailing list
> Simh@trailing-edge.com
>  http://mailman.trailing-edge.com/mailman/listinfo/simh
>
>
> Mr. Bruce Claremont, Software Preservationist
> Migration Spec

Re: [Simh] Largest VAX / PDP disk sizes

2010-03-27 Thread Bruce Claremont



Take a look at the RAUSER option.  That should resolve your drive
size issues.

At 09:40 AM 3/26/2010, Armistead, Jason wrote:
Content-class:
urn:content-classes:message
Content-Type: multipart/alternative;

boundary="_=_NextPart_001_01CACCFA.B37AC702"
According to 



http://simh.trailing-edge.com/vax.html

and



http://simh.trailing-edge.com/pdp11.html

Both mention the RA73, which is a
2Gb drive (that Id really
love to use with SIMH !)

I am trying to run the MicroVAX 3900
flavor of SIMH, but when I
try to put
SET RQ2 RA73 in my VAX.INI file I
get an error

parameter

vax.ini> set rq2 ra73

Non-existent
parameter

And I end up with a 159 Mb RD54
drive instead when I boot VMS and do a SHOW DEVICE DUA2: /FULL

According to both the VAX and PDP11
pages on the SIMH site, the RA73 is listed as supported, but when I dig
into the SIMH source code and look at PDP11_RQ.C,
in the
it has an X next to it which means
not implemented.

Whats this all mean ?

Is it
just
a documentation bug, and those web
pages shouldnt mention RA73s ?

Is there a technical/software reason
why SIMH doesnt
support these drives ?  

Is no-one able to fill in the
question marks in the
RCT column of the
table in PDP11_RQ.C which also has
blanks for RD32, RD33 and RA70 drives ?  I managed to figure out
that RCT stands for replacement and caching table
(a reference in the VMS I/O Users
Reference Manual to DEV$M_RCT).  We ought to strive to improve the
comments in the code to expand this (I found no 
On a side-note, the PDP11 web page
shows the capacities of these drives as a range.  The VAX
page lists the capacities as
12KB for VAX 780 and 200-1960MB for VAX 3900.  The 12KB entry for
VAX 780 seems like a typo perhaps.

Regards,

Jason
___
Simh mailing list
Simh@trailing-edge.com

http://mailman.trailing-edge.com/mailman/listinfo/simh


Mr. Bruce Claremont, Software Preservationist
Migration Specialties International, Inc.
217 West 2nd Street, Florence, CO   81226-1403
bruce.clarem...@migrationspecialties.com

www.MigrationSpecialties.com
+1 719-371-1711, Fax: +1 888-854-3417 
Continuity in Computing: 
Founded in 1992, Migration Specialties offers modern solutions for legacy
hardware & software.  Look to us for VAX, Alpha, HP1000, PDP-11,
and DG Nova & Eclipse replacement options.  Visit our web site
for more information. 


___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

Re: [Simh] Largest VAX / PDP disk sizes

2010-03-26 Thread Armistead, Jason

Tim

 

Doing a bit more digging, it looks like if I just use the SIMH “RAUSER” disk 
type, and give it a size large enough for my needs, I’ll be OK.  The 
precompiled SIMH binaries for Windows include 64 bit file support so I can go 
bigger than 2Gb without any problems.

 

I also came across a archived post from Bob Supnik lamenting the lack of 
information for the RA70, RA73 and the other disk I mentioned.  Kind of bizarre 
that no-one knows the details.  I half expected a former Digital employee or a 
NOPSIG member might have known the answers or been able to put their hands on a 
product technical / service manual, or that someone with a still-running system 
might have been able to provide the answers.  Thank goodness for MSCP !

 

Thanks

Jason

___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

Re: [Simh] Largest VAX / PDP disk sizes

2010-03-26 Thread Shoppa, Tim

All of the PDP-11 and VAX operating systems that I know of (with one exception) 
that can talk
to MSCP disk drives, will talk to arbitrary sized MSCP disk drives. Maybe they 
cannot use all the capacity
depending on the file system. (RT-11 has 65K blocks max per file system, ODS-1 
depends on the
version of RSX, etc.)

The exception that I recall is MicroRSTS, which actually insists on seeing a 
recognized device name with
known geometry. Maybe, just maybe, MicroRSX had some similar limitations, 
insisting on seeing
RD52's or RD53's and refusing to work otherwise.

XXDP diagnostics are device specific anyway.

MSCP was the breaking point of getting away from tracks, cylinders, sectors and
just thinking of a disk as a big bunch of sequentially numbered blocks. A big 
win for the late 70's!

SIMH supports arbitrary sized MSCP disks. RCT tables won't match any real drive 
but who cares?
We do not want to go back to bad block replacement in the OS's device handler.

Tim.


___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

[Simh] Largest VAX / PDP disk sizes

2010-03-26 Thread Armistead, Jason

According to 

http://simh.trailing-edge.com/vax.html

and

http://simh.trailing-edge.com/pdp11.html

Both mention the RA73, which is a 2Gb drive (that I'd really love to use with 
SIMH !)

I am trying to run the MicroVAX 3900 flavor of SIMH, but when I try to put SET 
RQ2 RA73 in my VAX.INI file I get an error
parameter
vax.ini> set rq2 ra73
Non-existent parameter

And I end up with a 159 Mb RD54 drive instead when I boot VMS and do a SHOW 
DEVICE DUA2: /FULL

According to both the VAX and PDP11 pages on the SIMH site, the RA73 is listed 
as supported, but when I dig into the SIMH source code and look at PDP11_RQ.C, 
in the it has an X next to it which means not implemented.

What's this all mean ?

Is it just a documentation bug, and those web pages shouldn't mention RA73s ?

Is there a technical/software reason why SIMH doesn't support these drives ?  

Is no-one able to fill in the question marks in the RCT column of the table in 
PDP11_RQ.C which also has blanks for RD32, RD33 and RA70 drives ?  I managed to 
figure out that RCT stands for replacement and caching table (a reference in 
the VMS I/O User's Reference Manual to DEV$M_RCT).  We ought to strive to 
improve the comments in the code to expand this (I found no 

On a side-note, the PDP11 web page shows the capacities of these drives as a 
range.  The VAX page lists the capacities as 12KB for VAX 780 and 200-1960MB 
for VAX 3900.  The 12KB entry for VAX 780 seems like a typo perhaps.

Regards,
Jason
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

Re: [Simh] Largest VAX / PDP disk sizes

Re: [Simh] Largest VAX / PDP disk sizes

Re: [Simh] Largest VAX / PDP disk sizes

Re: [Simh] Largest VAX / PDP disk sizes

Re: [Simh] Largest VAX / PDP disk sizes

Re: [Simh] Largest VAX / PDP disk sizes

Re: [Simh] Largest VAX / PDP disk sizes

[Simh] Largest VAX / PDP disk sizes

8 matches

Site Navigation

Mail list logo

Footer information