Running Debug in 64 bit Vista

[Michael Mattias]

Very annoying is say the least....have to re-insert all of the Watch variables.

You might want to submit a new feature suggestion to have those 'remembered', either "by program" or maybe just "last used."

I don't use the stepping debugger so I have no clue what would be useful to you or others.

[Carlo Pagani]

http://www.powerbasic.com/support/pb...ad.php?t=41325

And no AV does not solve the issue on Win 7...

[Bruce Wood]

I have (Had) the same problem.

Vista 64-bit (PBCC 5.x) would give me the same 496 Destination File Error msg after trying to exit from Debug.

Very annoying is say the least....have to re-insert all of the Watch variables.


Anyway, I closed AVG 8.5 and surprize! No more message. I can cycle debug as I please.

Just thought I'd post that info.

Bruce

P.S. I sure wish there was a way to auto insert my watch variables.
Like:
#Debug Watch Loop5
#Debug Watch hwnd

Manually inserting a series of variables is very tedious on each startup.

Thank You

[Gösta H. Lovgren-2]

Removed
==================================================
"It is unbecoming for young men to utter maxims."
Aristotle (384-322 B.C.)
==================================================

[Michael Mattias]

Not posted in PowerBASE forum.

[Alan Hill]

How long ago was that? It would be nice to know when we might hear from them about this.

[Scott Slater]

>I trust you two have reported this to PB Support?

Yes, awhile back when I first upgraded to PBWin9. I also am running the same processor as Alan, although it shouldn't be an issue, it is interesting.

[Michael Mattias]

>I also experience the same issue here

I trust you two have reported this to PB Support?

I think they'd like to know.

[Hedley Moses]

I am using an HP desktop with Intel's Q8200 Core 2 Quad processor running 64 bit Vista Home Premium and 8 GB of memory.

Thats a mean machine

[Scott Slater]

Not sure, but I also experience the same issue here and I am also using Vista 64-bit. I don't get the problem running under XP, so for now I do my debugging in an XP virtual machine under Vista.

[Alan Hill]

I enjoy programming as a hobby, not a profession. I have used this site to search for help numerous times, usually with great success. This site really helps in learning how to use PB for windows. Since I haven't found anything related to my problem, I decided to post a question for the first time.

I am using an HP desktop with Intel's Q8200 Core 2 Quad processor running 64 bit Vista Home Premium and 8 GB of memory. I like to use the Debug function to trace problems. With my old system (XP SP3 on a Pentium 4 processor), I had no issues running Debug. But with Vista, once I find the problem, exit Debug, correct the code, and then try to run Debug again (or even compile and execute), I get Error 496 Destination file write error. Using Task Manager, I confirm that the Application tab does not show my program still running, however, on the Processes tab, I see my program's name with a *32 at the end. I click to close the process, but it doesn't close. I have to close PB and then relaunch it before I can resume running Debug or compiling the program.

Any thoughts on what the problem is?

Thanks.