From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: battery life
Date: Wed, 20 Sep 2000 07:37:31 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0009200728520.7868-100000@localhost.localdomain> (raw)
In-Reply-To: <20000920140545.A644@scot-mur.demon.co.uk>
There are a number of things that will cut down on your usable battery
life. The guess that the UART uses more power when active is correct. Also
any sounds you have enabled cut down life. Hard disk usage does. If you
can cause you screen to blank out it will save a lot of power. Also eject
any and all PCMCIA cards you don't actually need at the time. (They
consume power even when not in use.)
If you really feel a need to run 24 hours on a charge, I have several
suggestions.
1. Make the processor run as slow as you can. Speed is the enemy.
2. Get as much memory as needed to avoid the hard drive.
3. Prepare to lug around either spare batteries or a huge single one.
If you are carrying this around, I think you would be better off planning
an 8 hour life span and have two batteries if needed. If your actually
using your computer for more then 8 hours in the day chances are there is
a power source you can tap. Consider that we have electricity in the house
because it is cheaper and more convenient then having the number of
batteries needed to swap them out. It is not because cords are cool.
--
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Seek simplicity -- and distrust it.
Alfred North Whitehead
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
extending a synth's life when needed to be portable Brent Harding
` rob
` Tommy Moore
` rob
` Kirk Wood [this message]
[not found] ` <Pine.LNX.4.21.0009200728520.7868-100000@localhost.localdom ain>
` battery life Brent Harding
` Kirk Wood
` extending a synth's life when needed to be portable Brent Harding
` Brent Harding
` Geoff Shang
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0009200728520.7868-100000@localhost.localdomain \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/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).