🚀 go-pugleaf

Sorry if this is a repost. From what I could tell my first 
posting from another machine never made it anywhere. 

In using the new System release 6.0 I've found possible bug
that may have to do with some of the new features. But this
bug could bite someone thats not a 'power user'. 

When downloading a file (the new version of DeskZap) from a local
BBS I found that when I put it in a folder with the rest of my 
DA's that upon opening the folder again all the DA's no longer
had the normal suitcase icon and much worse when double clicked
wouldn't lanch the Font/DA Mover. I thought a classic case of a
corrupted desktop and proceded to rebuild it. Guess again rebuilding
failed to help at all. But if I used any other system release it
worked and moving the file around was fine. Just with the new 6.1
Finder did this problem occur and ALLWAYS with 6.1. Upon looking
closer I found that all the DA's said there were not Font/DA Mover
documents but there were now all DeskZap documents.

Anyway to make a long story short I found that somehow the DeskZap
DA I downloaded had its bundle bit set. I've seen this happen many
times with files on BBS's, usually it's a MacWrite file that has it's
bundle bit set. In past versions of the Finder this didn't matter
or hurt you any. But now with Finder 6.1 if you by some accident or
BBS quirk causes the bundle bit of a document to be set and you copy
this file to a new disk the Finder will place an entry in the
desktops APPL(?) resource so that any document of this same kind
now thinks it belongs to the new document and not the real Application.

A few of us tryed for fun putting 2 MacWrite documents in a folder on
a blank disk. Then we put MacWrite in another folder. Everything is
fine. Now we set the bundle bit of new MacWrite doc and copyed it into
the same folder with the other MacWrite docs. Close the folder and then
reopen it. Voila all the docs are of the kind 'Name' of the 3rd one
that has it's bundle bit set. They all think the 3rd doc is the
application now and not MacWrite.

The solution? Reset the bundle bit? Not enough since the desktop is
still bad. The best way is to clear the bundle bit in Resedit and edit
out the desktop APPL entry for this document. You can also do it with
out editing the desktop file by clearing the bundle bit and then
rebuilding the desktop. This will of course loss all comments in the
desktop.

This seems to me to be a bad bug in the New Finder 6.1. Apple may have
made a change in the Finder for one of the new features but I find the
side affect to be very harmful. If your not a 'poweruser' and are
afraid of such things as resedit, which I think is a majority of the
Mac users this can be deadly. The big question is what is apple going
to do about it? I think they should fix the Finder. At worst case they
should create a utility to find inproper documents and fix them and the
desktop file. Have other people seen this bug yet?

***********************************************************
usual disclaimers---	

Patrick Mead			ogcvax!inteloa!omepd!patm

***********************************************************