When I compile a program that has certain "issues" I sometimes get the message, "destination file write error" if the program has been run before and there is some process still running because of the issue. Usually I can find it in the Task Manager, and sometimes using an application killer program, but how can I kill the process if I can't find it?
Announcement
Collapse
No announcement yet.
finding and killing an errant process
Collapse
X
-
Originally posted by Chris Holbrook View PostTry closing the PB IDE?
To anyone else that is interested, the problem seems to be that my serial port was acting up!
I tried using some terminal programs and the error message from them was that it could not open Com1 (but could open Com2).
I hadn't cleaned the computer for a while, so I blew out the dust, reseated the plug-in cards, and now the problem (seems to have) gone away.
Now what on earth can a piece of hardware like the serial port do that can act like a process that has not been stopped?
And why would the PB compiler say, "destination file write error"?Gary Peek, Industrologic, Inc.
Comment
-
Gary....not likely the port, but the process accessing it (or possibly to a further extent a anti-spyware trying to watch and catch a spyware)
what is the errant process? (since you mentioned serial ports, my interest is peaked)
Engineer's Motto: If it aint broke take it apart and fix it
"If at 1st you don't succeed... call it version 1.0"
"Half of Programming is coding"....."The other 90% is DEBUGGING"
"Document my code????" .... "WHYYY??? do you think they call it CODE? "
Comment
-
Originally posted by Cliff Nichols View PostGary....not likely the port, but the process accessing it (or possibly to a further extent a anti-spyware trying to watch and catch a spyware)
what is the errant process? (since you mentioned serial ports, my interest is peaked)
Gary Peek, Industrologic, Inc.
Comment
-
Ok this is a doozy hail mary that I found in the past, that a user claimed my software would shut down windows as if I had gone to the start menu to tell it to shut down.
I knew that Could NOT happen, because I have no shutdown code in the program. So I did some digging, and found that although they had no UPS, someone had set the UPS monitoring software (not seen in processes) to shutdown, on low battery signal (which I assume was the RTS or CTS lines), and not warn the user.
So you may want to check your control panel for (either UPS, or power monitoring or something like that....I do not have a XP machine in front of me at the moment), and one of the tabs will have a checkbox about monitoring (default is COM1), and see if that is set, if it is, un-set it.
Long shot, but worth a moment to check.Engineer's Motto: If it aint broke take it apart and fix it
"If at 1st you don't succeed... call it version 1.0"
"Half of Programming is coding"....."The other 90% is DEBUGGING"
"Document my code????" .... "WHYYY??? do you think they call it CODE? "
Comment
-
-
>So it may still be a code issue
Indeed it may. But as of now it only The Amazing Kreskin could help you find it.Michael Mattias
Tal Systems (retired)
Port Washington WI USA
[email protected]
http://www.talsystems.com
Comment
-
Originally posted by Gary Peek View PostAnd why would the PB compiler say, "destination file write error"?
Code:#Compile Exe
Just a thought.
=================================================
"We don't like their sound,
and guitar music is on the way out."
Decca Recording Co. rejecting the Beatles, 1962
=================================================It's a pretty day. I hope you enjoy it.
Gösta
My Ego Site: http://www.SwedesDock.comPB Newby Tips: http://www.swedesdock.com/powerbasic/pb_shortcuts.htmlJWAM: (Quit Smoking): http://www.SwedesDock.com/smokingLDN - A Miracle Drug: http://www.SwedesDock.com/LDN/
Comment
-
How dumb am I lately???
If you can get us a list of processes, or snapshots of "SysInternals Process Viewer", I am sure we can find the "Errant" process
Engineer's Motto: If it aint broke take it apart and fix it
"If at 1st you don't succeed... call it version 1.0"
"Half of Programming is coding"....."The other 90% is DEBUGGING"
"Document my code????" .... "WHYYY??? do you think they call it CODE? "
Comment
-
Originally posted by Michael Mattias View Post>So it may still be a code issue
Indeed it may. But as of now it only The Amazing Kreskin could help you find it.
We still have that issue of why the PB compiler says "destination file write error" when a piece of hardware is defective.Gary Peek, Industrologic, Inc.
Comment
-
We still have that issue of why the PB compiler says "destination file write error" when a piece of hardware is defective.
We have had scores of threads here over the years in which it has been pointed out that "errors" do not necessarily manifest themself to an application until sometime after the REAL error. Why would the compiler - itself an application - be exempt from this quirk of the O/S?
MCM
PS: FWIW, I have sent in a NFS requesting this error message be enhanced to include text based on the WinAPI error code... eg "invalid handle", "invalid path or filename", "permission denied" etc..Last edited by Michael Mattias; 6 May 2008, 08:10 AM.Michael Mattias
Tal Systems (retired)
Port Washington WI USA
[email protected]
http://www.talsystems.com
Comment
-
Originally posted by Pierre Bellisle View PostHi Gösta,
I was under the impression that this problem was resolved
with the latest 1.66 "Jelly Fish Pro" freeware edition.
Trying to compile when the program already is running causes the "Destination ..." error.
Is it the one you're using ?It's a pretty day. I hope you enjoy it.
Gösta
My Ego Site: http://www.SwedesDock.comPB Newby Tips: http://www.swedesdock.com/powerbasic/pb_shortcuts.htmlJWAM: (Quit Smoking): http://www.SwedesDock.com/smokingLDN - A Miracle Drug: http://www.SwedesDock.com/LDN/
Comment
-
Originally posted by Gary Peek View PostWhen I compile a program that has certain "issues" I sometimes get the message, "destination file write error" if the program has been run before and there is some process still running because of the issue. Usually I can find it in the Task Manager, and sometimes using an application killer program, but how can I kill the process if I can't find it?
There was no Dialog, just a MsgBox. The program would run (compile/beep) but not show the MB. Hmm, run again & get the dfwe. Pop up Task Mgr and there was the prog running. Okay, Kill it and make a change in program, run, and ditto. Even ended up adding a Dialog but same results (no mb showed up though). Close the Dialog and get the dfwe again.
Hmmm, after a few (dozen) of these, I went and did something else to get my mind off it. Couple minutes later, I hear a beep, and sure enough there's the MB popped up.
What was happening was the string manipulation routine was taking so long (minutes) I was ending the program (via taskmgr) before the Sub was finished. ((Not expecting it to be so slow.)
So Gary, what could be happening in your program is an exceptionally long running routine (maybe an endless loop). Just a thought.
=====================================
"Nietzsche was stupid and abnormal."
Leo Tolstoy (1828-1910)
=====================================It's a pretty day. I hope you enjoy it.
Gösta
My Ego Site: http://www.SwedesDock.comPB Newby Tips: http://www.swedesdock.com/powerbasic/pb_shortcuts.htmlJWAM: (Quit Smoking): http://www.SwedesDock.com/smokingLDN - A Miracle Drug: http://www.SwedesDock.com/LDN/
Comment
Comment