Freeware command interpreter

[Dos-Man]

This is a 40K MS-DOS command interpreter that I wrote using C++. I have
been working on it for several years, off and on.
It's not finished yet, but it is already pretty neat. An interesting
program to have if you are a command line junkie.

http://www.bee.net/prime-time/cmd.zip

The README file is in OpenOffice format.

dos-man

 

[fred]

This is a 40K MS-DOS command interpreter that I wrote using C++. I have
been working on it for several years, off and on.
It's not finished yet, but it is already pretty neat. An interesting
program to have if you are a command line junkie.

http://www.bee.net/prime-time/cmd.zip

The README file is in OpenOffice format.

A txt option might be an idea for those who do not use open office

 

[Terry Orchard]

A txt option might be an idea for those who do not use open office

Or html, since OpenOffice can produce that effortlessly.

Actually, Dos-man, I'd be interested in a short description of what
this command interpreter does that can't already be done on the normal
dos window command line. It sure wasn't clear in a quick skim of the
doc.

Terry

 

[Dos-Man]

Actually, Dos-man, I'd be interested in a short description of what
this command interpreter does that can't already be done on the normal
dos window command line. It sure wasn't clear in a quick skim of the
doc.

Terry

Well, I will try to list some things that it can do
that the DOS command interpreter can't do, but I don't
have the program or the docs in hand since I am at a library.

* It has a history command that shows the last 10
commands run. Maybe new versions of DOS have this,
but I have never encountered one that did.

* The exist command can check for the existance of folders.
if exist folder c:\batch write 'it exists'

* Takes up less memory because it's 60K smaller (I think)

* Some of the statements such as DEL accept multiple arguments

del file1 file2 file3

You can print out returned errorlevels without needing to
create a DOS batch file to find out what the errorlevel was.

run a program and then type in
write 'The errorlevel returned was ~\*errorlevel~'

These are some interesting things that cmd.com can do. Like I
said, it's not finished. It is probably only half way finished
(shudder).
A few of the commands need to be made to handle wildcard characters,
batch file abilities need to be added, etc.

I don't know that it will ever be finished, but it's an interesting
program, and a lot of work has gone into it. It wasn't meant to be
radically different
from the DOS interpreter - just an alternative.

dos-man

 

[Dos-Man]

That's fair. If you find it fun, go for it. If you want others to
play with it as well, some "hype" about the advantages or differences
is useful, I think. And change the doc file to something people can
read without installing OO. Thanks for the info.

Terry

Certainly my C programming skills have improved due to this program
and my library of useful functions is larger than ever so this program
has and will continue to benefit future C programs I write.

The doc is what it is. I'm not creating .txt file. No formatting makes
for a big mess.

I'm not using Wordpad to create .rtf or .doc file.
Wordpad sucks. Html is way too much work.

I need a good RTF editor but I want it to do nothing but RTF.
I like specialized tools that do one thing only and do it well.

I like RTF but both openoffice and wordpad are poor rtf tools.
Those are all that I have. I went with the better one.

Dos-Man

 

[REMbranded]

(e-mail address removed) (Dos-Man) wrote:

I need a good RTF editor but I want it to do nothing but RTF.
I like specialized tools that do one thing only and do it well.

How well can RTF be done?

I don't recall any stand alones for RTF, but Crypt Edit is what I use.

 

[Dos-Man]

He's already using Open Office, and it can write rtf (and html), just
by picking the format in the save-as dialog. So if he wants to produce
docs in a format that most people can read, he can.

Terry

Ha, OO is a joke for writing RTF files. How about they lose the
dialog box that says:

"Saving your file in an external format may cause data loss. Do you
want to save the document in OpenOffice text format?"

every time you try to save something?


Don't even get me started in on Wordpad. I just love it when it saves
something as text and then puts in /ra /q /b bunch of /i control /w codes/d
/i /b into your /c /d document.

Or better yet, trying to load any text
document above 5 megs, and it pauses for 4 seconds every time you press a
key.

Yeah, great freaking tools. You won't have these problems with my own
text editor, textbox:

http://www.bee.net/prime-time/textbox.zip

Some day, when it is finished, I am going to make an RTF version of it.

dos-man

 

[John Fitzsimons]

Command interpreter :

Female.

Code :

No = no.
Yes = yes.

After going through the command interpreter the code is changed to ;

No = no
Yes = yes, unless I change my mind afterwards.

If dynamic linking with the command interpreter ceases permanently
then the output changes to ;

No = no.
All previous "yes's" are now considered to have been "no's".

 

[M.L.]

He's already using Open Office, and it can write rtf (and html), just
by picking the format in the save-as dialog. So if he wants to produce
docs in a format that most people can read, he can.

OpenOffice 1.1rc also gives him the choice of saving his files in the
PDF format. CutePDF will save *any* printable file in the PDF format.

 

[REMbranded]

(e-mail address removed) (Dos-Man) wrote:

Some day, when it is finished, I am going to make an RTF version of it.

I gave it a spin hoping that it might work on large (30 meg) text
files from another thread. I get an "Unexpected Error" when I try to
open it in Win 98SE.

Also, are you using any dynamic memory? I'm wondering if this is the
problem most editors have in opening and manipulating large files.

 

[John Fitzsimons]

Freeware command interpreter : Cat.

Command : Sit.

Output : Sorry, I don't "accept" commands. I give them.

Now....

.........................sit !

 

[Dos-Man]

I gave it a spin hoping that it might work on large (30 meg) text
files from another thread. I get an "Unexpected Error" when I try to
open it in Win 98SE.

Also, are you using any dynamic memory? I'm wondering if this is the
problem most editors have in opening and manipulating large files.

The error you reported has now been researched and the cause is known.
The problem will be fixed - probably not in the next build, but in the build
following that one.

In the meantime, you should be able to edit your 30 meg text file by
first running textbox, and then dragging and dropping the text file
onto textbox's text area. Provided you have enough memory, of course.

dos-man