michlet

[dallolio]

Hi,
I've been busy trying to develop my construction technique, still far enough from perfect product , before next effort, I’d like to look again into design matter.
I’m experiencing issues running michlet into my windows xp, I’ve same problem even with version “807w” I used to run on this machine 3 years ago.
mlt920w.exe lunches the window but I just get the windows frame and takes a lot before I get some of michlet actual screen, then everything is almost stuck, any command, if works take forever to happen. Same files works great into other xp machine I tried.
Thanks for reading this and any idea you might share about this matter.

Andrea.

[Leo Lazauskas]

Originally Posted by dallolio

Hi,
I've been busy trying to develop my construction technique, still far enough from perfect product , before next effort, I’d like to look again into design matter.
I’m experiencing issues running michlet into my windows xp, I’ve same problem even with version “807w” I used to run on this machine 3 years ago.
mlt920w.exe lunches the window but I just get the windows frame and takes a lot before I get some of michlet actual screen, then everything is almost stuck, any command, if works take forever to happen. Same files works great into other xp machine I tried.
Thanks for reading this and any idea you might share about this matter.

Andrea.

I haven't heard that happening before. Michlet runs fine on my XP and Windows 7 machines and on the machines of some of my "beta testers".

If it works well on one of your XP computers but poorly on the other, then
you need to look at what is different between the two machines.

Good luck!
Leo.

[dallolio]

Copy that, thank you Leo.

Andrea.

[marshmat]

It sounds like you have some other background process aggressively taking up resources on the one XP machine. Michlet doesn't like being pushed to the background by other tasks; it is normal for it to go into a sort of "on hold" state if other things interrupt it in the middle of a calculation.

If you like troubleshooting, try running a trace with Sysinternals Procmon while you reproduce the problem. Its logs are not easy to parse but they are usually successful in revealing the source of mysterious glitches like this.

[dallolio]

Thank you Matt Marsh, I'm going to try Sysinternals Procmon.

Andrea.

[dallolio]

Matt Marsh, the log file of Sysinternals Procmon does not say much to me, I could not attach it, its format is not suppurted for upload. Any idea of what I shouldbe looking for ? It looks the program is not actually stuck, it’s just the graphic does not refresh the michlet windows, if I drag michlet window out of the screen view and pull it back the screen refreshes and the command has been executed.

Andrea.

[marshmat]

Procmon is a pretty sophisticated tool- it is not intuitive.

See http://blogs.technet.com/b/markrussinovich/about.aspx for examples of how to use it. The basic idea is to set it running, do the task in question, then filter the log to see what happened during that time. For many people, though, it is a bit too much tech gibberish to sift through; this is what good Windows repair techs are paid to do.

What you describe in post #6 sounds a lot like a graphics driver bug.

[dallolio]

Thank you Matt Marsh.

Andrea.

[Leo Lazauskas]

Originally Posted by dallolio

Thank you Matt Marsh.

Andrea.

Try updating the graphics drivers for your video card.

Leo.

[dallolio]

installed now Leo, no change ... I'll post something into forum into Matt Marsh post#7

Andrea

[Leo Lazauskas]

Originally Posted by dallolio

installed now Leo, no change ... I'll post something into forum into Matt Marsh post#7

Andrea

Did you work out the difference between the two computers and why
it works on one but not the other?

[dallolio]

Using sysinternals procexp I killed most of the processes, not the one making the issue, two PCs active processes look very close