winstep wrote:





Well, nothing is deleted WsMMPlay.exe is present and it seems today it is started. I will see if the crashes stop. I will also keep an eye to see if Winstep Media Player (32 bit), how it shows in the task manager, stops working.

Made another attempt at that folder with mp3 files. Same problem. I will investigate with similar files to see if it affects other albums. I will try to figure out what is going on as time permits.

Ok. Note that WsMMPlay.exe will unload itself automatically after 1 minute of not playing any sound.

winstep wrote:




I`ll test that now.

WsMMplay.exe Stops and starts as you said. Btw, no crashes so far....

Waaaait problem: the Winstep Media Player disappeared with the music playing. I stoped the music (via keyboard controls) and started again (via clicking on the dock icon). Music started, the Winstep Media Player did not. I`ve pushed the stop button on the keaboard, waited 1:30 minutes and started again the music (via clicking on the dock icon). The Winstep Media Player is nowhere to be found in Task Manager.

And it won't appear anymore until you restart the Winstep application.

That's a fail safe: if the Winstep application can't launch the Winstep Media Player for some reason, it will flag that internally instead of keep trying, and will start playing the music directly from the application itself.

Of course, if you read what was happening with Seeker in that thread I linked to, you already know what can then happen with bad media codecs: the application starts crashing almost randomly through no fault of it's own.

Looks like the Winstep Media Player might have crashed? But there should perhaps be a error message. Check your Windows Event Log, under Applications (Control Panel -> Administrative Tools -> Event Viewer -> Windows Logs -> Application).

Now, what I find strange is that the music kept playing. Unless the crash happened when transitioning from one music to the other and by the time you checked on the status of the Winstep Media Player the main application had already taken over.

Anyway, restart the Winstep application, open Preferences, go to the Sounds tab and disable all sounds and voices. This will make sure those do not interfere from then on.

Now make sure the Winstep Media Player is not already running, and if not start playing some music, while at the same time watching Task Manager closely to see what happens with WsMMPlay.exe

Ok, after 10 minutes of waiting, and 2 log offs (first followed by the crash listed below and no loading of workshelf at all). Things are back to normal. WsMMPlay.exe is running.

Nice crash dialog. Happened on log out, you say?

winstep wrote:




At log in, after log out.

Did some playing around with hotspots. Not sure if anybody brought this up: can you make grid stacks accesible via hotspot buttons?

While playing with the hotspots I`ve got the below error in this situation: I made a hotspot to open a deactivated dock. Everything was fine, but then with the nextart proprieties window opened (on the hotspot tab) I opened the dock proprieties and changed the name of the aforementioned dock. Then I got the crash, but the name changed and then the hotspot picked the change automaticlaly.

That WsMMPlay.exe stopped running again. So is on and off. To make it work again, I have to at least log off.


I`ll double check the Bitefender logs to see if I don`t get the cut off from there (yes I am running Bitdefender unfortunately) to see if that is the cause of the problem...

Eh? Restarting the Winstep application should be enough. Or does WsMMPlay.exe freeze and get stuck in memory?

winstep wrote:





It does not start if I try to restart winstep (double clicking Winstep.exe|WorkShelf.exe|Nextart.exe). A lot of times double clicking Winstep.exe only restarts the Nextart. Even if I completly exit the Winstep Suite, only Nextart gets restarted.

Well, that is weird!

And Workshelf.exe is not stuck in memory/Task Manager when you try to restart it?