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.
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.
Comment