Office 2000 on XPE

[Huw Ford]

I have got my XPE image running now thanks to Brad Combs.

I want it to be as close as possible to XP Pro in appearance but with EWF to
protect the hard drive.
The system is set up as dual boot so XPE boots from drive D:
So far all is looking good, but with EWF disabled I tried to install Office
2000 and got the following message;

Error 1991. Could not register type library for file
D:\WINDOWS\System32\VEN2232.OLB

I assume that there is some component missing from my XPE build, but how can
I track down what it is?

Thanks,
Huw Ford

[Brad Combs]

Huw,

Glad that audio component worked for you! I uploaded it to www.xpefiles.com
yesterday. As far as the component that you need to install software from
windows installers is, well, the "Windows Installer Service" component. It
will bring in a few dependencies though. Here's the only other glitch. (MS
Please respond). I think that you aren't able/allowed to install Office on
an XPe device. I'm not positive about that, but I think something along
those lines was discussed about a year ago and the answer was no. Hopefully
someone from MS can help us out here. So add the Windows Installer Service,
and hold your breath. HTH,

Brad Combs
Imago Technologies

"Huw Ford" <H...@NoSpamHuwFord.co.uk> wrote in message
news:eQCFa.3$__...@newsfep1-gui.server.ntli.net...

[Doug Gordon]

The license agreement (CLA) prohibits using an XPE system for general
"document creation", which effectively cuts out installing something like
Office. I think they want to prevent companies from making sort of an
"office automation terminal" with a reduced license cost over regular XP. I
know our IT department was looking at something like that until someone
actually read the license agreement text.

Doug G

"Brad Combs" <br...@imagotechnologies.com> wrote in message
news:eaLOWFCM...@tk2msftngp13.phx.gbl...

[Ravi [MS]]

XPE is licensed for LOB apps only -- so you can't run
Office locally on an XPE client. To achieve this, use
XPE as an RDP client to access Office on W2K/W2K3 Server.

Thanks,
Ravi, MS
Embedded Devices Group
Disclaimer: This posting is provided *AS IS* with no
warranties, and confers no rights.

>.
>

[Huw Ford]

Hi Ravi,

I have the evaluation copy of XPE and I can't find anything in it's EULA
about not running Office on an XPE system.
Please don't use obscure acronyms. I have no idea what a "LOB app" is, and
what is a "RDP client"???

What I am trying to create is a "Training Pc" for educational and training
organisations. The idea was to use XPE with EWF RAM to protect the hard
drives & configuration. The student/trainee can mess about with the config
etc.. Then at the end of the day the trainer/teacher just switches off all
the machines in the room without having to go round and shut each one down.
Next morning when they are switched back on they are back to the default
known state.
A typical sort of application that would be taught on these would be Office.

I did read in the evaluation EULA about "general purpose device" and
followed the link to the MS embedded web site but I couldn't find any more
about it there?

The systems I am trying to put together would not be usable for general day
to day use as any documents created would be deleted every time the machine
was switched off. But I'm not a lawyer so I don't know how you define a
"general purpose device".

I hope there is a way I can do this as it would really mess up my plans for
my new business if the licence agreement prevents me creating this product.

Thanks,
Huw Ford
Microprice Computers

[Graham Broadbridge]

What you probably need to do is use standard XP pro with a very locked down
and restricted policy
that prevents changes.

Embedded systems are usually used for more restricted appliances such as
Slot machines or bank ATM terminals, etc.

"Huw Ford" <H...@NoSpamHuwFord.co.uk> wrote in message

news:jAXFa.382$0H5....@newsfep1-win.server.ntli.net...

[Jon Fincher (MS)]

"Huw Ford" <H...@NoSpamHuwFord.co.uk> wrote in

news:jAXFa.382$0H5....@newsfep1-win.server.ntli.net:

> Hi Ravi,
>
> I have the evaluation copy of XPE and I can't find anything in it's EULA
> about not running Office on an XPE system.
> Please don't use obscure acronyms. I have no idea what a "LOB app" is,
> and what is a "RDP client"???

LOB - Line of Business. Basically a fancy term for the application your
device will run.

RDP - Remote Desktop Protocol. Refers to using Terminal Server to login
to a different machine.

