autolisp wont run on some computers

[upblossomhill]

I have a simple autolisp routine which loads successfully on all computers in the office. However on some computers it doesn't work! All search paths, cui macros are correct etc. Has anybody got any idea why?

[Anonymous]

What kind of errors are you getting?

wrote in message news:5698877@discussion.autodesk.com...
I have a simple autolisp routine which loads successfully on all computers
in the office. However on some computers it doesn't work! All search paths,
cui macros are correct etc. Has anybody got any idea why?

[upblossomhill]

It doesn't come up with any error messages-it's just a routine called instant messenger which allows users to talk to each other through acad by picking each others names and then typing a message. It acts as though it works but on some computers it doesn't transmit or receive the message.

[Anonymous]

It may be running through NETSEND (an old dos command). There was an MS
Hotfix that disabled Messenger (not the same as instant messenger) in your
services. See if it's turned off on the computers that are not working.

[Anonymous]

Does the lisp use a windows program to accomplish the task? Are all
computers on the same windows version?

--
Erik S. Deyo
http://ltsideofthings.blogspot.com/
wrote in message news:5698919@discussion.autodesk.com...
It doesn't come up with any error messages-it's just a routine called
instant messenger which allows users to talk to each other through acad by
picking each others names and then typing a message. It acts as though it
works but on some computers it doesn't transmit or receive the message.

[upblossomhill]

Yes that may be the problem the computers that do not work are on XP but the others are on older versions of windows.

[DaOtter]

NET SEND is effectively disabled and retired in XP, if my memory serves correctly. It works great in 2000, and I've used it many times in the office before I upgraded. I do not know if there is an easy way to turn in on, but you may not want to as it is a large security risk.

[Anonymous]

It's disabled but not retired. Easily turned back on under services. I had
to turn it back on for to communicate with my backup software and printer.
The only time it's a security risk is if your isp is assigning IP address
directly to your pc exposing your computer to the internet.

[DaOtter]

"Effectively" retired, mind.
Agreed, it's much LESS of a security risk when you're in a large business, hidden behind multiple firewalls. Of course, those companies are security conscious enough that they're not likely to LET you turn NET SEND back on.

Sadly, a lot of places I know of aren't even security savvy enough to have proper firewalls in place. Being on the network can be just as bad as being plugged directly to the outside world. 😞

Bottom line, unless you just HAVE to use it, leave it be.

[Anonymous]

I agree. Just use IM, it's free and it works. But it was sure fun sometimes
to send messages, spoofing who it was from, to others in the office using
netsend that didn't know about the command. The guy in the office next to me
(which is left handed) was arguing with his wife one day on the phone and
when he got off I sent him this:

Message from: "Your Computer"
Hey Lefty! You're not going to let here get away with that, are you?

After that popped up on his screen, he went home and took a sick day the
next day. Called and said he wasn't coming back until his computer was out
of his office.

[DaOtter]

LMAO... Sounds like the high school computer labs all over again. 😄