vista and quad cores

JVC

[H]ard|Gawd
Joined
Oct 24, 2004
Messages
1,280
quick question, does vista make use of quad cores processors?
 
All versions of Windows XP and Windows Vista can address all four cores on a quad core processor.

That's what I thought. Figured I'd better ask though.
Vista, the new Windows ME.
 
From what I read only VISTA really takes advantage of multi cores efficiently; the OS is truly multi-core aware; I don't think this is true in the same respect in XP but I don't have the sources to support this point, just my feeling.
 
Yep, definitely noticed somewhat of a little improvements over it than i did with xp for some reason.
 
That's what I thought. Figured I'd better ask though.

Vista, the new Windows ME.

Vista is far better than ME and XP. Just read up on how it works, and you'll see why. The ability it has to learn its users tendencies is what makes it great. The only downside is its hardware requirements.

The MS OS isn't limited by the number of cores on a single CPU, but rather the number of physical CPUs. So, its easier to think of it in sockets...

XP Home: 1 CPU socket
XP Pro: 2 CPU sockets
Vista Home Basic/Premium: 1 CPU socket
Vista Business/Enterprise/Ultimate: 2+ CPU sockets
 
Vista . The only downside is its hardware requirements.

And the fact that some software will not install or run. Also, the fact it is prone to crashing constantly. Yes the dreaded BSOD is back. ( I have never gotten a BSOD in XP.)
 
And the fact that some software will not install or run. Also, the fact it is prone to crashing constantly. Yes the dreaded BSOD is back. ( I have never gotten a BSOD in XP.)

Most crashes are caused by poorly written drivers and that goes for all OS's. And to anwser your some software will not run or install, it's not MS fault that companies can't port or write software well for the OS. I find that most users that complain about crashes pretty much have limited skills when it comes to messing with new OS's and computers in general.
 
Most crashes are caused by poorly written drivers and that goes for all OS's. And to anwser your some software will not run or install, it's not MS fault that companies can't port or write software well for the OS. I find that most users that complain about crashes pretty much have limited skills when it comes to messing with new OS's and computers in general.

As for drivers, the hardware companies should not be releasing products if they dont work with the OS. (The laptop I bought was ONLY available with Vista.)

As for the software, how would the developer of a program write it to work with Vista in 1997?
Failure of MS to offer compatibility in my book.
 
As for drivers, the hardware companies should not be releasing products if they dont work with the OS. (The laptop I bought was ONLY available with Vista.)

As for the software, how would the developer of a program write it to work with Vista in 1997?
Failure of MS to offer compatibility in my book.

Like I said even I got the developers code for vista so how hard is it for a software maker to get it and make sure the program will work in vista. I guess it's real hard indeed.
 
Most crashes are caused by poorly written drivers and that goes for all OS's. And to anwser your some software will not run or install, it's not MS fault that companies can't port or write software well for the OS. I find that most users that complain about crashes pretty much have limited skills when it comes to messing with new OS's and computers in general.


QFT, God I am so tired of posts claiming that Vista sucks. Vista is the best OS I have ever used hands down. I really enjoyed tweaking until things purred like a kitten. In all fairness , i dont use any software that is prehistoric so may be thats why
 
As for the software, how would the developer of a program write it to work with Vista in 1997?
Failure of MS to offer compatibility in my book.

Depends.
In a lot of cases it's developers not reading the docs properly, and ignoring things like parameters reserved for future use, and having to be 0. Or they don't test their code on more than one OS, and it 'accidentally' works, even though there are bugs.
Lesson 1 for a programmer: working code != bugfree code.
The compatibility problems with Windows are mostly not because they don't work according to the API specs, but rather that their behaviour with out-of-spec situations is different. Which makes sense, because their implementations are different (thank god... I'd hate to have only one implementation that's recycled over and over again. It has to be adapted to newer hardware from time to time, for better efficiency).
I think most programmers have experienced a situation where they discovered a bug that made them go "How could this ever have worked at all!?".
 
QFT, God I am so tired of posts claiming that Vista sucks. Vista is the best OS I have ever used hands down. I really enjoyed tweaking until things purred like a kitten. In all fairness , i dont use any software that is prehistoric so may be thats why


you QFT my post only stated the reasons for most BSOD.
 
And the fact that some software will not install or run. Also, the fact it is prone to crashing constantly. Yes the dreaded BSOD is back. ( I have never gotten a BSOD in XP.)

Really? I havnt got a single BSOD from vista. It runs SMOOOOTH! :D
 
QFT, God I am so tired of posts claiming that Vista sucks. Vista is the best OS I have ever used hands down. I really enjoyed tweaking until things purred like a kitten. In all fairness , i dont use any software that is prehistoric so may be thats why

I agree. If people cant get an OS working, then it must be the OS's fault and it sucks. Doesnt matter that most people found it works great.
 
I have 4gb of ram and a quad core CPU. Both Vista and XP-64 recognize and use all of it. However Vista runs much better and faster on my system than XP-64 and driver support is better.


