|
CrimsonJD
Posts: 6
|
 |
« on: 20 Mar '10 - 14:31 » |
 Quote
|
When I try to run xmplay 3.51 on Windows 7 64 bit, I get the "This file has been tampered with and MAY BE INFECTED BY A VIRUS!" message. I do have Comodo Firewall installed, but I even tried disabling defense+, then closing Comodo, then re-downloading the zip file and re-extracting the executable, and I still get the error.
The weird thing, and what makes me think it isn't Comodo, is that if I run the program as administrator, or run it in windows XP compatibility mode, xmplay runs fine and I don't get the error. (Vista compatibility mode shows the error) The problem is that both running as administrator and running in XP compatibility mode bring up a UAC screen that I have to approve. If I have to do that every time I run the program it would be pretty unusable.
Is there anyone who actually has 3.51 running under 64 bit Windows 7 and can advise?
Thanks!!
|
|
|
|
|
Logged
|
|
|
|
|
Dotpitch
Posts: 2472
|
|
« Reply #1 on: 20 Mar '10 - 16:04 » |
Quote
|
When I try to run xmplay 3.51 on Windows 7 64 bit, I get the "This file has been tampered with and MAY BE INFECTED BY A VIRUS!" message. I do have Comodo Firewall installed, but I even tried disabling defense+, then closing Comodo, then re-downloading the zip file and re-extracting the executable, and I still get the error. You have to permanently disable Defense+ and probably reboot as well. Comodo does not change xmplay.exe, so re-downloading won't help. Ian, could you shed some light on what Comodo is actually doing to trip Petite's protection? The weird thing, and what makes me think it isn't Comodo, is that if I run the program as administrator, or run it in windows XP compatibility mode, xmplay runs fine and I don't get the error. (Vista compatibility mode shows the error) It may very well be that running a program with admin credentials or in XP compatibility mode bypasses the whole Defense+ system. According to this thread at the Comodo forums, Vista compatibility mode seems to be disabled by Comodo on Win7 x64, which may explain why it does give the error. |
|
|
|
|
Logged
|
|
|
|
|
CrimsonJD
Posts: 6
|
|
« Reply #2 on: 20 Mar '10 - 17:19 » |
Quote
|
It may very well be that running a program with admin credentials or in XP compatibility mode bypasses the whole Defense+ system. According to this thread at the Comodo forums, Vista compatibility mode seems to be disabled by Comodo on Win7 x64, which may explain why it does give the error. Thanks for the advice. I ended up just uninstalling Comodo. That fixed the problem right up. You're right, it turns out it was screwing with Vista compatibility modes as well (I also encountered the problem with windows live messenger mentioned in the comodo thread you referenced). This is beyond the scope of this board, probably, but is there a better firewall I should use?  One bug I continue to see: the integration section of the options don't seem to work to integrate into windows explorer. Of course this isn't a big deal since I can just do it manually. (any command line switches I should know about for that?) Best |
|
|
|
|
Logged
|
|
|
|
|
Dotpitch
Posts: 2472
|
|
« Reply #3 on: 20 Mar '10 - 18:24 » |
Quote
|
One bug I continue to see: the integration section of the options don't seem to work to integrate into windows explorer. Do you mean the file associations don't work at all? Not for file types, and not for the context menu? Of course this isn't a big deal since I can just do it manually. (any command line switches I should know about for that?) If you untick 'Allow multiple instances', you can pass files to XMPlay from the command line. A more elegant way is to use DDE commands ([open(%1)] and [list(%1)]), which is how XMPlays own integration works. You might like to get the XP-like file association dialog back in Win7 with ExtMan . |
|
|
|
|
Logged
|
|
|
|
|
CrimsonJD
Posts: 6
|
|
« Reply #4 on: 21 Mar '10 - 11:54 » |
Quote
|
One bug I continue to see: the integration section of the options don't seem to work to integrate into windows explorer. Do you mean the file associations don't work at all? Not for file types, and not for the context menu? I played with it a little more. Apparently when xmplayer adds an association, when the type is already associated (at least with windows media player), it doesn't automatically become the _default_ player, but you still have to right click on the file and select "open with->xmplayer". Also, when the default player is windows media player, the context items don't show up on the context menu. When I clicked on "open with->choose default program" and select xmplayer, only then do all the items show up on the context menu. Is this the expected behavior? It basically solves my problem, but it might be nice to be able to have context menu options (play with xmplayer, add to xmplay-list) without actually having xmplayer as the default association. |
|
|
|
|
Logged
|
|
|
|
|
cerealkiller
Posts: 98
|
|
« Reply #5 on: 21 Mar '10 - 13:20 » |
Quote
|
The newest stuff version fixed my problem with the new comodo and xmplay just incase anyone was wondering. And yes im running win7 64 and comodo 4 as well.
|
|
|
|
|
Logged
|
|
|
|
|
CrimsonJD
Posts: 6
|
|
« Reply #6 on: 22 Mar '10 - 12:57 » |
Quote
|
The newest stuff version fixed my problem with the new comodo and xmplay just incase anyone was wondering. And yes im running win7 64 and comodo 4 as well.
Can you be more specific about which new version you mean? On the Comodo website the latest download seems to be March 3. Is there some sort of update which will make this work correctly? Thanks. |
|
|
|
|
Logged
|
|
|
|
|
cerealkiller
Posts: 98
|
|
« Reply #7 on: 22 Mar '10 - 14:23 » |
Quote
|
Was referring to the Xmplay stuff version which can be found here http://www.un4seen.com/stuff/xmplay.exe. The thing is though once i shutdown my comp and restarted it it started giving the error again, it works fine after i download it but the first time i log off or shutdown and then get back on it just starts giving the error. |
|
|
|
|
Logged
|
|
|
|
|
Ian @ un4seen
Administrator
Posts: 15244
|
|
« Reply #8 on: 22 Mar '10 - 16:52 » |
Quote
|
You have to permanently disable Defense+ and probably reboot as well. Comodo does not change xmplay.exe, so re-downloading won't help. Ian, could you shed some light on what Comodo is actually doing to trip Petite's protection?
I haven't tried Comodo myself, so I'm not sure what it is doing exactly, but I guess it must be modifying the file in memory to trigger the "tampered" message. If someone can tell me what to download (and any settings required) to reproduce the problem, I'll look into it |
|
|
|
|
Logged
|
|
|
|
|
Dotpitch
Posts: 2472
|
|
« Reply #9 on: 22 Mar '10 - 21:21 » |
Quote
|
I haven't tried Comodo myself, so I'm not sure what it is doing exactly, but I guess it must be modifying the file in memory to trigger the "tampered" message. If someone can tell me what to download (and any settings required) to reproduce the problem, I'll look into it You can get the installer here. The default settings should already be problematic. |
|
|
|
|
Logged
|
|
|
|
|
Ian @ un4seen
Administrator
Posts: 15244
|
 |
