#aaplay & P9000
4 messages in this thread
Has anyone had a problem palying 640×480 256 flcs using AA's windows player
with an Orchid P9000 ????
My system keeps crashing out (paging error with P9000 _drv etc) although small
flcs work fine.
Any advice would be most welcome.
Clive Jackson.
None of us in Product Support have had the pleasure of the P9000, so others can
chime in here.
Do the instructions include any information about a memory region that is in
extended memory which the Viper uses? We got a caller who said that the
documentation indicated 80000000-9FFFFFFF was used by the Viper. If you can
confirm this, try excluding this memory region.
Other than that, make sure you have the latest Windows / Viper drivers.
Nik
Hi Nik, whats the syntax to exclude address segment? (presumably to be placed
in my config.sys)
Clive.
I was hoping you wouldn't ask that!
Generally, after EMM386 (or QEMM386, etc.) it's X=80000000-9FFFFFFF.
I can't say I've seen numbers that high though!
If you have problems that are only within Windows, there is an EMMEXCLUDE
statement in the [386Enh] section of the SYSTEM.INI file that you could use.
However, I haven't verified that the Viper talks about this memory range. If
it does, the manual may also explain how to deal with it.
Nik