Recent content by Ren2610

  1. R

    HELP - can't get lower CPU multipliers to work on Asus A7N8X nForce2 mobo

    It seems like you can only use multipliers above 15x in your case. http://www.ocworkbench.com/2002/asus/a7n8x/a7n8xgallery3.htm The A7N8X bios in itself appears to be buggy. I have a locked palo 1800+, but all the multipliers are selectable for it in bios ( according to the manual, that...
  2. R

    nforce 2 Dual DDR questions

    You just need to put them in different banks. 1 & 3, 2 & 3, or all 3 ( where 2 sticks will be on the same controller ). I'm not 100% sure, but I believe you can use any size sticks @ any speed ( it'll just run at the slowest of the pair is you choose SPD ).
  3. R

    A7N8X Question for you propeller-heads out there.

    Most options can be configured in Bios. The only notable thing you cannnot do in bios is disable the SATA serial headers ( requires a jumper to be set ). I left mine to the default postion ( enabled ), and it delays the boot up time by 10 secs by looking for SATA drives.
  4. R

    A7N8X dual ch. ddr/sisoft sandra mem benchmark

    I'm getting rather low scores as well. Running @ 133 FSB and the memory in sync, I get 2085/1975 using 2,2,2,5 timings ( 2 x 256MB Crucial PC2100 ). I've updated the drivers with no effect.
  5. R

    USB problem on ASUS P4B533 with high FSB 166+

    I can't vouch for 166+ FSB... but I've been running at 165 FSB on the P4B533 for a few weeks now, with 2 USB 1.1 devices, and 1 2.0 device. No problems.
  6. R

    RedHat 8.0 Install Stuck

    Did you test all 3 CDs before the install process? It could be a bad image/CD.
  7. R

    Prime95 in WinMe and WinXP

    I don't believe that's it. I dual boot between XP and Me, and in XP 163 FSB is fine... in Me it's not ( when running Prime95 ). :confused:
  8. R

    Prime95 in WinMe and WinXP

    I've been running my P4 1.6A @ 163 FSB for about a week now, and ran Prime95 in WinXP Pro for 24hrs straight to check the stability. I also tried 166 FSB, and ran Prime95 for 12 hours without any problems, but 3DMark2001SE shows a few visual anomalies when I loop it, so I went back to 163 FSB...