Author Topic: An unexpected error occurred, because an error of type -110 occurred  (Read 19300 times)

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
If you are running OS 9.2 then I'm pretty sure that it has happened to you:
Quote
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
Quote
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?

Offline GaryN

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1053
  • active member
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #1 on: August 08, 2016, 06:56:08 PM »
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.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #2 on: August 10, 2016, 09:36:10 AM »
There are so many people who experience this, that it's probably a glitch in Finder.

Offline DieHard

  • Administrator
  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1686
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #3 on: August 11, 2016, 08:43:03 AM »
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...

Offline geforceg4

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 535
  • i did my time on mac os 9
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #4 on: August 11, 2016, 12:47:17 PM »
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"

Offline GaryN

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1053
  • active member
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #5 on: August 11, 2016, 03:42:07 PM »
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
« Last Edit: August 12, 2016, 08:47:41 AM by DieHard »

Offline geforceg4

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 535
  • i did my time on mac os 9
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #6 on: August 11, 2016, 03:46:08 PM »
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

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #7 on: August 12, 2016, 07:20:08 AM »
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.

Offline DieHard

  • Administrator
  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1686
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #8 on: August 12, 2016, 08:43:43 AM »
also, try this... and let me know if it helps...

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

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #9 on: August 17, 2016, 10:18:53 AM »
I just got a variant of the error (see attachment.)
It's clearly related to the file system.

Offline GaryN

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1053
  • active member
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #10 on: August 17, 2016, 02:06:25 PM »
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.

Offline geforceg4

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 535
  • i did my time on mac os 9
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #11 on: August 17, 2016, 02:08:40 PM »
memory is still involved with reading + writing of files

Offline DieHard

  • Administrator
  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1686
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #12 on: August 17, 2016, 05:05:34 PM »
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 :)

Offline GaryN

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1053
  • active member
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #13 on: August 17, 2016, 05:12:35 PM »
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.

Offline geforceg4

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 535
  • i did my time on mac os 9
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #14 on: August 17, 2016, 05:28:21 PM »
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

Quote
"*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

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #15 on: August 24, 2016, 06:53:39 AM »
I asked my question here in 2011:

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

But they didn't have the answer.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #16 on: August 24, 2016, 07:08:08 AM »
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?

Offline geforceg4

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 535
  • i did my time on mac os 9
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #17 on: August 24, 2016, 07:47:42 AM »
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 ;)

« Last Edit: August 24, 2016, 05:14:19 PM by DieHard »

Offline DieHard

  • Administrator
  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1686
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #18 on: August 24, 2016, 05:16:00 PM »
I think your "Cahnge FInfo" is so cool with the...

Quote
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

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #19 on: August 30, 2016, 06:52:03 AM »
No, I don't need it.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #20 on: August 30, 2016, 06:53:35 AM »
I reduced the disk cache to 2 MB in the control panel. Since then I didn't see the -110 error anymore. (The hard disks have a buffer of 2 MB.)

Offline GaryN

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1053
  • active member
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #21 on: August 30, 2016, 02:24:18 PM »
Well now, wasn't that just too simple!

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #22 on: September 14, 2016, 09:04:52 AM »
I gave Finder 33 MB of memory and chose 32 MB of disk cache and the error is gone.
I suspect that the error is caused by extensions and control panels that don't have a 'sysz' resource.
Then they use Finder's memory without Finder knowing that it has to allocate more memory.

Offline DieHard

  • Administrator
  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1686
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #23 on: September 14, 2016, 09:59:00 AM »
I gave Finder 33 MB of memory and chose 32 MB of disk cache and the error is gone.
I suspect that the error is caused by extensions and control panels that don't have a 'sysz' resource.
Then they use Finder's memory without Finder knowing that it has to allocate more memory.

I'm not gonna say I mentioned it but...

From Diehard
Quote
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

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #24 on: September 16, 2016, 09:37:47 AM »
Well, 10 hours after I wrote that the error happened again.
I think that the first solution was better: reduce the disk cache.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #25 on: September 16, 2016, 09:40:40 AM »
I know a bit more about the error:

1) It happens always shortly after the directory structure was changed.

