[Simh] VAX and disk device size oddness

[Joe Ambrose]

Lennert, 

 

According to the VAX.DOC page 13..... 

 

"The type options can be used only when a unit is not attached to a file.
RAUSER is a "user specified" disk; the user can specify the size of the disk
in either MB (1000000 bytes) or logical block numbers (LBN's, 512 bytes
each).  The minimum size is 5MB; the maximum size is 2GB without extended
file support, 1TB with extended file support"

 

I tried it, (I user RAUSER with 2048 as the argument, it works) anything
larger reports ...

 

VAX simulator V3.9-0

NVR: buffering file in memory

C:\VAX\vax.ini> set rq4 rauser=20480

Unit disabled

C:\VAX\vax.ini> attach rq4 C:\VAX\data\test.dsk

Unit disabled

 

=================================================

Joseph Ambrose

172 Ketcham Avenue

Amityville, NY 11701

Primary: 631-598-0528

  Mobile: 516-380-6047

    Email: jambrose0321 at gmail.com (Job search related)

               joeambrose at optonline.net (Personal)

Profile: http://www.linkedin.com/in/jambrose0321

 

-----Original Message-----
From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing-edge.com]
On Behalf Of Lennert Van Alboom
Sent: Friday, February 15, 2013 8:32 AM
To: simh at trailing-edge.com
Subject: [Simh] VAX and disk device size oddness

 

Hello,

 

 

I just started playing with a simh vax again. Built the 3.9 vax binary (on
linux/powerpc), and it works fine.

 

Odd thing though: I cannot use RAUSER, it seems. I tried the following line:

 

SET RQ1 RAUSER=20000 

 

Which should result in a 20GB disk. No dice though: simh claims "invalid
parameter". I tried lowering the size to 10000, 5000, ... no difference. 

 

I then tried replacing the RAUSER by RA92, which should be supported and
have a ~8GB size. This was accepted. However, from the OS (VMS 7.3), after
an INIT/ERASE the disk reports 2940951 blocks which is somewhat under 1.5GB.
The

RQ0 RA90 reports the expected 2376153 blocks or somewhat under 1.2GB. 

 

Now, the host OS is on a PPC G4, which means a 32bit kernel. Is this what is
causing this? If yes, can I work around it? I'd prefer something bigger than
1.5GB :-)

 

 

Thanks,

 

 

Lennert

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20130215/05a36364/attachment-0002.html>