Softpedia >Windows >Portable Software >Network >Network Drive Control >  Changelog

Network Drive Control Changelog

What's new in Network Drive Control 1.66

Mar 10, 2024
  • Disambiguated the CSV import menu label
  • Added a menu selection to open the online help rather than the installed help file This allows the user to see if the help files have been updated between releases Sometimes I will get questions from users where it's apparent I need to clarify the instructions or clarify how something works, rather than make a code change While I always could update the online help as needed, by adding a menu for users to jump directly to it, it makes it easier for users to check and see if the online help is more informative than the built-in help The on-line & built-in help are always synchronized when there's a new code release (they are both generated from the same HelpNDoc file)
  • Check that the window opens in the display of the moment, and if outside of it, bring it in In other words, check the coordinates the NDC window last saved against the present displays connected, and if the NDC window would be "off screen" for the PC, because for example, the monitor it should display on does not exist as can happen if a laptop with multiple monitors is being used as a stand alone laptop, then bring the NDC window onto an active display
  • Updated help files

New in Network Drive Control 1.65 (Feb 10, 2024)

  • Fixed bug where Windows 11 is sometimes reported as Windows 10 in the "About" box.
  • Added the ability to import drive mappings from a .CSV (comma separated value) file. Each line fof the file should be in the format of
  • Network Name, Drive Letter, Drive path, UserID, Password
  • with all fields in plaintext (including the password) and will be vetted on input as if it had been entered mannually using the "Add" button.
  • Updated help file.

New in Network Drive Control 1.64 (Nov 17, 2023)

  • Fixed bug where a code info box used during debugging was still active and could be displayed.
  • Updated help file.

New in Network Drive Control 1.63 (Nov 16, 2023)

  • Removed VM detection. Seems to cause issues on some machines. No one as said it's useful. (User reported issue.)
  • Fixed minor bug in the passing of parameters when connecting via WebDAV under some circumstances. (User reported bug.)
  • Updated help file. Expanded the WebDAV help with the suggestion that if folks have trouble with WebDAV it helps to try the connection using the Net Use command as then you explicitly get the resulting error codes without having to deal with NDC's log files.
  • Fixed minor bug when refreshing where WebDAV mapped connections did not display consistently.

New in Network Drive Control 1.62 (Aug 29, 2023)

  • Added feature that when the tray icon is used, the tray module checks the connection status of drives that should be mapped for the present network, and if any are not mapped (the logon mapping failed for some reason), another attempt at mapping the drive is made. (User requested feature.)
  • Changed the tray icon default to be "on".
  • Code signing certificate updated.
  • Updated help file.

New in Network Drive Control 1.61 (Feb 12, 2023)

  • Manual update check tells the user explicitly what the server says the present up-to-date version is, as well as the version NDC is running. I've made this change as it provides me with better positive feedback on how things are working.
  • The log file also now notes the two versions even when everything is up-to-date.
  • Updated help file.

New in Network Drive Control 1.60 (Jan 16, 2022)

  • Tested on Windows 11 VM's and satisfied compatible, so installer will now allow Windows 11 installations.
  • Export/import issue still not resolved due to a lack of time to focus on this issue. The root problem has to do with the way Windows identifies unique installations. Menu selections changed from grayed out to hidden, so they don't appear at all in the drop down menus.
  • Update help file.

New in Network Drive Control 1.58 (Dec 16, 2021)

  • Fixed bug where suppressing the path checkbox had stopped working due to a typo in Dialog Control constant assignment.
  • Problem with import/export functionality where the target machine could not import the settings and that process failing would be impossible for the user to fix without assistance due to issue #3 below. This appears to be an issue due to a recent Windows Update. Until it is resolved, Importing & Exporting are disabled. (User reported bug.)
  • Testing on Windows 11 shows instabilities which I believe are related to #2 above. So Innosetup is set to not do installs on Windows 11 systems for now.
  • Fixed bug in uninstaller where some System Registry entries were left behind.
  • The tray module wasn't always uninstalled if it was running during the NDC uninstall. Changed the Innosetup installer script so if need be, it will queue exe files in use for deletion at the next boot, and if triggered, will require a reboot at the end of the uninstallation.
  • Updated help file.

