Installation Problem/Question

Hi,

I've got four current NOD32 licenses, one of them expires this month and the other three in about 2 months, so it was time to think about renewal. I have 3 computers, I'm the only user. One is a dual-boot Win7 machine 32-bit on one drive, 64-bit on the other. The second computer is also Win7, but 32-bit only, and the third is an XP/SP2 machine. I've been using a single license on the dual-boot machine (one for the 32-bit side and one for the 64-bit side) the other two machines have their own licenses, and the fourth license is currently not being used. I ordered a 3-User version from Amazon, planning to use one license on each of the three boxes, and using one of the licenses twice on the dual-boot machine since when I asked here about two years ago, that was said to be legitimate.

A couple of weeks back, I ran across the upgrade to NOD32, v5.0.94 and downloaded that. I installed it on the 64-bit side of the dual-boot machine without any trouble and it's worked fine for me, so in preparation for the renewal, I thought that I would just download the update to v5 and install it across all four platforms, then when the new licenses came from Amazon I could just change the username and password, let things update, and I'd be all set. I did that a year ago and it worked fine.

So, today I downloaded the installer application for what turned out to be 5.0.95 and installed it on the 32-bit side of the dual-boot machine. It's just a test machine so it can be easily restored if need be. Again, the install went as expected and the 32-bit side came up and ran, did the normal boot scans and those worked just fine, everything looked good. I used the username and password that were on the dual-boot machine, the same as was already there on the 64-bit side of the same machine, since that's the one that machine that was going to need the shared license.

I wen't back to the 64-bit side of the same maching, 5.0.94 and it was still working, but there was a link to "Check" or "Check for Updates", at least that's what it seemed to be. I clicked it and it went to the ESET site and picked up the 5.0.95 version and proceeded to install that, really just what I expected to happen, except at the end it uninstalled itself, or at least most of itself, on the 64-bit side. There are still a few files there. The 32-bit side is still working fine under 5.0.95, but on the 64-bit side I get no tooltray icons, no boot scans, no ESET screen, no way to start the program at all in the Start Menu on the 64-bit side at all.

Is it not allowed to use the same copy on a dual-boot machine anymore or have I done something I shouldn't? Any help anyone might be able to give would be greatly appreciated. I can live with only the 3 licenses if need be, but I need to download or run Windows Update through that system and would need to buy another license as it stands.

Thank you!

 

Hello,

On the computer configured for dual-booting of Microsoft Windows 7 32-bit and 64-bit, what are the installation paths for ESET NOD32 Antivirus under each operating system?

Regards,

Aryeh Goretsky

 

Hi agoretsky,

Thank you for the reply, I appreciate it!

WRT the installation paths, I just took the defaults. I've since removed v5 from the 32-bit side and put v4 back, it's still got two months to run. I haven't touched the i386 side at all though, and it seems to be in the same place. The drives are visible to each other, but the system drive is always C: and the other D:. Depending on which OS I boot, C: and D: switch of course.

It wasn't a problem under v4, and actually 5.0.94 was already installed on the 64-bit side and working fine. After I put 5.0.95 on the 32-bit side, it still worked. It wasn't until I let it upgrade the 64-bit side to 5.0.95 that I had the problem, so they did coexist for awhile.

I've since ordered up a 3-user version of v4, I'm just going to let that run for another year, keep the v5 and use them when the 2013 renewal comes due. I don't know what happened, but I can't afford to be without the machin for the next month or so and that seemed the safest thing to do, so it's not really critical that it get fixed. It's been working absolutely flawlessly up 'til now.

In case it's of any use, I've include the ESET folder tree listing from the 64-bit side, it's about half the size of the one for v4/32. Some of the extensions seem to be from an odd character set, but FWIW. There is a reference to an x86 subfolder down there, I don't know if it's significant. I didn't get a .MSI file, just a 1.2 meg installer that seemed to do it from online, could it have thrown in the wrong version? The 32-bit side is back at v4 and probably of no interest so I didn't bother with it.

Thank you again for the reply!

Bob

Code:

// List of what was left of the 5.0.95 install once the upgrade was done...
//
Volume in drive C is unlabeled      Serial number is e87e:7b4d
Directory of  C:\Program Files\eset\*

.            <DIR>      12/05/11 10:33  
..           <DIR>      12/05/11 10:33  
ESET NOD32  <DIR>       1/08/12 23:09  
                 0 bytes in 0 files and 3 dirs

Directory of  C:\Program Files\eset\ESET NOD32 Antivirus\*

