"Internal application error..." - Known Bug, but is there any permanent fix ?

Hi there,

I am a new user of the Object Desktop suite and have experienced the apparently well-known "An internal application error has occurred"-bug when starting Windows Media Player. It would appear this bug is also affecting operation of other media players. I am using the "Killer media" DesktopX widget and, while it does not bring up the "An internal application error..." message, it does not play any mp3 files at all until the bug is fixed.

While the fix is known and rather simple (i.e. re-registering the jscript.dll and vbscript.dll libraries with the regsvr32 command), it is however only temporary. The bug keeps up occuring and I need to periodically re-run the fix, which is quite annoying.

Is there any permanent fix to this bug ? It would appear the bug is caused by the DesktopX application (or is it really ?). Is there any way to stop the jscript.dll and vbscript.dll libraries from being "unregistered" ?

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

Hi,

I'm having the same problem each time I try to open a script associated with a widget.
I checked the windows registry and saw that my anti virus program (KAV 6.0) manipulates some entries for vbscript.dll and jscript.dll in the registry. In order to scan scripts for dangerous content, KAV re-directs calls to vbscript.dll and jscript.dll to a scr_ch_pg.dll that is located in the KAV installation directory. This feature can't be turned off in KAV unless you unregister scr_ch_pg.dll but that's not a good solution.
Unfortunately, re-registering the dlls with regsvr32 doesn't help because a few minutes later KAV overwrites the entries in the registry again.
Other script-based programs seem to have no problems with this re-direction. It's only DesktopX that's crashing.

It would be really nice if this could be fixed in DesktopX.

Greetings
Jets

Successfully updated karma reason!

Script blocking will do that.

When I had Norton - script blocking would cause warnings on DTX - once allowed, no problems

Running pc-cillin - no problems with DTX

Since KAV is the one manipulating some entries, would it not be more of a AV problem than DTX?
No way to configure KAV to allow the DTX scripts, since you have no problems with others?

Successfully updated karma reason!

Basically, I agree with you, Bichur. KAV changes the registry entries, therefore it causes the trouble.
On the other hand, I think this could be a general issue when using DesktopX and anti virus software. I assume other anti virus programs install similar hooks in the registry to catch calls to the vbscript.dll or jscript.dll - you already mentioned Norton.
Even when script checking/blocking is disabled in KAV, the link to scr_ch_pg.dll will be installed. I've checked the KAV forum and it seems nobody has a problem with the way KAV handles script scanning. Other script-based software runs without problems on my system as well.
Of course I don't blame Stardock if another software manipulates the registry but I believe there's a work-around or no script-based software would run on my system.
If this work-around could be implemented in DesktopX it would probably solve Nigel's problem too.

Greetings
Jets

Successfully updated karma reason!

Sign Up or Login and this ad disappears!
There are many great features available to you once you register. Sign Up for a free account and browse the forums without ads.

have you tried rerunning scripten 5.6 from MS?

Successfully updated karma reason!

ZubaZ

Join Date 11/2001

+917

At this point you have stepped outside the forums community support and have entered the Stardock world. Go to https://www.stardock.helpserve.com and create a case there with all sorts of info. Versions of both apps and the notes you have posted here should be useful.

Successfully updated karma reason!

@Bichur

Re-installing the scripting host software doesn't help (I tried that too).
Registering the two dlls with regsvr32 is all you need to do. Everything is fine then until you start KAV because it re-installs the hooks and DesktopX will crash the next time it performs a call to one of the scripting dlls.

Greetings
Jets

Successfully updated karma reason!

Since Norton had an 'allow always' option, I'm wondering... does KAV have that option or maybe an 'ignore' or 'exclude' option (to maybe ignore everything in 'Stardock'?

and Z's right, it's probably time to head towards helpserve

Successfully updated karma reason!

I've tried everything KAV is offering but it was useless.
Actually, KAV doesn't seem to block anything at all (no entry in the log, etc.).
For instance, when I try to create a new script in DesktopX it crashes. Hence a new script is
empty there can't be any dangerous content to block.

I'll see what helpservice can do...

Greetings
Jets

Successfully updated karma reason!