SLDWORKS.EXE still shows in Task Manager

Below is another post from our esteemed IT genius, Boy "Radeon" Wonder.
Lets call him "Jordan", just for fun.

The copied post below seems to say he was having some problems with
crashing SolidWorks. Again, true to form, blaming his incompentence on
someone else. Isn't it great to live in a free country? It couldn't
be that those Radeons were causing an epidemic of crashes like they do
for other folks? I thought he said he had not had trouble with
crashing SolidWorks.

Jordan has a lot of questions. He's always out trying to get answers
from other people, not giving answers, or not giving right ones anyway.
I thought he was certified on everything under the sun, but it turns
out he's just bumming help from real IT people.


From: news.lightship.net - view profile
Date: Wed, May 5 2004 9:30 am
Email: "news.lightship.net" <>
Groups: comp.cad.solidworks

We are using a license auditing program KeyServer. Basically it works
by
seeing what tasks are running on the PC and locks notes it on the
license
managing server.

Lately I have been seeing a lot of licesnes being tied up on the server

saying that SolidWorks is running on some workstations. When I go to
the
workstations SW is closed, but if I [CTRL]&[ALT]&[DEL] and open the
Task
Manager I can see that SLDWORKS.EXE is still running in the list of
processes. I can end the process on the workstation and free the
license,
but that is an annoyance.


Is this a problem with SW2004 SP2.1?

 

There were problems like this with 2004. For some reason it would spawn
two processes sometimes killing the extra one, sometimes not. I haven't
seen it much in the later 2004 service packs.

 

<< The copied post below seems to say he was having some problems with
crashing SolidWorks >>

Wow, there you go again blabbering on like an idiot. I don't see anywhere
in that post a single mention of SW crashing on me nor do I see any mention
of the Radeons there either. Don't you think people can read and see that
you are a fool.

<< He's always out trying to get answers from other people, not giving
answers, or not giving right ones anyway. >>

Hey why don't you give everyone a laugh and show them the post where I was
the one that reponded to the user about how to install from a network share
and reference it by share name and not drive letter. You must remember
because it was just a few hours ago how you went blabbering on and on about
how they should use a UNC instead showing that you are a total moron that
does not know that referencing the share on the server by share name is the
UNC.

Why don't you just give up your pathetic attempt to burn me because you just
keep making a fool out of yourself. My lord, you copy and pasted the post
right into your new post and did not even read it. What a dope.......

 

Follow up:

Why don't you also post the response from all the other non-Radeon users
from that 2 year old thread like the one from Per O. Hoel
====
"In my opinion, it is not a "problem" isolated to SolidWorks 2004,
SP2.1 I have used the program over many years and the possible presence of
a
ghost image of SolidWorks is not just a recent characteristic."
===

So it was not a Radeon issue then was it you fool. Why blame the issue on
Radeon when you just read in that thread that other non-Radeon users said it
was a problem that SW had for years no matter if SW closed properly or
crashed.

Just keep them coming. I am really starting to feel bad about this now
because you are making it so easy for me Mr. "I don't know what a UNC is"

 

I don't see anywhere

All of the responses to your post were that the symptoms you were
having were due to SW crashes. Your favored Radeon is a popular source
of crashing with SolidWorks. In fact, aside from bad installs, the
Radeon card in specific is probably the #2 source of crashes.

Why do you come in here asking for help, get it, and then argue with SW
users about things you don't know anything about?

Your buddy,

Roland.

 

Per was saying that he had this problem with multiple versions of SW.
Radeons aren't the only source of crashes, there are others. People
who crash for reasons other than having a Radeon would see the same
problem with the license manager. He doesn't say it happens "no matter
if SW closed properly or crashed", he says "when it crashes or is
otherwise IMproperly shut down". Again, the reading thing. You
finished high school, right? Crashes cause the license manager to hang
onto licenses. Radeons are not recommended for SW. UNC does not equal
Folder Name. Simple stuff you just don't get.

We know you had problems because you are using SolidWorks and have
Radeons.

 

So by "improperly shut down" do you think he meant the engineers were to
stupid to press the little X up in the corner of the window? I think
"improperly" shut down is clearly SW screwing up, not the engineers.

<< UNC does not equal Folder Name >>

Glad to see you asked an IT guy what it meant. Unfortunately I never said
it did or still can't you read. Still trying to weasel out of shooting your
mouth off like an idiot and not knowing what a UNC was.

<< We know you had problems because you are using SolidWorks and have
Radeons >>

Two years ago the computers had RAGE 128 dumb @$$. There you go blabbering
on and on and on like an idiot. In your next post you will probably say the
Rage 128 cards were 3rd worst problems for SW because you already accused
installs and Radeon as being number 1 and 2.

Again, this is too easy because you just open your mouth without thinking.
Take a day or two off and gather your thoughts Jr. and then come back. Yes
that was a reference to me being older than you kiddo.

 

Try to keep to one thread. Look in the other genious and you will see that
you are shooting your mouth off again without even knowing what is going on.
FYI, those cards were Rage 128 at the time. Let me guess, even worse
right???

So since Installs were number 1 and Radeon was #2 problems then Rage 128 was
#3. Where can I find those statistics again? Oh, you just pulled them out
of your @$$.

 

Two years ago the computers had RAGE 128 dumb @$$.

Oh, well, THERE's an improvement. You don't need me to tell you that
the Rage and the RagePro were also shit game cards, definitely on the
bad list for SolidWorks. Along with the Viper, and I forget how many
other cards from that 97-01 vintage, ATI didn't have the corner on the
shit game card market. I see a pattern here. Cheap shit game cards in
engineering machines. The worst part of it is that people have told
you this before and you haven't listened then either.

I can't tell you how funny it is to see you in all seriousness write
this crap. The future at the engineering department in your company
looks rosy, as long as they're playing Half Life and not using
SolidWorks.

brainless game punk.

 

Where can I find those statistics again? Oh, you just pulled them out

I worked in SW tech support for 5 years. You might think I know what
I'm talking about. I helped idiots like you every day. Obviously
you're getting the brunt of it because I had to be nice to them. They
were generally a lot smarter than you, though.

Roland Scaleri
Zoetrope

 

<< brainless game punk >>

You know, this is the first game I have played in years and it has to be the
easiest. Instead of "Wack a Mole" I will call it "Slap the Weasel". Just
find a weasel in a news group who can't keep from shooting his mouth and
pulls BS from his own @$$ and just keep showing the group what a fool the
weasel is.

I can't believe the Rage (pardon the pun) at my successfully using these
cards in a manor that I need. Why the obsession to say something that works
just fine does not? Just can't admit that your a fool.

I would think that if the engineers had a problem they would have complained
about my computer selection at some point in the past 11 years you dope.

 

Try to clean it up and keep it in one thread. Yeah, clean it up like you
use to clean the Tech Support Department at SolidWorks when you worked there
as a Janitor.

<< I worked in SW tech support for 5 years >>

Well, now we are getting somewhere. You said you were 31 right and you
don't work there now so even if you were at your new job just a year that
means SW hires 25 year old kids or younger with no real experience to
"support" seasoned professionals. Figures

 

Guys if you keep up the name calling and slagging you are both going in my
blocked senders bin.

 

Waaah. Imagine you blocking senders. You've had to lay low for a
while after some pretty untoward posts of your own a few months ago, if
I rememvber correctly.

 

plonk

 

that

Not everyone is a seasoned slacker by the time they reach 25, don't
judge others by your own underacheivement.

 

This is no doubt a lot more fun <G>.

 

One thread Jr.