2710P with Vista 64bit?

[nutsnbolts]

Ok, I'm about to get this and do a fresh install of vista on it. Any reasons not to go with 64 bit? I have heard software issues that may come from using 64 bit but it seems to be almost a none issue nowadays.

What's the truth?

Should I jump to 64 bit? I will be upgrading to 4 gig memory and would benefit from using 4 gig because 64 bit will utilize all 4 gigs. Other than that, I just dont' want to deal with the 64 bit headaches if this is still the case with 64 bit vistas.

[Osiris]

I havent come across any troubles with X64 Vista and the HP 2710p. I havent run too many old apps but it seems like the compatibility is vastly improved and as I said no problems on new apps, X64 capable apps or what older apps I have run.

Osiris, performance wise, do you think there is a difference?, i.e. if you have 4gb running vista 64, do think it will run faster than having vista 32 recognizing only 3gb?

[nutsnbolts]

Good question.

[ericthebikeman]

XP64 had a ton of issues, Vista seems to be better. HP provides all of the drivers in either 32 or 64 which makes setting up Vista for the machine itself rather painless. There are still a few manufacturers that won't do 64bit drivers for some reason. Scanners were an issue for me, I eventually found one that worked. All my other peripherals didn't care what version I had.

Software is fine, hell even Vag-Com for my VW works on x64. My one and only issue is print to Onenote 2007 still doesn't work. I still think that's baffling that Microsoft can't get it working on x64 systems, nevermind the fact they've had ages to play with x64 systems XP or Vista. I learned to live without it, it would be nice to have back but I'll live.

[nutsnbolts]

Well it's official. I reverted back to x32. Although the process of going to x64 was painless, I had issues with the following:

1. Looping installer with MS project 2007 and MS Visio 2007
2. Took more HD space.
3. Little nuisances here and there.

The bottom line is, I went back to 32 bit and all those things didnt' exist. In addition, I don't see a performance difference. Although I can see that it's only registering ~3gig of memory.

[techgeek32]

I have tried both and still many programs that don't support X64. OneNote printing being the biggest. Microsoft has stated that they will not be providing drivers for this feature. Will have to wait for the new version. I didn't notice any speed difference and after upgrading to SP1 I am showing all of my 4GB. Vista utilizes some of the RAM anyway so I didn't notice my system being any faster with x64. On a system with the ULV processor it really doesn't make any sense because most enterprises that use 64 bit run CAD and graphics which no one will ever do on a 2710p.

[nutsnbolts]

Definitely good points. I wanted to take advantage of my memory but then again, it's using twice the memory from what I have read or something like that so it didn't make any sense.

[gst28]

Hi,
nutsnbolts: I'm running x64 and I didn't have a issue with MS project 2007 or visio 2007. I installed office 2007 with SP1 1st before doing so though. Yes I agree there are some issues with some apps I tried like send to one x64 driver, the ink on desktop and some tools in the tablet pc enhancement pack don't work but all in all I'm pretty happy. For the programs that don't run I'm willing to compromise and run it in a XP virtual machine. Which gets me thinking I might install XP tablet edition instead of non-tablet XP in the VM and see if I can ink in the VM as well.

Cheers,

ray.

[eddwo]

A lot of the problems with running applications on x64 occur because by default .Net apps run on the 64bit CLR. If the app was never tested on the 64bit CLR, or it requires a non .Net library which is only availablecompiled for 32bit windows it will often fail to run or produce messages regarding missing .dll s.
You can force a .Net application to run on the 32bit CLR even on x64 Windows using the 'corflags' utility.

officially 'corflags' comes as part of the Windows SDK, but you are not a developer who needs the whole sdk its probably easiest to get it by installing one of the 'Express' editions of visual studio 2008. (2mb download, ~60mb install)

Once installed 'corflags' can be found in
'C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\'

use 'corflags /32BIT+ {app exe file}'

if the exe is in 'Program Files' you will need to run the command prompt elevated under UAC.

This worked for me to get 'Ink Desktop' and several other programs running on my 2710p with Vista x64.