2) It happens always when clicking in the desktop or choosing something from Finder's menu.

3) I found no function in Inside Macintosh that can return -110.

4) I can actually cause error -110 if I want to.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #26 on: September 16, 2016, 09:42:11 AM »
I wrote a script that will cause error -110.
See picture in attachment.
It shows that the error is returned by an Apple event handler.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #27 on: September 16, 2016, 09:44:33 AM »
The following script stops the error.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #28 on: September 20, 2016, 07:07:33 AM »
I know a bit more about the error.
Some things that Finder can do work only correctly if the files are on the startup disk.
For example, copy a font suitcase to a volume that is different from the startup disk (for example, the RAM disk).
Open it.
Drag the fonts to the desktop.
They VANISH on my computer.
Can someone confirm this?

Offline devils_advisor

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 765
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #29 on: September 20, 2016, 04:29:02 PM »
need to look into that. i need to get more fonts soon

Offline GaryN

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1053
  • active member
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #30 on: September 20, 2016, 06:26:06 PM »
I know a bit more about the error.
Some things that Finder can do work only correctly if the files are on the startup disk.
For example, copy a font suitcase to a volume that is different from the startup disk (for example, the RAM disk).
Open it.
Drag the fonts to the desktop.
They VANISH on my computer.
Can someone confirm this?
Yes. That's what happens. Every time.
BUT… it's not that they have to be on the startup disk.
It's that you can't move them to a different volume OR the "Desktop Folder".

Font handling in ALL Classic Mac OS's was / is nuts. Go back to 68k and you even had to install and uninstall them with an app!  "Font-DA Mover"

I think that part of this is because fonts developed and evolved over time (screenfonts, Postscript, TrueType etc etc.) but they just kept patching and repatching the OS to keep it all working and backward-compatible.

Fonts moved from a different volume to the Desktop the way you describe will disappear into the ether if they're outside of a suitcase. Interestingly enough, make an everyday folder, put them inside and then move them and they're fine. Evidently they just need to be "wrapped" in something.

The OS9 "Desktop folder" which doesn't even appear as a folder in the Finder, exists in some kind of magic place where it can reference stuff from different volumes and more or less keep it together but it's not tolerant at all of loose font files.

Is THIS what started all of the error -110 stuff to begin with? Is it just me or is this all because you're somehow compelled to keep testing the limits of the OS? Understand, I'm NOT trying to be snarky here - I just can't begin to get a grip on what the hell it is you're trying to accomplish that's causing all of this.  Any enlightenment would be helpful and appreciated.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #31 on: September 28, 2016, 09:34:37 AM »
BUT… it's not that they have to be on the startup disk.
It's that you can't move them to a different volume OR the "Desktop Folder".
Not quite correct.
It works if the files are on a Disk Copy image (you can copy between images).
So it depends on:
  • AppleScript
  • disk cache
  • multiple volumes
  • disk driver

Offline GaryN

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1053
  • active member
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #32 on: September 29, 2016, 11:36:08 AM »
I give up. This is pointless.

Offline nanopico

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 722
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #33 on: September 29, 2016, 01:47:54 PM »
Based on everything that is here, it appears that there is a bug in system software somewhere.  More than likely the desktop manager or file manager systems.
The error -110 as noted is memAdrErr  and is defined in MacErrors.h as provided by apple with MPW.
I have no clue what all can return this error, but it is defined with in the enum for the Memory Manager errors
This would likely be cause by a request to the memory manager to reference a pointer that has been disposed of previously by the memory manager.  The bug would be that some method or procedure didn't properly clean up it's pointers or did so before needing to use it in a very specific circumstance that is not common so the actual state of the machine may be difficult to consistently be recreated.


If it ain't broke, don't fix it, or break it so you can fix it!

Offline geforceg4

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 535
  • i did my time on mac os 9
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #34 on: September 29, 2016, 02:53:57 PM »

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #35 on: November 03, 2016, 07:46:19 AM »
Yesterday the error happened like this: I put some items on the desktop.
When I wanted to move them back, I had also selected something that I had created on the desktop. So it complained that one item could not be put back because it was created on the desktop. Then I had error -110 and some items were not put back.

