unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: floyd@barrow.com (Floyd L. Davidson)
Subject: Re: dual head video system
Date: Tue, 30 Nov 2004 04:01:59 -0900	[thread overview]
Message-ID: <87vfbnpk1k.fld@barrow.com> (raw)
In-Reply-To: mailman.2423.1101810331.27204.help-gnu-emacs@gnu.org

ken <gebser@speakeasy.net> wrote:
>Floyd L. Davidson wrote:
>
>>(For anyone that hasn't tried it, using a dual head video system
>>under X is just astounding!)
>>
>>
>That tasty morsel has had me salivating for a long time.  How do
>you do it?  Is there a webpage or two which is/are particularly
>helpful?

Start by using google to find this Message-ID
87isb4afo3.fld@barrow.com, which is a description of XFree86
configuration that was posted to comp.os.linux.x last August.

Then search the web and Usenet archives for "xinerama" and
you'll find more about the mechanism.  If you have one
particular video card in mind, add a keyword for that too.

Basically it requires either two video cards or a video card
that supports dual monitors.  Neither the cards nor the monitors
need to be identical.  A number of inexpensive video cards
support dual monitors, so it does not require high end hardware.

I fired up one box using an old PII-300mHz and two old video
cards with 4K of RAM each, plus two 15" 1024x768 monitors that I
picked up at a local "surplus sale" for $10 each.  It is a
Point-Of-Sale system now...  In fact, that project was what got
me to try it, as I bought the old PII box with a 17" monitor for
peanuts just for the POS system.  But when I saw xinerama in
operation, that 17" monitor was quickly relocated to my work
position, as the existing workstation already had a G400 Matrox
video card.

But what it does is what you really want to know about... :-)

The two monitors can be totally separate, or they can be
combined as if they are one big screen.  They can also be at
different resolutions, though that gets strange if they are
combined.  With a combined screen, the second monitor's screen
can be positioned anywhere relative to the first.  They can be
stacked vertically or horizontally, with position 0,0 being
either the top, bottom, right or left monitor.

The only limitations that I discovered were having to use
builtin VESA modelines as I could not get mine to work with a
custom screen resolution, plus if your X server is configured to
switch between screen resolutions, only the first screen can be
switched.  One external problem is that so far not many programs
are xinerama aware, so such things as popup windows from your
web browser might just land smack in the middle of the extended
screen...  half on one monitor and half on the other. That's a
bummer, but not hard to ignore.  Eventually we can expect all
programs to check for dual monitors and adjust appropriately.

