Xibo 1.4.2 client mscorlib error

Hi Matt

We've never directly supported XP embedded so I'm not sure. It's probably the feed reader or something like that, but it's a missing method in the core .net framework.

Perhaps you can shoehorn a newer .net framework on the machine?

Alex

Hi Alex,

Thanks for the reply. I had a feeling that you may say what you have done. I struggled to get .NET installed on there as it stands at the moment.

I'm working on a live USB image with persistence of 10.04.4 so that I can use the python client. This is working on one of our RM PCs and I've left it running overnight to see how it goes. I may get a SSD if the memory stick works successfully

The PC running embedded XP is in the back of one of the Samsung TVs and was sold with the magic info software installed.

Matt

I am running into this same problem on a machine running Windows XP that had a previous Xibo client that did work. After upgrading to the latest Xibo I was forced to update the client software to ver 1.4.2. Once the update was complete xibo no longer worked with the same event error causing it to crash

EventType clr20r3 (5000)
P1 xiboclient.exe
P2 2.0.0.0
P3 5123e285
P4 mscorelib
P5 2.0.0.0
P6 471ebc5b
P7 1295
P8 14
P9 system.missingmethodexception
P10 NIL

I had this problem on an XP box. I turns out that XiboClient uses a .NET Framework method that is only available in .NET 2.0 Service Pack 2. The machine had only 2.0 Service Pack 1. Once Windows Update did its stuff XiboClient then worked.

* Details:
The exception was:
    0:011> !pe
    Exception object: 014971d4
    Exception type: System.MissingMethodException
    Message: Method not found: 'Boolean System.Threading.WaitHandle.WaitOne(Int32)'.

According to MSDN that specific method was added in .NET 2.0 Service Pack 2. (http://msdn.microsoft.com/en-us/library/cc189907(v=vs.90).aspx)

At the same time I was investigating this Windows Update offered "Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update for .NET versions 2.0 through 3.5 (KB951847) x86". After its installation XiboClient worked. Afterwards I see new versions of .NET installed (2sp2, 3sp2, etc).

That's correct. We always say keep up to date with the dotnet framework
updates, and that because the updates are not available on XP embedded (to
which the original question refers), the client is not and never has been
supported on that platform.

Best wishes

Alex

Yup. My comment may help someone in the same situation know just to update .NET (where possible), rather than having to crank out the debugging-tools/SDK as we did. :-)

Yes, but my point is that we don't say requires 3.5sp1 in the installation
guide for fun. This shouldn't be an issue because the software you
installed to resolve this is a prerequisite.

Best wishes

Alex

Hi i have the same problem on XP embedded (windows 7 version).
On my PC i have framework 4.0.

Can somebody help me to solve it.

Many thanks

No "embedded" versions of Windows have ever been supported. It will not
work. You need a full version of Windows

Hi Alex, thaks for your answer, the problem is that the client is a embedded lcd Monitor and is non possible to replace the os.
Anyway if you can address me to what i have to check i can add the missing component.

I am not able to replace OS, but i can add component on the os image.

In my application, becaus enobody check teh device, i need a embedded solution to be sure that nothing happens whe i turn on or off the device.

Thanks

Michele

It's part of the dot net framework which isn't available for embedded os

That's why we don't support embedded versions of Windows since Microsoft
don't make this available