2005 over 2004

Been too busy with 2004, that I haven't download the 2005...

Has anyone overlayed 2005 over 2004?

In other words installed on the same machine with 2004.
--

AUTODESK
Authorized Developer
www.Cadentity.com
MASi

 

Speaking of which, should I be in any 'rush' to get up to 2005? We just
upgraded our licensing for the 2000 deadline, please tell me that 2005 is at
least backwards compatible in drawing files w/ 2004?

Any big reason I would want to look to 2005 soon?

Thanks.

 

It's up to you if you want to rush. The file format is the same.

There are some big reasons that might want you to upgrade. Sheet sets,
fields, tables are some of them. More on www.jtbworld.com/autocad2005.htm
soon.

--
Best Regards, Jimmy Bergmark
CAD and Database Developer Manager at www.pharmadule-emtunga.com
Take a look at
JTB FlexReport (FLEXlm report tool) - www.jtbworld.com/jtbflexreport
SmartPurger (Purges automatically) - www.jtbworld.com/?/smartpurger.htm
or download some freeware at www.jtbworld.com
More on AutoCAD 2004;
www.jtbworld.com/autocad2004.htm
www.jtbworld.com/autocad2004tips.htm

 

You want to know what's funny, it's already been done before...

I did sheet setup back in R12.

My utility was called Cartoons, for Cartoon Sets.

Didn't AutoManager also have the same thing?

Kinda late, if you've already customized your own cartoon creator...

It's like the LMAN, I wrote my first Layer Manager for R12 Dos and called it
GLC "Group Layer Control".

I'm more than sure there's been others that have already written simliar if
not exact utilities.

 

Because AutoCAD 2005 is locked (including in North
America), there is going to be major problems debugging
in-process code (which requires AutoCAD to be loaded
as the debug target). The MacroVision SafeCast soft-
lock technology used by Autodesk contains "anti-debug"
code, that makes it difficult or impossible to debug
in-process DLLs.

So, if you're developing any ActiveX dlls (or ARX)
code, you're going to be in for a very unpleasant
surprise.

Note that nowhere in the release announcement was
there any indication that North American versions
of AutoCAD 2005 are locked.

Don't be suprised if the regulatory bodies in the
US take a very hard look at Autodesk's practices,
and the fact that they put AutoCAD developers and
consultants (which Autodesk is directly competing
against) at a significant competitive disadvantage.



AcadX for AutoCAD 2004 Beta 1
http://mysite.verizon.net/~vze2vjds/acadx/AcadX16.zip

 

Hey Tony, did they create some sort of bomb in R13 which split the acad.pwd
file into two and made autocad bomb out, and have to be reinstalled?

Or was it an earlier version? I remember that if I tried looking at some
files, that the pwd file would self-distruct.

I was getting into the guts of it all back then. I just wanted to learn the
entire core.

Give me a better understanding of what this doing and why. I'm a little slow
at the lock device you're talking about.

 

Tony,

Since you are not an ADN member and do not have the beta of AutoCAD 2005,
how can you make these wild speculations and accusations? You do understand
that posting something like this with malicious intentions is not acceptable
and can be serious?

Sincerely,
Shaan Hurley
Autodesk, inc.

 

Now that's interesting... wow!

I guess I'll have to download 2005 and test it myself.

Of coarse I don't know what Tony's talking about, but am interested in
knowing what's going on with what he claimed.

What exactly is he talking about? or is it even true?
--

AUTODESK
Authorized Developer
www.Cadentity.com
MASi

 

By the way Shaan, nice bike!

 

Shaan - The problem existed in 2004 (Locked versions), and
from what I was told just yesterday, remains in the beta of
2005, which is being discussed out in the open.



AcadX for AutoCAD 2004 Beta 1
http://mysite.verizon.net/~vze2vjds/acadx/AcadX16.zip

 

Tony,

You were speaking of AutoCAD 2005 specifically of what you have no idea what
was done or any changes. Before firing your malicious salvos on a product
you do not know, you should think about the facts and if you don't have
them, then channel your energy somewhere else or prepare to suffer the
consequences for your accusations. Posting as you did about AutoCAD 2005
without any facts is a serious issue. This is just one more time you have
spouted incorrect information without any facts to back yourself up.

How about admitting you do not know what you speak of on AutoCAD 2005 and
issue a formal apology for not basing your accusations on facts?


Shaan Hurley
Autodesk, Inc.

message news:4033c896$1_1@newsprd01...

 

Thanks Rudy, they are a lot of fun and grab attention.

Cheers,
-Shaan

 

What do you mean "without any facts"??????

I most certainly do have facts.

