mount volume crashing the machine when there is no network.
mount volume crashing the machine when there is no network.
- Subject: mount volume crashing the machine when there is no network.
- From: James Reynolds <email@hidden>
- Date: Fri, 5 Jan 2001 12:50:54 -0700
I am having a lot of trouble with the mount volume command that comes
with the Standard Additions. Here are the details.
My crash-test script:
try
mount volume "afp://myUsername:email@hidden/My Volume"
on error mes
display dialog mes
end try
Ok. I know the following test is kind of a stretch, but it is a
problem that I bump into every now and then and might help explain
other so-far-non-duplicatable crashes I get with the "mount volume"
command.
I am running OS 9.0.4, AppleScript 1.4.3, AppleScritpLib 1.4, and
Standard Additions 1.4.2 (which comes with 1.4.3 and which has the
mount volume command). Whenever I unplug the ethernet cable and
immediately run the above script (from the Script Editor 1.4.3), the
box crashes with this message:
"Sorry, a system error occurred. 'Script Editor 1.4.3' error type 10
-- restart"
or
"The application 'Script Editor 1.4.3' has unexpectedly quit, because
an error of type 2 occured..."
As an appliation/classic applet, I get: "The application "mount test
app" has unexpectedly quit, because an error of type 3 occured..."
Sometimes the "on error" catches it and gives me an error 3162. The
script-as-application catches the error more often than Script Editor.
I have tried this on a Beige G3/300 with 128 ram and a G4/450 MP with 320 ram.
The crash will only occur in that brief moment right after the
ethernet cable is unplugged that the mac thinks there is still a
network connection. So on the faster G4, the window of
crash-opportunity is much smaller than on the G3. Either way, I have
consistently achieved this crash over and over.
I was going to try this on a G3 b/w in a different building with a
totally different setup (someone else's machine) while I was
connected remotely using Timbuktu Pro (my friend was going to unplug
the ethernet cable). But, when I ran the script to make sure the
script worked under "good circumstances," (i.e. with ethernet cable
plugged in) it froze the whole machine. So I know something is wrong
here...
Anyone have any ideas?
--
Thanks:
James Reynolds
University of Utah - ACLIS
Academic Computing and Library Information Services
email@hidden
801-585-9811