Jump to content

How to install Outlook without OE


visitor

Recommended Posts

We know the normal, full functionality of Outlook won't be available w/out OE, but we are looking to install Outlook XP (2002) strictly for purposes of viewing/editing the contacts & calendar data.

This is for a WinFLP installation that allowed the OS to be setup without IE, OE & WMP. Installing the Office suite, including Outlook, succeeds (noting errors registering MsRclr40.dll & VEN2232.olb). Outlook will not run, though, complaining that OE is not installed.

Again, we are only looking to use Outlook to work with PST files (which OE does not support) and NOT trying to access eMail, newsgroups, etc...

ThaNX

Link to comment
Share on other sites


Cannot say if this is of any help, but here:

http://koti.mbnet.fi/digitale/throwoutoe/

is a "stand-alone" OE uninstaller.

Since it is in the form of a batch file it is very easy to modify it.

Maybe if you monitor with tools like Regmon, Procmon and Filemon from Sysinternals an install with both Outlook and OE, you could determine what parts of OE need to be kept to mantain the functionality you need (and thus you remove the corresponding line from the batch).

Fred Vork has a similar (said to be more thoroughful) PE uninstall in the form of an .inf file here:

http://www.vorck.com/ie-cleanup.html#oe

If you are not familiar with .inf files, here is a VERY good start:

http://www.boot-land.net/forums/Useful-inf...-inf-t1966.html

I guess starting with either of this bases it should be a matter of a few attempts.

jaclaz

Edited by jaclaz
Link to comment
Share on other sites

Very useful references, thaNX.

Being pretty lazy, though, and in line with our original intent - would there be an effective way to analyze the error messages from Outlook when it finds components of OE missing and approach the problem from that end?

I know it might be more complicated to acquire the missing files/settings that are not installed than to install OE & then remove all but the files/settings Outlook wants. That is more the approach we'd prefer to take on this, if possible.

Anyways, I will look into the INF & OE removal information in the meantime...

B)

Link to comment
Share on other sites

would there be an effective way to analyze the error messages from Outlook when it finds components of OE missing and approach the problem from that end?

Well, in my experience, error messages, with a particular emphasis on those generated by "microsoft Office related apps" tend to be so deceiving to be in a large number of occasions of no practical use.

You will find much sooner what you are missing analizing the running processes with monitor tools as already mentioned and running tools like "Dependency Walker" or similar ones to make a quick list of .dll's required by Outlook.

After having run Dependency Walker on the Outlook .exe and .dlll files, you could have some "basic" missing files that you can try adding to the install (those "hard referenced" in the .exe's).

Than you fire up Filemon and Regmon filtering out all the .exe's you have running but those you presume create the error and see what they are looking for when running and add any component found missing.

For Registry entries you might want to have a "parallel" build (working and with Outlook Express installed) to peek into it's Registry and copy the keys found missing on the "experimental" build.

The removal files linked to can be however a good reference for making an "inversed" .inf file, i.e. one that only installs the required files and Registry entries of Outlook Express.

Most probably you will need a batch, an Auto-it or VBS script to manage those Registry entries that are generated "on the spot" by the standard MS installer on a "per-machine" basis.

Also, for the little I know about WINFLP, since it is a somewhat "limited" version, maybe it is better if you do the experimental work in a full XP (so to be sure that none of the possible WINFLP limits "get in the way") and only later test your partial installer on WINFLP, doing, if necessary the needed adjustements.

jaclaz

Link to comment
Share on other sites

...analizing the running processes with monitor tools as already mentioned and running tools like "Dependency Walker" or similar ones to make a quick list of .dll's required by Outlook.

After having run Dependency Walker on the Outlook .exe and .dlll files, you could have some "basic" missing files that you can try adding to the install (those "hard referenced" in the .exe's)...

Great suggestion, jaclaz. In fact we do have at least one other system here running Outlook XP under the normal condition of having OE installed with Windows. Sounds like the perfect place to start. :thumbup
Link to comment
Share on other sites

  • 3 weeks later...

This turned out to be a lot simpler than expected :yes:

The registry entry shown under Method 2 -> Step 1 @ http://support.microsoft.com/kb/320863 appears to be the reference for Outlook looking for OE.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{44BBA848-CC51-11CF-AAFA-00AA00B6015C}]

"IsInstalled"=dword:00000001

"DontAsk"=dword:00000002

"ComponentID"="MailNews"

@="DirectShow"

"Locale"="EN"

"Version"="10,0,0,3802"

B)

Edited by visitor
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...