7.5meg file, 30 minute install,... Priceless!!

If my calculator serves me correctly - 32 hours.....hmmmm.

WT

Oh, also, the other funny moment was when the popup showed "0" minutes remaining during a ~10 minute duration!?

And of course, the total popups.. 89, (install #1 CD) 10, 5,.. 0, 8, 5, (install #3 CD) 0,... = ~30 mins.

Man, the sp2.1 and recent sp2 WI upgrades are convoluted install worm holes!

As most of you are aware, the WI is mainly about "PIRACY", which = revenue, not end user productivity.

And, a 2.4 meg log file!?? Wow, could there be enough information there... and... for what??

Yes, M$ Corp, may I have another!!??

..

Paul Salvador wrote:

I'm not fully aware. How is this headache supposed to prevent piracy? Because I need the install CDs? If that's it, then somebody is having a good laugh somewhere.

Oh, I agree, it's a total laugh!! It's beyond a joke = stupidly insane!

IMHO, M$ and SW Corp will "NEVER" win the fight against piracy!!

They're fools. Hey, everyone's gotta have a yob.

Man, the guys cracking only become more interested,.. it's psychology

..

Dale Dunn wrote:

BTW, sp2.0 installed in ~20 minutes, iirc?

..

Wayne Tiffany wrote:

See that's the rub... "cd's req'd" was the marketing snow that caused someone to buy into WI (wow, we can prevent piracy was this, cool, let's do it). To the actual user, or thief if applicable, it doesn't prevent a damn thing. So the honest end user suffers. Nothing gained, only time lost. Before any ex-app engineer's chime in about rolling back, we all know it was easier and faster to uninstall/reinstall and restore settings through a reg file.

Sort of reminds me of the extra security precautions that we have to go through now. It doesn't really help but it makes some people "feel" better and makes everyone else feel more inconvenienced.

Don't blame SW developers, blame the project manager (or team) at SW that bought into it.

- Eddy

CSWPComplainer

Jeff "Can I be a SWWorld Keynote Speaker in 2005?"

I haven't installed yet and waiting on the rest of you to figure it all out! Anyways, I'm still busy beta testing 2004/SP1

Kman

I'd like to know why it's taking everyone so long to install this SP2.1?

I installed it on 3 machines, 2 of them from 2.0 to 2.1 and 1 machine from 0.0 to 2.1. Each of these machines was done in about 10 to 15 minutes. Someone else I spoke with at a company I used to work at also installed it in the same amount of time. No errors when installing it and no errors running it after the upgrade.

What are you guys doing that is making install so slow? Or is it just because your computers are so old that they are really slow?;-)

snipped-for-privacy@elakeside.com (Richard Charney) wrote in news: snipped-for-privacy@posting.google.com:

If I knew that, I wouldn't do it. My Athlon 1400 isn't new, but it's not all that slow either.

Richard,

I think it may have to do with the previous sp's installed and the options/addins you include? So, (I have) if you had sp0, sp1, sp2 installed, then sp2.1 would take longer than a sp0-sp2.1 install?

BTW, iirc, the WI install times per sp for me were... (no less than listed but I walked away for a few minutes on two installs)

sp0 = ~15 mins (may have been taken longer??) sp1 = ~15-20 mins (121.5 megs) sp2 = ~20 mins (77 megs, may have taken longer?) sp2.1 = ~30 mins (only 7.5 megs!?, and why I posted)

(I'd guess a sp0-sp2.1 install may take about 15 mins?)

And, I think I'm installing faster than others and I don't think the machine I'm using is that slow? P4 3.0, 800mhz FSB, 2 gigs ram, 80gig sata hdrive, 48X cd.

So, the longer times could be from users with slower/older systems? Or, it may also have to do with the OS? I have Win2000Pro sp4, XP sp1a maybe faster? And, could be network related? (I'm not on a network)

..

Richard Charney wrote:

Also, note, I'm not adding eDrawing updates or the help files which are about 5+ mins extra?

..

Paul Salvador wrote:

Richard,

Consider yourself lucky.

And "what" if anything could "we" possibly do to make it slower. Why would we want too ?

Mark

Machine speed does seem to be involved. My Athlon 1400 did 2.0 to 2.1 in about twice the time of your P4 3000.

I guess I was just more curious as to what most of you thought was wrong. Of course nobody wants it to be slow on purpose.

I'm just assuming that our new computers are part of why it installed so fast. The 2 machines that we went from 2.0 to 2.1, we had installed each previous service pack as they came out(0.0 to 1.0, 1.0 to 2.0). So I really don't see any reason how having cumulative service packs install would differ from going from 0.0 to 2.1. They were the same amount of time for us. The only difference was that the 2.0 to 2.1 upgrade was on a P4 3.2Ghz machine with 1Gb of memory running WinXP Pro. The 0.0 to 2.1 install was on a P3 800Mhz machine with 1Gb of memory running Win 2000.

At any rate, I guess I should consider myself lucky.

Something to take a look at guys if you haven't already:

I just did the update from 2.0 to 2.1 over lunch - took 30 minutes, and the only hitch was that it couldn't reboot my machine - had to do it myself. Other than taking a long time, went pretty well.

WT

Mark,

If they were only using Install Shield, they wouldn't even need that page. !!!

WHY replace something simple and reliable, with something complicated and error prone.

They really didn't think this through at all. For instance, we "HAVE" to run multiple versions on the same machines. Not only for testing but for client compatibility. They really must think (if they think at all, which I doubt) we blindly install their software and start working. No one does that !!!

I'm really worried about SW future with my company. We haven't put 2004 into production yet, and my bosses aren't aware (yet) of all of the problems we "WILL" have when we implement it. They'll probably tell me to start seriously looking at other solutions. We're the sole engineering resource for many of our clients, so if we switch, they'll switch.

I would like to continue our relationship with SW, but they just continue to mindlessly make it harder for me to do so.

Regards

Mark