S3 Nitro 3D Video Adapter Driver Causes Fatal Exception 0E During a Color Change - Search Again

 

SUMMARY

I've installed LapLink on a computer with a STB Nitro 3D video adapter and Windows 95 installed. I can make a LapLink connection and start a remote control session to this machine. When I try to remotely change the number of colors displayed, it causes a Fatal Exception 0E error.

 

SOLUTION

This relates to the video driver used for the STB Nitro 3D.

To verify the driver version, follow these steps:

  1. Right-click My Computer and click Properties.

  2. Click the Device Manager tab, and click the plus (+) sign next to Display Adapters.

  3. Click to highlight the STB Nitro 3D video adapter and click Properties.

  4. Click the Driver tab. Note the date of the video driver.

  5. Click the Driver File Details button. Note the file version number listed.

  6. If the date of the driver is June 23, 1997, or the file version is 1.52A, the driver needs to be changed


We have found that using the Windows 95 driver provided by S3, the manufacturer of the chip set used in this adapter, provides a solution. The driver can be downloaded from the S3 web site at http://www.diamondmm.com. When at the web site, search for the S3 Virge/DX (375) drivers, and download the file named W9531201.zip.

Once downloaded, use a file extraction utility (such as WinZip) to extract the files, and follow the enclosed instructions to install the video driver. Reboot your computer to allow the new video drivers to take effect, then restart LapLink to have it recognize the new video settings.

 

 Related Articles

  Remote Control Guest Computer Freezes or has an Error
  Changing Windows Video Settings
  Error message: Unable to Load Device Driver: \SystemRoot\System32\Drivers\TSISTRM.SYS after Installing LapLink
  How Do I Discover What Type of Video Display Adapter I Have and Update the Drivers?
  How do I Locate Information About My Video BIOS?
  Installing LapLink on Computers Used to Connect to Main Frame Computers

 

Last updated: Tuesday, May 22, 2001

Article #26

Legacy Article #2006