Al, Bummer...
Next time PyMOL won't start or is acting freaky, can you try launching PyMOL via command line as follows: Start Menu->Run then enter: cmd Assuming PyMOL is in the default location, paste in the following line: "c:\program files\delano scientific\pymol\pymolwin.exe" +2 And then please send me the resulting output. Cheers, Warren -- Warren L. DeLano, Ph.D. Principal Scientist . DeLano Scientific LLC . 400 Oyster Point Blvd., Suite 213 . South San Francisco, CA 94080 USA . Biz:(650)-872-0942 Tech:(650)-872-0834 . Fax:(650)-872-0273 Cell:(650)-346-1154 . mailto:war...@delsci.com > -----Original Message----- > From: pymol-users-ad...@lists.sourceforge.net > [mailto:pymol-users-ad...@lists.sourceforge.net] On Behalf Of > al_pie...@vrtx.com > Sent: Friday, September 09, 2005 10:56 AM > To: pymol-users@lists.sourceforge.net > Subject: [PyMOL] minor irreproducible bugs > > > I have a couple of problems with pymol 0.98, but they only > happen once in a while and for no apparent reason. The > problem I'm having right now is that pymol just won't start > up. I double-click the pymol icon (or try to open a PDB or > pse file), it goes into the 'launching pymol' routine, the > pymol tab appears in the bar at the bottom of the screen, but > then a second later it disappears and pymol never starts up. > This problem tends to go away on its own, but sometimes it > takes a while. > The second problem is that occaisionally the pymol graphics > will become very slow and choppy. It seems that somehow the > graphics card isn't getting used anymore. This problem can > always be fixed by restarting the computer, but it's a bit of > a hassle. I guess this might be an OS problem rather than a > pymol problem. > > My system is a pentium 4 running Windows XP with an NVIDIA > Vanta graphics card and I'm running the precompiled binaries > of pymol. I know this isn't much information to work with, > and I can certainly live with these issues, but if anyone can > think what might be causing these problems I'd like to give a > shot at fixing them. > > Thanks, > Al Pierce >