Quoting Jerry Kreps on Sat, Mar 03, 2001 at 05:11:39PM -0600:
After upgrading to 7.1 from 7.0 I can say that: a) my 1996 Sony VAIO P166 with 64MB of RAM runs about 1/2 as fast. "locate" for example, use to snap back. Now it can take 30 secs to a minute. SO5.2, slow to load to begin with but acceptable in 7.0, has about doubled it's load time in 7.1 (But, it will be fast eought for my wife, who would make a newbie look like a seasoned pro :-)
b) the REAL REASON for this missive: MuPAD-1.4.2, on the SuSE CD, will not run under KDE2. When you click on xmupad or chose it from the KDE2 menu structure what pops up is Hytex, the xwindow mupad manual. Xmupad never appears. When you close Hytex it disappears off the screen but stays in memory hogging up to 30% of the CPU resources doing nothing. I have to kill it manually.
To test things out, I downloaded and installed the tar version of MuPAD-1.4.0 (notice the prior to 1.4.2) and encountered the same problem. The 1.4 tar version of MuPAD behaves identically.
AND, while I can use my registration on the 1.4.0 tar version of MuPAD to remove the memory restraint, the registration code fails under 1.4.2,
Now I believe this is just a library problem. Which library do I have to load to get 1.4.2 xmupad to run? I can always get another registration number. JLK
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
You could take the tar version and use the configure script to see what libraries it looks for or wants or capture the results of the ./configure to a logfile and see what it looks for. It may be a "newer library problem". I used to have this problem with my builds of gnome before SuSE and Gnome came together on the naming sequences of gnome packages. Then a gnome application would "expect glib.xxx.xxx.x". If it found something else, it would probably run but it would start acting wierd or eating memory when I closed it down. I stopped using a few programs (games especially) in gnome back then because I could not track the issues down. If I backcycled the library to something which appeared closer then some gnome core stuff would complain. Luckily, I had backed up the build a few times when I saw this happening so recovery was a bit easier. I also had a "junk install" of SuSE which I played with and tried different things on. When SuSE and gnome came together on package naming, things became much easier. I don't mess anymore with kde or gnome, but I would suspect that there is a library incompatability which you have found. Try trapping what the configure or make programs do and see if you spot something suspect like a rather significant change in libraries from what the program wants to what you have. I would also check on google for others which may have had this problem in the past with other applications. -- Michael Perry mperry@tsoft.com ------------------