InfiniTec - Henning Krauses Blog

Don't adjust your mind - it's reality that is malfunctioning

RSS feed registrations in Outlook 2007 disappear - the solution

If you have many RSS feed registrations in Outlook 2007, you may have noticed that at some point newly added RSS feeds start disappearing. They are added successfully, but on the next restart of Outlook, the registration is just gone.

You can work around this by setting the registry key DisableRoaming in HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\RSS to 1. If this key is not yet present, create it with a type of DWORD.

You'll have to restart Outlook for the change to take effect.

But be cautious: I don't know which side-effects this registry might have.

Currently rated 4.5 by 2 people

  • Currently 4.5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Categories: Miscellaneous articles
Posted by Henning Krause on Thursday, July 12, 2007 6:00 PM, last modified on Friday, July 13, 2007 6:00 AM
Digg It! DZone It! StumbleUpon Technorati Reddit Del.icio.us NewsVine Furl BlinkList
Permalink | Comments (2) | Post RSSRSS comment feed

Finalbuilder 5 crashing instantly when started

I got my copy of FinalBuilder a few days ago, and installed it right away. Unfortunately, it crashed the instant I ran it. Turns out, its the licensing scheme they are using. Its broken by the "Data Execution Prevention" feature in Vista which is supposed to protect one from buffer overflows. So you'll need to add the FinalBuilder executables to the exclusion list, like in this screenshot:


(click to enlarge)

Add the files ActionStudio.exe and FinalBuilder5.exe from the FinalBuilder program directory to the list.

I hope they fix this soon.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Categories: Miscellaneous articles
Posted by Henning Krause on Wednesday, March 14, 2007 6:00 PM, last modified on Thursday, March 15, 2007 2:00 PM
Digg It! DZone It! StumbleUpon Technorati Reddit Del.icio.us NewsVine Furl BlinkList
Permalink | Comments (0) | Post RSSRSS comment feed

Howto: Change the default download directory for Internet Explorer

Solution

The default download directory for Internet Explorer is the My Document folder. To change this location, follow these steps:

  1. Open the registry editor and navigate to HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer.
  2. Create a new value of type String and name it Download Directory
  3. Open the new value and enter the new directory.

The result should look like this:


Registy editor with changed default folder for the Internet Explorer (click to enlarge)

Currently rated 1.7 by 3 people

  • Currently 1.666667/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Categories: Miscellaneous articles
Posted by Henning Krause on Wednesday, May 24, 2006 6:00 PM, last modified on Wednesday, August 30, 2006 6:00 AM
Digg It! DZone It! StumbleUpon Technorati Reddit Del.icio.us NewsVine Furl BlinkList
Permalink | Comments (0) | Post RSSRSS comment feed

Vortrag in der .NET Usergroup in Paderborn vom 09.01.2006

Zusammenfassung

Am 09.01.2006 habe ich einen Vortrag in der .NET Usergroup Paderborn gehalten. Vorgestellt wurden einige ASP.NET Features und einige der neuen Security Features in .NET 2.0

Inhalt

Die folgenden Themen kommen in dem Vortrag vor:

  • ASP.NET Features
    • URL Rewriting
    • Eigene SitemapProvider
    • Caching
    • ObjectDatasource
    • XML Transformationen mit Extension Objekten
    • Mehrsprachigkeit
  • Security
    • SecureString
    • Sichere Passworteingabe
    • Passwörter speichern (ProtectedData, ProtectedMemory)

Downloads

Usergroup Vortrag 2006-01-09.ppt (1,433,600 Bytes)
Der Vortrag als Powerpoint Datei
Beispiele.zip (60,673 Bytes)
Die Beispiele aus dem Vortrag

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Categories: Miscellaneous articles
Posted by Henning Krause on Saturday, January 14, 2006 6:00 PM, last modified on Sunday, January 15, 2006 6:00 AM
Digg It! DZone It! StumbleUpon Technorati Reddit Del.icio.us NewsVine Furl BlinkList
Permalink | Comments (0) | Post RSSRSS comment feed

Sentinel Protection Dongle wird über ein Netzwerk nicht gefunden

Symptome