New in Network Drive Control 1.57 (Nov 14, 2021)

  • User reported NDC could not create a log file when his Document folder was redirected to reside an a non-System Disk drive. Issue appears to be with the way I was calling the Windows API function that retrives the user's Document folder, and I'm now calling it in a different way so it picks up the redirection if present. (User reported bug.)
  • Updated help file.

New in Network Drive Control 1.56 (Oct 19, 2021)

  • Updated help file.
  • Fixed bug where if a drive used the same "word" as the User ID and Password, while the configuration was stored properly, the drive could not be displayed or mapped properly. Using the same "word" as the User ID and Password is a really bad idea although it's sometimes used for "anonymous" user access. (User reported bug.)

New in Network Drive Control 1.55 (Apr 14, 2021)

  • Fixed a flicker that showed up on some test machines.

New in Network Drive Control 1.54 (Apr 12, 2021)

  • Added feature that when the tray icon is used, the tray module checks the network status to see if the PC has changed network connections, and if so, remaps the drives to match the new connection. This allows the laptop to adapt to being moved around from one network to another while the user is logged on. The check interval is 60 seconds.
  • Updated help file.

New in Network Drive Control 1.53 (Feb 28, 2021)

  • Updated help file.
  • Reversed the behavior of checking for updates to only run for users with Admin privileges. Appears under some circumstances Windows reports a user who has Admin privileges as not having them. Until I get to the bottom of this behavior, I am reversing this change.

New in Network Drive Control 1.52 (Feb 7, 2021)

  • Updated help file.
  • Change the 'check for updates' to only run for users with Admin privileges since non-Admin users can't run the installer.
  • If a user says they want the update, then NDC opens the default browser to directly download the zip file with the installerThis is because CNET has been having update issues and when the NDC web page is opened, too many people go for the (not yet updated) CNET download.
  • Fixed bug where use of INI file interfered with importing settingsProgram now temporarily disables use of the INI file (if it is being used), imports the settings, then (if it is being used) resumes use of the INI fileBug noticed while helping a user troubleshoot(User reported bug.)

New in Network Drive Control 1.51 (Feb 1, 2021)

  • Updated help file.
  • Added more error messages when a change isn't allowed to make it easier for the user to see what the issue is.
  • Have installer open the help file at end of installation.
  • Added the ability to also map a directory on a local drive to a drive letter. This isn't a network mapping, but is the equivalent of Command Line "subst" command. There is no use for the UserId or password, so they may be left blank. If you want the mapping to occur all of the time, use the * for the Network. (User requested feature.)
  • Fixed another bug where blank passwords show up as random characters in the display when passwords are displayed.
  • Updated program icon. (You will probably only notice if you use the tray.)

New in Network Drive Control 1.50 (Feb 1, 2021)

  • Updated help file.
  • Removed reference to the OS bit size (32 or 64) in the dialog frame titles & About message as people were misinterpreting what that meant.
  • Fixed bug where new installs would report a corrupted database when users were switched. Looking back through the code, this bug first appeared in v1.48 and looks like I failed to remove some test code inserted during the development of v1.48. (User reported bug.)
  • Updated how the NDC console behaves when it can't find window size settings. This only occurs the first time NDC is run from a user account which isn't the user who installed NDC. In that case, the NDC console window is small which is annoying. Once the user resized the NDC console, behavior was normal thereafter. Now, NDC will use the default windows size settings on first run.

