Linux-Hardware Digest #639, Volume #9 Fri, 12 Mar 99 08:13:33 EST
Contents:
SciTech Display Doctor 1.0 for Linux BETA 4 (Kendall Bennett)
Re: newbie: RivaTnT support for xfree86 3.3.3 (Lars Aas)
Re: LS-120 and the Linux Kernel ("Rodney Beede")
Re: Using 1.4Mb floppies with an Imation LS-120. ("Rodney Beede")
ASUS P5A mboard, 2.2.3 with DMA for ALi M15xx IDE access? (Lars Aas)
Re: fdisk partitioning > 8GB drive (Andries Brouwer)
Re: Partition table overlap (Andries Brouwer)
Clock Skew Problem...Can anyone help?? (#PARIMAL ASWANI#)
Re: Linux on a Toshiba Tecra 8000? (Nino Margetic)
Re: Using 1.4Mb floppies with an Imation LS-120. ("Rodney Beede")
Re: CDR For Linux? (Tim)
Re: ATI RAGE IIC AGP (Glen Morris)
Re: Help dial on KDE ! (Adam Wendt)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Kendall Bennett)
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.development.system,comp.os.linux.misc,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]
------------------------------
From: [EMAIL PROTECTED] (Lars Aas)
Subject: Re: newbie: RivaTnT support for xfree86 3.3.3
Date: 12 Mar 1999 11:43:37 GMT
Andreas Jung <[EMAIL PROTECTED]> wrote:
> There still seem to be some minor problems as mentioned in
> http://x.physics.usyd.edu.au/3.3.3.1/NVIDIA2.html#2 ,
> but I have the impression that these are only the very first
> steps in an accelerated support for the Riva chipsets.
> So things will probably become much better in the next
> XFree86 version.
I use the Creative GraphicsBlaster card and is pleased with XFree86 3.3.3pl1
when it comes to 2D graphics. 3D accelleration on the other hand - I'll
believe it when I see it. The f***ings graphics card hardware companies
don't have the habit of releasing specs, so Linux is the last OS that will
support 3D accelleration. Someone should reverse-engineer the windows
drivers to find out how to get 3D accelleration with the Riva TNT, and then
hook their findings to SGIs GLX.
Lars J
------------------------------
From: "Rodney Beede" <[EMAIL PROTECTED]>
Subject: Re: LS-120 and the Linux Kernel
Date: Sat, 6 Mar 1999 12:16:14 -0600
The LS120 is forgotten as being /dev/fd0 after your load your boot disk. My
drive does the same thing. I can use a boot disk but when asked to switch
disks over to a root (ramdisk) disk the drive fails (because it moves over
/dev/hdd). I use the rawrite program in ms-dos to make my boot disk and it
booted off fine. You can make a ms-dos bootable SuperDisk and install
ZipSlack on that to do a installation or get to your system. To install or
boot my system I just got a bootable Slackware 3.5 cd-rom.
/\V wrote in message <[EMAIL PROTECTED]>...
I have a bootable LS-120 drive which can't boot a kernel image on a
regular 1.2 Mb floppy.
My LS-120 is set up as /dev/hdd, my root partition is /dev/hda5 and I am
using kernel 2.2.1.
I created the image using 'cp /vmlinuz /dev/hdd
rdev /dev/hdd /dev/hda5'
When I rebooted, I got 'loading..............' and then the machine
reset.
I dug my old floppy drive out of storage and the boot disk worked
fine on it.
I tried rewriting the image using the floppy drive; same result.
I tried using 'dd if=/vmlinuz of=/dev/device bs=512' where device
was /fd0 or /hdd as appropriate; same result.
I tried all of the above using 2.0.35 instead of 2.2.1; same result.
I have a Lilo bootdisk that works fine.
It appears that the LS-120 is treating the floppy differently than a
floppy drive would. The kernel treats the LS-120 correctly as a block device
for purposes of reading and writing, since the image boots properly in a
regular floppy drive.
I would greatly appreciate some insight here,
/\V
============= Posted via Newsfeeds.Com, Uncensored Usenet News ============
http://www.newsfeeds.com/ The Largest Usenet Servers in the World!
============= Over 66,000 Groups, Plus a Dedicated Binaries Server ============
------------------------------
From: "Rodney Beede" <[EMAIL PROTECTED]>
Subject: Re: Using 1.4Mb floppies with an Imation LS-120.
Date: Sat, 6 Mar 1999 12:30:15 -0600
Carl Beaudry wrote in message <7ag4sm$8lv$[EMAIL PROTECTED]>...
>Since 120Mb Imation LS-120 disks work as removable IDE drives under
>Linux and can be used to boot Linux from either a 120Mb or 1.4Mb
>floppiee, the question becomes: why have a regular floppy disk drive at
>all?
You can't use a root disk if you boot from a regular 1.44MB disk for
installing linux. The LS120 won't recoginize the disk switch and the
installation mode is locked into looking at /dev/fd#
>Has anyone figured out how to create the special files in the /dev/
>directory needed to treat an IDE Imation LS-120 disk installed at, say,
>/dev/hdc as *either* a regular 1.4Mb floppy drive *or* a 120Mb drive
>(depending on the media of course)?
>
When you install the device (in the latest kernal 2.0.35 or later I think,
probably any kernal that supports ATAPI floppy support) it is given the
block device /dev/hd? (mine is /dev/hdd). You then do a mount and it reads
the difference (you can mount a regular floppy first and then check the
amount of disk space free, then try a superdisk, it can tell the
difference). Linux doesn't support the LS120 as a /dev/fd# device though.
That is a problem with the regular floppy formatting tools and boot/root
installation disks.
If you want to format floppies (regular or 120MB) in a LS120 you pretty much
format them like a hard drive (except partitions aren't necessary). Zip
drives are somewhat similar except they have some special tools made for
them as well.
============= Posted via Newsfeeds.Com, Uncensored Usenet News ============
http://www.newsfeeds.com/ The Largest Usenet Servers in the World!
============= Over 66,000 Groups, Plus a Dedicated Binaries Server ============
------------------------------
From: [EMAIL PROTECTED] (Lars Aas)
Subject: ASUS P5A mboard, 2.2.3 with DMA for ALi M15xx IDE access?
Date: 12 Mar 1999 12:04:21 GMT
Hi guys,
My Linux box has the ASUS P5A motherboard (no sound) and is running the
2.2.3 kernel (AMD K6II-3D/350).
When Linux boots, it can't recognize the IDE controller (ALi M15xx chipset),
so it turns off DMA. Has anyone solved this problem?
Is anyone working on ALi M15xx support for the Linux kernel?
I have tried including ALi M14xx support, but I haven't checked out enabling
it through kernel boot/runtime parameters, so I might have missed something
there.
Please CC your reply to my mailbox as I don't read this newsgroup regularly
and might miss your posting. Thanks in advance,
Lars J
------------------------------
From: [EMAIL PROTECTED] (Andries Brouwer)
Subject: Re: fdisk partitioning > 8GB drive
Date: Fri, 12 Mar 1999 12:07:22 GMT
Stephen J Bovy <[EMAIL PROTECTED]>, who clearly does not
understand what he is talking about, writes:
: Andries Brouwer wrote:
::
:: Bryan McKinley <[EMAIL PROTECTED]> writes:
::
:: : Ok, under RedHat lilo I tried:
::
:: : boot: hda=10022,8,[200,256,330] <--From drive specs 200-330 s/t
::
:: : The square brackets indicate 3 values I have tried with fdisk without
:: : committing
:: : the partition changes. Question is, since the sectors/track varies
: from
:: : 200-300,
:: : what should I use? 200 produced no warnings but 256 and 330 produced
:: : cylinder ending warnings. (Your e-mail is bounced by the way).
::
:: Read the Large Disk HOWTO. A quote:
:: "Only fools talk about the `real' geometry of the drive".
::
:: You see - nobody is interested in the `real' geometry.
:: It does not exist. It will not be used, and it cannot be used.
:: Linux wants the geometry only for interaction with DOS and BIOS.
:: But DOS and BIOS use a geometry concept where you have 6 bits
:: for the number of sectors per track. So each of the values
:: 200, 256, 330 is nonsensical, 63 is the maximum.
:: If you say nothing at all, and avoid giving "hda=..." options,
:: chances are good that all will be fine, especially if you use
:: a recent kernel, like 2.0.34 or 2.0.36.
::
:: Read the Large Disk HOWTO.
::
:
: No this is not true , because if the kernel passes the wrong geometry
: values to fdisk, it will not read the part table correctly, and if
: you actually go ahead, and modify the part table with fdisk, and the
: wrong geometry, it will screw up the part table for all other os's that
: may have used that geometry when they originally created the partition
: table.
You should also read the Large Disk HOWTO,
and understand that it is impossible to use 200 sectors per track,
and that, since it is impossible, no other operating system can have
used it.
Again: the fdisk geometry has no relation at all with the `actual'
geometry, if there is such a thing.
------------------------------
From: [EMAIL PROTECTED] (Andries Brouwer)
Subject: Re: Partition table overlap
Date: Fri, 12 Mar 1999 12:14:53 GMT
Wasim Juned <[EMAIL PROTECTED]> writes:
: 2 questions -
: Does a partition overlap (as reported in fdisk v2.1) mean that there is
: a risk of corrupted data
Yes.
: and, if so, how can this be changed.
Avoid DOS. Or use translation so that the number of cylinders
of your disk stays below 1024.
: I've been looking through the
: excellent README.fdisk to no avail. fdisk will not change the partition
: information so that Begin and Start match up.
: Here is a sample fdisk output:
(from a very old fdisk - ignore this meaningless Begin column)
: Device Boot Begin Start End Blocks Id System
: /dev/hda4 8192 8767 13328 2155545 5 Extended
: /dev/hda5 8192 8767 12884 1945723+ 83 Linux native
: /dev/hda6 12288 12885 13160 130378+ 82 Linux swap
>From the Large Disk HOWTO:
What is this nonsense you get from fdisk about `overlapping'
partitions, when in fact nothing is wrong? Well - there is something
`wrong': if you look at the begin and end fields of such partitions,
as DOS does, they overlap. (And that cannot be corrected, because
these fields cannot store cylinder numbers above 1024 - there will
always be `overlap' as soon as you have more than 1024 cylinders.)
However, if you look at the start and length fields, as Linux does,
and as Windows 95 does in the case of partitions with partition type
c, e or f, then all is well. So, ignore these warnings when cfdisk is
satisfied and you have a Linux-only disk. Be careful when the disk is
shared with DOS. Use the commands cfdisk -Ps /dev/hdx and cfdisk -Pt
/dev/hdx to look at the partition table of /dev/hdx.
------------------------------
From: #PARIMAL ASWANI# <[EMAIL PROTECTED]>
Subject: Clock Skew Problem...Can anyone help??
Date: Fri, 12 Mar 1999 16:08:00 +0800
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
======_=_NextPart_001_01BE6C5F.721E4EC7
Content-Type: text/plain
I have installed RedHat 5.2 on my PC. My system is giving weird
problems. It gives clock sew problems very often (Applications and
system time don't match...so the timings conflict)...How do I solve this
problem??
Thanx in advance,
Parimal
======_=_NextPart_001_01BE6C5F.721E4EC7
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2232.0">
<TITLE>Clock Skew Problem...Can anyone help??</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2 FACE=3D"Arial">I have installed RedHat 5.2 on my PC. =
My system is giving weird problems. It gives clock sew problems very =
often (Applications and system time don't match...so the timings =
conflict)...How do I solve this problem??</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Thanx in advance,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Parimal</FONT>
</P>
</BODY>
</HTML>
======_=_NextPart_001_01BE6C5F.721E4EC7==
------------------------------
From: Nino Margetic <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable,comp.os.linux.setup,alt.os.linux
Subject: Re: Linux on a Toshiba Tecra 8000?
Date: Fri, 12 Mar 1999 12:39:05 +0000
> : I want to install Linux (together with WinNT using a bootmanager) on
> : a Toshiba Tecra 8000...
> It cetainly can be done. I have Win95 and RH 5.2 on my Tecra 8K. You will
*** I can second that. I've got Win98, WinNT, RH52 (2.0.36-3) and OpenBSD
2.4 on mine and everything works fine. KDE1.1 in 1024x768x16bpp, 3CXEM556
(10MB/s + v.90 modem), OPL3-SAx sound everything working as expected.
--Nino
---
Nino Margetic <[EMAIL PROTECTED]> | http://www.well.ox.ac.uk/~nino
The Wellcome Trust Centre for Human Genetics, University of Oxford &
Centre National de Genotypage, Evry, France.
---
------------------------------
From: "Rodney Beede" <[EMAIL PROTECTED]>
Subject: Re: Using 1.4Mb floppies with an Imation LS-120.
Date: Sat, 6 Mar 1999 12:40:43 -0600
garv wrote in message <[EMAIL PROTECTED]>...
>I've used the ls-120 to write 1.44 floppies and then read those floppies on
1.44
>drives without
>problem (yet). This is my 2nd ls-120, as the first croaked within four
months of
>use, and always gave errors on bootup (may have been RH 5.1, too). New one
ok so
>far and no errors. First one made by Matsushita (sp?); 2nd by Mitsubishi.
(DR
>brands).
>
> I hear rumors of Sony coming up with a 250MB super that is supposed to be
5x
>faster.
>
Sony is coming up with a newer drive and Iomega has already came out with
250MB Zip Drive. Imation is suppose to be coming up with a new one that has
that capacity as well and still has backward support for 720KB, 1.44MB, &
120MB disks.
I took a tour of a plant that made the LS120 SuperDisks and talked with one
of their tech people who said that you can format a regular floppy in a
LS120 and it will work fine in other regular floppy drives. But if you were
to format a LS120 to 1.44MB (which would probably damage it) it would still
only work in LS120 drives (because of the way they are made).
I got my first drive from USA Identity and I accedentally broke some pins on
the IDE interface on the drive and they replaced my drive for free since it
was still under warrenty. I also bought a new motherboard that had a bios
that fully supported booting from the drive (bios date is 4/98 I think). I
actually used the low-level format tool that they gave me with the drive too
to low-level format my SuperDisk. Works ok for now, but is kinda slow.
I think Zip drives are faster than LS120's (the ide interface) but that is
why both companies are starting to offer scsi versions of the drives. I am
kinda waiting till someone comes out with something that can read/write/boot
from regular floppies, LS120's, 100MB Zip Disks, 250MB Zip Disks, & whatever
else is popular.
============= Posted via Newsfeeds.Com, Uncensored Usenet News ============
http://www.newsfeeds.com/ The Largest Usenet Servers in the World!
============= Over 66,000 Groups, Plus a Dedicated Binaries Server ============
------------------------------
From: Tim <[EMAIL PROTECTED]>
Subject: Re: CDR For Linux?
Date: 12 Mar 1999 12:46:58 +0000
"rob" <[EMAIL PROTECTED]> writes:
> Can anybody recommend an inexpensive IDE CDR
> drive that works with linux? I checked out the CD-Writing
> mini-howto but it's a year old and I suspect (hope) its
> list of compatible drives is not complete.
Go look at the cdrecord homepage for an up-to-date list.
I picked up an 8x2 Mitsumi 29?? for about 90 ukp. (Supposed to
be ~130 ukp at the moment) If you're prepared to look then there are
some masive bargains.
/\ /\
O ___ O
===\====|====/===
\_______/
U meow.
http://www.dur.ac.uk/~d61920 mailto:[EMAIL PROTECTED]
http://surf.to/timzpayj
------------------------------
From: Glen Morris <[EMAIL PROTECTED]>
Subject: Re: ATI RAGE IIC AGP
Date: Fri, 12 Mar 1999 02:55:29 -0500
Martyn Beer wrote:
> I'm a newbie with Linux, and I cannot get X to work with the above card and
> a CTX 1569SE monitor- the best I can achieve is a very wobbly 1024x768
> resolution with duplicated menus which is completely unusable. Every other
> res is always black. When I exit the server there are no obvious errors in
> the server output apart from deleting unsupported modes. The only other
> anomaly I can see is that Windows reports 2mb of RAM for this card, whereas
> X always shows 4mb.
>
> I would be extremely grateful if anyone could help me resolve this issue.
>
> Thanks
>
> Martyn
I have the same video card with 4 meg SDRAM and I also the same problem you have
when I selected the Mach64 chipset. I did get X to display properly with
different resolutions and 16 meg colours when I selected the SVGA server
though.
I downloaded X server version 3.3.3 which has AGP support for the ATI Rage IIC
video card but couldn't get it to work.
------------------------------
From: Adam Wendt <[EMAIL PROTECTED]>
Crossposted-To:
hk.comp.os.linux,comp.os.linux,comp.os.linux.help,comp.os.linux.x,uk.comp.os.linux,tw.bbs.comp.linux
Subject: Re: Help dial on KDE !
Date: Fri, 12 Mar 1999 07:12:47 -0500
Reply-To: [EMAIL PROTECTED]
> > On Mon, 22 Feb 1999, Kevin Chu wrote:
> >
> > > i am using SuSE 6.0
> > > and i want to dial to ISP by KDE
> > >
> > > after i dial to isp , it show a error message
> > > "The pppd daemon died unexpextedly"
> > > I am using IMS 56K (USR x2)
> > > i also want to know how to dial to isp on command mode (tty1)
> > > Thank you very very much ^_^
I just installed KDE and had no idea about kppp so when i read this I set it
up and I had the exact same problem you had. I found two different ways to
fix this 1) edit /etc/ppp/options and remove the word 'lock' which was the
only word in that file for me or 2) in the configuration of kppp under
device uncheck 'use lock file' eather way worked for me
-Adam-
------------------------------
** 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.hardware) 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-Hardware Digest
******************************
