to Sfor and Multibooter and all others ...
FYI: I did some testing of Opera 9.60 and its recent Shell\Open and/or DDE bug. Wondering if you get the same errors as any of these that I noted? Methodology: Opera was verified to be closed, one file manager was opened, a .MHT test file selected, and [ENTER] was pressed.
Result = whether the MHT file successfully opened into an Opera tab, and,
MsgBox = any message returned complaining about the Shell/Open action ...
;--------------------------------------------------------------------------------
application: Tracker v3.60.0030 ...
result: SUCCESS
msgbox: NONE!
;--------------------------------------------------------------------------------
application: XYplorer v7.00.0000
result: SUCCESS
msgbox: NONE!
;--------------------------------------------------------------------------------
application: nViPER.@bOX v0.0.0.401
result: SUCCESS
msgbox: NONE!
;--------------------------------------------------------------------------------
application: WinNC Next Commander v3.00
result: SUCCESS (NOTE: it opened it in two tabs! verified again)
msgbox: NONE!
;--------------------------------------------------------------------------------
application: Windows Explorer v4.72.3612.1700
result: SUCCESS
msgbox: Cannot find the file "TEST.MHT" (or one of its components). Make sure the path and filename are correct and that all
required libraries are available.
;--------------------------------------------------------------------------------
application: BenniSoft LCARS FileManager v0.11.049
result: SUCCESS
msgbox: Cannot find the file "TEST.MHT" (or one of its components). Make sure the path and filename are correct and that all
required libraries are available.
;--------------------------------------------------------------------------------
application: PowerDesk v6.0.4.2
result: SUCCESS
msgbox: Access to the specified device, path, or file is denied
;--------------------------------------------------------------------------------
application: WinAbility AB Commander v6.6
result: SUCCESS
msgbox: Access to the specified device, path, or file is denied
;--------------------------------------------------------------------------------
application: WinFile Win98se v4.10.1998 and
WinME v4.90.3000
result: SUCCESS
msgbox: File Manager cannot find the specified file (or one of its components).
Make sure the path and filename are correct and that all required libraries are available.
;--------------------------------------------------------------------------------
application: Total Commander v6.52
result: SUCCESS
msgbox: File not found!
;--------------------------------------------------------------------------------
All of the file managers actually do work, that is, they do pass the filename to the shell which opens the file as instructed by these registry keys:
[HKEY_LOCAL_MACHINE\Software\Classes\.mht]
@="Opera.MHTML"
[HKEY_LOCAL_MACHINE\Software\Classes\Opera.MHTML\Shell\Open\Command]
@="\"C:\\WinApps\\Opera\\096010447\\Opera.exe\" \"%1\""
;;; here are the DDE entries shown for completeness sake although
;;; I do not believe this branch is called during this test ...
[HKEY_LOCAL_MACHINE\Software\Classes\Opera.MHTML\Shell\Open\DDEexec]
@="\"%1\""
[HKEY_LOCAL_MACHINE\Software\Classes\Opera.MHTML\Shell\Open\DDEexec\Application]
@="Opera"
[HKEY_LOCAL_MACHINE\Software\Classes\Opera.MHTML\Shell\Open\DDEexec\Topic]
@="WWW_OpenURL"
Since the requested file
does get displayed in Opera (note that it opens in two tabs under WinNC), the only real problem is that nuisance MsgBox produced by the caller application in all but four of the tests. Another point, this MsgBox is not spawned from Opera, it is from the calling app. Even though during the Explorer test the MsgBox does not mention
Explorer in its title, during the PowerDesk test it clearly mentions
PowerDesk Pro.
Several have identical errors indicating they use the same function to pass the filename over to the shell:
Windows Explorer and
BenniSoft LCARS FileManager. Also
PowerDesk and
WinAbility AB Commander. And of course both the
Win98se and
WinME versions of WinFile.
I had hoped a simple patch to the parsing of the
Shell\Open\Command string would solve this but I think the variation in results under this test implies that fixing that registry string so that it works for one program (e.g., Explorer) will likely break it for others. But that is still a hunch at this point.
This does not mirror exactly the previous testing in this thread with URL shortcuts, but I figured this would help narrow the list of suspects down by eliminating the HTTP registry keys as variables. But please anyone chime in with ideas about this. I'm just offering up some data at this point and I hope someone else will notice something I missed.