Products
Rob Brooks-Bilson's Blog
In a previous entry I talked about a problem I was having with my laptop blue screening every time I tried to install/run ColdFusion 8 with the default 1.6 jvm. At the time, I believed the issue might be with java 1.6 and some drivers on my machine. It turns out I was only partially right.
I though others in my group had been successful at installing CF8 on their machines, but it turns out that they all had the same BSOD problem I did. After a little more digging, Adam Crump was able to determine that the fault was taking place with a file called fslx.sys. It turns out that this file is used by the Altiris Software Virtualization System that was installed on all of our laptops. We use Altiris for lifecycle management, helpdesk, patch management, and more. The software virtualization wasn't being actively used, but something about it is causing the BSOD. Removing the Altiris virtualization program and reverting back to the 1.6 jvm solved the problem.
We're planning to submit the issue to Symantec (they recently bought Altiris) so they can hopefully issue a fix. Their virtualization software is actually pretty cool, so I'd like to be able to have it reinstalled on my machine again at some point.
Aura skin for Raymond Camden's BlogCFC inspired by Joe Rinehart & Steven Erat. This blog is running version 5.5.1.
Funny thing is, it seems to be a combination of the Altiris virtualization software and the jvm. No BSOD with Java 1.4, but with 1.5 or 1.6, it blows up. As I understand it, fslx.sys is a filter that all I/O passes through, so it's something that the jvm is doing that the filter doesn't like/can't handle. I'm sure it's a Symantec problem, and we're forwarding the issue along to them, but who knows if/when it will ever be fixed.
Question is this: do you know if this conflict happens only during the install process ie could you install CF first and then Altiris?
Or will the two packages not run together at all?
The Altiris patch management piece will function ok with ColdFusion 8. It's only their software virtualization product (a separate product/install) that causes the BSOD problem. If you have to run the virtualization software, then for now, you'll have to run CF 8 with the 1.4 jvm.
I wonder if it's at all related (note: the issue didn't exist with the same code and xml on ColdFusion 7)
It can be very hard to tell with the virtualization stuff. I know a bunch of people running vmware (myself included) that aren't having problems with older versions of CF (7.0.x in my case), but I haven't heard much on problems with CF8 outside of a few cases.
If you write out to a dump file when you BSOD, it may help you see what was running when the BSOD occurs.