From: Gregory Nowak <greg@romuald.net.eu.org>
To: jaffar@jeffstudio.net,
"Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
Subject: Re: Me or my computer or both
Date: Sun, 29 Jan 2006 20:14:16 -0700 [thread overview]
Message-ID: <20060130031416.GA11782@localhost.localdomain> (raw)
In-Reply-To: <002801c62542$150e3640$d22ad4da@jaffar57b5aa42>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There are folks here that dual boot between windows and gnu/linux,
myself included. Are you sure that your serial port is enabled in
cmos? Have you checked for, and installed any updates available for
your system's bios? Finally, do you have access to another pc? If so,
then have you tried booting any of the install cds you used on the
second machine?
Given that you say you've tried a number of install cds with the same
results, it most likely isn't your fault. Your dectalk and pc don't
seem to like each other for whatever reason, but I'm at a loss to say
what that reason might be.
Greg
On Mon, Jan 30, 2006 at 10:08:33AM +0800, jaffar@jeffstudio.net wrote:
> Hi guys. Over the past year, I have been trying to install all flavors of linux, from fedora to debiant, gentoo to grml, slackware to ubantu, all without any modicum of success. I am running a panthium i368 build machine with a windows xp box installed. I have a 2.4 gb processor, with 1.8 gb of ram and an external dectalk synth. Typing the various installation commands for the fvarious flavors of linux will either yield some nonsense from my dectalk synth when speakup tries to interact with it, or, for the majority of the linux flavors, typing in the appropriate commands during the boot prompt yields nothing at all, not even a twitter from my dectalk synth. Mind you, this failure certainly does not arise from a lack of help and assistance from list members, but try as i might with all the advise and hints given by really helpful list members, nothing seems to work. I have updated the firmware on my dectalk synth, and i have thoroughly read all installation instructions for all the various installation procedure which accrues with the different linux flavors, but i've had 0 success so far. So what have i got to do next, that's my biggest question. I am very interested to venture into linux, but success with it seems to have eluded me. If there is anyone of you here running both windows xp and linux on the same machine, I'd certainly be interested to hear from you. All help given to a desperate guy here would be greatly appreciated. Cheers!
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD3YSI7s9z/XlyUyARAhKCAKCZPTPeDL8zkjwv4QdNvyCB63DIqACgquE2
dq8rCagrMu91YQ3TZwJJDEE=
=Nb27
-----END PGP SIGNATURE-----
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
jaffar
` Gregory Nowak [this message]
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=20060130031416.GA11782@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--cc=jaffar@jeffstudio.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).