MIB Smithy 4.0.8 provides bug fixes for the following issues:

• The right-click popup menu in the Project Tree will no longer show for Type/Value Assignment virtual folders as it was actually showing the menu for the module. Consequently, selecting “Remove” would remove the module, rather than all Type/Value Assignments as one might expect.
• A “record search string is ambiguous” error would occur when sorting OIDs for generating some output formats if the name assigned to one of those OIDs was also used in another module.
• An “invalid command name” error could occur when trying to show the calendar popup for REVISION and LAST-UPDATED timestamps due to a trace not being removed after the popup is hidden.
• Removed conversion of spaces to HTML entities in help file:// URLs under Windows to prevent errors launching help when MSIE 7 is the default browser.

Changes affecting MIB Smithy:

• A “wrong # args” error could occur when previewing a single OBJECT-TYPE in SMI format (the error did not occur when previewing the whole module).

Changes affecting both MIB Smithy and MIB Smithy SDK:

• The “piberrors” type in the XML-SMI Schema document was not correct and did not match the implementation and has been corrected.
• Newlines and carriage returns in OCTET STRING values were forcing conversion to hex (such as in varbind values in responses) as if they were on-printable characters.
• A crash could occur if the environment variable for pointing to the license key file were mistakenly set to a directory instead.

There was another issue with the table SEQUENCE definition relocation change merged into 4.0.4 and not fixed in 4.0.5 that caused them to be generated twice rather than once. This could cause a module that was saved to fail to load back into MIB Smithy later.

Also, when such failure occurred due to the duplicate definition, double-clicking on the error in the compiler log should have opened the text file editor for manual correction, but instead caused an “invalid workspace type” error.

Both of these issues have been corrected in the 4.0.6 release.

The change for grouping table SEQUENCE definitions with the table and entry OBJECT-TYPEs made in 4.0.4 was not completely merged into the 4.0.x branch. As a result, a “wrong # args” error could occur when generating or saving modules in SMI format. The problem has been corrected in this patch release.

Minor Changes

• Documentation should now conform to XHTML 1.0 Strict rather than just HTML 4.0.1 Transitional.
• SEQUENCE definitions for tables are now output where they usually appear in standard MIB modules, rather than at the top of the module with other type assignments.

Bug Fixes

• Error “bad window path name” could occur when closing and re-opening SNMP Tools.
• In the Syntax property window, selecting class filter “All” and module filter “– All –” did not show derived types in the “Primary Type” combobox.
• Error ‘can’t read “shortName”: no such variable’ would occur in the Table View when trying to view a table where columns did not share a common prefix (e.g. due to indexes from other tables).

NOTE: Earlier versions of the Windows builds of our software products were built using MSVC6 and we have switched over to MSVC8 for improved C++ standards and STL support necessary for new features that are under development. Unfortunately the installer project files are not compatible between MSVC6 and MSVC8, requiring them to be recreated from scratch, and were issues with the automatic conversion of the other project files.

As a result, there was a problem with the initial Windows build for MIB Smithy Evaluation and MIB Smithy Standard (MIB Smithy Professional was unaffected), so if you had problems running 4.0.4, such as an error regarding the “smilib” package not being found, this should be fixed in the 4.0.4 build posted March 19th.