XP dos-box slo, no history

  • Thread starter Thread starter baaa000
  • Start date Start date
B

baaa000

hi

being a dinasaur,
dating back to tabulating machines and vanilla DOS
i still use DOS (run CMD /e:on /f:on )
from XP

many problems.
here are just 2:

1= the command-line history works for a few commands, especially cmd
builtins
like 'type' and 'dir'
then
all history is, well, history
i have to re type every command again and again.
and pushing F7 shows nothing
worse

i type in my 'terse' text editor, and - sometime-
there is a time lag between my keyboarding and the appearance
of those keystrokes on the screen.
or a time lag to *exit* my old trusty Check-made picture
viewer.'pictview'
or DOS RAR

2- most external CMD.exe commands take about 15 seconds to *start*.
(nuf to do some cursing and yoga strtching)

even my very old/tiny/reliable/5k text editor 'terse;
that dates back to my 286 box


my current computer is a genuine intel pentium 4 with 512mB of ram.

i had a foray into linux, then came back to the devil i know, micro$.

Does my asrock mother board still have problems
(replaced it a year ago after a fight with the store and a
computerless month;
still the asrock clock does not keep good time)

or is my registry clogged
(cleaned it several times)
 
baaa000 said:
hi

being a dinasaur,
dating back to tabulating machines and vanilla DOS
i still use DOS (run CMD /e:on /f:on )
from XP

many problems.
here are just 2:

1= the command-line history works for a few commands, especially cmd
builtins
like 'type' and 'dir'
then
all history is, well, history
i have to re type every command again and again.
and pushing F7 shows nothing
worse

i type in my 'terse' text editor, and - sometime-
there is a time lag between my keyboarding and the appearance
of those keystrokes on the screen.
or a time lag to *exit* my old trusty Check-made picture
viewer.'pictview'
or DOS RAR

2- most external CMD.exe commands take about 15 seconds to *start*.
(nuf to do some cursing and yoga strtching)

even my very old/tiny/reliable/5k text editor 'terse;
that dates back to my 286 box


my current computer is a genuine intel pentium 4 with 512mB of ram.

i had a foray into linux, then came back to the devil i know,
micro$.

Does my asrock mother board still have problems
(replaced it a year ago after a fight with the store and a
computerless month;
still the asrock clock does not keep good time)

or is my registry clogged
(cleaned it several times)
Click to expand...

I experience none of the issues you are presenting on several thousand
machines.. I would guess it is likely more related to an installation issue
rather than a hardware component - but anything is plausible.
 
baaa000 said:
hi

being a dinasaur,
dating back to tabulating machines and vanilla DOS
i still use DOS (run CMD /e:on /f:on )
from XP

many problems.
here are just 2:

1= the command-line history works for a few commands, especially cmd
builtins
like 'type' and 'dir'
then
all history is, well, history
i have to re type every command again and again.
and pushing F7 shows nothing
worse

i type in my 'terse' text editor, and - sometime-
there is a time lag between my keyboarding and the appearance
of those keystrokes on the screen.
or a time lag to *exit* my old trusty Check-made picture
viewer.'pictview'
or DOS RAR

2- most external CMD.exe commands take about 15 seconds to *start*.
(nuf to do some cursing and yoga strtching)

even my very old/tiny/reliable/5k text editor 'terse;
that dates back to my 286 box


my current computer is a genuine intel pentium 4 with 512mB of ram.

i had a foray into linux, then came back to the devil i know, micro$.

Does my asrock mother board still have problems
(replaced it a year ago after a fight with the store and a
computerless month;
still the asrock clock does not keep good time)

or is my registry clogged
(cleaned it several times)
Click to expand...

You can dual boot Dos and XP you know. If DOS is that important to you
then perhaps you should run it natively.

John
 
Back
Top