 | | | XSICab Usage Update | XSICab Usage Update 2004-07-06 - By Henry Katz
Back
Christine Charette wrote:
Hi Christine,
I crashed several times due to nvidia driver issues which had been
resolved thanks to support. It would be nice
to see this product on Linux? /Non?
/Cheers,
Henry
> 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.
>
> o 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.
> o Invoke the/ XSICabs/ application from the Start menu /
> Programs / Softimage Products / XSI_V4.0 / XSICab.
> o /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.
> o A mail form should appear, created using your default
> mailer, with the .CAB file in it. It will be addressed to
> XSIData@(protected)
> o Add any additional information you think may be relevant
> to the crash in the e-mail.
> o 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 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859 (See http://ISO-8859.ora-code.com)-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Christine Charette wrote:<br>
<br>
Hi Christine,<br>
I crashed several times due to nvidia driver issues which had been
resolved thanks to support. It would be nice<br>
to see this product on Linux? <i>Non?<br>
<br>
</i>Cheers,<br>
Henry<br>
<blockquote
cite="midF902B0EA096A23418FECB8D27A063884022B6826@(protected)"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="MS Exchange Server version 6.0.6487.1">
<title>XSICab Usage Update</title>
<!-- Converted from text/rtf format -->
<p><font color="#800000" face="Arial" size="2">Hi folks,</font>
<br>
<font color="#800000" face="Arial" size="2">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.</font></p>
<p><font color="#800000" face="Arial" size="2">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. </font></p>
<p><font color="#800000" face="Arial" size="2">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" face="Arial" size="2">Here are the new steps
to follow when XSI crashes. </font>
</p>
<ul>
<ul>
<li><font color="#800000" face="Arial" size="2">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" face="Arial" size="2">Invoke the<i>
XSICabs</i> application from the Start menu / Programs / Softimage
Products / XSI_V4.0 / XSICab. </font></li>
<li><i><font color="#800000" face="Arial" size="2">XSICabs</font></i><font
color="#800000" face="Arial" size="2"> 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" face="Arial" size="2">A mail form
should appear, created using your default mailer, with the .CAB file in
it. It will be addressed to <a class="moz-txt-link-abbreviated" href="mailto
:XSIData@(protected)">XSIData@(protected)</a>. </font></li>
<li><font color="#800000" face="Arial" size="2">Add any
additional information you think may be relevant to the crash in the
e-mail. </font></li>
<li><font color="#800000" face="Arial" size="2">Press send.
That's it, and thank you very much! </font></li>
<br>
</ul>
</ul>
<p><font color="#800000" face="Arial" size="2">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" face="Arial" size="2">Thanks very much for
your co-operation!</font>
<br>
<font color="#800000" face="Arial" size="2">Christine</font>
</p>
</blockquote>
<br>
</body>
</html>
|
|
|