• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Vista 64 and the 'usual' tweaking/OC tools?

T

tempoct

Senior member
Hi,
Decided to try on the Vista Ultimate 64-bit version from my MSDN last night on my C2D box (E6300 @ 3.3GHz 2GB DDR2-940 on Asus P5B Deluxe Wifi GeForce 6600 + 128MB GPU). Interface is pretty but not familiar to find out where things are yet.
Also, all the usual tools (Intel TAT, Speedfan, etc) does not seem to work with this version. Anyone know the new set of tools that will natively work with Vista 64? I did not try Prime95 and Orthos yet.
I have hard time setting up Wifi on this. Seems like it won't connect even though everything has been configured (WPA-PSK + TKIP) *Sign*. This is what I have to pay as an early adopter.
Overall performance is OK. I tried my usual program I use for photo editing (Nikon Capture NX) which is a 32-bit .NET 1.1 apps. Little glitch on installation since it thoughts no .NET installed (in fact, vista included .NET 3.0). Overall, I got slower performance than Win XP 32-bit when try batch processing. Not a lot of losing performance though (but at idle, Vista seems to consume about 1/2 of my 2GB RAM!).
I guess Vista is really resource hungry but it is good to put the 2nd core in use. Overall it is sluggish a little (I guess Aero does put my GPU to work). I don't play game so I guess I will stick with this video card.
Maybe I would have better compatibility (and performance) with Win XP x64? Seems to be less resource consumption (and less pretty 🙂 )
 
Yup, that's not surprising at all. That's one of the reasons I'll be using 32-bit Vista if I ever do use it.

64-bit Vista requires drivers to be signed. That means, no more custom drivers from small-scale developers, unless they happen to have contracts with MS (they basically don't). I'm sure Intel TAT will eventually.

Prime95 does not use a custom driver, so it'll be fine.

Utilities that may never work in Vista 64 include:

ATITool
RivaTuner (some functions)
Daemon Tools
Alcohol 120%
 
AFAIK, no option in msconfig (btw, now called "System Configuration")
On other hand, Vista 32-bit seems to be more compatible with our usual stuff. Speedfan works.
 
1) That RAM usage is most likely Super Prefetch. It is a good thing. Unused RAM == wasted RAM
2) XP x64 will have worse compatibility and performance will be worse
3) .NET 1.1 is 32bit only, though it can be installed on 64bit Vista. The Frameworks are meant to be installed side-by-side since your application will target that specific framework.
4) You do not need a "contract" with MS to have signed drivers. A specific cert that any business can get for $500/year (chump change) from Verisign, etc. will work just fine.
 
Originally posted by: Rilex
4) You do not need a "contract" with MS to have signed drivers. A specific cert that any business can get for $500/year (chump change) from Verisign, etc. will work just fine.
Click to expand...

Well, that's good to know. I was under the impression that "signed" meant WHQL'd. I could understand them requiring the user to install only WHQL drivers, but why merely signed ones (and why only in 64-bit mode)? What does the signing actually accomplish? Any spyware company with $500 could sign their drivers with a key, right?
 
Originally posted by: Rilex
1) That RAM usage is most likely Super Prefetch. It is a good thing. Unused RAM == wasted RAM
2) XP x64 will have worse compatibility and performance will be worse
3) .NET 1.1 is 32bit only, though it can be installed on 64bit Vista. The Frameworks are meant to be installed side-by-side since your application will target that specific framework.
4) You do not need a "contract" with MS to have signed drivers. A specific cert that any business can get for $500/year (chump change) from Verisign, etc. will work just fine.
Click to expand...

Look like you are leaning toward Vista 64, any recommendation on the tools I'm asking?
Maybe it's better off to get back to XP 32-bit. Why u said XP 64 will be worse? I thought the OS is much older so many people must have tweaked it.
Also, Vista 64 doesn't allow to install framework 1.1. An error msg saying "Known compatibility issue" when trying to install.
 
No idea on those specific tools. Remember, general release isn't until Jan 07 and even mainstream driver vendors aren't expected to have "Vista ready" drivers until that time (including ATi/nVidia).

I have no issues with WPA-PSK + TKIP myself, again it might be a driver issue (since the driver exposes this functionality to the OS).

XP x64 will have less (driver) compatibility since it is basically a dead-end OS and compatibility hasn't been good to this date.

.NET 1.1 SP1 X86: http://www.microsoft.com/downloads/deta...-40B2-BBDB-A83353618B38&displaylang=en

Supported Operating Systems:
Windows Vista Business; Windows Vista Business 64-bit edition; Windows Vista Enterprise; Windows Vista Enterprise 64-bit edition; Windows Vista Home Basic; Windows Vista Home Basic 64-bit edition; Windows Vista Home Premium; Windows Vista Home Premium 64-bit edition; Windows Vista Starter; Windows Vista Ultimate; Windows Vista Ultimate 64-bit edition

Don't forget to install SP1. Did you turn off UAC?

I do run Vista x64, by the way. Mostly because Virtual Server runs far better on a C2D with a 64bit OS.
 
Originally posted by: xtknight
Yup, that's not surprising at all. That's one of the reasons I'll be using 32-bit Vista if I ever do use it.

64-bit Vista requires drivers to be signed. That means, no more custom drivers from small-scale developers, unless they happen to have contracts with MS (they basically don't). I'm sure Intel TAT will eventually.

Prime95 does not use a custom driver, so it'll be fine.

Utilities that may never work in Vista 64 include:

ATITool
RivaTuner (some functions)
Daemon Tools
Alcohol 120%
Click to expand...

Daemon Tools and Alcohol 120% work fine in 64-bit Vista now. They both use a 3rd party SPTD driver that is signed now IIRC.
 
OK, I tried disable the driver signing check and speed fan is able to read all the sensors now.
TAT is still not working.
I think I will go back to XP 32 for performance work (like photo editing) and will do dual-boot with Vista 32. Seems like Vista 64 will not be support by many providers yet. I hope it would be faster but MS does offer Vista 32 which make the push to mainstream 64 bit software availabilities to further future.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top