<?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>Thinkworx &#187; Handy References</title>
	<atom:link href="http://blog.thinkworx.com/category/handy-reference/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.thinkworx.com</link>
	<description>Adventures on the web, emerging technologies, random thoughts and more</description>
	<lastBuildDate>Wed, 11 Nov 2009 21:06:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Antivirus Definition Mistakenly Removes Winlogon.exe</title>
		<link>http://blog.thinkworx.com/2009/10/30/antivirus-definition-mistakenly-removes-winlogon-exe/</link>
		<comments>http://blog.thinkworx.com/2009/10/30/antivirus-definition-mistakenly-removes-winlogon-exe/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 18:58:23 +0000</pubDate>
		<dc:creator>Thomas Bowcut</dc:creator>
				<category><![CDATA[Handy References]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://blog.thinkworx.com/2009/10/30/antivirus-definition-mistakenly-removes-winlogon-exe/</guid>
		<description><![CDATA[Half our companies IT infrastructure was brought down by a bad virus definition which was downloaded and pushed out to all clients and servers on October 28th, 2009. The virus definition, def. 5474 distributed by Sunbelt Software’s VIPRE Enterprise Antivirus software, mistakenly interpreted the winlogon.exe file to be a virus and immediately put it in [...]]]></description>
			<content:encoded><![CDATA[<p>Half our companies IT infrastructure was brought down by a bad virus definition which was downloaded and pushed out to all clients and servers on October 28th, 2009. The virus definition, def. 5474 distributed by Sunbelt Software’s VIPRE Enterprise Antivirus software, mistakenly interpreted the winlogon.exe file to be a virus and immediately put it in quarantine. The winlogon.exe file is a critical windows file required at system logon, if Windows XP cannot find this file when starting up then the system will crash displaying the famous Blue Screen with the an error similar to the following:</p>
<p><em>STOP: C000021a {Irreversible System Error} Windows logon process terminated unexpectedly with state (0&#215;00000000 0&#215;00000000). The system has been closed.</em></p>
<p>Unfortunately the timing of the virus definition release corresponded with the schedule of our weekly deep scan on all client PCs. As a result close to half the company found their PCs inaccessible the next morning upon starting-up their computers. We still have to determine why not all of the systems were affected; from our experience it appears to have only affected Windows XP and Windows Server 2003 operating systems.</p>
<p>Fortunately after getting in contact with VIPRE support we were able to confirm that the source of the issue was related to a False Positive error in the definition file 5474 and that file definition 5475 was already available with the correction. Unfortunately, VIPRE does not yet have an easy fix to the problem, however in a follow-up email to our support ticket they indicated that “have been working on developing a bootable ISO utility designed to unquarantine the files detected by the FP (false positive)”.</p>
<p>Until the bootable ISO is made available to release the quarantined file the following steps are necessary to make the system once again accessible:</p>
<p>1. Copy the winlogon.exe file from C:\windows\system32\ on a working Windows XP machine to either a floppy disk or burn to a CD-ROM</p>
<p>2. Boot the system from a Windows XP installation disk. Press “R” on the first screen that asks whether to install windows or to recover an existing Windows XP installation. This will open the Recovery Console</p>
<p>3. Select the Operating System that you will be recovering by pressing the corresponding number from the displayed list. Type the password for the local Administrator account.</p>
<p>4. Insert the CD-ROM or Floppy Disk and copy the winlogon.exe file to the C:\windows\system32\ directory. (ex: \\&gt;copy d:\winlogon.exe c:\windows\system32\)</p>
<p>5. Reboot the pressing F8 on start-up to launch Windows in Safe Mode with Command Prompt</p>
<p>6. After Windows starts up login with the local Administrator account</p>
<p>7. Delete the virus definition files. To do so for VIPRE go to the definitions folder (C:\Program Files\Sunbelt Software\SBEAgent\Definitions\) and delete all the contents.</p>
<p>8. Reboot the system</p>
<p>Following this procedure we have been able to get all systems back up and running.</p>
<p>If you have experienced similar issues please leave a comment regarding your experience.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.thinkworx.com/2009/10/30/antivirus-definition-mistakenly-removes-winlogon-exe/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SQL Data Types</title>
		<link>http://blog.thinkworx.com/2006/11/13/sql-data-types/</link>
		<comments>http://blog.thinkworx.com/2006/11/13/sql-data-types/#comments</comments>
		<pubDate>Mon, 13 Nov 2006 14:27:35 +0000</pubDate>
		<dc:creator>Thomas Bowcut</dc:creator>
				<category><![CDATA[Handy References]]></category>

		<guid isPermaLink="false">http://blog.thinkworx.com/2006/11/13/sql-data-types/</guid>
		<description><![CDATA[I have found that on multiple occasions I have wanted to refer to the list of available data types in MS SQL or MySQL. I am currently working on a project in MS SQL and found the following definition of SQL data types. I am posting this to my list of handy references.


Data Types
Description


bigint
Integer data [...]]]></description>
			<content:encoded><![CDATA[<p>I have found that on multiple occasions I have wanted to refer to the list of available data types in MS SQL or MySQL. I am currently working on a project in MS SQL and found the following definition of SQL data types. I am posting this to my list of handy references.</p>
<table cellspacing="1" border="1">
<tr>
<th width="100" bgcolor="#333333"><strong><font size="2" face="Arial" color="#ffffff">Data Types</font></strong></th>
<th width="400" bgcolor="#333333"><strong><font size="2" face="Arial" color="#ffffff">Description</font></strong></th>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">bigint</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Integer data from -2^63 through 2^63-1</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">int</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Integer data from -2^31 through 2^31 &#8211; 1</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">smallint</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Integer data from -2^15 through 2^15 &#8211; 1</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">tinyint</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Integer data from 0 through 255</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">bit</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Integer data with either a 1 or 0 value</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">decimal</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Fixed precision and scale numeric data from -10^38 +1 through 10^38 -1</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">numeric</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Fixed precision and scale numeric data from -10^38 +1 through 10^38 -1</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">money</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Monetary data values from -2^63 through 2^63 &#8211; 1</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">smallmoney</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Monetary data values from -214,748.3648 through +214,748.3647</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">float</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Floating precision number data from -1.79E + 308 through 1.79E + 308</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">real</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Floating precision number data from -3.40E + 38 through 3.40E + 38</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">datetime</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Date and time data from January 1, 1753, through December 31, 9999,<br />
with an accuracy of 3.33 milliseconds</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">smalldatetime</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Date and time data from January 1, 1900, through June 6, 2079,<br />
with an accuracy of one minute</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">char</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Fixed-length  character data with a maximum length of 8,000 characters</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">varchar</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Variable-length  data with a maximum of 8,000 characters</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">text</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Variable-length  data with a maximum length of 2^31 &#8211; 1 characters</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">nchar</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Fixed-length Unicode data with a maximum length of 4,000 characters</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">nvarchar</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Variable-length Unicode data with a maximum length of 4,000 characters</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">ntext</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Variable-length Unicode data with a maximum length of 2^30 &#8211; 1 characters</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">binary</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Fixed-length binary data with a maximum length of 8,000 bytes</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">varbinary</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Variable-length binary data with a maximum length of 8,000 bytes</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">image</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">Variable-length binary data with a maximum length of 2^31 &#8211; 1 bytes</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">cursor</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">A reference to a cursor</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">sql_variant</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">A data type that stores values of various data types,<br />
except text, ntext, timestamp, and sql_variant</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">table</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">A special data type used to store a result set for later processing</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">timestamp</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">A database-wide unique number that gets updated every time<br />
a row gets updated</font></strong></td>
</tr>
<tr>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">uniqueidentifier</font></strong></td>
<td bgcolor="#dcdcdc"><strong><font size="2" face="Arial">A globally unique identifier</font></strong></td>
</tr>
</table>
<p>For additional information on choosing MS SQL Server data types, the source of the above table, refer to the following article:</p>
<p><font size="-1" face="Verdana, Arial, Helvetica, sans-serif"><a target="_blank" href="http://www.databasejournal.com/features/mssql/article.phpr/2212141"><font><strong>Choosing SQL Server 2000 Data Types</strong></font></a><br />
<strong>By   <a href="http://www.databasejournal.com/feedback.php/http://www.databasejournal.com/features/mssql/article.php/2212141">Alexander  Chigrik</a></strong><br />
</font></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.thinkworx.com/2006/11/13/sql-data-types/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
