CMD window screen draws (writes)

[Vic]

I am relatively new to XP (from Win98). There are a number of DOS apps
used here which are irreplaceable, and PAINFULLY slow running in a CMD
window. The biggest thing is S-L-O-W screen draws. Someone explained the
'coders' for XP did something writing it 'for security reasons' which
makes screen draws very slow compared to Win9x and DOS.

my questions:

1. is there ANY way to achieve FAST screen draws in a CMD window?

I use TAME and DOSBOX (for a VERY difficult to run DOS app). Screen
draws are still sooo s-l-o-w.

2. is there a better place to get an answer to the above question (e.g.
another newsgroup)?

Thanks
Vic

 

[cornedbeef007-groups]

I am relatively new to XP (from Win98). There are a number of DOS apps
used here which are irreplaceable, and PAINFULLY slow running in a CMD
window. The biggest thing is S-L-O-W screen draws. Someone explained the
'coders' for XP did something writing it 'for security reasons' which
makes screen draws very slow compared to Win9x and DOS.

my questions:

1. is there ANY way to achieve FAST screen draws in a CMD window?

I use TAME and DOSBOX (for a VERY difficult to run DOS app). Screen
draws are still sooo s-l-o-w.

2. is there a better place to get an answer to the above question (e.g.
another newsgroup)?

Thanks
Vic

You could use Microsoft Virtual PC 2004 (free download)http://
www.microsoft.com/downloads/details.aspx?FamilyId=6D58729D-DFA8-40BF-AFAF-20BCB7F01CD1&displaylang=en
and install MS-Dos (or Win98) in a virtual machine, and run your
application there.

Good Luck.
BarryG

 

[Vic]

Barry, you suggest Virtual PC. Have you tried that software and
specifically used DOS apps and seen FAST screen writes?

Reason I ask is because if CMD window screen writes are slow in all NT
OS's (I have W2K4, XP Pro and XP Home) why would DOS app screen draws be
fast in virtual PC in an NT OS?

___

 

[Shenan Stanley]

Barry, you suggest Virtual PC. Have you tried that software and
specifically used DOS apps and seen FAST screen writes?

Reason I ask is because if CMD window screen writes are slow in all
NT OS's (I have W2K4, XP Pro and XP Home) why would DOS app screen
draws be fast in virtual PC in an NT OS?

When you are using Windows XP Command Prompts - you are not running DOS.
When you utilize a Virtualized PC with DOS installed - you are running DOS.

 

[Vic]

Shenan, I've read on the VPC newsgroup programs running in VPC run
slower than they normally would (e.g. W2K in XP Pro) however is there
MUCH difference, do you know? In other words, if VPC *IS* the way to go
to run these old DOS apps instead of trying to hang on to Win98, I'll
take the time to install VPC and try it. Otherwise ... well, need more
be said?

Thanks for your answer BTW!
___

 

[Shenan Stanley]

Shenan, I've read on the VPC newsgroup programs running in VPC run
slower than they normally would (e.g. W2K in XP Pro) however is
there MUCH difference, do you know? In other words, if VPC *IS* the
way to go to run these old DOS apps instead of trying to hang on to
Win98, I'll take the time to install VPC and try it. Otherwise ...
well, need more be said?

Thanks for your answer BTW!

As I see it - you have nothing to lose.
Try it.

Your only other choice is Dual Booting with DOS/Windows 98.

VirtualPC 2007 - Free...
http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx

VMWarePlayer - Free...
http://www.vmware.com/download/home.html

If you have a working DOS/Windows 98 machine where everything works the way
you want, you could even use the VMware Converter to make that machine into
a VMWare machine.

The main reason things might run slower in some Virtual PCs vs an actual PC
is lack of resources. You are trying to use an OS (Windows 98/DOS) that
doesn't need much resources. I suspect that it would run fantastically
and - depending on the machine you installed it on and how you configured
your virtual machine - better than it would on the machine it was originally
intended for almost a decade ago.

 

[Bob I]

Try ALT+Enter to mak it full screen and see what response you get.