Microsoft office on XPE

[Guest]

Hi everyone,

There are a number of posts on installing MS office 2000 or 2003 on XPe.

I would like to confirm my understanding:
1) It is not legal to install MS office on XPE due to licensing issues?
2) It is possible to install MS office on XPE technically.
3) There are some errors that were encountered while installing MS office
2003 in XPE SP1:
- Setup cannot register module MSRCLR40.dll
- Error configuring ODBC data source: MS Access Database, ODBC error13:
Could not load up the setup or translator library
- Setup cannot register type library for file VEN2232.olb
Can these errors be resolved on a runtime? If not, what are the components
that need to be added to the image? Null device pointer?

4) Finally can XPE be used on for Access, Excel Files, Visual FoxPro, dBASE?

Many thanks!

 

[twicave]

Technical answer: Yes.
you may need create your own component to enable installation.
and add the following component:
"Microsoft VB Runtime 6.0"
all ODBC related component found in "Software\system service\application"


in fact,you can find it out which component or files are needed by using
"RegMon" and "FileMon".
the expert who give answer to you just use these simple tools.

 

[Gordon Smith \(eMVP\)]

Hi everyone,

There are a number of posts on installing MS office 2000 or 2003 on
XPe.

I would like to confirm my understanding:
1) It is not legal to install MS office on XPE due to licensing
issues? 2) It is possible to install MS office on XPE technically.
3) There are some errors that were encountered while installing MS
office 2003 in XPE SP1:
- Setup cannot register module MSRCLR40.dll
- Error configuring ODBC data source: MS Access Database, ODBC
error13: Could not load up the setup or translator library
- Setup cannot register type library for file VEN2232.olb
Can these errors be resolved on a runtime? If not, what are the
components that need to be added to the image? Null device pointer?

4) Finally can XPE be used on for Access, Excel Files, Visual FoxPro,
dBASE?

Many thanks!

1. You are allowed to have office components in your build if they are in
direct support of your embedded application. You can't have office sitting
around for general purpose work.

2. Yes - although you need to figure out which components are necessary to
support the install.

3. I believe this was answered in "twicave"'s response.

4. Yes. If you are using all of those file types, you'd probably want to
use Jet and it's ability to access those file types through Installable
ISAMs.

 

[Guest]

Hello,

Thanks Twicave and Gordon for your responses.

I am not trying to include Office in the image, but sometimes, customers
want to install it themselves and then run into problems. Is there also a
license issue for the customers to try install Office themselves too?

When you mentioned include the components, do you mean I have to
componentize Office, or do I have to include components that are missing and
are required to run Office? For Run time images, since I already cannot patch
it with components, is it ok to just copy and paste the required files over?
Will just adding the MS VB 6.0 runtime library be sufficient to support
Office? I don't have Office 2003 with me, so I can't verify right away what
files are needed.

For the part on Jet, currently I only have Jet Database Engine and Jet
Database OLEDB support. Did you mean that I should add all the available Jet
database components to my image?

Many thanks!