robot@unmvax.UUCP (03/07/86)
I recently got the Aztec C68K-c compiler for my Mac and installed it on my hyperdrive. After installing the Manx console driver in my system file, I was able to open the SHELL but the mouse would freeze. The folks at Manx gave me afour-line routine to patch the resource fork of the SHELL to thaw out the mouse. Although this patch works on their Hyperdrive (we both have ROM versions 410), it does not work on mine. It is certainly possible I did something wrong. If I knew how to use ResEdit I could verify the patch. I have an early version of ResEdit but no documentation. Where can I get the real thing? Another quirk happens when exiting the SHELL back to the Finder. Manx gives a one liner in their release documentation of the proper way to envoke the Finder. It involves changing a field in low memory which defines the command processor program. When entering the SHELL this field is changed to return back to the SHELL after executing a program. To return to the Finder, this field must be changed back to indicate the Finder as the command processor now. This exit works except that the drawer containing the SHELL sits in the startup drawer position on the desk top even though there are no system files whatsoever in it. My Startup drawer, containing all system related files, is put at the next lower position. The Finder and all applications seem to work fine, it's just that the drawers are not in their correct positions. Does this happen to anyone else? Even more baffling is that executing an application on the Startup drawer, such as the Manager, and then quiting back to the Finder does not straighten out the drawer positions. This situation is not impossible to live with but I'm afraid I'm one of se "e "a place for everything and everthing in it's place" people. Got any ideas? Cliff Loucks Sandia National Labs Albuquerque, NM
heins@trwrba.UUCP (Michael T. Heins) (03/12/86)
[] Concerning the "mouse freeze-up" problem...I experienced the same problem on my system (512K, 10Meg Hyperdrive, Finder 4.1, Commercial Aztec C). I had not talked to Manx about it, but through trial and error, I discovered that if I prevented the shell from executing .profile at startup and instead executed it manually after the shell was booted, I no longer had the problem. (I renamed the .profile to profile). Incidentally, I have also experienced a form of mouse horizontal-coordinate freeze-up (the mouse only moves vertically) following Hyperdrive boot-up. Re-booting usually takes care of the problem, which seems to have a low, random probability of occuring at each boot-up. I don't know if the two problems are related. -- ...!hplabs!sdcrdcf!trwrb!trwrba!heins We are a way for the universe to know itself. -- Carl Sagan