F-PROT Antivirus for Windows 64bit open beta

[Oliver]

Hi fellows,

I am pleased to announce on behalf of the team, that we have an open beta waiting for you here on the forum server.

Some basic rules for beta-testing, though:

• Don't use it on production machines!
• Don't install the beta in conjunction with another Antivirus program.
• If you want a stable and well-tested version, wait for the public release, don't beta-test!
• Please report any found bugs or issues via the support channels. Mention the keyword "litli geysir" in the request, so it gets forwarded to us more quickly.
• If the program would crash, you will see a dialog with an error message. We'd like you to send us the bugreport, if you participate in the beta. However, if you deem certain data fields in the bugreport confidential, you can also save the report and edit it (it's located in the same directory as the program itself, i.e. usually %ProgramFiles%\FRISK Software\F-PROT Antivirus for Windows)
• Given you encounter problems, please also check the program folder for .dmp files and send them to support as well (using the keyword).

The MD5 hash of the download is 245eef168020b95470bf1116115f7b79

Compatibility: this version should work on XP, 2003 Server and Vista for the x64 platform (that is AMD and Intels most recent processor series and running the 64bit operating system).

Download: http://forum.f-prot.com/public/245eef168020b95470bf1116115f7b79_fpav-windows-x64-hc-en.msi (out of beta, follow this link)

Known bugs and issues:

• The updater might signal an update to be available under certain circumstances, but will report that none was downloaded and report that the system is up-to-date (in progress)
• The DEF file update will complain about a mismatch between the product and the product key (in progress)
• Stability issue in "Advanced Tasks" (in progress)

We'll add to this list, while reports trickle in. Hotfixes to this beta will be made available here in the forum as well. Thanks to all participants in advance.

One note: the support team is of course not here during the weekend, so if the beta causes problems which require phone support or similar, that will have to wait until Monday. That's, by the way, the reason why we don't usually release anything at the end of the week in case there is an urgent problem to solve.

Feel free to comment on it or even discuss encountered issues here in this thread.

[karlfoley]

It's great that we now have a beta - thanks.

Apart the problems noted in your post, I have only come across one small problem so far. I started a manual scan and went to look at a few other tabs, but when I went back to the manual scan tab, it wasn't showing any progess, just blank with everything at 0.

I checked back later, when the scan was complete, and it was showing the correct number of files.

[Oliver]

Thanks, we're going to check that out. But today - or rather tonight - we'll have the FRISK xmas-party, so don't expect any results till Monday when (and if) the hangover is gone

[karlfoley]

Hope you had a great Xmas party - I miss them now I work on my own!

Anyway, I've had approximately 5 Stop 0x50 BSOD now.
They were all quoting FPAV_RTP.SYS on the BSOD.

Problem signature:
  Problem Event Name:   BlueScreen
  OS Version:   6.0.6000.2.0.0.256.1
  Locale ID:   2057

Additional information about the problem:
  BCCode:   50
  BCP1:   FFFFF88405800D00
  BCP2:   0000000000000000
  BCP3:   FFFFF9800848EAAC
  BCP4:   0000000000000005
  OS Version:   6_0_6000
  Service Pack:   0_0
  Product:   256_1

Files that help describe the problem:
  C:\Windows\Minidump\Mini112407-06.dmp
  C:\Users\karl.THEFOLEYHOUSE\AppData\Local\Temp\WER-85644-0.sysdata.xml
  C:\Users\karl.THEFOLEYHOUSE\AppData\Local\Temp\WERE703.tmp.version.txt

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

[Faik]

I think that Oliver (and the others on the team) would be interrested in geting the minidumps i.e. "Mini112407-06.dmp". The following thread explains what to do.  http://forum.f-prot.com/index.php/topic,158.0.html


PS: Excuse my spelling   


/Faik

[Oliver]

Hi,

indeed we'd need the respective dump and the other two files would be nice along with the dump. Up to now we had this problem only in conjunction with third-party software which was actually forcing the bluescreen by not playing by the rules. But I'll not rule out completely that there is a problem in our driver here - it's been created by humans

So if you could be so kind to send us the minidump, we'd be able to look into it. Anything else would be guess-work and probably in vain.

[karlfoley]

I cant supply that exact one, but I will supply the last set, from the last crash.
Windows seems to keep all the mini-dumps but only the last 4 or 5 txt\xml files.
I had a total of 10 BSOD on that machine before I pulled the beta off.

[Oliver]

Thanks, that would be nice. The XML/TXT shouldn't change at all, but the minidump would probably change slightly. Nothing received so far, so we'll keep waiting.

[Uze DaFarce]

This has been working great for me (XP Pro x64 SP 2) except for known issues. 

However, our signature files are now 6 days old, and they are beginning to look (and smell) like a refrigerator science experiment.   

[Oliver]

We're going to solve this particular issue on the server-side and it's supposed to work starting tomorrow. Didn't want to risk any experiments that late today in case it shows unforeseen side-effects

[Uze DaFarce]

Still not working today, maybe tomorrow?

[ryanri]

Hello! Thanks for the beta, been waiting for it! I was not able to update yesterday with a key/product error message. Now I am still not able to update but with no error message, it just sits attempting to "check for updates".

Not sure if that is a known issue or not.

also, is it just the core(service) that is 64bit? I ask because it looks like the tray icon is running under 32bit.

Thanks and keep up the good work!

[Oliver]

Having the guys look into it. Thanks. Was supposed to work by yesterday.

also, is it just the core(service) that is 64bit? I ask because it looks like the tray icon is running under 32bit.

Indeed. We're making use of WOW64.

[nheimler]

Having the guys look into it. Thanks. Was supposed to work by yesterday.

Anymore info on the issue with the subscription key mismatch issue?  I'm still having this on my box.  Thanks!

[nheimler]

Cool started working for me just now.