patm@omepd (Pat Mead) (06/17/88)
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 ***********************************************************
cayz@udel.EDU (James Cayz) (06/19/88)
>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'. It has.... *sigh* I know my way around Resedit and the Mac, but not when I don't have the time to debug the problem.... >.... They all think the 3rd doc is the application now and not MacWrite. That's the way I saw it happen.. Unfortunately, I didn't have the time (nor did the user on the Mac afflicted) to figure out the problem... Copying the file, and trashing the original now made all the other MacWrite docs "Copy of [original file name] document". Fastest thing was to lauch MacWrite manually, open the copy, print it, and then trash it, (also the orginal), and re-type it.... It was faster than hauling out Resedit seeing the bundle bit (if I had noticed it), figuring out to rebuild the Desktop, and all that good stuff Pat figured out on his own... >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. If anyone hears about one, or wants to know if they'll get $10 for writing a shareware utility, please let me know - I'll pay to have this on my Appleshare.. Thanx Pat, for letting me know that something isn't real flakey with that user's hard disk.... James |James Cayz can be found via: USPS: Educational Technology Laboratory, |E-MAIL (ARPA): cayz@louie.udel.edu : 203 Willard Hall Education Building, |PHONE: +1 302 451-6307 : University of Delaware, Newark DE 19716
gagaku@ucscd.UCSC.EDU (23527000) (06/19/88)
I found the same bug--some DA's downloaded from BBS were called "Desk Zap Documents" and double-clicking would not open Font-DA mover. The icon, type, and creator were all correct. My work-around (not knowing about the bundle-bit fix) was to open Font-DA mover first, open these files, and copy their contents to new DA files, then trash the old ones. Next time, I'll try resetting the bundle bit and see what happens. But is it necessary to use ResEdit for this? Seems like DiskTop or several similar small utilities can set/reset all of the various info-bits. Fred Lieberman gagaku@ucscd.ucsc.edu
robiner@ganelon.usc.edu (Steve) (08/18/88)
I have been using finder 6.1 for several weeks now, and I just now noticed a particularly ugly bug. This only happends on my SE not on my MAC II. The bug: If you scroll a finder window down, one of the lines from the upper border scrolls down with the icons as if it's part of the window. This is really annoying and a very ugly bug which I can't under- stand how it got through. I think Apple's getting sloppy. =Steve= P.S. Has anyone got a patch for this or is there a 6.1.0.1 Finder coming out too?
tecot@Apple.COM (Ed Tecot) (08/31/88)
In article <11663@oberon.USC.EDU> robiner@ganelon.usc.edu (Steve) writes: >I have been using finder 6.1 for several weeks now, and I just >now noticed a particularly ugly bug. This only happends on my >SE not on my MAC II. > >The bug: If you scroll a finder window down, one of the lines from >the upper border scrolls down with the icons as if it's part of the >window. This is really annoying and a very ugly bug which I can't under- >stand how it got through. I think Apple's getting sloppy. I just booted a virgin 6.0 on a Mac SE and could not get this to happen. Perhaps you are using some wierd INIT or CDEV. I'd appreciate it if you could narrow it down a little more. If this really is a bug, I'd want to ensure that it gets fixed. _emt
alexis@dasys1.UUCP (Alexis Rosen) (09/02/88)
In article <16352@apple.Apple.COM> tecot@apple.com.UUCP (Ed Tecot) writes: >In article <11663@oberon.USC.EDU> robiner@ganelon.usc.edu (Steve) writes: >>[...] The bug: If you scroll a finder window down, one of the lines from >>the upper border scrolls down with the icons as if it's part of the >>window. This is really annoying and a very ugly bug which I can't under- >>stand how it got through. I think Apple's getting sloppy. > >I just booted a virgin 6.0 on a Mac SE and could not get this to happen. > [etc.] > _emt I haven't seen this in over a year, but I assume he's talking about the same bug I saw. I would only happen when I modified the Finder's LAYO resource. The modification was something like: Use geneva 12 offset icons by -16 vertically I don't think there was anything else I changed. Also, I think the bug only occurred in the two iconic views. ---- Alexis Rosen {allegra,philabs,cmcl2}!phri\ Writing from {harpo,cmcl2}!cucard!dasys1!alexis The Big Electric Cat {portal,well,sun}!hoptoad/ Public UNIX if mail fails: ...cmcl2!cucard!cunixc!abr1 Best path: uunet!dasys1!alexis