Previous Section
Previous Section: Status Bar
Document HomeDocument Home
Next Section: Program Differences
Next Section


Ozterm Differences

Wozterm may be run in either standard Wozterm mode or Ozterm 6 Compatibility Mode. Using Compatibility Mode enables users to run their existing Ozterm 6 script files in Wozterm. Due to differences between the two programs, there are some script commands in existing Ozterm 6 script files that may be affected. Described below are the main script command and program differences. To assist with migrating to Wozterm, the Ozterm Syntax Checker has been updated to include Ozterm/Wozterm compatibility warnings. Click on the link above to download the updated Ozterm Syntax Checker.

Script

Modes

 

Mode types are different between Ozterm and Wozterm which affects the @Mode and @Getmode script commands:

Current Ozterm Mode New Wozterm Mode
FD MANUAL, SDP and NEAS SDP
IOG11 AXE, NEAS AXE, NEAS AXE APN, NEM AXE, NEM AXE APN and NEM AXE MTP
SYS12 S12, NEAS S12 and NEM S12
S12FD S12 MONI, NEAS S12 MONI and NEM S12 MONI
AOM AOM and NEAS AOM
MNOSS OSS AXE
OMI DMS and NEAS DMS
No equivalent mode UNIX, DCAP AXE, NEAS and NEM
TW, IOIM, HD and BFD No equivalent mode

Wozterm automatically selects the correct Exchange mode type when connecting via NEM or NEAS after a successful connect message has been received. System 12 modes automatically switch to the appropriate S12 MONI mode when an MPTMON session is started, and return to the appropriate S12 mode when the MPTMON session is ended.




Window & Draw

 

The @window command has been enhanced to include an ON option, ie @window(ON), which will display the @Window tab in full screen mode within the Wozterm session. All @Draw commands are performed within this window so the user can adjust their script appropriately to display menus, etc.




Waitfor & Sendwaitfor

 

A new script command @Sendwaitfor has been created to cater for fast response times, eg dial-up modems, where the response to a @Send command may be returned before the corresponding @Waitfor has been run in the script file. This new script command is available in standard mode and Compatibility Mode and uses the following syntax:

@Sendwaitfor('Send string', Time out in seconds (0 for no time out), 'Reply string')




Trace

 

The @Trace script command and menu option used in Ozterm creates a log file detailing script file results, with @Trace(Log file) turning the feature on and @Trace turning the feature off. Wozterm automatically provides this feature using the Messages tab and associated Messages.log file, which contains a log of all Wozterm interactions for that session. The @Trace feature in Wozterm now dictates whether the user has the choice to single step through a script file or not. Enabling the Trace feature dramatically slows the script file run time and is only used for debugging purposes. Tracing can be enabled or disabled in the Preferences menu, or in a script file using @Trace(on) to enable and @Trace to disable.




Execute

 

As Wozterm runs in the 32-bit environment, some responses from @execute commands may be formatted differently. For example, in Ozterm the DOS "dir" command returns all text in upper case with shortened file names where appropriate. When the same function is performed in Wozterm, long file names are returned without forcing the names to upper case, eg C:\PROGRA~1 will now appear as C:\Program Files. This also means some file name characters are no longer allowed. For example, the ampersand character '&' is used in CMD.EXE to concatenate commands and is no longer allowed as a file name character.




Deprecated Commands

 

The following script commands and functions are not implemented in Wozterm. They will cause a script runtime error, halting the script file:

  • @Autodial
  • @Cat
  • @Dtrbreak
  • Filetrans
  • @Getport
  • @Getprint

The following script commands are irrelevant in Wozterm and will not be implemented. They are reported as a script warning in the Messages tab, allowing the script file to continue:

  • @Title
  • @Bmoddir
  • @Catfile
  • @Printer
  • @Selprint
  • @Portno
  • @Screentimeout



Operator Precedence

 

In Standard Wozterm mode, normal operator precedence applies, ie from highest to lowest * / + and -. To achieve Ozterm-like processing in Ozterm Compatibility Mode, precedence follows the order of operators from left to right. To ensure correct calculation results please use brackets to preserve the correct order. For example, in Wozterm mode 1 + 2 * 3 = 7, but in Compatibility Mode 1 + 2 * 3 = 9, which can be changed to 1 + (2 * 3) = 7 to get the correct result.



Previous Section
Previous Section: Status Bar
Document HomeDocument Home
Next Section: Program Differences
Next Section



This publication has been prepared and written by Telstra Corporation Limited (ACN 051 775 556), and is copyright. Other than for the purposes of and subject to the conditions prescribed under the Copyright Act, no part of it may in any form or by any means (electronic, mechanical, microcopying, photocopying, recording or otherwise) be reproduced, stored in a retrieval system or transmitted without prior written permission from the document controller. Product or company names are trademarks or registered trademarks of their respective holders.

Note for non-Telstra readers: The contents of this publication are subject to change without notice. All efforts have been made to ensure the accuracy of this publication. Notwithstanding, Telstra Corporation Limited does not assume responsibility for any errors nor for any consequences arising from any errors in this publication.