.            <DIR>       1/08/12 23:09  
..           <DIR>       1/08/12 23:09  
Drivers      <DIR>      12/05/11 10:33  
eplgHook.d      11976   9/22/11 12:09  
eplgOE   dll    403384   9/22/11 12:09  
eplgOEEm.      254016   9/22/11 12:02  
eplgOutlook    380200   9/22/11 12:09  
eplgOutlook    234952   9/22/11 12:02  
License      <DIR>      12/05/11 10:33  
Microsof.V       1872   8/11/09 13:37  
Microsof.V       2374   8/11/09 13:37  
Microsof.V       1239   9/29/09 10:34  
msvcp80  dll   1068368   8/11/09 13:37  
msvcr80  dll    802640   8/11/09 13:37  
x86          <DIR>       1/08/12 23:09  
         3,161,021 bytes in 10 files and 5 dirs    3,178,496 bytes allocated

Directory of  C:\Program Files\eset\ESET NOD32 Antivirus\Drivers\*

.            <DIR>      12/05/11 10:33  
..           <DIR>      12/05/11 10:33  
epfwwfpr     <DIR>       1/08/12 23:09  
                 0 bytes in 0 files and 3 dirs

 Directory of  C:\Program Files\eset\ESET NOD32 Antivirus\Drivers\epfwwfpr\*

.            <DIR>       1/08/12 23:09  
..           <DIR>       1/08/12 23:09  
epfwwfpr cat      7448   8/04/11  9:20  
EpfwWfpR sys    137144   8/04/11  9:20  
           144,592 bytes in 2 files and 2 dirs    147,456 bytes allocated

    Total for:  C:\Program Files\eset\ESET NOD32 Antivirus\Drivers\epfwwfpr\*
           144,592 bytes in 2 files and 2 dirs    147,456 bytes allocated

    Total for:  C:\Program Files\eset\ESET NOD32 Antivirus\Drivers\*
           144,592 bytes in 2 files and 5 dirs    147,456 bytes allocated

Directory of  C:\Program Files\eset\ESET NOD32 Antivirus\License\*

.            <DIR>      12/05/11 10:33  
..           <DIR>      12/05/11 10:33  
                 0 bytes in 0 files and 2 dirs

    Total for:  C:\Program Files\eset\ESET NOD32 Antivirus\License\*
                 0 bytes in 0 files and 2 dirs    0 bytes allocated

 Directory of  C:\Program Files\eset\ESET NOD32 Antivirus\x86\*

.            <DIR>       1/08/12 23:09  
..           <DIR>       1/08/12 23:09  
eplgOE   dll    340464   9/22/11 12:09  
eplgOEEm.      192144   9/22/11 12:02  
eplgOutlook    299264   9/22/11 12:09  
eplgOutlook    183904   9/22/11 12:02  
eplgTbEm.      179784   9/22/11 12:02  
Microsof.V       1870   8/11/09 13:37  
msvcp80  dll    554832   8/11/09 13:37  
updater  dll    270424   9/22/11 12:11  
         2,022,686 bytes in 8 files and 2 dirs    2,039,808 bytes allocated

    Total for:  C:\Program Files\eset\ESET NOD32 Antivirus\x86\*
         2,022,686 bytes in 8 files and 2 dirs    2,039,808 bytes allocated

    Total for:  C:\Program Files\eset\ESET NOD32 Antivirus\*
         5,328,299 bytes in 20 files and 14 dirs    5,365,760 bytes allocated

    Total for:  C:\Program Files\eset\*
         5,328,299 bytes in 20 files and 17 dirs    5,365,760 bytes allocated
    18,270,806,016 bytes free

// EOF

 

Hello,

I am going to see if one of ESET's QA engineers can reproduce this. Can you tell me a little more about how the hard disk drive was set up in the computer?

Regards,

Aryeh Goretsky

 

Hi Aryeh,

>> I am going to see if one of ESET's QA engineers can reproduce this. Can you tell me a little more about how the hard disk drive was set up in the computer? <<

Sure. It's really nothing special....

It's a Gigabyte 880GMA-UD2H motherboard, onboard ATI 4250 video. It's got an AMD Sempron in it, running 1 core (think it's one of the Regor(?) AMDs, there's a second core there that works if I unlock it but I don't. The OS's are both retail copies of Win7 Home Premium. It has two 40 GB WD IDE drives in it on the one IDE channel that the board provides. There's also a SATA DVD ROM.

Originally, I booted the DVD and had Win7 format drive "0", put the 32-bit version of Win7 there. After a little checking of the 32-bit, I booted again and let it format and install 64-bit on drive "1" (different copies of Windows, they're not on the same license).

It's been updated with everything Windows Update has had to offer except the IE9 install and WU says "No Updates Available...".

I hope that answers the question. Let me know if you need more info!

Thanks!

Bob