Nod32 and VirtualPC 2007

Discussion in 'NOD32 version 2 Forum' started by virkelie, Apr 7, 2007.

Thread Status:
Not open for further replies.
  1. virkelie

    virkelie Registered Member

    Joined:
    Jan 29, 2005
    Posts:
    77
    Is Nod32 compatible with Windows95 in VirtualPC 2007?

    I downloaded and installed the trial version of Nod32 (for windows 95), into Microsoft VirtualPC 2007.
    Host Operating System: XP Pro
    Guest Operating System: Windows 95

    I was getting VERY frequent blue screens with a variety of error messages, but mostly "VXD VMM(01)" errors:

    -A fatal exception 0E has occurred at 0137:BFF9A141
    -A fatal exception 0E has occurred at 0000:0000006B. The current
    application willl be terminated.
    -A fatal exception OE has occurred at 0028:C00046A0 in VXD VMM(01) +
    000036A0. The current application willl be terminated.
    -A fatal exception OE has occurred at 0028:C00060F4 in VXD VMM(01) +
    000050F4. The current application willl be terminated.


    The errors and blue screens stopped after uninstalling Nod32.

    Does anyone know if Nod32 for windows 95 can work inside Microsoft's Virtual Machine 2007?

    Thanks for any help.
     
  2. joel406

    joel406 Registered Member

    Joined:
    Aug 21, 2006
    Posts:
    43
    I dont know of any reson to run Win95, even virtually.

    I run MSVPC2k7 Vista ult, on Vista ult. Have no problems running NOD32, no crashes just perfection.

    I wonder..are you running Win95 virtually in fat32?

    I guess you have to.

    Probably a conflict since the Win95 install has to connect to the internet through the xp host install. Its probably confusing the different versions of NOD32 while trying to update.

    Just a guess. Hope it at least gives you an idea or direction to solve your problem.
     
  3. virkelie

    virkelie Registered Member

    Joined:
    Jan 29, 2005
    Posts:
    77
    The reason to run Win95 virtually:
    1. I have old programs I still like to run.
    2. I have old DOS games.
    3. For nostalgia.


    "I wonder..are you running Win95 virtually in fat32?"

    I really don't know.
    I don't know how Virtual PC runs Win95 in the XP host.
     
  4. joel406

    joel406 Registered Member

    Joined:
    Aug 21, 2006
    Posts:
    43
    Well first I appologise for taking so long to reply.

    I got a feeling that since you have a virtual install of Win98 that you probably installed the Win98 NOD32 release. They may have a problem when it comes to updateing. The checksums probably conflict and I thimk it basicly confusing the program. I would try disableing auto update in the Win95 install and just do it manually for awhile and see if that helps.

    If not let us know and I will try to see what else I can figure out.
     
  5. virkelie

    virkelie Registered Member

    Joined:
    Jan 29, 2005
    Posts:
    77
    When I try to update manually, I will get (though not always) a blue screen with an error of the type I mentionned previously.

    Even adjusting the settings in Nod32 will provoke a blue screen error.

    I also tried the program, again in Windows 95, but using Virtual PC 2004 (instead of 2007). Same errors.

    The errors also appear at random (but frequently) when browsing with internet explorer; and dissapear after uninstalling Nod32.

    I tried AVAST - the only other windows 95 antivirus program I could find - same errors.

    So the problem is not specific to Nod32 - for some reason, Windows 95 in a virtual PC does not like antivirus programs.

    I finally found F-Prot for DOS - no problems so far - but it is only an on-demand scanner.
     
  6. FirePost

    FirePost Registered Member

    Joined:
    Jul 29, 2005
    Posts:
    212
    Hello virkelie,
    Did you install Winsock2 for the w95 client? Many of the later compatible programs required this.
     
  7. virkelie

    virkelie Registered Member

    Joined:
    Jan 29, 2005
    Posts:
    77
    Actually that was a good suggestion - I was checking the microsoft site and saw that the winsock 2 update contains some .vxd files (the errors I had been getting includes "VXD VMM" errors, so I got excited for a moment, thinking lack of winsock2 was the reason for the problem).

    But in fact I already have winsock2 - I have a file in my windows folder,
    "ws2setup.log", which confirms that winsock 2 had already been successfully installed.
     
  8. RejZoR

    RejZoR Registered Member

    Joined:
    May 31, 2004
    Posts:
    6,426
    If you need Win9x environment i'd certanly choose Win98 or Win98 SE. These are ultra polished Win95 systems...
     
  9. YeOldeStonecat

    YeOldeStonecat Registered Member

    Joined:
    Apr 25, 2005
    Posts:
    2,345
    Location:
    Along the Shorelines somewhere in New England
    DUN 1.4 also....although I haven't suffered through dealing with Win9X in ages.

    For those legacy games...get DosBox from Sourceforge...can get any cranky clunky old DOS app to run in that within 2K/XP.
     
  10. FirePost

    FirePost Registered Member

    Joined:
    Jul 29, 2005
    Posts:
    212
    Well it was worth a shot. Is that the updated version?

    How about this one? Which version of explorer is running? W95 had IE 3.0
    For AVAST
    For NOD32
     
  11. virkelie

    virkelie Registered Member

    Joined:
    Jan 29, 2005
    Posts:
    77
    Winsock 2 (this is the most recent version, for win95, as far as I know), is installed.

    Internet explorer 5.5 is running.

    S3 Trio 32/64 PCI Super VGA (SVGA) card is emulated in VPC 2004.
     
  12. virkelie

    virkelie Registered Member

    Joined:
    Jan 29, 2005
    Posts:
    77
    Someone suggested I try AVG free, even though according to its own documentation, Windows 95 is not supported.

    Well, it works! No blue screens so far in VirtualPC.

    So I guess I'll stick with this; but scanning is MUCH slower than with Nod32.
     
Thread Status:
Not open for further replies.