I was informed of the problem yesterday, by a beta
tester who was trying to use it to debug his code.

I am not the one making assumptions, you are.




AcadX for AutoCAD 2004 Beta 1
http://mysite.verizon.net/~vze2vjds/acadx/AcadX16.zip

 

Tony,

So you are only passing on second hand info, but standing behind it and
spreading anti competitive accusations? Your information is incorrect based
on the information I have. I would suggest until you have verifiable
information with facts, to cease the attacks, rumors, and speculations.
Could it be the method of debugging the person is using is actually the
problem or a bug that needs reported and is a isolated or test case?

The only assumption I made, is you do not have any verifiable facts to
support your malicious accusations. Please provide your facts or proof or
issue a formal apology and admission your claims were based on second hand
unverified information.

-Shaan

 

Shaan - I am standing behind what I was told, by 2
people so far, yes.

Also, I would suggest you be more responsible and
careful about your deliberately mislabling my comments
as 'accusations'.

There was no accusation in my comments.



AcadX for AutoCAD 2004 Beta 1
http://mysite.verizon.net/~vze2vjds/acadx/AcadX16.zip

 

Tony,

Your comments as posted (see comment 1 below) "are "accusations" with no
basis or provided fact as presented. How about explaining the method of
debugging you "claim" fails with safecast that is "not" being reported by
others debugging 2005? How about you try to be more responsible and just
post the specifics or have the contacts email me? Do it for the other
developers that you "claim" will hit this, or does that not matter. Or is it
really not debugging and something else at runtime not designed to be used
for debugging in the first place.

So the ball is in your court, choose to ignore and play games and fail to
report this, and you get to be the poster child of not reporting this issue
that you claim to know. My assumption is there is a little more to this
story than you claim. Perhaps you are now feeling backed into a corner and
simply cannot admit you are making serious allegations without any factual
proof to back them up.

-Shaan

comment 1:
"Because AutoCAD 2005 is locked (including in North
America), there is going to be major problems debugging
in-process code (which requires AutoCAD to be loaded
as the debug target). The MacroVision SafeCast soft-
lock technology used by Autodesk contains "anti-debug"
code, that makes it difficult or impossible to debug
in-process DLLs.

So, if you're developing any ActiveX dlls (or ARX)
code, you're going to be in for a very unpleasant
surprise.

Note that nowhere in the release announcement was
there any indication that North American versions
of AutoCAD 2005 are locked.

Don't be suprised if the regulatory bodies in the
US take a very hard look at Autodesk's practices,
and the fact that they put AutoCAD developers and
consultants (which Autodesk is directly competing
against) at a significant competitive disadvantage.

--
AcadXTabs: MDI Document Tabs for AutoCAD
http://www.acadxtabsxxxxxxx.com

AcadX for AutoCAD 2004 Beta 1
xxx"

message news:40341f75_3@newsprd01...

 

So Shaan, will US versions be locked or not? Or is this yet to be determined?

 

R.K.

Like many other applications available today, AutoCAD 2005 will be using
safecast software licensing. There will be much more information including a
FAQ about this as we get closer to the official launch.

Sincerely,
Shaan Hurley
Autodesk, Inc.

So Shaan, will US versions be locked or not? Or is this yet to be
determined?

 

R.K.

As Shaan noted, the AutoCAD 2005 will support Product Activation worldwide.
For those who are interested, you can visit the Autodesk Product Activation
website (http://www.autodesk.com/activation) for factual information and
details.

Regards,
Greg


So Shaan, will US versions be locked or not? Or is this yet to be
determined?

 

fact is, that pushing "new" acad products spins at ever faster
cycles (one year 5 days from 2005 to 2005 one page claims).
Working as cad manager and programmer for a german company with 60 acad
workplaces means
Telling my boss to shell out again some 60 * 1500 Euro. The building trade
faces the biggest slump in german history.

We just gotten over the change from R14 in mid 2002 to R2002 (coincidenc?).
Afer a hurried "migration", my software some 70.000 lines of Lisp,
10.000 Lines C,C++ runs stable after a year of blood sweat and tears and
nice help from this wonderful people of this forum.

Don't mention the cr...p with c-dilla and anti-virus software,
loss of authorisation and and ...
I'm pleased to see, that they integrated now something like excel,
can do the versioning of acad now with built in spread sheet.
Suggestion version number scheme: ACADyy-mm-dd-hh

Yes Tony, there is no smoke without fire, and I expect the unexpectable
Working as a developer, dependent on this programming environment,
it could be plausible to offer you a special version,
a special offer so to say, for a few bugs more....
The only one who are pleased are... guess the honorable shareholders...


Dieter Berger
(Germany)