PCbanter - View Single Post

**No_Name** · January 5th 21, 02:59 PM posted to microsoft.public.windowsxp.general

On Tue, 5 Jan 2021 11:55:54 +0700, JJ wrote:

On Mon, 04 Jan 2021 17:01:55 -0500, wrote:

The stuff that runs from the command line is pretty limited
after you got to XP or 7.

That'll be more like all 64-bit Windows, where they can't natively run
16-bit programs. Windows version doesn't really matter.

Some but not all batch commands are supported. Same with DOSBOX.

In terms of internal commands, the missing ones are only a few and they're
not quite important, IMO (e.g. TRUENAME). However, the trick that can make
the FOR command to iterate each character in the given string, is no longer
possible.

DosBox's command line features on the other hand, is more limited even if
compares with MS-DOS (v6.x).

Any ANSI.SYS tricks are not going to work at all.

ANSI escape codes is natively supported by DosBox's built in command
shell/prompt. Though, I don't know how well it covers the whole ANSI escape
code specifications.

Also, there's no way to disable the ANSI unless DosBox is used to boot a DOS
image which doesn't load ANSI.SYS. Running other command shell such as
FreeDOS' COMMAND.COM (i.e. FreeCOM) from within DosBox's built in command
shell won't disable ANSI either.

DOSBOX doesn't seem to support all of the PROMPT tricks I used in DOS
6.3. (redefining keyboard keys etc)
It does seem to support the direct access in dBase that Windows has
choked on since XP. I can also run pretty much all of my 16 bit stuff.
If I really want to walk down memory lane I do have a 1g FAT16
partition on one of my drives that will boot into real DOS. That looks
like the machine on my desk when I retired in 1996 with W/3.1
available if I want to look at my old Prodigy notes ;-)