It does work after a fashion - though I would not recommend actually trying to use these fonts - but it is a bit fiddly. I finally got the following to use the fonts at 300DPI:
\documentclass{article}
\usepackage{hvmath}
\begin{document}
Text $\Pr(A/B) \frac{x^{-2}}{\sum_{i=1}^{n} y - 23\pi}$.
\end{document}
Here's a listing of my working directory:
L209/ dpi300/ hvbc10mv.vf hvbo10mv.tfm hvbo10ts.vf hvmath.txt hvmaths.out hvrb108r.tfm hvrb10t1.vf hvrm10ot.tfm hvro10ex.tfm hvro10ts.tfm hvsc10t1.vf omxhvex.fd t1hvr.fd
PLAIN/ dpi329/ hvbc10ot.tfm hvbo10mv.vf hvbsy10.tfm hvmaths.aux hvmaths.ps hvrb10ex.tfm hvrb10ts.tfm hvrm10ot.vf hvro10mv.tfm hvro10ts.vf hvsy10.tfm ot1hvr.fd ts1hvr.fd
dpi150/ dpi360/ hvbc10ot.vf hvbo10ot.tfm hvex10.tfm hvmaths.dtx hvmaths.sty hvrb10mv.tfm hvrb10ts.vf hvrm10t1.tfm hvro10mv.vf hvsc10mv.tfm missfont.log prawf-hvmath.aux
dpi180/ dpi432/ hvbc10t1.tfm hvbo10ot.vf hvexb10.tfm hvmaths.dvi hvmaths.txt hvrb10mv.vf hvrm108r.tfm hvrm10t1.vf hvro10ot.tfm hvsc10mv.vf omlhvm.fd prawf-hvmath.dvi
dpi210/ dpi518/ hvbc10t1.vf hvbo10t1.tfm hvfonts.cfg hvmaths.hd hvmathts.txt hvrb10ot.tfm hvrm10ex.tfm hvrm10ts.tfm hvro10ot.vf hvsc10ot.tfm omlhvr.fd prawf-hvmath.log
dpi240/ dpi622/ hvbo108r.tfm hvbo10t1.vf hvfonts.map hvmaths.ins hvmi10.tfm hvrb10ot.vf hvrm10mv.tfm hvrm10ts.vf hvro10t1.tfm hvsc10ot.vf omshvr.fd prawf-hvmath.ps
dpi270/ hvbc10mv.tfm hvbo10ex.tfm hvbo10ts.tfm hvmath.sty hvmaths.log hvmib10.tfm hvrb10t1.tfm hvrm10mv.vf hvro108r.tfm hvro10t1.vf hvsc10t1.tfm omshvsy.fd prawf-hvmath.tex
This is basically the result of:
- Unpacking both archives and unpacking the archives inside the archive. I don't think the Schmidt archive actually helps much, so you could probably just unpack the fonts.
- Rename each directory of the form
<nnn>DPI to dpi<nnn> where <n> is a digit. I am not sure whether this step is necessary.
- Moving selected files from the resulting sub-directories into the working directory. Basically, if a directory is shown above, its contents are in-place. If the directory is missing, its contents are in the working directory. So I moved the contents of
L2E, METRICS, VF, CFG etc. into the working directory.
Compilation sequence (Linux, BSD, OS X etc.):
latex <filename>.tex
TEXINPUTS=.:dpi300:: dvips <filename>.dvi
Compilation sequence (Windows) - ?? can somebody confirm or correct this?:
latex <filename>.tex
set TEXINPUTS=.;dpi300;; dvips <filename>.dvi
Then open the resulting <filename>.ps in your DVI viewer. (I used Okular.)

As far as I can tell, there are no .mf sources, so you can only use the resolutions provided. For some reason, the resolutions provided are non-standard. For example, we have 622 but not 600. By default, Okular wants 1200 for DVI, which is why I converted to PS first.
Conversion to PS generates a bunch of checksum warnings, but dvips does use the contents of the dpi300 directory.
Obviously,
- You could install into a local
texmf tree to avoid the need to specify TEXINPUTS etc.
- The result is poor quality for electronic documents, but that is just the nature of bitmap fonts. The printed result is probably OK-ish if you like Helvetica.
.dtxcompiles OK for me. I can view the resulting.dvifine. it doesn't seem to actually use the fonts, but it isn't corrupt..dvifile with me? All the files in my folder, including the.tex,.logand.dvifiles are here: drive.google.com/drive/folders/….dtxwill compile anyway just using computer modern. and it is not much help in configuring anything. also, it is not possible to share a dvi here. but I imagine you can probably compile it on overleaf, if you just upload the.dtxand the.sty. I did it without the fonts.