[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference mvblab::alphaserver_4100

Title:AlphaServer 4100
Moderator:MOVMON::DAVISS
Created:Tue Apr 16 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:648
Total number of notes:3158

421.0. "time loss" by TROFS::J_SCOTT () Mon Jan 20 1997 18:24

T.RTitleUserPersonal
Name
DateLines
421.1could be UNIX problem ?GIDDAY::FLAWNMon Jan 20 1997 20:1212
421.2Potentially a UNIX/S3 time loss problem?LANDO::CUMMINSTue Jan 21 1997 09:0442
421.3UNIX believes it to be a problem on all platforms with S3 VGALANDO::CUMMINSTue Jan 21 1997 09:4624
421.4whre is the patchNETRIX::"[email protected]"lissandron gianniWed Feb 05 1997 15:258
hi
I would like to know if the patch has been supplied and in that case where I
can 
find it.

              thanks   Gianni
                            mcs italy
[Posted by WWW Notes gateway]
421.5LANDO::CUMMINSThu Feb 06 1997 10:094
    A patch has been generated and is being internally tested. I forwarded
    your request to the UNIX group and asked them to reply here once the
    patch is available for external consumption.
    
421.6Patches availableRUSURE::FRANZINIFri Feb 07 1997 16:5331
Patches for the problem where systems with an S3 Trio64 graphics card can
loose time are available via anonymous ftp from:

        alpha:/pub/s3_time_loss.tar.gz
 
or via DECnet from:

        alpha::/usr/ftp/pub/s3_time_loss.tar.gz
 
This compressed tar file contains patched versions of the X server S3
Trio64 ddx (lib_dec_s3.so) for Digital UNIX V3.2D-2 through V4.0B and
README files that describe how to install the patch.

These patches will be included in the next set of USEG patch kits with
the following Patch IDs:

        V3.2D-2         OSF365X-003
        V3.2F           OSF370X-365003
        V3.2G           OSF375X-365003
        V4.0            OSF400X11-011
        V4.0A           OSF405X11-400011
        V4.0B           OSF410X11-400011
 
This problem will be fixed in the next release of Digital UNIX after
V4.0B.

Note that the problem does not exist on versions of Digital UNIX before
V3.2D-2.

John F.