Likno Software Blog – Drop-Down Menus, Javascript Menus, DHTML Menus

Run-time error 339: Component ‘UniBox210.ocx’ or one of its dependencies not correctly registered

If you are getting the above (or similar) error, it is likely that there was a problem with the installation. There are many reasons this could happen, such as not having enough access rights or having other applications running during the installation.

The first thing you should try is to:

1) Uninstall the application.

2) Make sure that all its files are removed. Check under “Program Files” if you have 32-bit windows or “Program Files (x64)” if you have 64-bit windows.

3) Close any other applications that are running.

4) Re-install the application.

If this does not work, then you should try to manually register the specific components that are not being registered, as follows:

1) Go to the windows start menu and find “Command Prompt”.

2) Right-click on it and select “Run as administrator”.

3) When the User Account Control asks if the program should be allowed to make changes, click “Yes”.

4) The Command Prompt will open in Administrator mode. There, write the following commands and press Enter after each one:

If you have 32-bit windows:

regsvr32 c:\windows\system32\UniBox10.ocx
regsvr32 c:\windows\system32\uniflexsup.dll
regsvr32 c:\windows\system32\UniBox210.ocx
regsvr32 c:\windows\system32\UniBoxVB12.ocx
regsvr32 c:\windows\system32\UniGrid210.ocx
regsvr32 c:\windows\system32\UniFlexGrid10.ocx

If you have 64-bit windows:

regsvr32 c:\windows\sysWOW64\UniBox10.ocx
regsvr32 c:\windows\sysWOW64\uniflexsup.dll
regsvr32 c:\windows\sysWOW64\UniBox210.ocx
regsvr32 c:\windows\sysWOW64\UniBoxVB12.ocx
regsvr32 c:\windows\sysWOW64\UniGrid210.ocx
regsvr32 c:\windows\sysWOW64\UniFlexGrid10.ocx

After running each line, you should get a “succeeded” popup window like the following:

5) Try running the application again. This time it should open without problems.

Hello!

We have released new version of AllWebMenus Pro: Version 5.3 build #884.

Check out What's New:

- New "CSS Menu" Genre option. Contrary to the "Javascript menu", the "CSS menu" implementation is designed so that:

• it is Section 508, WCAG, WAI, DDA compliant (accessible menus required by certain governmental agencies in US, UK, Australia),
• it uses "lighter" code, due to the less features it supports (lack of submenu opening/closing effects etc.),
• it is still functional when the javascript is disabled on the browser (degrades gracefully and still functions as a menu).

The above advantages come with a cost: some features and options of the feature-rich "Javascript menu" implementation cannot be supported by CSS. These differences are documented at the related AllWebMenus Help Topic on "Menu Genre", or here in PDF:

http://www.likno.com/downldd/AllWebMenus_Manual.pdf#page=48

- Fixed an issue for iPad related browsers where the "Menu Floats on Scroll" feature was not working properly.

- Fixed an issue with the application freezing when a certain configuration existed.

- Fixed an issue where a border appeared in focused items (Chrome, Safari & IE9 only).

- Fixed a Chrome issue for all "Server-Side" related menus, where the menu images did not load correctly after a back or forward of the page.

All features here: http://www.likno.com/allwebmenusinfo.html

Download the new version of our CSS menu builder at http://www.likno.com/download.html

Hello!

We have released new version of AllWebMenus Pro: Version 5.3 build #882.

Check out What's New:

- Added an option to have a default "Menu-Linking Code in Tags" value for new menu projects (in "Tools > Customize AllWebMenus").

- Fixed an issue when using a Modal Window call with a menu that uses the ULLI population method.

- Fixed an issue with the positioning of sliding menus when a Doctype exists in page (IE only).

- Fixed an issue where a background color was taken from a css file (IE9 only).

- Fixed an issue where a variable of the javascript libraries conflicted with some user variables (Mozilla based only).

- Fixed an issue where floating images appeared in page even though the menu did not appear at all (Opera only).

- Fixed an issue with Keyboard Navigation on sliding menus: they did not open when the "left arrow" key was pressed.

- Fixed a minor issue for a user who used the following line in his CSS:
table { display:block; }

- Minor GUI fixes

Download the new version of our CSS menu builder at http://www.likno.com/download.html

Hello!

We have released new version of AllWebMenus Pro: Version 5.3 build #880.

Check out What's New:

- Added the "Keyboard Navigation" property to specify if the user can navigate through the menu by using the keyboard (arrow keys). "Shift-F12" gives the focus to the first item of the Main Menu, so that the user can then use the arrow keys to navigate from there.

- Enhanced the "Manually trigger groups" positioning method with more options (method also renamed to "Manually trigger Main Menu or any Group on user action").

- Fixed a minor issue when two or more "Server Side Menus" exist in the same page: image preloader was trying to preload non existing images.

- New version for all "Server Side Menus API" related products.

- Fixed an issue where submenus with unfolding effects didn’t appear properly in Chrome 64-bit environments only.

Download the new version at http://www.likno.com/download.html

For menu positioning you always had the option to use your own (custom) ID, through the Custom ID option. For example, you may be using a Content Management System that already applies its own "id" tag to every page element, thus not allowing you to add the AllWebMenus Default ID to your selected element. In that case, you simply copy this "id" of your selected element and paste it as Custom ID in AllWebMenus.

Alternatively (since Build #878), you can use a Custom "Class" instead of an "ID", in case that your authoring tool or CMS does not allow you to edit the "ID" attribute (or the "ID" values change dynamically) but does allow you to add/edit the "Class" attribute.

For example, if you select the "Custom Class:" option and add the menupositioner value there, you can then use this code in your page to achieve menu positioning:

<span class="menupositioner">&nbsp;</span>