2006 Just slow

[Anonymous]

Ok so we're aren't going to 2007 for some time. But here's my issue. I just installed LDT Comp 2006 on a computer here. License is on the computer, stand alone type. Yes, I installed C3D 2006. No I haven't put the patches on yet.

From the get go this program, LDT and Land Map Enabled run like DOGS! We load a drawing with an image and it's super slow, like 5 min. to load.

Consider that 2000i is on the machine also, that's what we're upgrading form and there is absolutely no performace issues with that version.

I DID NOT migrate settings over, it screwed it up last time. This time I uninstalled, took off all the Service packs, took off all the object enablers, rebooted then reinstalled LDT 2006 companion and Civil Design.

So with that said, what would be causing the program to run so slow.

1GB RaM
Win Media (ya I know)
2.36GHZ intel chip

Heidi

[Anonymous]

tsaxy wrote:
> Ok so we're aren't going to 2007 for some time. But here's my issue. I just installed LDT Comp 2006 on a computer here. License is on the computer, stand alone type. Yes, I installed C3D 2006. No I haven't put the patches on yet.
>
> From the get go this program, LDT and Land Map Enabled run like DOGS! We load a drawing with an image and it's super slow, like 5 min. to load.
>
> Consider that 2000i is on the machine also, that's what we're upgrading form and there is absolutely no performace issues with that version.
>
> I DID NOT migrate settings over, it screwed it up last time. This time I uninstalled, took off all the Service packs, took off all the object enablers, rebooted then reinstalled LDT 2006 companion and Civil Design.
>
> So with that said, what would be causing the program to run so slow.
>
> 1GB RaM
> Win Media (ya I know)
> 2.36GHZ intel chip
>
> Heidi
Hey Heidi;

Two questions for your consideration;

Why haven't you done the 2K6 SP yet?

