By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,961 Members | 1,665 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,961 IT Pros & Developers. It's quick & easy.

INFO: HP machine with hyperthreading does not like Access 2000

P: n/a
A client had this configuration. Our app would crash loading more than
350 rows into a particular combobox. Client worked with HP on
potentially returning the brand new machines (dual-core CPU), when
they suggested turning off hyperthreading in BIOS. It fixed the
problem. This apparently is not a problem with Access 2003, nor with a
Dell machine and Access 2000.

-Tom.

Oct 3 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Tom van Stiphout <no*************@cox.netwrote in
news:jb********************************@4ax.com:
A client had this configuration. Our app would crash loading more
than 350 rows into a particular combobox. Client worked with HP on
potentially returning the brand new machines (dual-core CPU), when
they suggested turning off hyperthreading in BIOS. It fixed the
problem. This apparently is not a problem with Access 2003, nor
with a Dell machine and Access 2000.
All Intel CPUs, or AMD?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Oct 3 '06 #2

P: n/a
All Intel CPUs.
-Tom.
"David W. Fenton" <XX*******@dfenton.com.invalidwrote in message
news:Xn**********************************@127.0.0. 1...
Tom van Stiphout <no*************@cox.netwrote in
news:jb********************************@4ax.com:
>A client had this configuration. Our app would crash loading more
than 350 rows into a particular combobox. Client worked with HP on
potentially returning the brand new machines (dual-core CPU), when
they suggested turning off hyperthreading in BIOS. It fixed the
problem. This apparently is not a problem with Access 2003, nor
with a Dell machine and Access 2000.

All Intel CPUs, or AMD?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Oct 3 '06 #3

P: n/a
On Tue, 3 Oct 2006 09:33:24 -0700, "Tom van Stiphout"
<no******************@kinetik-it.comwrote:

Tried it on a dual-core AMD machine, and failed the same way.
Set the Processor Affinity for the MsAccess process to one CPU, and
all is happy. Except the customer who bought an expensive CPU :-)

-Tom.

>All Intel CPUs.
-Tom.
"David W. Fenton" <XX*******@dfenton.com.invalidwrote in message
news:Xn**********************************@127.0.0 .1...
>Tom van Stiphout <no*************@cox.netwrote in
news:jb********************************@4ax.com :
>>A client had this configuration. Our app would crash loading more
than 350 rows into a particular combobox. Client worked with HP on
potentially returning the brand new machines (dual-core CPU), when
they suggested turning off hyperthreading in BIOS. It fixed the
problem. This apparently is not a problem with Access 2003, nor
with a Dell machine and Access 2000.

All Intel CPUs, or AMD?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Oct 4 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.