[comp.binaries.ibm.pc.d] Problem with Usher 1.1

tom@dvnspc1.Dev.Unisys.COM (Tom Albrecht) (01/25/91)

A colleague without Usenet access asked me to ask this question:

  I tried Usher 1.1 out and seem to have a problem.

  I have program called Idlewind which looks at keystrokes and mouse
  movement and blanks the screen after a certain time.

  If this program is in the ini file as a load file, Usher comes up with
  two screens asking me to switch diskettes to load a DLL file of some
  sort.  One of the files is ABOUTWEP.DLL.  I have no idea how to fix it.

  Has anyone seen this, and does anyone have a workaround

Thanks.

-- 
Tom Albrecht

dkyoon@pollux.usc.edu (Dae-Kyun Yoon) (01/26/91)

tom@dvnspc1.Dev.Unisys.COM (Tom Albrecht) writes:


>A colleague without Usenet access asked me to ask this question:

>  I tried Usher 1.1 out and seem to have a problem.

>  I have program called Idlewind which looks at keystrokes and mouse
>  movement and blanks the screen after a certain time.

>  If this program is in the ini file as a load file, Usher comes up with
>  two screens asking me to switch diskettes to load a DLL file of some
>  sort.  One of the files is ABOUTWEP.DLL.  I have no idea how to fix it.

>  Has anyone seen this, and does anyone have a workaround

I had the same problem with "magic" which is a screen saver, too.
While loading magic it looks for magic.dll (not sure about the filename).
I kept magic.dll in different directory other than windows default directory.
It worked fine with progman, but with "usher" I had to move magic.dll to
windows default directory.  So the solution is simple, move *.dll file
to windows default directory.

Here I would like to make a suggestion on the future version of usher.
It would be nice if we could keep *.dll files together with *.exe file
in different directory especially when we have no control over starting
directory.  Launching an application thru "usher.ini" is no problem as we
can specify initial directory.  However, if we launch an application in
"load=" or "run=" line in "win.ini" file,  we may be in trouble as described
above.  It would be even better, if we could keep "usher" files in
different directory other than windows default directory.


-- 
Dae-kyun Yoon
dkyoon@usc.edu, ..!uunet!usc!dkyoon