TROUBLESHOOTING

The following tips may help you solve any problems you encounter with AXS.

  • The program asks for a VESA 2.0 video card.
      AXS requires a videosystem which is VESA 2.0 compatible and can offer a 'Linear Frame Buffer'. If your card does not have native 2.0 support, loading a VESA 2.0 software driver may do the trick. (ie. SciTech's Display Doctor)
  • The program inits OK, but when I press any key, the screen messes up.
      AXS has support for VESA 2.0 videocards, but also contains native support for videocards with an S3 chipset. As these are pretty common it means a lot of people will not have to load a VESA 2.0 driver, even if there videocard is not VESA 2.0 compatible. The drawback of this is that some cards are incorrectly seen as having an S3 chipset. The solution to this is to load a VESA 2.0 driver anyway. AXS will first look for VESA 2.0 support, then for an S3 chipset.
  • The program runs OK, but there are some weird blinking pixels on the screen.
      If your BIOS has an option for VGA Frame buffer (usually combined with a frame buffer size selection), disable this option.
  • The program inits OK, but there is no sound and the GUI responds very slowly.
      This is caused by an IRQ conflict (the IRQs should occur, but are blocked somehow). Make sure your SB is correctly set up. If you are running from Windows 95 you may have to adjust the PnP settings in your BIOS. So if your SB is set at IRQ10, make sure in your BIOS, IRQ10 is set to legacy ISA and not to PnP.
      (P.S. To exit AXS press and hold ALT-X. It may take a few seconds, but you will be able to exit the program normally.)
  • There is no SB MIDI when running from Windows 95.
      Somehow the SB drivers for Windows 95 seem to hold back the MIDI section of the SB when running DOS applications. We have found that by disabling and re-enabling the 'Creative Sound Blaster 16 Plug and Play' driver (in Control Panel -> System) the MIDI will function in AXS.
  • The COM-port MIDI inits ok, but does not receive any data.
      This is caused by an IRQ-problem. The one time we encountered this problem was when our PnP/PCI BIOS settings were not set correctly. The IRQ used by the COM ports (IRQ3 and IRQ4) were assigned to 'PnP' instead of 'Legacy ISA/EISA'. Setting IRQ3 and IRQ4 to 'Legacy...' fixed the problem.