> On Feb 5, 2017, at 6:25 PM, Paul Koning <[email protected]> wrote:
>
>
>> On Feb 5, 2017, at 3:31 PM, Mark Pizzolato <[email protected]> wrote:
>>
>> ...
>>
>> So, I'd like to expand the set of file system types that the auto sizing
>> logic can perform
>> to include RSTS disks and whatever might be commonly used with RSX and RT11.
A possible complication with RSTS: I can't find the precise device size because
that isn't stored anywhere in the file structure. What I can find is the size
rounded up to the next multiple of 4096 times the cluster size (from the free
space bitmap size in blocks, since each bit represents a free cluster). I can
also find a lower bound, from the end of the last free cluster in the bitmap.
But if some of the space at the end of the pack is in use -- not all that
common but certainly possible -- then that doesn't help.
So if given a table of possible sizes for the controller model in question,
this is certainly doable. If two possible devices have sizes that are close it
wouldn't always be possible to get the right answer. Real disks are probably
ok, but MSCP disks with user-selected sizes not corresponding to actual DEC
models are likely to be a problem.
Does the autosize routine have access to the controller model designation?
paul
_______________________________________________
Simh mailing list
[email protected]
http://mailman.trailing-edge.com/mailman/listinfo/simh
