XPe on Kontron MOPSlcdGX1 board

[Cato Svellingen]

Hi,

anyone used XPe on Kontron board MOPSlcdGX1

Cheers

Cato

 

[KM]

Cato,

I've seen some posts here regarding the board. I am not working on the board, though.
What kind of problems are you having with it?
I thought Kontron (or Anacom) supplied SLD for thier boards? (at least they have done that for some boards) Not online I guess, but
per request.

 

[Guest]

Kontron does have XPe support online. If you go to

http://www.kontron.com/support/sptechlib.cfm

then search under "software utilities", then look for the file "xpspi112.zip" (at the bottom). Inside you will find components for ethernet support, video drivers, etc. I found it to be immensely helpful when I used it last year.

Enjoy!

Jesse

 

[Cato Svellingen]

Hi,
I have seen the Kontron site, and I am using the .SLD supplied together with
"Windows based Terminal Professional".

When booting nothing happens, so first thing I assume is that the Video
driver is missing, since the component for MOPSlcdGX1 does not seem to
contain video driver.
So I tried with Standard VGA 640x480 and Digital flat panel

I am using JILI interface to a TFT lcd display.

Still nothing ...

Anyone know ?

THANKS .

Cato

Kontron does have XPe support online. If you go to

http://www.kontron.com/support/sptechlib.cfm

then search under "software utilities", then look for the file

"xpspi112.zip" (at the bottom). Inside you will find components for
ethernet support, video drivers, etc. I found it to be immensely helpful
when I used it last year.

 

[KM]

Cato,

When booting nothing happens,

Do you see anything at all? BIOS errors, ntldr menu screen, XPe boot logo
screen?
Set timeout value > 0 in the boot.ini to see the ntldr menu screen. If you
don't see it, your likely have problem with disk partitions but not XPE
image yet. Mark your target disk system partition active.

 

[Cato Svellingen]

Hi,
nothing happens, even with timeout 20.
Just the cursor in the top left corner.

Cant see ntldr menu screen.

Should I see ntldr menu even if some drivers are wrong/ missing etc. ?

The system is marked active as well.

Cato

 

[Slobodan Brcin \(eMVP\)]

Hi Cato,

Make at least two entries same or different no matted in boot.ini, and of
course set timeout value.

You must see multi OS screen even if you don't have any file on your disk
beside ntldr. and boot.in

If not then something is wrong like:

1. Your disk geometry is wrong. (use dos fdisk, format, diskprep on your
target device)
2. From fdisk mark partition as active. (until you solve problem never use
Disk Manager or diskpart, or Windows format)
3. Place ntldr. and boot.ini
4. Run device. (You should see multi os choice screen)

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[KM]

Cato,

I have practically nothing to add to Slobodan's reply.
Basically, you will have to first make your target device (target HDD) bootable and then go back to the Korton's SLD.

 

[Cato Svellingen]

Hi,
made the disk bootable, and FBA starts now.

But I get Blut screen after a while with "System License violation"

I guess thats because I put in a mock Run time Licensing number ?

Thanks !

Cato

Cato,

I have practically nothing to add to Slobodan's reply.
Basically, you will have to first make your target device (target HDD)

bootable and then go back to the Korton's SLD.

 

[Slobodan Brcin \(eMVP\)]

Hi Cato,

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&q="System+Lice
nse+violation%22&btnG=Search&meta=group%3Dmicrosoft.public.windowsxp.embedde
d.*

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[KM]

Cato,

Unless you have a working PIS number that you got from your XPe distributor, do not put anything in the ID field in TD. This will
produce an evaluation image but will likely fix the BSOD.