Program fails

Hi

On my PC with WinXP Embedded for Point of Sale is a problem with an
application. It fails every couple of days without a trace neither in the
EventLog nor in a logfile (as far as i know). Now I'm looking for a tool or
another possibility to figure out my problem...

Thanks in advance

"Armin Galliker" <ArminGalliker@discussions.microsoft.com> wrote in message
news:B4745729-F457-4F21-8FA9-806299067A65@microsoft.com...
> Hi
>
> On my PC with WinXP Embedded for Point of Sale is a problem with an
> application. It fails every couple of days without a trace neither in the
> EventLog nor in a logfile (as far as i know). Now I'm looking for a tool
> or
> another possibility to figure out my problem...
>
> Thanks in advance

You need to supply more details - "it fails" does not tell us
a great deal. Does it crash the computer? Terminate by itself?
Lock up?

Also: Have you checked the FAQs of the supplier?

> You need to supply more details - "it fails" does not tell us
> a great deal. Does it crash the computer? Terminate by itself?
> Lock up?
>
> Also: Have you checked the FAQs of the supplier?

Sorry, my fault. The program terminats by itself. The program was written by
myself and works without any problems on other computers. The difference is
that the other PC's are running on W2K. Unfortunately it's not possible to
run the program with a debugger. WinXP isn't affected by the problem. At the
moment the workaround is just to restart the process... Even though the
program doesn't need a lot of memory, the computer is brand-new (3GHz,
Pentium 4, 2GB-RAM).

"Armin Galliker" <ArminGalliker@discussions.microsoft.com> wrote in message
news:5E448185-0859-428A-9EA7-260671250485@microsoft.com...
>> You need to supply more details - "it fails" does not tell us
>> a great deal. Does it crash the computer? Terminate by itself?
>> Lock up?
>>
>> Also: Have you checked the FAQs of the supplier?
>
> Sorry, my fault. The program terminats by itself. The program was written
> by
> myself and works without any problems on other computers. The difference
> is
> that the other PC's are running on W2K. Unfortunately it's not possible to
> run the program with a debugger. WinXP isn't affected by the problem. At
> the
> moment the workaround is just to restart the process... Even though the
> program doesn't need a lot of memory, the computer is brand-new (3GHz,
> Pentium 4, 2GB-RAM).

If you wrote the program by yourself then you should be able
to insert some diagnostic code that reports exactly how far
the program gets and why it bombs out at that stage. Perhaps
you're dealing with an unitialised variable that just happens to
assume a fatal value on this particular PC.