Re: NS3.0 FloppyDisk Eject Problem

Thread View: comp.sys.next.sysadmin

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Robb Aley Allan Mon, 28 Sep 1992 16:21

#1589

Author: Robb Aley Allan
Date: Mon, 28 Sep 1992 16:21

30 lines
1718 bytes

From: rallan@helical.com (Robb Aley Allan)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: NS3.0 FloppyDisk Eject Problem
References: <1992Sep23.170928.6666@aplcen.apl.jhu.edu>
Reply-To: rallan@helical.com

Tim Pugh writes
   craigh@domino.sps.mot.com (Craig Hansen) writes:
   
   >In article <1992Sep17.195148.13949@aplcen.apl.jhu.edu> tim@aplcen.apl.jhu.edu  
   >(Tim Pugh) writes:
   >> Is anyone else experiencing a problem with floppy disk ejection.  To be
   >> more precise, I automount a DOS formatted disk, transfer certain files
   >> to the hard disk (copy).  When done I select Disk from the main menu
   >> of WS Manager and find that in the submenu, the eject command is inactive;
   >> i.e., it is grey (not balck).  Is this a bug or simply an installation
   >> problem?  Thanks for your response.
   
   I have since found that the problem is related to the running of Engage!
   Apparently a bug in NS3.0 causes this behavior when Engage! is running.


Don't think so. People are reporting this all over the place. I have the same problem,  
and don't run Engage. It affects all removable disks (ODs, floppies, CDs).

-- 
Robb Aley Allan, The Gulfstream Group
220 Sunrise Avenue, Palm Beach, FL 33480
voice: 407/ 832-4013   email: rallan@helical.com
Co-founder/director, Gotham Users of NeXT (GUN)

Re: NS3.0 FloppyDisk Eject Problem

#1613

Author: Ben E. Cline
Date: Tue, 29 Sep 1992 15:29

7 lines
594 bytes

I had the floppy eject problem when I was autolaunching co-Xist and 
AltDock v. 2.  When I stopped autolaunching, the problem went away.
I didn't take the time to verify which (or both) of these was causing
the problem.

Benjy
Virginia Tech Computing Center

Re: NS3.0 FloppyDisk Eject Problem

#1716

Author: Bob Peirce #305
Date: Thu, 01 Oct 1992 17:05

19 lines
1458 bytes

In article <1992Sep28.162115.6323@helical.com> rallan@helical.com writes:
>Tim Pugh writes
>   
>   I have since found that the problem is related to the running of Engage!
>   Apparently a bug in NS3.0 causes this behavior when Engage! is running.
>
>
>Don't think so. People are reporting this all over the place. I have the same problem,  
>and don't run Engage. It affects all removable disks (ODs, floppies, CDs).
>
It happens when programs "like" Engage are autolaunched.  Programs that
pick up icons in some way have this problem.  I had it with Engage!.  I
have to start it manually now.  I suspect AltDock and the other dock
extenders have the same problem.  I don't know what other types of
programs do the same things with icons, but autolaunching them could
cause the problem.
-- 
Bob Peirce, Pittsburgh, PA         rbp@investor.pgh.pa.us         412-471-5320
venetia@investor.pgh.pa.us [NeXT Mail]  !uunet.uu.net!pitt!investor!rbp [UUCP]

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads