AE Debug

Sorry, I got carried away,

I don't know what you should do. Approach I said is to radical for you,
since you are experiencing application failure not XPE BSOD.

Best regards,
Slobodan

"Slobodan Brcin" <sbrcin@ptt.yu> wrote in message
news:uzaWk8#iDHA.548@TK2MSFTNGP11.phx.gbl...

> Cons,
>
> For debugging tools for windows to works have you tried adding to boot.ini
> /debug switch.
> Also you need remote debugger, since this is only decent thing that will
> give you real results.
> So you need to setup communication channel, on both sides.
> But, on XPE side in boot.ini also.
>
> Then before error happens you need to connect to XPE, let say break in to
> the XPE, and then let it go.
> Or just let kd to connect during the boot automatically.
>
> here is the piece from my boot.ini that will allow you to use RS232 to
> remote debug.
>
> multi(0)disk(0)rdisk(0)partition(9)\WINDOWS="Micro soft Windows XP Embedded
> FAT disk 192 MB" /fastdetect /debug /debugport=com1 /baudrate=115200
>
> Best regards,
> Slobodan
>
> "Cons" <c.consbruch.NO@Spam.Beckhoff.de> wrote in message
> news:Oabmqx#iDHA.220@tk2msftngp13.phx.gbl...

> > Hi everybody,
> >
> > I want to use a JIT-Debugger on XPE, but neither drwtsn32 nor the

> debugging

> > tools for windows works. The regestry-Key AeDebug is correct(works under
> > XPPro).
> > If an error occurs, the "send error report wizard" pops up, even if I
> > disable it in System Properties.
> >
> > Thanks for your help.
> > Cons
> >
> >

>
>

To get Dr. Watson to work, serach old archives. There were numerous threads
about this 6+ months ago. Lynda Allen from MS answered this.

HTH... Doug
"Cons" <c.consbruch.NO@Spam.Beckhoff.de> wrote in message
news:Oabmqx#iDHA.220@tk2msftngp13.phx.gbl...

> Hi everybody,
>
> I want to use a JIT-Debugger on XPE, but neither drwtsn32 nor the

debugging

> tools for windows works. The regestry-Key AeDebug is correct(works under
> XPPro).
> If an error occurs, the "send error report wizard" pops up, even if I
> disable it in System Properties.
>
> Thanks for your help.
> Cons
>
>

If your program is written in visual studio look at the jester question in
next thread.
And see if you can use msvcmon.exe.

Best regards,
Slobodan

"Cons" <c.consbruch.NO@Spam.Beckhoff.de> wrote in message
news:Oabmqx#iDHA.220@tk2msftngp13.phx.gbl...

> Hi everybody,
>
> I want to use a JIT-Debugger on XPE, but neither drwtsn32 nor the

debugging

> tools for windows works. The regestry-Key AeDebug is correct(works under
> XPPro).
> If an error occurs, the "send error report wizard" pops up, even if I
> disable it in System Properties.
>
> Thanks for your help.
> Cons
>
>

I have the exact same problem and tried the same as you,
so my short question is - did you solve your problem and
if so - how?

I have read through all the registry settings for the
disabling Error Reporting tool and for enabling
application debugging - in my best believe all my
settings are correct, but it still doesn't work.

I made a small program that provoke a memory violation
crash (mycrash.exe) - and every time it crashes XPE
automatically start a program called "dwwin.exe" which is
the client of the windows reporting tool.

I have searched quite a lot but have found no solution.

I have tried to rename dwwin.exe and copy drwtsn32.exe to
dwwin.exe. When a crash occur Dr. Watson's setup GUI come
up - just as if you started drwtsn32.exe from start | run.

My ugly workaround will be to try and see what parameters
are being supplied to dwwin.exe and if the "process id"
is being supplied then make a program or script that
calls drwtsn32.exe with "-p <proves id>" parameter to
force Dr. Watson to store a crash dump file.

Virtually,
Thomas

>-----Original Message-----
>Hi everybody,
>
>I want to use a JIT-Debugger on XPE, but neither

drwtsn32 nor the debugging

>tools for windows works. The regestry-Key AeDebug is

correct(works under

>XPPro).
>If an error occurs, the "send error report wizard" pops

up, even if I

>disable it in System Properties.
>
>Thanks for your help.
>Cons
>
>
>.
>