annoying printer problem--it prints when XPe starts

  • Thread starter Thread starter danis
  • Start date Start date
D

danis

Hello !
I have a strange problem with my XPE image. I have a ticket
printer conected to my device, where my image is installed. When
Windows starts, the printer starts to print strange caracters, with no
sense ( something like ??-u??) and sometimes when windows restarts
also. The printer is conected to com1, and in device manager, the
settings are how they are supossed to be.
What can it be?? I tryied to build several xpe images,
diferent, with diferent ports configuration, but the same thing
happends.
Please help, because I can't take it anymore :p.
 
danis said:
Hello !
I have a strange problem with my XPE image. I have a ticket
printer conected to my device, where my image is installed. When
Windows starts, the printer starts to print strange caracters, with no
sense ( something like ??-u??) and sometimes when windows restarts
also. The printer is conected to com1, and in device manager, the
settings are how they are supossed to be.
What can it be?? I tryied to build several xpe images,
diferent, with diferent ports configuration, but the same thing
happends.
Please help, because I can't take it anymore :p.
Click to expand...

I've seen a similar problem on various versions of Windows during
startup. It seems that Windows is looking for a serial mouse or other
device. On XP /XPe, if you have /FASTDETECT on the operating system
line in your boot.ini it seems to prevent this from happening. For
example:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Embedded" /fastdetect /bootlogo /noguiboot /NoExecute=OptIn

I've also seen where PnP device enumeration has to be disabled for a
port to completely eliminate undesired COM port activity. To do this,
you can add "SkipEnumerations"=dword:ffffffff to the
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\PNP0501\1\Device
Parameters] registry key. This key is for COM1, so if you need to do
something similar for other ports, change the \1\ appropriately.

Regards,

Dave
 
The problem was a serial driver from MicroTouch touch screen, that was
sending information to com1 port, when windows booted up, to test if
there is a monitor plugged in. I've disabled that and now all is
fine.
In my future images I won't even install it.
Thank for the reply!
 
Back
Top