Tips & Tricks - Revision history

Benzac: /* Launcher MSX */

2025-06-19T12:41:02Z

Launcher MSX

2024-10-17T07:42:43Z

Web Version Loader

2024-06-10T10:03:51Z

The application cannot be started because a UI component could not be loaded:

2024-06-10T10:03:13Z

The application cannot be started because a UI component could not be loaded: {DETAILS}

2024-06-10T10:02:55Z

The application cannot be started because a UI component could not be loaded: {COMPONENT}: {ERROR}

2024-06-10T10:02:31Z

The application cannot be started because a UI component could not be loaded: {COMPONENT}: Server responded with status: 0

2024-06-10T10:02:05Z

Common Errors

2024-06-07T07:45:16Z

Node Browser MSX

2024-06-07T07:45:04Z

Node Browser MSX

2024-06-07T07:42:18Z

Node Browser MSX

@@ Line 412: / Line 412: @@
 </syntaxhighlight>
-For more information about the '''Launcher MSX''' service, please visit: https://msx.benzac.de/info/?tab=Showcases&section=Showcase11.
+For more information about the '''Launcher MSX''' service, please visit: https://msx.benzac.de/info/?tab=Showcases&section=Showcase12.
 === Screenshot ===

@@ Line 28: / Line 28: @@
 If you have an older version of Media Station X, you can use the web version loader service to load the latest version from the web. Additionally, this service allows you to load the entire Media Station X application in a secure context (i.e. via <code>https://</code>) to be able to use services like '''Twitch MSX'''.
 Enter the start parameter '''<code>web.msx.benzac.de</code>''' to set it up.
-Alternatively, enter the start parameter '''<code>id:web</code>''', which sets up an auto loader edition of the web version loader (i.e. by setting a [[Start Action]]).
+Alternatively, enter the start parameter '''<code>id:web</code>''', which will set up a new version of the web version loader that allows automatic loading (i.e. by setting a [[Start Action]]).
 For more information about the '''Twitch MSX''' service, please visit: https://msx.benzac.de/info/?tab=Showcases&section=Showcase7.

@@ Line 425: / Line 425: @@
 * If you are getting this error on TV but not on mobile devices, the HTTPS certificate can probably not be verified (some older TV devices cannot verify newer HTTPS certificates).
-=== The application cannot be started because a UI component could not be loaded: ===
+=== The application cannot be started because a UI component could not be loaded ===
 There are currently a lot of requests on the server and the trend is increasing. Unfortunately, the current server does not have enough power to answer all requests. Therefore, errors can occur more frequently. If you are getting this error, please wait a few minutes and try it again.

@@ Line 425: / Line 425: @@
 * If you are getting this error on TV but not on mobile devices, the HTTPS certificate can probably not be verified (some older TV devices cannot verify newer HTTPS certificates).
-=== The application cannot be started because a UI component could not be loaded: {DETAILS} ===
+=== The application cannot be started because a UI component could not be loaded: ===
 There are currently a lot of requests on the server and the trend is increasing. Unfortunately, the current server does not have enough power to answer all requests. Therefore, errors can occur more frequently. If you are getting this error, please wait a few minutes and try it again.

@@ Line 425: / Line 425: @@
 * If you are getting this error on TV but not on mobile devices, the HTTPS certificate can probably not be verified (some older TV devices cannot verify newer HTTPS certificates).
-=== The application cannot be started because a UI component could not be loaded: {COMPONENT}: {ERROR} ===
+=== The application cannot be started because a UI component could not be loaded: {DETAILS} ===
 There are currently a lot of requests on the server and the trend is increasing. Unfortunately, the current server does not have enough power to answer all requests. Therefore, errors can occur more frequently. If you are getting this error, please wait a few minutes and try it again.

@@ Line 424: / Line 424: @@
 * If you are getting this error on mobile but not on TV devices, the CORS headers are probably missing or incorrect (some older TV devices ignore CORS headers and allow any content).
 * If you are getting this error on TV but not on mobile devices, the HTTPS certificate can probably not be verified (some older TV devices cannot verify newer HTTPS certificates).
 == Well Known Issues ==

@@ Line 113: / Line 113: @@
 It is also possible to integrate the Node Browser MSX service directly in your menu or content by using the following action syntax.
-* <code>content:request:interaction:access:{SERVER}@http://nb.msx.benzac.de/interaction</code>.
+* <code>content:request:interaction:access:{SERVER}@http://nb.msx.benzac.de/interaction</code>
 The <code>{SERVER}</code> part must be replaced with the server IP + port or hostname (e.g. <code>192.168.0.10:8080</code>).

@@ Line 111: / Line 111: @@
 '''Note: Please note that the CORS HTTP headers must also be present for the loaded index file.'''
-It is also possible to integrate the Node Browser MSX service directly in your menu or content by using the action syntax <code>content:request:interaction:access:{SERVER}@http://nb.msx.benzac.de/interaction</code>. The <code>{SERVER}</code> part must be replaced with the server IP + port or hostname (e.g. <code>192.168.0.10:8080</code>).
+It is also possible to integrate the Node Browser MSX service directly in your menu or content by using the following action syntax.
 For more information about the '''Node Browser MSX''' service, please visit: https://msx.benzac.de/info/?tab=Showcases&section=Showcase5.