[comp.os.vms] indexf.sys, odds & ends

tada@athena.mit.edu (Ivan Tadayoff) (01/29/88)

Does anyone out there know how do decode the indexf.sys file at the root
level of a disk?  I'm writing a disk analysis program, and I know one can
dump/header the file, and get all the information in text form, but
for an RA81 it makes a *big* file.  Also, I'd like to do all the decoding
from within a C program, instead of a mixture of C and DCL.

Thanks in advance any help...

-------
Odds & ends: 'n' now if you're in a hurry.

Wow!  I finally got rn to work.  I've been reading news for a couple of 
weeks, but the stupid thing refused to let me reply to anyone.  This is
sort of a mixture of replies to a few people....

re: windows
(someone wrote: does anyone else have problems with uVax II's crashing
under WS3.2 and VMS 4.5...)

Yes!  We've been having constant problems with the machine crashing, with
processes going into resource wait states, and windows hanging around on 
the screen for no apparant reason.  Partly it's our fault, because the
machine that has had the most problem was a VaxStation 2000 running Lisp.
DEC reccommends at least 9M of memory for a single user Lisp machine, but
they only sell the 2000 with 6M....

When we moved our development to a VaxStation II with 9M the problems went
away mostly.  It seems to be a memory problem, and we were suspicious of
exceeding UIS$QVSS_POOL_SIZE, but had no way of being certain.  Thanks to
whoever posted the method of checking if that is indeed the problem.


re: AST's (& UIS)
We've been doing some development here with window based interfaces, and
naturally we have AST's coming out of our ears (one for each menu entry, 
etc, etc, etc).  I had done some graphics hacking last fall during which I
discovered that (although the manual doesn't indicate it) the different AST's
refused to interrupt each other.  When the programmers here started work
and asked me questions about what I had found out concerning using UIS calls,
I told them to watch out for AST's.  Unfortunately, some of them can't seem to
understand.  Thanks to Jamie Hanrahan for the excellent explaination
of AST vs. wait states.  It's been a great help.