Configuring XPe to look like full XPPro

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Does anyone know how to configure XPe to resemble a full XPPro installation?

I have an application which runs fine on XP-Pro, but the manufacturer
refuses to give any support to getting it working with XPe. Unfortunately, it
uses the latest-and-greatest - .NET, IIS and as many external components as
humanly possible.

I've got a 400mb XPe image which is 99% there, but the application still
isn't quite operating correctly - throws the occasional system exception -
probably yet another missing component.

Included the usual Application Compatibility macros, to no avail.

Any ideas?

Mat
 
Mat,

First idea that I get is XPProEmulation image. The much tested SP1 version of the project you will find on www.xpefiles.com.
There is also SP2 upgrade to it but I have not tested it personally.
 
KM,

Many thanks for the assistance - I am trying your file now.

One thing I have noticed is that .NET framework, even on this full XP
installation, still doesn't work with SP2 (see my previous post). Running the
..NET configuration still throws an error.

Can you, or anyone, confirm this problem before I blame it on a bug?

cheers,

Mat.
 
Mat,

I cannot confirm whether it is a bug or not. I haven't tried .Net 1.1 component on SP2.

Btw, you may want to know that there is another .Net component on SP2 not in database though. It is in XPe SP2 installation kit,
under VALUEADD\MSFT folder. Basically, this is .Net 1.1 SP1 (SP1 of the .Net 1.1) bits.

KM
 
KM,

I've been manually running the .NET install after reseal.

However, your XPPro image has made my application finally work - thank you!
All I need to do now is reduce this image to fit on a 500mb card!

ta,

mat.
 
Matt,

Although it is good that you got it running on XPProEmulation, that promises you to be able to have it working on your own image. It
will be just a matter of satisfying all dependencies.

However, what is the purpose for you to run the .Net install manually? Many of us have done that manually on our images but that was
way before Microsoft released the .Net component(s).
 
KM,

I've been running .net install manually, firstly because the SP2 component
doesn't work, and secondly because I need to run another install manually
also. Alas I've not managed to get the National Instruments IEE488 drivers
into a component (they cluster-bomb both the registry and file system).

I've encountered another strange thing with your XPPro config: it includes
"Windows Socket2 Namespace" and "Windows Sockets 2.0 Service Provider".
Although they are in the database, they do not appear on the tree at any
visibility.

Ta,

Mat
 
Matt,

The "Windows Sockets 2.0 Service Provider" has a visibility level set to 50 so you won't be able to (easy) see the component within
TD.
I don't see "Windows Socket2 Namespace" component at all but I see "Windows Socket2 NameSpace Library". Its visibility=200 so you
should be able to see it if you lower your Min.Visibility level in TD.
 
Back
Top