If I start v3.116, exit and attempt to restart, I get an error saying the program is already running. Clrmame isn't listed in the task manager and I end up having to restart to be able to use the program again. Problem returns If I exit and attempt to start it again. Running Vista x64 SP1 with cmpro64. Its not running in a protected folder, btw :)

> If I start v3.116, exit and attempt to restart, I get an error saying the
> program is already running. Clrmame isn't listed in the task manager and I end
> up having to restart to be able to use the program again. Problem returns If I
> exit and attempt to start it again. Running Vista x64 SP1 with cmpro64. Its not
> running in a protected folder, btw :)
>
Not confirmed on 32b version under win xp sp2

I'm on 64bit Vista myself, this is a common MS Windows hickup which keeps window titles in memory. On startup, cmpro uses FindWindow() or something to check if it's already running.

Normally after a while you can start it....or you simply set "Adv_AllowRestart = on" in cmpro.ini.

It has nothing to do with 3.116


Roman Scherzer

> I'm on 64bit Vista myself, this is a common MS Windows hickup which keeps window
> titles in memory. On startup, cmpro uses FindWindow() or something to check if
> it's already running.
>
> Normally after a while you can start it....or you simply set "Adv_AllowRestart =
> on" in cmpro.ini.
>
> It has nothing to do with 3.116
>
>
> Roman Scherzer
>


It happens too me constantly with 3.116. Precious version didn't have this problem. Thanks for your help :)

> It happens too me constantly with 3.116. Precious version didn't have this
> problem. Thanks for your help :)

As I said, it has nothing to do with 3.116. It's a known Windows thing and happend in the past as well. I may think about removing the check completely.


Roman Scherzer

> > It happens too me constantly with 3.116. Precious version didn't have this
> > problem. Thanks for your help :)
>
> As I said, it has nothing to do with 3.116. It's a known Windows thing and
> happend in the past as well. I may think about removing the check completely.
>
>
> Roman Scherzer
>


I just deleted the cmp folder, created a fresh dir and all is well now. Botched upgrade or something I guess ;) Thanks again!

> I just deleted the cmp folder, created a fresh dir and all is well now. Botched
> upgrade or something I guess ;) Thanks again!


You're wrong. Again: It has nothing to do with 3.116 or your update. It's simply a common hickup with the FindWindow() API call.


Roman Scherzer

> > I just deleted the cmp folder, created a fresh dir and all is well now.
> Botched
> > upgrade or something I guess ;) Thanks again!
>
>
> You're wrong. Again: It has nothing to do with 3.116 or your update. It's simply
> a common hickup with the FindWindow() API call.
>
>
> Roman Scherzer
>


I understand what you're saying, but if its solely a Windows problem, why am I only experiencing the issue with cmpro and why was it not happening constantly with the previous version? I did in fact encounter this problem with an older version of cmpro, but it only happened a couple of times and as mentioned, I've only encountered this issue with cmpro. Sheesh...You seem to be getting rather defensive about this.

ok..here we go again...

The fact that you get it today only is purely accidently and is NOT related to 3.116. It happens since years. Guess why the allow_restart option was added years ago. It happens with other applications as well if they use the FindWindow() API call. The WindowsTitle of the already quit application is simply still in memory and the API call returns a valid handle. Easy as that.
Usually it goes away after a couple of minutes...most likely you experienced this when you removed the folder (which was not necessary).



Roman Scherzer

> ok..here we go again...
>
> The fact that you get it today only is purely accidently and is NOT related to
> 3.116. It happens since years. Guess why the allow_restart option was added
> years ago. It happens with other applications as well if they use the
> FindWindow() API call. The WindowsTitle of the already quit application is
> simply still in memory and the API call returns a valid handle. Easy as that.
> Usually it goes away after a couple of minutes...most likely you experienced
> this when you removed the folder (which was not necessary).
>
>
>
> Roman Scherzer
>

Thats fine and may well be the case. In no way am I complaining or trying to start a war over this. Just came here for help and to report a possible bug, thats all. In, my defense, I waited for a good while between attempts to restart and only a complete reboot allowed me to run cmp again. A new cmp install with a fresh dir was created as a last resort.

you're welcome...
well...I don't like the FindWindow behaviour either but I also had even worse experience when using Atoms or other Mutex objects...anyway...use the cmpro.ini switch and you'll never see the message again ;)


Roman Scherzer

> you're welcome...
> well...I don't like the FindWindow behaviour either but I also had even worse
> experience when using Atoms or other Mutex objects...anyway...use the cmpro.ini
> switch and you'll never see the message again ;)
>
>
> Roman Scherzer
>


-nt-