Originally Posted by fonzye
I just installed windows 7 today
With prime you test the cpu for 5-6 hours I think that is enough and guess what I wake up in the morning and start my computer windows 7 loads I open up mozilla firefox and i get a freeze just like that cause windows 7 wants to.So yeah thanks I am still backing up right now and yes I game a lot to but I will dual boot with XP,I usualy game only at night so it won't be a problem booting from ubuntu into xp
Were you using 64bit XP? If not, you can't be sure that the OC isn't unstable. I've herd of problems like 32bit code running perfectly fine where 64bit code faults, all because of stability (assuming you ran 64bit Win7, if not omit that but still read on). Also, did you format? Do you know if it's not a FS issue? 5-6Hrs isn't enough to prove stability in Prime, I've seen faults right after 7hrs where a thread will die/lockup. =O Oh noes, impossible!
Blah, seriously, if you have a stability problem it WILL show up in Linux and not be nearly as friendly. I'm not here to tell you not to switch, but I will tell you that you should get that checked out and run prime for at least 12+hrs.
You should backup your data though, especially if you want to try the raid solutions out there. You also need to understand that you won't get BAC2 in Linux, period.
Originally Posted by Kolovrat
Someone say it's doesn't matter 32vs64 but i found it it's more logical and actually stable to use both 64vs64 in dual boot
It doesn't matter, not one bit. 64bit cpu's run 32bit code exactly the same, well.... You get what I mean. Since grub (any bootloader) runs in real mode (bios level) it doesn't actually have 32bit vs 64bit. That's all done kernel side, after passing control. Since 32bit kernels can't run 64bit binary (not exactly true) it doesn't matter if it's pared with a 64bit kernel. this is even more so when you have Linux & OtherOS, they can't even "see" each other. There is NO difference in stability or compatibility going across different systems, they don't contact each other, no stability conflicts.
As for any question about 64bit not supporting hardware like 32bit, that's just more FUD. We are trying to push everything to go 64bit in linux, EVERYTHING. Also, every piece of hardware that's supported in the 32bit kernel IS supported in the 64bit kernel. There's no question, that's a fact of how the kernel works. If you bring me an example of where the 32bit version supported your hardware where a 64bit version wouldn't, I'll most likely point you to another distro and tell you to try that. If it works, your hardware works. Don't make the fault of a distro having poor hardware support the entire point of 64bit not having hardware support.
 Also, if you want any linux to boot you'll have to re-size your raid0 or make a new one. Currently there isn't a bootloader that can read fakeraid/software/raid0, period. The only known methods are:
Install /boot on a separate physical partition on one of the drives and raid everything else, (the other drive will have the same space as /boot but as un-partitioned space).
Install raid1 for /boot and raid0 for everything else.
 There is apparently a solution for fakeraid/software that has grub read one device from the raid. It's in the Ubuntu wiki and you have to manually set up grub.Edited by mushroomboy - 1/26/11 at 8:05am