quote:
This is starting to stray far afield I fear
Not too far. We're trying to find what's on your system that is unique and interfere's with WW. Unique in that you are the only one to report this problem. There may be others. If we can pinpoint the problem we may be able to determine a fix.
quote:
tell it to integrate with the shell
This is where we differ, I have nothing integrated into my Explorer shell. I have some integrated into IE but not WE. I also use WinZIP rather than WinRAR, and that is a left over from my Win 98 days since Win XP has ZIP decompression built in.
I’m not sure what you gain from having WinRAR or QuickSFV hooked into the Explorer shell rather than into WE or simply as standalone apps. But I have no files on my Desktop, only shortcuts.
quote:
...in the bottom pane you'll see all the DLL's that are involved with Explorer. .... Right now, I have 41 in total hooked into Explorer.
Well I just found a feature that Process Explorer could add to it's display, number of entries listed. Good grief, I have 115 DLLs listed in the bottom window associated with Explorer.exe of which 9 begin with the letters "MS", none of which are msvbvm60.dll. Process Explorer also shows Explorer has 408 Handles and I have no idea what that means.
quote:
I know the apps that invoke it on my system,
Are you running the current version of the app in each case?
quote:
the mystery is why they're doing that
They're written in Visual Basic, and an older version if I'm not mistaken.
quote:
why does running, say, OE invoke it while on your system and my virtual one, it does not?
Because, in this case, you selected the option to have a VB app linked to OE during it's install. Since WinRAR works with email files I would think it would be the one but that's strickly a guess.
quote:
I'm wary of the idea of renaming the file and rebooting, since I don't see what I'll learn from it.
The thought was by renaming it a single app would fail thus identifying the culprit of the conflict. But if you have many VB apps it would not be as useful as hoped for.
Another approach would be to use MSCONFIG to limit what starts, since things that hook into Explorer like WinRAR automatically start. [:)] And in Windows XP, nothing on the startup tab of MSCONFIG has to start when Windows does. All vital system processes have been removed from that section. So in theory you can disable them all and still start Windows just fine. I would start with WinRAR, disable it, reboot, try WW. If it works we know the conflict. If not, bring MSCONFIG back up and disable another process. Repeat until WW runs. Then reenable all but the last task and repeat. If WW still starts then we know the conflicting app.
You can then check to see if you have the latest version, contact the author of the app and see if they are aware of any conflicts, inform Singer so he can test it out on his system, and rest easier knowing the problem has been identified. [:D]
quote:
Anything to try here?
Aren't you sorry you asked now? [:D]
quote:
my virtual one
I'm jealous. [:p]
EdP