At 07:12 PM 8/17/2001 -0500, Carl Perkins wrote:
How to find out if you can access the data other than trying and checking
the status?
From SYS$SMHANDLER_STARTUP.COM:
$ ! 1) If called by the startup process, this command procedure starts the
$ ! server management driver and recursive entry to
At 11:29 AM 8/20/2001 -0400, Dan Sugalski wrote:
At 10:23 AM 8/20/2001 -0500, Craig A. Berry wrote:
Thanks, Carl, that's exactly the sort of stuff I was looking for. I'll see
if I can work up a patch to VMS::System that uses this to figure out whether
we can request the environmental stuff from
On a DS20E, VMS7.2-1:
$ write sys$output f$getsyi(thermal_vector)
FF01
$
On an ES40, VMS7.2-1:
$ write sys$output f$getsyi(thermal_vector)
$
Neither of these seems useful...
Carl
-Original Message-
From: Craig A. Berry
At 06:41 AM 8/17/2001 -0400, Carl Friedberg wrote:
On a DS20E, VMS7.2-1:
$ write sys$output f$getsyi(thermal_vector)
FF01
$
On an ES40, VMS7.2-1:
$ write sys$output f$getsyi(thermal_vector)
$
Neither of these seems useful...
They
At 12:45 PM -0400 8/17/01, Dan Sugalski wrote:
At 06:41 AM 8/17/2001 -0400, Carl Friedberg wrote:
$ write sys$output f$getsyi(thermal_vector)
$
Neither of these seems useful...
They aren't. You've apparently got a set of systems without the on-chip temperature
Dan Sugalski [EMAIL PROTECTED] wrote:
On a DS20E, VMS7.2-1:
$ write sys$output f$getsyi(thermal_vector)
FF01
$
On an ES40, VMS7.2-1:
$ write sys$output f$getsyi(thermal_vector)
$
Neither of these seems useful...
They aren't. You've
