<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 8 things you should know before moving to x64 version of Windows</title>
	<atom:link href="http://blog.nirsoft.net/2009/09/22/8-things-you-should-know-before-moving-to-x64-version-of-windows/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nirsoft.net/2009/09/22/8-things-you-should-know-before-moving-to-x64-version-of-windows/</link>
	<description>The official blog of nirsoft.net</description>
	<lastBuildDate>Thu, 18 Mar 2010 01:53:03 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tyra Misoux</title>
		<link>http://blog.nirsoft.net/2009/09/22/8-things-you-should-know-before-moving-to-x64-version-of-windows/comment-page-1/#comment-5655</link>
		<dc:creator>Tyra Misoux</dc:creator>
		<pubDate>Sat, 16 Jan 2010 10:07:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nirsoft.net/?p=227#comment-5655</guid>
		<description>I moved to Win7/64 and Ubuntu/64. The real 8 GB memory is a dream when working with lot of huge pictures for example while having a virtualbox runnig as well as the browser.
I am not sure yet if disabling that driver integrity check is a good idea.
There are some cool Microsoft tools (by Marc Russinovich, http://technet.microsoft.com/en-us/sysinternals/default.aspx) also providing a tool (handle) to list (and force close) open files. This works for 64 bit.
Btw. Nir, you should add a &quot;paypal&quot;-Button to your site.</description>
		<content:encoded><![CDATA[<p>I moved to Win7/64 and Ubuntu/64. The real 8 GB memory is a dream when working with lot of huge pictures for example while having a virtualbox runnig as well as the browser.<br />
I am not sure yet if disabling that driver integrity check is a good idea.<br />
There are some cool Microsoft tools (by Marc Russinovich, <a href="http://technet.microsoft.com/en-us/sysinternals/default.aspx)" rel="nofollow">http://technet.microsoft.com/en-us/sysinternals/default.aspx)</a> also providing a tool (handle) to list (and force close) open files. This works for 64 bit.<br />
Btw. Nir, you should add a "paypal"-Button to your site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the_elektronik</title>
		<link>http://blog.nirsoft.net/2009/09/22/8-things-you-should-know-before-moving-to-x64-version-of-windows/comment-page-1/#comment-4966</link>
		<dc:creator>the_elektronik</dc:creator>
		<pubDate>Sat, 02 Jan 2010 03:08:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nirsoft.net/?p=227#comment-4966</guid>
		<description>First of all I&#039;m very happy with Vista x64 SP1.
64-bit OS supports more RAM than 32-bit systems [4GB RAM cap]
32-bit hardware intensive software benefit somehow with up to 8% efficiency increase on the same hardware.
I&#039;m using it now for about 2 years and it has never BSOD&#039;ed me yet. 

Vista x64 is a fairly acceptable OS but it is not all that good. There are many annoyances and some of them are:

- minor 32-bit software compatibility issues
- User Account Control [UAC] is very annoying but easy to turn off
- Vista has a complete mess with its system folders
- Driver Signature Enforcement preventing installation of third party drivers
- Vista blocks access to user files and system sub-folders, obtaining OWNERSHIP is required for access
- installing DX11 requires upgrade to SP2 [577MB] or [745MB] for multi-language support
- more complex system registry
- Windows side-by-side [WinSxS] occupies a lot of space on the HDD often 5GB for average user and over 10GB if additional software or multiple versions of the same software are installed
- File indexing, it is really trashing HDDs especially if you have about 5TB in HDDs with about 1kk files on them and about 100k in windows folder alone

- OS goes over 260 character long path length by itself in USERS and DOCUMENTS AND SETTINGS directories. well, NTFS supports over 32k path length but Windows API allows 260 characters only. I noticed that explorer switches to \XXXXXX~1\ directory name and I reached 28 dirs deep totaling over 480 character long path before explorer gave me an error. the CPU utilization was very high and changing a directory required few seconds.

- problems with soundcards noticeably line-in/mic pass through and audio out recording.
 [on some hardware configurations it can be fixed with registry/driver hacks but often extremely difficult to fix]
 [problems with playback and recording an audio from capture cards, TV/sat cards and video grabbers]
 
As for now I have a Dual Boot, Vista x64 and XP x86. I had to connect a Sound Blaster USB for two reasons. XP doesn&#039;t support my HDAudio soundcard and Vista can&#039;t record digitally from it but can record via digital-analog converters loosing quality.

I have multiple Virtual machines installed as well for testing purposes.

MOST OF IT IS AN VISTA THING
Install XP x64 for all benefits regarding 64-bit hardware support, well almost [DX9].</description>
		<content:encoded><![CDATA[<p>First of all I'm very happy with Vista x64 SP1.<br />
64-bit OS supports more RAM than 32-bit systems [4GB RAM cap]<br />
32-bit hardware intensive software benefit somehow with up to 8% efficiency increase on the same hardware.<br />
I'm using it now for about 2 years and it has never BSOD'ed me yet. </p>
<p>Vista x64 is a fairly acceptable OS but it is not all that good. There are many annoyances and some of them are:</p>
<p>- minor 32-bit software compatibility issues<br />
- User Account Control [UAC] is very annoying but easy to turn off<br />
- Vista has a complete mess with its system folders<br />
- Driver Signature Enforcement preventing installation of third party drivers<br />
- Vista blocks access to user files and system sub-folders, obtaining OWNERSHIP is required for access<br />
- installing DX11 requires upgrade to SP2 [577MB] or [745MB] for multi-language support<br />
- more complex system registry<br />
- Windows side-by-side [WinSxS] occupies a lot of space on the HDD often 5GB for average user and over 10GB if additional software or multiple versions of the same software are installed<br />
- File indexing, it is really trashing HDDs especially if you have about 5TB in HDDs with about 1kk files on them and about 100k in windows folder alone</p>
<p>- OS goes over 260 character long path length by itself in USERS and DOCUMENTS AND SETTINGS directories. well, NTFS supports over 32k path length but Windows API allows 260 characters only. I noticed that explorer switches to \XXXXXX~1\ directory name and I reached 28 dirs deep totaling over 480 character long path before explorer gave me an error. the CPU utilization was very high and changing a directory required few seconds.</p>
<p>- problems with soundcards noticeably line-in/mic pass through and audio out recording.<br />
 [on some hardware configurations it can be fixed with registry/driver hacks but often extremely difficult to fix]<br />
 [problems with playback and recording an audio from capture cards, TV/sat cards and video grabbers]</p>
<p>As for now I have a Dual Boot, Vista x64 and XP x86. I had to connect a Sound Blaster USB for two reasons. XP doesn't support my HDAudio soundcard and Vista can't record digitally from it but can record via digital-analog converters loosing quality.</p>
<p>I have multiple Virtual machines installed as well for testing purposes.</p>
<p>MOST OF IT IS AN VISTA THING<br />
Install XP x64 for all benefits regarding 64-bit hardware support, well almost [DX9].</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WytnoiZ</title>
		<link>http://blog.nirsoft.net/2009/09/22/8-things-you-should-know-before-moving-to-x64-version-of-windows/comment-page-1/#comment-2393</link>
		<dc:creator>WytnoiZ</dc:creator>
		<pubDate>Wed, 25 Nov 2009 16:55:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nirsoft.net/?p=227#comment-2393</guid>
		<description>Yikes, I hit this thread at the wrong time (or perhaps the right).  I&#039;ve spent the last week making images/backing up, getting prog updates, drivers, etc.  I was finally ready to perform my Win7 install TODAY.  Reading the above informed me about concerns I hadn&#039;t considered (uh, many more such concerns have presented themselves during the last week too)...My first foray into x64 has been more intense than building a machine from scratch!

     That settles it...definitely going to *dual boot* Vistax32 &amp; Win7x64 Home Premium for awhile.  Thanks to all, and MANY thanks to Mr. Sofer for some incredibly useful utils!</description>
		<content:encoded><![CDATA[<p>Yikes, I hit this thread at the wrong time (or perhaps the right).  I've spent the last week making images/backing up, getting prog updates, drivers, etc.  I was finally ready to perform my Win7 install TODAY.  Reading the above informed me about concerns I hadn't considered (uh, many more such concerns have presented themselves during the last week too)...My first foray into x64 has been more intense than building a machine from scratch!</p>
<p>     That settles it...definitely going to *dual boot* Vistax32 &amp; Win7x64 Home Premium for awhile.  Thanks to all, and MANY thanks to Mr. Sofer for some incredibly useful utils!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ratz</title>
		<link>http://blog.nirsoft.net/2009/09/22/8-things-you-should-know-before-moving-to-x64-version-of-windows/comment-page-1/#comment-2274</link>
		<dc:creator>Ratz</dc:creator>
		<pubDate>Sat, 21 Nov 2009 18:43:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nirsoft.net/?p=227#comment-2274</guid>
		<description>@pcunite,

Not all pc users are morons, some are actually intelligent users that unfortunately aren&#039;t intimate programmers either. I for one am grateful for this list and found the fact that if obviously (if you think about it and know the difference of 4-bytes vs. 8-bytes) causes bloat.

Unfortunately, I don&#039;t understand why the system has to always use all 64-bits and rather has a method of calling the appropriate 16/32/64-bit registers instead.

I will give you an example where this does realize itself, at our University, in the engineering labs, the available RAM and CPU upgrades for hundreds of PC&#039;s is limited, certain machines need higher spec for CAD graphics handling too.  Budgets on PC&#039;s are thus limited, especially as other high end technical equipment must also be purchased. 

Now, you sit with a bloat filled OS, running bloat filled applications and bloat filled security measures. Each little variable in those programs don&#039;t all require that 64-bits, but they get it. (yes, appropriate variable type assigning aside), but all this bloat decreases the efficiency of the machine, on top of this you now have students coding, running simulations etc all bogged down because of the bloat.

Users should get out of this rubbish of &quot;oh I am confused.&quot; and learn a bit about the workings of the things they are using. Given the nature of the rest of this useful website, I really doubt the target audience was the average consumer home user or secretary/businessman who has Vista 64 for typing, emails, facebook and pr0n.

@Nir,

Thanks for the list, is an interesting read and decent explanation.</description>
		<content:encoded><![CDATA[<p>@pcunite,</p>
<p>Not all pc users are morons, some are actually intelligent users that unfortunately aren't intimate programmers either. I for one am grateful for this list and found the fact that if obviously (if you think about it and know the difference of 4-bytes vs. 8-bytes) causes bloat.</p>
<p>Unfortunately, I don't understand why the system has to always use all 64-bits and rather has a method of calling the appropriate 16/32/64-bit registers instead.</p>
<p>I will give you an example where this does realize itself, at our University, in the engineering labs, the available RAM and CPU upgrades for hundreds of PC's is limited, certain machines need higher spec for CAD graphics handling too.  Budgets on PC's are thus limited, especially as other high end technical equipment must also be purchased. </p>
<p>Now, you sit with a bloat filled OS, running bloat filled applications and bloat filled security measures. Each little variable in those programs don't all require that 64-bits, but they get it. (yes, appropriate variable type assigning aside), but all this bloat decreases the efficiency of the machine, on top of this you now have students coding, running simulations etc all bogged down because of the bloat.</p>
<p>Users should get out of this rubbish of "oh I am confused." and learn a bit about the workings of the things they are using. Given the nature of the rest of this useful website, I really doubt the target audience was the average consumer home user or secretary/businessman who has Vista 64 for typing, emails, facebook and pr0n.</p>
<p>@Nir,</p>
<p>Thanks for the list, is an interesting read and decent explanation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pcunite</title>
		<link>http://blog.nirsoft.net/2009/09/22/8-things-you-should-know-before-moving-to-x64-version-of-windows/comment-page-1/#comment-1776</link>
		<dc:creator>pcunite</dc:creator>
		<pubDate>Sat, 07 Nov 2009 14:03:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nirsoft.net/?p=227#comment-1776</guid>
		<description>Quote from #7 &quot; x64 might consume much more memory than on 32-bit system&quot;

This has yet to realize itself in any meaningful way. x64 has proven itself to benefit users and you can&#039;t have something in this world without cause and effect. It would be best to not sweat the little things. As a programmer your used to dealing with the details but you will drive yourself crazy from caring about this point. Just let it go and don&#039;t confuse customers by telling them pointer sizes cause bloat.</description>
		<content:encoded><![CDATA[<p>Quote from #7 " x64 might consume much more memory than on 32-bit system"</p>
<p>This has yet to realize itself in any meaningful way. x64 has proven itself to benefit users and you can't have something in this world without cause and effect. It would be best to not sweat the little things. As a programmer your used to dealing with the details but you will drive yourself crazy from caring about this point. Just let it go and don't confuse customers by telling them pointer sizes cause bloat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Haudy Kazemi</title>
		<link>http://blog.nirsoft.net/2009/09/22/8-things-you-should-know-before-moving-to-x64-version-of-windows/comment-page-1/#comment-1655</link>
		<dc:creator>Haudy Kazemi</dc:creator>
		<pubDate>Tue, 03 Nov 2009 01:51:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nirsoft.net/?p=227#comment-1655</guid>
		<description>Here are two posts on how to use unsigned drivers with Vista x64...

http://forums.laptopvideo2go.com/topic/18585-installing-unsigned-drivers-in-vista-x64/
http://forum.xcpus.com/operating-systems/5767-howto-use-unsigned-drivers-under-vista-x64.html

The workaround is for the user to use another tool to solve the signing problems.  Some such tools include ReadyDriverPlus and Driver Signature Enforcement Overrider.</description>
		<content:encoded><![CDATA[<p>Here are two posts on how to use unsigned drivers with Vista x64...</p>
<p><a href="http://forums.laptopvideo2go.com/topic/18585-installing-unsigned-drivers-in-vista-x64/" rel="nofollow">http://forums.laptopvideo2go.com/topic/18585-installing-unsigned-drivers-in-vista-x64/</a><br />
<a href="http://forum.xcpus.com/operating-systems/5767-howto-use-unsigned-drivers-under-vista-x64.html" rel="nofollow">http://forum.xcpus.com/operating-systems/5767-howto-use-unsigned-drivers-under-vista-x64.html</a></p>
<p>The workaround is for the user to use another tool to solve the signing problems.  Some such tools include ReadyDriverPlus and Driver Signature Enforcement Overrider.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yer</title>
		<link>http://blog.nirsoft.net/2009/09/22/8-things-you-should-know-before-moving-to-x64-version-of-windows/comment-page-1/#comment-1038</link>
		<dc:creator>yer</dc:creator>
		<pubDate>Wed, 21 Oct 2009 10:24:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nirsoft.net/?p=227#comment-1038</guid>
		<description>rey , what are these known tricks ? Any links for us ?</description>
		<content:encoded><![CDATA[<p>rey , what are these known tricks ? Any links for us ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rey</title>
		<link>http://blog.nirsoft.net/2009/09/22/8-things-you-should-know-before-moving-to-x64-version-of-windows/comment-page-1/#comment-735</link>
		<dc:creator>rey</dc:creator>
		<pubDate>Wed, 07 Oct 2009 18:28:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nirsoft.net/?p=227#comment-735</guid>
		<description>I very appreciate your OpenedFilesView and hate MS for the issue 4. Never mind, I suggest you to create your unsigned OpenedFilesView driver for  W7x64 and let users to solve the problem of loading the driver. Thanks god there are some known tricks for this.</description>
		<content:encoded><![CDATA[<p>I very appreciate your OpenedFilesView and hate MS for the issue 4. Never mind, I suggest you to create your unsigned OpenedFilesView driver for  W7x64 and let users to solve the problem of loading the driver. Thanks god there are some known tricks for this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ender</title>
		<link>http://blog.nirsoft.net/2009/09/22/8-things-you-should-know-before-moving-to-x64-version-of-windows/comment-page-1/#comment-664</link>
		<dc:creator>ender</dc:creator>
		<pubDate>Mon, 05 Oct 2009 19:10:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nirsoft.net/?p=227#comment-664</guid>
		<description>I remember reading somewhere that 32bit applications were actually 2-3% faster when running in x64 Windows compared to running in 32bit Windows on the same hardware.</description>
		<content:encoded><![CDATA[<p>I remember reading somewhere that 32bit applications were actually 2-3% faster when running in x64 Windows compared to running in 32bit Windows on the same hardware.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mikael</title>
		<link>http://blog.nirsoft.net/2009/09/22/8-things-you-should-know-before-moving-to-x64-version-of-windows/comment-page-1/#comment-471</link>
		<dc:creator>Mikael</dc:creator>
		<pubDate>Tue, 22 Sep 2009 13:20:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nirsoft.net/?p=227#comment-471</guid>
		<description>And to Nir:
I mail an pdf with instructions how to sign your own drivers.
Hope this will work for you.</description>
		<content:encoded><![CDATA[<p>And to Nir:<br />
I mail an pdf with instructions how to sign your own drivers.<br />
Hope this will work for you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
