Danny Ciarniello wrote:
With the release of several 64-bit versions of Vista that will probably be widely used, maybe the need will become more apparent. I'm not even sure how to get 64-bit firefox/seamonkey for my x64 XP. In my opinion, those three are dropping the ball, though.Rudolf Kastl wrote:I figured the SMP thought was a shot in the dark and it was more likely to be 32-bit plugin issues. As far as dropping non-free plugins is concerned, it all depends on the websites that one frequents and the experience that one wants from them. For myself, it's not an option to be without flash, java or realplayer so I have opted for the 32-bit solution. And going from an 800MHz PIII with 512 MiB of RAM to an Athlon 64 X2 4200+ with 1 GiB of RAM means that I don't really notice any issues with pulling in extra libs. Hopefully macromedia, sun and real will soon get with it and provide 64-bit plugins.2006/3/28, Eugen Leitl <eugen@xxxxxxxxx>:On Mon, Mar 27, 2006 at 01:52:30PM -0800, Danny Ciarniello wrote:A thought just occured to me. I am using a dual core Athlon 64. I wonder if firefox is having some SMP problems?No, that bug occurs on single-core AMD64s, too. I was suspecting a malfunctioning extension. It's good to learn the problem can be fixed by reverting to 32-bit Firefox. The bug has driven me to drink, and my wife to XP/OS X.The bug in itsself are the non free browser plugins :). Reverting to 32 bit browser is a workaround not a fix cause the plugins are non free and therefor one has to wait until some companys manage to build 64 bit versions of their plugins (if ever.) regards, Rudolf Kastl p.s. i just drop crap like flash and am happily using a 64 bit only os with only free components... a 32 bit browser pulls in 32 bit libs which eats up extra ram...Dan.
-Another Dan