I have been using Vista Ultimate since release day. I made a clean break from XP and only installed software that that manufacturer either designed for or said was compatible with Vista. I have yet to see a BSOD. Yup, I have had ZERO crashes in Vista. :cool:
 
As for drivers, the hardware companies should not be releasing products if they dont work with the OS. (The laptop I bought was ONLY available with Vista.)

As for the software, how would the developer of a program write it to work with Vista in 1997?
Failure of MS to offer compatibility in my book.


Dear gawd you live in a small world. :rolleyes:

In a perfect world no one would have to worry about deadlines, unexpected failures, unresolved programming errors. They wouldn't have to worry about investors breathing down their throats to complete and distribute a product or in the presence of a lack of investors deadlines to keep the cash flowing in so that they can pay programmers to keep writing/debugging code.

Make note that I do not excuse the way some things work in this world, this is simply an acknowledgment and understanding that crap doesn't usually work as you want it to.
Thus...we have driver revisions, software patches, system upgrades (amongst other reasons), etc.
When you start adding new and improved functions eventually you're going to have to stop supporting TEN YEAR OLD applications so that you're not lagging the new system behind. Eventually the architecture will mature and you'll have to trim the fat. :eek:
 
And the fact that some software will not install or run. Also, the fact it is prone to crashing constantly. Yes the dreaded BSOD is back. ( I have never gotten a BSOD in XP.)

Have you ever stopped to think that any software that will not install (or run) in Windows Vista (despite the compatibility options available) is, quite simply, software that deserves to be replaced? The *only* software that I have had issues installing on Windows Vista are: games that require MS-DOS Mode (not a DOS compatibility box) and Lexmark printer drivers. I have old Windows games (one, Microsoft Fury3, dates back to the launch of Windows 95) that run quite happily on Vista (however, Fury3 is so well-behaved that it runs on *Windows NT 3.51 Workstation*). Newer games also behave quite well (from Bioshock to Enemy Territory: Quake Wars).


What software has been giving you grief?
 
Vista is called ME by usually 2 people. The ones too cheap to upgrade to a new OS because they are still fine with a 5 year old operating system. Or by those who generally can't build a stable system to begin with. Vista is a fantastic OS some people just need to move on. It's like people ranting about the move from win 2k to XP all over again.
 
Have you ever stopped to think that any software that will not install (or run) in Windows Vista (despite the compatibility options available) is, quite simply, software that deserves to be replaced? The *only* software that I have had issues installing on Windows Vista are: games that require MS-DOS Mode (not a DOS compatibility box) and Lexmark printer drivers. I have old Windows games (one, Microsoft Fury3, dates back to the launch of Windows 95) that run quite happily on Vista (however, Fury3 is so well-behaved that it runs on *Windows NT 3.51 Workstation*). Newer games also behave quite well (from Bioshock to Enemy Territory: Quake Wars).


What software has been giving you grief?
Yes software does need to be replaced. IF, there is a replacement available.
I have a couple of programs that there is no replacement or upgrade for. One is a office program for production. The other is a special 3D rendering program for photography.

The other two are games. Return to Castle Wolfenstein and Quake III. Both are OpenGL based. The good news is that I think I have found a way to get those working OK. Tigerwolf7 over on the Dell forums posted a way to install the latest Forceware drivers WITHOUT having to mess with the ini files. I post it all below to help others on this board.

Tigerwolf7 wrote:
Disclaimer: Be sure to back up data before attempting this, and I am not responsible for any data loss, problems, etc. that you experience, nor is Dell responsible. I can only say that this procedure worked for me on a notebook with a Geforce 8600GT and Windows XP SP-2. Obviously you must also have a notebook with an Nvidia GPU for this to work.

Notes: I’ll update this as more info is gained about the procedure.
-I’m told that clock speed settings are set in hardware, and so you don’t need to worry about the regular Nvidia drivers accidentally overclocking your GPU (from my experience on an 8600GT this proved true).
-On my system, even after installing the new drivers my system still knew it was a laptop, still had laptop related power settings in the Nvidia control panel. Potentially installing reference drivers might disable laptop features (such as power settings, sleeping by closing the lid, etc.)
-Note also that I don’t think this will work for enabling SLI on systems with two video cards and an Intel chipset. It’s my current belief that such systems (such as the XPS 1730) will only work with special drivers, though POSSIBLY you can use this procedure to get one GPU working.
-Using the newest drivers games such as Bioshock seemed to run flawlessly, though I only played them briefly. I experienced no video related errors in my brief tests.
-I’m going partially by memory here, so these directions may not be absolutely 100% the same as what you see.
-Also note that this procedure is actually much simpler than these long instructions would make it seem. If you’ve updated a driver on a desktop system before, you’ll probably be fine. If not these are hopefully detailed enough to help you out.

Procedure:
Normally you’d want to uninstall your current drivers before installing new ones. I did this WITHOUT first uninstalling my current drivers, however I believe this will work if you first uninstall the old drivers, and you probably should.

