It looks like I've succeeded in attaching the zipped file here this time. I'll see if it's still attached when I submit.
It looks like that worked.
You can ignore the .hta file. I'm pretty sure it was an original file that was cannibalized for the new purpose. And the .html file could probably be replace with something whose body contains one header and one data element. But in any case, I don't think it contains anything that is causing the ActiveX error.
@pokeefe0001 What version of MediaMonkey (3? 4? 5?) are you using and what version of the SongInformationPanel (1.6? 2.0?)?
On both Windows 7 and Windows 10, with no MediaMonkey installed, I got the same error you posted. I installed MediaMonkey_3.2.6.1307.exe and SongInformationPanel2.0.0.1.mmip on both Windows 7 and Windows 10 and then it worked without error on both systems. Once I hear back regarding which versions you're running, I'll test again.
I'm afraid the answer to both questions is "No".
The installation that works is MM 2.5 running on Win7. I want to get it to work in MM 4.1 on Win10, but first I'm trying for MM 2.5 on Win 10. I've got MM 2.5 installed on a desktop, MM 3.? installed on a laptop, and portable MM 4.1 on a USB flash memory "drive".
I have no idea what the original version of SongInformationPanel was, but it's been changed by at least 2 - probably 3 - people before I got it. The last change was in 2011 (I think) so the original has to be pretty ancient.
- - - Updated - - -
Hmm. When you installed MediaMonkey did you get an mmscript.ocx registration error? I got it with all MM installations on Win10 and have no idea if my manual registration did what was required.
No mmscript.ocx registration error. I got a "COM Elevator" UAC prompt to which I clicked Yes. MM 5 did not work, but MM 3 and MM 4 were fine. I don't think MM 4 portable will work, but didn't try.
For quick testing, I renamed SongInfo.htm to SongInfo.hta so I could just double-click it and have it run via MSHTA. The DockInfo.vbs script has the line "Set WB = SDB.UI.NewActiveX(Form, "Shell.Explorer")". I'd have to do more investigating, but this probably invokes Internet Explorer instead of MSHTA. I have uninstalled IE from my machine, but MSHTA continues to work (the HTML rendering engine is part of the OS and still included with Windows 11). I mentioned this in case it accounts for any differences in our testing.
Also see: ActiveX Browser Version [#7383] - MediaMonkey forum
While you are waiting for the ActiveX experts to respond, do check that Microsoft Defender [WD] does not show anything in Protection history about that .hta file or your script itself.
I used to use hta but had to drop it in Windows 10 because WD was such a pig about it. At that time, I did not know about WD Exclusions so these guides might prove useful.
Add or Remove Windows Defender Exclusions - TenForumsTutorials
Add an exclusion to Windows Security - MSSupport
Best of luck,
Denis
The error would be quite different if the HTA file was being caught in Defender's net. I just dealt with this issue for WinSetView.hta. I had to file a false positive report with Microsoft. They adjusted their definitions, so it's all okay now. For the issue in this thread, the current script is running SongInfo.htm (via IE I think). I renamed it to hta (like the older version) for easier testing.
I don't use IE (or Edge) but I see that some maintenance helpfully replaced IE with Edge so directly invoking IE could be a problem. I can't find it now, but I recently ran into an MM script that directly invoked MSHTA. I'll try to find that and see if I can use that technique, but I have other stuff I need to get to for the rest of the day so this is going on the back burner for a while.
Quote
