On Thu, 22 Oct 2020 08:45:59 +1100 David <bouncingc...@gmail.com> wrote:
> On Thu, 22 Oct 2020 at 02:04, Celejar <cele...@gmail.com> wrote: > > > I poked around a bit, but was unable to get anything to run: > > > > 'dir' shows two files: DFT-V300.EXE and LOADDFT.EXE. The latter > > returns: "Error: Missing parameter." The former returns: > > > > PKSFX (R) FAST! Self Extract Utility Version 2.50 03-01-1999 > > Copr. 1989-1999 PKWARE Inc. All Rights Reserved. Registered Version > > PKSFX Reg. U.S. Pat. and Tm. Off. > > > > Searching EXE: A:/DFT/DFT-V300.EXE > > Inflating: CleanDsk.PID > > Inflating: CleanMBR.PID > > Inflating: DFT.EXE > > PXSFX: (E50) Disk Full, file: * > > > > A:\DFT> > > > > I switched to disk B: 'dir' shows four files: the two in A:, and > > CLEANDSK.PID and CLEANMBR.PID. Running DFT-v300 gives the same error > > (after warnings about overwriting the two *.PID files), and running > > LOADDFT also gives the same error as above. > > > > I understand that no one here can be expected to support this > > ridiculously crufty proprietary closed source software. I'm just > > wondering whether there's any FLOSS solution to emulate the actual > > environment the thing expects closely enough for it to work. > > On Thu, 22 Oct 2020 at 05:07, Dan Ritter <d...@randomstring.org> wrote: > > > But I suspect that we now know why the DFT utility can't see it: > > because DOS can't see it, because DOS doesn't have any SATA > > support. The best that can be done is providing a virtualized > > interface, and that won't let you interrogate the disk. > > Hmmm. That error message from LOADDFT.EXE and its name > makes me suspect that LOADDFT.EXE could possibly be the > driver that needs to be loaded before running DFT-V300.EXE. > > At a guess, I would try adding something like > DEVICE=LOADDFT.EXE > to your CONFIG.SYS file. [1] > > [1] https://en.wikipedia.org/wiki/CONFIG.SYS Thanks. I think I'm done with wasting time on this silly thing, but FWIW, LOADDFT does not appear in the CONFIG.SYS shipped with the DFT tool, but it is called by its AUTOEXEC.BAT in its final line: LOADDFT.EXE DFT-V300.EXE DFT.EXE /!BLOB /PSR >NUL I tried running this line from the DOS prompt, and it threw some error about the RAMDRIVE, but that's probably because I was running it from the FreeDos environment, rather than the DFT one. Celejar
