"NoOp" <[email protected]> wrote in message news:[email protected]... > On 04/02/2012 02:45 AM, Desiree wrote: >> "Chris Ilias" <[email protected]> wrote in message >> news:[email protected]... >>> I've finished updating <http://seamonkey.ilias.ca/>! >>> >>> Aside from content now being up to date, the big change is that it is >>> mostly screencasts. I've written a blog post about it at >>> <http://ilias.ca/blog/2012/03/seamonkey-help-is-back-with-screencasts/>. > ... >> I just get a blank page when going to your site both in Fx 10 Enterprise >> and >> SM 2.6.1 on two different computers both running XP Pro. Mozilla in its >> "wisdom" saw fit to blacklist my video driver which does HTML5 just fine >> on >> Opera and had passed all Mozilla tests for HTML5 until Mozilla decided to >> blacklist it and then, of course, the HTML5 tests no longer worked. I >> have >> zero interest in updating my video driver. I like the version I use and >> have >> specific reasons for why I use this version of nVidia nForce driver. I > > Perhaps if you upgraded to 2.8 you might not have the problem. The > blacklisted drivers are for WebGL, not HTML5. Here are mine:
I didn't upgrade SM to 2.7 because an extension would not work so SM told me. I have not tried to since then to see if the extension may work with SM 2.8. > > ==== > Graphics > Adapter DescriptionNVIDIA Corporation -- Quadro4 900 XGL/AGP/SSE2Driver > Version1.5.8 NVIDIA 96.43.19 > WebGL RendererBlocked for your graphics driver version. Try updating > your graphics driver to version NVIDIA 257.21 or newer. > GPU Accelerated Windows0. Blocked for your graphics driver version. Try > updating your graphics driver to version NVIDIA 257.21 or newer. > > > And from a WinXP with the same nVidia card: > Graphics > Adapter DescriptionNVIDIA Quadro4 900 XGLVendor ID0x10de > Device ID0x0258Adapter RAMUnknownAdapter > Driversnv4_dispDriver Version9.1.3.6Driver Date7-12-2006 > WebGL Rendererfalse > GPU Accelerated Windows0. Blocked for your graphics driver version. > ==== > > And I can render the HTML5 just fine. I also have WinXP running in a > VMWare virtual machine. That VM uses an SVG II 2D video driver, and I > can view the HTML5 on that as well: I checked my Workstation 7 virtual machine and I can't see anything about the video driver that is being used. That information is missing. I haven't looked at that for ages but I used to be able to see it. I also have no information on using multiple monitors and that should be visible too. There is a newer version of Workstation that I keep being bugged to install. I have resisted because it is a hassle to update Workstation. You essentially cannot. You have to uninstall the current version and then install the new version. I doubt I have enough space on my drive to download the new version which is huge. I am extremely low on space. I am waiting for Ivy Bridge processors to buy a new computer so I haven't been really concerned about this disk space on this one as it has a bulging capicator on the mobo so its days are limited anyway. But if I can free up some space, I will go ahead and install the latest Workstation update and see if that fixes the missing video driver information and maybe makes it so I can view HTML5. > > WebGL RendererBlocked for your graphics card because of unresolved > driver issues. > GPU Accelerated Windows0. Blocked for your graphics card because of > unresolved driver issues. > > So I'd recommend upgrading to 2.8. 2.8 resolved/fixed several HTML5 > issues: > http://www.seamonkey-project.org/releases/seamonkey2.8/#new > as did SeaMonkey 2.7: > http://www.seamonkey-project.org/releases/seamonkey2.7/changes > > >> would never have blamed Mozilla if my video driver caused Fx or SM to >> crash >> so I don't think Mozilla should arbitrarily placed video drivers older >> than >> the date they chose on a black list as some very old drivers work fine >> with >> HTML5 yet Mozilla put them on the black list. (I didn't blame Mozilla >> when >> Fx4 was crashing constantly a year ago and it turned out to be nVidia's >> nView that I love greatly but I had to disable it forever if I wanted to >> use >> Fx4 and above. I lost 50% of the functionality of my video card just to >> be >> able to use Fx4 but I didn't blame Mozilla so I certainly would not have >> blamed Mozilla if my video driver had problems with HTML5 on Fx or SM. >> Thus, >> I don't think Mozilla should have placed any video card driver versions >> on a >> black list. > > Interesting... On the WinXP I have nView 110.44 installed and working. > It's never cause an issue with Firefox or SeaMonkey for me. You might > try reinstalling to see if it is still giving you issues with the > current version of Firefox (11) or SeaMonkey (2.8). My nView version is 110.60. I had no problems until I upgraded Fx from 1.5 (that I used for a very long time because of one extension that was not available on Fx 2 or 3 but became available again for Fx4) to Fx 4 a year ago. From the moment I installed Fx 4, it began to freeze and crash very frequently. I would, at the same time, see dozens of errors in Event Viewer regarding nView. Plus, I would start getting popups from nView saying there was a stuck mutex and Desktop Manager needed to sever whatever program had the stuck mutex. Desktop Manager wanted my ok to do this. Even if I acted very rapidly to say ok, I would almost immediately get another popup about another program with a stuck mutex that needed to severed for stability of the desktop. That action might fix it for a bit but then soon I would get another popup about another program with a stuck mutex and then more popups from Desktop Manager that it needed to sever Fx and then Explorer.exe! At that point, usually, Fx would be totally frozen and Windows would then freeze. I didn't connect the nView problems with Fx4 at first. But the stuck mutexes got rapidly worse and worse with more and more of them and Fx would freeze very quickly. I noticed that if I used Opera I had no problems at all with stuck mutexes and Opera worked fine and never froze. At that point, I started researching and learned that this is a fairly widespread problem with Fx4 and above and nVidia's nView. At nVidia forums, most reporting this conflict were using the classic nVidia display/control panel not the newer Vista GUI and it seems the problem occurs more often if one is using XP with the classic nVidia display/control panel but there were also reports of this problem with those using the Vista style nVidia GUI for the control panel on XP. I don't recall the problem affecting Vista or Win 7 users but that may just be bad memory as I haven't looked at posts about this since last year around this time. No solutions. Most users stopped using Firefox rather than turn off nVidia Desktop Manager or use the Vista style control panel. I finally, very reluctantly, chose to turn off nVidia Desktop Manager and after doing this I never had a single instance of Fx freezing/crashing and then Windows freezing nor never saw another popup about a stuck mutex. But, oh, how I miss all the wonderful things I no longer can do. I really miss the transparency of the taskbar and windows when I grabbed them that Desktop Manager gave me and other things that I used constantly. > ... _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