New in Network Drive Control 1.49 (Oct 1, 2020)

  • Logging improved.
  • Message encoding improved.
  • Fixed code bug in "Export NDC Settings" menu selection that enabled a functionality that was not intended to be enabled (which didn't affect anything as I didn't try to use that functionality, but I'd rather it not have been enabled at all). That enabling also didn't create any type of security issue.
  • Option under the help menu to use INI file. If this option is set in the menu, then upon exiting NDC will save it's Registry Settings as an encapsulated Registry BLOB in the user's "DocumentsNDC Logs" folder as "Network_Drive_Control.INI". When NDC is started, it will check whether the INI file exists & is valid, and if so, will map it back on to the System Registry. In this way, one can make NDC portable. The INI file is not editable, and is not interchangeable with a setting export file. (User requested feature.)
  • Fixed minor installer bug. Fortunately, NDC has enough self checks & recovery routines that it functioned correctly despite this installer bug.
  • Fixed bug where a mapping with a null password could sometimes display random data when console set to display passwords. (User reported bug.)
  • Updated help file.

New in Network Drive Control 1.48 (Sep 16, 2020)

  • Fixed memory leak in the delete all drives routine.
  • Added ability to save all settings to a file with a "Export NDC settings" menu selection. The file is an encapsulated blob of System Registry data and is not editable.
  • Added ability to restore all settings from a file generated by the "Export NDC settings" function with a "Import NDC settings" menu selection. To use this to transfer settings between PC's, both PC's have to have the same version of NDC installed.
  • Changed the Console password system internals. This was done to allow changes 2 & 3 above to be implemented. Unfortunately the implementation of this means that if you had your console password protected in prior versions, after this update that protection was removed during the update. You can, of course, implement it again.
  • Updated help file.

New in Network Drive Control 1.47 (Aug 21, 2020)

  • Remember window size & position from last run.
  • Fixed bug that showed up sometimes when an account connection that does not use a password would try to connect.
  • Updated help file.

New in Network Drive Control 1.46 (Jun 17, 2020)

  • Fixed situation where update check would not understand when the website was unavailable. This is related to my web hosting company making behind the scene changes to the website's error reporting, as opposed to a fault in the program.

New in Network Drive Control 1.45 (Jun 4, 2020)

  • The update check was broken by my website hosting company changing something in their server setting having to do with redirection, I don't know exactly what. My old update code is something I wrote roughly 20 years ago where I was doing all of the heavy lifting. Rather than try to figure out what was going on, I wrote a new routine that uses the Windows WinInet API. In principle, this should keep working even as servers change as it gets updated as Windows & Edge get updated. When NDC asks michaelburns.net what the current version of NDC is (which it does by asking - no user info is sent), it does so via https.
  • Updated help file.

New in Network Drive Control 1.44 (Apr 5, 2020)

  • Fixed bug in "About" of tray icon where it reported the wrong version of NDC.
  • Fixed bug in System Tray toggle message.
  • Added warning if user manually enters a network name and it does not match a known network, and asks if that's what they intended. While adding an unknown network name may be a perfectly legitimate thing to do, and is allowed by NDC, this warning is to help catch typos. This is based on helping a user where the appearance on the screen obscured that this was the cause of the problem they were seeing.
  • Added additional logging info. After having investigated a problem, realized a little more info put into the log file would have saved a bit of time.
  • Updated help file.

New in Network Drive Control 1.43 (Mar 8, 2020)

  • Code signing certificate changed to a SHA256 one issued by Sectigo. Old one was a SHA1 issued by Digicert.
  • Added Caps Lock check to some of the password input boxes if passwords are hidden.
  • Added Windows version info to "About" box. (For Windows 10.)
  • Updated help file.

New in Network Drive Control 1.42 (Nov 30, 2019)

  • Added grip to bottom on Console window to make it easier to re-size.
  • Added allowing selection of multiple items for connection or disconnection. If multiple items are selected and any of the other buttons are pressed, only the top-most item is affected. (User requested feature.)
  • Updated help file.

New in Network Drive Control 1.41 (Nov 30, 2019)

  • Added "Connect All Possible" & "Disconnect All Possible" buttons.
  • Update help file to say how one can trigger NDC from a script(User request.)
  • Changed button & checkbox layout.
  • Made Console dialog re-sizableThe languages NDC is written in don't do this automatically, so I have to monitor the dialog size and handle it manually in callbacksThat's why I didn't do this earlier as I'm lazy(User requested feature.)
  • Updated help file.

New in Network Drive Control 1.40 (Nov 3, 2019)

  • Added Checkbox to console password request dialog to allow display of password.
  • Added Checkbox to console password set dialog to allow display of password.
  • Help file updated.

New in Network Drive Control 1.39 (Oct 6, 2019)

  • Added right-click context menus. Right clicking on a drive listing causes a context menu to open listing (Connect, Disconnect, Edit, Clone+Edit, Move Up, & Move Down).
  • Help file updated.

New in Network Drive Control 1.38 (Jun 5, 2019)

  • Fixed bug in periodic update check communication routine in the icon tray module. This is related to the mid-May addition of a SSL certificate to the michaelburns.net website. Module would sometimes mis-parse the response to it's asking michaelburns.net what the most up-to-date version of NDC is.

New in Network Drive Control 1.37 (Jun 1, 2019)

  • Fixed the update check communication routine which broke when I added a SSL certificate to the michaelburns.net website, which I did in mid-May 2019.
  • When NDC asks michaelburns.net what the current version of NDC is (which is does by asking - no user info is sent), it attempts to ask via https. Falls back to http if it has to.
  • Help file updated.

New in Network Drive Control 1.3.5 (Jan 10, 2019)

  • 1. Fixed bug where tray program could check for updates even when told not to.
  • 2. Installer now provides the option to create a System Restore point for the PC before installing NDC. I've not had any reports of NDC messing up PC's, but I like the idea of making it easy to roll back the install or update just in case. Note that Windows 8 & 10 normally won't allow a new System Restore point to be created unless 24 hours have passed since the last Restore Point was created. This interval can be changed in the System Registry. You can see how here: https://www.tenforums.com/tutorials/94682-change-system-restore-point-creation-frequency-windows-10-a.html Windows Vista & 7 do not have this 24 hour default System Restore interval.
  • 3. Binaries (exe files) are now digitally signed. This insures that any alterations of the exe's after I release them is detectable.
  • 4. Minor code cleanup.
  • 5. Updated help file.

New in Network Drive Control 1.3.4 (Nov 12, 2018)

  • No longer have console open automatically at end of installation to reduce confusion between that behavior & the installer's request to reboot system.
  • If System Tray icon active, and the "Automatically Check For Updates" is active, then the System Tray icon program will check for updates once per day. The check interval is once every 24 hours with the interval starting when the Tray icon program starts. This means that doing things like restarting the PC or toggling the NDC Console up may restart the interval. The program uses the Windows API SetTimer function & Windows message pump so the CPU utilization is basically unaffected.

New in Network Drive Control 1.3.3 (Oct 16, 2018)

  • Attached the NDC icon to other executables used by the installer/uninstaller. Just cosmetic.
  • Compiler for tray program set to optimize for speed rather than minimum size of binary. (To minimize it's use of Windows resources.) Other modules are still set for size optimization.
  • Fixed bug in NDC Console module where editing a drive mapping that had a null password could display random giberish in the password field. (User reported bug.)
  • Updated help file

New in Network Drive Control 1.3.2 (Sep 18, 2018)

  • Added keeping the focus on a given item when the "Move Up" & "Move Down" buttons are used to make it easier to perform repeated moves on the same item.
  • Add a menu item that causes a tray item to be present that when clicked on, brings up the Console. Normally no part of NDC is running after the drives are mapped. Nor is any part of NDC running after the Console is closed. But if one opts to have a System Tray icon, then a small program will remain running that calls the Console when left clicked. Right clicking on the tray icon gives the user the option to stop the icon program. (User requested feature.)
  • Updated help file.

New in Network Drive Control 1.3.1 (Jul 30, 2018)

  • Changed the way the display refreshes when the "Move Up" & "Move Down" buttons are used so that it refreshes faster.
  • Fixed typos in help file.

New in Network Drive Control 1.3 (May 21, 2018)

  • Fixed bug introduced in v1.29 where manually connected mapped drives with the correct drive letter & path did not display as connected because the network was incorrect. Now, any drive that is connected will display as connected if the drive letter and path are correct even if the network is not correct.
  • Added "Move Up" & "Move Down" buttons to allow reordering of the Network Drives list (move a row up or down in the list). This is probably not an issue for 99.9% of users, but my drive list has 16 entries most of which are rarely used, but are necessary. The drive ordering is not entirely cosmetic in that when the user logs into their account, NDC checks whether to try to map a drive in the order listed. Depending on the system, this order may be important.
  • Updated help file.

New in Network Drive Control 1.29 (Apr 10, 2018)

  • Updated help file.
  • Security improvements on checking for active network interface.
  • Added caps lock check when passwords are entered on top of any Windows may perform.
  • Re-architected the "Connected ?" column to filter by network. If a given drive letter was connected, and that drive letter was used multiple times, all of the instances would display the connection status even those to the other networks. This was due to the way Windows reported connection status by drive letter. Now, only the drive actually mapped for the active network(s) shows the active connection status.

New in Network Drive Control 1.28 (Feb 4, 2018)

  • Fixed typo in help file & release notes.
  • Fixed bug introduced in v1.25 which triggered a password too long error in the Add/Edit dialog when the password was null. (User reported bug.)
  • Code cleanup.

New in Network Drive Control 1.27 (Jan 25, 2018)

  • Security improvements on server communications when program checks for updates.
  • Security change on drive mapping databasev1.26 & earlier will not be able to correctly recognize mapped drives created or edited with v1.27 or later versionsv1.27 & later versions will however, correctly recognize mapped drives made with v1.26 & earlier versions, and automatically convert them to the v1.27 database formatThis means that downgrading from v1.27 or later to v1.26 or a lower version isn't possible once mapped drives are created or modified by v1.27 or later, unless the v1.27 or later mapped drives are deleted and recreated with the older version
  • Fixed typo in database corruption error message.
  • Updated help files.

New in Network Drive Control 1.25 (Jan 9, 2018)

  • Additional security checks on inputs with an eye towards preventing possible buffer overflows when accessing the Windows API. So now the console checks for passwords to be less than 128 characters, UserIDs less than 104 characters, Network Names less than 32 characters, Paths less than 248 characters (260 minus the 8.3's 12 characters). Note, as near as I can tell, the Windows GUI will only allow you to create UserID's as large as 20 characters, but larger ones can be created programatically. SSID's (which Windows will consider a WiFi networks "network name") are limited to 32 characters. In a future version, I may allow the user to set these sizes smaller to better match policy restrictions admins may have imposed on machines. If anyone thinks these defaults should be changed, I'd like to hear from you.
  • Code cleanup.
  • Added post install one-time check for updates. While my site & CNET are the only sites I support, many others now carry NDP and some don't update their setups often.
  • Compiler set to optimize for minimum size of binaries rather than speed. (NDC is not a numerically intensive program so the speed hit is negligible.)
  • Innosetup script change to display welcome screen showing the version about to be installed.
  • Help file updated. Typos fixed. Support link added.
  • Help menu area reorganized. Support menu selection added.
  • Added system calls to update system icons faster in strategic places within the program. (User requested feature.)

New in Network Drive Control 1.24 (Dec 18, 2017)

  • Fixed bug where the "present drive" could disappear when the edit dialog was open. (User reported bug.)
  • Added the "present drive" to the drive list when the edit dialog is open.
  • Changed how the edit & add dialog behaves when conflict warnings are acknowledged by the user. Now the dialog stays present making corrections easier.
  • Updated Help file.

New in Network Drive Control 1.23 (Dec 14, 2017)

  • Updated Help file
  • Fixed typo in manual update check message dialog
  • Fixed bug introduced in v121 where when editing an existing mapping, hitting the Cancel button on the edit dialog causes the last mapping on the list to be deleted (User reported bug)
  • Fixed bug where when editing an existing mapping, hitting the Save button on the edit dialog can cause the dialog to hang (User reported bug)

New in Network Drive Control 1.22 (Dec 11, 2017)

  • Updated Help file
  • Added System-menu box in the console's main dialog title bar (X in upper right that can close the application) (User requested feature)
  • Added Minimize button in the console's main dialog title bar (_ in upper right that can minimize the application) (User requested feature)
  • When adding or editing a drive, if a network has been selected in the "Network Name" box, then the available driver letters in the "Drive" box is filtered of any drive letters already taken by prior network mappings on that network removed The drive list was already filtered to remove drive letters already assigned to hard/optical drives One can still manually type any drive letter into the box, but if a conflict is created the user is warned & the configuration is not saved (User requested feature)
  • Minor code cleanup to Innosetup installer script
  • Added Windows & Mircosoft trademark statement when dialog shown when "About" menu option chosen

New in Network Drive Control 1.21 (Nov 27, 2017)

  • Set Innosetup to only allow the installer to run if Windows Vista or higher.
  • Enhanced logging info.
  • Enhanced OS determination by displaying the OS build version (helps me when dealing with Windows 10 related bugs).
  • Added ability for anonymous connections to mapper drives (i.eno UserID), in which case the user leaves the User ID field blank of the Add/Edit dialog(User requested feature.)
  • Added ability to leave NDC settings intact during an uninstall in case NDC is reinstalled laterWindows won't be able to use saved NDC settings to do any drive mapping(Default is to not delete all NDC settings.)
  • Fixed bug where hitting cancel on a "Clone + Edit" could result in a duplicate drive being created.
  • Updated Help file.

New in Network Drive Control 1.20 (Nov 9, 2017)

  • Minor security improvements.
  • Reorder TAB order on main dialog
  • Reorder TAB order on secondary dialog
  • Added more input validations.
  • Added a wildcard selection (*) for Network name, so that one can use NCD to mount drives for all networks.
  • Added check to prevent wild card Network from conflicting with a non-wildcard mapping.
  • Change the start delay from being in minutes to being in seconds.
  • Added Innosetup mod to convert the existing startup delay (if there is one) from minutes to seconds.
  • Updated Help file.

New in Network Drive Control 1.19 (Oct 20, 2017)

  • Removed Redpill VM Check Only use RDTSC counter method for VM checking Redpill seemed to cause problems under Windows 2016 Server
  • Added operating system check Part of debugging issue fixed by #1 above
  • Added OS identification when dialog shown when "About" menu option chosen
  • Updated Help file
  • Fixed issue in Innosetup where not all items always appeared in the Windows start menu

New in Network Drive Control 1.19 (Oct 20, 2017)

  • Removed Redpill VM Check Only use RDTSC counter method for VM checking Redpill seemed to cause problems under Windows 2016 Server
  • Added operating system check Part of debugging issue fixed by #1 above
  • Added OS identification when dialog shown when "About" menu option chosen
  • Updated Help file
  • Fixed issue in Innosetup where not all items always appeared in the Windows start menu

New in Network Drive Control 1.18 (Aug 14, 2017)

  • Updated Help file.
  • Added a check when a drive is added, so that it does not conflict with an existing mappingi.eYou can't have more than one entry where both the Network Name and Drive Letter are the same as some other entry.
  • Indicates if a WebDav mapping reports it is encrypted.

New in Network Drive Control 1.17 (Aug 14, 2017)

  • Changed how drives mapped with no password are displayed.
  • Fixed bug where trailing "/" in path (for SMB, CIFS or Netbios paths) would cause problems.

New in Network Drive Control 1.16 (Aug 14, 2017)

  • Fixed typo in download file name.
  • Provided allowance for shares where the password is blank.
  • Updated help files.

New in Network Drive Control 1.15 (Apr 21, 2017)

  • Display refresh on Console run as separate thread. This can sometimes speed up the screen refreshing.
  • Add a "remove all mapped drives" menu option.
  • Additional Innosetup changes to facilitate a cleaner uninstall process.
  • Fixed issue that started happening after the April 11, 2017 Windows Updates where the program would hang trying to refresh the drives list when connected to a VPN.

New in Network Drive Control 1.14 (Dec 19, 2016)

  • The add mapped drive dialog drop-down list of drive letters now lists all drive letters not already used by the PC's internal hard drives & optical drives (One has always had the ability to assign any drive letter by typing it in, even those letters not in the drop-down list,and that feature still exists)
  • Minor display bug fix
  • Help file updated

New in Network Drive Control 1.13 (Dec 16, 2016)

  • Add network type for active connections.
  • Moved log files to the users Documents folder in a "NDC Logs" subdirectory. This allows the logging to work even if not run with Administrator privileges. Also, this more consistent with the fact that the NDC settings are user specific.

New in Network Drive Control 1.12 (Dec 6, 2016)

  • Added ability for user to turn on logging that generates local log files to disk to help me or them to diagnose problems. No credential info is every written to the log files, however the server path is. Files are not erased, so they can accumulate and take up disk space, so leaving this turned on is not recommended. (Default is off for privacy. User needs to opt-in.)
  • Minor help file improvements.
  • Added WebDAV protocols to types of drive mappings. See caveats in help file in the "Permissions & Other Issues" section.
  • Updated help files to include WebDAV.
  • Minor bug fix on menus.
  • Fixed bug in Inno Setup installer script that pointed to outdated product URL.

New in Network Drive Control 1.11 (Dec 6, 2016)

  • Minor cleanup of look to the Network Drives list.
  • Minor errors in help file corrected.
  • Minor error checking improvements.
  • Security improvements in variable handling, mainly additional explicit overwriting of RAM holding sensitive info once that info is no longer needed before releasing the RAM to the Operating System.
  • Minor change to the version check to detect an error with the remote server.

New in Network Drive Control 1.10 (Oct 17, 2016)

  • Added "Clone + Edit Drive" button to make it easier to duplicate a drive to be connected to via another Network name.
  • Security improvements to memory handling & network mapping storage. v1.9 & earlier will not be able to correctly recognize mapped drives created or edited with v1.10. v1.10 will however, correctly recognize mapped drives made with earlier versions. This means that downgrading from v1.10 to a lower version isn't possible once mapped drives are created or modified by v1.10, unless the v1.10 mapped drives are deleted and recreated with the older version.
  • Minor bug fixes.

New in Network Drive Control 1.9 (Oct 17, 2016)

  • Fixed bug in Inno Setup installer script that could cause an error when NDC is first run after installation.
  • Minor code cleanup.

New in Network Drive Control 1.8 (Oct 17, 2016)

  • Added user adjustable time delay after logon before attempting to map drives. This can be useful if the PC is on a network that takes a long time to stabilize its network connections.

New in Network Drive Control 1.7 (Oct 17, 2016)

  • Updated copyright notice.
  • Fixed minor display bug in Network Drives list where multiple drives could sometimes inadvertently be selected.
  • Added an optional improved detection method for whether network is up & running sufficiently to connect drives by adding an "aggressive" mode for network detection. (Default is off for privacy. User needs to opt-in.)

New in Network Drive Control 1.6 (Oct 17, 2016)

  • Added detection for when web.com (who hosts my site) is having reliability problems, and when that occurs, the update check will not offer an upgrade.

New in Network Drive Control 1.5 (Oct 17, 2016)

  • Fixed minor display bug in Network Drives list.

New in Network Drive Control 1.4 (Oct 17, 2016)

  • Security improvements to memory handling such as tighter explicit overwriting of RAM holding sensitive info once that info is no longer needed.

New in Network Drive Control 1.3 (Oct 17, 2016)

  • Added mutex checking to prevent multiple instances of program from running at the same time.

New in Network Drive Control 1.2 (Oct 17, 2016)

  • Added ability for user to force the console to manually check for updates.
  • Added ability for user to turn on automatic checking for updates on logon & when console is opened. (Default is off for privacy. User needs to opt-in.)

New in Network Drive Control 1.1 (Oct 17, 2016)

  • Added ability to edit existing network drive mapping.