It depended again on AppleScript and file system.

Offline nanopico

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 722
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #36 on: November 03, 2016, 08:05:25 AM »
I would be interested to look into this more.
OS923 would it be possible for you to make an image/clone of your drive and make it available?  This would allow a full view of everything and probably recreate the issue.
If it ain't broke, don't fix it, or break it so you can fix it!

Offline geforceg4

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 535
  • i did my time on mac os 9
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #37 on: November 03, 2016, 05:11:23 PM »
isnt there a logical chance that  - perhaps all your 'mucking about' with the system files of the OS has CAUSED the problem in the first place?

Offline GaryN

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1053
  • active member
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #38 on: November 04, 2016, 01:14:17 AM »
Duh…

Offline IIO

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 2346
  • new to the forums
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #39 on: November 04, 2016, 10:56:46 AM »
Quote
I think that it's caused by my creating folders and moving files and folders very quickly.

that is exactly where i have seen it too - and where my name comes from.

"It is true that the "pre-emptive multitasking" advantage present in OS X can be illustrated by downloading CD-ROM ISOs and rendering chaos theory formulas while simultaneously instant messaging and posting on FaceBook what you ate... but in reality, what did you create?"
- DieHard, random forum troll at macos9lives.com

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #40 on: May 07, 2018, 09:27:11 AM »
Last week I made an alias to the trash. I added this as a launcher to a Malph document. I use this instead of the trash. Since then I experienced not a single error -110.

Offline IIO

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 2346
  • new to the forums
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #41 on: May 08, 2018, 03:49:34 AM »
this error is where my nick once came from. "cant write to file because file is still busy" describes my abuse of keybard and mouse best.
"It is true that the "pre-emptive multitasking" advantage present in OS X can be illustrated by downloading CD-ROM ISOs and rendering chaos theory formulas while simultaneously instant messaging and posting on FaceBook what you ate... but in reality, what did you create?"
- DieHard, random forum troll at macos9lives.com

Offline mrhappy

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1024
  • new to the forums
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #42 on: May 08, 2018, 07:08:08 AM »
this error is where my nick once came from. "cant write to file because file is still busy" describes my abuse of keybard and mouse best.

I like!! ;D  Sounds like my brain in the morning before I've had a few coffees too!! Haha!

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #43 on: August 12, 2018, 01:25:03 AM »
I disabled all my weird extensions and it's still happening. It seemed gone after I removed all extensions which patch PPC or FAT with 68K. When I disabled TSM Fix too the error returned.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #44 on: February 21, 2019, 05:00:13 AM »
I identified the toolbox function which causes error -110. Now I try to log which program is usually responsible. I have to be sure before I announce it.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #45 on: March 06, 2019, 08:10:40 AM »
If your volumes have the same creation date, then the Alias Manager may mistake one volume for another. Then it calls PBSetCatInfoSync with the wrong vRefNum, and it returns -110, which is undocumented, instead of -50. Finder doesn't know what to do with this error code and keeps repeating the same error message.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #46 on: September 25, 2019, 01:53:51 AM »
I'm testing a new solution that is remarkably simple. I patched SystemTask to flush the dirty volumes. I expected this to be slow, but there's no speed penalty. I expect it to be safer than DiskShield, which patches low level write and installs a GNE filter, which looks a bit fishy.

OS 9 flushes the cache once per second. Because I do things quickly, this wasn't fast enough. Programs have to be written to allow SystemTask to be called at least 10 times per second.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #47 on: September 30, 2019, 05:19:20 AM »
I had 5 days without -110 error.

Offline DieHard

  • Administrator
  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1686
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #48 on: September 30, 2019, 07:40:43 AM »
I had 5 days without -110 error.

Cliff, good thing that you don't "give up" on things easily :)

Rewards come to those with tenacity...

Offline macStuff

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1415
    • oldschooldaw.com
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #49 on: October 01, 2019, 07:04:47 AM »
a very annoying error; would love to know what really causes this; + to be able to avoid it;
honestly one of the most frustrating things i can think of other than the btree... but possibly worse because most of the time. u have no idea what it meant.

