A7V8X-X and Athlon XP1600+

[Dave B3650]

according to some blurb ive read, this mobo only works with Athlon XP 2700+
cpu's,

I would like to use one with my old Athlon XP1600+ chip but am not sure if
it would work.

Has anyone got any info ?

Many Thanks

DaveB

 

[Iconoclast]

according to some blurb ive read, this mobo only works with Athlon XP 2700+
cpu's,

I would like to use one with my old Athlon XP1600+ chip but am not sure if
it would work.

Has anyone got any info ?

Many Thanks

DaveB

Mine's been working fine with an XP 2100+ since last year - no probs
whatever.

 

[Dave B3650]

great, just what i wanted to hear........the website says 2700+ but i
reckoned so long as its an Athlon XP there shouldnt be any problems.

now.....is there anyone there with one of them using 1600's to make me feel
even better.

Dave

 

[Creeping Stone]

great, just what i wanted to hear........the website says 2700+ but i
reckoned so long as its an Athlon XP there shouldnt be any problems.

now.....is there anyone there with one of them using 1600's to make me feel
even better.

Feel Great -
I ran it fine with a Duron 1200.

 

[Creeping Stone]

great, just what i wanted to hear........the website says 2700+ but i
reckoned so long as its an Athlon XP there shouldnt be any problems.

now.....is there anyone there with one of them using 1600's to make me feel
even better.

Feel Great - ( )
I ran it fine with a Duron 1200.

- sorry I didnt mean to sound abrupt :[

ps.
Anyone getting problems since moving to bios 1007 or 1008?
I havent had any mysterious beeping or crashing for 4 days now
since changing back to 1006 - but had to completely repair windows after
the change because the system registry hive stopped booting immediately
after going back. Bootscreen said it was corrupt, but I rather doubt is was
damaged or changed, I think it might have gotten confused with the changed
bios. Im even slighlty suspicious it had a Kernel mode trojan ?!

- Or the old bios was damaged.

 

[Dave B3650]

CREEPING STONE.......many many thanks.........you's guy know more than the
peeps in the shops.....

aaah......nem mobo tomorrow nite (been on the drink tonite and dont wanna
fry myself,lol)

P.S. dont know what bios i've got yet.......will find out soon tho.

AGAIN,, many thanks to all - just what these groups are for

DaveB : )

great, just what i wanted to hear........the website says 2700+ but i
reckoned so long as its an Athlon XP there shouldnt be any problems.

now.....is there anyone there with one of them using 1600's to make me feel
even better.

Feel Great - ( )
I ran it fine with a Duron 1200.

- sorry I didnt mean to sound abrupt :[

ps.
Anyone getting problems since moving to bios 1007 or 1008?
I havent had any mysterious beeping or crashing for 4 days now
since changing back to 1006 - but had to completely repair windows after
the change because the system registry hive stopped booting immediately
after going back. Bootscreen said it was corrupt, but I rather doubt is was
damaged or changed, I think it might have gotten confused with the changed
bios. Im even slighlty suspicious it had a Kernel mode trojan ?!

- Or the old bios was damaged.

 

[Creeping Stone]

CREEPING STONE.......many many thanks.........you's guy know more than the
peeps in the shops.....

- a different focus ;]

aaah......nem mobo tomorrow nite (been on the drink tonite and dont wanna
fry myself,lol)

Aye, see how it goes - should be plain sailing.

P.S. dont know what bios i've got yet.......will find out soon tho.

AGAIN,, many thanks to all - just what these groups are for

Yeah - the essential non-politcal topic helps, I still manage to loose it
sometimes though

There sould prob be an a7v8x-x faq by now - to fall back on when the
queries outnumber available replies

....../'scratches chin

 

[RonK]

Built one just last month for a customer - A7V8X-X with AMD 1800+.
Runs great !

CREEPING STONE.......many many thanks.........you's guy know more than the
peeps in the shops.....

aaah......nem mobo tomorrow nite (been on the drink tonite and dont wanna
fry myself,lol)

P.S. dont know what bios i've got yet.......will find out soon tho.

AGAIN,, many thanks to all - just what these groups are for

DaveB : )

