Loading time of BS.player [CAUSE FOUND]
 

The new versions of BS.player take a long time in order to load.
I don't know if this is a bug but it happens only the first time which I open BSplayer after the os has loaded.
Other players open instantly.
I've used the latest version of BSplayer with CCCP along with the systems below:

Specs1:
OS: WindowsXP SP3
CPU: Intel Core 2 Duo E6850 @ 3.00GHz
RAM: 2 GB DDR2 667MHz

Specs2:
OS: WindowsXP SP3
CPU: AMD Athlon 64 X2 4850E @ 2.50GHz
RAM: 2 GB DDR2 800MHz

EDIT: I've found that this problem is caused by the AVG 8.0.
http://bsplayer.com/forum/viewtopic.php?t=13134

Possible Solution: Add Bsplayer.exe into Avg exceptions

Thanks for reporting this and also adding the possible solution.
(No BS.Player bug. Therefore moved this post to "General discussions")
:wink:

Yes, it's a known problem with some antivirus programs since v0.84.472 (some later versions are not affected by this behavior), and definitely from v1.0 on..
You can either add it to the exception list, or unpack the exe, or change AV program with one feaster.. (I would recommend the second one, even if it goes against BSplayer EULA) :roll:

Yes, actually I was the one which first (in 2004) found a work-around: http://bsplayer.org/forum//viewtopic.php?p=15728&15728
But I had not experienced it, nor heard of this problem since quite a long time now.
:wink:

The best workaround is to add BS path in the exceptions list of Resident Shield of AVG (settings>Resident Shield>Exceptions) :wink:

Thx again!
I'm still using Norton (360PE).
But good info for other AVG users!
:wink:

Yes, well, at least you posted the solution :P
I unpacked BSplayer EXE (the real cause is the compressor used that make the AV program to unpack the EXE before it can analyze it) since early 2003, when my McAfee antivirus program updated its engine :evil: (unfortunately for me, at that time McAfee checked the EXE every time you started it, not only the first time).. then switched to another antivirus program and never had problems again.. :D

But in my opinion to add bsplayer to the exclusion list is not the best solution (it's surely the most practical one ;) , but I don't like to add exes to the AV exclusion list... maybe I'm paranoid, especially since I never encountered a single virus since the day I adopted a good firewall :P )

Note: like I said, I didn't post the solution, just a work-around.
:wink:

And what you posted is the method most BSplayer users have adopted :wink:

Depends on the user's AV-program and firewall I suppose.
E.g. I have not experienced such problem any time recently. (Did you?)
Also I have not excluded BS.Player from Norton since quite some time (f.y.i. I'm using Norton (360PE) at present).
Anyhow, it appears that (at least) AVG still (or again?) causes this.
And DragonFighter has shown the work-around for AVG users.
:wink:

Never added BSplayer exe to the exclusion list since the day I adopted nod32 ;)