office2003 install error

  • Thread starter Thread starter Mark Hempstead
  • Start date Start date
M

Mark Hempstead

have an embedded XP sp2 install - try to install office 2003 and it
complains "ven2232.OLB" can't be registered.
I've hunted through to make sure i've got all the relevent mdac
components but still no luck
any ideas?
how can you actually tell what software components you need, is there a
software equivalent to "tap"???

Thanks
Mar
 
For the record, I believe that it's a violation of the license agreement to install Office on an XPE device. :-)

For app components. a good way to componetize an app, is to install it on a XP Pro box, and sysdiff the unit.

Here's an article on app componetization: http://msdn.microsoft.com/library/d...p/html/xehowhowtocomponentizeapplications.asp

HTH,
JC



--
John Coyne- Windows Embedded Black Belt- XPE and CE
BSquare Corp.
If you wish to reply directly to me, remove the <nospam_ > from the address.
______________________________________________________________________________
have an embedded XP sp2 install - try to install office 2003 and it complains "ven2232.OLB" can't be registered.
I've hunted through to make sure i've got all the relevent mdac components but still no luck
any ideas?
how can you actually tell what software components you need, is there a software equivalent to "tap"???
Thanks
Mar
 
<callto://markhempstead/>

Thanks JC - I'll try that.

re. licensing, I'm a bit concerned over this as it's a commercial
project, why would office on a dedicated embedded device be in breach of
the XPe license?

_____

From: JC [mailto:JCBSQ@nospam_yahoo.com]
Posted At: 04 March 2005 17:30
Posted To: microsoft.public.windowsxp.embedded
Conversation: office2003 install error
Subject: Re: office2003 install error


For the record, I believe that it's a violation of the license agreement
to install Office on an XPE device. :-)

For app components. a good way to componetize an app, is to install it
on a XP Pro box, and sysdiff the unit.

Here's an article on app componetization:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp
/html/xehowhowtocomponentizeapplications.asp

HTH,
JC



--
John Coyne- Windows Embedded Black Belt- XPE and CE
BSquare Corp.
If you wish to reply directly to me, remove the <nospam_ > from the
address.
________________________________________________________________________
______

have an embedded XP sp2 install - try to install office 2003 and it
complains "ven2232.OLB" can't be registered.
I've hunted through to make sure i've got all the relevent mdac
components but still no luck
any ideas?
how can you actually tell what software components you need, is there a
software equivalent to "tap"???

Thanks
Mar
 
Mark,

Office by default fall in the category of non embedded usages and it is against the license that you have signed. If you feel otherwise contact MS legal departement and try to convince them in why you need this and how it fall in to the embedded usage.

More about office and XPe:
http://groups-beta.google.com/group...oft.public.windowsxp.embedded&q=office&qt_g=1

Regards,
Slobodan



Thanks JC - I'll try that.

re. licensing, I'm a bit concerned over this as it's a commercial project, why would office on a dedicated embedded device be in breach of the XPe license?



------------------------------------------------------------------------------
From: JC [mailto:JCBSQ@nospam_yahoo.com]
Posted At: 04 March 2005 17:30
Posted To: microsoft.public.windowsxp.embedded
Conversation: office2003 install error
Subject: Re: office2003 install error


For the record, I believe that it's a violation of the license agreement to install Office on an XPE device. :-)

For app components. a good way to componetize an app, is to install it on a XP Pro box, and sysdiff the unit.

Here's an article on app componetization: http://msdn.microsoft.com/library/d...p/html/xehowhowtocomponentizeapplications.asp

HTH,
JC



--
John Coyne- Windows Embedded Black Belt- XPE and CE
BSquare Corp.
If you wish to reply directly to me, remove the <nospam_ > from the address.
______________________________________________________________________________
have an embedded XP sp2 install - try to install office 2003 and it complains "ven2232.OLB" can't be registered.
I've hunted through to make sure i've got all the relevent mdac components but still no luck
any ideas?
how can you actually tell what software components you need, is there a software equivalent to "tap"???
Thanks
Mar
 
Mark,

You should read the definition of an embedded system in Windows XP Embedded Licensing Requirements and Guidelines:
http://msdn.microsoft.com/library/d...xpembeddedlicensingrequirementsguidelines.asp

Also, this FAQ will be helpful to you to answer some licencing question:
http://www.bsquare.com/licenses/resourcecenter/faqswinxpembed.asp

KM

Thanks JC - I'll try that.

re. licensing, I'm a bit concerned over this as it's a commercial project, why would office on a dedicated embedded device be in breach of the XPe license?



------------------------------------------------------------------------------
From: JC [mailto:JCBSQ@nospam_yahoo.com]
Posted At: 04 March 2005 17:30
Posted To: microsoft.public.windowsxp.embedded
Conversation: office2003 install error
Subject: Re: office2003 install error


For the record, I believe that it's a violation of the license agreement to install Office on an XPE device. :-)

For app components. a good way to componetize an app, is to install it on a XP Pro box, and sysdiff the unit.

Here's an article on app componetization: http://msdn.microsoft.com/library/d...p/html/xehowhowtocomponentizeapplications.asp

HTH,
JC



--
John Coyne- Windows Embedded Black Belt- XPE and CE
BSquare Corp.
If you wish to reply directly to me, remove the <nospam_ > from the address.
______________________________________________________________________________
have an embedded XP sp2 install - try to install office 2003 and it complains "ven2232.OLB" can't be registered.
I've hunted through to make sure i've got all the relevent mdac components but still no luck
any ideas?
how can you actually tell what software components you need, is there a software equivalent to "tap"???
Thanks
Mar
 
Back
Top