Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: don't show: foobar2000 was terminated abnormally last time. (Read 4350 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

don't show: foobar2000 was terminated abnormally last time.

I'm using Foobar2000 on my HTPC with my iPhone. This works, modulo some bugs, pretty well

But Sometimes I'm just lazy and just reset my HTPC (no proper shutdown). When next time the computers starts, Foobar2000 won't start and gives the annoying popup:
Quote
foobar2000 was terminated abnormally last time.
- Start in safe mode
- Check online troubleshooter
- Start normally

So I would like to start always normally. I don't care about this abnormally termination!

Someone has an idea to solve this? It didn't find an option to turn this 'feature' off nor there is a commandline argument to force normally mode.

And no, always proper shutdown is not possible.


don't show: foobar2000 was terminated abnormally last time.

Reply #1
Start foobar2000 using a batch file that erases the "running" file from the configuration directory before starting the player.

Note that if you aren't using something like foo_jesus, your playlists and configuration aren't being saved since this normally only happens on a proper shutdown.

don't show: foobar2000 was terminated abnormally last time.

Reply #2
Start foobar2000 using a batch file that erases the "running" file from the configuration directory before starting the player.

Yeah, that I was looking for. But where can I locate the "running" file?

edit: %USERPROFILE%\AppData\Roaming\foobar2000\running

Note that if you aren't using something like foo_jesus, your playlists and configuration aren't being saved since this normally only happens on a proper shutdown.

If I don't change the configuration in that 'session', there is nothing to save?

So easily solved after all. THX!