2.1. Rebel 10 won't run after Installation
A few users (< 1%) reported problems running Rebel 10 after installation.
After installation they get the following error message in starting Rebel 10:
"Program aborted. Install again ..."
This is due to a necessary file, that has not been copied correctly at the installation. Schröder BV offers the program FIX.EXE for this users.
How to run FIX.EXE
- Be sure to have your original REBEL 10.0 CD-Rom in your CD-Drive
- It's doesn't matter if you run FIX.EXE from your harddisk
or from your floppy disk
- Run FIX.EXE and type the letter of your CD-drive when
you're asked to
- Now go to your REBEL 10.0 directory or click on the REBEL
icon and run REBEL!
Download FIX10.ZIP (zipped version of FIX.EXE):
2.2. Running Rebel in a Win32 Environment
In a Win32 environment (Win95, Win98) we recommend to use one of the Rebel windows shortcuts, which will optionally be created during the Rebel 10 installation.
We don't recommend to switch tasks while running Rebel 10.0.
Nevertheless this should be possible. Some users report, that task switching (using ALT + TAB) don't work with Rebel 10 under Win98. If you run in this problem, try to use the
"no VESA" Rebel icon.
2.3. How to create a Rebel Windows Shortcut
If you haven't created the optional Rebel windows icons during the Rebel installation, you can manually start the program REBGROUP.EXE from the Rebel 10 Cdrom. This program will create two Windows shortcuts, which are adapted to your actual system configuration.
REBGROUP.EXE won't run under Windows 3.x, because it is a Win32 program.
2.4. Display Problems
There are known problems with Matrox and Cirrus Logic (CL-GD5434) graphical adapters. Both cards doesn't support a font of Rebel, therefore the Rebel menu isn't displayed correct.
The menu is okay from next start on.
- press "F6" (CFG menu)
- press "ARROW UP" 6 times
- press "ENTER"
- press "ALT+X" (exit program) plus save changes
There are reported problems with a flickering display, running Rebel in
DOS mode, using a Matrox Millenium card. In this case you should download the Vbe utility from the Matrox WWW site.
Some (older) graphical adaptors are not fully VESA compatible. You can bypass Rebel's VESA mode by running Rebel with the "V" option.
Example: REBEL.EXE V
Best is, to use the "no VESA" Rebel icon.
2.5. Mouse Problems
If you can't use the mouse with Rebel, you must distinguish two cases:
No mouse driver loaded
You must add the mouse driver loading to your AUTOEXEC.BAT file.
Mouse support switched off in Rebel
Press F6 (menu CFG), position with the cursor key "ARROW DOWN" to the menu entry "Mouse" and press ENTER. Than position with the cursor key "ARROW DOWN" to the menu entry "Save configuration" and press ENTER again. After pressing ESC, the drop down menu vanishes.
"Illegal Operation" Error
On some machines you get an "Illegal Operation" error in running Rebel 10.0 on Win 3.1 or Win95. This error might be related to the mouse driver in use. As a workaround try one of the following points:
- use START.BAT to run Rebel
- disable the mouse in the menu CFG
- select another mouse driver (probably best hint)
- Win95 only: boot your machine in DOS mode
See the Rebel 10.0 README file for further details.
2.6. Memory Problems
64 MB Problem
On some PCs with 64 MB (or more) of memory, Rebel may report "Insufficient memory". The reason is unknown. The problem seems to be HIMEM.SYS related. You can try the following as a workaround:
Running DOS 6.x
Remove HIMEM.SYS from your CONFIG.SYS.
Running Windows 95
- Run Rebel 10.0 by using the shortcuts, created during the Rebel installation.
- Don't run Rebel 10.0 from the Win95 MSDOS prompt, because this seems to be the problem maker (reason unknown). There seems to be a different HIMEM.SYS behavior under Win95 than under the Win95 MSDOS prompt while having a 64 Mb Pc.
- However if you insist playing on MSDOS the only solution to bypass this 64 Mb problem is to follow the exact rules as pointed out in the "Windows 95 (F8 trick)" in the Rebel 10.0 README file.