Adding the Windows Installer (MSI Installer) to XPe builds

[Ed Senechal]

Hi,

I work in tech support for a software developer. One of our customers
has some older Compaq Evo T30 terminals with XPe. In order to install
our product, the MSI installer needs to be present, but it hasn't been
included in the XPe build for these devices. The redistributable
Windows Installer found on the MS website doesn't allow itself to be
installed on the XPe box because it checks the OS version and thinks
that it is an XP box ("Wrong OS version"). I guess they figured that,
since it ships automatically with XP, it wouldn't ever need to be
installed from scratch there...

Does anyone know if there is a full version 2.0 of the MSI installer
which runs on XP/XPe and how to get it?

I appreciate any help here!

Thanks,

Ed

 

[KM]

Ed,

You can try fixing the Wrong OS Version problem by adding CSDVersion reg.value.

Read more details from this thread: http://groups.google.com/groups?hl=en&lr=&c2coff=1&[email protected]

Also, it may appear that you are gith and there is no easy way to install MSI on XP/XPe.
Then you are left with the option to find out all MSI components (files/registry/dependencies) and deploy them to your run time
manually. The best way to analyze the MSI would be to explore the Windows Installer Service component of the XPe database.

Let us know if it helps.

KM

PS. Contact me (kosntmor @ no_spam_hotmail . com) or BSquare Corp. (www.bsquare.com) for more complicated solutions. We worked with
Evo T20/T30 thins clients.

 

[Ed Senechal]

I'll try this.

BTW, what does "gith" mean? "Gone In The Head"? (probably true... ;-) )

Thanks,

Ed

 

[KM]

Ouch... my fingers sometimes ain't friends with keyboard.
That was "right"

 

[Ed Senechal]

Hi KM,

It still doesn't work. The complete install for the Installer Service
component is only available for up to Win2K and will not run on XP.
The OS reports itself as XP, even though some functionality has been
removed in the embedded version, and I can't find a full version of
the Installer Service which will install on XP.

I could (possibly) hack the registry to make it think that it's
installing on W2K, but I doubt that this would be effective in the
long run.

Thanks for trying!

Ed

 

[Guest]

Hi all ed im traying to build a windows xp embedded image for a t20 96/128
you know how to build this image, this machine com why nte and only need to
upgrade the remote conection to version of support 16 bit colors any one know
hot to upgrade the rdp or the only wy to get the lastest version of rdp is to
build the windows xp embedded image for this machine and any one know how to
flash this

Thanks

 

[KM]

Jorge,

BSquare has worked a lot with Evo T20/T30 clients so you may contact the company. Also HP should be able to help you with the client
as well.

Theoretically you can "upgrade" RDP client on the device but that may be harder than updating the entire image.

 

[Guest]

Thanks KM but what is BSquare and where contact this company and tomorrow im
trai to contact the hp sopport center

Thanks

 

[KM]

Jorge,

My appology. I forgot to put more info in my previous reply.
About BSquare (SI) you can read more here: www.bsquare.com.
If you are interested, contact me offline at "konstmor At hotmail Dot com" and I will send you some good contact info there.

Regards,
KM

 

[Guest]

Thanks im add to my msn messenger tomorrow im tray to contacto you
Thanks for all

 

[KM]

Jorge,

Please use email if possible.

Thanks,
KM

Thanks im add to my msn messenger tomorrow im tray to contacto you
Thanks for all

 

[Guest]

Ok KM thanks but im find the solution of my problem im using the new version
of rdp client from microsoft and this is now working i have the 16 bits color
option but THANKS FOR ALL of your help

 

[KM]

Jorge,

I am really glad you managed to install the client manually.

Btw, I am not sure sure what client version was included in your terminal images but you might want to try playwing with default
value under [HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp] registry key. Set it to between 1 and 4 and
see if it makes any difference.

KM

PS. Personaly I always prefer having SLX project for any image I am playing with. This is why I suggested you to contact BSquare.
Also, IIRC, they added some useful device manageability options to the Evo 20 image.

 

[Guest]

im Use the version remote desktop client for old operating system put on the
microsoft.com web site and is working fine i not need to upgrade any more on
this machines im only need this for 16 bit colors all aplication is on a
server and not on the thin, and im very happy why this solution and thanks
for all of your help

Jorge,

I am really glad you managed to install the client manually.

Btw, I am not sure sure what client version was included in your terminal images but you might want to try playwing with default
value under [HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp] registry key. Set it to between 1 and 4 and
see if it makes any difference.

KM

PS. Personaly I always prefer having SLX project for any image I am playing with. This is why I suggested you to contact BSquare.
Also, IIRC, they added some useful device manageability options to the Evo 20 image.

Ok KM thanks but im find the solution of my problem im using the new version
of rdp client from microsoft and this is now working i have the 16 bits color
option but THANKS FOR ALL of your help