Mathematica crashed -- where did my notebook go?
Bob F
of course everything I had done is gone. Is there any temporary file
or anything still left on the disk that contains anything of what I
was working on at the time of the crash? I tried to do a bit of
investigating, but could not see any open files that exist while
working on a new notebook, so where does Mathematica put everything I
type into a notebook until I save it?
If it doesn't write anything to a file - why not? My gosh, this
happens often enough to people all over the world, that I would think
that Wolfram would have some sort of recovery mechanism built in, but
I haven't found anything so far. How many times have customers asked
for something like this? How many people think the same thing when
this happens? My guess is a quite a few.
So Wolfram -- add this to your list of things to put in the next
version -- your customers would truly appreciate not having to
recreate that program they had been working on for a couple of hours
when the crash occurred and they very quickly tell themselves -- Oh
CRVPPPPP!!! WHY DIDN'T I SAVE THAT FILE!!!!!
Anything would be better than nothing -- why not use the disk to write
the new notebook contents to while it's being developed. Yes I should
have known that a crash was imminent, but my crystal ball is in the
shop getting a new LED display installed ;-)
If this has happened to you and you wished that Wolfram had some sort
of recovery mechanism, please add your 2 cents to this post and let
Wolfram know how important, we the customers, think this is (or
isn't).
-Bob
ps -- this was on a Mac OS X 10.5.6 system with Mathematica version
7.0.1 if it matters
David Bailey
I totally agree - this and an infinite undo would make Mathematica a lot
more friendly. My impression is that since 6.0, frontend crashes (which
destroy unsaved notebooks) have become more frequent - presumably
because of all the extra complexities associated with the dynamic mechanism.
David Bailey
http://www.dbaileyconsultancy.co.uk
Sjoerd C. de Vries
I feel your pain. Perhaps NotebookAutoSave partly meets your
requirements. It lets your notebook save after each evaluation.
Cheers -- Sjoerd
Helen Read
>
> My impression is that since 6.0, frontend crashes (which
> destroy unsaved notebooks) have become more frequent - presumably
> because of all the extra complexities associated with the dynamic mechanism.
This semester I saw students repeatedly lose all their work when they
tried to save a file that had RevolutionPlot3Ds in it. Sometimes the
front end would crash while they were in the middle of working (as soon
as they made a RevolutionPlot3D), but what was far worse was that it
would crash whenever they tried to save the file.
I saw this twice this semester, first when we were doing volume for
solids of revolution (7.0.0 at that point), and again when we did
surface area for surfaces of revolution (7.0.1 by then). Moving to a
different machine and saving to the hard instead of the network did not
help any, nor did downloading a fresh copy of the file and starting
over. I finally told the students who were having the issue not to make
the revolution plots until they had everything else finished, then make
sure the file is saved, *then* do the plots but delete the output before
they save again. Futzing around with this probably doubled the time it
took them to complete the assignment.
The crashing problem only affected a couple of students, and I have no
idea what was different for them. I have not been able to reproduce it
myself, but I did witness it when it happened to the students.
--
Helen Read
University of Vermont
AES
David Bailey <da...@removedbailey.co.uk> wrote:
> My impression is that since 6.0, frontend crashes have
> become more frequent - presumably because of all the
> extra complexities associated with the dynamic mechanism.
If true -- and seems to me this is a reasonable hypothesis -- there
might be a lesson here for the "all in one" (with "all" meaning
absolutely everything) proponents at Wolfram.
Bob F
wrote:
> Bob,
>
> I feel your pain. Perhaps NotebookAutoSave partly meets your
> requirements. It lets your notebook save after each evaluation.
>
> Cheers -- Sjoerd
>
NotebookAutoSave does not work with new notebooks, only for ones that
have been saved before. Perhaps if Wolfram changed that it would be a
step in the right direction.
-Bob
Vince
I'll give a dime.
Too frequently I've lost work to Front End 'sublimation', and
consequently have developed a CTL-S 'tick'. (I'll look into
NotebookAutoSave, though that doesn't seem to sufficiently address the
problem.)
Vince Virgilio
sean_...@yahoo.com
on windows vista. I have both 32 and 64 bit vista running same version
of the mathematica. And it just craps out and unlike the previous
versions, mathematica (or windows not sure which is the culprit behind
this behavior) doesn't allow me to save the frontend--which is
supposed to take precedence over kernel. Is that still true?
Also Mathematica used to have a cache directory where crashed files
can be salvaged, but now it seems like the file after crash isn't
saved there. Anyone know how to set it so that a copy is saved to
cached directory after a crash?
Another question about autosaving.
After I set the autosave "true" I noticed that Mathematica keep
making defualt sound everytime an expression is evaluated.
It starting to get quite annoying, so.. Is there a way to turn that
sound off but keep the autosave feature?
On Apr 28, 1:46 am, "Sjoerd C. de Vries" <sjoerd.c.devr...@gmail.com>
wrote:
Bob F
>
> Another question about autosaving.
>
> After I set the autosave "true" I noticed that Mathematica keep
> making defualt sound everytime an expression is evaluated.
>
> It starting to get quite annoying, so.. Is there a way to turn that
> sound off but keep the autosave feature?
>
If you click on the "Why the beep" in the "Help" menu, it tells you
that the notebook you are working on that has the "AutoSave" set to
true has not been named, so it can't be saved. Give it a name and the
beeping will stop.
If Mathematica beeps, you probably don't want to ignore it -- find out
why and see if it is important. I think it will be something that you
want to address before going on.
-Bob