MS Installer 2.0 and Office 2000

MS Installer 2.0 and Office 2000

Post by Anthony Fremon » Sat, 25 Jan 2003 15:08:17



Hello all,

I'm now recovering from a recent traumatic experience involving Office 2000
SBE.  I have a customer that happens to use Office 2000 SBE and their
store-bought CD is a first version pressing.  IOW, it's not MSO 2000 SR-1,
it's a prior release.

You might not think that there would be anything significant about that, but
there is a dirty secret that I seem to have stumbled upon.  As some of you
may already know, M$ has upgraded the Installer to version 2.0.  It just so
happens that to apply some (if not all) of the patches using OfficeUpdate
you have to install MS Installer 2.0, if it's not yet installed.

This is where things get interesting.  Once you install the 2.0 Installer,
you can no longer do a repair or reinstall from the first release CD.  Once
you stick the disk in, the Installer takes control and runs thru the
process without asking you what you want done.  :-O  Afterwards, your
Office installation is unusable.  You basically have to wipe the registry
out and start over, there is no fixing it since you can't remove Installer
2.0.  BTW, the OS is Win98SE.

Apparently, Installer 2.0 is incompatible with the format of the information
on the first release Office 2000 CD, and doesn't install the software
correctly leaving an unusable mess.  Now it's a catch-22 situation, after
fixing everything you can't go to OfficeUpdate or it will break things
again.  I'm sure that it's only a matter of time before the user has
Installer 2.0 back on their machine.

Thank you so much MS for being incompatible with your own stuff.  Par for
the course, I guess.

SAME STORY, DIFFERENT TWIST (this happened a few days before the above
issue)

I just replaced a couple of computers for another customer, they have about
20 connected to a Novell (soon to be Linux) network.  Everybody runs Win98
and they want to keep it like that for now, no problem I say.

Of course I inform them that they will have to spend as much for new
software as the new hardware will cost.  They cringe, but agree that they
have to stay legal.

Since everyone else is using Office97 still, I recommended Office 2000 SBE
over Office XP, figuring that there would be fewer problems with
compatibility.

Imagine my surprise when I pick up my shiny new OEM Office 2000 SBE's that
now include PRODUCT ACTIVATION.  :-/  I think to myself, amazing, they
retrofitted it in, I'm sure this is going to be neat.  I figure so what,
it's not that big of a deal and the customer has nothing to hide anyway.

I put the (identical) computers together and installed Win98 on one.  Once I
had that all done and all the other nit-noy stuff installed, I decided to
install Office.  So, I opened the package and stuck the CD in the drive.  
You'll never guess what happened next.

The disk auto-played and went thru the installation without prompting me for
the components I wanted installed (sounds familiar huh?).  After a reboot
so that the installer could continue configuring Office, it went thru the
stupid blue line accross the box multiple times *and then finally
finished.  Well guess what, none of the apps worked they just froze part of
the way open.  I went to OfficeUpdate and this where I learned about
Installer 2.0.  I downloaded Installer 2.0 and installed it and then ended
up reinstalling Office.  Now things worked right, amazing.

SUMMARY

It seems that the first release Office 2000 cd's can't be used with
Installer 2.0.  It also appears that the latest cd's (with PA) require 2.0,
but don't have sense enough to install it automatically.

THANK YOU MS, FOR NOTHING (and wasting about 8 or 10 hours of my time)

Now maybe Simon or EF can tell me about the benifits of all this nonsense.  
I think I'm going to recommend to my customer to just upgrade all their
computers and switch to Open Office.  They can buy twice as many new
computers and still open Word documents.  Free goes a long way with them.  
It makes a few problems and inconveniences completely worthwhile.

--
michael brown

  6:32am  up 70 days, 20:02,  1 user,  load average: 0.25, 0.09, 0.02

 
 
 

MS Installer 2.0 and Office 2000

Post by Sinister Midge » Sun, 26 Jan 2003 02:48:08



Quote:> Hello all,

> I'm now recovering from a recent traumatic experience involving Office 2000
> SBE.  I have a customer that happens to use Office 2000 SBE and their
> store-bought CD is a first version pressing.  IOW, it's not MSO 2000 SR-1,
> it's a prior release.

> You might not think that there would be anything significant about that, but
> there is a dirty secret that I seem to have stumbled upon.  As some of you
> may already know, M$ has upgraded the Installer to version 2.0.  It just so
> happens that to apply some (if not all) of the patches using OfficeUpdate
> you have to install MS Installer 2.0, if it's not yet installed.

> This is where things get interesting.  Once you install the 2.0 Installer,
> you can no longer do a repair or reinstall from the first release CD.  Once
> you stick the disk in, the Installer takes control and runs thru the
> process without asking you what you want done.  :-O  Afterwards, your
> Office installation is unusable.  You basically have to wipe the registry
> out and start over, there is no fixing it since you can't remove Installer
> 2.0.  BTW, the OS is Win98SE.

