Hi,
Thanks for your post. I experimented a bit more and got the following results under Debian with Wine:
- Rather than renaming Renderer.pm, one can also edit it to replace the reference to IERenderer\IERenderer.dll with a reference to bearhtml.dll. However, this step isn't really needed at all (for me, at least), in fact.
- Once you rename IERenderer.fff (the only thing which I really had to do), there's no need to rename IERenderer\IERenderer.dll any longer.
I'd like to add that I also had issues with running the setup program with simple 'wine w32-471.exe'. Wine complained about certain API calls being just stubs and finished without doing anything useful. Unfortunately, the installer isn't a ZIP archive any longer (unlike all previous versions up to 4.70!), so there was no option of simply upgrading my existing copy manually by overwriting the respective files from the archive. Anyway, I managed to fix it by starting 'wineconsole cmd' and running the setup from there - interestingly, that worked (FWIW, I started the wine console with root privileges, however the same was the case with 'wine w32-471.exe' mentioned above).
Tomas
<p>Hi,</p><p>Thanks for your post. I experimented a bit more and got the following results under Debian with Wine:</p><ol><li>Rather than renaming Renderer.pm, one can also edit it to replace the reference to IERenderer\IERenderer.dll with a reference to bearhtml.dll. However, this step isn't really needed at all (for me, at least), in fact.</li><li>Once you rename IERenderer.fff (the only thing which I really had to do), there's no need to rename IERenderer\IERenderer.dll any longer.</li></ol><p>I'd like to add that I also had issues with running the setup program with simple 'wine w32-471.exe'. Wine complained about certain API calls being just stubs and finished without doing anything useful. Unfortunately, the installer isn't a ZIP archive any longer (unlike all previous versions up to 4.70!), so there was no option of simply upgrading my existing copy manually by overwriting the respective files from the archive. Anyway, I managed to fix it by starting 'wineconsole cmd' and running the setup from there - interestingly, that worked (FWIW, I started the wine console with root privileges, however the same was the case with 'wine w32-471.exe' mentioned above).</p><p>Tomas</p><p>
</p>