TV300

Q. TV300 in a 486-66Mhz machine, 16Mb of RAM. Executing the TV300 
program, "TV300 caused a General Protection Fault in module CXITL.DRV at 
0001:D383."  
A. Start windows like this:   WIN /D:FSVXC

Q. TV300  and Hercules Video cards.
A. Hercules Graphite Terminator does not work; the video BIOS uses too many 
memory segments and the video logic is not "smart" enough to handle the TV card's 
address mapping...
Hercules Graphite Pro ISA and its latest drivers is OK in Windows at 800x600x256.

Q. TV300 (PrimeTime Ver 1.1) : Image Capture - not working or locking up 
system.
A.  This depends on the BUFFER address setting in the TV300 setup. Try the D and A 
address range, and make sure you add the exclude range in your EMM386.EXE 
statement in your config.sys i.e.:   if you choose D000h as address, add x=d000-d8ff to 
your EMM386.EXE.

Q. Techworks Thunderbolt 64 Display Card - TV300 not working in SVGA mode.
A. This card is sold by PC World. Because of technical problems it has been withdrawn 
as from June 1995. Problems with the onboard BIOS causes conflict with all PC’s 
except some Compaq and WYSE models.

Q. PCI Display adapters and TV300 - no display, or only in VGA, example cards: 
#9E with 2Mb VRAM, Oak and Diamond.
A. When you load the proprietary driver that activates the video accelerator on the 
video card, it will "mask" (if you will) the feature connector from being seen by the 
video card and it's drivers because the feature connector is only an 8 bit data path.  
Since the feature connector is only an 8 bit data path, if it remains under the drivers 
control while the accelerator engine is activated, this will slow down the card and 
hamper the drivers ability to work in a streamlined fashion.

When the accelerator is on, the VESA connector is not going to work properly, hence, 
your screen goes blank.  The "work around" is to load the standard generic drivers that 
come with Windows.  This will effectively solve the issue, however, you will loose the 
high performance from your video card.  

Currently, Reveal cannot fix this problem because of the dependency we (the industry) 
have on the connector to supply alternate video signals in conjunction with video (the 
current VESA standard).