Wird ein Sentinel Dongle über ein Netzwerk benutzt (insbesonders Dial-Up oder VPN Verbindungen), so kann es vorkommen das der Dongle von der Client Applikation nicht nich gefunden wird, obwohl der Dongle auf dem Server eingesteckt ist.

Ursache

Der Sentinel Protection Server bindet sich nicht auf die allgemeine IP Adresse (0.0.0.0/0), sondern explizit auf jede verfügbare IP Adresse und wartet auf UDP Port 6001 auf eingehende Verbindungen.

Ändert sich eine IP Adresse oder wird eine neue Verbindung aufgebaut (z.B. eine VPN Verbindung), bekommt der Sentinel Protection Server dies nicht mit.

Lösung

Bei jeder Änderung von IP Adressen muss der Dienst "Sentinel Protection Server" (SentinelProtectionServer) neu gestartet werden:

    1 net stop SentinelProtectionServer

    2 net start SentinelProtectionServer

Alternativ kann die angehängte Software benutzt werden. Es handelt sich dabei um einen Windows Dienst, der bei Änderungen an der Netzwerkkonfiguration (neue IP-Adresse oder Aufbau einer DFÜ Verbindung) den in der Konfigurations-Datei angegebenen Dienst neustartet. Um den Sentinel Protection Server neustarten zu lassen, tragen Sie den Dienstnamen "SentinelProtectionServer" in die Konfigurationsdatei NetworkAddressMonitorService.exe.config:

    1 <?xmlversion="1.0"encoding="utf-8" ?>

    2 <configuration>

    3     <configSections>

    4         <sectionGroupname="applicationSettings"type="System.Configuration.ApplicationSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >

    5             <sectionname="InfiniTec.NetworkAddressMonitorService.Properties.Settings"type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"requirePermission="false" />

    6         </sectionGroup>

    7     </configSections>

    8     <applicationSettings>

    9         <InfiniTec.NetworkAddressMonitorService.Properties.Settings>

   10             <settingname="ServiceToRestart"serializeAs="String">

   11               <value>SentinelProtectionServer</value>

   12             </setting>

   13         </InfiniTec.NetworkAddressMonitorService.Properties.Settings>

   14     </applicationSettings>

   15 </configuration>

Downloads

NetworkAddressChangeSericeSetup.exe (441,457 Bytes)
NetworkAddressMonitorService Setup
NetworkAddress Monitor Service.zip (17,003 Bytes)
Quellcode

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Technorati: , , , ,

Tags: , , , ,

Categories: Miscellaneous articles
Posted by Henning Krause on Tuesday, January 10, 2006 6:00 PM, last modified on Saturday, January 14, 2006 6:00 AM
Digg It! DZone It! StumbleUpon Technorati Reddit Del.icio.us NewsVine Furl BlinkList
Permalink | Comments (0) | Post RSSRSS comment feed

Mount a CD/DVD image via context menu in the Explorer using Daemon-Tools

More Information

The daemon tools are by default set up to start a small program that is accessed via the system tray, near the clock. With a right-click on the program icon, one can easily mount and unmount images, or change the number of virtual drives on the fly.

However, one often comes accross an image with an explorer window. To mount such an icon, the user must do the following:

  1. Right-click on the daemon-tools tray icon

  2. Navigate to the virtual drive, where the image should be mounted

  3. Choose Mount image.

  4. In the Open file dialog, navigate to the folder

  5. Click Ok.

Luckily, the daemon tools have a rich set of command line parameters, so most of the above steps can be eliminated.

     

Solution

