[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Walking Icons?



>     This means Finder decided that the icon object list that it was
>walking (probably to update a window with the latest file information) was
>damaged. You're the second person who's reported seeing this, and they
>have both involved file manipulations with 3rd-party utilities. Most
>interesting. I'll have to think about this one. This shouldn't happen,
>but obviously something is causing it in extremely rare circumstances.

I think I was the other guy seeing the message...  I saw it a few times
when I first installed 6.0.1, but I haven't seen it recently.  Kinda
weird.  

I'm getting "Finder needs 300k" ( something like that, or more memory ), or
ftype.apple not found, or a crash which prompts a 40 column text saying
something like "memory trashing problem encountered, software problem (
likely ), hardware problem ( unlikely ) Error: $0308"...  $0308 is damaged
HeatBeat I thought...

Is this a old mesage in ROM or new 6.0.1 message?  I don't recall ever 
seeing this one before 6.0.1.  I've used the RAM test utility that came
with my board, and also AppleWorks GS's RAM test, both tells me my RAM
card is fine.  Any ideas?  I'm almost always running in GNO, and Switch-It!
from GNO, so I guess possibilities are almost unlimited.  :-\

>     The icon object walking code simply checks if the link to the next
>icon references the same icon. This happens if the end link somehow gets
>pointing to a non-existant bank, like $AB. If you fetch any data from
>that bank, or any bank from $80-$DF, which the GS doesn't decode, you'll
>get a read of the last value on the data bus, which was the bank address
>byte (due to the multiplexed nature of the GS address/data bus). 

Ahh...

>    One question. Was the folder that contained the file you were making
>filetype changes to open in a window?

I'll keep my eyes open next time.

-- 
frank m. lin
fmlin@netcom.com