EPOC Release 5 OPL SDK Copyright (c) 1998-1999 Symbian Ltd PRODUCT INFORMATION The EPOC Release 5 OPL SDK provides a PC-hosted development environment for rapid application development in OPL. It comprises EPOC Release 5 system components, development tools including the EPOC emulator, system documentation and examples. OPL (Organiser Programming Language) is a Symbian proprietary language with a long heritage in Psion’s Organiser range. It provides a BASIC-like syntax, and its easy accessibility and shallow learning curve have spawned a vigorous development community. The EPOC OPL SDK enhances ease of OPL programming by providing PC-hosted development tools and documentation. OPL APIs provide access to the most commonly-used EPOC facilities. OPL extensions (OPXs) may be written, in C++, to provide access to other C++ APIs, or to provide optimised function implementations. To write OPXs, you need to the EPOC C++ SDK. To use an OPX written by someone else, you need a suitable build of that OPX (either for the emulator, or for a target machine). To see the full documentation, after the SDK in installed, see \sysdoc\oindex.html. SYSTEM REQUIREMENTS To install and run the EPOC Release 5 OPL SDK, you will need - a PC running Windows NT 4.0, Windows 95 or Windows 98 - 80MB of free space - speed and RAM requirements as for Microsoft Windows installation To install and run software on an EPOC device, you will need - an EPOC device using EPOC Release 1, 2 or 3, or later unless otherwise stated - EPOC Connect 2.1 or above, or badged version such as PsiWin, and link cable To browse the system documentation, you will need - a web browser which supports tables and frames, for the HTML version - a browser for HTML Help files, such as Microsoft Internet Explorer 4.0 or above, for the HTML Help version If you wish to develop OPXs, you will need the EPOC Release 5 C++ SDK (and its PC requirements). RELEASE NOTES Installation drive must be distinct from other EPOC SDK products This SDK uses the \epoc32\ root directory on a root directory of your PC. Other EPOC SDK products (with the exception of the EPOC Connectivity SDK) and the EPOC Emulator also this directory. This SDK will not successfully co-reside with such a product, on the same installation drive. If you have such a product, you must either delete it, or install this SDK onto another drive. If you choose to install this SDK onto another drive, you may need to create a logical drive. Two methods are suggested: - make a directory, eg c:\epoc32a\, and use the subst command to map this to (say) drive e: subst e: c:\epoc32a You may install this subst command in your autoexec.bat or some convenient command file that is executed prior to every EPOC32 development session. On Windows 95 and Windows NT, the subst command makes the mapped drive visible to all programs immediately. - a cleaner method for achieving this is to use shared drives. This method is available for Windows NT only. Create an \epoc32a\ directory as above. In Windows NT Explorer, right-click this directory, and select Sharing. Change from "not shared" to "shared as", and accept the defaults. Then, from Windows NT Explorer, select Tools | Map Network Drive, and connect to the drive you have just shared. Remember when sharing to set the permissions appropriately. Sharing your own drives works just as fast as substing. Having used either of these methods to create a new logical drive letter, run the SDK installation program and select the installation drive to the logical drive you have just created. Emulator under Windows 95 The EPOC emulator is primarily developed and supported under Windows NT 4.0. Known limitations of the Emulator under Windows 95 include - EPOC Spell does not exit cleanly - sometimes, after a combination of applications has been invoked, the Emulator does not exit cleanly - sometimes, when the Emulator is run in the Emulate EPOC Large mode, for example from the Start bar shortcut, the fascia bitmap is scrambled Windows 98 support Limited testing under Windows 98 indicates that Windows 98 issues are likely to be the same as those for Windows 95.