Startup Suite

I have a VLX file that I load using the Startup Suite. Up until today
everything has been working fine. Now after updating the users It loads fine
and runs but AutoCAD freezes. If I remove it from the Startup Suite and load
it manually, everything works fine again. No changes were made to the
program.

Any suggestions or comments as to what may have caused this?

Dale

 

Demons.

What happens if you change the loading order?

"Dale Levesque" <dale at dynamicwindows.com> wrote in message I have a VLX file that I load using the Startup Suite. Up until today
everything has been working fine. Now after updating the users It loads fine
and runs but AutoCAD freezes. If I remove it from the Startup Suite and load
it manually, everything works fine again. No changes were made to the
program.

Any suggestions or comments as to what may have caused this?

Dale

 

Michael can you reach into my left pocket, and pull out the bag of tricks?

With that said, you'll have to expose, not you Michael, Dale, what exactly
you did to the code.

 

re: "Michael, can you reach into my left
pocket ..." -- Not in this lifetime Rudy.

re: "Expose what exactly you did to the
code", -- please re-read the original post.


Michael can you reach into my left pocket, and pull out the bag of tricks?

With that said, you'll have to expose, not you Michael, Dale, what exactly
you did to the code.

 

Hi Dale, what do you mean by "after updating the users"?

"Dale Levesque" <dale at dynamicwindows.com> wrote in message I have a VLX file that I load using the Startup Suite. Up until today
everything has been working fine. Now after updating the users It loads fine
and runs but AutoCAD freezes. If I remove it from the Startup Suite and load
it manually, everything works fine again. No changes were made to the
program.

Any suggestions or comments as to what may have caused this?

Dale

 

If a .dll changed, you should un-register, then re-register the .dll

Bob

 

Have you verified that your code is not loading twice?

 

"Now after updating the users ..."

No updated code, but the users were...huh?....

Perhaps I'm lost in limbo....

 

Sorry guys. My update routine is created by Inno setup and includes various
VLX files. This particular VLX hasn't been modified in ages but it gets
overwritten during the update.

Best regards,

Dale

 

From what I can see from the Startup Suite dialog, the apps are listed in
alphabetical order. I don't see a way of changing the order Michael.

Dale

 

Hi Dale,
Could you translate that for us? Is the problem fixed?
If not, I'm really lost. ;-)

Regards,
Doug

 

Then...with that said... what VLX code did you add or update?

Since the original was not update, but others were, that means there must
have been a conflict at some point....

I find your post a little cryptic...

Tell us more exactly what the utilities do, and who, you or whom its
occurring it to.

 

It's definitely being loaded twice Tony.

 

Forget about the order that they were loaded, I don't really think thats
important.

What is important, is that you're not defining the same function more than
once or that perhaps the function is having a conflict with another
application or autocad itself.

 

Ha, more clues...

I think we're getting warmer...

 

I'll start over. I have a setup.exe that is created with Inno setup. This
setup.exe copies files to the users drives. One of these files is a VLX
file. This VLX was not modified since the last time it was placed on the
users machine but It was overwritten with the same file by my setup routine
yesterday. Today the code inside the VLX loads and runs but freezes AutoCAD.
I've since verified that Startup Suite seems to be loading it twice but I'm
not sure what effect this has or how to fix it.

Dale

 

Rudy my man, we're red hot. My sincerest apologies to all. A variable name
in the locals list was identical to one in another VLX. I did of course
modify the second VLX var to be local. I changed the var name in VLX 1 and
all is well. You guys were right, I had to have changed SOMETHING!.

Thanks alot everybody,

Dale

PS. I'm still investigating the loading twice issue.

 

That's much more informative but I don't think I have enough
info to even make WAG's but I'll take a stab at it.

1) Often when I write a routine, it contains header files that
load only if they are not loaded. Perhaps there is no check
in your new routines.

2) Since VLX files have their own namespace, perhaps your
new routines have event handlers that conflict with your old
routines.

3)Name collision with globals or User Defined programs.


In order for anyone to help, they'll need to know when ACAD
locks up( at load, after a certain command, during a view change...)

4)Some things should not be done during startup but only after
everything has been loaded.

Regards,
Doug

 

And to think...someone said I need to re-read the original post...

I knew something was amuck....

--

AUTODESK
Authorized Developer
http://www.Cadentity.com
MASi

 

In order for anyone to help, they'll need to know when ACAD

Your right Doug, I just thought that there might be something with the
Startup Suite that was well known. Of course it's turned out to be a change
made to another program that caused the error. Actually it exposed a bug
that I've now fixed. Global variables ... yikes.

Thanks again.

Dale