[Info-vax] Looking for suggestions for new $GETDVI item codes

[kenneth.randell at verizon.net]

On Saturday, October 18, 2014 at 9:35:21 AM UTC-4, Stephen Hoffman wrote:
> On 2014-10-18 03:03:56 +0000, Robert A. Brooks said:
> 
> > Back in the day when I worked in VMS Engineering in Nashua, NH, I would 
> > periodically poll the collective wisdom of comp.os.vms for suggestions 
> > regarding
> > new $GETDVI item codes.
> 
> OK... You asked for it...
> 
> 
> That four-byte DVI$_MAXBLOCKS field is going to need some work, sooner 
> or later.  Might want to make it happen sooner, even if the underlying 
> change doesn't arrive until later.
> 

So I am late in commenting...

I agree with Hoff here.  This needs work; it's already too late.

Try a DVI$_MAXBLOCK on a drive over 1.0 TB capacity and you get a negative number.  DVI$_FREEBLOCKS has the same issue.