Ata 133 is xp help! and slow performance

Sulik2

Member
Mar 15, 2002
25
0
0
I just built an athlon 64 3000+ system with an aopen ak86-l motherboard. Anyways I have it running windows xp pro and I cannot get ultra ata 133 running even though my harddrive (seagate 120gig) and xp with sp1 supports it. How do you get it to run?

Also, I seem to be getting slow perfomance when opening programs. It seems to hang a sec when starting autoplay, explorer, opening a web page, etc.
Anyone know a way I can test if my comp is running slow and how to diagnose and fix it.

Thanks for the help!
 

johnjkr1

Platinum Member
Jan 10, 2003
2,124
0
0
Seagate drives are ata-100 only. Did you load all the proper drivers for your motherboard? Is DMA enabled for your drives?
 

Sulik2

Member
Mar 15, 2002
25
0
0
Haha, label me a moron, I completely forgot that my seagate didn't support ata 133, I remeber that from when I picked out the drive.
Yep, I installed all the drivers and have it running in dma 5. But my performance still seems sluggish.
OH and while I am thinking of it, has anyone ever run into this problem when first running a computer. I could only start it up once and set the bios settings. Then it wouldn't let me restart again (wouldn't post) until i used the jumper and flashed the bios. I worked with it enough times to get windows installed and then updated the bios and it stopped doing that. But then I got a checksum error when I booted, which then stopped when I installed all the drivers and got anything working. Now my computer seems to run fine, but it just seems like programs start up to slow. Could there be something stiill wrong with my bios?
 

LeetestUnleet

Senior member
Aug 16, 2002
680
0
0
Originally posted by: Sulik2
Haha, label me a moron, I completely forgot that my seagate didn't support ata 133, I remeber that from when I picked out the drive.
Yep, I installed all the drivers and have it running in dma 5. But my performance still seems sluggish.
OH and while I am thinking of it, has anyone ever run into this problem when first running a computer. I could only start it up once and set the bios settings. Then it wouldn't let me restart again (wouldn't post) until i used the jumper and flashed the bios. I worked with it enough times to get windows installed and then updated the bios and it stopped doing that. But then I got a checksum error when I booted, which then stopped when I installed all the drivers and got anything working. Now my computer seems to run fine, but it just seems like programs start up to slow. Could there be something stiill wrong with my bios?

I'm assuming you mean reset the bios, not flash (upgrade) it. If you flashed it, you may have flashed it incorrectly, in which case you need to locate your original or another compatible BIOS flash.

checksum error is interesting though ... are you overclocking ANYTHING?
 

Sulik2

Member
Mar 15, 2002
25
0
0
Thanks for the reply, yes I did mean reset not flash. And no I am not overclocking anything, I don't feel comfortable doing it :)
What exactly is a checksum error though, I have no idea what it is? And why is it interesting I had it?
 

LeetestUnleet

Senior member
Aug 16, 2002
680
0
0
Originally posted by: Sulik2
Thanks for the reply, yes I did mean reset not flash. And no I am not overclocking anything, I don't feel comfortable doing it :)
What exactly is a checksum error though, I have no idea what it is? And why is it interesting I had it?

checksum errors generally mean something was set incorrectly in your BIOS, and it automatically fixed it for you. You have to reboot and check your BIOS and resave.

When you reset your BIOS, did you also remove the battery, or did you only do the jumper? Try doing the jumper AND removing the CMOS battery (write down any important BIOS changes you've made though!).

If you got the checksum error after only rebooting the first time after flashing, then it might not be too big of an issue as the updated BIOS may have added more options and changed some existing ones incorrectly. Like I said, clear it both ways and reboot - if it gives you the checksum error on your first boot, it could be a CPU, battery, or mobo issue.

Quickie Link