[comp.windows.ms] WIN 386/2, problem with WRITE double clicking on .WRI files

Barry Bailey (06/06/90)

 
   Whenever I double click on a document created by WRITE, a dialog box
   is displayed with the message "Cannot find file", I click on OK then
   WRITE is loaded with a new document. At this time I can FILE OPEN the
   document in the current subdirectory. I have checked the WIN.INI file
   for some sort of PATH restrictions in the [WRITE] section, none
   exist. I was told that the APPEND command in AUTOEXEC.BAT might mess
   up WIN, I took it out. My PATH command is OK, the application is
   always found but not the document.
 
   I am able to launch all other applications (including standard app's)
   by double clicking on their respective document files from a variety
   of subdirectories and floppy disks (I tested for this :<
 
   What's the deal?
 
   Anyone ever have this happen to them? Reply to USERE9W9@RPITSMTS or
   here.
 
   thanks
 
   barry

rspangle@jarthur.Claremont.EDU (Randy Spangler) (06/07/90)

In article <9848.2364.forumexp@mts.rpi.edu> Barry Bailey writes:
>
> 
>   Whenever I double click on a document created by WRITE, a dialog box
>   is displayed with the message "Cannot find file", I click on OK then
>   WRITE is loaded with a new document. At this time I can FILE OPEN the
>   document in the current subdirectory. I have checked the WIN.INI file
>   for some sort of PATH restrictions in the [WRITE] section, none
>   exist. I was told that the APPEND command in AUTOEXEC.BAT might mess
>   up WIN, I took it out. My PATH command is OK, the application is
>   always found but not the document.

I've had similar problems with some shareware apps, and I discovered that
it wasn't necessarily the file I clicked on that they couldn't find.  For
some reason, Windows looks only in the windows directory sometimes, completely
ignoring the path.  Workaround unknown.  I DO wish that it would tell me
WHICH file it couldn't find.  (the last problem I eventually solved - programs
were looking for WIN87EM.EXE in the Windows directory and not finding it -
so I copied WIN87EM.DLL from the windows/system directory and renamed it *.EXE
and it worked fine).

----------

As a side note, would someone with Compuserve access please tell the net
about all the shareware programs being announced there?  I haven't got access
to it, and I haven't heard diddly about shareware for Win 3.0.  

How about someone posting these programs, or at least putting them somewhere
we can anon.ftp them?  All the ftp sites I've looked at recently still have
the same year-old garbage but nothing for 3.0.


-- 
 --------------------------------------------------------------------------
|    Randy Spangler                    |    The less things change, the    |
|    rspangle@jarthur.claremont.edu    |    more they remain the same      |
 --------------------------------------------------------------------------