> Someone recently emailed me to see if I found an answer, as they too had > this problem. The only way to stop it was to turn off debugging. Most > ignoring. The best I got from Borland was D5 is not win2000 certified. Bring > on D6. This problem will occur on D6 also. (And pretty much any software that uses the Windows Debug API to debug a process) - See my other post for a solution. Deepak Shenoy Agni Software http://www.agnisoft.com --------------------------------------------------------------------------- New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] Website: http://www.delphi.org.nz To UnSub, send email to: [EMAIL PROTECTED] with body of "unsubscribe delphi"
- [DUG]: F12 - CPU debug window Paul Lowman
- Re: [DUG]: F12 - CPU debug window Deepak Shenoy
- Re: [DUG]: F12 - CPU debug window Rohit Gupta
- Re: [DUG]: F12 - CPU debug window Robert Martin
- Re: [DUG]: F12 - CPU debug window Paul Lowman
- RE: [DUG]: F12 - CPU debug window Max Nilson
- RE: [DUG]: F12 - CPU debug window Roser, Wayne
- Re: [DUG]: F12 - CPU debug window Paul Lowman
- RE: [DUG]: F12 - CPU debug window Max Nilson
- RE: [DUG]: F12 - CPU debug window Alan Rose
- RE: [DUG]: F12 - CPU debug window Deepak Shenoy
- RE: [DUG]: F12 - CPU debug window Alan Rose
- Re: [DUG]: F12 - CPU debug window Deepak Shenoy
- Re: [DUG]: F12 - CPU debug window Nello Sestini
- Re: [DUG]: F12 - CPU debug window Nello Sestini
- Re: [DUG]: F12 - CPU debug window Rohit Gupta
- Re: [DUG]: F12 - CPU debug window Paul Lowman
- RE: [DUG]: F12 - CPU debug window Scott Cree