🚀 go-pugleaf

In <15941@bfmny0.BFM.COM> tneff@bfmny0.BFM.COM (Tom Neff) writes:

>Unfortunately I find that VP/ix can be a bit flakey when invoked from a
>shell script.  Also it messes with the screen, other devices etc. and
>can be slow to load.  In comparison, the UNXUDI loader is very fast and
>clean.  It still creates a V86 task but is much less ambitious about
>trying to create an elaborate PC simulation within the box.  All it sets
>up is what a well behaved UDI application needs to run.

You're still right. Once we started on a VAX using a Cross-Compiler, we
bought the INTEL-Dos-Package for our field technicians to use on a LAPTOP.
The INTEL-package was much faster on the laptop than the one on our vax.
So we decided to switch to a faster multi-user-system and bought SCO-UNIX
(I use Interactive, ever installed NEWS on SCO-UNIX ??). INTEL, Munich,
told us that a package for 8086 assembler is not available for UNIX, only
one for the 386. So my boss decided not to buy this package, instead we
now use VP/IX. We didn't invoke VPIX from a UNIX-Shell-Script, we use a
DOS-Batch-Job. VPIX is automatically invoked when a DOS-Command is to be
executed in the command line (try: dir). We load the INTEL-Hex-File with
a parallel interface ( cp anc39.abs /dev/lp0) directly in our CNC and
then we use our hardware debuggers.
The only problem we had with VPIX is when we try to copy a large Hex-File
with DOS-Command copy to a disk. The file is sometimes corrupted (50:50)
so we use doscp.

Regards
Joachim