From: Justin Mierta <Crazed_Cowboy@stones.com>
To: lung@theuw.net, linux-kernel@vger.kernel.org
Subject: Re: ECS k7s5a motherboard doesnt work
Date: Sun, 28 Oct 2001 19:58:37 -0500 [thread overview]
Message-ID: <3BDCA9BD.9030308@stones.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0110281907240.22555-100000@narboza.theuw.net>
I'm using this archive:
http://www.uwsg.indiana.edu/hypermail/linux/kernel/index.html
and nowhere can i find the thread you mentioned.
Also, this motherboard works *perfect* in windows (which is
unfortunately where i've been stuck) -- it hasnt crashed in the last
several weeks i've been using it! (probably the longest uptime i've ever
seen for a windows machine that's actually being used) So I *seriously*
doubt its bad hardware.
Can you maybe give me a link to the thread you mention?
Justin
lung@theuw.net wrote:
>You might be interested in my recently initiated tread:
>
>Subject: Repeatable File Corruption (ECS K7S5A w/SIS735)
>
>
>You should always check the archives before posting. You problems seem
>much worse than mine, so I'm going to assume there is something else not
>working for you. Alan's suggestion that you might have some bad hardware
>makes sense. RAM is a common culprit. Good luck.
>
>
next parent reply other threads:[~2001-10-29 0:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0110281907240.22555-100000@narboza.theuw.net>
2001-10-29 0:58 ` Justin Mierta [this message]
[not found] <Pine.LNX.4.10.10110291523140.27909-100000@coffee.psychology.mcmaster.ca>
2001-10-29 20:53 ` ECS k7s5a motherboard doesnt work Justin Mierta
2001-11-02 14:03 ` Marco Colombo
2001-10-29 16:40 Daniel Freedman
[not found] <E15y9q4-0002ER-00@the-village.bc.nu>
2001-10-29 15:10 ` Justin Mierta
2001-10-29 19:30 ` Adrian Burgess
2001-10-29 19:33 ` lung
2001-10-31 8:30 ` Zephaniah E. Hull
2001-10-31 10:52 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-10-28 23:18 Justin Mierta
2001-10-28 23:50 ` Alan Cox
2001-10-29 8:02 ` Justin Mierta
2001-10-29 17:42 ` Joel Jaeggli
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=3BDCA9BD.9030308@stones.com \
--to=crazed_cowboy@stones.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lung@theuw.net \
/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