1) Download the newest drivers for your video card and operating system from www.nvidia.com. Save them to your desktop or somewhere else you will remember. (Select “Geforce” as the product type, not “Geforce Go”.)
As of October 3, 2007, the current drivers for Windows XP are 163.71 WHQL
Release Date: September 28, 2007.

2) Double click the driver install file. This will extract the driver files, and then launch setup. Setup will fail immediately, with an error that your hardware isn’t supported. This is okay.
By default the drivers will have been extracted to c:\Nvidia\ (and then usually something like \win2kxp\).

3) Allow setup to quit, and then right click on “My Computer” on your desktop or in your Start menu (may be called “Computer” under Vista). Click “Properties”, then “Hardware”, then “Device Manager”.

4) In Device Manger, you should see an entry for “Display Adapters”. Double click this to expand it, and then right click on the entry for your video card (might be “Geforce 8600” or whatever). Chose “update driver” from the menu.

5) You will be asked if Windows can connect to Windows Update. Choose “No, not this time” and hit next.

6) Choose “Install from a list or specific location (Advanced)” and hit next.

7) Choose “Don’t search. I will choose the driver to install.” and hit next.

8) The next window will probably display a driver for your video card, but that’s not what we’re using (it’s the old driver). Instead, hit “Have Disk”.

9) An “install from disk” window opens. Click “Browse”

10) Now we have to locate the driver’s inf file-use the drop down menu to navigate to your default “c:” hard drive, then double click on the Nvidia folder, double click the folder for your OS (will probably say win2k or win2kxp if this is for Windows XP), double click the newest driver version (currently 163.71 ).

11) You will now see a fill called “nv4_disp”-double click this, and click “okay” on the “Install from Disk” window.

12) You should see a list of Nvidia desktop GPUs. I would select the one that most closely matches your mobile GPU, though I’m not sure if this is actually necessary. For example I have an 8600m GT, so I picked 8600GT. This will probably work for an 8700GT as well (I’d probably pick 8600GT or 8600GTS for an 8700GT) since they’re basically identical hardware. I’m really not sure it matters what you pick here, but it can’t hurt to pick something close to the type of GPU you have.

There's a possibility that picking a very different architecture here would cause this to fail and blue screen (ie picking a Geforce 7600 for a mobile 8600or a 6800 for a mobile 4200, etc.), but I don't know.

13) Once you’ve picked a GPU, click “next”. It will give a warning message that this driver isn’t designed for your hardware. This isn’t exactly true (your mobile GPU isn’t listed in the INF file, but the actual hardware is basically the same thing). Click that you want to go ahead and install it anyway.

14) If I’m remembering correctly, at this point the system will being installing the new drivers files, which in my case took a few minutes. My display switched to a generic mode at the end of this process (lower resolution), and I was asked to reboot.

15) After rebooting, my system came up fine, and I verified my driver version in the Nvidia control panel. I was running the newest reference drivers! At this point you should be done. I’d test out a game or game demo to see if your 3D is working.

Note again that in my case the Nvidia control panel still identified my monitor as a laptop display, and still gave me access to laptop GPU power settings that aren’t available on desktop parts, despite that this was using the regular desktop drivers! My display control software that handles brightness settings was still working just fine too (in this case this was Apple provided software-I’d expect Dell’s software would work just fine too).
It’s possible however that you will lose access to specific laptop GPU features, so you might not be able to sleep the system by closing the lid, etc. However for many of us that would be a perfectly acceptable trade off to be running the newest, most compatible drivers.
 
Vista is called ME by usually 2 people. The ones too cheap to upgrade to a new OS because they are still fine with a 5 year old operating system. Or by those who generally can't build a stable system to begin with. Vista is a fantastic OS some people just need to move on. It's like people ranting about the move from win 2k to XP all over again.

I guess I am the 3rd type. I have every OS Microsoft has released since DOS 2.0. I just bought MS Home Server, and it is awsome. Stable and works right with minimal tweeking.
As for building a stable system, been doing it for years. Started with a 386 in 1992. Current rig is an Opteron 144 overclocked to 3.0Ghz. Stable as hell with XP SP2.
Oh, I did rant about the move from Win2000 to XP. Ranted about how nice it was to have a stable OS like 2000 with a game friendly OS like 98.
 
The only bsods I've had with my recent move to Vista x64 were when trying to install with 4GB of ram. After I read that was an issue I pulled a stick and it installed great with 2GB. After running update I added the other stick back and I was good to go.
While that crash really did piss me off (why is a 64bit os unable to install with 4GB ram????) once I found the workaround it was pretty simple.
 
If I could get my games to run on Vista, I would be there. But until then it will have to be XP Pro
 
I recently switched from XP Pro to Vista Ultimate and am loving it.

Question, I've realized that CPUZ takes a lot longer to open now. Anyone have any idea why?
(It has always taken considerable longer than other programs, considering the complexity of the program of course, but now it takes about twice as long as before with XP.)
 
Back
Top