Randem Systems Support Board

InnoScript => InnoScript - General Questions, Report Bugs, Problems etc... => Topic started by: davethomson on January 20, 2014, 03:51:42 PM

Title: Strange InnoSetUp Problem
Post by: davethomson on January 20, 2014, 03:51:42 PM
This is really weird and it just started recently. I make a program's .exe file. I already have the .iss file so I don't need to run InnoScript again. Load InnoSetUp and select the previously .iss file. Runs fine until it hits the program .exe and stops saying,

"The process cannot access the file because it is being used by  another process."

So, I restart my PC and run InnoSetUp again and same .iss file.  Now it compiles just fine.

Have you heard of this situation?  Or what do you make of it?  I check the Start Task Master and don't see anything related to the program in either Applications or Processes.
Title: Re: Strange InnoSetUp Problem
Post by: davethomson on January 20, 2014, 04:07:26 PM
P.S. On my PC I am using InnoScript 10.5 Build 9 whereas on my laptop I am using 11 and no such problem there.
Title: Re: Strange InnoSetUp Problem
Post by: Randem on January 20, 2014, 08:25:02 PM
It means that the "program.exe" is loaded somewhere in memory and needs to be released or terminated before Inno Setup can use the file. When you restart your computer the program.exe gets released.
Title: Re: Strange InnoSetUp Problem
Post by: davethomson on January 21, 2014, 02:53:27 AM
Yes, I figured that out.  But the question is, "Why it the .exe still in memory someplace?  And I don't recall this ever happening before.  By this I mean I could change a VB program, make the .exe, run InnoSetUp (no need to run Innoscript again and nothing is changed there), and do this over and over again  without this "strange bug".  Could it be some weird virus that causes this?
Title: Re: Strange InnoSetUp Problem
Post by: Randem on January 21, 2014, 11:05:14 AM
I cannot tell you exactly why your program is in memory but it was loaded into memory somehow and there it sits until it is terminated it in some manner. Obviously something on your computer changed. VB could still have control of the "program.exe" and will not release it until VB is terminated.
Title: Re: Strange InnoSetUp Problem
Post by: davethomson on January 22, 2014, 12:20:52 AM
Well, no matter "who or what" is holding the .exe I know what to do, i.e. a "work-around" that works.  No big deal.  Thanks again for your excellent help.