Linux-Hardware Digest #539, Volume #10 Sun, 20 Jun 99 13:13:29 EDT
Contents:
Re: Windows easy to install? BULLSHIT! (Johan Groth)
Re: how to configure on board Ethernet chip? (Malware)
Reboot during Linux installation (Imran Quraishi)
CMI8330 ("l. yao")
Philips CDRW 400 series (ollivier civiol)
stupid dual motherboard questions (Jim Shaffer, Jr.)
Re: Diamond modem compatability. (Christopher Warren)
On board ESS1938 SOLO1 3D Sound Chipset ??? (Lucinda-Jane Janse van Rensburg)
Redhat 6.0 and USB mouse (Yanhong Li)
Re: 360K 5 1/4" drives on linux (Henrik Carlqvist)
Re: 360K 5 1/4" drives on linux (B'ichela)
Re: @home ISP Sucks! (Alex Lam)
Re: Linksys Etherfast 10/100 ("Eric Harmon")
Re: IBM PS/2 maximum serial port speed? (Georg Schwarz)
----------------------------------------------------------------------------
From: Johan Groth <[EMAIL PROTECTED]>
Crossposted-To: comp.os.ms-windows.advocacy,comp.os.linux.setup
Subject: Re: Windows easy to install? BULLSHIT!
Date: Sun, 20 Jun 1999 16:18:59 +0200
Jack Coates wrote:
> =
> [deletia]
> =
[deletia]
> Why does GNOME/Enlightenment randomly freeze, requiring CTRL-ALT-Backsp=
ace?
> Was it GNOME or E that froze? /var/log/messages doesn't say. I could st=
art
> randomly upgrading RPMs until the problem goes away....
Neither GNOME nor Enligthenment are finished products. The latest
'stable' of Enlightenment you can find is 0.15.5 and as you can see it
isn't a 1.x release. Many feel that the release of a 1.x of GNOME was
too early. Too much of didn't work well. I'm one of them that thinks
GNOME shouldn't have been released even now. It's still a bit unstable. =
Just my 2 =F6re.
///Johan
-- =
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=
=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
"Better to ask questions and seem stupid
than not to ask questions and remain stupid" -Unknown
Johan Groth <[EMAIL PROTECTED]> Kupolen Data
------------------------------
From: Malware <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: how to configure on board Ethernet chip?
Date: Sun, 20 Jun 1999 10:52:32 +0200
Hi Vidar,
you wrote:
> Both eepro100.c and rclanmtl.c have the number '82558' in them.
Later one is used for the feature 'Red Creek Hardware VPN
(EXPERIMENTAL)'. I do not think that is what the questioner does have
on-board.
Malware
------------------------------
From: Imran Quraishi <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Reboot during Linux installation
Date: Sun, 20 Jun 1999 11:20:55 -0400
Reply-To: [EMAIL PROTECTED]
Hello,
I am trying to install Linux on my machine, but it reboots whenever I
try to run the installation routine. The specs are:
Intel PII 450
Asus P2B motherboard
128MB non-ECC RAM
Aopen 48X CD-ROM
IBM Deskstar 10.1 gb HD (5400 rpm)
Matrox Millennium G200 w/ 8mb SGRAM
Silicom Multimedia 8400 ISA v.90 modem
First I tried Redhat 6.0. The installation proceeds through the initial
steps just fine. I'm installing on the second primary partition (the
first is a Windows 98 FAT32 drive). When the files start being copied,
the system suddenly reboots.
After trying this many times, I decided to try Slackware 4.0. The CD
wasn't bootable, so I made a boot and root floppy. The boot floppy
seemed to work fine. After I switched to the root floppy, the screen
says it found a compressed root image and starts to read it. It then
says the root image is loaded for a fraction of a second and the system
reboots suddenly. I read the readme file for the root and boot images,
which says that some Pentium II and Celeron chips have a timing error
that causes the system to reset when the keyboard LEDs are reset. So I
tried the workaround root image (no_kbd), but got the same results.
Finally, I borrowed a copy of Slackware 3.5 on a bootable CD. The CD
starts to boot fine but still restarts after a minute or so.
I have not had any problems with Windows 98 and this is my first time
installing Linux on this machine, which I have had for about 6 months.
It looks to me like either a power supply problem or an incompatibility
with between Linux and my hardware.
Please, let me know if you have any ideas or if you have seen this
problem before.
Thank you,
Imran Quraishi
[EMAIL PROTECTED]
------------------------------
From: "l. yao" <[EMAIL PROTECTED]>
Subject: CMI8330
Date: Sun, 20 Jun 1999 11:07:38 -0400
Hi, there,
I am new comer to Linux world but I like this newsgroup at the beginning
of I read it. So, I come here for your suggestion.
I have a sound card with CMI8330 chip. It doesn't work in my Linux
box (Red Hat 6.0). snconfig detected this card. But when it played sample
sound, there was nothing. I am sure the speakers were turned on. 8-) Maybe
it's due to wrong card settings? In the card settings window of sndconfig,
I didn't change anything and olny used the I/O PORT, IRQ,DMA and MPU I/O
presented by sndconfig. I think they were detected by sndconfig itself,
right? And more important and more shamely, I don't know how to modify it.
8-<
Is there anybody who knows how to make it work?
Thank you very much,
Long
------------------------------
From: ollivier civiol <[EMAIL PROTECTED]>
Subject: Philips CDRW 400 series
Date: Sun, 20 Jun 1999 16:20:08 GMT
Hello,
I own a, IDE Philips CDRW 400.
I recompiled my kernel with the SCSI emulation, at boot up I see a=20
SCSI emulation for IDE CDROM but no drive is available on the CSI bus=20
??
can anyone help ?
Thanks
------------------------------
From: [EMAIL PROTECTED] (Jim Shaffer, Jr.)
Subject: stupid dual motherboard questions
Date: 20 Jun 1999 11:23:10 -0500
Reply-To: [EMAIL PROTECTED]
Are either the QDI TwinMagic (or whatever it's called) or the ABIT BP6 actually
available yet? I can't find them.
Also, is there any such thing as a dual motherboard (for anything newer than the
Pentium Pro) that's NOT ATX? I'd really like to be able to upgrade without
having to buy not only a new case, but also a new mouse and keyboard with PS2
connectors. (Why did they go with that format anyway? I thought the PS2 was a
failure.) I have enough old parts taking up space already!
--
Secretary, Williamsport Area Computer Club <http://www.sunlink.net/wacc>
Member, Susquehanna Valley Amateur Astronomers
<http://www.geocities.com/CapeCanaveral/Hangar/2999/svaa.html>
Personal Home Page: http://woodstock.csrlink.net/~jshaffer
------------------------------
From: Christopher Warren <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Diamond modem compatability.
Date: Sun, 20 Jun 1999 12:27:52 +0000
I just purchased a Diamond SupraExpress 56K v.90 w/speakerphone. This is
an ISA modem and can be configured as PNP or with jumpers. I set my as
pnp with the isapnp application. It now works good.
Initially, I set it up under W98 to make sure everything would work ok.
It didn't. Since this one doesn't come with an on-board speaker and I
don't have any sound cards in the Linux box, it was difficult to tell if
it was working properly. I kept getting messages that in summary said
unable to connect (or something like that). I searched Diamond's web
site and found a firmware update. After installing the latest firmware,
it now works very well.
Darren Johns wrote:
>
> I am looking at getting a new 56K modem, and from what I can see the
> Diamond SupraExpress 56 ones look quite good. I would like to hear from
> anyone who has got any experience/problems etc. with any of the
> 56, 56 Pro, or 56 Memory modems by Diamond (internal or external).
> I run Redhat 5.2, but will be moving to RH6 (probably) soon.
>
> BTW Does anyone know if it is possible to get an external WinModem?
>
> Thanks, Mark.
>
> P.S. If you haven't got one of the above modems I don't want to hear any
> general 'Diamond are rubbish' type of messages.
> --
> | To take no action is in itself taking an action, and to have no opinion is |
> |/-\| to have an opinion, so are we helpless in what goes on around us?? |/-\|
> |\-/|\-/|\-/|\- D Mark Johns. mailto:[EMAIL PROTECTED] -/|\-/|\-/|\-/|
> |_____________________ http://www.csd.abdn.ac.uk/~djohns ____________________|
------------------------------
From: Lucinda-Jane Janse van Rensburg <[EMAIL PROTECTED]>
Subject: On board ESS1938 SOLO1 3D Sound Chipset ???
Date: Sun, 20 Jun 1999 18:32:24 +0100
Jetway (www.jetway.com.tw) motherboard model J-7BXAS with the following
description of the on-board sound chipset:
"On Board 3D Audio
On Board ESS1938 SOLO1 Sound Chipset
Single , High-Performance , Mixed-Signal , 16-bit Stereo VLSI Chip
Full Native Dos Game Compatibility , Via Three Technologies :TDMA ,
DDMA , PC/PCI
Microsoft Direct Sound 3D DirectX5.0
Full Duplex Operation For Simultaneous Record And Playback
Meets PC97/PC98 and WHQL Specifications
Sound Driver for Windows 95 , Windows98 & Windows NT4.0 , ESS Media
Rack "
I use Redhat 2.2, sndconfig recognises no pnp or PCI soundcards, pnpdump
recognises no pnp cards at all. Specifying my own card in sndconfig
results in "/lib/modules/2.2.2/whatever.o: , init_module: Device or
resource busy , sound: Device or resource busy"
I've played around with the BIOS but this seems to have no effect
(should it?)
The settings in Windows98 seems to be IRQ=5, DMA=1, SBIO=220h,
MPU401=330h
How can I make this work in Linux 2.2.2?
Thanks in advance.
------------------------------
From: [EMAIL PROTECTED] (Yanhong Li)
Crossposted-To: comp.os.linux.misc
Subject: Redhat 6.0 and USB mouse
Date: 20 Jun 1999 16:42:10 GMT
Hi -
I am trying to install Redhat 6.0 on a new machine - Acer Aspire 6150,
it has a USB mouse, which linux does not recognize.
Questions:
1. Where can I find the patch for this (redhat 6.0 is linux 2.2.5)?
2. How can I install the patch to my system?
Thanks
------------------------------
From: Henrik Carlqvist <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: 360K 5 1/4" drives on linux
Date: Sun, 20 Jun 1999 15:43:33 +0200
B'ichela wrote:
> I had a 360K in my system as B: in addition to a 1.44MB as A:.
> Bios was properly configured as such, linux works the 1.44 with out
> a hassle but it Would NOT work the 360K despite the fact that it
> recognized it from the system bootup.
How did you try to use the drive? Have you tried something like
mount /dev/fd1d360 /mnt
If you are only using mtools, does b: point to /dev/fd1d360 in
/etc/mtools.conf?
regards Henrik
--
spammer strikeback:
root@localhost [EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (B'ichela)
Crossposted-To: comp.os.linux.setup
Subject: Re: 360K 5 1/4" drives on linux
Date: Sun, 20 Jun 1999 16:00:06 GMT
Reply-To: [EMAIL PROTECTED]
In article <[EMAIL PROTECTED]>, Henrik Carlqvist wrote:
>B'ichela wrote:
>> I had a 360K in my system as B: in addition to a 1.44MB as A:.
>> Bios was properly configured as such, linux works the 1.44 with out
>> a hassle but it Would NOT work the 360K despite the fact that it
>> recognized it from the system bootup.
>
>How did you try to use the drive? Have you tried something like
>
>mount /dev/fd1d360 /mnt
>
>If you are only using mtools, does b: point to /dev/fd1d360 in
>/etc/mtools.conf?
>
>regards Henrik
>--
>spammer strikeback:
>root@localhost [EMAIL PROTECTED] [EMAIL PROTECTED]
>[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
I found part of the problem. My old creaky 5 1/4" half hight drive
does not have the Disk Change line. It sounds stupid but Linux keeps
thinkign I took the disks out of the drive. How can I modifiy the kernal
NOT to look at the floppy disk change line?
Is there an option on the lilo boot line to turn checking the
change line off or do I need to modify the floppy.c routines of the kernal.
or GASP! find a cheat (hardware wise for this drive.)
speaking of the mtools.conf file do you have a known working one?
aparently my mtools.conf was leftover from when I used the original mtools
that came with slackware 3.1 and that had less configuration settings in
it.
--
A pearl of wisdom from the y2K newsgroups:
=========================================================================
Y2K appears to be the Baby Boomers mid-life crisis, and it has the
potential to be a dandy.
-- Anonymnous --
==========================================================================
B'ichela
------------------------------
From: Alex Lam <[EMAIL PROTECTED]>
Subject: Re: @home ISP Sucks!
Date: Sun, 20 Jun 1999 09:01:55 -0700
nope wrote:
>
> I know this is the wrong group, but I just wanted to get the word out on
> what @home is doing with cable modem service. This is a internal memo,
> atleast to my knowledge and so far It has not been disputed. If you
> want to check for yourself call @home or your local cable provider that
> uses @home and they'll confirm the cap. They don't want to talk about
> it, but they'll eventually confirm the cap.
> ----------------------------------------
>
> ONadvantage Upstream Enhancement
> Date posted: 9 Mar 1999
> Date last updated:
> Author: Karen Thomas
> Distribution status: MSO
> Review status: Preliminary
>
> Also referred to as 'Upstream Defined
> Bandwidth' or 'Upstream Rate Limiting'
>
> Background and FAQs for Operations including
>
> Customer Service Representatives
> Field Installers
>
> Background
>
> ONadvantage Overview and Upstream Enhancement - an integral part
> of the @Home experience
>
> @Home's network was designed on the fundamental premise that
> sustainable
> high performance requires a highly scaleable architecture that removes
> Internet
> traffic jams and enables true end-to-end performance management.
> ONadvantage (Optimized Network Advantage) has two goals that carry this
> premise forward:
>
> 1.Ensure that the @Home experience is fast and delivers multi-megabit
> speeds.
> 2.Ensure that speed and service is consistent across the growing
> subscriber
> base.
>
> To this end there are three ONadvantage projects:
>
> 1.ONadvantage Proxy Evangelization - Improve speed by storing data as
> close to the subscribers as possible by using proxy or caching
> servers.
> 2.ONadvantage Upstream Enhancement - Ensure consistent speed and
> performance across the subscriber base by proactively managing the
> network at the subscriber's end.
> 3.ONadvantage CAR (Committed Access Rate) - Ensure consistent speed
> and performance by shielding the @Home Network from external
> problems including security attacks and off-net data abuses.
>
> The remainder of this document addressed ONadvantage Upstream
> Enhancement details that arise from MSO and @Home planning sessions.
>
> ONadvantage Upstream Enhancement - What it is and why
>
> The ONadvantage Upstream Enhancement is an improvement in speed and
> service consistency that is implemented at each customer's modem. The
> maximum rate at which a modem can send data (upstream) is set at 128
> kbps
> (kilobits per second).
>
> Speed remains at multi-megabit levels.
> Current speed claims of 'peak speeds over 100 times faster than
> a
> 28.8 kbps modem' and 'up to 100 times faster' remain and are
> not
> affected in any way.
> Downstream rates remain as is and benefit from ONadvantage
> Upstream Enhancement.
> Over 99.5% of the subscriber base will experience improved service.
> Consistent high speed service: Sending files at rates up to 128
> kbps ensures that each subscriber receives consistent high
> speed
> experience. The @Home Network has done research and has
> noticed that certain customers are abusing the network by using
> a
> disproportionate share of network resources, which in turn
> causes
> poor performance for others on the network. To help manage this
> abuse and ensure that all our customers get consistent high
> speed
> service, ONadvantage is being rolled out. The ONadvantage
> Upstream Enhancement is targeted specifically at protecting the
> HFC network from the small set of subscribers that may use a
> disproportionate share of bandwidth.
>
> All modems have a limit on the rate at which they can send data,
> although this
> rate is different from modem to modem and depends on many additional
> factors.
> The @Home service, designed for residential use and designed for
> acceptable
> use as outlined in the Acceptable Use Policy, benefits by proactively
> managing
> this rate, the upstream rate, to 128 kbps for all subscribers. By mid
> 1999 all
> new modem deployments will have 128 kbps upstream rates. As of March 1,
> 1999 all existing proprietary (non-DOSCIS) modems are in the process of
> being deployed with the ONadvantage Upstream Enhancement.
>
> Analogy: Think of ONadvantage Upstream Enhancement as metering
> lights on highway on-ramps. The speed on the highway is fast and
> remains fast as long as cars entering the highway do so in a
> managed,
> organized fashion without impairing the speed of those already on
> the
> highway. When metering lights are off cars may enter freely. When
> metering lights are on, cars wishing to enter must first adhere to
> the
> metering lights. This prevents a surge of vehicles from entering
> the
> highway all at once and slowing the entire highway and all the
> drivers' fast
> speed experience. The speed of each driver on the highway is
> preserved.
> Note that this analogy falls short in that the ONadvantage Upstream
> Enhancement delivers an on-ramp rate that is faster than the
> typical
> on-ramp. ONadvantage Upstream Enhancement is 4 times faster than a
> dial-up modem while ensuring that the peak (downstream) rates are
> over
> 100 times faster than a 28.8 kbps modem. ONadvantage Upstream
> Enhancement delivers on-ramp speeds that reach peak speeds that are
> orders of magnitude faster than typical dial-up modems offer in the
> same
> situation.
>
> Customer Service Representatives
>
> ONadvantage Upstream Enhancement - FAQs
>
> What is ONadvantage?
>
> ONadvantage stands for 'Optimized Network Advantage'. Based on customer
> feedback, we're making a few changes to our network to ensure that you
> consistently experience the blazingly fast speed of the Internet over
> cable. MSO
> @Home is a series of enhancements that will give all our members the
> opportunity to enjoy superior performance and unwavering reliability of
> the
> MSO @Home service.
>
> ONadvantage enhancements include upgrading all our mail and caching
> servers.
> The new mail servers are designed to ensure consistent, reliable
> performance as
> our subscriber base grows, and the new caching servers are designed to
> ensure
> super-fast performance for Web surfing.
>
> What is ONadvantage Upstream Enhancement?
>
> We have noticed that certain customers are abusing the network by using
> a
> disproportionate share of network resources, which in turn causes poor
> performance for others. To help manage this abuse and ensure that all
> our
> customers get consistent high speed service, we have recently deployed
> a series
> of enhancements called ONadvantage or Optimized Network Advantage. The
> ONadvantage Upstream Enhancement is a speed and service consistency
> improvement implemented at each customer's modem.
>
> What is the upstream rate of my @Home service?
>
> Is the @Home service rate-limited?
>
> Downstream rates are NOT limited. Upstream rates are limited to 128
> kbps.
>
> I bought an 'unlimited' service. I asked you if the @Home service is
> upstream rate limited, and you said yes. This doesn't sound like the
> 'unlimited' service I signed up for. What happened?
>
> The @Home Network is committed to providing the highest level of
> network
> performance. We constantly improve the service to ensure the fastest
> possible
> experience. ONadvantage Upstream Enhancement ensures that everyone has
> upstream rates required for the fastest possible residential use. As
> per the
> Acceptable Use Policy we reserve the right to make changes to the
> network as
> needed to ensure that this is accomplished. You should read the
> Acceptable
> Use Policy for more information:
> http://www/V3/tabhelp/houseruls/aup/index.htm
>
> Why does my server at home appear to be slow when it is accessed from
> the outside?
>
> The @Home residential service offering is designed for your personal
> use of the
> Internet. As per the Acceptable Use Policy, a residential user may not
> run
> programs or servers which provide network services to others via the
> @Home
> residential service - for example, an @Home user should not be running
> a
> web/mail/ftp server to serve external connections. To help manage this
> abuse
> and ensure that all our customers get consistent high speed service, we
> have
> recently deployed a series of enhancements called ONadvantage or
> Optimized
> Network Advantage. This will ensure that you and all subscribers will
> always be
> able to use the @Home service as it was designed to be - super fast
> @Home
> Experience.
>
> To address the more sophisticated needs of customers like you, we are
> investigating the possibility of providing a service whereby you will
> be able to
> host your own servers in your residence.
>
> What is considered acceptable use of the @Home service?
>
> What is the definition of 'residential use'?
>
> What is @Home's policy on network abuse?
>
> The Acceptable Use policy can be found here:
> http://www/V3/tabhelp/houseruls/aup/index.htm
>
> Field Installers, Other Operations
>
> ONadvantage Upstream Enhancement - Field Installer Notes
>
> Field installers and all individuals with customer contact should *NOT*
> discuss ONadvantage with subscribers (unless specifically asked).
>
> The best ONadvantage explanation is to avoid talking about it to
> begin with-if possible.
> All ONadvantage communications to the customer is based
> on an as-needed basis only.
> ONadvantage is a benefit to subscribers and it is also very
> complicated to explain-therefore limiting subscriber
> communication regarding ONadvantage prevents
> unnecessary misunderstandings.
> ONadvantage needs your help by keeping it low-key in the eyes of
> the subscriber.
> Ideally the customer will experience the advantages of
> ONadvantage program without ever knowing it existed.
>
> ONadvantage Upstream Enhancement - Additional Background
>
> ONadvantage Upstream Enhancement provides significant benefit by
> protecting
> the HFC plant. Data shows a small minority, as few as one or two users,
> can
> use a disproportionate share of bandwidth and negatively affect the
> performance
> of other subscribers. The likelihood of this happening increases as the
> number of
> subscribers grows. (An example of this kind of abuse is running servers
> off of
> the @Home Network and is clearly outlined in the Acceptable Use Policy
> (AUP)). @Home is committed to addressing this problem early and before
> significant subscriber growth leads to increased performance issues and
> makes
> ONadvantage Upstream Enhancements difficult to deploy. A handful of
> abusers
> can use up to 50% of a given node's resources if left unchecked.
>
> Implementing the ONadvantage Upstream Enhancement is the only known,
> scaleable solution to managing the subscriber abuse. Other approaches
> are not
> proactive and therefore leave the network and all subscribers open to
> severe
> performance loss whenever an abuser grabs an upstream bandwidth above
> and
> beyond a residential user's needs. The AUP clearly states what is and
> is not
> acceptable. The ONadvantage Upstream Enhancement makes the @Home
> residential service very unattractive for subscribers who push the
> limits of the
> service into the unacceptable use area. Specifically, those subscribers
> who wish
> to deploy servers (clearly not acceptable use and outlined in the AUP
> as such)
> will find that the 128 kbps maximum upstream rate unacceptable
> performance
> for this kind (unacceptable) activity. They will seek services
> elsewhere, including
> business services offered by the MSO and MSO@Home (including @Work
> products). Again, this is a minute portion of the subscriber base, less
> than half a
> percent.
>
> Deploying Upstream Enhancements
>
> The schedule, and this includes status on what markets have been
> deployed to
> date, is found here:
>
> Master Schedule:
>
>
>http://partner.home.net/prod_marketing/info/onadvantage/UpstreamRateLmtg_MasterSchedule.xls
>
> This schedule is for all markets and all modems. We will constantly be
> posting
> updates to it so check back frequently. Note that the schedule
> distinguishes
> between 'tentative' and 'confirmed' dates. MSO approval is
>
> required for dates to be 'confirmed'.
>
> Marketing, Public Relations, Communications
>
> ONadvantage Upstream Enhancement - Additional notes
>
> ONadvantage Upstream Enhancement is a positive development for the
> @Home Network. It is also very complex as it involves network
> management
> decisions that are technical in nature and easily misconstrued by
> subscribers.
> @Home strongly recommends that subscriber communication be limited to:
>
> 1.The ONadvantage letter sent out in late 1998.
> 2.The broadcast banner next to the 'Talk to Us' button on the @Home
> Home page that includes a click-through letter. This click-through
> letter is
> posted 24 hours prior to deployment and will:
> Explain ONadvantage in broad terms.
> Will inform the subscriber of the time of the brief service
> interruption.
> Will target the audience by MSO and by state and often more
> granular.
> This limits the message to those who need to know.
> 3.In both instances the following will *NOT* be mentioned:
> 128 kbps
> Upstream rate limiting
>
> This basic plan is based on the premise that subscribers wish to have a
> service
> that is fast and reliable. They want the service to be provided with a
> minimum
> amount of effort on their part. This includes network management
> decisions and
> improvements and other technical aspects of the service. Customers
> would
> prefer NOT to be dragged into technical discussions or emails.
> Furthermore, the
> concepts of 128 kbps, rate limiting, and servers are not easily
> conveyed. In fact,
> the chances for misunderstandings and miscommunications with
> subscribers is
> very great. Therefore @Home's communication plan is based on delivering
> only
> what the customer needs to know.
>
> ONadvantage should be kept low-key in the eyes of the
> subscriber.
> Ideally the customer will experience the advantages of
> ONadvantage program without ever knowing it existed.
>
> Clearly if a subscriber asks point-blank, 'am I being rate limited?',
> the answer
> must be yes. See FAQs above.
>
> Note that @Home Public relations is actively involved in shaping
> ONadvantage
> communications strategy and kept informed of all developments.
>
> Document ID #: tt352
> Review date: 1 Aug 1999
> Keywords: ONadvantage, upstream
>
> � Copyright @Home Corporation 1999 All rights reserved
>
I don't blame @home in doing that. You should see how many @home
subscribers
are abusing the service, but unnecessary flooding many of the music
related binaries
groups. Posting several hundred megabytes of binaries daily.
Alex Lam.
--
*remove the X (upper case X) if reply by e mail.
** no more M$ Windoze.
------------------------------
From: "Eric Harmon" <[EMAIL PROTECTED]>
Subject: Re: Linksys Etherfast 10/100
Date: Sun, 20 Jun 1999 13:01:08 -0400
I'm using the Linksys 10/100 in mine without a problem. I'm currently using
the 0.90 driver. I've had it connected to both 10 and 100 hubs and it
autodetected without a problem. Check
http://cesdis.gsfc.nasa.gov/linux/drivers/index.html#PCI for notes on the
drivers and options to force it to either 10 or 100.
Hopefully that will help.
Eric
Michael D. Amoroso <[EMAIL PROTECTED]> wrote in message
news:7kbuuh$58e$[EMAIL PROTECTED]...
> Just added a Linksys Etherfast 10/100 PCI in place of the old NE2000 ISA
in
> my Red Hat 5.2 system. The card is stuck in 100Mb mode even though it is
> connected to a Linksys 10Mb hub and it's supposed to be auto-sensing. All
I
> get is a bunch of collisions every time the system accesses the network.
I'm
> using a *very* vanilla system at this point with the Tulip v0.88 driver.
> The card is detected and I don't get any complaints from the system for
it.
> Any suggestions would be appreciated.
> Mike.
>
>
>
------------------------------
From: [EMAIL PROTECTED] (Georg Schwarz)
Crossposted-To: comp.sys.ibm.ps2.hardware
Subject: Re: IBM PS/2 maximum serial port speed?
Date: 20 Jun 1999 17:02:39 GMT
COMPUTERCRAFT <[EMAIL PROTECTED]> writes:
>Though it was far from an ambitious project like this, around five years ago I
setting up a PPP server with Linux isn't too ambitious either
>used a 55SX in serial communications. That model had a modern UART. The serial
>port was not the bottleneck in system performance - the hard drive size/speed
>was.
so what port speeds did you use? What software was running?
--
Georg Schwarz ([EMAIL PROTECTED], [EMAIL PROTECTED], PGP 2.6ui)
Institut f�r Theoretische Physik +49 30 314-24254 FAX -21130 IRC kuroi
Technische Universit�t Berlin http://home.pages.de/~schwarz/
------------------------------
** 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
******************************
