Archived from groups: alt.comp.periphs.mainboard.abit (
More info?)
only comment I can have regarding the ram is that the 875 and 865 chipset
series boards seem to be *real* picky on the ram. any instability in that
area seems to show right quick.
--
Thomas Geery
Network+ certified
ftp://geerynet.d2g.com
ftp://68.98.180.8 Abit Mirror <----- Cable modem IP
This IP is dynamic so it *could* change!...
over 130,000 FTP users served!
^^^^^^^
"Gareth Jones" <usenet@nospam.demon.co.uk> wrote in message
news:IIxxnxSfxzrAFwym@nospam.demon.co.uk...
> In message <40af2204$0$4588$db0fefd9@news.zen.co.uk>, Dion L Heap
> <NoSpam@ThankYou.Com> writes
> >> I'm running an IC7-G with an 800 Mhz 2.8c CPU and Corsair XMS4400 ram
at
> >> 1:1. no issues and I am currently running the fsb at 247 stable.
> >
> >Same board with a 3.2c CPU, and corsair xms3700 CAS 2 at 5:4 with FSB at
238
> >giving me 3.8 gig on the cpu, read your post below asking for drives and
gfx
> >card, on the IC7-G it's immaterial since those buses can be locked at
66/33
> >despite the fsb speed, however, mine is a 9800xt and drives are sata raid
0
> >and are Seagate Barracuda VII 7200RPM 80GB Serial ATA 150 8MB Cache.
>
> And as a 'me too' ... with a couple of hopefully valid points (and
> questions)
>
> Abit IS7-G running
> Radeon 9700 AIW pro
> 1GB (512*2) PC3200 RAM.
>
> Was using twinmos. System was very stable at the stock 2.4GHz (800MHz HT
> chip) but for some strange reason I couldn't really overclock it at all
> (even with locking everything and lowering the RAM ratio so this wasn't
> overclocked).
> However I had to shuffle some components around recently, and swapped to
> some pretty ordinary Geil RAM - all of a sudden, its doing 3GHz 24/7
> with ease. Very strange, and I still don't understand why - anyone??
>
> Lastly, The only instability on this board was to do with the two maxtor
> 120GB drives in a SATA RAID0 config.
> These were PATA drives with Abit convertors on.
> We used to get the occasional blue screen. Having swapped over to 2 *
> 160 GB proper SATA drives and moved the original drives to another
> machine, I'm pretty sure now that the crashing was due to not having an
> updated SATA controller BIOS _AND_ (that's in capitals for a reason!!)
> having a matching version number windows driver.
>
> Machines rock solid now.
>
>
> --
> __________________________________________________
> Personal email for Gareth Jones can be sent to:
> 'usenet4gareth' followed by an at symbol
> followed by 'uk2' followed by a dot
> followed by 'net'
> __________________________________________________