did you ever try using macos9 with an SSD?
good chance that would solve the issue


Offline mrhappy

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 1024
  • new to the forums
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #50 on: October 01, 2019, 09:35:12 PM »

OS 9 flushes the cache once per second. Because I do things quickly, this wasn't fast enough. Programs have to be written to allow SystemTask to be called at least 10 times per second.

Yeah, who's got time to wait around for that lazy ass, once per second cache... we want 'TPS' (ten per second)... lets get the show on the road!!! ;D

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #51 on: October 02, 2019, 03:46:57 AM »
Then I increased the disk cache to maximum and it works already 2 days without error.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #52 on: October 11, 2019, 08:32:49 AM »
I changed it to leave 1/10 second between 2 flushes.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #53 on: October 18, 2019, 10:09:59 AM »
It still works without error.

Offline Custos

  • Veteran Member (100+ Posts)
  • ****
  • Posts: 125
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #54 on: October 18, 2019, 11:27:07 AM »
Few months back pro tools was giving me this error at random. I disabled tons of plugins and extensions and slowly added them back one at a time to see where the culprit was hiding. Oddly enough I never did pinpoint any conflicting plug or extension. It hasn't happened since. Really annoying and even more so when you are busy recording.
"A mistake is only an error. It only becomes a mistake when you fail to correct it."  -John Lennon

Offline IIO

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 2346
  • new to the forums
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #55 on: October 18, 2019, 05:07:56 PM »
that´s interesting, because PT has a custom disc access method.
"It is true that the "pre-emptive multitasking" advantage present in OS X can be illustrated by downloading CD-ROM ISOs and rendering chaos theory formulas while simultaneously instant messaging and posting on FaceBook what you ate... but in reality, what did you create?"
- DieHard, random forum troll at macos9lives.com

Offline Custos

  • Veteran Member (100+ Posts)
  • ****
  • Posts: 125
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #56 on: October 19, 2019, 05:09:02 AM »
I keep PT on separate drives too. The program the audio files and dae are all on different drives.
"A mistake is only an error. It only becomes a mistake when you fail to correct it."  -John Lennon

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #57 on: October 23, 2019, 07:01:55 AM »
The error happened again, but I must say, I was changing types and creators while Finder was very unresponsive because CW was linking projects in the background.

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #58 on: November 09, 2019, 01:49:45 AM »
I tried a less intrusive solution: if SystemClick has been called, then the next time that SystemTask is called it flushes the dirty volumes. This works, except if NoFinderZoom9 is installed, which suggests that this is the culprit. Apparently, the zooming effect serves a purpose: I guess it gives an asynchronous call from Finder time to complete before it processes the next Apple event. If NoFinderZoom9 is installed, then Finder processes the next Apple event with an invalid directory ID in the parameter block and this causes -110.

Offline IIO

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 2346
  • new to the forums
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #59 on: November 09, 2019, 03:42:19 AM »
have you tried to replace nofinderzoom with something else?
"It is true that the "pre-emptive multitasking" advantage present in OS X can be illustrated by downloading CD-ROM ISOs and rendering chaos theory formulas while simultaneously instant messaging and posting on FaceBook what you ate... but in reality, what did you create?"
- DieHard, random forum troll at macos9lives.com

Offline OS923

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 529
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #60 on: November 13, 2019, 07:12:10 AM »
No, but I remember that there was something that could install a different zoom effect where the rectangle rotates. Do you remember its name?

Offline IIO

  • Platinum Member (500+ Posts)
  • *****
  • Posts: 2346
  • new to the forums
Re: An unexpected error occurred, because an error of type -110 occurred
« Reply #61 on: November 13, 2019, 11:57:21 AM »
i have seen that one with the rotation too but cant remember what it was, i am only disabling them here because i find it distracting.

"It is true that the "pre-emptive multitasking" advantage present in OS X can be illustrated by downloading CD-ROM ISOs and rendering chaos theory formulas while simultaneously instant messaging and posting on FaceBook what you ate... but in reality, what did you create?"
- DieHard, random forum troll at macos9lives.com