vito@trwspf.UUCP (05/15/87)
David Berry's patch for uw and system 4.1 not only works for uw, but also for: MacTerminal 1.1 FastEddie TMM (a Red Ryder Host utility) and probably many other things. I guess we know which compiler these came from :-)............. Try this on your favorite problem application: find 02B6 and change this to 0A78 there of usually several (not always just 2) occurences of this. -- Herb Barad - TRW Data Systems Lab ARPA: barad@brand.usc.edu USENET: ...!trwrb!trwspf!vito
lsr@apple.UUCP (05/15/87)
In article <248@trwspf.TRW.COM> vito@trwspf.UUCP (Herb Barad) writes: >Try this on your favorite problem application: > >find 02B6 and change this to 0A78 Just a few words of explanation. The purpose of this patch is to change applications that use memory location $2B6 (which was reserved by Apple and is now used in System 4.1) to use location $A78 (which is the start of a 12 byte area that is available to applictions). There are 2 things to watch out for: (1) Locating all occurences of 02B6 is potentiall dangerous since those 2 bytes may occur in other circumstances. Ideally, you should check to see if those bytes are part of an instruction that is actually referencing the memory location, and not something else. (2) Since the 12-byte area is available to applications, it is possible that the application is already using it. (I suppose one could search of occurrences of 0A78 first to see if this is true.) Since the scratch area is 12 bytes long, there are other possible choices for the replacement string. Also, the usual advice (work on a copy of the application, etc.) applies. -- Larry Rosenstein Object Specialist Apple Computer AppleLink: Rosenstein1 UUCP: {sun, voder, nsc, mtxinu, dual}!apple!lsr CSNET: lsr@Apple.CSNET
dwb@apple.UUCP (Dave W. Berry) (05/15/87)
In article <248@trwspf.TRW.COM> vito@trwspf.UUCP (Herb Barad) writes: >David Berry's patch for uw and system 4.1 not only works for uw, but >also for: > >Try this on your favorite problem application: > >find 02B6 and change this to 0A78 > >there of usually several (not always just 2) occurences of this. I might reiterate that before actually making the change you ought to search the program for other occurences of 0A78 to make sure that the application isn't already using ApplScratch for something else. If it is you might want to disassemble the area and see how much of the region from 0A78 to 0A83 is used and replace the 02B6 references with references to a long word in the region which isn't used by the application. >Herb Barad - TRW Data Systems Lab >ARPA: barad@brand.usc.edu >USENET: ...!trwrb!trwspf!vito -- David W. Berry dwb@well.uucp dwb@Delphi dwb@apple.com 293-0752@408.MaBell
fry@huma1.HARVARD.EDU (David Fry) (05/16/87)
Does anyone have any guesses why Manx's Aztec C shell program doesn't work under System 4.1? It starts up and displays the "hello" screen, but crashes while setting up the menus. The crash ID is 99, whatever that is. Macsbug showed that the SHELL was not using $2B6 and sure enough the patch given here doesn't help. David Fry fry@huma1.harvard.EDU Department of Mathematics fry@harvma1.bitnet Harvard University ...!harvard!huma1!fry Cambridge, MA 02138
steele@unc.UUCP (05/16/87)
>Try this on your favorite problem application: > >find 02B6 and change this to 0A78 What exactly is 02B6 used for by the new System/Finder? If it's just used by the Finder, an init to hook onto _Launch and _ExitToShell to save and restore its contents would fix everything, otherwise more drastic measures might still save patching so many programs. ------------------------------------------------------------------------------ Oliver Steele ...!{decvax,ihnp4}!mcnc!unc!steele steele%unc@mcnc.org "Education and religion are two things not regulated by supply and demand. The less of either the people have, the less they want." - Charlotte Observer, 1897
duffy@ttidca.TTI.COM (David Duffy) (05/19/87)
In article <1997@husc6.UUCP> fry@huma1.UUCP (David Fry) writes: > >Does anyone have any guesses why Manx's Aztec C shell program >doesn't work under System 4.1? .... > You probably copied the new System file into your System Folder rather than running the Installer scripts to update your old System. By doing this, you lost the ".con" resource which is required to run the Aztec shell. Use the InstallConsole application supplied in the Aztec C development system to re-install this resource. I am using the Aztec shell will System 4.1 and have not experienced any problems. Dave Duffy
levin@cc5.bbn.com.UUCP (05/26/87)
In article <728@ttidca.TTI.COM> duffy@ttidcb.UUCP (David Duffy) writes: >You probably copied the new System file into your System Folder rather >than running the Installer scripts to update your old System. By doing When I opened the box with my shiny new SE and looked at the disks, there was an installer with scripts for loading up systems specifically for each of the possible mac types, as well as a 'universal' script to build a system to run on any machine. There was also a 'read me' file with a release note, which said, in effect, ignore the instructions in the manual and COPY the files in the new System folder onto your various disks. !! Anyone know what this is about? > Dave Duffy /JBL -- UUCP: {harvard, husc6, etc.}!bbn!levin ARPA: levin@bbn.com {My apologies for possible second copy -- I'm reposting after our news got fixed} -- UUCP: {harvard, husc6, etc.}!bbn!levin ARPA: levin@bbn.com
dgold@apple.UUCP (05/29/87)
In article <1354@cc5.bbn.com.BBN.COM> levin@cc5.bbn.com.UUCP (Joel B Levin) writes: >When I opened the box with my shiny new SE and looked at the disks, >there was an installer with scripts for loading up systems >specifically for each of the possible mac types, as well as a >'universal' script to build a system to run on any machine. There was >also a 'read me' file with a release note, which said, in effect, >ignore the instructions in the manual and COPY the files in the new >System folder onto your various disks. > >!! Anyone know what this is about? There should be no problem using the installer, unless you have a one- drive system. You should be using System 4.1/Finder 5.5, the latest release. There is no longer a "Universal" installation script; however, the "Macintosh II (4.1)" script is in effect a universal script; it will produce a system which will work for all Macintoshes. -- David Goldsmith Apple Computer, Inc. MacApp Group AppleLink: GOLDSMITH1 UUCP: {nsc,dual,sun,voder,ucbvax!mtxinu}!apple!dgold CSNET: dgold@apple.CSNET, dgold%apple@CSNET-RELAY BIX: dgoldsmith