Different problems with XPE

[Guest]

Dear all

I'm creating an XPE image for a Siemens Panel PC (Simatic 677), basically it
works well, but I've some open point.

1) I've created a customize shell to lunch a my application at the
beginning. My application works with relative path (for example ..\App\), but
when it starts I obtain an error because probably it dosen't find the path;
if I try to lunch again it manually after the error, it works well. I've
tried to modify the path with absolute path and the application works well
also with the shell. The problem is that I can not use absolute path, so how
can solve the problem? is there a way to lunch the application whe the OS has
finished to load all services?

2) in the PC there is an UPDD touch screen, I find the SLD component, and I
check in the device manager that the component is well installed, but the
touch dosen't work. What could be the problem? Do I miss some component? I
try also to installa the drive directly by the Siemens PC, but the problem is
always the same (with XP professional it works well).

3) I've introduced a PCI Card Sunix 4018 to have a parallel port, but with
his SLD component, the FBA during first run is blocked without error. what
could be the problem?

Thanks a lot for any kind of help

Marco

 

[mwwade]

Problem #1
Add a regsitry keyin the list space for the project name at the top of
the Components listing in Target Designer, make sure its
HKLM\Software\Microsoft\Windows\CurrentVersion\RUN
Make it a String Value, name it anything you like,
in the Value Data give it the absolute path including the name of the
executable like; C:\Program Files\Yourfolder\yourexecutable.exe.
Why you think it won't run with an absolute path is something I don't
understand. This value will be written when FBA runs the first time and
will then execute on the first functional bootup and thereafter. It
also will NOT run until all the services are started.

Problem #2 You mention using UPDD touch screen driver, that's a driver
from 3M corporation.. You will need to add a COM port or USB
components to the system pmq or add it in the Target Designer, add all
dependencies, so that depending on the version number of the driver
file, it might or might not work with USB also. I have used variations
of this driver for approximately 15 different computers with touch
screens. Don't expect it to work right off. If you can put a mouse,
pS2, USB whatever on the CPU and use it to set the touch screen up the
first time the system is running in normal mode. Because the driver is
touchy and can cause the touch screen to go off into la-la land, until
everything is up and running I'd leave the PS2 mouse plugged in.

Another thing I would do if I were you is to compile the load WITHOUT
this driver or component for the driver and get all of your other bugs
worked out first! The biggest failure of Windows is that a bad serial
port or anything connected to the serial port can hang the system.
Although sometimes I'd like to blame Microsoft for it, IBM with the
original PC, they saved 37 cents by not adding one NAND gate tot heir
system design and created this problem that has to be replicated in
every damn serial port since then! There is no way outside of turning
the power off and then back on to reset a serial port. This problem
occurs frequently with a serial connected touch screen controller
particularly the NFI type.

I just Googled the CPU and it does have USB so I'd add the USB
components as well. Since its using the Intel 915 chipset, the USB is
most likely part of the chipset. You probably have to build XP
embedded components for the chipset if you haven't done that yet.

Problem #3-- I have no clue except that to run as a PCI card, you'll
need to add 915 chipset PCI component files that match the PCI
subsystem on the CPU board.. And you'll need to componentize the driver
for the card.

have fun.

windowsjunkie