|
Whoops...never mind...already went to the list :-)
Kris
On Jan 29, 2008 3:02 PM, Kris Rivel < krisrivel(at)gmail.com> wrote:
Ha ha...awesome!!! You guys rock. That did the trick. I totally assumed a clean boot would shut down NOD but apparently it was still running. NOD is probably the best anti-virus running out there...I love it. So with that being said, this note should be mentioned perhaps in the install docs so that anyone else with a similar setup won't have the same problem. I'll mention this solution on the list server too in case anyone is curious how it turned out. Thanks again.
KrisOn Jan 29, 2008 5:24 AM, Stéphane Bonnot < stephane(at)def2shoot.com> wrote:
Ok, I found some time to have a look at it.
The issue comes from a recent update (it used to work before). I didn't manage to find out if this comes from a Windows or Nod update. Indeed, the issue comes from Nod, for some reason one packet seems to be
altered by Nod antivirus. To solve the issue all you have to do is open Nod control center, IMon tab (internet protection), configuration , advanced, then exclude from the scan both xsi.exe and xsibatch.Exe
I tried to track the packets at ethernet level, the spm communication seemed ok with and without Nod32 IMon. Nod is not reporting any blocked packet , nor threat detected, therefore there is definitely something strange with the spm communication or
another network communication of xsi and xsibatch.
Thanks Guy for the clue on the spm connection, I was not thinking about it at the beginning since the Xsi32 Gui is starting (needs a licence for this) but locks when about to show viewports.
Excluding xsi.exe and xsibatch..exe from Nod IMon solved both issues on my Vista64 computer : Xsi32 gui not showing up completely (blocked when about to show viewports) and xsibatch reporting a semaphore issue.
Stephane.
-- Stéphane Bonnot R&D Manager
Tek2Shoot 24-26 , rue notre dame des victoires 75002 Paris FRANCE Tel: +33 (0)1 44 82 00 82 www.tek2shoot.com
Guy Rabiller wrote: > > We have the problem here too. > > It seems to be related to some windows recent update. Didn't had time > to investigate it yet though. > > The problem appeared on one Vista 64 bit workstation here. It's
> interresting to learn that the problem appeared on XP 64 bit too. > ( XSI 64 bit runs fine too )
|