> Apparently, Installer 2.0 is incompatible with the format of the information
> on the first release Office 2000 CD, and doesn't install the software
> correctly leaving an unusable mess.  Now it's a catch-22 situation, after
> fixing everything you can't go to OfficeUpdate or it will break things
> again.  I'm sure that it's only a matter of time before the user has
> Installer 2.0 back on their machine.

> Thank you so much MS for being incompatible with your own stuff.  Par for
> the course, I guess.

> SAME STORY, DIFFERENT TWIST (this happened a few days before the above
> issue)

> I just replaced a couple of computers for another customer, they have about
> 20 connected to a Novell (soon to be Linux) network.  Everybody runs Win98
> and they want to keep it like that for now, no problem I say.

> Of course I inform them that they will have to spend as much for new
> software as the new hardware will cost.  They cringe, but agree that they
> have to stay legal.

> Since everyone else is using Office97 still, I recommended Office 2000 SBE
> over Office XP, figuring that there would be fewer problems with
> compatibility.

> Imagine my surprise when I pick up my shiny new OEM Office 2000 SBE's that
> now include PRODUCT ACTIVATION.  :-/  I think to myself, amazing, they
> retrofitted it in, I'm sure this is going to be neat.  I figure so what,
> it's not that big of a deal and the customer has nothing to hide anyway.

> I put the (identical) computers together and installed Win98 on one.  Once I
> had that all done and all the other nit-noy stuff installed, I decided to
> install Office.  So, I opened the package and stuck the CD in the drive.  
> You'll never guess what happened next.

> The disk auto-played and went thru the installation without prompting me for
> the components I wanted installed (sounds familiar huh?).  After a reboot
> so that the installer could continue configuring Office, it went thru the
> stupid blue line accross the box multiple times *and then finally
> finished.  Well guess what, none of the apps worked they just froze part of
> the way open.  I went to OfficeUpdate and this where I learned about
> Installer 2.0.  I downloaded Installer 2.0 and installed it and then ended
> up reinstalling Office.  Now things worked right, amazing.

> SUMMARY

> It seems that the first release Office 2000 cd's can't be used with
> Installer 2.0.  It also appears that the latest cd's (with PA) require 2.0,
> but don't have sense enough to install it automatically.

> THANK YOU MS, FOR NOTHING (and wasting about 8 or 10 hours of my time)

> Now maybe Simon or EF can tell me about the benifits of all this nonsense.  
> I think I'm going to recommend to my customer to just upgrade all their
> computers and switch to Open Office.  They can buy twice as many new
> computers and still open Word documents.  Free goes a long way with them.  
> It makes a few problems and inconveniences completely worthwhile.

Ewik and Simon might be good sources. They can add great programmer and
consultant views about these things. But I think this is right up the
alley of Rich "Ding-Dong" Bell. He's certainly well-versed in the
goings on of the multiple WinDOS versions. He can surely explain what
_should_ have been done to get this all to play happy together!

--
"One world, one web, one program"  -- Microsoft promotional ad
"Ein Volk, ein Reich, ein Fuehrer"  -- Adolf Hitler

 
 
 

1. MS Office 2000 is buggy, buggy, buggy

My day today with MS Office 2000:

I'm a programmer and was asked to prepare documentations and a presentation,
something no programmer really likes. Well, I swore and thought, lets just
slap something together quickly with Word and Powerpoint... I was mistaken.

The g**m Word crashed on me five times. Each time, after restarting Word
again, I could not open the file I was working on previously. Word
complained: "File locked by <me>".

After a while, I found out that I actually have to

1) kill the (window-less) process WINWORD.EXE and
2) delete all hidden files starting with '~'

before I could go on and open the file again. Being a programmer, I wrote
myself a tool to do this automatically.

"Ease of use"? Yeah right, I can just see all the secretaries just opening
the taskmanager and killing processes...

Poor, poor, poor quality. Amazing what they get away with.

More issues:
- The graphical component (vector graphics) inside MS Word and Powerpoint is
a Joke. No, really. The behaviour is often illogical and unpredictable. It
also caused two of my five crashes. Scaling groups of objects does not work
properly. And so on. Pure pain - I wish I had Visio installed or some other
*professional* Graphics tool.
- Importing data from Word to powerpoint is error prone, to say the least.
Tables get scr*ed up.

As a bottomline, this will be the last presentation I prepared using MS
Office.

2. Linux Video Server

3. Somewhat Off-Topic -- Hefty Minimum MS Office 2000 Hardware Requirements/Bloatware At Its Best (Worst?)

4. How do I contribute to ports?

5. Is StarOffice 5.2 "compatible" w/MS Office 97/2000?

6. Apsfilter and HP710c

7. Intel Wabi 2.0 and MS OFfice

8. mpeg_play name

9. Wabi 2.0 and MS-Office 4.2?

10. How to Install MS-OFFICE 4.3 under Wabi 2.0

11. Wabi 2.0; network install MS Office and/or Project fails

12. Can I run MS office files with Star Office on linux?

13. Is Star Office just as crash prone as MS Office?