-=> On 11 Jun 96  21:47:16 Jonathan de Boyne Pollard said to Andrew
Grillet <=-


 JdBP> If your argument is based on the principle that OS/2 users are
 JdBP> generally more astute than Windows users, then I can very easily
 JdBP> throw that right back at you by saying that binary INI files do *not*
 JdBP> stop OS/2 users from fixing INI files, because OS/2 users are astute
 JdBP> enough to be able to write 3-line REXX scripts to hand-modify INI
 JdBP> files when they need to. 
 JdBP> Or use one of the 15 or so INI file editors Out There ...
 
My point was missing a smiley perhaps, but generally OS/2 users fall into the
two divisions of 'those with the time and skill to find out how to hack an
ini file with an editor' and 'those who know they can't and call in an
expert' - More Win users than OS/2 users are in the class 'I dont know how
to do it, and can't afford to pay a man that does'.

You cannot in general expect to find an ini editor on another user's machine.
(So remember to take one when called out). But you also cannot easily tell
someone over a phone how to use an ini file editor you've never seen. Its
a lot easier to tell them how to use windows write IME.

Sure they can down load one from your BBS, etc, but its definitely less
convenient. THEY remember the grief. Its certainly painful to try to
find out whether a problem is attributable to sick binary ini files on
someone else's machine over a phone. Particularly if it isnt. This is
simply not the case for a quick view of a text ini file with their
favorite editor (except if their favorite editor is edlin of course).

Andrew

Andrew

 
... Apathy ERROR: Strike any key, or none. Who cares?!
--- Blue Wave/Max v2.12 OS/2 [NR]