Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!ellis.uchicago.edu!lair
From: lair@ellis.uchicago.edu (Scott A. Laird)
Newsgroups: comp.windows.ms
Subject: Re: Problem with Usher 1.3
Message-ID: <1991May21.180139.15034@midway.uchicago.edu>
Date: 21 May 91 18:01:39 GMT
References: <1991May21.010920.18478@DMI.USherb.CA>
Sender: news@midway.uchicago.edu (NewsMistress)
Organization: University of Chicago
Lines: 34

I'm having a similar problem that I can sort of deal with.  Usher loads but 
apparently does not load usher.ini, therefore will not pop up a menu.  This
happens whenever I try to load usher from the shell, load, or run lines
in win.ini/system.ini.  It _will_ work just fine, however, when I don't run
ATM, i.e. change the system.drv=atmsys.drv line back to system.drv.  Then it 
loads just like it should, but by changing just that line it fails to load.  It
works just fine when I use File Run... to run it.

So what is the conflict between ATM and usher?  I really like usher, but
its a hassle to have to hand load it every time. 

System:
	286-20, 5 Mb RAM
	200 Mb IDE drive, Windows (and everything else) on drive D:
	VGA
	ATM.

Since someone has a problem on a 386/33, it doesn't seem to be extremely
system-specific, but I haven't seen anyone else with the problem posting, 
so there must be some factor in common.

If anyone has any suggestions, please either post or email them, I'll test
them and report back to the net, if appropriate.

Scott.




-- 
Scott A. Laird            |  Any semblance of the above to anything is purely
lair@midway.uchicago.edu  |  coincidental, as it was the result of an infinite
The University of Chicago |  number of monkeys sneaking in to use my computer 
                          |  for the afternoon.