On Wed, Jan 9, 2013 at 12:54 PM, Art Heimsoth <artst...@artheimsoth.com>wrote:
> I am using Process Explorer from sysinternals and the cpu usage does > not go above 10% on the XP, and the I/O counts are also very low. > What about the total memory usage in the XP? Even though it has roughly the same memory as the Windows 7 system, if the XP system has most of the physical memory in use and the Windows 7 does not have much physical memory in use, this might cause a problem. I doubt it is this or you would have mentioned it. You didn't actually say, are the versions of ooDialog and ooRexx the same on both systems? Apart from the 32-bit and 64-bit do both systems have ooRexx 4.2.1 and ooDialog 4.2.0 on them? Can you put a couple of say statements in the program to see which method is taking the most time. I was thinking of something like this: ::method init say 'Entered init()' .... say 'Leaving init()' ::method initDialog say 'Entered initDialog()' .... say 'Leaving initDialog()' Do the same thing for defineDialog() if you are using it. If you don't mind sending me the program, I can test it on my XP and my Windows 7 systems and see if I get similar results. If I do get the same results I may be able to determine what the problem is. -- Mark Miesfeld
------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612
_______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
