A7V133 w/ XP 1600+ issues??

XRaider

Senior member
Mar 1, 2001
226
0
0
I know this has been a topic b4, and I can't find it. Plus I am on a slow a$$ PC. I plan on purchasing a XP 1600+ Retail and placing it on my Asus A7V133 MB -for my bro. I believe my MB is rev 1.04 and I flashed it with the updated bios (not sure which vers.) awhile ago. I will head home for lunch to verify what rev. the board is. This board is currently in a static bag waiting to go in my bro's PC (upgrade), in 2 weeks. I heard of some issues with XP's with this mobo, but I have seen in here that these issues have been with 1800+ and higher.. is this correct ????? Can you guys give me some advice on this? Thanks! -Also posted this in CPU forum.
:confused:
 

Boonesmi

Lifer
Feb 19, 2001
14,448
1
81
i belive asus officially says that the a7v133 rev 1.05 and newer support all of the xp cpu's

but... most people have 1.04 :)
1.04 still works with all of the xp cpu's but from what i understand the motherboard sometimes has problems auto detecting the cpu, meaning you may have to set it up with the dipswitches (for example 1600+ actually runs at 1.4ghz so you would have to manually set the motherboard, via the dipswitches, to run 133mhz fsb and set the multiplier at 10.5x... this would give you 133x10.5 or 1.4ghz)
 

XRaider

Senior member
Mar 1, 2001
226
0
0
Thank you very much sir.! I will try your recommendations out, or B: Just buy a T-bird 1.4
 

cmaMath13

Platinum Member
Feb 16, 2000
2,154
0
60
I just put a AMD Athlon XP 1900+ cpu on my Asus A7V133 (1007 bios) and no problems. In fact, on post it recongizes it as a 1900+.
 

colonel

Golden Member
Apr 22, 2001
1,783
20
81
I have same board rev 1.04 and I was thinking to get the XP athlon, but heard the overclocking is hard, and useless sometimes, so I got the 1.4 Tbird. I dont doubt It will work, but Asus did not said a word about the issue, third parties came over with the conclusion.
 

Wind

Diamond Member
Jul 22, 2001
3,034
0
0


<< I have same board rev 1.04 and I was thinking to get the XP athlon, but heard the overclocking is hard, and useless sometimes >>

Coz on nearly all occasion, the PCB ver 1.04 will only run stable using jumper mode & not jumper free mode. Jumper mode limit O/Cing abilities.
 

Wind

Diamond Member
Jul 22, 2001
3,034
0
0


<< I know this has been a topic b4, and I can't find it. Plus I am on a slow a$$ PC. I plan on purchasing a XP 1600+ Retail and placing it on my Asus A7V133 MB -for my bro. I believe my MB is rev 1.04 and I flashed it with the updated bios (not sure which vers.) awhile ago. I will head home for lunch to verify what rev. the board is. This board is currently in a static bag waiting to go in my bro's PC (upgrade), in 2 weeks. I heard of some issues with XP's with this mobo, but I have seen in here that these issues have been with 1800+ and higher.. is this correct ????? Can you guys give me some advice on this? Thanks! -Also posted this in CPU forum.
:confused:
>>

b4 u proceed.
1. Update to bios 1007 first.
2. Boot up the PC.
3. Go into bios & load default settings.
3. Save & Reboot.
4. Then only put the new XP.
5. Manually set to jumper mode & adjust the jumper as per ur XP setting.
6. Fire-up.
 

rimshaker

Senior member
Dec 7, 2001
722
0
0
Always try using jumperfree and default modes first, just to see if it might work. You never know... you might have a nice surprise if you're lucky ;) I got an overclocked XP2000+ in my 1.04 board, jumperfree.
 

Wind

Diamond Member
Jul 22, 2001
3,034
0
0


<< Always try using jumperfree and default modes first, just to see if it might work. You never know... you might have a nice surprise if you're lucky ;) I got an overclocked XP2000+ in my 1.04 board, jumperfree. >>


A good idea...u might be lucky.
 

Wind

Diamond Member
Jul 22, 2001
3,034
0
0
To add on, if u got NO POST in jumperfree mode...just clear the CMOS & set to jumper mode. Set RAM timing to SPD also...
 

cmaMath13

Platinum Member
Feb 16, 2000
2,154
0
60
I used the jumpers. From what I understand to run a 266MHz FSB cpu on the A7V133, you must at least set FSB to 133MHz. I went ahead and set multiplier to 12, too.