Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[OS923]

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

[GaryN]

Well now, wasn't that just too simple!

[OS923]

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.

[DieHard]

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

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

[OS923]

Well, 10 hours after I wrote that the error happened again.
I think that the first solution was better: reduce the disk cache.

[OS923]

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.

[OS923]

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.

[OS923]

The following script stops the error.

[OS923]

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?

[devils_advisor]

need to look into that. i need to get more fonts soon

[GaryN]

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.

[OS923]

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

[GaryN]

I give up. This is pointless.

[nanopico]

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.

[geforceg4]

I give up. This is pointless.

LOL

[OS923]

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.

[nanopico]

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.

[geforceg4]

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?

[GaryN]

Duh…

[IIO]

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.