HowTo - Windows « Geekzine.org

Archive for the HowTo - Windows Category

\SystemRoot\System32\RDPDD.dll failed to load

Posted in HowTo - Windows on October 23, 2008 by aristomagnus

From: http://blogs.technet.com/brad_rutkowski/archive/2008/01/04/systemroot-system32-rdpdd-dll-failed-to-load.aspx

This is an FYI post for an issue we’ve seen on a couple of Windows 2003 SP2 servers internally. Hopefully if someone hits this in the wild they’ll be able to find this post on the intertubes.

Symptom:

When attempting to connect from the client via RDP, you would click “connect” and then soon after it would silently fail and “connect” would be clickable again.

Each time when attempting to connect, the server would log this event:

Event Type:   Information
Event Source: Application Popup
Event Category:      None
Event ID:     26
Date:         9/25/2007
Time:         12:13:57 PM
User:         N/A
Computer:     ServerX
Description:
Application popup: : \SystemRoot\System32\RDPDD.dll failed to load

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00000000 006c0002 00000000 4000001a
0010: c0000017 c000009a 00000000 00000000
0020: 00000000 00000000

Our Resolution

A) We found that in our cases it was an issue with the ATI driver and by either rolling back the ATI driver for the display on the server or upgrading the display driver on the server resolved the issue. Reports in the comments show the same for Nvidia drivers

B) In another instance it was found that by going to: Display Properties –> Settings –> Advanced –> Troubleshoot, turn off “Hardware acceleration” resolved the issue as well without adjusting the drivers.

C) On the internet I’ve seen posts showing SFC to help but in my cases it did not.

Update from comments:

D) A solution found at http://forums.nvidia.com/index.php?showtopic=67147&hl=remote%20desktop&st=60 worked for me (and others.)

It’s a registry fix that increases the size of the session image space. Add the following key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

“SessionImageSize”=dword:00000020

Where 00000020 is hex for 32

In any case the event was a red herring and was just a generic error being bubbled up from Win32k.sys..

Create a text file and copy that in it. Rename the extension with .reg - double click on it to apply - reboot to take effect.

————————————————-

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Memory Management]
“ClearPageFileAtShutdown”=dword:00000000
“DisablePagingExecutive”=dword:00000000
“LargeSystemCache”=dword:00000000
“NonPagedPoolQuota”=dword:00000000
“NonPagedPoolSize”=dword:00000000
“PagedPoolQuota”=dword:00000000
“PagedPoolSize”=dword:00000000
“SecondLevelDataCache”=dword:00000000
“SystemPages”=dword:000c3000
“PagingFiles”=hex(7):43,00,3a,00,5c,00,70,00,61,00,67,00,65,00,66,00,69,00,6c,\
00,65,00,2e,00,73,00,79,00,73,00,20,00,34,00,30,00,39,00,36,00,20,00,34,00,\
30,00,39,00,36,00,00,00,00,00
“PhysicalAddressExtension”=dword:00000001
“SessionViewSize”=dword:00000030
“SessionPoolSize”=dword:00000004
“WriteWatch”=dword:00000001
“SessionImageSize”=dword:00000020

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Memory Management\PrefetchParameters]
“VideoInitTime”=dword:00000639
“EnablePrefetcher”=dword:00000003
“AppLaunchMaxNumPages”=dword:00000fa0
“AppLaunchMaxNumSections”=dword:000000aa
“AppLaunchTimerPeriod”=hex:80,69,67,ff,ff,ff,ff,ff
“BootMaxNumPages”=dword:0001f400
“BootMaxNumSections”=dword:00000ff0
“BootTimerPeriod”=hex:00,f2,d8,f8,ff,ff,ff,ff
“MaxNumActiveTraces”=dword:00000008
“MaxNumSavedTraces”=dword:00000008
“RootDirPath”=”Prefetch”
“HostingAppList”=”DLLHOST.EXE,MMC.EXE,RUNDLL32.EXE”

———————————————————

Leave A Comment »

How do I flush DNS?

Posted in HowTo - Général, HowTo - Linux, HowTo - Mac OS X, HowTo - Windows on October 2, 2008 by aristomagnus

From: http://www.tech-faq.com/flush-dns.shtml

Most DNS clients cache the results of name resolution requests. This speeds up name resolution if multiple lookups are done to the same address, such as is common when browsing the web.

Sometimes a bad DNS entry will be cached and you will need to either flush the DNS cache to get rid of it, or wait up to 24 hours for it to be dropped from the cache automatically.

How to Flush DNS in Microsoft Windows

In Microsoft Windows, you can use the command ipconfig /flushdns to flush the DNS resolver cache:

C:\>ipconfig /flushdns
Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

You can also use the command ipconfig /displaydns to view the DNS resolver cache.

Turning off DNS Caching under Microsoft Windows

If you experience frequent issues with DNS caching under Microsoft Windows, you can disable client-side DNS caching with either of these two commands:

net stop dnscache
sc servername stop dnscache

This will disable DNS caching until the next reboot. To make the change permanent, use the Service Controller tool or the Services tool to set the DNS Client service startup type to Disabled.

Tuning DNS Caching under Microsoft Windows

You can modify the behavior of the Microsoft Windows DNS caching algorithm by setting two registry entries in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters registry key.

The MaxCacheTtl represents the maximum time that the results of a DNS lookup will be cached. The default value is 86,400 seconds. If you set this value to 1, DNS entries will only be cashed for a single second.

MaxNegativeCacheTtl represents the maximim time that the results of a failed DNS lookup will be cached. The default value is 900 seconds. If you set this value to 0, failed DNS lookups will not be cached.

How to Flush DNS in Mac OSX

In Mac OSX Leopard, you can use the command dnscacheutil -flushcache to flush the DNS resolver cache:

bash-2.05a$ dnscacheutil -flushcache

In Mac OSX versions 10.5.1 and before, the command lookupd -flushcache performed the same task:

bash-2.05a$ lookupd -flushcache

How to Flush DNS in Linux

In Linux, the nscd daemon manages the DNS cache.

To flush the DNS cache, restart the nscd daemon.

To restart the nscd daemon, use the command `/etc/init.d/nscd restart`.

Leave A Comment »

Augmenter la limite de RAM d’une application (Windows 32bits)

Posted in HowTo - Windows on November 15, 2007 by aristomagnus

Vous saviez que le maximum que Windows XP 32 bits peut utiliser en RAM est de 4gb. Ceci est relié au 32 bits d’adresse. Je ne rentrerai pas dans les détails car ce post n’est pas de cette nature.

Vous voudriez que vos application puisse utiliser 3gb? Rien de plus simple, vous devez éditer boot.ini qui ce trouve dans C:\boot.ini

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=”Microsoft Windows XP Professional” /noexecute=optin /fastdetect /3GB

Vous ajouté l’attribut /3GB et le tour est joué. Évidemment, vous devez redémarrer votre ordinateur pour que le changement prenne effet. boot.ini est lu seulement au démarrage de Windows.

Notez bien que ce n’est pas toutes les applications qui supporte la mémoire étendu à 3gb. Par exemple, Autodesk AVID ne supporte pas bien cette option.

Mais elle peut s’avérer très utile pour l’application AfterEffect 7 par exemple qui la supporte et même qui est recommandé par Adobe.

Lien Microsoft: http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx

Leave A Comment »