~e5d141.tmp - an observation.

[Anonymous]

OK, so C-Dilla is dead (allegedly) and has been reincarnated as Safecast, and actually so far I have to say it is an improvement.
Just a quick observation, I'm assuming that the two processes that Inventor kicks into life when it starts (both called
~e5d141.tmp) are the replacements for cdilla10 and cdilla64 processes that used to run, and the file that's left in the temp
folder is harmless cos if it's deleted it gets recreated.

Now here's an interesting one, Inventor was a bit wobbly this morning on a clients machine so I went to have a look at it. You
could open files, but as soon as you tried creating a new file, POW, straight back to Windows Desktop. Going through the process
list I noticed that one of these "tmp" processes was stuck. End process and all was happy again. Wierd.

BTW, this is non-US locked version of Inventor

John Bilton

[Anonymous]

John,

I've had a similar problem whilst getting Inv7 to start. Ending the process and Inv7
starts immediately, instead of several minutes.

Do I need to put a couple more shovels of coal on my steam driven abacus or is Autodesk
going to tell us how wonderful Inv7sp1 or Inv8 is going to be ?

Duncan

--
"Humour ... is one man shouting gibberish in the face of authority, and proving by
fabricated insanity that nothing could be as mad as what passes for ordinary living."
(Terence 'Spike' Milligan K.B.E., 1918-2002)


"John Bilton" wrote in message
news:0F1493DF2D026FDF3ABF6E6670AFF0CD@in.WebX.maYIadrTaRb...
> OK, so C-Dilla is dead (allegedly) and has been reincarnated as Safecast, and actually
so far I have to say it is an improvement.
> Just a quick observation, I'm assuming that the two processes that Inventor kicks into
life when it starts (both called
> ~e5d141.tmp) are the replacements for cdilla10 and cdilla64 processes that used to run,
and the file that's left in the temp
> folder is harmless cos if it's deleted it gets recreated.
>
> Now here's an interesting one, Inventor was a bit wobbly this morning on a clients
machine so I went to have a look at it. You
> could open files, but as soon as you tried creating a new file, POW, straight back to
Windows Desktop. Going through the process
> list I noticed that one of these "tmp" processes was stuck. End process and all was
happy again. Wierd.
>
> BTW, this is non-US locked version of Inventor
>
> John Bilton
>

[Anonymous]

Can you reproduce this problem at will? Does it happen from a reboot? What
OS do you have?

--Cy--

"Duncan Anderson" wrote in message
news:9B4E129A942E89991745A84ED3785FB9@in.WebX.maYIadrTaRb...
> John,
>
> I've had a similar problem whilst getting Inv7 to start. Ending the
process and Inv7
> starts immediately, instead of several minutes.
>
> Do I need to put a couple more shovels of coal on my steam driven abacus
or is Autodesk
> going to tell us how wonderful Inv7sp1 or Inv8 is going to be ?
>
> Duncan
>
> --
> "Humour ... is one man shouting gibberish in the face of authority, and
proving by
> fabricated insanity that nothing could be as mad as what passes for
ordinary living."
> (Terence 'Spike' Milligan K.B.E., 1918-2002)
>
>
> "John Bilton" wrote in message
> news:0F1493DF2D026FDF3ABF6E6670AFF0CD@in.WebX.maYIadrTaRb...
> > OK, so C-Dilla is dead (allegedly) and has been reincarnated as
Safecast, and actually
> so far I have to say it is an improvement.
> > Just a quick observation, I'm assuming that the two processes that
Inventor kicks into
> life when it starts (both called
> > ~e5d141.tmp) are the replacements for cdilla10 and cdilla64 processes
that used to run,
> and the file that's left in the temp
> > folder is harmless cos if it's deleted it gets recreated.
> >
> > Now here's an interesting one, Inventor was a bit wobbly this morning on
a clients
> machine so I went to have a look at it. You
> > could open files, but as soon as you tried creating a new file, POW,
straight back to
> Windows Desktop. Going through the process
> > list I noticed that one of these "tmp" processes was stuck. End process
and all was
> happy again. Wierd.
> >
> > BTW, this is non-US locked version of Inventor
> >
> > John Bilton
> >
>
>

[Anonymous]

Have you tried logging in as a different user and see if it still pauses. If it works fine, you need to rebuild your profile. If
you need some tips on doing this, let me know.

John Bilton

[Anonymous]

I haven't tried logging on as a different user, but could you still post any advice you
can give on rebuilding my profile.

Cheerz
Duncan Anderson


"John Bilton" wrote in message
news:7DC76715B222F7F496FA05359F574810@in.WebX.maYIadrTaRb...
> Have you tried logging in as a different user and see if it still pauses. If it works
fine, you need to rebuild your profile. If
> you need some tips on doing this, let me know.
>
> John Bilton
>

[Anonymous]

O/S = WinXP home

Can't re-produce on command.

Since the original posting I've taken more notice of .tmp process and Temp directories.

Once Inv has started I now have two process called ~e5d141.tmp

There are also two sub-directories in %USERPROFILE%\Local Settings\Temp
with similar names to the processes. Each contains three .tmp files with the same names, a
system file (again with the same name) and one sub-directory contains a file with
extension .csa When Inv is closed the processes disappear as do the sub-directories and
files they contain. But the file ~e5d141.tmp still remains in %USERPROFILE%\Local
Settings\Temp

Will these files and sub-directories remain if Inv crashes ?
Is it worthwhile adding a "deltree" to the Autoexec.bat file to delete any unwanted,
remaining files ?

I've been doing a lot of nosing around and I be interested to know about the files
"Perflib
_Perfdata_###.dat that are created in %SystemRoot%\Temp and not deleted. As well as
ws_ProdProf_########_0.log that are created in %USERPROFILE%\Local Settings\Temp. These
files have appeared since installing AIS7 (# = single digit)

Any info on the build up of these files and processes would be welcome.

Cheerz
Duncan Anderson

"Cy Shuster" wrote in message
news:BE89D764C436D17CE906A2EFB5F88C2F@in.WebX.maYIadrTaRb...
> Can you reproduce this problem at will? Does it happen from a reboot? What
> OS do you have?
>
> --Cy--
>