V2DOSFIX.TXT Driver File Contents (V2200.zip)

--------------------------
V2DOSFIX.EXE V1.0 12/23/97
--------------------------

This program patches Verite-accelerated MSDOS games so that V2x00 chips
can execute them natively under MSDOS without Win95's dos-box.

*************************************************************************
*** MAKE A BACKUP OF ALL EXE FILES YOU PLAN TO PATCH WITH V2DOSFIX!!! ***
*************************************************************************
-----------
The problem
-----------

 *   Many V2x00 regularly play one or more RReady MSDOS (Speedy3d API) titles.
 *   Unforunately, most of these MSDOS games (Nascar2, Tomb Raider, etc.)
 *   were written before the V2x00 came into existance and have not been
 *   updated since.  While they can still be run in all their
 *   Rendition-accelerated glory, doing so requires use of Win95's DOS-box,
 *   an undesirable arrangement for some.

Workaround
----------
 *
 *   v2dosfix is a generic patch for Verite-accelerated DOS games.  When
 *   invoked with a user-specified filename, the program performs a search
 *   and replace operation on the first located occurence of the V1000's
 *   PCI identification string: deviceID (0x0001) and vendorID (0x1163)
 *   Upon locating these two elements, V2DOSFIX replaces the old deviceID
 *   with the 0x2000 (V2x00's deviceID)
 *
 *   if you're a bored C-programmer, you can look at my source code for some
 *   laughs...

-----------------------
HOW TO USE V2DOSFIX.EXE
-----------------------

Before you start, does the game need to be patched?

    YES - The game in question loads and aborts with a message saying
                something to the effect of "could not find Rendition chipset."

    NO  - The game already runs fine under vanilla MS-DOS.  The latest
                Vquake patch and Indycar II patch are examples of such games.

    NO  - The game is "designed for Windows95."  (i.e. Rendition Redline
                API titles do NOT need to be patched!)  If your RRedline
                game doesn't work, it's probably a totally different issue
                that has nothing to do with chipset misidentification.

Now that you've determined whether you need to run v2dosfix, here are the
instructions!  Not hard at all.

        1)      Make a BACKUP of the Rendition-Ready DOS-binary
                (nasrend.exe, tomb.exe, etc.)

        2)      invoke v2dosfix from the dos command-line with the
                filename of the game's binary

                        e.g.  C:\TOMBRAID\V2DOSFIX tomb.exe

        3)      Cross your fingers.

        4)      Run your program under vanilla MS-DOS (kein Win95, bitte.)


-----------
Limitations
-----------
 *
 *   A succesfully patched game file will NO LONGER RUN on V1000 boards!
 *   Probably not a big deal to most of you, but I still have to mention it.
 *
 *   The loose nature of the pattern-finding algorithm may cause multiple
 *   occurences of the search-pattern (deviceID/vendorID) to be detected.
 *   If V2DOSFIX detects more than 1 occurence, it will assume the worst, i.e.
 *   the patch-process failed.  You will receive a message warning of 
 *   probable failure.
 *
 *   The absence of a failure report is not a 100% assurance:  running
 *   the patched game-executable is the real test.
 *
 *   For the record, I've tested v2dosfix with the following titles :
 *
 *      Nascar2         ( NASREND.EXE   v1.02   05/97 )
 *      Tomb Raider     ( TOMB.EXE      beta4   01/97 )
 *


----------
Final note
----------
 *   most Speedy3D are *not* optimized for the V2x00 architecture.
 *   As a result, the V2x00 board may not run certain Verite-accelerated
 *   games much faster than the old V1000.  ID Software cites this disclaimer
 *   in its distribution of VQuake.

 *   If V2DOSFIX.EXE doesn't work on your game, try using a HEX-EDITOR on
 *   the game-binary.  Search for the PAIRED 32-bit pattern(s) "63 11 00 00"
 *   and "01 00 00 00"  Try changing "01 00 00 00" (V1000 ID) to
 *   "00 20 00 00" (V2100 ID.)  Through trial and error, you may still be able
 *   to patch your RReady DOS game.


--------------------
Comments, questions?
--------------------
 *   Please, I'm a busy college-student...chances are other people on the
     'net can help you with this program.  Try out the usenet newsgroups
     like
        comp.sys.ibm.pc.hardware.video,
        comp.sys.ibm.pc.games.action,
        comp.sys.ibm.pc.games.adventure,
        etc.

     Be sure to visit Rendition's site (http://www.rendition.com) frequently
        Bjorn's 3D-site http://www.bjorn3d.com is another excellent site
        loaded with tips&tricks for Verite owners.

 *   Well, if you *must*, you can email me at liaor@uci.edu
     (If you indicate that your social status is single, Taiwanese, female,
      I *might* find more time to reply!  just kidding :)

        Rendition Crusader #7
        Royce Liao (liaor@uci.edu)
        http://www.eng.uci.edu/~liaor
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web4, load: 1.07