Image Problems

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

Guest

I have developed a couple of basic Windows Based Terminals which seem to be
having some trouble installing correctly. I have created 2 images for 2
completely different sets of hardware (motherboards/VGA/LAN) with very
similar results.

I initially installed XP Pro on a HDD and installed all the drivers. I then
ran TAP.exe and inported this into the Component Designer and then imported
the SLD file into the Component Database. From there I created a new image
using the corresponding component in Target Designer including the
"Windows-based Terminal Professional". I have also included all the EWF
components as I am using a solid state HDD.

However, once the XPe image has booted, progressed through the FBA and
prompted for login, I get a number of error messages. I will list them below.

"Windows could not load the installer for Ports. Contact your hardware
vendor for assistance."

"The instruction at '0x5f52c7ce' referenced memory at '0x00000058'. The
memory could not be 'read'."

"Error during installation of the Task Scheduler Service; MSTask.dll
error=14001"

"Exception C:\WINDOWS\system32\iasrecst.dll, DllRegisterServer, 0xe06d7363"

Any help in getting a good working image (RDP and IE) working would be
greatly appreciated.

Thanks
 
Hi skylark,

You can try to get device pmq via TAP.exe from a clean XP Pro which is only
OS installed without any driver or get pmq from WinPE. Use pure envirnment
might be helpful.

Best Regards,
Ethan Chen
 
Hi Ethan Chen

Thanks for your response. I have loaded a fresh XP Pro SP2 install on which
I have loaded all the hardware drivers (LAN, VGA, Chipset) and then run
TAP.exe however I am still getting these the same results as I described in
my first thread.

Any other ideas?

Thanks

Jason
 
Hi Jason,

I mean you should try to load a pure XP Pro which didn't load any driver
into it and get pmq from that OS. Another fast way is use WinPE to boot
platform and get pmq. You can install drivers after FBA. The problem you
met might because the driver components in your TD database corresponding to
hardware definition (pmq) are not correct.

Ethan
 
Ethan

Thanks, I have WinPE v2.0 (Vista version), will that be OK to run TAP.exe or
do you recommend using WinPE v1.0 (XP version).

I will give it a try and post my findings back here.

Jason
 
Back
Top