XPe asks for XP Pro CD-ROM

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

Guest

Dear Community

I have encountered a real strange error message. While starting Windows XPe
an error message popped up saying "Files needed" (Title bar). Its content is:
"The file 'sermouse.sys' on Windows XP Professional CD-ROM is needed. Type
the path where file is located and then click OK."
I can manually edit a path or browse to one. Or I can click on OK or cancel
on corresponding buttons.

Additional info:
- This does not happening on FBA. It is a startup using a Compact Flash I
cloned.
- The file mentioned above cannot be found neither on the Compact Flash
source of the clone nor on similar clones.
- cancelling the dialog seemed to help on the next startup no message box
appeared.
What could be wrong? Customers won't like errors like that.

Kind regards and thank you in advance
Sandor
 
Sandor,

I may not be the best person to answer this, but it sounds to me like
there's a hardware component asking Windows for serial mouse support.
Two choices... manually copy sermouse.sys to the C:/Windows/System32/
drivers folder AFTER you build your image (or just add it as an extra
file and manually point it's destination to that folder). Or, try
adding the Standard Serial Mouse component under Hardware > Devices >
Mice and Other Pointing Devices and then resolve the dependencies.

It's not uncommon to get that request for files from the XP Pro CD,
believe me.

~ Jodie
 
Dear Community

I have encountered a real strange error message. While starting Windows XPe
an error message popped up saying "Files needed" (Title bar). Its content is:
"The file 'sermouse.sys' on Windows XP Professional CD-ROM is needed. Type
the path where file is located and then click OK."
I can manually edit a path or browse to one. Or I can click on OK or cancel
on corresponding buttons.

Additional info:
- This does not happening on FBA. It is a startup using a Compact Flash I
cloned.
- The file mentioned above cannot be found neither on the Compact Flash
source of the clone nor on similar clones.
- cancelling the dialog seemed to help on the next startup no message box
appeared.
What could be wrong? Customers won't like errors like that.

Kind regards and thank you in advance
Sandor
Click to expand...

Sandor,

Sermouse.sys may be getting requested because there is a serial device
(Not a mouse) connected to the serial port. I have this issue with my
GPS unit - It is sending serial data on the port, and Windows XP
"Autodetects" it as a mouse and tries to use the serail data stream to
move my mouse. I have to boot my laptop with the GPS unit unplugged,
then then attach it after Windows gets started up.

Do a search for Serenum.sys in the newsgroups - this is the serial
device enumerator - you may find out how to stop this behavior.
 
Dear "Archilea"

Thank you for your Answer.

We do not have any serial or PS/2 mouse connected to our IPC. We have a
Touchscreen connected via USB. So this is another device and corresponding
driver.

But what we do have is a hardware interface connected to a serial port. It
connects a proprietary bus to the our IPC. Because of testing my XPe I
repeatedly sent data over our bus to the IPC. Probably I generated similar
conditions as your GPS unit.

So: The file was not lost. Windows tried to load the file because windows
needed a driver to interpret the signals, that were misunderstood as mouse
signals. Right?

I have tried to find out what is the best option now. Include the Component
for serial mouse or skipping enumeration of the corresponding com port? Any
tip?

I will post results when I have them.

Thank you
Sandor
 
Sandor,

Just a guess in a dark (not enough details to make the full analysis). Did you try removing serial mouse *class installer* component
in TD? ("Mice and other pointing devices")

Also, just to eliminate other problems during the loader. Try adding /NoSerialMice switch to the default ArcPath in the boot.ini/
(or use /fastdetect:comnumber syntax instead). http://support.microsoft.com/default.aspx?scid=kb;[LN];Q131976
 
Hi MrJodie

Thank you for your post. Yours and Archilea's tip helped me a step further.
I will post results.

Kind regards
Sandor
 
Sandor, I dealt with this one. We use elo TouchSystems touchscreens
for our installations. I ended up deleting the generic HID compliant
device, so that it didn't keep popping up in Device Manager and cause
a conflict or ask for files, from my components and that helped
resolve the issue. Our touchscreens are both USB and serial (the
serial connection runs through a KVM extender) and they accomplish
this through true mouse emulation (X,Y mapping). I was lucky with
mine, however. The manufacturer provided .SLD files that I was able
to import directly into my database. I can tell you that I was
getting BSOD errors before I included the components in my original
image in TD. XPe did NOT like having the drivers installed after the
image was running.

Have a great day!
~ Jodie
 
Back
Top