aa41@terre (Eric Trepanier) (05/21/91)
Hello. I'm new to this newsgroup and lately, I've seen mentions of a program manager alternative: Usher. It seemed to be a relatively good piece of software so I ftp'ed it from Cica. Once unzipped, I ran it using the File Run command. Everything seemed to work fine, I even managed to customize the Usher.ini file to get all the programs I wanted in the menus and everything was Ok. After a few hours, I was quite convinced that Usher provided a neat replacement of the program manager, so I edited the system.ini file to replace the "shell=progman.exe" for a "shell=usher.exe" command line. I then closed down windows and reloaded it. The little Usher icon appeared on the bottom left as Windows was booting up, along with other icons, (winexit, afterdark, ...). But when the hard disk finally stop spinning, I couldn't get usher to display its menus. Everything else worked fine, but Usher seemed totally inactive, even though the task manager reported it as active. I tried single clicking, double clicking but nothing happened. All that was left for me to do was to double click winexit and reboot (after having restored progman.exe in the system.ini). I then tried running Windows file manager (winfile.exe) as a shell and it worked fine. Anybody have any idea what could be causing this situation? Any tips would be really appreciated. Now I can run usher automatically upon entering windows by putting it in the run= statement, but I would like to get rid of program manager which I don't use anymore. If it can help, I do have a 386/33 and I have been running Windows for months without having any particular problems... -- +-----------------------------------------------------------------------------+ | Handy Guide To Modern Science: | Eric Trepanier | | 1. If it's green or it wiggles, it's biology. | trep@tgm.Sherb.CAM.ORG | | 2. If it stinks, it's chemistry. | aa41@Terre.DMI.USherb.CA |
lair@ellis.uchicago.edu (Scott A. Laird) (05/22/91)
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. george@garfield.catt.ncsu.edu (George Browning) (05/22/91)
>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. Sorry -- I know about the conflict. I'm working on Usher 1.31 now. So far: - added system resources information display - compatibility with ATM (I hope) - general code cleanups I'm looking at: - keyboard shortcuts - ??? I'm kind of busy at work now but the update will come out soon. Thanks for your comments, george (the author of Usher) ------------------------------------------------------------------------ | o | George Browning george@catt.ncsu.edu | o | | o | NC State University Raleigh, NC | o | ------------------------------------------------------------------------