To allow the mounting of images via the context menu, the image files must be associated with the daemon tools. To do this apply the following registry information to your computer:

    1 Windows Registry Editor Version 5.00

    2 [HKEY_CLASSES_ROOT\DaemonTools.File]

    3 @="CD/DVD Image"

    4 [HKEY_CLASSES_ROOT\DaemonTools.File\shell]

    5 @="open"

    6 [HKEY_CLASSES_ROOT\DaemonTools.File\shell\mount1]

    7 @="Mount Image on Second Virtual Drive"

    8 [HKEY_CLASSES_ROOT\DaemonTools.File\shell\mount1\command]

    9 @="\"C:\\Program Files\\D-Tools\\daemon.exe\" -mount 1,\"%l\""

   10 [HKEY_CLASSES_ROOT\DaemonTools.File\shell\open]

   11 @="Mount Image on First Virtual Drive"

   12 [HKEY_CLASSES_ROOT\DaemonTools.File\shell\open\command]

   13 @="\"C:\\Program Files\\D-Tools\\daemon.exe\" -mount 0,\"%l\""

   14 [HKEY_CLASSES_ROOT\.iso]

   15 @="DaemonTools.File"

   16 [HKEY_CLASSES_ROOT\.nrg]

   17 @="DaemonTools.File"

   18 [HKEY_CLASSES_ROOT\.bin]

   19 @="DaemonTools.File"

   20 [HKEY_CLASSES_ROOT\.cue]

   21 @="DaemonTools.File"

   22 [HKEY_CLASSES_ROOT\.bwt]

   23 @="DaemonTools.File"

   24 [HKEY_CLASSES_ROOT\.cdi]

   25 @="DaemonTools.File"

   26 [HKEY_CLASSES_ROOT\.ccd]

   27 @="DaemonTools.File"

   28 [HKEY_CLASSES_ROOT\.mds]

   29 @="DaemonTools.File"

   30 [HKEY_CLASSES_ROOT\.pdi]

   31 @="DaemonTools.File"

The above registry file is designed for two virtual drives. If you have more or less drives, you'll have to modify this area of the file:

    1 [HKEY_CLASSES_ROOT\DaemonTools.File\shell\mount1]

    2 @="Mount Image on Second Virtual Drive"

    3 [HKEY_CLASSES_ROOT\DaemonTools.File\shell\mount1\command]

    4 @="\"C:\\Program Files\\D-Tools\\daemon.exe\" -mount 1,\"%l\""

    5 [HKEY_CLASSES_ROOT\DaemonTools.File\shell\open]

    6 @="Mount Image on First Virtual Drive"

    7 [HKEY_CLASSES_ROOT\DaemonTools.File\shell\open\command]

    8 @="\"C:\\Program Files\\D-Tools\\daemon.exe\" -mount 0,\"%l\""

    9 For a third drive, simply add the following lines:

   10 [HKEY_CLASSES_ROOT\DaemonTools.File\shell\mount2]

   11 @="Mount Image on Third Virtual Drive"

   12 [HKEY_CLASSES_ROOT\DaemonTools.File\shell\mount2\command]

   13 @="\"C:\\Program Files\\D-Tools\\daemon.exe\" -mount 2,\"%l\""

 

Note that you must replace the path to the Daemon tools folder.

Downloads

daemontools_2drives_english.zip (548 Bytes)
A registry file preconfigured for 2 drives, for an english version of Windows.
daemontools_2drives_german.zip (541 Bytes)
A registry file preconfigured for 2 drives, for a german version of Windows.

Currently rated 5.0 by 1 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Categories: Miscellaneous articles
Posted by Henning Krause on Thursday, December 30, 2004 6:00 PM, last modified on Sunday, December 25, 2005 6:00 AM
Digg It! DZone It! StumbleUpon Technorati Reddit Del.icio.us NewsVine Furl BlinkList
Permalink | Comments (1) | Post RSSRSS comment feed

Scripts no longer function after you run an ASP.NET page which displays performance data

Symptoms

After you view an ASP.NET webpage which displays performance counter data via the PerformanceCounter class, scripts no longer function. This includes scripts launched from a command line as well as client-side scripts in any browser window that is opened after you viewed the original page. Scripts are working again after you have stopped the Word Wide Publishing service.

Cause

A deadlock occurs because of a bug in one of the WMI providers. An event tracing is done which calls the RegisterTraceGuids API which in turn calls into one of the WMI Service hosted within the Services.exe.

Resolution

A hotfix is available from Microsoft, at least in english and german.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix for KB834010. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS

Status

This problem was first corrected in Microsoft Windows XP Service Pack 2

Steps to reproduce the problem

  1. Create a new ASP.NET web application
  2. Add a label control to the page
  3. Add this code to the Page_Load event:

    4.     1 using (PerformanceCounter counter = new PerformanceCounter())

        2 {

        3     counter.CategoryName = "Memory";

        4     counter.CounterName = "Available MBytes";

        5     Label1.Text = counter.NextValue().ToString();

        6 }

  4. Compile the application

  5. Open the webform with Internet Explorer

  6. Now, open any website which has client-side scripting

