This file is URL ftp://ftp.xinside.com/accelx/1.2/demo/README and was 
last modified on October 31, 1995.

This is where the Accelerated-X Demo is published.  These files are
updated to include Update C, bringing them to Release Level 1.2c.
This is excatly the same as the diskettes that are now shipping.

           ---+++===*** What you need. ***===+++---

Files:
	README			- this file.
	INSTALL.txt		- Text description, install method.
	demo1_2.html		- HTML description, install method.
	ports.d/${OS}.tar.gz	- Gzipped demo for a specific OS.
	ports.d/${OS}.tar.Z	- Compressed demo for a specific OS.
	boardlist.html		- Web page of board configurations.
	knownbug.txt		- Any known bug(s).

The Anon-FTP Server we use will uncompress files, so if you do not have 
gzip available, just use the ftp GET command on the file name without the
".gz" suffix and the FTP server will uncompress the file before 
transmission.  For example, if you are using UnixWare, you could use the
ftp command "get UnixWare.tar", even if the only file on our system with
any similar name is "UnixWare.tar.Z", you will receive UnixWare.tar.
WU-FTPD is a wonderful thing :-)

OS's tested currently include:

	BSDI		BSD/OS 2.0
	FreeBSD		FreeBSD 1.1, 2.0.5, 2.1.0-SNAP-951020
	Linux		Linux 1.0, 1.1, 1.2, 1.3 (a.out and ELF)
	NetBSD		NetBSD/i386 1.0
	ISC		ISC 4.1
	SCO		Open Server/Desktop 3, 5
	Solaris		Solaris/x86 2.4
	SVR4		generic UNIX System V/386 Release 4.0, 4.2, 4.2MP
	UnixWare	UnixWare 1.0, 1.1, 2.0

         ---+++===*** Practice and Experience. ***===+++---

Don't use the Generic entries (e.g. Tseng ET4000/W32p) if we provide 
explicit support for your board (e.g. Diamond Stealth 32).  We assume
that the generic entries will have the least capable DAC, so you get
restricted colors, resolutions and it may not work properly if the
chip is coupled with a more advanced DAC.  If your board is *not*
explicitly listed, use a board with a similar combination of chipsets.
For example the Tseng VGA/32 is a good choice for the multiplicity of
ET4000/W32p based boards, because it is for Tseng's sample implementation
board, and many board vendors will copy the sample board hardware, wiring 
and timings.  

The files in AcceleratedX/boards/*/* list the graphics chip and at least 
one of the types of DAC that we expect... We have to dynamically configure 
DAC's on known, supported boards because some vendors change DAC's very 
frequently.  For example, ATI seem to continuously rev either the DAC, the
memory or the graphics chip.  If you have a supported board and your DAC
is not explicitly listed, it will probably work just fine.  If it doesn't,
you may have a board that is newer than the last board submitted to us by
the board vendor... in which case it won't work and you can let us know,
so we can fix it!

If you have a VLB motherboard and graphics card, please read the 
section after the License (Hardware Considerations).

              ---+++===*** License. ***===+++---

You may freely copy the Demonstration version of the product.

You must include this README in any copy that you make.

If you copy the Demonstration version, you must copy the whole 
Demonstration version for one Operating System, unmodified.

The demonstration version is identifiable by:

* The word DEMO printed in the version identification string when 
  the product starts.
* A message printed by the Server when it starts, warning that the 
  DEMO version is limited to a specific number of clients.
* A small number of client connections is permitted.
* Only Server 0 can be started.

If you find anything else, there is no license to use it for any 
purpose at all!  It's probably a packaging error and may be an 
internal or beta test version...  The scripts to produce all the 
different versions are rather complex.  Distribution media install
procedures differ, as do the Anon-FTP versions and the various test 
versions.  The first reporter of an erroneously included file on
our Anon-FTP Server gets at least a free copy of the full release 
for their own use :-)

The demonstration version can not be sold either individually or as 
part of a collection, without a written distribution agreement from 
X Inside Incorporated.

You may not modify or reverse engineer the binary product, disassemble, 
decompile or use other methods to investigate the internal operations
and code of the Server.

Text files may be examined and modified, but modified files may not be 
included with the Demonstration version and further copied.  

The demonstration version is intended for proof of operation and 
benchmarking only.

No warranty is provided, express or implied.

The demonstration version must not be copied or used where these
rules are not legal or can not be enforced.

        ---+++===*** Hardware Considerations. ***===+++---

*** VLB Motherboards ***

Some VLB motherboards, particularly early designs of VLB motherboards,
have problems with using memory addresses over 64MB.  Symptoms are that
graphics chipsets using a linear memory mapping will fail and may cause
the machine to halt, or the OS to fail.  We do not know of any test for 
the failing motherboards, other than using it and seeing the results.

There are two common VLB motherboard failure modes:

1/	Memory is wrapped, typically modulo 64MB.  A reference to memory
	above this value, ends up as a reference into memory address
	space, possibly where another program is in operation.  The Server
	may work for a brief time, while the memory is being corrupted.

or:

2/	The machine will hang when the address is accessed.

*** Chipsets and workrounds ***

If you have a VLB system and the Server fails, then try putting one of the
two lines that follows, in the [SCREEN] section of the Server configuration
file (/etc/Xaccel.ini or $HOME/.Xaccel.ini):

        PhysBase = 0x04000000;                  // mapping @ 64MB
        PhysBase = 0x000A0000;                  // disable linear mapping

If the first one succeeds, then you have memory mapped as high as it 
probably will work.  If you want to disable linear memory mapping 
completely, use the second line.

The following graphics chipsets will read back config registers to find 
out the default mapping the board vendor uses:

        ALLIANCE
        ARK
        ATI             (only Mach32 and Mach64, and only with VLB)
        CHIPS           (64xxx and 65xxx)
        OAK             (OTI107)
        S3              (732, 764, 864, 868, 964, 968)
        WEITEK          (P9100)

The following chips will not use default linear mapping, however you can
enable it with the PhysBase:

        CIRRUS
        OAK             (OTI087)
        TSENG

The following chips don't use linear mapping at all:

        AVANCE
        COMPAQ
        I8514
        IIT
        OAK             (OTI067, OTI077)
        S3              (801, 805, 805i, 911, 924, 928)
        TRIDENT         (currently ... new chips will use linear mapping)
        VGA
        WD
        WEITEK          (W5086, W5186, W5286)
        XGA     

The following chips enforce linear mapping and cannot be reconfigured:

        JAWS
        MATROX
        NUMBER9
        WEITEK          (P9000)


           ---+++===*** Other Stuff ***===+++---

The full and final release of Accelerated-X 1.2 is available from:

	X Inside Inc
	1801 Broadway, Suite 1710
	Denver, CO 80202

	Tel: +1(303)298-7478
	     1(800)946-7433 (800-XINSIDE - US only)
	FAX: +1(303)298-1406
	Email: orders@xinside.com
