From: David Hollister <david@digitalaudioresources.org>
To: Anton Altaparmakov <aia21@cus.cam.ac.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Conquering the Athlon optimization troubles
Date: Thu, 13 Sep 2001 19:22:23 -0700 [thread overview]
Message-ID: <3BA169DF.3060306@digitalaudioresources.org> (raw)
In-Reply-To: <Pine.SOL.3.96.1010914012401.21012A-100000@virgo.cus.cam.ac.uk>
Anton Altaparmakov wrote:
> On Thu, 13 Sep 2001, David Hollister wrote:
>
>>My motherboard is the Epox 8KTA3+, and I'm running an Athlon 1.4GHz.
>>
>>Epox was kind enough to mail me a new BIOS chip to replace my locked
>>chip. This chip contained a version of the BIOS that I believe was
>>dated 8/6/2001 (I don't feel like rebooting again to find out). Suffice
>>it to say, that version is not listed on their website, but there is an
>>even newer one. For anybody with the 8KTA3 or 8KTA3+, the BIOS page is
>>located at http://www.epox.com/html/english/support/motherboard/bios/8kt3.htm
>>
>
> Maybe you meant 9/6/2001. That is the latest available version. From only
> 5 days ago.
No. I just rebooted to check. It's dated 8/16/2001. Strange.
>>Anyway, I was running the BIOS dated 3/5/2001 up until now.
>>
>
> That was ancient! There were quite a few releases between then and now.
But I couldn't update because my BIOS chip was locked.
>>The point to all this is that with the newer BIOS, my machine is now up and
>>running absolutely fine with Athlon optimization turned on.
>>
>
> Congratulations! (-: I would recommend you to run a long memtest86 as well
> in particular tests 5 and 8. - They are the ones that used to fail for me
> with the inappropriate memmory settings...
Thanks for the suggestion.
--
David Hollister
Driversoft Engineering: http://devicedrivers.com
Digital Audio Resources: http://digitalaudioresources.org
next prev parent reply other threads:[~2001-09-14 2:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 23:54 Conquering the Athlon optimization troubles David Hollister
2001-09-14 0:28 ` Anton Altaparmakov
2001-09-14 2:22 ` David Hollister [this message]
2001-09-14 7:25 ` brian
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=3BA169DF.3060306@digitalaudioresources.org \
--to=david@digitalaudioresources.org \
--cc=aia21@cus.cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
/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 NNTP newsgroup(s).