Re: xsi 32 bit won't run on win64 anymore

["Kris Rivel" <krisrivel(at)gmail.com>]

True.  I have no idea if this happened when I installed NOD or when windows did an update unfortunately.  NOD is fairly new to my system so the problem "may" have occurred when I installed NOD.

Kris

On Jan 29, 2008 6:13 PM, Guy Rabiller <guy.rabiller(at)tek2shoot.com> wrote:

Hey Kris,

Remember though, that we are still not sure if the problem was caused by
a Windows update or a Nod update ( or both ).

What we are sure is that this was working perfectly well prior this (
these ? ) update(s), without the need to exclude XSI/XSIBatch from the
Nod scan.

We shouldn't have to do this. Perhaps a Nod update is now needed to sync
it with some recent Windows update. I've not seen any mention of this
kind of problem on their forum though. Odd.

--
guy rabiller | cg r&d manager (at) tek2shoot / def2shoot (.com)



Kris Rivel a écrit :

> 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.
>
> Kris
>
> On Jan 29, 2008 5:24 AM, Stéphane Bonnot <stephane(at)def2shoot.com

> <mailto: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 <http://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 )
>     >
>
>
>     ---
>     Unsubscribe? Mail Majordomo(at)Softimage.COM

>     <mailto:Majordomo(at)Softimage.COM> with the following text in body:

>     unsubscribe xsi
>
>


---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi