js7@CUNIXA.CC.COLUMBIA.EDU (Jackson) (08/25/89)
Hi All, I've got lots of questions... Does anyone have a list of all Apple GS errors? I'm getting errors like "$0911" and "Tool Error $004A". What the heck does this stuff mean, and where can I found a list of all such possible errors. What can I do about these things? Thanks for any help. On a different note, can anyone tell me how to install more fonts than the ones that come with AppleWorksGS? What files/directories do I need to copy from the GS/OS Sys disk in order to make my own that will boot? I would like to try and make a self-booting disk, without needing to first boot up the GS/OS disk. Any ideas? Also, anyone have an NDA that will allow me to instantly add NDA's? And, how about an NDA or something that will allow me to make changes to the Control Panel and have them effective immediately? Thanks everyone.... Jackson -- js7@cunixa.cc.columbia.edu
dlyons@Apple.COM (David Lyons) (08/26/89)
In article <CMM.0.88.620061359.js7@cunixa.cc.columbia.edu> js7@CUNIXA.CC.COLUMBIA.EDU (Jackson) writes: >Does anyone have a list of all Apple GS errors? I'm getting errors >like "$0911" and "Tool Error $004A". What the heck does this stuff >mean, and where can I found a list of all such possible errors. What >can I do about these things? Thanks for any help. There's no *complete* list, since any piece of software you're using can display whatever error codes it wants--but *usually* the error codes are things that are being passed along from GS/OS or the Toolbox, and you can find error codes in the GS/OS Reference Manual Vol 1 (APDA) and the Apple IIgs Toolbox Reference, Vols 1 and 2 (Addison-Wesley). There's probably not a lot you can do about 0911. I occasionally get those on my GS at home. Some machines never get them; some get them occasionally. (If you get them *frequently* & are still under warranty consider getting your dealer to replace your motherboard.) 0911 means that the system was unable to get synchronized with the "keyboard microcontroller" (the chip inside the GS that talks to the keyboard and mouse). The problem may be related to heat and/or power-supply load. >On a different note, can anyone tell me how to install more fonts than >the ones that come with AppleWorksGS? Copy them into the Fonts folder inside the System folder on the disk you start up from. >What files/directories do I need to copy from the GS/OS Sys disk in >order to make my own that will boot? I would like to try and make a >self-booting disk, without needing to first boot up the GS/OS disk. >Any ideas? Normally, you want to use the Installer or make an exact copy of an existing bootable disk. If you're looking for a *minimum* set of files you need to boot, see GS/OS Technical Note #1 (available lots of ways, including FTP from apple.com). --Dave Lyons, Apple Computer, Inc. | DAL Systems AppleLink--Apple Edition: DAVE.LYONS | P.O. Box 875 AppleLink--Personal Edition: Dave Lyons | Cupertino, CA 95015-0875 GEnie: D.LYONS2 or DAVE.LYONS CompuServe: 72177,3233 Internet/BITNET: dlyons@apple.com UUCP: ...!ames!apple!dlyons My opinions are my own, not Apple's.
dlyons@Apple.COM (David Lyons) (08/26/89)
In article <CMM.0.88.620061359.js7@cunixa.cc.columbia.edu> js7@CUNIXA.CC.COLUMBIA.EDU (Jackson) writes: >Does anyone have a list of all Apple GS errors? I'm getting errors >like "$0911" and "Tool Error $004A". [...] (Whoops--forgot to answer part of that in my last note.) Error $004A isn't really a toolbox error (the program that displayed that message was being a little lazy). From ProDOS and GS/OS, error $4A is "version error" or "bad file format"--the idea is that the version of the OS you're running thinks the file you're trying to read on disk was created by a later version of the OS, so it can't read it. This sounds a bit fishy to me, since I don't think that feature has ever been used for its originally-intended purpose. Possibly the file's directory entry on disk has gotten mucked up. Or possibly, IF you were using ProDOS 8 (earlier than 1.8) or ProDOS 16 (not GS/OS) at the time, it was complaining because you tried to get at a directory that had lower-case letters in its real name. (The "version" bits for files and directories were redefined as indicating the case of the characters in the name. For files they were never used anyway, but for directories, they were. See GS/OS Technical Note #8.) What were you doing when you got error $004A, and what software and OS versions were you using? --Dave Lyons, Apple Computer, Inc. | DAL Systems AppleLink--Apple Edition: DAVE.LYONS | P.O. Box 875 AppleLink--Personal Edition: Dave Lyons | Cupertino, CA 95015-0875 GEnie: D.LYONS2 or DAVE.LYONS CompuServe: 72177,3233 Internet/BITNET: dlyons@apple.com UUCP: ...!ames!apple!dlyons My opinions are my own, not Apple's.
fadden@cory.Berkeley.EDU (Andy McFadden) (08/26/89)
In article <34319@apple.Apple.COM> dlyons@Apple.COM (David Lyons) writes: >In article <CMM.0.88.620061359.js7@cunixa.cc.columbia.edu> js7@CUNIXA.CC.COLUMBIA.EDU (Jackson) writes: >>Does anyone have a list of all Apple GS errors? I'm getting errors >>like "$0911" and "Tool Error $004A". [...] [snip] >From ProDOS and GS/OS, error $4A is "version error" or "bad file format"--the >idea is that the version of the OS you're running thinks the file you're trying >to read on disk was created by a later version of the OS, so it can't read it. > Or possibly, IF you were using ProDOS 8 (earlier >than 1.8) or ProDOS 16 (not GS/OS) at the time, it was complaining because you >tried to get at a directory that had lower-case letters in its real name. This is rather common. I wound up renaming several subdirectories back to all upper case because I kept getting this error. Since I dont have an InnerDrive for GS/OS 3.0 yet (and the new system recognizes my UDC w/ 3.5" drive as a UniDisk but doesn't install the driver for it (!!)), I have both versions of GS/OS on my hard drive. The old version uses ProDOS v1.7, which doesn't cope with altered version numbers very well... The easiest solution is just to use ProDOS v1.8 everywhere. > --Dave Lyons, Apple Computer, Inc. | DAL Systems -- fadden@cory.berkeley.edu (Andy McFadden) ...!ucbvax!cory!fadden