Can't install on 32-bit non-SSE2 (i.e. Pentium III or earlier) PC and can't disable 'ubiquity' slide slow during install attempt

Trisquel leverages the 'ubiquity' installer from Ubuntu to provide hard drive installation. That installer in turn leverages WebKitGtk to provide an entertaining graphical slideslow during the installation process. Unfortunately, in recent years WebKitGtk has begun utilizing the SSE2 instruction set even on the 32-bit builds despite prior reassurances they never would. Consequently, the Trisquel installer now crashes on these machines due to the failed launch of the slideshow! (Midori, the web browser based on WebKitGtk, also crashes for the same reason)

There is an internal option available in Ubiquity to disable the slideshow, however this must not have been tested in a long time, because the installer crashes mid-way through the installation process on all hardware when this option is enabled. Furthermore, there does not appear to be a command-line only installer or installation mode for Ubiquity that could be used instead?

There also isn't enough RAM disk space on the /cow live root to perform an APT upgrade installation of WebKitGtk or Ubiquity, so the only way to apply a patch of fix package is by sideloading a .deb package in the ALT-F2 terminal. The only way I was able to work around these multiple obstacles was to download (on a separate computer) the Debian source package for WebKitGtk, modify the build script compiler flags to only enable SSE (i.e. SSE1) instructions, and buildta replacement .deb package to install into the live session. This procedure not only fixes the Ubiquity installer slideshow crash, but also the Midori browser!

Trisquel really needs to fix this issue with the Ubiquity installer in one of the following ways discussed above:
1) Provide a non-SSE2 binary build of the WebKitGtk package in its repository (which I could provide with a little help),
2) Fix the crash of Ubiquity when the slideshow is set to 'hidden', along with providing a command-line argument or UI dialog to disable it,
or 3) Provide an alternative command-line installer or installation mode.