- March 24, 2007
- 12,073
- 7,459
- Home Country
- Germany
- Moderator
- #11
This is a different issue than the one posted here. You already have a working installation, and running of MP2-Client is not possible via RDP.The MP2-Server is running flawlessly when connecting by RDP or without any gfx. Only the client did not start as it needs more GFX that RDP can deliver.
The issue here is that the installer can't install DX9 at all. The detection fails to find following files:
(https://github.com/MediaPortal/Medi...up/Bootstrapper/Fragments/DirectX9.wxs#L8-L12)
[SystemFolder]D3DX9_41.dll -> needs to be version v9.26.952.2844
[SystemFolder]D3DX9_43.dll -> needs to be version v9.29.952.3111
@treason can you please (in this order):
- check if after the manual DX installation those 2 files are present inside C:\Windows\System32 ?
- check if after the manual DX installation those 2 files are present inside C:\Windows\SysWOW64 ? (if you run x64 Windows)
- try to use this newer MP2-Installer: https://forum.team-mediaportal.com/threads/mediaportal-2-weekly-snapshot-2016-02-07.133630/
@Lehmden to skipping the DX check for server-only installs:
This is a problem, as I explained above there are 2 parts involved: the bootstrapper checks for DX. And then later(!) the .msi installer allows selection of client+server or single component installation. This means the bootstrapper doesn't know yet what the user will choose later.
To change this, there have to be done very big changes to put selection into bootstrapper process before and then to control the .msi installer with a kind of preselection. And unfortunately there is no one who is able to write a custom bootstrapper for this idea