There is no additional installation needed in order to run ATS as an application. Just launch it. You can do that manually from the Start..Run dialog, or more likely, you’ll want to set up a shortcut. The command line syntax is:
<path>\atsd.exe –i <miame.ini spec> -a <ashw32.exe spec> -p <port> <other switches> <cmd>
For example:
C:\vm\miame\bin\atsd.exe –i c:\vm\miame\miame.ini –a c:\vm\miame\bin\ashw32.exe –p 9923 start
Although that is probably enough said, here are a few more comments about the switches:
Switch |
Description |
|---|---|
-i <ini> |
This mandatory switch must be followed by the full path specification of the MIAME.INI file, which is typically the same one used by A-Shell. The only parameter which is currently essential from the MIAME.INI file is the SERIAL= line, although it is likely that future releases of ATSD may use other parameters from the MIAME.INI. |
-a <ashw32> |
This mandatory switch must be followed by the full path specification of the A-Shell/Windows executable, which is normally ashw32.exe. This is how ATSD.EXE launches the A-Shell/Windows sessions. |
-p <port> |
This optional switch may be used to specify the port number on which incoming Telnet connections will be accepted. The default is 23, which is the normal port for Telnet. Possible reasons for changing it would include avoiding conflict with the standard Windows telnet service (which is incompatible with A-Shell), improved security, or other firewall-related issues. Make sure the port is open to the clients in the firewall. |
-l <fspec> |
Log file. If specified, ATSD will record in the log file all connection, disconnection and startup events. |
-ntts |
This is actually an A-Shell switch, and thus like any other switch not recognized by ATSD will be passed on to A-Shell. It is noted here specifically because it adjusts the way A-Shell identifies independent client sessions in a way that is typically essential for ATSD. Without it, multiple sessions may end up with the session identifier and clobber each others' job table records. Note that this switch requires A-Shell 6.5.1639.0+ or 6.4.1558.2+; older versions should be updated, or you can add OPTIONS=NTTS to the miame.ini. |
-z |
Causes ATSD to run from the system tray (icons in the lower right corner of the Task Bar). Otherwise it runs as a normal application. If running from the system tray, you can display the user interface by double-clicking on the icon in the system tray. |
-proto2 |
Enables a second and newer protocol for launching the A-Shell child sessions. While the old protocol was fine in 99% of the cases, some NIC drivers did not support it, with the result that sessions would appear to connect and then instantly disconnect. When the -proto2 command line switch is passed to ATSD.EXE (either via the ATSDSRV.INI or a shortcut), it now uses Microsoft-recommended WSADuplicateSocket protocol. This protocol requires ASHW32.EXE 5.1.1144.0 or higher, although only for the ASHW32.EXE which is launched on the server side. It does not affect or depend on the telnet client version. |
<other switches> |
Any other switches or parameters which are not recognized by ATSD will be passed on to A-Shell. Typically, at the very least you would want to add the name of a startup command file so that your sessions started out at something other than a logged-out dot prompt. In the example above, we are specifying a CMD or DO file called START (which must reside in DSK0:[2,2]). |
<cmd> |
At the end of the command line, after all the switches, typically you would put the name of a startup command file for A-Shell to execute at the start of each new session, rather than starting out at the dot prompt. Note that since there is no initial authentication for these connections, you'll almost certainly want to launch new connections directly into your own application sign-on program. See Security / Login for more details. |
If you want ATSD to launch automatically when you log into the server, just drag its shortcut in the Startup folder for the desired user. But note that the problem with this is that you have to actually log in on the server console (as that user) before the startup folder is processed. If you want ATSD to start running as soon as the server is up, and for it to stay running regardless of login/logout activity on the server console, then install it as a service, as described in the next section.
