nCity Legacy Errors

Presented here are some of the more common error messages, their meanings and (hopefully) solutions, in order of severity. But first, a few words about error messages in general.....
From a programmer's point of view, the easy thing to do is create a general purpose, one-size-fits-all dialog box containing some meaningless technobabble, then put it onscreen whenever there might be a potential problem. It prevents the program from crashing, plus you can use the same message over and over again.
I mention this because I've watched more than one former PC user handle error messages: The very instant a box appears onscreen, they're pounding that Return key to make it go away - without even a thought of reading what it has to say.
Apple has always gone to great lengths to identify specifics in Mac error messages, including the probable cause, and will even suggest a solution whenever possible. (These should not be confused with errors originating from within an application, which might be a different story.) When the MacOS puts up a message, it _always_ has something to say, even technical errors that report nothing more than a code number; this is usually the OS choking on an application program's internal error. The resulting error code still has a specific meaning, but these may be too lengthy and technical to fit within a dialog box or error message. Read those error messages! And write 'em down if necessary.

Disappearing, renamed and duplicate files: Some common problems involve "losing" files (i.e., not knowing where they were saved or copied to), accidentally renaming files, and creating multiple copies of multiple copies. In the example (right), a new document named "Yuma" is about to be saved into a folder named "Arizona." The first time you Save a doc, and every time you Save As (making a new copy), this dialog box appears. Name the document, note (or change) its destination, then click "Save." Accidentally renaming a file is easy to do, too (which will make it impossible to find by name). Clicking a file's name - instead of its icon - selects the name for editing. If you're not paying attention, your next keystroke will replace that file's entire name. In the first example shown (to right), the file named "HAL Y2K" has been selected by clicking its icon (first), compared to clicking its name (second illustration) where the name is highlighted for editing and cursor has changed from an arrow to an I-beam (text) cursor. At this point, the next keystroke will replace entire "HAL Y2K" file name. In a List view, accidental changes are even easier since the icon's size is reduced, making a much smaller target as compared to file's name. Housekeeping and organization is a must, especially on today's huge hard drives. If you have copies of copies of copies scattered all over your drive, you need to check out the Prevention section below - and be ready to do some serious housecleaning.	Save (Save As) dialog box showing document's destination. Editing file names in Icon view (top) and in List view.
Downloading files: This isn't exactly an error, but it leads to a lot of confusion (as does the next entry). When you download a file, it goes to the location set in your browser's preferences; that location _should_ be your desktop. As many as three files may appear when downloading: First will be an encoded _and_ compressed file (usually having a filename extension of .hqx or .bin - see examples top row, right). If your browser is configured properly, the StuffIt utility will automatically produce the second file, a decoded but still compressed version of the first (second row). StuffIt will then produce the third file, decoded, decompressed and ready to use. The first file may disappear on its own (or might not appear in the first place); the second (compressed) version should be saved somewhere as a backup; and the third should be dragged into your hard disk for use.
Installers: The folder you just downloaded might contain an "Installer," designed to put software components in their proper places within your System (often requiring a restart after installation completes). Launching the installer icon is all you need to do; the installer does the rest. Installers (by law) must include an installer log (text file, far right) and usually include a "ReadMe" file which is best read _prior_ to running the installer.