« Reply #10 on: 23 Mar '10 - 17:21 » |
Quote
|
OK. I installed that (with default options) on a Win7 (32-bit) system, but I had no problem running XMPlay with it. I tried the 3.5 and 3.5.1 releases, as well as the latest "stuff" version. Does the problem only happen on 64-bit systems? If so, I'll try that later.
|
|
|
|
|
Logged
|
|
|
|
|
Dotpitch
Posts: 2472
|
|
« Reply #11 on: 23 Mar '10 - 18:11 » |
Quote
|
Does the problem only happen on 64-bit systems? If so, I'll try that later. The users who reported the problem were all using Win7 x64, so I think it's limited to 64-bit indeed. |
|
|
|
|
Logged
|
|
|
|
|
cerealkiller
Posts: 98
|
|
« Reply #12 on: 23 Mar '10 - 23:04 » |
Quote
|
Yes im having the error and its on 64 bit win 7.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
cerealkiller
Posts: 98
|
|
« Reply #14 on: 7 Apr '10 - 03:28 » |
Quote
|
I have the same version of CIS as you do and i still get the error.
|
|
|
|
|
Logged
|
|
|
|
|
winner
Posts: 193
|
|
« Reply #15 on: 7 Apr '10 - 05:17 » |
Quote
|
I have the same version of CIS as you do and i still get the error.
Maddening, isn't it!  I suppose you've done a full uninstall and reinstall of Comodo CIS? Be sure to delete related folders if they weren't deleted by the uninstall program. |
|
|
|
|
Logged
|
|
|
|
|
Elrinth
Posts: 103
|
|
« Reply #16 on: 19 Apr '10 - 15:56 » |
Quote
|
"Is there anyone who actually has 3.5X running under 64 bit Windows 7 and can advise?"
I have xmplay running on winxp pro x86 and win7 pro x64.
I have no problem whatsoever with the program. Except some of the skins are weird when u drag xmplay around.
|
|
|
|
|
Logged
|
|
|
|
|
logitech1975
Guest
|
|
« Reply #17 on: 23 Apr '10 - 08:02 » |
Quote
|
right click xmplay.exe then properties. set compatibility to windows XP SP3 or Vista. It will work.
|
|
|
|
|
Logged
|
|
|
|
|
logitech1975
Guest
|
|
« Reply #18 on: 23 Apr '10 - 08:03 » |
Quote
|
I'm running win 7 x64 ultimate. Just set the compatibility mode to XP or Vista.
|
|
|
|
|
Logged
|
|
|
|
|
saga
Posts: 1362
|
|
« Reply #19 on: 23 Apr '10 - 09:29 » |
Quote
|
You don't need compatibility mode. XMPlay is fully compatible with Win7.
|
|
|
|
|
Logged
|
|
|
|
|
