Network Drive Manager - 2.5

Windows - especially XP - does not properly reconnect network drives after logon that have been configured using Map Network Drive in Windows Explorer with the "Reconnect at logon" feature checked. Although they will be remembered, they are usually not activated. This behavior causes problems e.g. when you use a server that is mapped to a network drive to store your documents and settings. If an application is launched that uses the settings stored on the network drive it will complain or even fail to start because the network location is not available. Even if the network drive was reconnected properly, another problem will arise after a few minutes because Windows will de-activate the network drive if they're not accessed in a while. Although the network drive is obviously working fine in Windows explorer, your application probably cannot access it.
NDM is a dedicated tool for managing network drives. During windows logon it will reconnect the network drives that are configured using NDM. After connection they will also be kept 'alive' to prevent de-activation. In case NDM is launched before any network connection is available (this is likely the case after starting Windows on your computer) a short interval mechanism is used to reconnect the network drives until they are connected where after a longer interval mechanism is put in place.