Greetings,

We currently have a released image used by customers that we plan on adding
some new features to. These new features require .NET 3.0. For the .NET
3.0 install to work, I need to have the Microsoft-Windows-HTTP component on
the image. Unfortunately this component does not exist on the image. Is
there a way to manually install this component on an already existing image?

The currently released image is an XP SP2 image with .NET 2.0 already on it.

Thanks in advance,
Robert

I'm having a problem with my program not running on the target and I'm pretty
sure it's because it's missing a system DLL. But when I try to load it under
'depends.exe' on the target, nothing happens. I have the depends.exe and
it's DLL. Any idea what other things it needs to run that I might not have
on the target? Thanks!

If I set the 'Apply Windows key combinations' Keyboard property in a RDP to
'On the remote computer' on an XPe unit, the shortcuts are executed on the
local unit instead of the remote server.

Setting this property on XP Pro works correctly.

Is there another setting I need to change on XPe for this work correctly?

Hi guys,

I am looking at the XPe platform, but am a little confused as to what needs
to be downloaded and installed, and in what order.

So far, I have got:

- XP Embedded + SP2 Eval
- .NET 2.0 for XPe
- XP Embedded Feature Pack 2007
- Update Rollup 1.0 (Released 20 May 07)

Is this correct, and in the right order? Are there any other updates I
should get?

Finally, if I then decide that XPe is for me, do I need to uninstall
everything before getting the "full" version, or is there an upgrade path?

Many thanks,

Martin Hughes

I installed the embedded tools including msde on my local computer.
Everything worked fine.
When getting a new computer I want to move the database to a sql server
so others can use it too.
I managed to get the database work on a sql2000 server after moving the
tyo database files. But I cannot connect via td or the Component
database manager.
My idea was that the msde workes with an empty password for sa. Thia
isn't a good idea and our sql2000 server of course has a set password. I
belief that the embedded tools need to be told that they should use a
password but I cannot find any information of how to get my password
into that tools.

- Who has done a move the same way as I did?
- Where can I find any information about how to set up a working
environment when moving to a sql2000 server?
- What kinds of authentification do the tools use (windows / db
authentification)
- What are the usernames and passwords that the tools use when
connecting to a db and where can I change them?