References

See KB Article 834010 for more information

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Technorati: , , , , , , ,

Tags: , , , , , , ,

Categories: Miscellaneous articles
Posted by Henning Krause on Tuesday, May 31, 2005 3:46 PM, last modified on Sunday, December 25, 2005 6:00 AM
Digg It! DZone It! StumbleUpon Technorati Reddit Del.icio.us NewsVine Furl BlinkList
Permalink | Comments (0) | Post RSSRSS comment feed

Repair a corrupted MDAC installation

Affected products

  • Windows XP
  • Windows 2003
  • MDAC 2.71
  • MDAC 2.8

Summary

The MDAC component is a set of components that allow uniform data access to various data sources. These components can become corrupted. This article outline a way to manually repair the MDAC components.

Symptoms

If a program that accesses databases via ADO (ActiveX Data Objects) or similar displays the error message
The specified Procedure was not found
this indicates, that the MDAC installation is damaged.
Additionally, a new installation of the MDAC components does not solve the solution.

Solution

If a reinstallation of the MDAC components does not solve the problem, try the following steps to manually repair the MDAC components:

  1. Download the MDAC setup suite in the version that is already installed on your system. It can be found on the Microsoft Download website.

  2. Open a command prompt and change to the directory where you saved the file.

  3. Type
    MDAC_TYP /c /t:<myfolder>
    where <myfolder> is a folder on your harddisk, e.g. c:\temp\mdac

  4. Change the current folder to <myfolder> and type the following:
    md temp
    expand mdacxpak.cab temp -f:*.*

  5. Cut-and-paste the following code snippet into a text editor and save it as makedirs.cmd in the <myfolder>\temp directory:
    @echo off
    md ADO
    copy /b MSADER15.DLL ADO
    copy /b MSADO15.DLL ADO
    copy /b MSADO20.TLB ADO
    copy /b MSADO21.TLB ADO
    copy /b MSADOMD.DLL ADO
    copy /b MSADOR15.DLL ADO
    copy /b MSADOX.DLL ADO
    copy /b MSADRH15.DLL ADO
    copy /b MSJRO.DLL ADO
    md MSADC
    copy /b MSADCE.DLL MSADC
    copy /b MSADCER.DLL MSADC
    copy /b MSADCF.DLL MSADC
    copy /b MSADCFR.DLL MSADC
    copy /b MSADCO.DLL MSADC
    copy /b MSADCOR.DLL MSADC
    copy /b MSADCS.DLL MSADC
    copy /b MSADDS.DLL MSADC
    copy /b MSADDSR.DLL MSADC
    copy /b MSDAPRSR.DLL MSADC
    copy /b MSDAPRST.DLL MSADC
    copy /b MSDAREM.DLL MSADC
    copy /b MSDAREMR.DLL MSADC
    copy /b MSDFMAP.DLL MSADC
    md "OLE DB"
    copy /b MSDADC.DLL "OLE DB"
    copy /b MSDAENUM.DLL "OLE DB"
    copy /b MSDAER.DLL "OLE DB"
    copy /b MSDAORA.DLL "OLE DB"
    copy /b MSDAOSP.DLL "OLE DB"
    copy /b MSDAPS.DLL "OLE DB"
    copy /b MSDASC.DLL "OLE DB"
    copy /b MSDASQL.DLL "OLE DB"
    copy /b MSDASQLR.DLL "OLE DB"
    copy /b MSDATL2.DLL "OLE DB"
    copy /b MSDATT.DLL "OLE DB"
    copy /b MSDAURL.DLL "OLE DB"
    copy /b MSXACTPS.DLL "OLE DB"
    copy /b OLEDB32.DLL "OLE DB"
    copy /b OLEDB32R.DLL "OLE DB"
    copy /b OLEDB32X.DLL "OLE DB"
    echo.
    echo Finished !!
    :eof

  6. In your command prompt window, change to the directory where you extracted the cab file.

  7. Start the above file by typing
    makedirs.cmd

  8. The above batch file has now created three directories within the current directory, , MSADC and OLE DB. These three directories must now be placed under the %CommonProgramFiles%\system directory.

  9. Now, cut-and-paste the following snippet into a text editor and save it as RegFiles.cmd in the %CommonProgramFiles%\system directory:
    @echo off
    echo Unregistering DLLs...
    for %%a in (ado\*.dll msadc\*.dll "ole db"\*.dll) do regsvr32 /u /s %%a
    echo Finished.
    echo Reregistering DLLs...
    for %%a in (ado\*.dll msadc\*.dll "ole db"\*.dll) do regsvr32 /s %%a
    echo Finished.

  10. Within your command prompt, change the current directory to %CommonProgramFiles%\system and type the following:
    RegFiles.cmd
    This will de-register the MDAC components and the re-registers them.

