Kevin Clarke
September 18th 07, 02:33 AM
Hi folks,
I'm having a devil of a time getting DUATS to work on my XP SP2 laptop.
I've looked on line and have not found a similar problem.
Description is that on startup, the application dumps core. DUATS is
compiled without symbols so the stack traceback is non symbolic, not
much use in terms of debugging. But I can tell you that is does not map
to the screen. It dumps prior to that. The weird thing is that it *does*
work, once in 20-35 times (random) when I start it. If the application
runs to the point where it maps to the screen, it runs fine. It is just
a pain to get it started.
I've tried uninstalling it and removing it, reloading it, etc. etc. All
the obvious stuff.
Has anyone else experienced this problem? Any clues as to resolution? My
workaround is to run via the website, but I like the standalone
application better.
thanks,
KC
I'm having a devil of a time getting DUATS to work on my XP SP2 laptop.
I've looked on line and have not found a similar problem.
Description is that on startup, the application dumps core. DUATS is
compiled without symbols so the stack traceback is non symbolic, not
much use in terms of debugging. But I can tell you that is does not map
to the screen. It dumps prior to that. The weird thing is that it *does*
work, once in 20-35 times (random) when I start it. If the application
runs to the point where it maps to the screen, it runs fine. It is just
a pain to get it started.
I've tried uninstalling it and removing it, reloading it, etc. etc. All
the obvious stuff.
Has anyone else experienced this problem? Any clues as to resolution? My
workaround is to run via the website, but I like the standalone
application better.
thanks,
KC