The GNUCASHPORTABLE keeps being blocked by my antivirus program. i have read several different antivirus has it classified as a trajan VBS/PSYME GE
details on it are as follows:
Virus Encyclopedia
Welcome to the Virus Encyclopedia of Panda Security.
Psyme.GE
Threat LevelHigh threatDamageSevereDistributionNot widespread
At a glanceTech details | Solution
Common name: Psyme.GE
Technical name: VBS/Psyme.GE
Threat level: Medium
Type: Trojan
Effects: It allows to get into the affected computer.It does not spread automatically using its own means.
Affected platforms:
Windows XP/2000/NT/ME/98/95
First detected on: Sept. 3, 2007
Detection updated on: Sept. 3, 2007
Statistics No
Brief Description
Psyme.GE is a Trojan, which although seemingly inoffensive, can actually carry out attacks and intrusions: screenlogging, stealing personal data, etc.
Psyme.GE does not spread automatically using its own means. It needs an attacking user's intervention in order to reach the affected computer. The means of transmission used include, among others, floppy disks, CD-ROMs, email messages with attached files, Internet downloads, FTP, IRC channels, peer-to-peer (P2P) file sharing networks, etc.
anyone else having this same problem? please post if you can help with this. thanks
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
"Windows XP/2000/NT/ME/98/95"
Unless you are running one of these old, unsupported, operating systems I wouldn't worry about it.
You might want to consider updating or replacing your AV app though.
Ed
It's a false positive in the F-Prot scanning engine. You'll need to report it to your antivirus vendor for them to fix.
You'll note that only F-Prot and Commtouch (which licenses the F-Prot engine for their product) alert on it: https://www.virustotal.com/en/file/5f50abb20bb0ef8787d89eb8f88da709d4fa3...
The error is with the F-Prot product and isn't something we can fix on our end. Please note: F-Prot is slow to fix errors of this nature.
Sometimes, the impossible can become possible, if you're awesome!
Destry: You don't say what version of GnuCash so I'm presuming 2.6.3 from this site rather than some other place; if so it is your AV that is behind as John says.
Ed P: it has nothing to do with the WinOS, I'm compiling/building GnuCash on WinXP a few times a week and I haven't seen it take any notice of which WinOS it is on at all in any of the code I've looked at. Further, the current build from scratch process under Win is only known to work on XP so far, i.e. "one of these old, unsupported, operating systems" like XP is actually *required* to build GnuCash and anyone using a recent binary Gnucash on Win is probably using one "tainted" by XP because even with a cross-compile XP in a VM is the reference Win used by the GnuCash people.
Wm
"XP is actually *required* to build GnuCash "
Thanks for the info Wm.... I was considering trying gnucash, I use an old version of Quicken, and didn't realize it required XP.
Thanks again.
Ed
It's required to *build* GnuCash, not run it. Quite a few apps have very specific build environments, often on VMs that aren't connected to the internet. GnuCash runs fine on Windows XP through Windows 8.
Sometimes, the impossible can become possible, if you're awesome!
Thanks John, I appreciate the clarification.
PEBuilder was designed to run on Windows XP but runs fine on Windows 7, if a single Windows XP file is included in the app's build folder. Is that the case with GnuCash or has no one looked into this?
And Wm... why does GnuCash need to be recompiled every week?
Ed
GnuCash works on Windows XP to Windows 8 as distributed without modifications of any kind. Everything being discussed above is related to compiling GnuCash, not running it.
Wm.. is working on a modification of GnuCash to allow Python support on Windows if I recall correctly. It's unrelated to the bug reported in this topic.
Sometimes, the impossible can become possible, if you're awesome!
As John says, I am working on a Win native GnuCash+Python because it can't be cross-compiled (at least not until someone works out how to do it) and there are no repeatable instructions for doing it natively though there are stories of it having been done before with earlier versions.
There is no reason why GnuCash (not including Python) shouldn't compile+build on other WinOS except that no-one has got around to trying very hard. It isn't a priority for the GnuCash devs as WinOS isn't their home. The code itself is platform independent, e.g. I have needed to change exactly one line in the actual GnuCash code: I changed "const char" to "static const char" in one .c file in the test suite which doesn't even get compiled into the distribution binary. I've done a lot of tinkering with the Python environment by contrast.
In case I gave the wrong impression GnuCash isn't welded to WinXP or any WinOS at all, it doesn't know or care, WinXP is just a convenient environment to build it in as later WinOS seem to introduce more env complications to build around is all and the latest fancy Win-bits aren't in *that* much demand if double-entry is your expectation of good accounting!
Ed P: Quicken does accounting wrong, that is why it is a personal finance manager
Ducks and runs.
Hope that tides a few things up, but I thought I was doing that with my last post here. Certainly didn't mean this thread to go on.
P.S. I use GnuCash Portable for real-life accounts which allows me to mess about with live builds to my hearts content without the two environments getting mixed up. A possibly unusual situation where the PortableApp is a convenient, known to work, safe environment while I beat an experimental build environment with sticks. You can quote me on that, John.
Wm
I appreciate your follow-up.
Ed