Have you done the Repair to 2Ki yet that has been in the ReadMe [I know
what's that? - ;-)] for awhile? To quote our friend John Mayo;
I make sure that I do not open or mess with any previous version until a
repair of that version is complete. Almost all Readme files on newer LDT
setup disks have recommend a repair for co-existing versions. I think
the goes back 2002. We had a few bumps but no horror stories. No one
lost any work or a great deal of time. Just keep in mind we have small
projects in relation to many others so I haven't really pushed 2007 like
I may have if I was doing miles of highway.

John Mayo
Conklin Associates


--
Don Reichle
"The only thing worse
than training your staff,
and having them leave is -
not training your staff,
and having them stay."
Courtesy Graphics Solution Providers
----------------------------------------------------------
!! Please discuss whatever we tell you with your SysMgr !!
!! They appreciate staying in the loop 🙂 !!

LDT/CD-2K4
AMD Athlon 64 X2 Dual 2.01GHz
XPPro 32bit SP2
2GB RAM
Dual WD800JD Hard Drives - 149GB Nvidia Stripe
Nvidia Quadro FX 1300 128MB
Dual ViewSonic 19-inch VA902b monitors

[Anonymous]

Ok so I haven't installed SP 1 or 2 yet because, time. I didn't have the time yesterday while my coworker was gone, it's his machine and he needs it today! I plan on installing those on Monday when he's gone.

Repair? I intially had issues with LDT 2006 not letting me save back to different formats and I think that was from migrating the settings over from 2000i. There was also the issue where you loaded map enabled and it gave you LDT but you couldn't get them separated. That had nothing to do with how they were installed or opened, it just freaked out. Had that happen before and had to repair, but his machine wouldn't let me repair, it just croaked at the install screen. So I stripped it out and restarted basically.

So, what is this about a fix to 2000i? He doesn't have any issues what so ever with 2000i, just 2006 is super slow when he has an image loaded in the drawing, in this case several. On the other hand, in 2000i there is no speed issue in the same drawing(s).

Heidi

[Anonymous]

2006 takes more memory than 2000i to run. Usually 1 GB is enough for 2006
until you get in to very large files. Watch your memory usage and see if
you notice a difference between the two.

Brad

wrote in message news:5217261@discussion.autodesk.com...
Ok so I haven't installed SP 1 or 2 yet because, time. I didn't have the
time yesterday while my coworker was gone, it's his machine and he needs it
today! I plan on installing those on Monday when he's gone.

Repair? I intially had issues with LDT 2006 not letting me save back to
different formats and I think that was from migrating the settings over from
2000i. There was also the issue where you loaded map enabled and it gave
you LDT but you couldn't get them separated. That had nothing to do with
how they were installed or opened, it just freaked out. Had that happen
before and had to repair, but his machine wouldn't let me repair, it just
croaked at the install screen. So I stripped it out and restarted
basically.

So, what is this about a fix to 2000i? He doesn't have any issues what so
ever with 2000i, just 2006 is super slow when he has an image loaded in the
drawing, in this case several. On the other hand, in 2000i there is no
speed issue in the same drawing(s).

Heidi

[Anonymous]

I realize that the ram may have something to do with this. I'll have to watch this after I install the SP's on Monday. I just thought there might be a quick fix for today. Otherwise what we opened up in 2006 was saved back to 2000 and now when he opens we keep on getting that Arch. Desktop object enabler message for some reason. Even though I installed the 2004 OE for 2000i.

Thanks for the help though.
Heidi

[Anonymous]

It's not the ram. LDT 2006 is just slow.

I think Autodesk's company line is "Why don't you have the newest fastest
computer available?" I do, and 2GB of RAM, and the latest patches, and the
lastest drivers, and a gigabit network. I also keep the drawings small
(typically less than 1MB), although I do multitask a lot (usually
outlook/excel/vba/Land(2-4 sessions)/winamp). After opening the first
session, the rest are faster, but I've found that if I'm working with
anything calculation intensive, it's quicker to fire up 2000...

You can turn off all the new options that have been added recently (object
highlighting, dynamic input, etc.) and it'll still be slower than 2000. In
particular, menu loading, the CUI editor and layer dialog just crawl. They
worked just fine before. If it isn't broke... what happened?

BTW, don't use SAVEAS to save back to 2000. You have to use a feature
called "export to AutoCAD"... or type in _AECCEXPORTTOAUTOCAD2000. It's in
the Land Desktop File menu, not the AutoCAD file menu. That command is the
only reliable way I know of to remove the "Architectural Desktop" errors
you're getting.

If you're going back and forth between 2000/2004/2006, you'll also want to
locate and use a program called PurgeIDs (I think I found it in one of these
newsgroups, but you can google it), to get rid of AppIDs that get imported
into r2000 versions. The appids spread like a virus from drawing to drawing
by xrefing. When we started using PurgeIDs, our typical drawing had
ballooned by 1.5MB each, because of about 50,000 unused APPIDs,... After
using PurgeIDS, the drawings were reduced to their normal size of about
100-200KB... and opened a lot faster without the ADT errors. The program
has some quirks, but it does the job.

Good luck
- Aaron Lance

wrote in message news:5217304@discussion.autodesk.com...
I realize that the ram may have something to do with this. I'll have to
watch this after I install the SP's on Monday. I just thought there might
be a quick fix for today. Otherwise what we opened up in 2006 was saved
back to 2000 and now when he opens we keep on getting that Arch. Desktop
object enabler message for some reason. Even though I installed the 2004 OE
for 2000i.

Thanks for the help though.
Heidi

[Anonymous]

Aaron thanks for the reminder re. PurgeIDs.

I'm going to have to hunt down the copy I have put somewhere?

Or just Google it;
http://tinyurl.com/oqbqq

It's the Zip file attached to James Maeding's post.

HTH


--
Don Reichle
"The only thing worse
than training your staff,
and having them leave is -
not training your staff,
and having them stay."
Courtesy Graphics Solution Providers
----------------------------------------------------------
!! Please discuss whatever we tell you with your SysMgr !!
!! They appreciate staying in the loop 🙂 !!

LDT/CD-2K4
AMD Athlon 64 X2 Dual 2.01GHz
XPPro 32bit SP2
2GB RAM
Dual WD800JD Hard Drives - 149GB Nvidia Stripe
Nvidia Quadro FX 1300 128MB
Dual ViewSonic 19-inch VA902b monitors



Aaron Lance wrote:
> It's not the ram. LDT 2006 is just slow.
>
> I think Autodesk's company line is "Why don't you have the newest fastest
> computer available?" I do, and 2GB of RAM, and the latest patches, and the
> lastest drivers, and a gigabit network. I also keep the drawings small
> (typically less than 1MB), although I do multitask a lot (usually
> outlook/excel/vba/Land(2-4 sessions)/winamp). After opening the first
> session, the rest are faster, but I've found that if I'm working with
> anything calculation intensive, it's quicker to fire up 2000...
>
> You can turn off all the new options that have been added recently (object
> highlighting, dynamic input, etc.) and it'll still be slower than 2000. In
> particular, menu loading, the CUI editor and layer dialog just crawl. They
> worked just fine before. If it isn't broke... what happened?
>
> BTW, don't use SAVEAS to save back to 2000. You have to use a feature
> called "export to AutoCAD"... or type in _AECCEXPORTTOAUTOCAD2000. It's in
> the Land Desktop File menu, not the AutoCAD file menu. That command is the
> only reliable way I know of to remove the "Architectural Desktop" errors
> you're getting.
>
> If you're going back and forth between 2000/2004/2006, you'll also want to
> locate and use a program called PurgeIDs (I think I found it in one of these
> newsgroups, but you can google it), to get rid of AppIDs that get imported
> into r2000 versions. The appids spread like a virus from drawing to drawing
> by xrefing. When we started using PurgeIDs, our typical drawing had
> ballooned by 1.5MB each, because of about 50,000 unused APPIDs,... After
> using PurgeIDS, the drawings were reduced to their normal size of about
> 100-200KB... and opened a lot faster without the ADT errors. The program
> has some quirks, but it does the job.
>
> Good luck
> - Aaron Lance
>
> wrote in message news:5217304@discussion.autodesk.com...
> I realize that the ram may have something to do with this. I'll have to
> watch this after I install the SP's on Monday. I just thought there might
> be a quick fix for today. Otherwise what we opened up in 2006 was saved
> back to 2000 and now when he opens we keep on getting that Arch. Desktop
> object enabler message for some reason. Even though I installed the 2004 OE
> for 2000i.
>
> Thanks for the help though.
> Heidi

[Anonymous]

At the command line type in

mapskinmap

Do this in both LDT and LE Map

--
Karl M. Fuls PLS
Autodesk Discussion Group Facilitator
AEC Training and Consulting


tsaxy wrote:
> Ok so we're aren't going to 2007 for some time. But here's my issue. I just installed LDT Comp 2006 on a computer here. License is on the computer, stand alone type. Yes, I installed C3D 2006. No I haven't put the patches on yet.
>
> From the get go this program, LDT and Land Map Enabled run like DOGS! We load a drawing with an image and it's super slow, like 5 min. to load.
>
> Consider that 2000i is on the machine also, that's what we're upgrading form and there is absolutely no performace issues with that version.
>
> I DID NOT migrate settings over, it screwed it up last time. This time I uninstalled, took off all the Service packs, took off all the object enablers, rebooted then reinstalled LDT 2006 companion and Civil Design.
>
> So with that said, what would be causing the program to run so slow.
>
> 1GB RaM
> Win Media (ya I know)
> 2.36GHZ intel chip
>
> Heidi

[Anonymous]

Exactly what does that command effect? Mapskinmap. From what I can tell it just changes the skin of the program. Does this also effect how fast images are rendered and used within the program?

Heidi

[Anonymous]

strictly cosmetics

--
Dana Breig Probert
http://civil3drocks.blogspot.com/
CADapult Ltd
Empowering Design With Innovative Solutions
www.cadapult.net
----------------------------------------------
wrote in message news:5227169@discussion.autodesk.com...
Exactly what does that command effect? Mapskinmap. From what I can tell it
just changes the skin of the program. Does this also effect how fast images
are rendered and used within the program?

Heidi

[Anonymous]

Using only its name brings up 8 occurrences on a Search of the Knowledge
Base Heidi;
http://tinyurl.com/ph5ag

Maybe Karl will be back to explain a little more of his intentions re. this.

--
Don Reichle
"The only thing worse
than training your staff,
and having them leave is -
not training your staff,
and having them stay."
Courtesy Graphics Solution Providers
----------------------------------------------------------
!! Please discuss whatever we tell you with your SysMgr !!
!! They appreciate staying in the loop 🙂 !!

LDT/CD-2K4
AMD Athlon 64 X2 Dual-Core 3800+ 2.01GHz
XP-Pro 32bit SP2
2GB RAM
Dual WD800JD Hard Drives - 149GB Nvidia Stripe
Nvidia Quadro FX 1300 128MB
Dual ViewSonic 19-inch VA902b monitors

"The only Constant is Change".


wrote in message news:5227169@discussion.autodesk.com...
Exactly what does that command effect? Mapskinmap. From what I can tell it
just changes the skin of the program. Does this also effect how fast images
are rendered and used within the program?

Heidi

[Anonymous]

That would be nice, wouldn't it. Heidi

[Anonymous]

i mean, mapskin is strictly the way the interface looks (looks "cool") but
turning it off increases your performance cause it isn't trying to look cool

--
Dana Breig Probert
http://civil3drocks.blogspot.com/
CADapult Ltd
Empowering Design With Innovative Solutions
www.cadapult.net
----------------------------------------------
wrote in message news:5227955@discussion.autodesk.com...
That would be nice, wouldn't it. Heidi

[Anonymous]

Exactly.....

I'm not sure exactly what it does, but it does improve startup performance.

--
Karl M. Fuls PLS
Autodesk Discussion Group Facilitator
AEC Training and Consulting

Dana Breig Probert wrote:
> i mean, mapskin is strictly the way the interface looks (looks "cool") but
> turning it off increases your performance cause it isn't trying to look cool
>