An unexpected error occurred, because an error of type -110 occurred

[OS923]

If you are running OS 9.2 then I'm pretty sure that it has happened to you:

An unexpected error occurred, because an error of type -110 occurred

I experience this frequently after emptying the trash or moving something.
The error means "Object not found".
It means that Finder has a pointer to something that has been deleted or moved.

The answer that you find here is wrong:

http://discuss.pcmag.com/forums/702/1000018714/ShowThread.aspx

I'll tell you that I've never had an error message like this in a Windows program:
An unexpected error occurred because an error of type -110 occurred.
It starts occurring when I attempt to access a drive (network or on system) and it's occurred on at least 4 Macintoshes with 9.2 on them. It doesn't cause any harm at first (and I can still save to drives through applications), but eventually it just happens over and over again until you can't do anything but work with the little dialog box, then restart.

I looked it up. It's a memory allocation error. That's all I can find about it. I did a Google search, found next to nothing. The AppleCare Knowledge Base? Well, it told me that it's a memory allocation error.

What else is there to do? It's not related to the software installed on the machine, because it happens with no programs running. It's not NETWORK related, because it happens when we unplug the machine from the network. All unnecessary extensions were also disabled, and sometimes accessing the System folder brings it up anyway.

It comes up randomly, it comes up unexpectedly, and it forces a restart of the machine.
I have found solutions to nearly all the issues that occur on the Macintosh OS 9.2, but some still pop up and some still occur. The administrators are aware of them, but are as clueless about stopping them beforehand as I am. Talking to my immediate colleagues, three of the five sitting in my area have had the issue in the past 6 months.

This is wrong.
It's not out of memory.

Now they say that the error doesn't hurt.
How can I get rid of the error and continue instead of restart?

[GaryN]

I also looked it up and found this:

Under "Storage Allocator Errors"
memAdrErr: address was odd; or out of range

Do I have any better idea what this means than the other guy?………Hell no…maybe.  It sounds disk-related for sure, so immediate thought is a drive issue-possibly about to fail or a really corrupted directory.

I do know this: In 25+ years, I've never once seen that error that I can remember, and I think if it had ever been that big a pain, I'd remember it.

So first: Verify backup is good and (preferably) replace drive. You should have a spare for this exact purpose…you're using "obsolete" hardware, remember.

If that works, cool. Don't believe everything you read from Windoze users.

If not, then:     (See what I'm doing? If we could post graphics, this would be a tree, wouldn't it?)

I also know that: Just about every single time any of my Macs have started throwing un-explainable errors related in any way to memory, it's been a RAM issue - usually an intermittent RAM issue which, of course, makes it that much harder to pin down.

My SOP:

1) Clean & reseat RAM…if no joy, goto 2
2) Run MEMTEST…Result BAD, goto 3…Result GOOD, goto 4
3) Replace bad RAM with known-to-be-good RAM
4) Replace all RAM with known-to-be-good RAM OR go back to 2 as long as you can stand it until you get new RAM

If all of that doesn't work, you're probably in motherboard territory.

[OS923]

There are so many people who experience this, that it's probably a glitch in Finder.

[DieHard]

As far as I know this error is NOT very common.  As POSITIVE error numbers are usually connected with full system crashes and unexpected quits; NEGATIVE error numbers usually less severe and can be tracked down, such as disk is full -34, end of file -39, port in use -97, etc.

Now, errors are usually grouped and for sure -108 in out on memory, so I am guessing -110 is memory related;  Apple was know for not documenting all errors, which is totally ridiculous. So just a few quick questions...

1) What type of Mac are you running

2) Are these errors generated from a modified Finder, or the Original Apple one; if original I would resedit and increase the memory of the finder

3) Is virtual memory on or off

I can't remember if the "MacErrors" gave a complete list of negative errors...

[geforceg4]

i think ive seen this error before
and im pretty sure it was caused by mismatched RAM sticks that had some type of difference between the two..
and i fixed it by replacing the ram with proper matching pairs

OS923 can u post a pic of the ram modules u are using in the machine??
i bet u money they arent the same type/brand


http://www.cwu.edu/~lynnl/nvec.html
this page says that range is for "Storage allocation errors"

[GaryN]

I seem to recall saying all of this 3 days ago…wait, let me look