Can't open doc, application not found: One of two conditions can cause this message: Either it is literally correct and you are trying to open a foreign document without its application, or you need to rebuild your desktop. To rebuild the desktop, hold down Command+Option keys during startup (also see Prevention section). Odds are good that you can still open that orphan doc within some other app that you _do_ have onboard, and here's an easy way to find out: Drag the doc's icon over your app icons until one hilites. Since this example (right) is probably a text doc, some other text app should open it. In this illustration, the "US Constitution" doc is dragged over SimpleText first, which does not hilite; SimpleText can't open it. Dragging the doc over BBEdit _does_ cause BBEdit to hilite, indicating it will open within BBEdit. Releasing the mouse at this point will launch BBEdit and open the doc. (This operation does not move icons from original locations.)	Maybe that document has been severely damaged.....? Dragging a foreign doc in search of an app that can open it.
File too large to open: SimpleText has survived all these years by being..... simple. It's primary function is to handle "ReadMe" docs included with most software. This SimpleText message is proof that it can't handle anything over 32K. Also: A similar message (from the OS) will appear when trying to open any file that requires more memory than is allocated to its application (see above).	SimpleText pressed beyond its limitations.
Finder needs attention: When something requires attention it usually means trouble, and this Finder-generated message is no exception. You just attempted to do something that couldn't be done (illegal instruction), and switching back to the Finder will tell you what went wrong and why.
Insufficient memory: (also see Type 1, Type 2 errors below) Unlike the previous error message generated by the Operating System, this one (right) originates from within an application. Many apps simply freeze when they run out of memory, losing everything you've done since the last time you saved the file, and possibly creating a Type 1 or Type 2 error from the OS (also see below). Well designed apps will check available memory prior to executing certain commands, giving you a chance to save your work. Take it! Then assign more memory to the application using the Mac's unique memory allocation. Here's how: First, you must quit the application before adjusting its memory. Find the app's icon in your hard drive and select it (one click). In the illustration (right) the application named "HyperCard" has been selected and is hilited. Next, choose Get Info from the File menu and select Memory from the Get Info submenu, as illustrated. The resulting window shows the app's name, version and kind (app), then you will see three fields (boxes) under "Memory Requirements," two of which may be edited. (All applications have memory allocation available since it is a function of the MacOS.) Suggested Size cannot be changed. It is the amount of memory required to by the application to operate properly. Minimum Size may be the same or less than the suggested size; if you have memory to spare, you can bump it up to match the suggested size. (If you set it to zero then click another field, it will be reset to the app's default setting, as will the Preferred Size field.) Preferred Size is the field we're after. This is where you can add more memory and eliminate some of those memory errors. The amount of memory you may allocate to a given app depends on (at least) three factors: The amount of installed RAM you have in your machine. Your work habits regarding the number of apps you typically have open simultaneously. The size and type of files you will be working on with the application you are adjusting (sound, movie and photo files can be quite large). NOTE: Memory specifications are in kilobytes (K). The default Preferred Size for the application shown here was 8667K; I've added 2 megabytes (2048K), so the new Preferred Size is now 10715K, as shown. Don't worry about the exact numbers you enter into these fields - I could have added 2000 instead of 2048, or entered an even 10000, it doesn't matter - the app will round-off your entry if it needs to. Use the Mac's memory allocation judiciously. To see how much memory an open/active application is using, switch to the Finder and look at the first menu item under the Apple menu, "About This Computer."	An application's out of memory warning. Select app, then open File menu -> Get Info -> Memory The Get Info's memory window.

Cannot Shutdown: Here's a weird one..... especially when there's nothing running. It can cause what's known as a "closed, locked loop" with no way out except to shutdown the hard way. In this case, the culprit was a printer driver, but it could've been most anything else running unobtrusively in the background. It's harmless, intermittent, and - to my knowledge - rare. (I've yet to see it when there's actually a program open in the Applications menu.)	Shutdown, OK, shutdown, OK, shutdown, OK.....
Empty box with ">" character: It looks like a dialog box, but isn't. Called a "programmer's window," it is activated by an obscure key combo, and its function is to interrupt any ongoing process to give the programmer a chance to modify code. If you don't have any programming utilities onboard, you'll probably never see it. If you do, typing a "g" into the box will make it go away, no harm.	The Programmer's Window.
Huh? This "Virus Transfer" (?!) progress bar only appears on the 4th of July, and only when using a Mac to save the world from invading outer space aliens. The movie was Independence Day ID4 (1996, 20th Century Fox). It starred a PowerBook 5300 (with Jeff Goldblum in a supporting role), and featured a cameo appearance by the notorious Hal 9000.
Type 3 error (types 1, 2 in next section): Browsers seem to be the predominant victims of Type 3 errors. I got this one by trying to print from a web site that wanted me to log on first. The official explanation for Type 3 is that the URL Access Extension needs to be updated (2.3 or later), but mine is the newest version. This error will promptly bring down whatever pre-OSX browser you might be using, and may prevent it from launching again without a restart.
Type 10 error: Application tried to execute an instruction that does not exist (unimplemented trap). Often a result of running newer software on an older CPU that cannot support it.

