Linux-Misc Digest #423, Volume #19 Fri, 12 Mar 99 07:13:08 EST
Contents:
Re: user accounts (bklimas)
Re: self extracting .exe on linux? (Sechylmanos)
Re: Linux setup (Phil)
Accessing Modem, Running X Apps ([EMAIL PROTECTED])
Re: VNC: server on LInux, viewer on NT - GREY screen problem ([EMAIL PROTECTED])
Re: If I had the time I know how to make a fortune in unix (Nick Manka)
Re: swapon -s: /proc/swaps: No such file or directory ([EMAIL PROTECTED])
sed: splitting word over several lines ("Anthony Borla")
Re: Linux setup (John Thompson)
Re: Help: No man pages in Debian 2.1? ("D. Vrabel")
Re: [question] dcc for linux ("D. Vrabel")
Re: Linux on Fujitsu 420D with KVM switch (Bill Stephens)
Re: g77 anyone? (Shane Steven Sturrock)
Linux server for dos/windoze machines. . . (Norvell Spearman)
SciTech Display Doctor 1.0 for Linux BETA 4 (Kendall Bennett)
----------------------------------------------------------------------------
From: bklimas <[EMAIL PROTECTED]>
Subject: Re: user accounts
Date: Fri, 12 Mar 1999 05:33:14 GMT
[EMAIL PROTECTED] wrote:
> Hi,
>
> I'm a newbie to Linux, and have gotten befuddled by the man pages & how
> to's. How do I give access to a modem, sound card, zip drive ect... to users
> on my machine?
>
> Jon Lindberg
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
You might be able to find an answer to this question at:
http://www.magma.ca/~bklimas/FAQ.htm#mounting_as_user
Hope this helps. Best regards,
Stan
ps. sorry if I posted it twice.
------------------------------
From: [EMAIL PROTECTED] (Sechylmanos)
Crossposted-To: utah.linux,linux.redhat.misc,linux.redhat.rpm
Subject: Re: self extracting .exe on linux?
Date: Fri, 12 Mar 1999 02:36:07 -0800
In article <7c3qtg$jgu$[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote:
> I have a self extracting zip file (.exe). Is
> there a way to expand it under Linux without
> going to a windows machine running it and bringing
> it back to my linux box?
>
> I am running RedHat 5.2 so an rpm would be nice
> if available.
>
> thanks
>
> am
You could try running it under either DosEMU or WINE, but I am going to
assume that you need a windows machine to get it uncompressed.
:P
sechylmanos
------------------------------
From: [EMAIL PROTECTED] (Phil)
Crossposted-To: ibmnet.general,comp.os.linux.setup
Subject: Re: Linux setup
Date: 11 Mar 1999 18:51:04 GMT
Reply-To: [EMAIL PROTECTED]
Georges Heinesch <[EMAIL PROTECTED]> wrote:
>Quoting David Kirkpatrick (10-Mar-99 17:59:19):
>
>> He said his computer name "can be" 111.111.111.111 when it gets the
>> random 111.111.111.111 on the dynamic alocation. It will be different
>> the next time he dial's in.
>
>Exactly!
And what I said was that you can't get it to respond to
it's name unless you register with NIC and get hosted...
I also said that you COULD write a script in your favorite
scripting language that updates a webpage somewhere with
your current dynamically assigned IP address and links
to your machine -- Just have the web page automatically
switch to your local public_html directory if you are
connected... SEE? It updates every time you connect...
like this: <meta content="1,url=http://111.111.111.111:80/index.html"
http-equiv="refresh">
(note that I had to wrap the line here, don't do that.)
It sounds so good, I think I'll do it.
That's what those services (dyndns, etc.) do, I swear!
Phil
------------------------------
From: [EMAIL PROTECTED]
Subject: Accessing Modem, Running X Apps
Date: Fri, 12 Mar 1999 10:37:42 GMT
Hi all,
I am a newbie learning different Linux commands. After reading some of "Linux
Unleashed" book (a fat and useless junk book; dont buy it !!!), I only got
more confused. I was able to mount and unmount my CD-ROM drive and floppy,
but after following the book and Serial Howto, I could not figure out how to
access the modem and dial out to my ISP even after creating /dev/modem and
running "minicom -s". As I run minicom to dial my ISP #, the modem does not
dial the no. even though the screen says that the no is being dialed. Anybody
know what the problem could be? I looked at xinitrc file but could not
understand what to do with it !
After I run X from X11 directory, X starts and I see the X-shaped
pointer/cursor but nothing happens after that; no xterm or console box or any
other app starts/shows up. How do I start xterm or netscape? Do I also need
to start fvwm and how do I do that? What is the order in which fvwm and X are
started? I was also not able to exit from X so I restarted my computer; what
is the proper way to get out of X? Thanks for any help.
BOB
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.networking,comp.os.linux
Subject: Re: VNC: server on LInux, viewer on NT - GREY screen problem
Date: Fri, 12 Mar 1999 10:51:21 GMT
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] wrote:
> >
> > I have the VNC server on Linux. The VNC viewer on NT.
> > I can connect with the
> > viewer, but all that I see is a grey screen with the X
> > cursor (similar to
> > that seen on Linux after 'startx' but before your
> > chosen window manager kicks
> > in). Although I can move the
> > cursor, there is nothing there to select!!
> > Anyone know what I'm not doing that I should be?
>
> I had a similar problem, but I am not at the box where I had VNC
> running, so I don't know if I can give a complete answer. If I recall
> correctly, it was because there was no route in the routing table to the
> IP adddress that the windows box was seeing my linux box as. My
> situation was linux <-> via TCP/IP over a serial cable. I was
> frustrated since I could run a PC X server on the windows box just fine,
> remotely running apps from the linux box. But VNC would give me the
> grey screen. It turned out that although I had a loopback route to
> localhost (127.0.0.1, as does everybody), I had to add a separate route
> in the routing table to the "internal" IP address I had assigned to the
> linux box (e.g. 192.168.0.2) as part of the TCP-over-serial connection.
> Unlike running a remote X server, where you are displaying the remote
> apps on a server on the remote box, VNC works by actually running the
> "remote X server" on the "home box". Thus, unless you have a route to
> that IP address (i.e. the IP address of the linux box, as seen by the
> windows box) in the routing table, you can't send apps there to be
> displayed.
>
> Or else it is becuase you have no apps starting up in your startup file,
> as someone else suggested.
>
> Hope this helps.
>
> Jon Sundquist
>
I have a feeling that this might be the problem, though I am not sufficiently
familiar with Linux configuration to be sure. Here's something I tried after
having run vncserver on the Linux box and vncviewer on the WIndows box, On
the Linux box, I tried:
xman -display PC007248Linux:2
expecting to see xman appear on the windows PC. However, the Linux CLI
came back with...
_X11transSocketINETConnect: Can't connect: errno = 101
Error: Can't open display@ PC007248Linux:2
On the windows end, running vncviewer with the -console option displays
a console window that confirms the display name...
...
VNC authentication suceeded
Desktop name "sjm's X desktop (PC007248Linux:2)"
Does this support the notion that I might need some new entry in the
routing table? If so, how do I do this? Where is the routing information
held? Is it the IP address of the Linux box I need to add here (i.e.
the *server* end IP address)???
I feel I'm closing in on fixing this thing.
Thanks for your help so far.
Steve.
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED] (Nick Manka)
Crossposted-To: comp.unix.admin,comp.unix.misc,comp.unix.programmer,comp.unix.shell
Subject: Re: If I had the time I know how to make a fortune in unix
Date: 11 Mar 1999 20:47:41 GMT
Reply-To: [EMAIL PROTECTED]
In article <7c7vdo$m4m$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (John DuBois) writes:
> In article <RWxF2.25144$[EMAIL PROTECTED]>,
> No Spam <[EMAIL PROTECTED]> wrote:
>>Why not just simply break the 8 character barrier on unix login commands for
>>a start.
>
> Because there are zillions of utilities out there written in a manner that
> depends on the 8-character limit (and even some leftovers from the preceding
> 7-character era).
That's not a good reason not to do it, it's a good reason to hope
someone else implements it :>
This is just like every other value-overflow issue. At some point you
are going to suffer and enlarge it, be it sooner or later. A few
Unices have done it.
Enter argument about usernames being of indefinite length and how the
next time_t should be 256bits.
--
Closed software is modern alchemy.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: swapon -s: /proc/swaps: No such file or directory
Date: Thu, 11 Mar 1999 20:26:07 GMT
On 7 Mar 1999 21:39:05 GMT, [EMAIL PROTECTED] (Dieter Rohlfing) wrote:
>On Sat, 06 Mar 1999 21:11:45 GMT, [EMAIL PROTECTED] (Juergen
>Heinzl) wrote:
>
>>In article <[EMAIL PROTECTED]>, Dieter Rohlfing wrote:
>>>I have the proc filesystem installed, but no entry /proc/swaps. Where is
>>>the switch to get /proc/swaps? TIA.
>>
>>man swapon
>
>Man swapon doesn't tell me, how I can get /proc/swaps. Did you read man
>swapon?
>
>Dieter Rohlfing
what do you need /proc/swaps for?
free
gives swap space info
if you are looking to creat swap space, your looking in the wrong
place
man mkswap
------------------------------
From: "Anthony Borla" <[EMAIL PROTECTED]>
Subject: sed: splitting word over several lines
Date: Thu, 11 Mar 1999 21:20:34 GMT
System: Red Hat 5.2
Shell: bash 1.14.7(1)
Prog: sed 3.02
A file, datefile1, contains a single line, a date in the form :dd/mm/yyyy.
Using the hexdump utility it is: 0000000 1 2 / 1 2 / 1 9 9
9 \n
I am attempting to use a sed command sequence to replace each '/' character
with the newline character so that each date component is placed on a
seperate line.
I am using the following sed command sequence to achieve this:
sed 's/\(..\)\//\1^N/g' datefile1 > datefile2
Note: The '^N' character was obtained via the Ctrl-V Ctrl-N key
combination.
Instead of obtaining, as expected, an output of:
0000000 1 2 \n 1 2 \n 1 9 9 9 \n
I get:
0000000 1 2 016 1 2 016 1 9 9 9 \n
and the date components remain on the same line.
Can anyone see what the problem is and suggest a solution ?
Anthony Borla
------------------------------
From: John Thompson <[EMAIL PROTECTED]>
Crossposted-To: ibmnet.general,comp.os.linux.setup
Subject: Re: Linux setup
Date: Thu, 11 Mar 1999 13:22:44 -0600
Georges Heinesch wrote:
> > Actually, your computer can be addressed as 111.111.111.111
> > since that's your name for all practical purposes.
> Yes, I know that. But the 111.111.111.111 was only an example. The
> address will change next time when I dialup. That's why I would like
> to know if it is possible to assign a fix name (like "foobar") to my
> machine independantly what my actual IP address is.
I don't think this is possible with dynamic IP addresses,
since a domain name has to map to a specific IP address.
> >>Is it possible to configure Linux that way?
> > Sure, but you need to register your name with NIC
> > and convince some unwitting ISP to host you.
Yes, this is how a domain name gets assigned to an IP
address, but this generally costs more than dymanic IP
dialup service since that IP address won't be usable by
anyone else. Dial-up ISP's are assigned a number of IP
addresses that they dole out to their users on an "ad hoc"
basis. This reduces the ISP's costs since they don't need a
separate IP address for each customer. But most ISP's
(including ibm.net) do offer fixed IP domain name hosting
for an additional cost. I believe ibm.net's offering can be
found unde Comercial Services on their web site. But be
prepared to pay dearly...
> > Best thing is to use a script to update an html file
> > at your ISP with your dynamic IP address whenever you
> > connect and then when you are connected anyone who
> > knows to look there can connect to your box. Voila!
> Yep, that sound like a solution indeet, though not quite what I
> imagined at the beginner, but it should work, right.
But since ibm.net does not offer a service like that at this
time (at least not for personal dial-up accounts) you may be
SOL.
> > Your name "foobar" or whatever is just for show unless
> > it is registered... and you had better check and make sure
> > no one else has registered that name so that if by some
> > quirk you mess up good you don't hose the owner of the
> > name!
> Hmmm ... correct.
But there's nothing stopping you from using whatever names
you please on your own little network.
--
-John ([EMAIL PROTECTED])
------------------------------
From: "D. Vrabel" <[EMAIL PROTECTED]>
Subject: Re: Help: No man pages in Debian 2.1?
Date: Fri, 12 Mar 1999 11:11:25 +0000
On Fri, 12 Mar 1999, Bill wrote:
> With the help of people in these groups, I finally chose a distribution and
> installed it, Debian 2.1. But the command I had hoped to use to help start
> learning what it's all about and how it works is missing. When I type man,
> I get an error message like bash: no such command. I know just about
> nothing but tried a few things I found in a book, like find, which turned up
> some directories with man in their name (man1, man2, etc.) but none had the
> man command itself.
>
> I'm mystified and stumped, wondering maybe if they changed it in this new
> distribution or hid it or what? Thanks for your help.
You need to install the mandb package to get man. I'd also install
the info package as well while you're at it. Use apt-get to download a
package and all it's required packages.
David
--
David Vrabel
Engineering Undergraduate at University of Cambridge, UK.
------------------------------
From: "D. Vrabel" <[EMAIL PROTECTED]>
Subject: Re: [question] dcc for linux
Date: Fri, 12 Mar 1999 11:13:10 +0000
On 12 Mar 1999, Jean-Yves Simon wrote:
> Hi,
> in windows 95, one can have a "poor man network" by connecting
> 2 computers using parallel port with a little utility called
> dcc.
>
> Is there such a thing in Linux ?
Can't you use plip or somesuch thing?
David
--
David Vrabel
Engineering Undergraduate at University of Cambridge, UK.
------------------------------
Date: Fri, 12 Mar 1999 05:17:52 -0600
From: Bill Stephens <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.laptops,comp.os.linux.setup,comp.os.linux.hardware
Subject: Re: Linux on Fujitsu 420D with KVM switch
I don't know if this will help, but I had the same problem with my thinkpad
until I closed the the laptop. I still can't switch with X-Windows open.
If I leave X open, the mouse stops functioning. To get it functioning
again, I have to switch to one of the virtual consoles and back.
-Bill
Chris Browning wrote:
> Got an old cast-off Fujitsu 420D with a bad LCD. Trying to run Linux w/
> XWindows on it through a KVM switch. My BSD box runs XWindows through
> the KVM switch w/ no problem. The laptop w/ Linux runs the console
> display through the switch no problem, but startx seems to want to run
> through the LCD. Anyone got any ideas? I can't figure out how to bypass
> the LCD. The laptop BIOS has an option for CRT which I have selected and
> that seems to give me the console display but X is no go. Help please!
> Thanx!
> --
> Chris Browning
> [EMAIL PROTECTED]
>
> "If you believe in Nothing...
> Honey, It believes in you."
------------------------------
From: [EMAIL PROTECTED] (Shane Steven Sturrock)
Subject: Re: g77 anyone?
Date: Thu, 11 Mar 1999 17:58:50 +0000
On Thu, 11 Mar 1999 10:42:17 , Oliver D. Bedford <[EMAIL PROTECTED]> wrote:
>Hello,
>
> does anybody here use fortran on Linux? I�ve compiled a f77 program on
>a K6-2 (350 Mhz) and it is slower compared to a SGI Box (R10000 @ 195
>Mhz)
>by a factor of 3-4.
There could be several reasons for this. The R10K is a pretty fine processor,
it has multiple pipelines and on the fly instruction reordering which means
it will easily beat a Pentium or equivalent at twice the clock speed. Also,
SGI go to great pains to get their memory access times down to a bare minimum
so if you are accessing large chunks of main memory then the SGI is going
to score highly over a PC architecture.
Although I use Alphas, I have a great deal of respect for SGI boxes, in
particular our R10K based Challenge box, expensive but nice.
--
Dr. Shane Sturrock - http://nova.bru.ed.ac.uk/~sss
Linux, a better WinNT than WinNT
------------------------------
From: Norvell Spearman <[EMAIL PROTECTED]>
Subject: Linux server for dos/windoze machines. . .
Date: Thu, 11 Mar 1999 23:35:38 -0600
Can someone point me to or give me information about setting up a Linux
server to provide thin-client services to dos/windoze machines? I
believe something called Citrix WinFrame does this and I'd like to know
how to do this with Linux.
Thanks much. . .
--
[EMAIL PROTECTED]
To reply, remove my opinion about
unwanted e-mail from my address.
------------------------------
From: [EMAIL PROTECTED] (Kendall Bennett)
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.development.system,comp.os.linux.hardware,comp.os.linux.setup,comp.os.linux.x
Subject: SciTech Display Doctor 1.0 for Linux BETA 4
Date: Thu, 11 Mar 1999 21:49:09 -0800
SciTech Display Doctor 1.0 for Linux
------------------------------------
PREVIEW RELEASE 4
-----------------
Where to get it?
================
You can download the beta 4 preview release from:
ftp://ftp.scitechsoft.com/sdd/beta/linux/sdd-10b4-glibc.sh
for glibc based systems, or:
ftp://ftp.scitechsoft.com/sdd/beta/linux/sdd-10b4-libc5.sh
for older libc5 based systems.
NOTE: We have removed all support for our legacy VBE/AF based drivers due
to compatibility problems. Hence we are now only supporting the new
SciTech Nucleus based drivers for Linux, so please check the list of
supported chipsets below to see if your graphics card is supported or
not. We will be adding lots more chipsets to the list of supported
hardware as the release matures.
About SciTech Display Doctor for Linux:
=======================================
SciTech Display Doctor for Linux brings SciTech's proven DOS and Windows
device support technologies to the Linux Operating System. Although one
of the core features of our DOS and Windows products is the support for
the VESA VBE/Core standard, the Linux version has nothing at all to do
with VESA services. Rather SciTech Display Doctor for Linux incorporates
the new SciTech Nucleus, Graphics Architecture device driver technology
to bring SciTech's device support to the Linux platform.
SciTech Nucleus is a binary portable, OS neutral, device driver
architecture. As binary portable drivers, SciTech can fully develop and
test the core device drivers in the DOS and Windows environments, while
being able to target any Intel x86 based OS as the runtime environment
(such as Linux). This essentially allows the Linux product to utilise the
same SciTech binary device drivers as the DOS and Windows versions of the
product, improving the quality and performance of the drivers for all
supported operating systems.
Universal X11 Server:
=====================
Although SciTech Nucleus drivers will be able to be used directly by
applications built with the free SciTech MGL Graphics Library for Linux,
SciTech Display Doctor for Linux also provides a Universal X11 driver
based on the XFree86 sources. All features of traditional XFree86 servers
are supported including:
. Full 2D acceleration
. XFree86 extensions such as VidMode and DGA for fullscreen
applications
. XAA (XFree Acceleration Architecture) support
. On-the-fly mode switching
. Full Monitor Power Management support via the VESA DPMS Standard.
The SciTech Display Doctor X11 server also provides the following
additional features not found in other servers:
. Plug and Play configuration of your hardware, including the
monitor for DDC2B-compliant monitors (Microsoft Plug and Play
compatible). This includes never having to create CRTC timings by
hand again!
. Single binary server than runs on every chipset supported by the
SciTech drivers (virtually any existing card), with hardware
acceleration.
. Both 16:9 and 4:3 aspect ratio display modes.
. Low resolution display modes such as 320x240, 400x300 and 512x384
for fullscreen games like Quake and Quake II.
Universal SVGALib Driver:
=========================
SciTech Display Doctor for Linux also includes a new SVGAlib-compatible
library using the SciTech Nucleus device drivers. The new SVGALib shared
library provides support for full hardware acceleration and enables the
use of all your graphics hardwares capabilities for fullscreen games and
applications (including XMame, Quake, Snes9x and many more). Some of the
features of the SciTech Nucleus SVGALib driver are:
. Much better hardware support than regular SVGAlib (all Nucleus
supported cards can be used to full extent).
. Many more supported modes than regular SVGAlib, including 16:9
aspect ratio modes.
. Hardware acceleration through Nucleus.
. Joystick, mouse and keyboard support from the latest SVGAlib
libraries.
Universal Extended Text Mode Driver:
====================================
SciTech Display Doctor for Linux also includes a new extended text mode
utility, based on our SciTech Nucleus drivers. This utility allows you to
change the Linux text mode console to any of the extended text mode
resolutions supported by SciTech Nucleus. The textmode utility also
includes full support for refresh control allowing you to set the maximum
refresh rate that your hardware can handle.
The textmode utility is installed along with other Nucleus binaries in
/usr/lib/nucleus/bin.
Software requirements:
======================
. Any Linux distribution, with kernel >= 2.0 (tested with a 2.0.35
and 2.2 kernels).
. XFree86 3.3.3 libraries and files (not provided in this package),
previous versions may work too but are not recommended.
SciTech Display Doctor for Linux is provided in two separate
distributions, one for GNU Libc 2.0 (a.k.a glibc) systems, and another
for older libc5 systems. Make sure you get the correct package for your
system, or the drivers will not work correctly.
If you do not have the above or later versions of the software installed
on your Linux system, you may want to upgrade your software before
attempting to install SciTech Display Doctor. Please also ensure that you
are using the latest versions of the above software before sending in any
bug reports.
Installation and configuration:
===============================
SciTech Display Doctor for Linux comes in self-extracting shell archives
(*.sh shell scripts). There are two packages available, depending on your
libc version:
sdd-10-glibc.sh for Glibc systems (RedHat 5.x, Debian 2.x ...)
sdd-10-libc5.sh for older libc5 systems (RedHat 4.x,
Slackware...)
You need to run the appropriate script *as root* on a text mode console.
Do *not* run the setup script from an XTerm or a remote login, as it
require direct access to the hardware to detect and configure the
software. For example, to install the glibc version of SciTech Display
Doctor:
sh sdd-10-glibc.sh
or you can give execution permissions to that file (chmod +x sdd-
glibc.sh), and then just run it that way:
./sdd-10-glibc.sh
Of course, the same applies to the sdd-10-libc5.sh package.
Please note that you may have to kill GPM before running the install
program, for certain non-serial mice (e.g. PS/2 mice).
Follow the instructions on the screen and answer the questions about the
installation paths, etc. After installing all the necessary files, the
setup script will then attempt to do automatic detection and analysis of
your graphics hardware. If this succeeds, the XF86Setup program should be
automatically started to allow you to configure the server. Once you get
to the XF86Setup stage, installation and configuration is similar to a
regular XFree86 setup with the following exceptions:
1. You don't have to choose your graphics hardware; it is detected
automatically for you.
2. If your graphics card supports the VESA DDC2B services (see
below) and your monitor is Plug and Play compatible, the setup
program will automatically detect your monitor, it's frequency
range and capabilities. If not you may select your monitor from
extensive databse of known monitors.
3. You don't need to edit the XF86Config configuration script to add
mode tables, CRTC timings and refresh rates. This is all done
automatically for you using the VESA GTF timings and SciTech's
extensive Discrete Monitor Timing database.
4. Refresh rate control is currently provided by an extension to the
SDDConfig configuration script. You can change the global refresh
rate for all modes (default is 60Hz Non-Interlaced) by adding the
following to XF86Config:
RefreshRate freq Choose the vertical refresh rate in
hertz to be used (in the "scitech"
Screen section).
However if you do not specify a refresh rate in your SDDConfig
file, the defaults that have been set through the centering and
refresh control programs will be used.
5. Some additional command line parameters have been added to the
XF86_SDD server:
-vfreq <freq> Choose the refresh rate in Hertz
-device <dev> Choose the controller to use (0..n-1)
Please note that the SDDConfig file, along with all the SciTech Display
Doctor for Linux files, are all located in /usr/lib/nucleus. The XFree86
XF86Config file is not used, and as such you can have both a regular
configuration file for XFree86 servers, and a SDDConfig file for the
SciTech X11 server.
After the XFree86 server installation, you will be prompted to install
the SVGAlib wrapper library, which will enable you to use legacy SVGAlib
programs with the SciTech Nucleus drivers, providing enhanced performance
and many more display modes.
The Linux extend text mode utility program will also be installed
automatically for you.
Beta reports and bug reports:
=============================
To send in bug reports, please use the web hosted bug report form located
on our web site at:
http://www.scitechsoft.com/t_reqsdd_linux.html
If you don't have access to the web, please send email bug reports to
[EMAIL PROTECTED] Please use the supplied bug report form
(bugrept.txt) to ensure that we have enough information to be able to
track down your problem.
You may also want to check out the SciTech Display Doctor beta newsgroup
on our news server at:
news://news.scitechsoft.com/scitech.display.doctor.beta
List of all supported chips:
============================
This is a complete list of the various graphics cards that this version
of SciTech Display Doctor supports. Please note that this list refers to
the actual chips being used, not a board-level implementation. Thus you
will not see any products from Hercules or STB on the list, but their
products are supported because they use S3, Cirrus, Tseng, etc. chips.
Also, any card with less than 512KB of memory cannot be supported by
SciTech Display Doctor.
Please note that we are in the process of moving all our existing device
support code to our new SciTech Nucleus device driver architecture. If
you have a chipset that is not listed below that you would like to see
supported in SciTech Display Doctor for Linux, please send an email to
[EMAIL PROTECTED] to let us know.
. Alliance ProMotion 6422, ProMotion AT24, ProMotion AT25
. Alliance ProMotion AT3D
. InteGraphics IGA1680, IGA1682, IGA1683, CyberPro 2000
. InteGraphics CyberPro 2010
. Intel i740
. Matrox MGA Millennium, MGA Millennium II, MGA Mystique
. Matrox MGA Mystique 220, MGA G100, MGA G200
. Cyrix Media GX, Media GXi, Media GXm
. Macronix 86250, 86251
. Philips 9710, 9712
. S3 Trio32, Trio64, Trio64V+, Trio64UV+, Trio64V2/DX, Aurora64V+
. S3 Virge, Virge/DX/GX, S3 Virge/VX, Virge/GX2, Trio3D
. SiS 6202, 6205, 6215, 5595, 5597/5598, 6326
. Tseng Labs ET6000, ET6100, ET6300
. ATI Mach64 CT, Mach64 ET, Mach64 VT, 3D Rage, Mach64 VTB
. ATI 3D Rage II, 3D Rage II+, 3D Rage IIC, 3D Rage Pro
. ATI 3D Rage LT Pro
. Cirrus Logic 5434, 5436, 5440, 5446, Laguna 5462, Laguna 5464
. Cirrus Logic Laguna 5465
SciTech Software, Inc.
505 Wall Street
Chico, CA 95928
(530) 894-8400
(530) 894-9069 FAX
Web: http://www.scitechsoft.com
Email: [EMAIL PROTECTED]
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Misc Digest
******************************