> I did read in the evaluation EULA about "general purpose device" and
> followed the link to the MS embedded web site but I couldn't find any
> more about it there?

A general purpose device refers to something like your desktop machine or
a laptop. It has no specific purpose, but can be used for anything -
media playing, document creation, internet access, etc. Compare that to a
set-top box, which may be use the same hardware as a PC, but only performs
a specific function, namely serving media to a TV device.

> The systems I am trying to put together would not be usable for general
> day to day use as any documents created would be deleted every time the
> machine was switched off. But I'm not a lawyer so I don't know how you
> define a "general purpose device".

Even if you're wiping them clean everyday, they're general purpose
machines at that point. The computer lab at my college did the same thing
with the machines in their lab to cut down no virus infection - every
evening, they'd reimage the machines in the lab.

As for licensing, Graham is right - you'd need to use XP Pro with special
licensing and restrictive policies.

--
--Jon, MS

This posting is provided "AS IS" with no warranties, and confers no
rights.

[jt]

>.
>
IANAL, but as far as i know the XP embedded license allows
the use of a office component if it is a integral part of your
own application.

1. fix the registry (alternative: install mdac.inf)

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\DAO]
"Path"="C:\\Program Files\\Common Files\\Microsoft Shared\\DAO"

2. run batch:

md "C:\Program Files\Common Files\Microsoft Shared\DAO"

expand -r MSINFO32.IN_ c:\windows\inf

expand -r ODBCJI32.DL_ C:\Windows\System32
expand -r ODFOX32.DL_ C:\Windows\System32

expand -r odbcjt32.dl_ c:\windows\system32
expand -r odtext32.dl_ c:\windows\system32
expand -r oddbse32.dl_ c:\windows\system32
expand -r odexl32.dl_ c:\windows\system32
expand -r odpdx32.dl_ c:\windows\system32
expand -r vfpodbc.dl_ c:\windows\system32

expand -r DAO360.DL_ "C:\Program Files\Common
Files\Microsoft Shared\DAO"
expand -r MSEXCH40.DL_ C:\Windows\System32
expand -r MSEXCL40.DL_ C:\Windows\System32
expand -r MSJET40.DL_ C:\Windows\System32
expand -r MSJINT40.DL_ C:\Windows\System32
expand -r MSJTER40.DL_ C:\Windows\System32
expand -r MSJTES40.DL_ C:\Windows\System32
expand -r MSJTOR40.DL_ C:\Windows\System32
expand -r MSLTUS40.DL_ C:\Windows\System32
expand -r MSPBDE40.DL_ C:\Windows\System32
expand -r MSRCLR40.DL_ C:\Windows\System32
expand -r MSRD2X40.DL_ C:\Windows\System32
expand -r MSRD3X40.DL_ C:\Windows\System32
expand -r MSRECR40.DL_ C:\Windows\System32
expand -r MSREPL40.DL_ C:\Windows\System32
expand -r MSRPJT40.DL_ C:\Windows\System32
expand -r MSTEXT40.DL_ C:\Windows\System32
expand -r MSVCRT.DL_ C:\Windows\System32
expand -r MSVCRT40.DL_ C:\Windows\System32
expand -r MSWDAT10.DL_ C:\Windows\System32
expand -r MSWSTR10.DL_ C:\Windows\System32
expand -r MSXBDE40.DL_ C:\Windows\System32
expand -r VBAJET32.DL_ C:\Windows\System32

cd \windows\sytem32

regsvr32.exe MSEXCH40.DLL
regsvr32.exe MSEXCL40.DLL
regsvr32.exe MSJET40.DLL
regsvr32.exe MSJTES40.DLL
regsvr32.exe MSJTOR40.DLL
regsvr32.exe MSLTUS40.DLL
regsvr32.exe MSPBDE40.DLL
regsvr32.exe MSRCLR40.DLL
regsvr32.exe MSRD2X40.DLL
regsvr32.exe MSRD3X40.DLL
regsvr32.exe MSRPJT40.DLL
regsvr32.exe MSTEXT40.DLL
regsvr32.exe MSXBDE40.DLL

regsvr32.exe "C:\Program Files\Common Files\Microsoft
Shared\DAO\DAO360.DLL"