From: vporguen@unlinfo.unl.edu (victor porguen)
Newsgroups: comp.archives.msdos.d
Subject: How to eliminate the SECOND Telix nag screen
Date: 29 Dec 1992 05:07:27 GMT
Organization: University of Nebraska--Lincoln	
Distribution: world
NNTP-Posting-Host: unlinfo.unl.edu
Keywords: Telix Shareware Crippling Screen Telecommunications

Further writes ts@uwasa.fi (Timo Salmi), on the subject of the Telix
nag screens:

> That is up to the users to decide.  If they find such a system 
> useful in a situation like this, then so far so good.  If they 
> don't find it useful, then the users just won't use it, and again 
> so good so far.

Certainly, but facts are facts.  If a given program DOES something, 
then it does it. If it does NOT, then it does not.  Not a matter of 
opinion, but a matter of fact.  But I wasn't trying to demean your 
utilities - Popscr and Pushscr may actually be excellent. It's just 
that they can't eliminate the closing nag screen any sooner than 
`cls' will (though they *will* restore the original screen, 
eventually).

Horse beaten to death, end of subject!

>   But let's not forget that in the long run the only acceptable 
> method of removing the said screen is registering.

I would rephrase your sentence to say that in the long run (after the
trial period), the honorable thing to do is to register the program 
IF YOU CONTINUE USING IT, yes.  But does that mean that I have to 
tolerate the unmitigated... !pain! of those Telix nag screens, 
flashing at me on-and-off, on-and-off, DURING the 30-day trial 
period?  Absolutely not!

The nag screens are obnoxious and offensive.  They interfere with
my testing of the program.  They cause me to have a negative attitude
toward the program and its author.  I believe that people trying the 
program out are free to get rid of the nag screens in ANY way they 
can.  Including, but not limited to, throwing Telix into the garbage 
can, as I eventually did, for that sole reason. 

But here's some remedy:

How To Eliminate the Telix CLOSING Nag Screen Completely
--------------------------------------------------------
There is a simple, legal and ethical way to make that closing screen 
disappear: if you set your Telix colors so that the Menu Border and 
the Menu Border Background are the same color, the closing screen 
washes out!  If you choose black Menu Border and black Menu Border 
Background, the closing screen will actually become *invisible*, and 
all you'll see is a black screen for 3 seconds, then the DOS prompt 
reappears.   (TIMOPLUG: In this case, Prof. Salmi's utilities POPSCR 
and PUSHSCR might come in handy here to restore the original screen 
after 3 the second delay.  You're welcome.)  Under one possible 
Telix color scheme:

    Screen forgrnd     -  White
    Screen backgnd     -  Blue
    Screen border      -  Black
    Menu border        -  Blue
    Menu border bckgnd -  Blue
    Menu forgrnd       -  Black
    Menu bold          -  White
    Menu backgnd       -  Cyan
    Menu bar           -  Magenta
    Menu selection     -  Yellow
    
the closing screen is also unreadable: blue on blue.  All you see is 
a blue rectangle for 3 seconds. That's not bad, what the heck. Quite 
legal, too: it's built right into the program   }:-)

> No big deal.  The important part was to exchange information, 
> which the users may then utilize if they find it relevant.  I 
> think this about covers our exchange of views.

Fine. Agreed.

I do have some more information about Telix' serious crippling (the 
Script-Learning function), and how to legally and ethically cure it. 
That will be posted separately.

Newsgroups: comp.archives.msdos.d