-=> On 01 Mar 96  15:38:20 Mike Bilow said to Andrew Grillet <=-

 AG> It would really be a MAJOR improvement if E.EXE offered you
 AG> the choice to NOT LOAD AT ALL if it finds nulls. Generally
 AG> you want to start a different program in place of E.EXE at
 AG> this point, and not open E.EXE and then close it and then
 AG> start the other app. Or am I missing something?

 MB> Well, how is E.EXE going to know whether nulls are present unless it
 MB> runs?

Telepathy might be worth a try :-)

You know what I mean - after you get the dialog saying the file had nulls
in it, you know you did not want to start E.exe. BUT there is no way
to prevent E.exe spending far more time setting itself up after the
dialog than it spent before the dialog, even though you don't want e.exe
at all. The dialog box needs an 'ABORT' option.

This normally happens because you double clicked on something which has
no association, so e.exe is invoked on a binary file, which is normally
useless. You knew what the correct association should be, and need
to set t up. EG you don't know whether a .DOC file is 'Word for
OS/2' or plain text - if it has nulls, you need Word.

Andrew


... Politics defined:  poli=many  tics=blood suckers
--- Blue Wave/Max v2.12 OS/2 [NR]