Good evening:
Thanks very much to Eric Auer and Michael Devore for all of the
suggestions! The support has been OUTSTANDING!
OK, I have learned a bit more. Apparently, NTFS4DOS is
slightly smarter than the documentation would have me believe.
I did some experiments with MS-DOS 6.22 and let the
Hi Michael:
Ok, this fails with BOTH UMBPCI and EMM386 in my Emachines T1600
and on an HP Pavillion P4. It works with UMBPCI and not EMM386
on a Dell D600.
I guess I need to try DOS=HIGH without UMB, but I'm beginning to
think NTFS4DOS is busted. Next step I suppose is to try MSDOS
6.22, like t
At 04:14 PM 7/13/2005 -0400, Mark Bailey wrote:
Will try DOS=HIGH only. Thanks! Too bad UMBPCI doesn't
work on all the computers. :-(
Well, if DOS=HIGH doesn't do it, I may have to d/l NTFS4DOS myself, force
64K UMB, and see if I get the same fragmentation. Something bizarre going
on with
Hi Michael:
OK, I believe the application does use VGA graphics. :-(
Will try DOS=HIGH only. Thanks! Too bad UMBPCI doesn't
work on all the computers. :-(
Mark
Michael Devore wrote:
At 08:23 AM 7/13/2005 -0400, Mark Bailey wrote:
OK. Development Kernel, Development command.com, Developm
At 08:23 AM 7/13/2005 -0400, Mark Bailey wrote:
OK. Development Kernel, Development command.com, Development SYS,
new emm386/himem, NTFS4DOS 1.4. The INSTALLHIGH failed.
Interestingly, a "LOADHIGH" failed with ALMOST the same error
and a little more information:
DOS/32A fatal (1001): DOS re
Hi Michael:
OK. Development Kernel, Development command.com, Development SYS,
new emm386/himem, NTFS4DOS 1.4. The INSTALLHIGH failed.
Interestingly, a "LOADHIGH" failed with ALMOST the same error
and a little more information:
DOS/32A fatal (1001): DOS reported insufficient memory, additiona
