I have an issue with executable files generated by HTMLexe that are being used on the new Windows 10.
I generate my files as an Internet Explorer executeable, therefore I believe the issue might be related to the fact that Windows 10 does not actually include Internet Explorer anymore. The executeable files run without any issues on computers with older versions of Windows (that still include IE), but on computers with Windows 10, no audio is played.
Is there an update planned to ensure compability or is there a workaround present at current? Or maybe there is something I don’t know to ensure files are running on Windows 10?
This will be a growing issue for my customers, as I expect them slowly to move forward to the new Windows.
unfortunately, that did not change anything for Windows 10!
Any other suggestions? And if it’s a change in the code, is there a more efficient way to replacing the faulty lines instead of going through them one by one?
It was set to Microsoft Groove, which seems to be their new app to play music. I switched to Media Player to test it (it did not offer any alternatives) and it still didn’t work.
Yes, this sample proves that audio in Windows 10 seems to work on your computer too. So the problem lies somewhere else. In our sample, we use the same way to open and play the media file than
I did not get an error message the last time I tried to add target="_heopenit" and it didn’t work.
The dummy file you asked me to create however did indeed work. Unfortunately, it opened up a seperate instance of Media Player, which is not the way to go for our customers, but the dummy itself got played with that.
I hope that helps you. What would be the next step?
Actually, that is just what I did last time you asked me to create a dummy-mp3 file. I copied one of my articulation mp3s, renamed it to dummy.mp3 and put it into the root folder of my publication.
When I clicked it, the file was played in a seperate instance of media player (which was opened by clicking the file in the executeable).
Most of my audios are NOT in the root folder, as the executable is structured in different chapters. The .mp3s are in the respective folders of those chapters (the same folder where the respective html-page is). The only audio-file that is in the root is the dummy-file currently and the starting index page of the executable. The rest is in folders.
Here is an example of the code in one of the chapters:
The respective audio is in the same folder as the page, therefore the link should be working and has always worked in the past. It still works on every computer that does not have Windows 10.
The _heopenit target parameter requires the full virtual path for the MP3 file to be played.
So this explains why the dummy MP3 files play as expected, and not the normal MP3 in your publication.
I suppose that something changed in Windows 10 Trident engine so that links without the _heopenit tag stop working.
We’ll study this problem and see what can be made.