Type 1 and Type 2 errors: If you've ever worked all day and long into the night on some complex project, only to encounter this message and watch helplessly as all your hard work vanishes into oblivion, you know how important it is to Save often. (Your file isn't written to disk unless you Save it; until then, it remains in RAM where it can easily be erased.) You've run out of memory, the program has quit, and the OS is telling you what happened. Add more RAM and/or allocate more of what you have to the app(s) you're using (see "Insufficient memory" above). And remember to save your work frequently by using Save (File menu) or typing Command+S.	Good advice, even if it is too late. Save your work often!
Freeze (or hang) on startup: Possible Extension or hardware conflict. Try holding down the Shift key during startup (bypassing all extensions). If you get to the desktop, see section above under System Settings on the Extension Manager. If using the Shift key doesn't help and/or the desktop never appears, power down and disconnect all peripheral devices, then try again.
Blinking question mark on startup: Your Mac cannot find an Operating System. Restart from your MacOS CD by holding down the "C" key during startup. Make certain your startup disk is selected in the Startup Disk control panel. Try running Disk First Aid on the hard drive from your MacOS startup CD (DFA is in the Utilities folder) and see if it can fix your drive. If your HD does not appear on the desktop, or Disk First Aid can't fix the problem, your next concern is to try and recover your data from the hard drive. This may or may not be possible, depending on extent and type of damage. See Service section for information regarding data recovery.
Unusual startup sound: Your Mac executes a hardware diagnostic on every startup, and the sound you normally hear indicates everything is okay. If you hear anything other than its normal startup sound, there has been a hardware failure. It might be the hard drive, a RAM problem, the video board, power supply, or any number of other things. If anything appears on the screen, copy it down and take it with you; the machine needs to go to the shop.	This is a QuickTime sampler of ugly startup sounds. These usually indicate a hardware failure on startup.
Gray screen: Try starting up from the MacOS CD (see Blinking question mark, above). If that doesn't work, turn off the machine, disconnect its power cord, strip it of everything that's not absolutely necessary (including PCI cards), and try again. If that doesn't help..... it needs diagnostics.
Crashes and the Bomb: A genuine, bonafide system crash is as spectacular as it is ugly. It might last a few seconds and briefly look something like the photo to the right, but you'll have no doubt that the machine is having a complete and total nervous breakdown. Fortunately, these are extremely rare. Instead, you might see a bomb notice with a restart button - or not - but there's usually no mystery as to cause; the first suspect is the last thing installed. This is one reason why hardware and software installations should always take place one-at-a-time, making certain everything is okay following each individual installation.	Freezes are far more common today than crashes ever were, but not nearly as entertaining.
"This program cannot run on your computer." (G4 Macs only.) Applies to retail OS9 install CDs and all OS9 updates (9.0 thru 9.2.2) when attempting to install/update OS9 on a G4 Mac that has previously been run under OS10.3+. While this message is valid for very old Macs that cannot run OS9, it also appears on some G4s that can, in fact, boot from OS9. Regardless of hard drive condition or contents, this message appears immediately upon launching the OS installer (which, by the way, also interferes with burning an OS9 startup CD). Workarounds involve avoiding use of the installer: Drag-and-drop a preconfigured System Folder from another volume, or restore your OS from a backup. G3s machines are not affected.	This OS9 Installer message may appear erroneously on G4s.

nCity Home..........Solutions..........Support..........Technical..........Services..........Courses..........Links..........nCity Forum