-- 
Floyd L. Davidson           <http://web.newsguy.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska)                         floyd@barrow.com

  parent reply	other threads:[~2004-11-30 13:01 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16  5:41 emacs for everything? Joe Corneli
     [not found] ` <mailman.3197.1100662500.8225.help-gnu-emacs@gnu.org>
2004-11-16 11:58   ` Fabian Braennstroem
2004-11-17 19:05     ` Floyd L. Davidson
2004-11-20 17:19       ` Kai Grossjohann
2004-11-21  9:17         ` Janusz S. Bień
     [not found]         ` <mailman.363.1101029322.27204.help-gnu-emacs@gnu.org>
2004-12-05  1:23           ` Zajcev Evgeny
     [not found]       ` <mailman.236.1100971735.27204.help-gnu-emacs@gnu.org>
2004-11-20 18:18         ` Pascal Bourguignon
2004-11-20 21:40           ` Jay Belanger
2004-11-20 23:05             ` Alan Mackenzie
2004-11-21  9:29               ` Joe Corneli
2004-11-21 16:22             ` Pascal Bourguignon
2004-11-20 18:45         ` Floyd L. Davidson
2004-11-22 10:27           ` Kai Grossjohann
2004-11-22 13:50             ` John Sullivan
2004-11-23 19:57             ` Maciek Pasternacki
2004-11-25 13:31               ` Kai Grossjohann
2004-11-25 14:52                 ` Maciek Pasternacki
2004-11-26  9:03                   ` Kai Grossjohann
2004-11-27 17:12                     ` Maciek Pasternacki
2004-11-27 19:50                       ` Kai Grossjohann
2004-11-28  1:29                         ` Maciek Pasternacki
2004-11-28 11:47                           ` Kai Grossjohann
2004-11-27 23:16                       ` Daniel Pittman
     [not found]               ` <mailman.1437.1101390082.27204.help-gnu-emacs@gnu.org>
2004-11-25 15:19                 ` Mike
2004-11-25 15:45                   ` Maciek Pasternacki
     [not found]             ` <mailman.1058.1101240531.27204.help-gnu-emacs@gnu.org>
2004-11-24  4:13               ` Lee Sau Dan
2004-11-24 13:10                 ` Maciek Pasternacki
2004-11-24 14:25                   ` Leonardo Boiko
2004-11-24 20:33                     ` Maciek Pasternacki
2004-11-24 20:49                       ` Leonardo Boiko
     [not found]                       ` <mailman.1312.1101329987.27204.help-gnu-emacs@gnu.org>
2004-12-01 17:49                         ` Kevin Rodgers
     [not found]                     ` <mailman.1308.1101329036.27204.help-gnu-emacs@gnu.org>
2004-11-25  3:16                       ` Pascal Bourguignon
2004-11-25 13:16                         ` Maciek Pasternacki
     [not found]                         ` <mailman.1434.1101389211.27204.help-gnu-emacs@gnu.org>
2004-11-25 20:12                           ` Stefan Monnier
2004-11-25 21:03                             ` Maciek Pasternacki
     [not found]                             ` <mailman.1503.1101417224.27204.help-gnu-emacs@gnu.org>
2004-11-27 22:00                               ` Stefan Monnier
2004-11-28  1:31                                 ` Maciek Pasternacki
2004-11-25 17:06                       ` Mathias Dahl
2004-11-28 14:29                       ` Lee Sau Dan
2004-11-28 20:24                         ` Joe Corneli
2004-11-30 10:00                     ` ken
     [not found]           ` <mailman.591.1101120112.27204.help-gnu-emacs@gnu.org>
2004-11-24 23:58             ` Floyd L. Davidson
2004-11-27 20:07               ` Kai Grossjohann
2004-11-27 23:08                 ` Micha Feigin
2004-11-28  1:33                 ` Maciek Pasternacki
     [not found]                 ` <mailman.1945.1101634177.27204.help-gnu-emacs@gnu.org>
2004-11-28 12:24                   ` Floyd L. Davidson
2004-11-29 11:56                     ` Kai Grossjohann
     [not found]                     ` <mailman.2151.1101729999.27204.help-gnu-emacs@gnu.org>
2004-11-29 15:11                       ` Floyd L. Davidson
2004-12-01 16:34                         ` Kai Grossjohann
     [not found]                         ` <mailman.2811.1101919485.27204.help-gnu-emacs@gnu.org>
2004-12-03 19:55                           ` Floyd L. Davidson
     [not found]               ` <mailman.1836.1101586658.27204.help-gnu-emacs@gnu.org>
2004-11-27 22:00                 ` Floyd L. Davidson
2004-11-28 18:36                 ` David Hansen
2004-11-30 10:15               ` dual head video system (was Re: emacs for everything?) ken
     [not found]               ` <mailman.2423.1101810331.27204.help-gnu-emacs@gnu.org>
2004-11-30 13:01                 ` Floyd L. Davidson [this message]
2004-11-18 19:47     ` emacs for everything? Alan Mackenzie
2004-11-17 20:50   ` Alan Mackenzie
2004-11-17 22:46     ` Joe Corneli
     [not found]     ` <mailman.3419.1100732160.8225.help-gnu-emacs@gnu.org>
2004-11-18 19:42       ` Alan Mackenzie
2004-11-18 22:41         ` Joe Corneli
2004-11-17  3:24 ` Joe Corneli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vfbnpk1k.fld@barrow.com \
    --to=floyd@barrow.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).