06-26-2002
older versions of DOS were made deliberately incompatible with newer versions, also PC-DOS (IBM's rival proprietary DOS) made it all the more incompatible!
why not get either DR-DOS, FreeDOS, OpenDOS or all three? they are all designed to be totally MS-DOS compatible, they are all free, i think at least one of them is open source, and since they are newer versions of DOS, you may find that they are compatible with more things than any MS-DOS is, also i think it would be fun to get an old version of windows running on top of one of these non-micro$oft DOS systems!
10 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hi, In my MSDOS version on windows'98, many keys are not working. I feel that my version is old and I wnt to update it. Can anyone tell me how can i do so.
Please tell me soon.
Thanks a lot.
-Kinnaree
:confused: (1 Reply)
Discussion started by: kinnaree
1 Replies
2. UNIX for Dummies Questions & Answers
I know nothing of unix and didn't know where to start. I've heard of a DOS to Unix translator, and since I know DOS pretty well, I thought that this program would be perfect. Any help you could give me would be appreciated.
Bryan (1 Reply)
Discussion started by: bferguson
1 Replies
3. Windows & DOS: Issues & Discussions
I had just recently experienced, a bad experience... Apperently, a worm got into my computer a created itself in my MS-DOS. No serious damage was done, but I did a little study on it, through my computer. The virus got thought my scan, by coding itself as an HTML file. Don't know why it did that,... (2 Replies)
Discussion started by: hdk_mkr
2 Replies
4. UNIX for Dummies Questions & Answers
I have navigated every DOS and UNIX FAQ to find the DOS equivalent of the UNIX ps command (ps -f would be even better) but all listings of DOS<>UNIX commands do not have it (they all have the same basic commands listed). DOS must have a way of detecting running processes and TSRs. mem /c is the... (7 Replies)
Discussion started by: dancingfool
7 Replies
5. Windows & DOS: Issues & Discussions
Please where can i get the origanal MS-DOS, I need it.
Not mandatory but botting from a floppy is best. (9 Replies)
Discussion started by: Irish Jimmy
9 Replies
6. Shell Programming and Scripting
Hi
I have a dos batch file in window server where I call a cmd command for creating some db.
this cmd commad is located in e:\data\abcd\xyz.cmd.
Now I call this batch file from unix ssh.sh but my access point is D in window server here I want to change the dos prompt to e:\data\abcd.
in... (3 Replies)
Discussion started by: Jamil Qadir
3 Replies
7. Linux
Hello ;
I have a problem running some script on dos .
when i run :
C: ls /temp
ls: cannot access /temp: No such file or directory
but when i run
C: ls \temp
windriver backup remotebackup
also when i run
C: ls temp
windriver backup remotebackup
The... (4 Replies)
Discussion started by: mulder20
4 Replies
8. Linux
Dear all, I am trying to write a unix shell with C++ that is similar to Windows command line. I planned to call it Dosh (DOS-sHell).That means you can directly run dos or win32 console programs with it. It will be distributed according to the license g GPL. Any advice? (This is my first c++ program... (3 Replies)
Discussion started by: elgarteo95
3 Replies
9. Cybersecurity
About 3 days ago our Apache logs started filling with the following errors:
mod_ssl: SSL handshake failed (server <weberver>:443, client 41.235.234.172) (OpenSSL library error follows)
OpenSSL: error:1408A0B7:SSL routines:SSL3_GET_CLIENT_HELLO:no ciphers specified
These initially were... (1 Reply)
Discussion started by: ccj4467
1 Replies
10. Windows & DOS: Issues & Discussions
Hello
Where is there a good source to receive an understanding of MS DOS.
I have tried google books " MS DOS ", no luck.
i did try " command prompt " , no luck.
the subject " seems " to be dry. no water flowing in that creek.
what would be good search terms.
I would like to aim towards the... (6 Replies)
Discussion started by: cowLips
6 Replies
INPUT(1) General Commands Manual INPUT(1)
NAME
input - Yagi-Uda project antenna defining program
SYNOPSIS
input [ - h ]
DESCRIPTION
The program input is one of a number of executable programs that forms part of a set of programs, collectively known as the Yagi-Uda
project , which were designed for analysis and optimisation of Yagi-Uda antennas. input is an interactive program, that asks the user for
information about a Yagi design, such as position of elements, spacing between elements, frequency span of interest and a filename to save
the data to. input then writes this information into an ASCII file, which can be read by yagi or optimise The file is ASCII and it's for-
mat is easily understood by inspection (there are comments printed in it), so it can if necessary be edited manually.
After running input and specifying a filename (for example 144e10) you should then type yagi 144e10 and then output 144e10 and optionally
optimise 144e10
OPTIONS
-h Print a help message.
FILES
filename ASCII data file in which design is put.
PLATFORMS
Both DOS and Unix versions have been built. The DOS version as distributed requires a 386 PC with a 387 maths coprocessor.
AUTHORS
Dr. David Kirkby G8WRB (david.kirkby@onetel.net). with help with in converting to DOS/PC from Dr. Joe Mack NA3T (mack@fcrfv2.ncifcrf.gov)
SEE ALSO
first(1), yagi(), output(1), optimise(1), input (5), first(5), yagi(5), output(5) and optimise(5).
Bugs should be reported to
david.kirkby@onetel.net.
Bugs tend actually to be fixed if they can be isolated, so it is in your interest to report them in such a way that they can be easily
reproduced.
If a mistake is made during inputting of data (such as entering an incorrect length), it is not possible to go back and correct this. You
should make a note of the error, and edit the ASCII text file with a text editor (vi, DOS edit etc).
Version 1.16 24th October 2000 INPUT(1)