From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] OT: sam on XP Message-ID: <20020303000351.C1495@cnm-vra.com> References: <20020227203722.A2370@cnm-vra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gwyn@arl.army.mil on Thu, Feb 28, 2002 at 04:02:17PM +0000 From: Micah Stetson Date: Sun, 3 Mar 2002 00:03:51 -0800 Topicbox-Message-UUID: 5e1ba252-eaca-11e9-9e20-41e7f4b1d025 > Yeah. You can fix it by selecting Properties for the invoking icon > and setting it up with an earlier environment, e.g. Windows 98 > if using Windows XP Home Edition. Hmmn. This didn't seem to fix it. Using the sam from netlib, the behaviour is the same no matter what the setting in the Compatability tab. Using the one form the Plan 9 updates page, it behave the same except that if I set the compatibility mode to "Windows 95" it gives some error about not being able to initialize. I'll try to get a hold of the exact message next week. But when the setting is not "Windows 95", it starts up and will allow me to use the mouse for a little while (I can open the menu a couple of times or create and place a new window). But after that, or immediately if I try to use the keyboard, the program stops responding at all. Thanks for your help, Micah