That's weird in a way since FSB1066 = 266MHz base clock,
FSB1333 = 333 MHz base clock.
Even WITH 266MHz (FSB1066) CPUs I thought it was COMMON for people to overclock
their FSB/base clock to like 400-500 MHz, obviously being equal to or higher
than the mere 333MHz value that would match a FSB1333 CPU's specification.
I know nothing much about the 680i chipset, but I thought it was supposed to
be at least OK for overclocking, so it seems weird if it cannot hit 333MHz to get
FSB1333 even if it's not "supported" officially.
Similarly I didn't think the Vcore requirements for the Q6850 were that different
than the QX6800, and if anything less power being needed for the former. So the
motherboard OUGHT to handle that is a guess I'd make.
So if the CPU just plain WON'T work then I'd assume it's a BIOS bug that causes
the settings for Vcore / Frequency or whatever to just be wrong for that CPU,
and if you can at least get into BIOS setup, I'd assume you could manually set
the timing, volts, and frequency to make it work.
Now VISTA64 on the other hand I've had direct personal ....experience.... with,
and to say that its installer is a flaming load of buggy cr*p would be to put it kindly.
I installed XP32 SP2 on a system on one hard disk, that took like 45 minutes, totally
no problems.
Immediately after I installed XP32 on that box I installed VISTA64 on another hard
disc without changing a thing about the hardware.
Six HOURS of constant VISTA64 installer crashes, installer bugs / failures later
I was tearing my hair out thinking it was just not POSSIBLE to install VISTA64.
After hours more of pouring over billions of similar users problem reports and
hypothetical "solutions" online I was going to give it ONE MORE TRY after tweaking
a few more things.
I changed the IDE Master/Slave jumper for my *EXTERNAL USB* (i.e. shouldn't MATTER)
DVD ROM install drive to Master.
I changed some of the IDE hard disk settings for the internal drives in trivial ways like
turning off DMA mode, forcing PIO 4, etc. I tried new permutations of forcing VISTA
to preload chipset, USB, IDE, LAN, etc. drivers "pre-install" though I'd done all the
sane configurations many times already.
I changed some stuff like disabling or enabling Legacy USB device support in the BIOS,
etc. Basically nothing that ought to matter a bit.
Next time I tried it the installer continued and it installed. I don't know exactly WHAT
made it happy after the 20th+ try of tweaks, but something that SHOULDN'T matter
did, and that made the difference.
So I'd bet more on your installer problem being a VISTA bug possibly in
conjunction with a (solvable?) motherboard BIOS issue about setting proper
volts/MHz/clocks for your CPU.
IMHO if you can boot a MEMTEST86+ CD and survive a pass of MEMTEST, you
ought to be able to run VISTA64 giv
Facebook
Twitter