Oberon for Windows V4.0-1.0 (c) 1993 by ETH Zurich INTRODUCTION Oberon for Windows is an implementation of Oberon for Microsoft Windows NT and Microsoft Windows 3.1. This is release 1.0 of the ETH Oberon System Version 4.0. Oberon Version 4.0 is a new release that replaces Version 2.2. The main difference between V2.2 and V4.0 is the replacement of TextFrames by WriteFrames and Edit by Write. A more precise des- cription of the differences between V2.2 and V4.0 can be found in the text "OberonV4.Text". When running under Microsoft Windows 3.1, the operating system extension Win32s is required. If Win32s Version 1.1 is not available, it can be downloaded in a compressed form from neptune.inf.ethz.ch (129.132.101.33), directory ~ftp/Oberon/Windows. Microsofts Win32s is an operating system extension to Windows 3.1 that allows Windows 3.1 to run programs written for Windows NT. It basically translates 32-bit calls to the Windows NT API into calls to the 16-bit Windows 3.1 API. SYSTEM REQUIREMENTS Hardware: - An IBM Computer or Compatible running Microsoft Windows NT or Microsoft Windows 3.1 in enhanced mode. - A 386, 486 or Pentium processor. - 4MB of extended memory (absolute minimum). - 5 MB of hard disk space. - preferably a screen with resolution of 1024 by 768 pixels (although smaller size screens will work, too). - preferably a three button mouse (and a mouse driver that supports all three mouse buttons). Software: - Microsoft Windows NT or Microsoft Windows 3.1 - If running under Microsoft Windows 3.1, the operating system extension Win32s is required. CONTENTS This disk contains the following files: README.TXT this file SYSTEM.EXE compressed, self-extracting archive containing the Oberon System for both, Windows 3.1 and Windows NT INSTALLATION 1. If you intend to run Oberon under Windows 3.1, install Win32s first (see instructions below). 2. Create a new directory, e.g. C:\OBERON. This newly created directory will be called "Oberon directory" for the rest of this document. 3. Copy the file SYSTEM.EXE to the Oberon directory. 4. Run SYSTEM.EXE. The Oberon files will be extracted and uncompressed. 5. In order to work properly, the Oberon directory must be defined in an environment variable "OBERONDIRS". If your Oberon directory is C:\OBERON, you should define SET OBERONDIRS=C:\OBERON;C:\OBERON\FONTS You should include this line in your AUTOEXEC.BAT file when you run Windows 3.1. If you run Windows NT, the environment variable can be set using the System option in the Control Panel. 6. If you use SHARE, set the command line parameters to the following values: SHARE /F:16348 /L:255 (SAHRE is normally called from the AUTOEXEC.BAT file.) If any troubles occur with share, increase the value of the /F option. If this does not help, remove SHARE from AUTOEXEC.BAT. 7. Reboot the machine. INSTALLATION OF WIN32S (Win32s is only needed when you intend to run Oberon under Windows 3.1) If you do not have Win32s Version 1.1 or a newer version, you need to install it. 1. Start Windows. 2. In the File Manager Window, display the files on the Win32s floppy, then double-click on SETUP.EXE to run the Setup program. 3. Follow the setup instructions to complete the installation. 4. Verifying Win32s installation: In addition to installing the Win32s system components, the Win32s Setup program optionally installs the Win32 card game FreeCell, the same program that ships as part of Windows NT. After installing Win32s, you can run FreeCell to verify that Win32s installed correctly. FreeCell is located in the Program Manager group "Win32 Applications", which the Win32s Setup program creates. STARTING OBERON a) Windows NT On the command line, type OBERON. The command line options are: OBERON [-h ] for further command line options, see UserGuide.Text. b) Windows 3.1 Under Windows 3.1, the Oberon application must be started from the Program Manager. Create a new Program Item in a Program Group. The default value for the heap size is 4MB. Change this value to 2MB if your system has 4MB only. The minium heap size is 2MB. If the heap size is too big, system startup under Windows 3.1 may take a while because Windows tries to move other memory blocks in order to free a contiguous area of memory. If your system has 4MB only and in your autoexec.bat file some programs are moved to the "high memory area" using the LH command, Oberon might not be able to start up with a heap of 2MB. In this case, remove the LH commands from your autoexec.bat. When started the first time, Oberon builds up an image of the directory structure of all directories indicated in the environment variable OBERONDIRS. This may take some time. QUITTING OBERON Oberon can be quit by either choosing "Close" in the windows system menu, by pressing ALT+F4, or by executing the command "System.Quit." SUPPORT FOR TWO-BUTTON MOUSE Oberon makes use of all three mouse buttons. On systems with a two- button mouse, the middle mouse button is emulated by the control key on the keyboard. Pressing the control key is equivalent to pressing the middle mouse button. ONLINE DOCUMENTATION There is more documentation about this release of Oberon for Windows in the text UserGuide.Text. The differences between Oberon V2.2 and V4.0 are described in the text OberonV4.Text. CONSOLE OUTPUT Oberon writes critical error messages to a console window. Under Windows 3.1, a GUI application cannot write to a console. Oberon then writes the console output to a file instead. The name of the file is "c:\debug.log". It may be convenient to create a program icon that starts the notepad utility and displays the log file. Oberon and Oberon for Windows are trademarks of Eidgenoessische Technische Hochschule, Zurich Microsoft, MS and MS-DOS are registered trademarks of Microsoft Corporation. NT, Win32, Win32s, Windows and Windows NT are trademarks of Microsoft Corporation. IBM is a registered trademark of International Business Machines Corporation. Intel is a registered trademark, i486 and Pentium are trademarks of Intel Corporation.