Came out 2nd best overall & behind by only 0.01% though ...Quote:
Originally Posted by Ace-a-Rue
It's fair to say that they all were pretty closely grouped which isn't surprising really.
Printable View
Came out 2nd best overall & behind by only 0.01% though ...Quote:
Originally Posted by Ace-a-Rue
It's fair to say that they all were pretty closely grouped which isn't surprising really.
Almost all of the boards in the TH review were scoring so close together that the difference wasn't statistically significant.
need more info, what are you tring to do exactly?Quote:
Originally Posted by xTr33m sammich!
Hmmm...I just got my "Snake" and it will be replacing my DS3...I do some comparisons. I've simply had it with boot issues with the DS3
When first booting up XP (32-bit) the internet works for about 30 seconds, then stops working for about 30 seconds, then works fine until I reboot again. I'm using the first NIC. The second one doesn't do that. Anyone else get this? I've used XP Pro and XP MCE. Tried latest realtek driver and the one on the Abit Disc.
EDIT:Quote:
Originally Posted by derektm
Nevermind... it does it on BOTH onboard nic's. Right after Windows XP booted up I started the ping. Here what I get:
Edit 2:Code:C:\Documents and Settings\Derek>ping -t google.com
Pinging google.com [64.233.187.99] with 32 bytes of data:
Reply from 64.233.187.99: bytes=32 time=51ms TTL=242
Reply from 64.233.187.99: bytes=32 time=50ms TTL=242
Reply from 64.233.187.99: bytes=32 time=51ms TTL=242
Reply from 64.233.187.99: bytes=32 time=50ms TTL=242
Reply from 64.233.187.99: bytes=32 time=51ms TTL=242
Reply from 64.233.187.99: bytes=32 time=52ms TTL=242
Reply from 64.233.187.99: bytes=32 time=55ms TTL=242
Reply from 64.233.187.99: bytes=32 time=51ms TTL=242
Reply from 64.233.187.99: bytes=32 time=54ms TTL=242
Reply from 64.233.187.99: bytes=32 time=52ms TTL=242
Reply from 64.233.187.99: bytes=32 time=51ms TTL=242
Reply from 64.233.187.99: bytes=32 time=51ms TTL=242
Reply from 64.233.187.99: bytes=32 time=51ms TTL=242
Reply from 64.233.187.99: bytes=32 time=52ms TTL=242
Reply from 64.233.187.99: bytes=32 time=51ms TTL=242
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.187.99: bytes=32 time=52ms TTL=242
Reply from 64.233.187.99: bytes=32 time=53ms TTL=242
Reply from 64.233.187.99: bytes=32 time=51ms TTL=242
Reply from 64.233.187.99: bytes=32 time=52ms TTL=242
Reply from 64.233.187.99: bytes=32 time=50ms TTL=242
Reply from 64.233.187.99: bytes=32 time=51ms TTL=242
Reply from 64.233.187.99: bytes=32 time=50ms TTL=242
Ping statistics for 64.233.187.99:
Packets: Sent = 34, Received = 22, Lost = 12 (35% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 55ms, Average = 51ms
Control-C
^C
C:\Documents and Settings\Derek>
Looks like this Realtek onboard doesn't like my DD-WRT router. Plugged in the net directly and this issue went away :up:
i run one to show you...be back:)Quote:
Originally Posted by mercyless
Quote:
Originally Posted by mercyless
here are the results for the IP35 Pro at 390@9X = 3510 Mhz (loose and semi-tight timings) exactly what i was using on the QuadGT.Quote:
Originally Posted by Ace-a-Rue
bottom pic is the QuadGT:
I recieved my IP35 PRO yesterday so I'll be posting my results over this weekend, I've also updated the original 1st page showing memory compatability as well as the latest drivers for the motherboard.
Theirs a nice article on the Coolaler Forum regarding the ABIT IP35 PRO, if anyone is interested in reading CLICK HERE :cool:
To any mods reading - I hope I'm not breaching any forum rules regarding the above even though I have read the rules I'm not sure, if I am please let me know & I will edit this thread asap as the last thing I would want is the thread to be locked.
Many thanks,
Nelly.
multi rail psu is bs but not cause its "marketing bling"Quote:
Originally Posted by Neon Biker
its some EU mandate :down: saying you cant have more than X watts on any single "user accessible interface"
somewhere around 250 i think
Yeah, I know, I think it was Intel who came up with it though, and not the EU, but anyway, later it was turned into a marketing bling.
Back on topic: Has anyone tested the cheapo IP35-E yet? Or at least the IP35 vanilla since it looks the same except for a few extra features, cuz I'm just about to place the order. :D
Update on my ip35-e woes. Firstly the e6300 appears to be dead and I still have the same symptoms with an e2160, so either the board is knackered or the cpu is not supported. Anyone else tried an e2160 yet? Abit UK cant tell me one way or another if the e2160 is supported with the shipping bios and have contacted taiwan. I see there is a new bios out but of course I have no way of flashing without a cpu it will recognize. So all in all no further forward. :brick: :brick:
I've been in contact with Abit Taiwan by the way & at this present time their is definitly no Beta Bios for the Abit IP35 PRO at this present time.
If anyone does have any issues with any of the boards which needs addressing please use this link:- ABIT Technical Support
I'm going to put a request in for 1T Command Rate. :)
Damn, that's a bummer. I was thinking of an E21x0 too, but now that option is definitely out. Wondering about an E4300... will it behave the same because of the 800MHz FSB or maybe it'll be OK? :confused:Quote:
Originally Posted by davvy76
If I was you, maybe contact Abit UK again & ask if you can send the bios chip to them & let them flash it with the very latest bios?? They shoudnt charge you for this as this is a bios bug which came with the original IP35-E by the sounds of things.Quote:
Originally Posted by davvy76
hey guys got a review of the board finished
http://www.xtremesystems.org/forums/...d.php?t=149024
feel free to comment on anything else you want tested :)
So which one is offical??:rofl:Quote:
Originally Posted by Johnny Bravo
I've got a question for you but I'll post it on your thread. :) Your reviews are like a breath of fresh air, Excellent. :clap: :up: :)Quote:
Originally Posted by Johnny Bravo
right. removed them yesterday, fiddled with the pipes a bit. now the NB and mosfet heatsink lays nearly flat.Quote:
Originally Posted by derektm
PWN temps dropped 11 c after doing that!
nb is roomtemp to the touch..compared to the inferno my last p5n32 was on the nb.. this is a postive thing
stock cooling seems fine, with some fans blowing in its general direction
Boards borked mate, e6320 and p4 631 no booty :mad: , local computer shop thinks i've got a cpu fetish :ROTF: , Just as well I know the owner or i'd be severely out of pocket!Quote:
Originally Posted by Nelly
Upon reading the above few posts it seems there are problems with the IP35-e. Does that mean I should hold off till its fixed?
so there's 1 DOA board? :rolleyes:
It happens to all mobo mfrs.
im working on getting a screenshot posted but so far with this board i have gotten into windows stable and gaming at 463 FSB on a E6420 so its running at 3.7 my ram is running at 926 ( its supertalent ddr2 800) with timmings of 4-4-3-9
my cooler is a Coolit eliminator
it idles at around 25c and load is somewhere near 40-45
super pi is running its 1m test at around 13-14 seconds
Im new here but it was these forums that encourged me to go with this board. so far i am very happy
This is my first from scratch build in a few years. I got the e6300 (L625A705, packed 7/06) last year and ran it on an 865 chipset board until I decided on the IP35 Pro. I'm glad I waited. I almost bought a 965 chipset board earlier but the memory prices scared me away. Once memory prices dropped I waited for the 35 chipset to arrive. I've suffered bad customer support with ASUx in the past and really wanted to avoid purchasing any of their products again. I've had a number of ABIT boards in the past and have never had a problem with them and this IP35 Pro is no exception. With less than a day of tweaking I've gotten this to combination to run at 3.45 ghz in orthos for 8 hours. It did fail after 3 hours of Orthos at 3.5 ghz. I could increase my cpu core voltage past 1.42 but I'm a little wary. Maybe later. Here are the specifics:
IP35 Pro, BIOS F10
e6300, L625A705, pack date 7/22/2006 @ 1.42 volts
Thermalright Ultra 120 Extreme, arctic silver, scythe sflex @1500 rpm pushing
Crucial Ballistix PC2-8500, 2x1gb @ 1:1 ratio, 2.2 volts
NB voltage increased to 1.37 at 3500mhz, 1.33 at 3450mhz.
Stable orthos > 8 hrs at 3450 mhz with memory @ 4,4,4,12. Super PI < 16 sec. with 1M calculation.
Orthos ran for over 3 hrs at 3500 mhz with memory relaxed. Screen shot included if i can figure how to post it. I think it will post but I've had to use a low quality jpg. Hopefully you can read it.
If anyone has suggestions to increase stability let me know.
Thanks
i was able to do 500 FSB on my Q6600 with the board on my test bench...but...once i slid everything into the case, NO WAY!..to much heat for the chipset...i think 500 (3500 Mhz) was about the upper limit of the NB with my Q6600...i am now holding 3600 Mhz at 450 FSB with no problem at all!