Mailing List
Home
Forum Home
Softimage
Carrara
trueSpace
Dir3d-l
Maya - a powerful 3D animation and visual effects software
Macromedia Flash Development
Subjects
Cameras
scaleDown command
black out solved
Aircraft Tutorial
Mathematical XYZ ?
Its done This vs That
Its done first week
recommendations for screen video captures?
3DExplorer "Oddity "
New Director
ProTeam renewals
Fuel 's new websites (X post)
Blue peter create a make toy
targeting groups question
XPost: Shockwave 3D game ( sort of )
RES: RES: RES: Fish Modeling
Emitting particles from object intersection
Fuel 's new websites (X post)
Texturing
Big Break Contest Videos
New Plugins
Models and Texture on my updated site
Error Installing Patch tS6 6
Plasma?
Looking for Inspiration
Weird EMail Q
It 's done first week ?
Cherry not cranberry
New game
Camera Animation Problem
Particle plugins?
 
XSICab Usage Update

XSICab Usage Update

2004-07-06       - By Christine Charette

 Back
Reply:     1     2     3     4     5     6     7     8     9     10     >>  

Hi folks,
As many of you know, we made available a tool called XSICab with the release of
XSI v4.0.  This tool collects data that helps us find the source of crashes you
encounter in XSI.  Thanks to those of you who have been using it, we have
already collected a good amount of data that helps us track down bugs which we
are working on fixing.

We noticed however that some of the cabs we received didn't contain complete
data.  A user would send us a cab along with some repro steps that lead to a
crash, but the data in the cab didn't reveal any crashing.  We realized then
that our tool sometimes needed another session of XSI to be opened and closed
in order to gather all of the data we needed.  

We will be fixing this limitation and updating the web with a new version of
XSICab in the near future, but in the meantime, we ask you to follow new
instructions in order to capture all of the information we need to tack down
the root of the crashes.

Here are the new steps to follow when XSI crashes.
*   As soon as you encounter a crash, the first thing to do is to restart XSI and
then close it again. This ensures that the XSICab tool captures all of the data
relevant to the crash in the previous session.
*   Invoke the XSICabs application from the Start menu / Programs / Softimage
Products / XSI_V4.0 / XSICab.
*   XSICabs then asks for a version of XSI from which to package the crash files.
Please select the version you were just using at the time of the crash.
*   A mail form should appear, created using your default mailer, with the .CAB
file in it. It will be addressed to XSIData@(protected)
*   Add any additional information you think may be relevant to the crash in the
e-mail.
*   Press send. That's it, and thank you very much!

You can grab the XSICab tool from here http://www.softimage.com/support/Xsi
/XSIcabs/


Thanks very much for your co-operation!
Christine


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859 (See http://iso-8859.ora-code.com)-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6487.1">
<TITLE>XSICab Usage Update</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR="#800000" SIZE=2 FACE="Arial">Hi folks,</FONT>

<BR><FONT COLOR="#800000" SIZE=2 FACE="Arial">As many of you know, we made
available a tool called XSICab with the release of XSI v4.0.&nbsp; This tool
collects data that helps us find the source of crashes you encounter in XSI.
&nbsp; Thanks to those of you who have been using it, we have already collected
a good amount of data that helps us track down bugs which we are working on
fixing.</FONT></P>

<P><FONT COLOR="#800000" SIZE=2 FACE="Arial">We noticed however that some of
the cabs we received didn't contain complete data.&nbsp; A user would send us a
cab along with some repro steps that lead to a crash, but the data in the cab
didn't reveal any crashing.&nbsp; We realized then that our tool sometimes
needed another session of XSI to be opened and closed in order to gather all of
the data we needed.&nbsp; </FONT></P>

<P><FONT COLOR="#800000" SIZE=2 FACE="Arial">We will be fixing this limitation
and updating the web with a new version of XSICab in the near future, but in
the meantime, we ask you to follow new instructions in order to capture all of
the information we need to tack down the root of the crashes.</FONT></P>

<P><FONT COLOR="#800000" SIZE=2 FACE="Arial">Here are the new steps to follow
when XSI crashes. </FONT>
<UL>
<UL>
<LI><FONT COLOR="#800000" SIZE=2 FACE="Arial">As soon as you encounter a crash,
the first thing to do is to restart XSI and then close it again. This ensures
that the XSICab tool captures all of the data relevant to the crash in the
previous session. </FONT></LI>

<LI><FONT COLOR="#800000" SIZE=2 FACE="Arial">Invoke the<I> XSICabs</I>
application from the Start menu / Programs / Softimage Products / XSI_V4.0 /
XSICab.<I></I> </FONT></LI>

<LI><I><FONT COLOR="#800000" SIZE=2 FACE="Arial">XSICabs</FONT></I><FONT COLOR=
"#800000" SIZE=2 FACE="Arial"> then asks for a version of XSI from which to
package the crash files. Please select the version you were just using at the
time of the crash. </FONT></LI>

<LI><FONT COLOR="#800000" SIZE=2 FACE="Arial">A mail form should appear,
created using your default mailer, with the .CAB file in it. It will be
addressed to XSIData@(protected) </FONT></LI>

<LI><FONT COLOR="#800000" SIZE=2 FACE="Arial">Add any additional information
you think may be relevant to the crash in the e-mail. </FONT></LI>

<LI><FONT COLOR="#800000" SIZE=2 FACE="Arial">Press send. That's it, and thank
you very much! </FONT></LI>
<BR>
</UL></UL>
<P><FONT COLOR="#800000" SIZE=2 FACE="Arial">You can grab the XSICab tool from
here <A HREF="http://www.softimage.com/support/Xsi/XSIcabs/">http://www
.softimage.com/support/Xsi/XSIcabs/</A></FONT>
</P>
<BR>

<P><FONT COLOR="#800000" SIZE=2 FACE="Arial">Thanks very much for your co
-operation!</FONT>

<BR><FONT COLOR="#800000" SIZE=2 FACE="Arial">Christine</FONT>
</P>

</BODY>
</HTML>