Under "Storage Allocator Errors"
memAdrErr: address was odd; or out of range

Yep, that was me.

Everybody should have a copy of this - so here.

Modified by Diehard...

Thanks Gary !   This attachment is critical please download, if contains many "hard to find" error codes

[geforceg4]

yes exactly..
"Storage Allocator Errors"

it seems OS923 misinterpreted the meaning of that title to be related to hard drive/file allocation
rather then its true meaning which is storage allocation within MEMORY rather then files.

pretty sure its a memory problem.
ram can go bad over time i believe.
it happens

[OS923]

So just a few quick questions...

1) What type of Mac are you running

G4 MDD 1.25 DP.

2) Are these errors generated from a modified Finder, or the Original Apple one; if original I would resedit and increase the memory of the finder

Original Finder.

3) Is virtual memory on or off

Off because it's 2 GB, 4 identical modules of 512 MB PC3200 CL3 from Kingston.

In the past I had a beige G3/300 with 3 identical modules of 256 MB from Kingston. The -110 error occurred there too.

I think that it's caused by my creating folders and moving files and folders very quickly. I paid attention to it. If I wait 1 second after moving things before I do it again, then the error doesn't happen.

[DieHard]

also, try this... and let me know if it helps...

if original I would resedit and increase the memory of the finder

[OS923]

I just got a variant of the error (see attachment.)
It's clearly related to the file system.

[GaryN]

So first: Verify backup is good and (preferably) replace drive. You should have a spare for this exact purpose…you're using "obsolete" hardware, remember.

Maybe this is just too simple, but this is how you troubleshoot stuff my friend. You swap in a known-to-be-good part, system, subsystem, whatever and eliminate that entire area all at once. If you're determined to believe that Apple produced gazillions of computers with a never-corrected defect in the operating system instead of something as simple as a failing drive, even though HDD's are the single most failure-prone component in any computer, you're hopelessly lost in the forest.

[geforceg4]

memory is still involved with reading + writing of files

[DieHard]

So please humor me and reduce the RAM to exactly 1 GB (with virtual memory turned off) and run it like that for a while

[GaryN]

memory is still involved with reading + writing of files

So is your finger from clicking the mouse. The question is: whattaya gonna test first? You have to actually identify the problem in order to fix it.

DieHard also has a practical, do-able test that should be done.

I laid out the whole troubleshooting procedure two weeks ago. Until 923 actually starts testing something, you're all going to be just speculating in the dark.

[geforceg4]

So please humor me and reduce the RAM to exactly 1 GB (with virtual memory turned off) and run it like that for a while

maybe there is a reason why the MDD's technical specs mentioned to use less than 2gb of ram if booting mac os 9

"*This system can support up to 2.0 GB of RAM, but can only use 1.5 GB while booting MacOS 9 (less than 1.0 GB per application)." -- http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_1.25_mdd.html

[OS923]

I asked my question here in 2011:

https://discussions.apple.com/thread/3255579?tstart=0

But they didn't have the answer.

[OS923]

Here's a useful answer:
https://discussions.apple.com/thread/402593?start=0&tstart=0

If you make many changes to the directory (for example, by copying or renaming many files), then the OS can get behind in updating the directory. If you attempt an action (for example, moving files or emptying the trash) before the directory is updated, then it will complain with the -110 error.

In other words: when you copy or move or delete files then it doesn't flush files or volumes, and it can get behind in updating the directory.

I improved this with my "Flush within a second" extension, but it's still not good enough.

How can I see that the OS gets behind in updating the directory, that the cache needs to be flushed urgently before I continue with something else?

[geforceg4]

perhaps it is caused by you trying to do things too quickly..
perhaps u are super-humanly fast with your drag + drop!

why are you using an old mechanical hard drive instead of SSD or compact flash?
because if the -110 error is caused by lack of speed in updating the file system - u know what will fix that?
SSD. its a great new technology wherby harddrives require no moving parts = faster write/read access
u should try it - gary told u - replace the drive
try it , fix your problem, move on to bigger fish

[DieHard]

I think your "Cahnge FInfo" is so cool with the...

choose type and creator by clicking on an icon.

I am assuming you are not putting that back into it

https://www.gangstalking.eu/os923/AlgHoeHetAllemaalBegon.htm

[OS923]

No, I don't need it.