KarlOttenstein‘s tip on using the WIBU -Key Control Panel!
The sometimes considerable delay while ArchiCAD is starting is actually the WIBU protection key driver searching all ports for the key. You can change things so that only the proper port is searched, making startup considerably (at least for me) faster! For ArchiCAD 10, I saw the time to display the Start dialog drop from 45 seconds to 12 seconds!”
Exit ArchiCAD if open.
Under Start menu, choose Settings/Control Panel ( Windows 2000 ) or simply Control Panel (Windows XP).
Open the WIBU-Key Control Panel and select the Setup tab. If you do not see the Setup tab, left-click the title bar of the WIBU dialog and click on Advanced.
You can change each port one by one: click on each supported port on the left and CLEAR the check mark on the right under Port setting that says “Enabled (port accessed by WIBU-KEY driver)” …EXCEPT for the port that your key is plugged into. For most of the Windows users (7.0 and above), that would be the USB port as most now have USB keys.
Or you can shift-click to select and modify a group of ports all at once. In the port list below, we could click on LPT1 and then shift-click on PcCard6 to highlight all of those ports. Any changes to the port settings change all highlighted ports at once.
After you have updated the settings click OK.
WIBU key will now only check the port that is enabled making the startup of ArchiCAD faster. (Editor’s note: on my HP Omnibook XE3 the speed gain was about 2 seconds. )
NOTE: Be careful since a mistake at step 4 (disabling all ports for example, or leaving only the wrong ports enabled) would prevent you from running the control panel again to re-enable the wibu key port. In this case it is recommended to re-install the WIBU software driver.
Speeding Things Even More
If your keyplug is used on a single workstation and is not accessed over a network, you can speed things up even more by disabling the network features. You can always change back, or just reinstall the driver if you need network support in the future.
Under the Server tab, clear the checkmark for WkLAN, which disables TCP/IP access to the key:
Under the server WkNet tab, clear the checkmark for Active:
This may be sufficient, but it doesn’t hurt to go to the Network tab and clear all of the checkmarks for Subsystems: Local (kernel), WkLAN and WkNet :