23.04.2013 Views

Release Notes MicroImages, Inc. TNT-Products V. 6.8

Release Notes MicroImages, Inc. TNT-Products V. 6.8

Release Notes MicroImages, Inc. TNT-Products V. 6.8

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

RELEASE OF RV<strong>6.8</strong> <strong>TNT</strong> PRODUCTS<br />

You will no longer be able to download the smaller patches needed to correct a single<br />

application in RV<strong>6.8</strong>. To obtain a patch for a specific feature you will always need to<br />

download the larger, latest PV<strong>6.8</strong>.<br />

When you have patched RV<strong>6.8</strong> (replaced it with a PV<strong>6.8</strong>) the date of this total patch,<br />

and, thus, the identity of your current PV<strong>6.8</strong> will be clearly displayed. This “Date of<br />

Patch” of your PV<strong>6.8</strong> should always be provided to <strong>MicroImages</strong>’ software support to<br />

identify your PV<strong>6.8</strong> with every communication from you for any technical assistance request<br />

or error report. You will find this date on the Help/About <strong>TNT</strong>mips window and it<br />

will be changed by each new PV<strong>6.8</strong> you install.<br />

What<br />

is the Development Version (DV6.9)?<br />

<strong>MicroImages</strong> has many innovative and imaginative (and patient) clients who work<br />

closely with us to guide and test the development of the <strong>TNT</strong> products. If you are in this<br />

group, you already know that you have a direct role in the evolution of the <strong>TNT</strong> products.<br />

For meeting our short run goals you patiently work with the Development Version and<br />

provide both error identification and design feedback, especially when we are working<br />

on improvements in your particular area of interest in a <strong>TNT</strong> product. Sometimes your<br />

suggestions are easily and quickly incorporated in the Development Version. Sometimes<br />

implementing your request is complex even though it may not seem so to you. Or<br />

sometimes your need is very specialized and is judged to be of low interest to any other<br />

<strong>TNT</strong> client. In these cases, it goes on our big “new feature list” for consideration in the<br />

future or as part of the periodic redesign of the entire processes or its low-level core operations.<br />

Windows is very resistant to the installation of multiple copies of any software product.<br />

This is very important to keep you from mixing old and new components. Everyone has<br />

had the experience of concluding something was not operating properly in an earlier<br />

Windows application<br />

only to find, after much frustration, that a path led to the wrong ver-<br />

sion<br />

of a component. However, this Windows one-and-only-one-version policy has<br />

made it difficult to set up 2 versions of a previous <strong>TNT</strong> product. This is now simple as<br />

the DV6.9 of the <strong>TNT</strong> products has a new and totally different identity in so far as Windows<br />

is concerned. Thus, DV6.9 can by automatically installed and managed separately<br />

from RV<strong>6.8</strong> or its subsequent conversion to PV<strong>6.8</strong>, and Windows will treat each<br />

as a separate product.<br />

Note: Windows will let you install and patch DV6.9 whenever you choose as it is a separate product from<br />

your RV<strong>6.8</strong> or PV<strong>6.8</strong><br />

Using the Development Version (DV6.9).<br />

Working with DV6.9 of the <strong>TNT</strong> products is now more or less equivalent to your past<br />

experience with working with a patched version of V6.70. However, to work with DV6.9<br />

you will have to download it from microimages.com and install it. DV6.9 with alterations<br />

and corrections will be replaced weekly rather than the previous Tuesday/Thursday<br />

patch procedure.<br />

MICROIMAGES MEMO 20<br />

5 MAY 2003

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!