Show Posts
1
Questions About Latest Products / Re: Can't rebrand new WP EZ Setup plugin
« on: July 17, 2016, 04:37:38 PM »
I did not attempt to reopen with 60 seconds or less. On one of the occasions it had actually been a few minutes between closing and reopening as I had gotten distracted. When I came back a few minutes later, I had encountered the issue.
Currently, I'm running Windows 8.1. Even when pressing the cancel after the error, that seems to close out the WP EZ Setup visually, but it stays running in the background. As I had mentioned, I had manually ended the WP ES Setup app via Task Manager and clicking "End Task." From what I've observed, it seems as if the WP EZ Setup application and the RRW Brander application are two separate apps. The WP EZ Setup being WP EZ Setup Brander.exe and the RRW Brander suite being rrwbrander.exe.
Thus far, the temp fix that I do is to just exit the RRW Brander. Once I exit the RRW Brander, then I can run the WP EZ Setup Brander with no issue. I just have to remember to exit out of the RRW Brander each time as it runs as a taskbar application.
Looking more closely at the .win10setup directory in the Temp directory, I see that the exe in there is rrwbrander.exe. It seems that is still there since the RRW Brander is running as a background/taskbar application. When I exit the RRW Brander (i.e. right click on icon, then click on Exit), I have noticed that the .win10setup folder as well as the rrwbrander.exe file still exists in the Temp directory.
That leads me to believe that the Temp directory is irrelevant to the issue. When the WP EZ Setup Brander.exe application is ran, it seems as if it's also starting up the rrwbrander.exe app. When the rrwbrander.exe app is already running, the WP EZ Setup Brander.exe app doesn't know how to handle the error, so it throws the error I and others have been getting. That is, it may need some error-checking code to handle this issue.
Therefore, I believe a fix would be for the WP EZ Setup Brander.exe to first check to see if rrwbrander.exe is running. If it's not running, then it would load rrwbrander.exe. If WP EZ Setup Brander.exe detects that rrwbrander.exe is already running, then it wouldn't attempt to start the rrwbrander.exe application.
Currently, I'm running Windows 8.1. Even when pressing the cancel after the error, that seems to close out the WP EZ Setup visually, but it stays running in the background. As I had mentioned, I had manually ended the WP ES Setup app via Task Manager and clicking "End Task." From what I've observed, it seems as if the WP EZ Setup application and the RRW Brander application are two separate apps. The WP EZ Setup being WP EZ Setup Brander.exe and the RRW Brander suite being rrwbrander.exe.
Thus far, the temp fix that I do is to just exit the RRW Brander. Once I exit the RRW Brander, then I can run the WP EZ Setup Brander with no issue. I just have to remember to exit out of the RRW Brander each time as it runs as a taskbar application.
Looking more closely at the .win10setup directory in the Temp directory, I see that the exe in there is rrwbrander.exe. It seems that is still there since the RRW Brander is running as a background/taskbar application. When I exit the RRW Brander (i.e. right click on icon, then click on Exit), I have noticed that the .win10setup folder as well as the rrwbrander.exe file still exists in the Temp directory.
That leads me to believe that the Temp directory is irrelevant to the issue. When the WP EZ Setup Brander.exe application is ran, it seems as if it's also starting up the rrwbrander.exe app. When the rrwbrander.exe app is already running, the WP EZ Setup Brander.exe app doesn't know how to handle the error, so it throws the error I and others have been getting. That is, it may need some error-checking code to handle this issue.
Therefore, I believe a fix would be for the WP EZ Setup Brander.exe to first check to see if rrwbrander.exe is running. If it's not running, then it would load rrwbrander.exe. If WP EZ Setup Brander.exe detects that rrwbrander.exe is already running, then it wouldn't attempt to start the rrwbrander.exe application.