| Opera Remote |
|
Opera Remote - Installation issues Quickstart 1. Ensure that Opera will run in a DOS Window on the Windows NT server / NT Pro / 2000 Server / 2000 Pro system which you will be running Opera Remote. In particular:- * CONFIG.NT should allocate sufficient file handles, Windows NT defaults
to 20, * The data path specified in your Opera Company Profile should be appropriate for server based operation and specify drive letters that are visible from the server. If it is the name of a subdirectory within your Opera directory (e.g. DATA then you should have no problems (see note below re. Opera for Windows). 2. The original PEGLOGO.EXE program should be removed, this program only displays the Opera Logo but because it switches into Graphics mode it will cause the system to fail. Deleting PEGLOGO.EXE is not detrimental to Opera however its absence will briefly cause a ‘bad command or filename’ message to be displayed. This can be suppressed by copying the PEGLOGO.EXE file included with Opera Remote into the Opera program directory. This program does nothing but its presence suppresses the error message. N.B. If your user re-installs, or upgrades Opera then you must make sure the original PEGLOGO.EXE is not re-installed. To avoid this you may wish flag the original as READ ONLY. If Opera will not run on your server or starts and hangs immediately and you have a multi-processor system then the chances are that Microsoft Windows NT Service Pack 4 has not been applied. This corrects a bug in Windows NT and must be applied for correct operation of Opera Remote. If Opera Remote is closing as soon as you enter your password and you are using the Administrator user which you know as local logon access please ensure your firewall is not blocking port 23. Please refer to the main user guide for details on changing the port Opera Remote uses. Having validated that Opera will run correctly on your server, you can install Opera Remote. Opera Remote for Opera for Windows (16) Consider the situation where Opera is installed in a directory on a drive that the server sees as drive C: but your Windows clients have it mapped as drive F: The company parameters would be set to F:\Opera\DATA which the server sees as C:\Opera\DATA, in these circumstances you will need to map the same drive letter on the server use the Net Use command for this. e.g. NET USE F: \\servername\C$ To make sure this substitution stays valid you may wish to include it in your k_start.bat file At the server A registration key will be forwarded to you within 30 days, the software will be fully functional in the meantime. Create a script to log users into Opera, this can either be by individual user name or a global script for the system as a whole, if a script is specified for a user then it takes precedence over a global script. A global script goes in the INSTALLATION_PATH\SCRIPTS directory Installation path is normally C:\OR_TNET The manual describes how to create scripts but the sample K_START.BAT file included with the system is a good point from which to start. The file looks like this: echo off For testing purposes you may wish to have an empty user script to take you to a DOS prompt. N.B. The above script will feed keystrokes to gracefully terminate Opera in the event of the server losing contact with the client. If your server is a little slow you may wish to increase the number after each SLEEP command. If you have confirmation turned on in Opera then you may need an additional ESC,SLEEP2 at the start of the string. Script parameters are explained in the user manual scripts section. At the client If the client is a Windows NT workstation simply run SETUP.EXE, or
copy the If the client is not Windows NT or Windows 95 then you cannot run the Opera Remote Client, it may however be possible to use a 3rd party Telnet client but this will lead to some loss of functionality. N.B. The client consists solely of one program, there are no DLL’s so it can happily be copied/e-mailed to other users. If you wish you can modify the Opera Remote shortcut to include parameters as detailed below: The following command line parameters may be used -uUsername This specifies name of the user -pPassword This specifies password for the user. Use '.' if user has no password. -dDomain This specifies the domain of the user. Use '.' if you want to user default domain or no domain. -hHostname This specifies host name to connect to. -HHeartbeatTime This specifies our client side heartbeat. You need that parameter for the session cleanup!! Example- Host: soloman GS_CLNT -H150 -hsoloman -ujohndoe -pfastest -d. //the last dot is for the default domain. Keyboard Input
If you wish to print on a printer local to the client then that Printer should be shared using the standard Windows NT ‘NET USE’ command. Network connection For Modem connections you would normally install Microsoft Remote Access Server on the server and Microsoft Dial-Up Networking on the client. ISDN connection Opera Remote generates no superfluous ISDN network traffic, if however the Opera Clock is turned on then it will constantly update the client’s screen and the line will never drop. For this reason we provide a utility to turn off the clock. To utilise this copy the included SQSTART.FXP file to the Opera program directory and include the line SET CLOCK=OFF in your script. Because Opera Remote generates no superfluous network traffic, there has to be a way for the server to detect that the client is no longer there. This is achieved using a ‘heartbeat’ where the client effectively says to the server, ‘unless you hear from me in n seconds, assume I have gone and terminate the application’. Individual circumstances will determine the heartbeat interval, a setting of 3,600 would mean that if the remote user has started Opera Remote but not used the application, then after an hour the client would send a message to the server saying ‘I’m still here’. If on the other hand the client has been switched off or suffered a system failure then the absence of the heartbeat would cause the server to shut down the application. This would mean that there would be at least one ISDN call per hour from the client to the server. Alternatively you can set the server timeout (see manual). This then says that if there is no activity from the client in the defined time period then the application will be shut down. In this instance there will be no unnecessary ISDN calls but the user will have to log back in after a period of inactivity. Opera Remote makes calls on Windows network services via the WINSOCK interface, and has no networking elements of its own. You should therefore ensure that your network connection is set up correctly. Windows 95 in particular is notorious for creating network traffic that causes ISDN calls on some types of ISDN connection, we urge you strongly when installing an ISDN connection to monitor your line usage. Remember that mouse as well as keyboard activity causes traffic between the client and server, it is therefore prudent to minimise the Opera Remote Window when it is not in use. Using Opera Remote with Novell Netware Gateway Services for Netware presents Netware directories as if they were native Windows NT resources. Smaller Installations can use Windows NT Workstation with Client Services for Netware (again a standard component). There is however a documented problem whereby multiple virtual machines cannot have access to the same volume on a Netware Server. The way around this is to have separate login scripts for each user and include a different Net Use command with each. The workaround is however messy compared to the elegance of the NT server approach. If the Novell server is called SERVER, the required disk volume is called SYS and Opera is in a directory called OPERA then Opera Remote Scripts would look something like this: User1 SET LRA_TERMINATION=ESC,SLEEP2,ESC,SLEEP2,ESC,SLEEP2,ESC,
SLEEP2, Q,SLEEP2,ESC,SLEEP3,Q,SLEEP2,Y,sleep9 User 2 SET LRA_TERMINATION=ESC,SLEEP2,ESC,SLEEP2,ESC,SLEEP2,ESC,
SLEEP2, Q,SLEEP2,ESC,SLEEP3,Q,SLEEP2,Y,sleep9 User 3 SET LRA_TERMINATION=ESC,SLEEP2,ESC,SLEEP2,ESC,SLEEP2,ESC,
SLEEP2, Q,SLEEP2,ESC,SLEEP3,Q,SLEEP2,Y,sleep9
|
