1. 64 bit programs
2. New Programs
3. Retirements
4. Changes to Multiple Programs
5. Changes to Individual Programs

Release Notes for JRButils for Netware V18

Changes to Multiple Programs

• Updated netcopy, fsupdate, movehome and the GUI whodidit to strip backslashes from NFS names when copying NFS files and directories which can be created by Macintoshes. While the backslash is a valid character in NFS names, its use is not supported by NCP, and an attempt to create an entry incorporating that character results in error 0x899C (invalid path). Removing the backslash is consistent with the behaviour of Novell's Server Consolidation Utility.
• Updated netcopy, fsupdate, movehome and the GUI whodidit to copy resource forks associated with NFS files. These may be created by Macintoshes. At this point there does not appear to be any way to check for and copy Mac finder information for NFS files.
• Updated netcopy, fsupdate, movehome and the GUI whodidit to do internal file copies in smaller chunks i.e. 5 MB instead of 50 MB. This reduces an issue in the Part 2 and Part 4 versions where the program is unresponsive to scrolling the output while an individual copy request to the server is in progress. Note that the use of internal copies remains unavailable on Vista, Windows 7 and W2008 R2 due to a limitation of the Novell 2.0 Client.
• Fixed an issue in all Windows versions of programs where jrberr.msg was being found only if it was in the current directory or in the same location as the program.
• Updated all Linux versions of programs to locate jrberr.msg when it was not in the current directory, or the same directory as the program, but somewhere in the search path.
• Updated programs such as jrbmap, home2 and setcx which attempt to modify the parent cmd.exe to retain environment changes e.g. a relative path for a mapped drive. On 64 bit Windows 7, the 32 bit versions previously reported "Cannot obtain the module handle for the parent process" but they now fail without error. It is not possible for a 32 bit process to modify a 64 bit parent process. All other functions of these programs work correctly in 32 bit versions run on 64 bit Windows. Use the 64 bit versions of these programs (see above) on 64 bit Windows.
• Updated the logging options in the fully GUI programs which do not display their results in a list view. Changes include:
  • Added a "No logging" radio button to turn off logging.
  • Changed the "Append" option from a radio button to a check box.
  • Fixed an issue where the starting directory in the "Open file" dialog was inconsistent, depending on previously selected options.
  • Made numerous minor enhancements to improve the behaviour.
  • Corrected an issue where file names given on the command line via /l and /e were ignored.
• Fixed an issue in various Linux versions of programs where a path was not expanded correctly when using a mapping in the form /root/b/abc.
• Fixed an issue in various Linux versions of programs where the case was not retained for the names of input files. This did not matter on an NSS volume, but was an issue particularly when running programs on SLED clients.
• Fixed inconsistencies across both Windows and Linux platforms where log file names were sometimes converted to lowercase, rather than the exact case being retained.
• Made changes to programs processing Windows drives to correct an issue where they reported "access denied" when verifying the path while logged in as administrator, but that account held no rights to the path. This has been overcome by invoking backup privilege.
• Fixed a cosmetic issue in the tree view used to select eDirectory objects in fully GUI programs where on Windows 7, due to the thicker outer border, the bottom of the object class combo box was obscured.
• Fixed a cosmetic issue in numerous programs where error messages could refer to "a Organization" or "a Organizational Unit". The article "an" is now used where appropriate.
• Fixed an issue on W2008/Vista/W7 where if programs were run repeatedly e.g. in a provisioning script, the process would begin to run more slowly or the programs would fail reporting "No connection to a file server". The problem occurred if the program failed to close all connection handles and came about through an architectural change in the Novell 2.0 SP1 client. The problem does not occur under the 4.91 client on XP or under the Novell client for Linux. All programs have been checked for unclosed connection handles and tested by running 2000 times in succession on Windows 7. However, this testing has revealed that Novell's libraries are also responsible for some leaks. These affect programs which deal with NDPS/iPrint printers, and those which map drives as in jrbmap and home2. Novell expect a solution to the unclosed connection handle problem to be incorporated into SP2, scheduled for release in late 2011 or early 2012.
• Modified all programs to report "Insufficient resources" instead of "No connection to a file server" when a connection cannot be established due to the problem in the previous item preventing allocation of a new handle.
• Fixed an issue in netcopy, fsupdate and the GUI whodidit where they could fail to truncate a file to the copied length when replacing the file with a shorter one on a Windows drive.
• Modified netcopy, fsupdate, movehome and the GUI whodidit to not attempt to retain compression when copying files under the Novell 2.0 SP1 client. The function NWSetCompressedFileSize returns error 0x8836 (invalid parameter) under this client but works correctly under the 4.91 client. The use of this function is understood to be essential to ensure that the logical size of the new compressed file is set correctly.