=|[ Dave B3650's ]|= wrote:

great, just what i wanted to hear........the website says 2700+ but i
reckoned so long as its an Athlon XP there shouldnt be any problems.

now.....is there anyone there with one of them using 1600's to make

me

feel

even better.


Feel Great - ( )
I ran it fine with a Duron 1200.

- sorry I didnt mean to sound abrupt :[

ps.
Anyone getting problems since moving to bios 1007 or 1008?
I havent had any mysterious beeping or crashing for 4 days now
since changing back to 1006 - but had to completely repair windows after
the change because the system registry hive stopped booting immediately
after going back. Bootscreen said it was corrupt, but I rather doubt is was
damaged or changed, I think it might have gotten confused with the changed
bios. Im even slighlty suspicious it had a Kernel mode trojan ?!

- Or the old bios was damaged.

 

[Dave B3650]

Excellent news...and there was me thinking i'd been sold a
turkey......actually bloke in shop siad if it didnt work he'd take it back.

It's not a bad old world is it really.

I'll do pc tomorrow nite hopefull and if all goes well, report back soon



The beers r on me, so long as you live near me and r in the pub on sat nite.


Thanx all


Dave

Built one just last month for a customer - A7V8X-X with AMD 1800+.
Runs great !

CREEPING STONE.......many many thanks.........you's guy know more than the
peeps in the shops.....

aaah......nem mobo tomorrow nite (been on the drink tonite and dont wanna
fry myself,lol)

P.S. dont know what bios i've got yet.......will find out soon tho.

AGAIN,, many thanks to all - just what these groups are for

DaveB : )

=|[ Creeping Stone's ]|= wrote:

=|[ Dave B3650's ]|= wrote:

great, just what i wanted to hear........the website says 2700+ but i
reckoned so long as its an Athlon XP there shouldnt be any problems.

now.....is there anyone there with one of them using 1600's to make

me

feel
even better.


Feel Great -
( )
I ran it fine with a Duron 1200.

- sorry I didnt mean to sound abrupt :[

ps.
Anyone getting problems since moving to bios 1007 or 1008?
I havent had any mysterious beeping or crashing for 4 days now
since changing back to 1006 - but had to completely repair windows after
the change because the system registry hive stopped booting immediately
after going back. Bootscreen said it was corrupt, but I rather doubt

is
was

damaged or changed, I think it might have gotten confused with the changed
bios. Im even slighlty suspicious it had a Kernel mode trojan ?!

- Or the old bios was damaged.

 

[R45six]

I havent had any mysterious beeping or crashing for 4 days now
<snip>

Wasn't there a virus that was supposed to beep at various intervals this
week ?
http://news.bbc.co.uk/1/hi/technology/3525627.stm

 

[RonK]

I'd like to take you up on that beer but it's a long drive, swim, from
Ontario Canada.

Excellent news...and there was me thinking i'd been sold a
turkey......actually bloke in shop siad if it didnt work he'd take it back.

It's not a bad old world is it really.

I'll do pc tomorrow nite hopefull and if all goes well, report back soon



The beers r on me, so long as you live near me and r in the pub on sat nite.


Thanx all


Dave

Built one just last month for a customer - A7V8X-X with AMD 1800+.
Runs great !

CREEPING STONE.......many many thanks.........you's guy know more than the
peeps in the shops.....

aaah......nem mobo tomorrow nite (been on the drink tonite and dont wanna
fry myself,lol)

P.S. dont know what bios i've got yet.......will find out soon tho.

AGAIN,, many thanks to all - just what these groups are for

DaveB : )





=|[ Creeping Stone's ]|= wrote:

=|[ Dave B3650's ]|= wrote:

great, just what i wanted to hear........the website says 2700+

but

i

reckoned so long as its an Athlon XP there shouldnt be any problems.

now.....is there anyone there with one of them using 1600's to

make
me

feel
even better.


Feel Great -
( )
I ran it fine with a Duron 1200.

- sorry I didnt mean to sound abrupt :[

ps.
Anyone getting problems since moving to bios 1007 or 1008?
I havent had any mysterious beeping or crashing for 4 days now
since changing back to 1006 - but had to completely repair windows after
the change because the system registry hive stopped booting immediately
after going back. Bootscreen said it was corrupt, but I rather doubt is
was
damaged or changed, I think it might have gotten confused with the changed
bios. Im even slighlty suspicious it had a Kernel mode trojan ?!

- Or the old bios was damaged.

 

[Creeping Stone]

I havent had any mysterious beeping or crashing for 4 days now

<snip>

Wasn't there a virus that was supposed to beep at various intervals this
week ?
http://news.bbc.co.uk/1/hi/technology/3525627.stm

Ta - thats an email attached virus, which I/most of us wouldnt get
caught out by. Most viruses/trojans ive seen (just a couple) appear
conveniently in the process monitor and trigger my firewall. There is a
nasty rare kind which might get installed along with drivers, that
antivirus and debuggers cant spot at all, unless they can scan the disk
from a separate, uninfected OS installation -and know what theyre looking
for.

A keylogger I ran accidently on another machine last week, hid from
taskmanager but was caught out by sysinternals process explorer.

I think the tricky threat is from code which can slip in through the
network and take advantage of unpatched, unfiltered or newly discovered
holes in common windows network services, or common listening programs like
messengers & media players. They can get executed by taking advantage of
possible circumstances which developers once routinely overlooked (until
virus writers enlightened them - like buffer overruns.

It was driving me crazy getting this *unlogged* beep every once a while and
having an unstable machine which was improved but not cured by
underclocking - but now Ive deleted the old installation, Ill never know if
something nasty was doing it, or maybe the Bios itself was slightly
corrupted.

Rgds,