Newsgroups: comp.sys.novell Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!bronze!copper!wsadler From: wsadler@copper.ucs.indiana.edu (william sadler) Subject: Re: WP Office Shell and Netware 2.2 Message-ID: Sender: news@bronze.ucs.indiana.edu (USENET News System) Organization: Indiana University References: <5540@mindlink.bc.ca> Date: 19 Apr 91 14:04:40 GMT Lines: 28 Ullrich_Fischer@mindlink.bc.ca (Ullrich Fischer) writes: >I've run into similar problems on a number of machines including networked with >Netware 2.15c and 386. In each case the solution was to change the SHIFT-F1 >setup so that the automatic backup directory mentioned there pointed to a >directory which actually existed. If automatic backup is enabled and the >directory to which the backup >is directed does not exist, this message seems to come up{ While this suggestion and another about checking the rights of users in the backup directory, and also checking the amount of free disk space and any limitations imposed by disk quotas are all correct, they are not the source of this bug. It seems to only effect stations with extended memory above 640K for some reason on my network. WP has informed me that it definitely is a compatibility problem between Netware 2.2 and the WPOffice Shell. If you run WP outside of the shell the problem goes away. I'm still waiting for an answer from WP and/or Novell via WP. Will -- ********************************************************************** *Will Sadler Indiana University Law School-Bloomington * *will@ogre.cica.indiana.edu wsadler@copper.ucs.indiana.edu * **********************************************************************