References

This solution was taken from the newsgroup microsoft.public.data.ado. The name of the thread was Repair a corrupted MDAC 2.71 installation - the Solution. Many thanks to the author Jens Geyer

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Technorati: , , , , , , ,

Tags: , , , , , , ,

Categories: Miscellaneous articles
Posted by Henning Krause on Friday, December 31, 2004 9:13 AM, last modified on Sunday, January 02, 2005 12:23 PM
Digg It! DZone It! StumbleUpon Technorati Reddit Del.icio.us NewsVine Furl BlinkList
Permalink | Comments (0) | Post RSSRSS comment feed

100% CPU-Auslastung durch den CSRSS Prozess, und Untermenüs öffnen erst nach einigen Sekunden

Affected products

  • Windows 2003
  • Tweak UI for Windows XP/2003
Symptoms
The CSRSS process consumes about 100% of the cpu under certain circumstances, such as opening an Outlook mail folder. Additionally, cascading menus open only with a significant delay.

Solution

One possible cause for this is the Tweak UI tool from Microsoft. This tool exposes a bug in that it sets the MenuShowDelay to zero. In fact, the lowest valid value for this setting is one. To correct this, follow these steps:

  1. Open the registry editor.

  2. Navigate to the HKEY_CURRENT_USER\Control Panel\Desktop node.

  3. Double-Click the MenuShowDelay entry.

  4. Set the value of this entry to 1.

  5. Close the registry editor.
    The changes are loaded the next time you log on to your computer.

More informations

The Tweak-UI tool from Microsoft is a tool to configure several aspects of the user interface from Windows. One of these settings is the delay for cascading menus.

Status

The status of this problem is unknown.

Currently rated 5.0 by 1 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Technorati: , , , ,

Tags: , , , ,

Categories: Miscellaneous articles
Posted by Henning Krause on Friday, December 31, 2004 8:49 AM, last modified on Friday, December 31, 2004 8:49 AM
Digg It! DZone It! StumbleUpon Technorati Reddit Del.icio.us NewsVine Furl BlinkList
Permalink | Comments (0) | Post RSSRSS comment feed

Radeon 9000 Driver under Windows 2003 produces STOP 50 (PAGEFAULT_IN_NONPAGED_AREA)

Affected products

  • Windows 2003
  • ATI Radeon/FireGL 9000

Symptoms

When the Radeon/FireGL 9000 drivers are installed under Windows 2003, the system produces a STOP 50 (PAGE_FAULT_IN_NON_PAGED_AREA) every time it is restarted.

Workaround

To work around this problem, restart the system in safe mode and remove the video driver. Also, you can use the last good known configuration. After the removal of the driver, restart the system and then set the hardware acceleration of the video adapter to full. To do this, follow these steps:

  1. Right-click the desktop and select Properties.

  2. Select the Settings tab.

  3. Click Advanced.

  4. Select the Troubleshoot tab.

  5. Move the Hardware acceleration slieder to maximum.
    The drivers can now be safely reinstalled.

Status

The status of this problem is unknown, but it seems to be solved in the current driver release.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Technorati: , , , ,

Tags: , , , ,

Categories: Miscellaneous articles
Posted by Henning Krause on Friday, December 31, 2004 8:36 AM, last modified on Friday, December 31, 2004 8:38 AM
Digg It! DZone It! StumbleUpon Technorati Reddit Del.icio.us NewsVine Furl BlinkList
Permalink | Comments (0) | Post RSSRSS comment feed