TWAR For Windows version 1.001 was released on November 24, 1998 which followed its previous DOS versions. Unfortunately, Douglas Underwood, the program's author, has never released an upgrade to the TWAR For Windows. The patch update released in March 1999 did not address many of the issues that still exist within the program. This survival guide is only designed to deal with some of the problems with TWAR and how to cope with some of its "access violation" errors. Most of this information is drawn from my own experiences as well as from message postings that coincided with what I had already discovered since its release.
 

1. Retrieve Galaxy Data (Control-F9) and Best Sectors Report (F9)

Using this function sometimes causes the following error:

"Access violation at address 004EF8A1 (or some other number) in module TWAR.EXE. Read of address 034825B0 (or some other number)."

SOLUTION: Pressing Control-F9 and running the CIM data again usually stops this error. You must press the "escape" key continously to clear the error messages before pressing control-F9. [Note: This will require using both hands simultaneously.]

2. Visual Map Diagram (F2)

Same as "Retrieve Galaxy Data."

SOLUTION: Pressing Control-F9 and running the CIM data again usually stops this error. You must press the "escape" key continously to clear the error messages before pressing control-F9. [Note: This will require using both hands simultaneously.]

3. Word Processor (Control-W)

Same as "Retrieve Galaxy Data."

SOLUTION: Pressing Control-F9 and running the CIM data again usually stops this error. You must press the "escape" key continously to clear the error messages before pressing control-F9. [Note: This will require using both hands simultaneously.]

4. SST, SSM, RMR, RTR (Control-X)

Same as "Retrieve Galaxy Data."

SOLUTION: This one differs from the others mentioned earlier but pertains to all of the options under the Control-X function. First, press the "Escape key" to remove any error messages remaining on the screen. Second, scan the sectors with the "Holographic Scanner." I do not know why this works but it does. Please note that the "density scan" does not work to revive this script.

5. Port Pair Trading (F3)

During this script, an error will sometimes occur during the trading where incorrect numbers are entered causing the ship to fly 8 to 10 sectors away and repeat again. I have had this happen with 400 turns and was left with less than 50 turns before I could stop the error. This is a dangerous error and can get you killed in the game should you enter an unwanted sector.

SOLUTION: Pressing the "Escape" button DOES NOT stop this error! You must shut down the program to stop the error. The only other suggestion I have is to watch the trading script like a hawk and catch it early in the process.

6. Deceiving CIM Data

After viewing the CIM data (using F9) you may notice higher than normal amounts between port pairs--usually 2,000 or more units. As the old saying goes "if it looks too good to be true, it usually is." It usually turns out to be a "one-time" port-pair where one of the ports is in a "one-way only" sector. This can be a "turn'killer" if you're not careful. I recommend moving between the two ports to be certain they are in fact one warp away from each other going both directions.
 
 

Revised 8/18/1999
GRO