Opera is configured to be fast and efficient. This requires that the underlying communications software is fully compliant with the winsock standard and that it is able to handle multiple connections simultaneously. With most winsock implementations this is not a problem, but some implementations
are somewhat incomplete or unable to handle the load. In the worst case this will lead to a program crash. Then next time you start Opera, Opera will show this dialog. If the problem is infrequent, you can probably just press 'cancel' and continue. If not, you can try out some of the settings and see if that helps. If it does, you should save these settings in the advanced settings dialog (just open it and select 'OK').
NB: Most of the changes will lead to slower net access.
Do Not Load Documents at Startup - This choice enables you to start Opera without fetching any documents. You can then do any necessary changes to the advanced settings and thus solve the problem. This choice is needed if Opera will not start due to problems with the communications
software. You may, however, also select any of the choices below. That may cure the problem as well.
Minimize number of simultaneous connections - Opera will by default fetch a great number of documents and images at the same time. Some communications programs (winsock) are unable to handle this. If this is a problem, you can reduce the number of simultaneous connections. This
setting reduces the number of connections to 4. This setting is normally set in the advanced settings.
Minimize network buffer size - Some implementations of winsock require a certain size for a network buffer. This choice sets the size of the buffer to 1 kb. This setting is normally set in the advanced settings.
Synchronous DNS - Some implementations of winsock do not have support for asynchronous DNS (convention from names of machines to numbers). Changing this setting will make Opera work with these implementations.
