![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
|
Welcome to Vista Forums we are your forum to discuss Windows Vista x64 and x86 systems. Whether you need help or just want to post an idea you have on Vista, this is the forum for you.
br> br> |
| |||||||
![]() |
| | Thread Tools | Display Modes |
| | #2 (permalink) |
| Underwhelmed | Re: Vista 64 and AMD 64 X2 "Worth the upgrade"? NO! Vista is decidely unstable on multi-core machines: see the other 5 posts today for machines similar to yours. I also run an old AMD Athlon 64 X2 "Hammer" on an MSI K8N Plat board; 4 gig of RAM; GS7800 video card; Audigy sound card "experience index" of 4.1 With XP x64, I was over-clocked almost 10% and TOTALLY ROCKED! With Vista Home Premium, over-clocking is out-of-the-question and I still freeze/lock-up/stop/shutdown daily - 'tis MOST annoying Vista is more stable if you turn off the whole "glass" thing; but it is no faster than XP no matter what you do. |
| | #3 (permalink) |
| Plays with his WEI | Re: Vista 64 and AMD 64 X2 "Unstable"!?!? If you're having problems with stability, then you have issues besides the OS. Full Stop. If the problem only occurs after you overclock, then your OC settings are not stable. What you need to do is determine the source of the issue. Fix that, and the OS will be stable again. I've had Vista 64 running on a 25% Quad-Core processor overclock (fm 2.4 to 3.2Ghz), 60% Front Side Bus overclock (1066 to 1600), on Air, and near stock voltages for the last 6 months - Not a single crash. I'm telling you: If you're having problems with the OS after overclocking, it's not related to Vista. Go back and look at what you've done while tinkering around in the Bios. For the OP: As you guessed already, I am very much pro-Vista. It's been very good to me, and I haven't had any troubles I couldn't solve myself by either digging through the book I bought for it or hitting up the web. Having said that: If/since you already have XP running on an older computer, there is little reason to switch to Vista. And there *are* issues with older hardware - Most makers did not bother to create drivers for their older stuff. Why?? Because they want you to buy a new one. And because it costs them money to write, test, and deploy new drivers. Money which will *not* come back to them in the form of sales. So by and large the various parts guys created new drivers (slowly...) for the parts they *had* to in order to meet their support contracts. No more. New parts? Of course. Old?? Not so much. We'll all be on Vista sooner or later - But if you have XP, especially on a box a couple years old, then you really should stick with it until your next build. New OEM purchasers will get Vista anyhow... If you want to play with it. Or if you're like me and just want the new thing: There is a Vista Upgrade Adviser which you can download from Microsoft: Download details: Windows Vista Upgrade Advisor Install this. Run it. Run it again. Take it's advice seriously. It is quite accurate. If it says you'll have a problem with something - you will. If it says you might have a problem - You will likely "find" the issue sooner or later. So whatever it says to fix. Fix it. If you want to play with V on the system you have now, buy another hard drive, set your comp up for dual booting, and give Vista it's own playground. I'd also advise not formatting the drive from within XP - Do so from a bootable disc/thumb drive and a C prompt. If you're already running 32 bit Vista, there's not a whole lot of reason to go to 64. It's almost *exactly* the same. From a user perspective the biggest single benefit is to be able to address and fully utilize 4GB+ (up to 64GB for home users) of RAM. There's other differences, sure, but the ability to use more RAM is the primary reason users would want to make the switch. Besides that, as you user you get what is essentially the same OS with some more security related functionality. Regarding the usage of "Major" programs: Know that Vista 64 includes the libraries needed to run 32 bit code. And 95% of the time it's completely transparent to the user whether a given program is running in 32 or 64 bit mode. There may be occasions where you need to specify a 'Compatibility Mode' - Right click the program icon and check the appropriate box on the 'Properties' tab. Easy. If you're a graphic artist who somehow doesn't use a Mac, the Adobe has done almost nothing for Vista, and have flatly stated they don't intend to support V64 ever. Acrobat Reader works fine, tho. I also know that Macromedia don't have a 64 bit version of Flash - But I can tell you for a fact that you can install the 32 bit version of Flash on your 32 bit browser of choice and never notice the difference. Please note that I said "Browser of Choice" - The lastest versions of IE (of course - 32 and 64), Firefox/Thunderbird, Opera, all run on Vista 64 just like they would on a 32 bit OS. From a user perspective, there is no difference. Games?? I have Bioshock, NWN1/2/Mask, The Witcher, Oblivion/Shivering/Knights, and WOW/Burning all installed and running on my computer - No crashes except for NWN2, which is hardly a stable game on XP either. One other thing of note: No Application or driver issue (error/crash) has ever taken down Vista 64 as long as I've had it. I've been through pre-service pack XP, and let me tell ya: The difference is night and day. At the same point in it's development cycle as Vista is now, if an app so much as farted on XP the entire OS would crash. If a driver had a bug, Crash... And forget overclocking - unless your settings were *perfect* XP would endlessly crash. And sometimes, XP would just crash for no reason at all. It was bad enough that dedicated users started seeing Blue Screens in their sleep. Lay down, relax, start to drift off, and the last thing they'd see before oblivion was endless blue... No, Vista (32 or 64 bit) is not as fast as XP SP2 - I's hugely more aggressive about managing system resources and has more overhead/background tasks to run. But looking at the two at the same stages in their respective development, Vista is better by far. Last edited by Scotteq; 01-05-2008 at 09:03 AM. Reason: Spellingg and Grammurr :) |
| | #5 (permalink) |
| Underwhelmed | Re: Vista 64 and AMD 64 X2 Yes, unstable. Take a gander at the plethora of messages on this and other threads: Vista freezes; craches; locks-up' stops; reboots; etc. Denying that it doesn't happen only delays the eventual fix. Further, if XP x64 ran great on this patform, and Linux Gutsy Gibbon runs great on this platform, but Vista DOESN'T run great on this patfrom; what do you suspect to be the culprit? Don't get me wrong: I'm no Widnows-basher. But I'm also not a Microsoft bigot, either. I just want to get a decent STABLE OS for the money I spent. |
| | #6 (permalink) |
| Underwhelmed | Re: Vista 64 and AMD 64 X2 Apparently I was not clear enough about my over-clocking. My experieince is this: Vista is unstable with NO over-clocking at all - dead stock "default" settings across-the-board. It was my previous XP x64 configuration that would tolerate significant over-clocking, on exactly the same platform, with no problems at all. |
| | #8 (permalink) | ||||||||||||
| Plays with his WEI | Re: Vista 64 and AMD 64 X2 Archimedez - Like I said earlier - I have a Huge overclock going, and am perfectly stable. If we're gong to help, we need *details* about what exactly the error codes are. What conditions it's crashing under, etc. Merely hollering that "It Sucks" doesn't do anyone any good. We could link you thousands of similar posts about problems in XP - So what?? If there's an issue, you hunt it down and kill it. Doesn't matter what OS you are running: You don't just throw up your hands and rant all over the place. You identify the problem and work out the solution. When you overclock, are you running Prime 95, Everest, or other torture testing program?? If so, then for how long?? Does it pass? If not, you have a problem with your overclock. And so you know I'm not pulling your leg about the overclock:
| ||||||||||||
| |
| |