		NVOPTION ALPHA

This program only run under Linux.

To install:

tar xzvf nvoption_alpha.tar.gz

cd nvoption

make install

nvoption

-----------------------------
nvidia parameters more information www.nvidia.com
TAB OPTIONS

	Option "SWCursor" "boolean"
                Enable or disable software rendering of the X cursor.
                Default: off.

        Option "HWCursor" "boolean"
                Enable or disable hardware rendering of the X cursor.
                Default: on.

        Option "NoAccel" "boolean"
                Disable or enable 2D acceleration using the XAA module
                (note that this is different that 3D acceleration).
                Default: acceleration is enabled.

	 Option "ShadowFB" "boolean"
                Enable or disable use of the shadow frame buffer layer.
                See shadowfb(4) for further information.  Default: off.

 	Option "NoRenderAccel" "boolean"
                Enable or disable experimental hardware acceleration of
                the RENDER extension.  Default: RENDER is accelerated
                when possible.

        Option "NoLogo" "boolean"
                Disable drawing of the NVIDIA logo splash screen at
                X startup.  Default: the logo is drawn.

        Option "CursorShadow" "boolean"
                Enable or disable use of a shadow with the hardware
                accelerated cursor; this is a black translucent replica of
                your cursor shape at a given offset from the real cursor.
                This option is only available on GeForce2 MX or better
                hardware (ie GeForce2 MX (200/400), GeForce2 Pro, GeForce
                2 Ultra, GeForce2 Go, GeForce3, Quadro, Quadro DDC,
                Quadro2 (MXR/EX), Quadro2 Pro and Quadro2 Go chip sets).
                Default: no cursor shadow.

TAB TWINVIEW

        Option "TwinView" "boolean"
                Enable or disable TwinView.  Please see APPENDIX I for
                details. Default: TwinView is disabled.

        Option "TwinViewOrientation" "string"
                Controls the relationship between the two display devices
                when using TwinView.  Takes one of the following values:
                "RightOf" "LeftOf" "Above" "Below" "Clone".  Please see
                APPENDIX I for details. Default: string is NULL.

 	Option "ConnectedMonitor" "string"
                Allows you to override what the NVIDIA kernel module
                detects is connected to your video card.  This may
                be useful, for example, if you use a KVM (keyboard,
                video, mouse) switch and you are switched away when
		 X is started. In such a situation, the NVIDIA kernel
                module can't detect what display devices are connected,
                and the NVIDIA X driver assumes you have a single CRT
                connected. If, however, you use a digital flat panel
                instead of a CRT, use this option to explicitly tell
                the NVIDIA X driver what is connected. Valid values for
                this option are "CRT" (cathode ray tube), "DFP" (digital
                flat panel), or "TV" (television); if using TwinView, this
                option may be a comma-separated list of display devices;
                e.g.: "CRT, CRT" or "CRT, DFP".  Default: string is NULL.


TAB TV

	The "TVStandard" option should be added to your screen section; valid
    	values are:

        "PAL-B"  : used in Belgium, Denmark, Finland, Germany, Guinea,
                   Hong Kong, India, Indonesia, Italy, Malaysia, The
                   Netherlands, Norway, Portugal, Singapore, Spain,
                   Sweden, and Switzerland
        "PAL-D"  : used in China and North Korea
        "PAL-G"  : used in Denmark, Finland, Germany, Italy, Malaysia,
                   The Netherlands, Norway, Portugal, Spain, Sweden,
                   and Switzerland
        "PAL-H"  : used in Belgium
        "PAL-I"  : used in Hong Kong and The United Kingdom
        "PAL-K1" : used in Guinea
        "PAL-M"  : used in Brazil
        "PAL-N"  : used in France, Paraguay, and Uruguay
        "PAL-NC" : used in Argentina
        "NTSC-J" : used in Japan
        "NTSC-M" : used in Canada, Chile, Colombia, Costa Rica, Ecuador,
                   Haiti, Honduras, Mexico, Panama, Puerto Rico, South
                   Korea, Taiwan, United States of America, and Venezuela

    The line in your XF86Config file should be something like:

        Option "TVStandard" "NTSC-M"

    If you don't specify a TVStandard, or you specify an invalid value,
    the default "NTSC-M" will be used.  Note: if your country is not in
    the above list, select the country closest to your location.

    The "TVOutFormat" option can be used to force SVIDEO or COMPOSITE
    output.  Without this option the driver autodetects the output format.
    Unfortunately, it doesn't always do this correctly.  The output format
    can be forced with the options:

         Option "TVOutFormat" "SVIDEO"

                     or

         Option "TVOutFormat" "COMPOSITE"



