home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Der Mediaplex Sampler - Die 6 von Plex
/
6_v_plex.zip
/
6_v_plex
/
DISK1
/
GAMES_27
/
REBCODES.ZIP
/
REBEL.TXT
< prev
Wrap
Text File
|
1993-11-27
|
6KB
|
132 lines
Rebel Assault Technical Notes
LucasArts Entertainment
11/23/93
Troubleshooting Quick Checklist:
[ ] Runs OK with no sound ?........DMA or IRQ conflict
[ ] Runs OK with no mouse ?........IRQ conflict
[ ] Runs slowly ?................Disable Mem Manager!
[ ] Sound buffer size below 700000....Disable Mem Manager!
[ ] Pro Audio Spectrum echoes.....Set PAS DMA to an alternate
channel
---DMA / IRQ CONFLICTS---
The majority of problems running Rebel Assault come from DMA or
IRQ conflicts with a sound card or mouse driver. Rebel Assault
pushes the hardware much harder than many games, so some conflicts
may interfere with Rebel Assault even when they go undetected with
other games.
---SOUNDBLASTER 16---
Rebel Assault runs 16-bit sound cards like the Sound Blaster in
16-bit native mode. When doing so, it defaults to using a 16-bit
DMA channel. You must set Rebel Assault the correct 16-bit DMA
value (Not the 8-bit DMA channel), or you will not get any sound.
---PRO AUDIO SPECTRUM---
Rebel Assault runs the PAS in native mode. When configuring this
sound card,make sure that its native-mode DMA channel is not the
same as the DMA channel used for Sound Blaster emulation (which is
usually set at one). Otherwise, your sound will echo, play double
speed or get normally undesirable results.
---MEMORY---
In most cases, you should not run with a memory manager. If
you do, the game will likely slow down. Additionally, memory
managers take memory and allocate it for use as EMS memory. Rebel
Assault runs in 386 protect mode and does not use EMS. It is also
not sensitive to the amount of free DOS memory (<640k). Thus,
running a memory manager may also take memory away and not allow
Rebel Assault to run with the 4 megs it needs.
A clue that you may not have enough free memory can be found on
the calibration screen of Rebel Assault, which appears after you
launch the game.
Your sound buffer size should be 700000 (what you normally set in
the launcher). If it isn't, then Rebel Assault was not able to
allocate all of its sound buffers due to insufficient memory.
---UNEXPECTED INTERRUPTS---
We are currently trying to correlate this error with certain
hardware configurations. DOS4GW, the DOS extender Rebel Assault
uses may have a confliction with certain hardware/software setups.
If this is occuring, check to see if you run any other programs in
'Protected' mode.
Some suggestions to help work around this error are as follows:
1) Run the ASSAULT.EXE program from the "DOS Prompt" from within
Windows
2) Run the "REB.BAT" file from the C:\>REBEL\ directory.
3) Contact Product Support at (415)721-3333 8:30 am - 6:00 PM,
Mon-Fri. PST
4) Fax your system specs (i.e. processor, speed etc..), name and
address to us at (415)721-3482. We will contact you via mail if
any patches are created.
*****Advanced Technical Notes*****
Below are some techie notes regarding the 'Advanced Configuration'
screen in Rebel Assault. If all else fails, try the recommended
tips below.
---MULTITASKING TIMER---
To achieve smooth animation limitations in the MPC spec, Rebel
Assault runs the bulk of its code out of interrupt, dividing time
between the rendering and game code and the CD file code, which
runs out of the mainline.
CPU processing is time-sliced between the two processes using
the multitasking timer, which runs at 300Hz. Typically, one timer
interval is given to the CD code for every four given to the game
code (this means 20% cpu usage). This means that the CD driver code
is given 3.3 ms CPU time every 16.7 ms.
Unfortunately, some CD drivers do not take kindly to this kind
of interruption, possibly because they rely on being able to simply
poll the CD hardware for incoming blocks. When interrupt code is
running, they may miss incoming blocks and read bad data. Some
drivers not only bad data but returns it to you as if it were good.
Fortunately, Rebel Assault has its own checksums to catch any
bad data. If a bad checksum is found, Rebel Assault will ask the CD
to re-read the block. Still, it is important to minimize re-reads
as they may cause the game to periodically halt as the game engine
waits for the correct data. If any re-reads have occurred during
your game session, the message "CD CHECKSUM ERROR"
will be printed when you exit the game.
In some cases, game performance can be improved by modifying the
multitasking timer. By increasing the timer rate, you will
decrease the amount of time the CD driver code will be interrupted
and thereby lowering the chance of the CD driver missing an
incoming block of data. This does not come however, without
a price. The game code runs in 386 protect mode. The CD code runs
in real mode. The DOS extender can only switch back and forth
between the two modes so fast. Turn the multitasking timer too high
and the game will lock up. Both increasing or decreasing the the
timer rate may help Rebel Assault, depending on your hardware and
drivers. 300Hz is the default setting for this.
If you have any other problems, please feel free to leave me a
message in the LucasArts Forum. You can also reach Product Support
at (415)721-3333 8:30-6:00 Mon-Fri PST.
Thanks for your interest in LucasArts Entertainment.
--Jason / LucasArts