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

[OS923]

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.

[IIO]

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.

[mrhappy]

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!!   Sounds like my brain in the morning before I've had a few coffees too!! Haha!

[OS923]

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.

[OS923]

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.

[OS923]

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.

[OS923]

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.

[OS923]

I had 5 days without -110 error.

[DieHard]

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...

[macStuff]

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

[mrhappy]

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!!!

[OS923]

Then I increased the disk cache to maximum and it works already 2 days without error.

[OS923]

I changed it to leave 1/10 second between 2 flushes.

[OS923]

It still works without error.

[Custos]

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.

[IIO]

that´s interesting, because PT has a custom disc access method.

[Custos]

I keep PT on separate drives too. The program the audio files and dae are all on different drives.

[OS923]

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.

[OS923]

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.

[IIO]

have you tried to replace nofinderzoom with something else?