<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Persistent notes &#187; windows</title>
	<atom:link href="http://alexkr.com/tag/windows/feed/" rel="self" type="application/rss+xml" />
	<link>http://alexkr.com</link>
	<description>Alexander Krivutsenko&#039;s online journal</description>
	<lastBuildDate>Sat, 07 Apr 2012 20:46:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Loading VS 2008 solution files on VS 2004</title>
		<link>http://alexkr.com/posts/130/loading-vs-2008-solution-files-on-vs-2004/</link>
		<comments>http://alexkr.com/posts/130/loading-vs-2008-solution-files-on-vs-2004/#comments</comments>
		<pubDate>Mon, 17 Dec 2007 16:16:49 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[cpp]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://alexkr.com/posts/130/loading-vs-2008-solution-files-on-vs-2004/</guid>
		<description><![CDATA[Visual Studio 2004 won&#8217;t open solution files generated by newer IDE like Visual Studio 2008.
But if you really needed it, you can apply the following trick.

First of all, this is a dirty hack and in some circumstances resulting solution will not be identical to the original one.
So, the idea is that one can open all [...]]]></description>
		<wfw:commentRss>http://alexkr.com/posts/130/loading-vs-2008-solution-files-on-vs-2004/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unicode encodings UTF8 and UCS on Windows and Linux</title>
		<link>http://alexkr.com/memos/123/unicode-encodings-utf8-and-ucs-on-windows-and-linux/</link>
		<comments>http://alexkr.com/memos/123/unicode-encodings-utf8-and-ucs-on-windows-and-linux/#comments</comments>
		<pubDate>Mon, 05 Nov 2007 16:32:40 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[big]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[unicode]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://alexkr.com/memos/123/unicode-encodings-utf8-and-ucs-on-windows-and-linux/</guid>
		<description><![CDATA[Here are some issues I faced when I had to support UTF8 on Windows and Linux. 
Universal Character Set (UCS) is a set of all characters which are ever needed in a software. UCS defines integer code for each symbol.
The ASCII characters set is included in UCS using same values from 00 to 7F. First [...]]]></description>
		<wfw:commentRss>http://alexkr.com/memos/123/unicode-encodings-utf8-and-ucs-on-windows-and-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pure virtual destructors on Windows and Linux</title>
		<link>http://alexkr.com/posts/109/compile-time-type-checking/</link>
		<comments>http://alexkr.com/posts/109/compile-time-type-checking/#comments</comments>
		<pubDate>Tue, 15 May 2007 14:18:55 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[cpp]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://alexkr.com/source-code/109/compile-time-type-checking/</guid>
		<description><![CDATA[The idea is that you can create abstract class with only one pure virtual entity, which is a virtual destructor. This class would be abstract with all its features.
However, since compiler always generates code for derived objects to implicitly invoke destructor of the base object, you will have to specify the body of the pure [...]]]></description>
		<wfw:commentRss>http://alexkr.com/posts/109/compile-time-type-checking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to limit process memory</title>
		<link>http://alexkr.com/posts/96/how-to-limit-process-memory/</link>
		<comments>http://alexkr.com/posts/96/how-to-limit-process-memory/#comments</comments>
		<pubDate>Sat, 14 Apr 2007 15:52:38 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://alexkr.com/source-code/96/how-to-limit-process-memory/</guid>
		<description><![CDATA[On Linux you can always do something like


	ulimit -v 1024


This command limits the amount of available virtual memory for processes which will run by current user.
On Windows 2000+ the only way to place constraint on the memory for a process is to use jobs. Among other useful features jobs allow to apply some restrictions to [...]]]></description>
		<wfw:commentRss>http://alexkr.com/posts/96/how-to-limit-process-memory/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Who throws bad_alloc in Microsoft Visual C++ 7.1</title>
		<link>http://alexkr.com/posts/95/who-throws-bad_alloc-in-microsoft-visual-c-71/</link>
		<comments>http://alexkr.com/posts/95/who-throws-bad_alloc-in-microsoft-visual-c-71/#comments</comments>
		<pubDate>Thu, 12 Apr 2007 14:27:56 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[cpp]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://alexkr.com/posts/95/who-throws-bad_alloc-in-microsoft-visual-c-71/</guid>
		<description><![CDATA[C++ standard says that operator new must throw std::bad_alloc exception
when memory allocation fails.
Consider the following test application:


#include &#60;iostream&#62;
#include &#60;limits&#62;
int main(){

 try{
  char * ptr = new char[std::numeric_limits&#60;int&#62;::max()];
  if (!ptr) std::cout &#60;&#60; "NULL returned!" &#60;&#60; std::flush;
  else std::cout &#60;&#60; "Miracle!" &#60;&#60; std::flush;
 }
 catch(std::bad_alloc e){
  std::cout &#60;&#60; "Exception: bad_alloc!" &#60;&#60; std::flush;
 }

 [...]]]></description>
		<wfw:commentRss>http://alexkr.com/posts/95/who-throws-bad_alloc-in-microsoft-visual-c-71/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unknown error in VS</title>
		<link>http://alexkr.com/fun/91/unknown-error-in-vs/</link>
		<comments>http://alexkr.com/fun/91/unknown-error-in-vs/#comments</comments>
		<pubDate>Tue, 27 Mar 2007 17:44:03 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[fun]]></category>
		<category><![CDATA[cpp]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://alexkr.com/fun/91/unknown-error-in-vs/</guid>
		<description><![CDATA[Some nice error message gave me Visual Studio today.
Though I am sure this error belongs to CVS provider, which was source safe at that moment.



Anyway it was not over informative.
I would be glad to hear at least that it is a network error or something related to source code integrity among files in different projects.
]]></description>
		<wfw:commentRss>http://alexkr.com/fun/91/unknown-error-in-vs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ACE sleep on Linux and Windows</title>
		<link>http://alexkr.com/posts/82/ace-sleep-on-linux-and-windows/</link>
		<comments>http://alexkr.com/posts/82/ace-sleep-on-linux-and-windows/#comments</comments>
		<pubDate>Wed, 28 Feb 2007 16:06:51 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[ace]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://alexkr.com/programming/82/ace-sleep-on-linux-and-windows/</guid>
		<description><![CDATA[Today I found one significant difference in running ACE on Windows and Linux.
Consider the following statement:



 ACE_OS::sleep(0xFFFFFFF1);

 The effect is:

On Windows this will force the thread to sleep for 4294967281 seconds.

On Linux this command is processed immediately.


At this moment I don&#8217;t know why this happens.
I tried with value 0&#215;0FFFFFF1 on Linux and it went fine [...]]]></description>
		<wfw:commentRss>http://alexkr.com/posts/82/ace-sleep-on-linux-and-windows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A trick to create a service using SC.exe under Windows XP</title>
		<link>http://alexkr.com/posts/69/a-trick-to-create-a-service-using-scexe-under-windows-xp/</link>
		<comments>http://alexkr.com/posts/69/a-trick-to-create-a-service-using-scexe-under-windows-xp/#comments</comments>
		<pubDate>Tue, 21 Nov 2006 18:12:08 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://alexkr.com/uncategorized/69/a-trick-to-create-a-service-using-scexe-under-windows-xp/</guid>
		<description><![CDATA[Placing space symbol in the right place would save your time]]></description>
		<wfw:commentRss>http://alexkr.com/posts/69/a-trick-to-create-a-service-using-scexe-under-windows-xp/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

