hodas@eniac.seas.upenn.edu (Josh Hodas) (03/31/88)
I recently ran into a queer thing on my system. After transfering the contents of a folder to various other folders I attempted to toss the now empty folder. The Finder refused, saying it was busy/locked, though getinfo returned that it had 0 items in it. When I looked at it in Disktop and MacSnoop they each reported that the folder contained, now get this, "-1 items". DiskFirstAid and Disk-Express both found no fault with my disk. After a couple of weeks of just letting it stay there, I finally deleted it by putting a copy of an application in it and then trashing it. Finder agreed without a complaint. (It did not even ask if I really wanted to delete the application). Any Thoughts? (NB MacII, 2 meg, Apple internal 40Meg) ------------------------- Josh Hodas (hodas@eniac.seas.upenn.edu) 4223 Pine Street Philadelphia, PA 19104 (215) 222-7112 (home) (215) 898-9515 (school office) ------------------------- Josh Hodas (hodas@eniac.seas.upenn.edu) 4223 Pine Street Philadelphia, PA 19104 (215) 222-7112 (home) (215) 898-9515 (school office)
cooper@thor.ucsd.edu (Ken Cooper) (04/01/88)
In article <3845@super.upenn.edu> hodas@eniac.seas.upenn.edu.UUCP (Josh Hodas) writes: >I recently ran into a queer thing on my system. After transfering the contents >of a folder to various other folders I attempted to toss the now empty folder. >The Finder refused, saying it was busy/locked, though getinfo returned that >it had 0 items in it. I had this same problem, though I didn't look into it as thoroughly as you. Out of desperation (I was working on a friend's machine at work, and didn't want to leave tracks), shooting in the dark, I placed a file in this folder, and then finder had no problem with it. I was a happy camper. I'd also be interested in a clarification of this. Ken Cooper ARPA: cooper%cs@ucsd.edu UUCP: ...!ucsd!sdcsvax!cooper COMPUSERVE: 71571,407
gillies@uiucdcsp.cs.uiuc.edu (04/01/88)
I had a more amusing bug. I printed a document in MS-Word, then
returned to the finder. I then option-1/2 ejected the SE's floppy
(HD+floppy SE). But the icon was still on the screen, so I dragged it
to the trash. The Mac complained, saying "Please Insert Your Floppy
Disk xyz". I then inserted it, the SE wrote on it, and the icon
disappeared into the trash.
BUT my floppy was still in the machine! It hadn't been ejected
(properly) So I hit option-1/2 again to get it out. The disk ejected,
and then a dialog appeared with the real shocker:
"Please insert the disk HD-20 SC"
I scratched my head and rebooted the sick! sick! sick! machine.
Don Gillies {ihnp4!uiucdcs!gillies} U of Illinois
{gillies@p.cs.uiuc.edu}jv0l+@andrew.cmu.edu (Justin Chris Vallon) (04/06/88)
How about this one:
Please insert the disk:
RamDisk
Not a chance...
-Justinack@eleazar.Dartmouth.EDU (Andy J. Williams) (04/08/88)
In article <8WKQ4ZI1DU-0QO008d@andrew.cmu.edu> jv0l+@andrew.cmu.edu (Justin Chris Vallon) writes: >How about this one: > > Please insert the disk: > RamDisk > >Not a chance... > >-Justin This actually is a RamDisk "attribute" which is documented. I haven't read it in a while but I believe it said something to the effect If you try to drag the RamDisk to the trash, it will screw things up. The first time, nothing will happen, the next... poof... Don't try this at home. -Andy Just say fieyrnt. -- Andy J. Williams'90 |_ /| ACK! |BITNET: ack@eleazar.dartmouth.edu HB 509 Dartmouth Clg|\`o_O'Systems|UUCP:{ihnp4,decvax,linus}!dartvax!eleazar!ack Hanover, NH 03775 | ( ) |DISCLAIMER: You better like my opinions, 603-643-7727 | U --ACK! | my mother can beat up your mother...
jnp@daimi.UUCP (J|rgen N|rgaard) (04/12/88)
In article <8WKQ4ZI1DU-0QO008d@andrew.cmu.edu> jv0l+@andrew.cmu.edu (Justin Chris Vallon) writes: >How about this one: > > Please insert the disk: > RamDisk > >Not a chance... Isn't it the driver for the ramdisk that is responsible for not ejecting it ? -- Regards J|rgen N|rgaard e-mail: jnp@daimi.dk -------------------------------------------------------------------------------
ephraim@think.COM (ephraim vishniac) (04/14/88)
In article <1415@daimi.UUCP> jnp@jupiter.UUCP (J|rgen N|rgaard) writes: >In article <8WKQ4ZI1DU-0QO008d@andrew.cmu.edu> jv0l+@andrew.cmu.edu (Justin Chris Vallon) writes: >>How about this one: >> Please insert the disk: >> RamDisk >>Not a chance... >Isn't it the driver for the ramdisk that is responsible for not >ejecting it ? There's a field in the drive queue element which indicates (among other things) whether the drive holds an ejectable medium. Generally, Mac software is pretty casual about observing this flag. _Eject, for example, doesn't check it. Instead, you're supposed to check it *before* trying to eject a disk. Fortunately, the standard file dialogs do check it, so the problem doesn't come up too often. A well-written ramdisk needs several lines of defense. (A poorly written one, like the atrocity that comes with Aztec C, hasn't got any defenses at all.) First, it should set the "not ejectable" flag. Second, it should post a disk inserted event whenever it receives an eject call. Third, it should check periodically to see whether it's mounted (i.e., whether it's volume is on-line in the vcb queue), and post a disk inserted event if it's not. Some programs are incredibly stupid about ejecting disks. Old versions of Microsoft Multiplan were the worst. They expected to find the key disk in the internal floppy drive. If it wasn't there, they ejected *the current system disk* (not the floppy) and put up a modal dialog asking for the key disk. They didn't care whether the disk that they "ejected" was a ramdisk, hard disk, or floppy, they just blew it away. Ephraim Vishniac ephraim@think.com Thinking Machines Corporation / 245 First Street / Cambridge, MA 02142-1214 On two occasions I have been asked, "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?"
tom@ronin.cc.umich.edu (Tom Wuthrich) (04/15/88)
Some Folks out here have seen a bug where the mac SE
running all the current system software will not let the
mouse do a double ckick anymore.
Has anyone sceen this or have any ideas. I know this is vague
but its all i have.
thanks.
grina@soleil.UUCP (Pete Grina) (04/15/88)
In article <469@mailrus.cc.umich.edu>, tom@ronin.cc.umich.edu (Tom Wuthrich) writes: > Some Folks out here have seen a bug where the mac SE > running all the current system software will not let the > mouse do a double click anymore. This has happened to me several times. I don't remember which product caused this problem, although I certain it was public domain (I just got my shipment of goodies two weeks ago.) If I run into it again, I'll jot down the name of the guilty product. When this happens, I just restart the MAC. Pete, you're scum
rmf@actnyc.UUCP (Robert M. Fuhrer) (04/19/88)
In article <278@soleil.UUCP> grina@soleil.UUCP (Pete Grina) writes: >In article <469@mailrus.cc.umich.edu>, tom@ronin.cc.umich.edu (Tom Wuthrich) writes: >> [...] the current system software will not let the >> mouse do a double click anymore... > >When this happens, I just restart the MAC. > In the editorial section of the April 1988 issue of MacTutor, the problem is described as being caused by applications that improperly mask out (disable the reporting of) mouseUp events. (Apparently, the Finder needs these events to detect double-clicks.) When the program exits, the Finder does not reset the event mask, and so never sees the mouseUps... -- The Foundation for Unmitigated Sillyness uunet!actnyc!rmf Department of Redundancy Department City of Kansas City, Kansas