FREQUENTLY ASKED TWINVIEW QUESTIONS (to nvidia) :
 

Q: Nothing gets displayed on my second monitor; what's wrong?
 
A: Monitors that do not support monitor detection using Display Data
   Channel (DDC) protocols (this includes most older monitors) aren't
   detectable by your NVIDIA card.  You need to explicitly tell the NVIDIA
   XFree86 driver what you have connected using the "ConnectedMonitor"
   option; e.g.:

        Option "ConnectedMonitor" "CRT, CRT"


Q: Will window managers be able to appropriately place windows
   (e.g. avoiding placing windows across both display devices, or in
   inaccessible regions of the virtual desktop)?

A: Not exactly. NVIDIA is considering writing an implementation of the
   Xinerama extension; this would allow Xinerama-aware window managers
   to query the screen layout.  The other solution is to use panning
   domains to eliminate inaccessible regions of the virtual screen
   (see the MetaMode description above).


Q: Why can I not get a resolution of 1600x1200 on the second display
   device?

A: Because the second display device was designed to be a digital
   flat panel, the Pixel Clock for the second display device is only
   150 MHz.  This effectively limits the resolution on the second display
   device to somewhere around 1280x1024 (for a description of how Pixel
   Clock frequencies limit the programmable modes, see the XFree86 Video
   Timings HOWTO).


Q: Do video overlays work across both display devices?

A: Hardware video overlays only work on the first display device.
   The current solution is that blitted video is used instead on TwinView.


Q: How are virtual screen dimensions determined in TwinView?
 
A: After all requested modes have been validated, and the offsets
   for each MetaMode's viewports have been computed, the NVIDIA driver
   computes the bounding box of the panning domains for each MetaMode.
   The maximum bounding box width and height is then found.

   Note that one side effect of this is that the virtual width and
   virtual height may come from different MetaModes.  Given the following
   MetaMode string:

        "1600x1200,NULL; 1024x768+0+0, 1024x768+0+768"

   the resulting virtual screen size will be 1600 x 1536.


Q: Can I play full screen games across both display devices?

A: Yes.  While the details of configuration will vary from game to game,
   the basic idea is that a MetaMode presents X with a mode whose
   resolution is the bounding box of the viewports for that MetaMode.
   For example, the following:

        Option "MetaModes" "1024x768,1024x768; 800x600,800x600"
        Option "TwinViewOrientation" "RightOf"

   produce two modes: one whose resolution is 2048x768, and another whose
   resolution is 1600x600.  Games such as Quake 3 Arena use the VidMode
   extension to discover the resolutions of the modes currently available.
   To configure Quake 3 Arena to use the above MetaMode string, add the
   following to your q3config.cfg file:

        seta r_customaspect "1"
        seta r_customheight "600"
        seta r_customwidth  "1600"
        seta r_fullscreen   "1"
        seta r_mode         "-1"

   Note that, given the above configuration, there is no mode with a
   resolution of 800x600 (remember that the MetaMode "800x600, 800x600"
   has a resolution of 1600x600"), so if you change Quake 3 Arena to use
   a resolution of 800x600, it will display in the lower left corner of
   your screen, with the rest of the screen grayed out.  To have single
   head modes available as well, an appropriate MetaMode string might
   be something like:

        "800x600,800x600; 1024x768,NULL; 800x600,NULL; 640x480,NULL"

   More precise configuration information for specific games is beyond the
   scope of this document, but the above examples coupled with numerous
   online sources should be enough to point you in the right direction.
