NOD32 problems with Win98 SE

Discussion in 'NOD32 version 2 Forum' started by lucspe, Nov 28, 2005.

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

    lucspe Registered Member

    Joined:
    Nov 28, 2005
    Posts:
    1
    Hi,

    I am quite new to this forum and I am posting to request some help...

    We have just deployed NOD32 in a network of 18 computers running a mix of Win2000, WinXP and Win98_SE O/S.
    The license of NOD32 we have bought is an enterprise edition, so we have a central Remote Administrator Console as well.

    We are having 2 big issues on the Windows 98 SE machines:

    a) DOS printing
    On 2 Win 98 machines, after installing NOD32, one of our applications (still DOS based) refuses to print and whenever we print the computer freezes up completely with no other option than a reboot.
    This problem happens on 2 different machines with different printers (1 Epson Stylus C80 inkjet and 1 Epson LX-300 dotmatrix).
    If AMON is disabled the problem disappears.
    We tried exlcuding from real-time scanning the DOS application folder, c:\windows\spool and c:\windows\temp (where the temp print file is created) but no luck.

    b) Booting directly into shutdown screen
    On another 2 Win 98 machines, after installing NOD32 the computer boots directly into "IT IS NOW SAFE TO TURN OFF YOUR COMPUTER" screen. If we boot in safe mode and uninstall NOD32, the problem disappears.

    Has anybody any idea or has found/solved similar problem before? We contacted local NOD32 reseller (we are in Hungary) but they seem to have no clue on how to solve these problems...

    Thank you very much for any help that might come...
     
  2. questorz

    questorz Registered Member

    Joined:
    Feb 3, 2006
    Posts:
    6
    Re: NOD32 problems with Win98 SE Dos Printing

    We are having the problem also. While printing in DOS on some computers running Windows 98SE (all updates) the computers will freeze and the A: / Diskette drive will light up and grind until you end the process, which usually leads to a reboot (with or without a floppy disk in the drive). We did a test where we disconnected the floppy drive and the printing worked flawlessly with no lockups. Weird prob. It could be fixed easily by using an external USB floppy and just unplugging it when it's not needed, but not practical in our case due to the high number of workstations effected. We are still running tests to find a better solution.
     
  3. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    This is a guess, but try checking to AMON --> Security --> Load file system monitor dynamically.
     
  4. questorz

    questorz Registered Member

    Joined:
    Feb 3, 2006
    Posts:
    6
    I have been talking back and forth with NOD32's tech support on the Dos Printing problem. Their tech support has been very active in conversing with me on the problem. If we get a solution I will post it.
     
  5. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Thank you, it helps us all to learn...

    Cheers :D
     
  6. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Lucspe, have you had any luck with problem b? I just realized that you cannot going into AMON to change the settings, because the computer boots straight to "It is now safe to turn off your computer." I am kind of slow sometimes. :p :D

    Anyway, for those two computers, try reinstalling NOD32 with the "expert" options, and choose not to include AMON and IMON. If you are able to boot the computers, then you can try activating AMON or IMON later on, and see which one causes the problem.
     
Thread Status:
Not open for further replies.