Welcome

VINCEd Editor

The Time editor lets you set the date and time on your system. Figure X-X illustrates the Time Preferences editor window.

Figure X-X. VINCEd Preferences Editor Window

To set the date:

Click the cycle gadget in the upper right corner until the correct month is displayed.
Select the year text gadget, delete the incorrect year, and enter the correct year.
select the correct day from the calendar display. The day is highlighted when selected.

To set the time:

Point to the slider bar in either the Minutes or Hours slider.
Drag the bar to the right to increase the value and to the left to decrease the value. When the correct value is shown, release the selection button. Repeat these steps for the other slider.

WarpOS Editor

The WarpOS Editor stores its options in sys:prefs/env-archive/powerpc. The following options are currently supported: Figure X-X illustrates the Time Preferences editor window.

Figure X-X. WarpOS Preferences Editor Window

General

Memory Protection	Activating this option causes the memory-protection facilities of WarpOS to be switched on. If low-memory situations occur it can help to deslect this and turn off memory protection.
No PPC	This must be selected, if the powerpc.library V8+ is installed on a Non-PPC system. Afterwards all demos which also run without PPC (but which try to open the powerpc.library) should run. If this is not selected, then the library will crash at initialization.
Early Term	If this is not activated, then problems can occur in conjunction with programs like WShell. In this case this should be selected. Afterwards, the tools "stackppc" and "changemmu" can NOT be used anymore. The PPC stack can be set using the stack command (the PPC stack gets about double the size of the 68K stack of the shell).

env:powerpc/Terminator This variable represents the terminator mechanism, which is needed to start up WarpOS on systems where the ppc.library can't be deactivated. This variable should always be set to 2. env:powerpc/HideWarning If this variable is set to 1, the appearance of the requesters, which come up in conjunction with ppc.library Warning, is avoided. env:powerpc/nopatch If this variable is set to 1, WarpOS doesn't attempt to patch all ppc.library functions and redirect them to dummy functions, if the terminator 2 is activated. This variable should never be touched unless explicitely noted. This variable was added to make it possible to create PowerUp emulations, which should allow to run PowerUp software under WarpOS. env:powerpc/force If this variable is set to 1, the address specified using the env variable 'powerpc/gfxaddr' is definitely added to the system using a BAT register, even if no corresponding address space was found in the system structures. This variable has to be set if CyberVisionPPC resp. BVisionPPC graphics hardware is used. env:powerpc/gfxaddr Requires a hexadecimal address (either with or without prefixed $). If the powerpc.library isn't able to find the graphics-RAM, it takes the value from this environment variable. If an expansion address space is found which contains this address, the address space is put into a BAT register, if possible, to gain a higher access speed. The variable also can be set to 0, if no problems with the graphics RAM occur. IMPORTANT: Owners of CyberVisionPPC resp. BVisionPPC graphics boards have to set this variable to $e0000000. Additionally the variable 'powerpc/force' must be set to 1. env:powerpc/debug May contain a number between 0 and 3. This specifies the debugging-level to use when WarpOS boots. Should *ALWAYS* be left at 0 unless you are interested in what happens during the booting process. The debugging-level can be changed during operation by using the 'setdb' tool. env:powerpc/seginfo This variable requires a numeric value. If this value is not zero, then segment information is printed out if crashes occur (hunk/offset pairs). The value of the variable defines the max. number of lines to be printed out. Usually the variable should be set either to zero or to some value like 100. This feature only works, if 'SegTracker' and 'Sushi' are installed. env:powerpc/crashfile Demands a filename/path. If a PPC-crash occurs, WarpOS writes all crash data to this file. The file may also be a CON-Window in order to display the data in a window. If the file string is preceded by a semicolon no output is made. This is useful for people running programs such as 'sushi' which also display the crash data. This way you can keep the data from appearing twice. env:powerpc/alertfile Works in the same way as the 'crashfile' variable only that this file is used for system-messages (e.g. corrupt semaphores).