Tag: registry-hack

WinXP: How to Deactivate the “Windows Genuine Advantage Tool”

To re­move Mi­crosoft’s new “Win­dows Gen­uine Ad­van­tage-Tool”, which in the cur­rent ver­sion will check the sys­tem’s li­cense every day against a Mi­crosoft data­base, sim­ply re­move the reg­istry key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\ CurrentVersion\WinLogon\Notify\WGALogon

VisualStudio.NET: Text-Editor Guide at 80

Guiding lines in VS.NET 2005It is still con­sid­ered good style to keep code-lines within a cer­tain bound (e.g. 80 char­ac­ters). IDEs like Eclipse offer to dis­play a red guid­ing line at the cho­sen off­set to help de­vel­op­ers keep within this bound.

By mod­i­fy­ing the reg­istry a sim­i­lar guide can be en­abled for Vi­sual Stu­dio 2003 / 2005. Add a string value Guides to the key (VS.​NET 2005, VS 2003 has ver­sion 7.1)

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\Text Editor.

Set the value to

RGB(128,0,0) 80

To have mul­ti­ple guides (like in the screen­shot), add the ad­di­tional columns space de­lim­ited, e.g.

RGB(128,0,0) 80 100

Ackn.: This in­for­ma­tion has been pro­vided by Hannes Pavelka in Mi­crosoft’s news­group mi­crosoft.​public.​dotnet.​languages.​csharp, Mes­sage-ID: <e1­jag7$qk7$02$1@​news.​t-​online.​com> (Ar­ti­cle in Google Groups):

Changing MSDE Authentication Scheme After Installation

If you are using Mi­crosoft SQL Server 2000 Desk­top En­gine (MSDE 2000) you are sup­posed to de­cide if you are going to use “in­te­grated win­dows au­then­tifi­ca­tion” only or if you are using “mixed mode au­thet­i­ca­tion”. Lat­ter is some­times con­sid­ered less se­cure but if you are de­vel­op­ing ASP.​NET ap­pli­ca­tions it can be eas­ier to use a non-NT user for the con­nec­tion.

If you ever tried that you are surly fa­mil­iar with the “login is not as­so­ci­ated with a trusted con­nec­tion” ex­cep­tion when try­ing to ac­cess the data­base. Today I had to in­stall an ASP.​NET ap­pli­ca­tion on a server with MSDE where mixed mode au­then­ti­ca­tion was not avail­able. A quick re­search on the net re­vieled a blog entry in­di­cat­ing how to change the au­then­ti­ca­tion scheme of MSDE after the in­stal­la­tion.

  • Stop the MSDE ser­vice
  • Search the reg­istry for

    HKEY_LO­CAL_­MA­CHINE\Soft­ware\Mi­crosoft\MSSqlserver\MSSqlServer

    (for un­named in­stances) or

    HKEY_LO­CAL_­MA­CHINE\Soft­ware\Mi­crosoft\Mi­crosoft SQL Server\In­stance Name\MSSQLServer\

    (for named in­stances)

  • Change the key LoginMode to value 2.

Un­like a com­ment on the page, value 0 will not work (at least it didn’t in my case).