PRB: Cannot install the QFE Desktop installer tool [XPe SP2]

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

Guest

Hi,

I reinstalled my XPe-IDE (PC set it's EOL) by doing following:

Installed SP1 Tools, DB-Engine, Database from the package we recieved
Updated the tools with SP2
Updates the DB-Engine with SP2
Updated Database with SP2

Now, when trying to install the QFE-Desktop-Installer-Tool (Q84706) I will
be reminded that I have to install Q842930 at first. So far, so good.
But when trying to install Q842930 I'll get following error:

"Faild copying file 328310_sysmain.sdb to the QFE-repository directory.
Repository directory {.....} does not exist."

Q328310 was a QFE published on 25.02.2003 - long time before SP2 was coming.
Does that mean that I have to install all the QFE's that were raised before
SP2 was released even if SP2-Database-Update is installed?
 
No. You do not have to install all QFE's again. It sounds like you didn't
get a full install of SP2...

from where did you obtain the SP2 Update? If you had XPE SP1 running first,
then tried to reinstall all to get to SP2, did you uninstall SP1 XPE first?
this could be an issue...

HTH,
JC
 
XPEApplicator,

I haven't tried Desktop Installer on SP2 but keep in mind these facts:
- You can extract (use /x switch on QFE's exe or just WinZip) the SLD from QFE's exe and just import it using CDM manually
- The Desktop Installer component is nothing more that just a set of dependencies - components that are required to be in your
image in order to be able to launch Desktop QFEs at the XPe run time. So you can always go ahead and just include those components
manually and don't mess up with the Desktop Installer.
 
You need to look in your component database for the old
version of the QFE Installer and remove it before trying
to install the new one. Below is straight from the MS
site.

It is recommended that OEM Customers who downloaded the
Installer Tool between May 14-20, uninstall the Installer
Tool and replace it with the current version

Robert
 
Hello JC,

I recieved the Update from the Microsoft Embedded OEM-Site (XPEEFI.EXE did
the downloads for me). I installed it by choosing the options "Tools update"
and "Database update" provided in the setup.exe that was created as DISK 3
after the download.

I installed the Windows Embedded Studio SP1 on a new computer (the old one
seems to have many failures) from the CD's we buyed, then I performed the
updates that came with the download.
 
Hello KM,

does "I haven't tried Desktop Installer on SP2" mean that I can install
QFE's on targets that were build with SP2-Database and -tools - without
adding the "QFE Desktop Installer Component" in the image?

best regards
XPEApplicator@BE
 
Hello Robert,

no, I didn't installed the old version. I've seen this information when I've
downloaded the current version.

But have much thanks.

Best regards
XPEApplicator@BE
 
XPEApplicator,
does "I haven't tried Desktop Installer on SP2" mean that I can install
Click to expand...

No, that meant what it said - I never tried adding the Desktop Installer component in to my SP2 images :-)
QFE's on targets that were build with SP2-Database and -tools - without
adding the "QFE Desktop Installer Component" in the image?
Click to expand...


Yes, you can install *some* Desktop QFEs on a target that was built with SP2 ToolKit even if you did not include the "QFE Desktop
Installer Component" in the image. But you will have to check first if all the component's dependencies were presented in that image
configuration at the time you built it.

Pointing to *some* QFEs I mean the fact that not all Desktop QFEs could be lauched at run time even with the "QFE Desktop Installer
Component" in the place. For the "broken" QFE information please see the QFE Installer documentation and search through this NG
archive (some of the broken QFEs have been reported here).

--
Regards,
KM, BSquare Corp.

 
The "Desktop QFE Support" component doesn't actually contain any updated
binaries, it is simply a macro component that brings in the necessary
dependencies that will allow newer desktop QFE's to run on the system.
Rather that fussing with installation order, etc. I would recommend creating
your "own" version of the component. Just create a macro that depends on
these components:

Win32 API - Advanced
Common Control Libraries Version 6
Primitive: Crypt32
Primitive: Mpr
Primitive: Ntdll
Primitive: Ole32
Primitive: Oleaut32
Primitive: Psapi
Primitive: Setupapi
Primitive: Shell32
Primitive: Userenv
Primitive: Version
Primitive: Winspool
Windows API - GDI
Win32 API - Kernel
Windows API - User
Microsoft Visual C++ Run Time
RPC Local Support
Client / Server Runtime (Console)

HTH,
Tony
 
in looking at the documentation from the start menu, check and see if it
states in the header that this is Pre-Release version, and subject to
change. I noticed that when I downloaded the SP, but when I installed the
full version from a CD toolkit from MS, this was not there. that lead me to
believe that there may have not been some things there. Just
brainstorming... I had a simialr isse with DQI, but when I used the CD from
MS, the issue went away...

only bummer, is the toolkit is another purchase :-(
JC
 
Back
Top