[Simh] trouble with idle detection on VAX

[Villy Madsen]

Bill

An update - I had forgotten some stuff....

When the VAX is mounting drives what I see on the REAL windows app (VAX.EXE) are
a lot of writes (and not many reads) - it appears  to be one byte for each byte
on the drive being mounted.  For the system drive it happens right after the

%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.

Message.

If I shut down the VAX - and exit the sim console, and then start it up again -
it doesn't (always) happen..  VMS can then come up very quickly in deed.....

XP Home. SP2 and all of the latest patches...


Disk VGMVAX$DUA0:, device type RA92, is online, mounted, file-oriented device,
    shareable, available to cluster, error logging is enabled.

    Error count                    0    Operations completed               6243
    Owner process                 ""    Owner UIC                      [SYSTEM]
    Owner process ID        00000000    Dev Prot            S:RWPL,O:RWPL,G:R,W
    Reference count              217    Default buffer size                 512
    Total blocks             2940951    Sectors per track                    73
    Total cylinders             3099    Tracks per cylinder                  13

    Volume label        "OVMSVAXSYS"    Relative volume number                0
    Cluster size                   3    Transaction count                   219
    Free blocks              1046007    Maximum files allowed            367618
    Extend quantity                5    Mount count                           1
    Mount status              System    Cache name      "_VGMVAX$DUA0:XQPCACHE"
    Extent cache size             64    Maximum blocks in extent cache   104600
    File ID cache size            64    Blocks currently in extent cache    423
    Quota cache size               0    Maximum buffers in FCP cache       1227
    Volume owner UIC        [SYSTEM]    Vol Prot    S:RWCD,O:RWCD,G:RWCD,W:RWCD

  Volume Status:  ODS-2, subject to mount verification, protected subsystems
      enabled, erase on delete, file high-water marking, write-through caching
      enabled.


Would you believe that I never noticed the erase on delete and high-water mark
spec.  On my 750 that would have killed  us!!  I'll turn it off, but I'm
reasonably sure that I've tried that before....

Villy



-----Original Message-----
From: Bill Gallagher [mailto:bill.gallagher at augharue.com] 
Sent: Tuesday, June 12, 2007 11:44
To: Villy Madsen
Subject: RE: [Simh] trouble with idle detection on VAX

Any chance it is some AV product deciding to scan the file on open?

Bill

> -----Original Message-----
> From: simh-bounces at trailing-edge.com [mailto:simh-bounces at trailing- 
> edge.com] On Behalf Of Villy Madsen
> Sent: 12 June 2007 18:11
> To: Michael Unger
> Cc: simh at trailing-edge.com
> Subject: Re: [Simh] trouble with idle detection on VAX
> 
> It appears to me that windows is handling IO the same way that VMS
does
> for memory mapped IO.  I think that what is happening is that Windows 
> isn't sure where the end of the file is, so it reads the entire file
to
> find the end....
> 
> - it is mapping it to virtual memory, but that virtual memory is
backed
> up by that file, not the windows swap file...
> 
> I think
> 
> Villy
> 
> ----- Original Message -----
> From: Michael Unger <unger at decus.de>
> Date: Tuesday, June 12, 2007 8:43 am
> Subject: Re: [Simh] trouble with idle detection on VAX
> 
> > On 2007-06-12 15:42, "Villy Madsen" wrote:
> >
> > > [...]
> > >
> > > I am still finding that there is still something strange going on 
> > > when mounting VAX disks (running under XP).  What I think is 
> > > happening is that Windoze is sometimes mapping the entire disk 
> > > into memory (a la Noncontiguous Shared Segment <G> anyone 
> > > recognize that term).  When that happens, windows reads every byte 
> > > on the virtual disk before VMS can mount it...
> > >
> > > That could be the source of the slow boot-up of VMS (if you are 
> > > running under windows)
> >
> > There *might* be a simple explanation for this: What is an entire 
> > *disk*for VMS is a *single* file for Windows, and perhaps it just 
> > tries to "cache" this file -- which usually doesn't fit into RAM so 
> > the page file is accessed as well.
> >
> > > [...]
> >
> > Is there any possibility to open these "container files" _uncached_?
> >
> > Michael
> >
> > _______________________________________________
> > Simh mailing list
> > Simh at trailing-edge.com
> > http://mailman.trailing-edge.com/mailman/listinfo/simh
> >
> _______________________________________________
> Simh mailing list
> Simh at trailing-edge.com
> http://mailman.trailing-edge.com/mailman/listinfo/simh