|
|||||||||||
Download by anonymous FTP
from: ftp://ftp.inf.ethz.ch/pub/ETHOberon/
Your text may include any blending of:
Alternatively, consult the HTML documents on this site - http://www.oberon.ethz.ch. Ben Smith-Mannschott wrote a summary of the Oberon evening that took place in Zürich on May 7, 1999. The page also has links to some pictures and screen snapshots of the demos.
[ Native | Windows | Linux | MacOberon ] Note: These installation sections act as breaking news for the current public release 2.3.4. The follow-up release will be accompanied by a new install.txt incorporating most of the information which arouse from user questions. Questions related to problems will be moved to a special section, if the problem solutions have been integrated in a new release.
Device Id Num Part Size System
Type
/dev/
hda1 6 0 6 400 MB C:DOS FAT16 - DOS 6.21
hda2 6 1 6 2.040 MB E:DOS FAT16 - Win NT & Oberon for Windows
hda3 4f 2 79 196 MB Native Oberon or QNX Posix
hda4 5 3 5 Extended
hda5 50 4 80 196 MB | Native Oberon (alt) or Lynx RTOS / DM
hda6 83 5 131 1,004 MB | Linux fs - SuSE 6.1 & Linux-based Oberon
hda7 82 6 130 119 MB | Linux swap
hda8 6 7 6 1,004 MB | D:DOS FAT16 - Native Oberon in a file
In all, four Native Oberon and one Oberon for Windows.
The Win NT Bootmanager is used and is defined as:
DOS booting is controlled by a boot menu:
and Linux booting is controlled by LILO with a menu defined as:
Linux Native Oberon is also installed and working under X11. The other two Stand-Alone Oberon
systems can also be started under X11.
All these systems, except Linux Oberon, can be started with boot diskettes.
Useful hint: In order to access directly and unmistakably the source module text of a module, without prior knowledge
of the correct prefix, execute the Oberon command:
Miscellaneous.ShowMod [ moduleName | ^ ]
The various implementations also show differences in their release levels since the concurrent maintenance of that many ports consumes a manpower which exceeds the manpower available in the group. Some ports are necessarily lagging behind. Presently, Native Oberon (all variants) and Oberon for Windows are in unison.
Installation instructions are found in:
Known problems
Temporary fix: change the drive letter in native.par with an editor. The next release will be corrected.
A2: Yes, when the system is installed in a logical
partition, this symptom may appear. If the TRAP information is obtained
for that case, it will show TRAP=15 and the line above says: Error:
~16-bit FAT. The next release will be corrected.
No such problem exists when the system is installed in a primary
partition. The partition should however be at least 16 MB large.
Smaller partitions/logical drives are formatted with 12-bit FAT, which
is currently not supported by the module Disk.
A2: To get the fuzzy copy command out of the way, a combined dosbased.zip is now uploaded to ftp.inf.ethz.ch. The subdirectories ETHOberon/Native/DosBased/Full/ and ETHOberon/Native/Update/v236/DosBased/Full/ each contain such a combined dosbased.zip.
BIOS
However, some cards only support Vesa 2.0 for a few modes, e.g. the Diamond FireGL only has Vesa 2.0 support for 640x480 modes! Run the vesainfo.exe utility available from ftp://ftp.inf.ethz.ch/pub/Oberon/ETHOberon/Contrib/Native/ under DOS (without loading any TSRs or drivers) to see which modes your Vesa 2.0 bios supports. As an example, running this utility against the Intel 740 AGP video card shows that the card supports all these VESA 2.0 modes:
VESA 2.0 8192kb Intel740 Super VGA
100 C000:3165 A000 RW 64K 64K E7000000 640x400x8 101 C000:3165 A000 RW 64K 64K E7000000 640x480x8 103 C000:3165 A000 RW 64K 64K E7000000 800x600x8 105 C000:3165 A000 RW 64K 64K E7000000 1024x768x8 107 C000:3165 A000 RW 64K 64K E7000000 1280x1024x8 11C C000:3165 A000 RW 64K 64K E7000000 1600x1200x8 11D C000:3165 A000 RW 64K 64K E7000000 320x200x8 11E C000:3165 A000 RW 64K 64K E7000000 320x240x8 121 C000:3165 A000 RW 64K 64K E7000000 400x300x8 124 C000:3165 A000 RW 64K 64K E7000000 512x384x8 136 C000:3165 A000 RW 64K 64K E7000000 1152x864x8
rem The display refresh rate can be adjusted now before starting Oberon rem The DOS command is usually provided by the video card manufacturer rem s3refrsh applies to the S3 Trio64V+ chip set rem The x and y values are obtained by executing: s3refrsh /? c:\dos\s3refrsh x y >nul cd native oberon
oberon.bat would start Native Oberon with:
noboot native.bin oberon.par
Hard disk / controller
TRAP 17 Disk error
ATADisk.Report PC=9213
err=9
Partition.Show reports
Disk 0 956 Mb Num Disk Mb Typ Description 0 0 956 6 C:DOS FAT16 >= 32M
and System.OpenKernelLog produces the following Kernel.Log information (extract):
ETH Oberon System 3 / PC Native 2.3.6 (13 May 1999) ... Disk0: IDE1.0, 957Mb, 1945*16*63, removable, SyQuest SparQ, ver 4.23 Disk1: IDE1.1, 0Mb, 0*0*0, Disk2: IDE0.0, packet, removable, ASUS CD-S340
Native Oberon can be installed on the removable disk. Communication
More generally, if you have a 3Com card and you don't know exactly which one, run 3LINK-ID.EXE.
TRAP 99 HALT statement
PPPMain.SendPacket PC = 808
How do I get around this problem?
A: Check that NetSystem.Route0.Mode = "" in Oberon.Text
Citing him: Using an ISDN adapter with a serial interface like a modem is just like using a modem. However you must pay attention to the CHAP and PAP way of identifying yourself. I use PAP, and this means that I must fill in the PAPname and PAPPassword strings in Oberon.Text. The relevant part of my Oberon.Text is:
DIAL = {
Host = { "<slipserver>" } {* SLIP only *}
Init = { COM2 57600 } {* modem port and speed *}
PAPName = { "provo005@tref.nl" } {* if using PAP only *}
PAPPassword = { "............" } {* if using PAP only *}
Dial = {
"ATZ"
10 "OK"
"ATD 2301333"
60 "CONNECT"
CALL PPPMain.StartInst
}
Notice that immediately following the "CONNECT" PPPMain.Startinst is called.
End of citation
Watch out of cards that require special Windows drivers to function, they will not work with Native. Perhaps Edgar Schwarz knows more about this.
Installation and usage information are found in OType.Text -> access Contributions - ftp://ftp.inf.ethz.ch/pub/Oberon/ETHOberon/Contrib/
The trace output of the Oberon test PC will be sent over the serial cable for display on the other PC's terminal program.
Another variant may be used if you have access to a network PS printer. You may then choose to install the LPRPrinter, which is found among the applications (LPRPrinter.Arc).
WinPrinter prints Oberon fonts as bitmaps (for each character). Thus, the resulting page can get very complex. Most cheap printers do not have enough printer memory to print complex pages with this printer driver. In that case, the output will get messed up. To print with 300 DPI resolution at least 1 MB of printer memory is needed, to print with 600 DPI resolution at least 4 MB are needed. WinPrinter has proven to work with the following printers:
A2: The Oberon startscript contains an error.
Replace the line: xset fp+ /usr/local/X11/lib/fonts/OberonXFonts
by: xset fp+ ${ohome}/XFonts
Information supplied by Guenter Feldmann
F := Files.New("ABC");
Files.Register(F);
Files.Old("abc"); --> trap
For temporary files, always prepend "Temp", so you can easily delete them.
For retrieving a file by theme/subject, use the following methods, in order:
Seeing a list of files, N days old, would help to find a file quickly. This is not possible at present but someone could take ftp://ftp.inf.ethz.ch/pub/Oberon/ETHOberon/Contrib/Native/TestDir.Mod and make such a tool out of it.
Here is another "Clean up" recipe brought forward by Peter Easthope:
After installing the system do: System.Directory ^ ... *\d .This gives a complete list of files. Store it in a file named Directory.
When you want to tidy the file system do: System.Directory ^ ... *\d again and store it in Directory.new. Do Diff.Do Directory Directory.new . The new files appear in the right viewer of the comparator in blue and are easy to find. Step through the viewers and copy the file names you wish to delete into the argument of System.DeleteFiles ~ . Once the argument is assembled, execute System.DeleteFiles.
Some will object that they did not do "System.Directory ^ ... *\d" after system installation and hence can not use this technique. Oberon occupies so little space that two or more partitions can be allocated for it at very little cost. In about 30 minutes the system can be installed in a spare partition and the directory listing can be obtained.
A2: To ascertain that a task runs correctly:
A3: To ascertain that a selection is correctly handled (the Display.SelectMsg or the Oberon.SelectMsg are involved):
For an example of the use of modular arithmetic comparisons on signed numbers, see "TCP/IP Illustrated, Vol. 2: The Implementation" by Wright and Stevens, pp. 810-812.
Make sure no other selection exists, otherwise it will be copied instead.
Note: Currently this works only with the TextGadgets editor, but in the next release it will also work with TextFrames and ScriptFrames (editors Edit, Script, ET).
System = {
..
InitCommands = {
{ System.Open System.Tool }
{ Configuration.Marker set system}
{ System.Grow }
{ System.OpenLog }
}
..
}
With Oberon for Windows, edit Configuration.Text as follows:
.. Configuration.Marker set system System.Grow System.OpenLog ..
This will start Oberon in single-track, but this setting can be left at any time with System.Close,
and resumed with System.Grow.
As an Oberon user, you can view the source of a message (use the [Source] Button in the menu bar). The line after "--- start of oberon mail ---" marks the beginning of the mail with encoded Oberon objects, perceived as junk. You can also view it by selecting this beginning and executing AsciiCoder.DecodeText % @
Note that the current file size limit of Native Oberon is about 12Mb, so it is a good idea to periodically collect your mail, not using Mail.Collect, but rather starting "afresh" with an empty "MailMessages" file.
In the basic Native Oberon system one can use Script. Open its documentation with Script.Open ScriptGuide.Text. In the Windows, Linux and Macintosh implementations, Script is an application which must be installed (Script.Arc).
If Gadgets is installed on top of the basic system, you can compose TextDocs documents. See TextDocs.Tool and EditTools.Tool. Open a document with Desktops.OpenDoc <name>.
Script and the editor of TextDocs documents are formatting document editors that allows arbitrary objects like graphics or pictures to flow within the text stream. Mouse events are forwarded to objects when the mouse cursor resides within their screen area, so the object's content can be manipulated and edited in-place. TextStyle gadgets control the look of the text following their occurrence. TextStyle attributes cover formatting modes, widths of the left and right margins, tabulator stops, line spacing and page break at the style location. When made visible, a TextStyle displays as a "ruler" at the style location showing its current state. The most important style attributes can be set directly at the ruler with mouse commands.
The text editor TGX, an extension of ET, is offered as a contribution by Christian Hoffmann - christian.hoffmann@wsl.ch.
Other Oberon systems have their own brand editor(s) / word processor(s).
A2: The module HTML.Mod can be used to convert an Oberon text to HTML. The text must be composed according to a small number of rules enabling the compiler to recognize headings, normal text, italic text, preformatted text, lists and horizontal rulers. Though very rudimentary, it covers basic needs. The HTML document you are reading now has been prepared with that tool.
MODULE My;
IMPORT Fonts;
PROCEDURE DefaultFont*;
BEGIN
Fonts.Default := Fonts.This("Oberon12.Scn.Fnt")
END DefaultFont;
END My.
This will only affect new texts that you create. Existing texts have their font stored with them.
A2: Select the most suitable command among those offered in the EditTools module: EditTools.IncSize, EditTools.ChangeSize, etc. (open EditTools.Tools to be informed). These command operate on the selected text. To make a large selection, Copy the viewer, select the top in the top viewer, and select the bottom in the bottom viewer while holding down the SHIFT key.
To transfer a whole directory structure, build a "command script" using Unix.
In Linux:
find /some/dir -type f > Temp.Script # list all files into Temp.Script vi Temp.Script # edit script :%s/$/" => / # append " => to every line :%s/^/"/ # prepend " to every line Go~<ESC> # append ~ at end of file :1 # go to first line ODOS.Copy<ESC> # prepend DOS.Copy command ZZ # save and exit
In Oberon:
DOS.Copy "/some/dir/Temp.Script" => Temp.Script ~ Desktops.OpenDoc Temp.Script
and add the Oberon file name at the end of every line. Execute the command and voilà!
More generally, to be informed on Oberon-based programming environments related to Oberon, consult Guy Laden's Oberon System Implementation List - http://www.math.tau.ac.il/~guy/Oberon/systems.html and the associated Oberon Compiler List - http://www.math.tau.ac.il/~guy/Oberon/compilers.html
A2: Parallel port: Use the facilities provided in the Centronics module of PC Native Oberon.
It is limited to output only, i.e. a bi-directional protocol is not supported. This subject is treated more generally in Parallel Port Central -
http://www.lvr.com/parport.htm.
A3: Sound card: Get some inspiration by looking at the source text in the Sound module of PC Native Oberon or in Win.Audio.Arc for the ETH Oberon System for Windows. These support the Soundblaster compatible cards. Watch this: some of the modules used in the Windows implementation are not portable (compile with option \N).
Pros
Contras
Citation: "Being able to cross-compile from ETH Oberon System to Win32 means that we are totally independent of Microsoft for our production of software. Even if the target is Windows, there's a world of difference between getting a system working for a user, and getting it working smoothly as a development machine - now we don't have to!" - Paul Reed, Managing Director, Padded Cell Software Ltd
The source code is copyright-protected as specified by the license terms in ftp://ftp.inf.ethz.ch/pub/Oberon/ETHOberon/license.txt. An excerpt of the license text appears as comment at the beginning of each source module text as a reminder.
Oberon system = V1 ( V2 V4 | ETH Oberon ).
The main difference between V1 and V2 is the introduction of an extensible text model and the text editor Write.
The main difference betwen V2 and V4 is the unification of the two text editors Edit and Write. In order to avoid confusion with ETH Oberon (which was then called "System 3"), the direct successor of V2 was named V4.
The main difference between V2 and ETH Oberon System is that the ETH Oberon, which emerged approximately one year later, introduced a more general object model, not restricted to text elements, and the notion of persistent object libraries.
Citation of Josef Templ - approx. 1994
At present, the Oberon System V4 is maintained by the System Software Group of the University of Linz which has developed it considerably.
In the mean time, several other Oberon systems have appeared.
9 Dec 2002 - Copyright © 2002 ETH Zürich. All rights reserved.
E-Mail: oberon at inf.ethz.ch
Homepage: www.oberon.ethz.ch/
Wichtiger Hinweis:
Diese Website wird in älteren Versionen von Netscape ohne
graphische Elemente dargestellt. Die Funktionalität der
Website ist aber trotzdem gewährleistet. Wenn Sie diese
Website regelmässig benutzen, empfehlen wir Ihnen, auf
Ihrem Computer einen aktuellen Browser zu installieren. Weitere
Informationen finden Sie auf
folgender
Seite.
Important Note:
The content in this site is accessible to any browser or
Internet device, however, some graphics will display correctly
only in the newer versions of Netscape. To get the most out of
our site we suggest you upgrade to a newer browser.
More
information