Changes

400 bytes added ,  21:45, 25 September 2018
no edit summary
Line 1: Line 1:  +
<html>
 +
<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
 +
<!-- misc-responsive -->
 +
<ins class="adsbygoogle"
 +
    style="display:block"
 +
    data-ad-client="ca-pub-8542359430745061"
 +
    data-ad-slot="5971110325"
 +
    data-ad-format="auto"
 +
    data-full-width-responsive="true"></ins>
 +
<script>
 +
(adsbygoogle = window.adsbygoogle || []).push({});
 +
</script>
 +
</html>
 +
 
As SGI hardware ages you are less and less likely to want to run your systems with the original graphics hardware especially if that hardware is only 8-bit or perhaps the hardware is a server (without graphics). This page will demonstrate how to get the most out of your SGI by running a full X session from another, better equipped, workstation. I'm using a SGI Indy as my example but most of this will apply to any class of older SGI computer with only minor variations in the setup.
 
As SGI hardware ages you are less and less likely to want to run your systems with the original graphics hardware especially if that hardware is only 8-bit or perhaps the hardware is a server (without graphics). This page will demonstrate how to get the most out of your SGI by running a full X session from another, better equipped, workstation. I'm using a SGI Indy as my example but most of this will apply to any class of older SGI computer with only minor variations in the setup.