6 replies to this topic

[JoeThompson]

If my target machine has Windows 2000, do I need the OLEAUT32.MSM as part of my project or can I assume it is already installed?

Thank you,
Joe

[Kurt Schneider]

Joe,

It's not the best idea to assume that it will be there.  You're better off including it in your setup.  Most likely the file will already exist and therefore will not be installed anyways.  That file is also a pretty common dependency of many other MSM's and could screw things up if not included.

Kurt Schneider

[JoeThompson]

Kurt,

I guess I'll leave it then to be safe.  I didn't originally write this installation and am by no means an expert at installations so I don't really know what some things do.  It just seems to take a long time to "merge" this module during the build process so I thought I might delete it.

Anyway, thanks for the reply...

Joe

[Kurt Schneider]

Joe,

How long is long?

Kurt

[JoeThompson]

Kurt,

I just did a build tables only to see.
The other merge modules (COMCAT, MFC42, MFC42U, MSVCIRT, MSVCP60, and MSVCRT) all take about 3 seconds.  But when it gets to OLEAUT32 it takes about 4 minutes on my machine.  Either that or the next line "File table successfully built" is not showing but is what is actually happening.  That may make since being that I have alot of files...
What do you think?

Thanks you,
Joe

[Kurt Schneider]

Joe,

Your exactly correct.  I remember seeing the same behavior at my end.  The result pane used to hang up merging one of my .MSM's, when in actually that part had finished and it was actually build a vast file table.

Sounds pretty normal

Kurt

[JoeThompson]

Cool.  Thanks for the info...

Joe