Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.soft-sys.math.mathematica > #12692 > unrolled thread

Re: Mathematica 9.0.0.0 for windows crash

Started byDietmar <Rempfer@iit.edu>
First post2012-12-08 06:29 +0000
Last post2012-12-11 07:23 +0000
Articles 2 — 2 participants

Back to article view | Back to comp.soft-sys.math.mathematica


Contents

  Re: Mathematica 9.0.0.0 for windows crash Dietmar <Rempfer@iit.edu> - 2012-12-08 06:29 +0000
    Re: Mathematica 9.0.0.0 for windows crash Vince Virgilio <blueschi@gmail.com> - 2012-12-11 07:23 +0000

#12692 — Re: Mathematica 9.0.0.0 for windows crash

FromDietmar <Rempfer@iit.edu>
Date2012-12-08 06:29 +0000
SubjectRe: Mathematica 9.0.0.0 for windows crash
Message-ID<k9umnj$sj1$1@smc.vnet.net>
No, for me Mathematica 9 continues to be a disaster: I uninstalled 8.0.4, and attempted to install 9.0 using the supposedly "fixed" installer. The result was a BSOD on first starting up Mathematica. I then attempted each of the fixes mentioned in the knowledge base article. The result is that the Mathematica frontend crashes on startup. So this is a no-go: I am unable to install and run Mathematica 9, period.

I might add that the Mathematica installer has had issues with font installation for years. One wonders why it is that every piece of software on the planet can successfully install their fonts on a Windows machine, but Wolfram has trouble figuring this out.

[toc] | [next] | [standalone]


#12757

FromVince Virgilio <blueschi@gmail.com>
Date2012-12-11 07:23 +0000
Message-ID<ka6n2d$h3e$1@smc.vnet.net>
In reply to#12692
On Windows 7 x64 (AMD quad-core 16GB RAM); /never/ BSOD'ed until after the 
M9 install.

Two days of BSODs until I recalled the M9 font problems. Complete recovery 
after uninstalling both 8 and 9, then removing all Mathematica* fonts from 
c:\windows\fonts.

Reinstalled the new Mathematica 9 after stabilizing the system; no BSODs since.


Before recovery, during those two days of BSODs, Windows Safe Mode was my one stable point. Eventually I figured out that I could BSOD even that by opening c:\windows\fonts in Windows Explorer. I think the font "preview" triggered the BSOD. Of course, a plain-text dir listing at the cmd prompt did not BSOD.

Vince


[toc] | [prev] | [standalone]


Back to top | Article view | comp.soft-sys.math.mathematica


csiph-web