steve@mstar.UUCP (Steve Wilson) (01/25/89)
I _know_ this has been discussed before, but of course I lost all my references before I needed them. Apologies to all.. I just updated the system software on my MS Word disk (yes, I haven't bought that hard disk yet) to 6.0.2 from some-older-than-the-hills version. Now, when I double-click on a Word document, I get the dialog about the application being "busy or missing". I seem to remember that this has something to do with bundle bits, but I'm not sure. If anyone can help, I'd appreciate it. Please e-mail or post as seems reasonable. Thanks! -- Steve Wilson, Morning Star Technologies UUCP: ...!{cbosgd, osu-cis, pyramid, sequent, sgi}!mstar!steve Internet: osu-cis!mstar!steve@tut.cis.ohio-state.edu
aa0s+@andrew.cmu.edu (Adel Talaat Assaad) (01/26/89)
Hi, The old Finders were very sloppy about DOCUMENTS having their Bundle bits set. They didn't seem to care one whether the Bundle bit was set. The new ones AREN't!!! In my uninformed experience, they don't like seeing an application and one of its documents with the bundle bit set. Thus in the old version if the bundle bit is set on a document nothing happens, but with the new finder it seems that the finder looks for the first file ( be it a document or the application itself), with the Bundle bit set and having a corresponding icon in the desktop, and JUST says that every other document of the creator belongs to that FIRST document it happened to meet. This seems to be a purely haphazard thing, so you may have things fine and then all of a sudden they go out of whack, say because you rebuilt the desktop and a document with the bundle bit set now preceeds the application in the desktop. One horrible instance of such screw-ups occurs when you have the application on a volume other than the startup, with a document IN the startup volume with its bundle bit set. I've had this happen ove a period of three or four months on my own system. The only solution is to UNSET the bundle bit (Resedit can do it) on the DOCVUMENT that you find listed as the creator in the GET INFO BOX of the "troubled" document species, and then you have to rebuild the desktop.... This will keep trickling on and on until every thing is "cleaned up". Obviously it's best if you could find out all the problem sources in one bout. There may be a TechNote on this subject, but I don't remember, any info anyone? Good luck! A. Assaad CMU Pittsburgh,PA.