Exploring the Failure of the DOS 'TYPE' Command

  • Thread starter jackson6612
  • Start date
  • Tags
    Dos Type
In summary: I would say something like 3D printing, artificial intelligence, or quantum computing.In summary, DOS "TYPE" command problem is caused by Spaces in the path and the lack of quotes around the path and file name.
  • #1
jackson6612
334
1
dos "TYPE" command problem

Hi

You can see in the video that I have text file "hello" in "C:\Documents and Settings\Administrator". But when I try to access it using the "TYPE" command it fails. Could you please explain the reason for this failure?

The "type" command displays the contents of a text file or files. Syntax: TYPE [drive:][path]filename

Video:

Thanks.
 
Last edited by a moderator:
Technology news on Phys.org
  • #2


Spaces in the path break the syntax. Try to use quotes around path and file name.
 
  • #3


Hi Borek

I think I have used the command as told in the help file. I have never seen quotes being used with DOS commands. I still don't understand what's wrong with it. Perhaps, the "TYPE" isn't used to show the contents of a text file!
 
  • #4


You were right. I have used qoutes as:
C:"\Documents and Settings\Administrator\hello.txt"

It works now. I still don't understand how the spaces break the syntax because they are natural part of the path; how else would you write "Documents and Settings"?

Thanks a lot.
 
  • #5


Command may take many arguments, they are separated by spaces. There is no way to tell if spaces separate arguments, or are part of the string. That's a problem that was not present in early DOS times, when spaces were not allowed in file names, once they were allowed it added ambiguity.
 
  • #6


Borek said:
in early DOS times, when spaces were not allowed in file names

Also file names could be no longer than either six or eight characters, plus three for the extension. So a name like "hello.txt" was OK, but not "hellothere.txt" or "my file.txt". As far as I know, most operating systems had this kind of restriction until the mid 1980s. I first used long file names with a Macintosh in 1985.
 
  • #7


jtbell said:
Also file names could be no longer than either six or eight characters, plus three for the extension. So a name like "hello.txt" was OK, but not "hellothere.txt" or "my file.txt". As far as I know, most operating systems had this kind of restriction until the mid 1980s. I first used long file names with a Macintosh in 1985.

Hi JT

I have searched it. It's called 8.3 filename, e.g. TEXTFILE.TXT. It was used by older versions of DOS. I wonder what was the reason for this limitation. Could you please help me with it? Thanks.
 
  • #8


jackson6612 said:
I have searched it. It's called 8.3 filename, e.g. TEXTFILE.TXT. It was used by older versions of DOS. I wonder what was the reason for this limitation.

When you had something like 100/200 kB on disk, using long names is a waste of space. It is also much easier to implement file system with a rigid format of file names.
 
  • #9


Borek said:
something like 100/200 kB on disk

These were floppy disks, of course. Hard disks were a luxury on personal computers in those days. My first hard disk, an external unit for a Macintosh, had a capacity of 20 megabytes (yes, MEGAbytes) and cost about $700 in 1988 (probably equivalent to at least $1500 now).
 
  • #10


Luxury gradation these days: one sided floppy, two sided floppy, two two sided floppy drives in one computer, hard disk. I have skipped one sided part (although I think I do remember one sided floppy disks being sold). We were a little bit late with computers in this part of the world, I think we catch up around 386/486.

Around 1990 I wrote in Pascal program that was able to read/write/import/export files from some version of CP/M and TOS (T=Timex, not tape), we (editorial staff of Bajtek and Top Secret magazines) used it to transfer files between Spectrum with FDD3000 and PC. Program was called Borek Utilities :smile:
 
  • #11


Thank you, Borek, JT. You both have really helped me. Borek, thanks a lot for always being there to help me. I wish you good health and happiness.

jtbell said:
These were floppy disks, of course. Hard disks were a luxury on personal computers in those days. My first hard disk, an external unit for a Macintosh, had a capacity of 20 megabytes (yes, MEGAbytes) and cost about $700 in 1988 (probably equivalent to at least $1500 now).

After reading yours and Borek's posts I believe you guys really lived in a technologically expensive times. Thank God that I was born in modern times after '88.:smile:
 
  • #12


jackson6612 said:
8.3 filename, e.g. TEXTFILE.TXT. It was used by older versions of DOS.
Still used on FAT partitions by windows. The file name entry is 8.3, and is the "short name" of the file. If actual file name is greater than 8.3, then following the 8.3 name entry, a set of fixed size (16 byte) entries (with "hidden" and "volume" attributes set) are used used to contain the "long name" as a zero terminated string.

http://en.wikipedia.org/wiki/Long_filename
 
  • #13


jackson6612 said:
After reading yours and Borek's posts I believe you guys really lived in a technologically expensive times.

Well, it wasn't that it was expensive, it's that it was right on the bleeding edge.

I'm not sure what the current equivalent bleeding edge technology would be today. It doesn't even really apply, since current advancements happen on the order of months/weeks instead of years. Even 4G or the latest iPad is just another incremental change - old news.
 

Related to Exploring the Failure of the DOS 'TYPE' Command

What is the Dos TYPE command problem?

The Dos TYPE command problem refers to an issue that occurs when using the TYPE command in the DOS operating system. This command is used to display the contents of a text file, but can sometimes cause errors or display incorrect information.

What causes the Dos TYPE command problem?

The Dos TYPE command problem can be caused by a variety of factors, including corrupted or incomplete text files, incorrect usage of the command, conflicts with other commands or programs, or issues with the DOS operating system itself.

How can I fix the Dos TYPE command problem?

There are a few different ways to fix the Dos TYPE command problem, depending on the specific issue. Some possible solutions include checking for and repairing any corrupted text files, ensuring proper usage of the command, closing any conflicting programs, or troubleshooting issues with the DOS operating system.

Can I prevent the Dos TYPE command problem from happening?

While it may not be possible to prevent the Dos TYPE command problem entirely, there are some steps you can take to reduce the likelihood of encountering it. These include regularly backing up important text files, using the TYPE command correctly and carefully, and keeping your DOS operating system up-to-date.

Are there any alternative commands to use instead of Dos TYPE?

Yes, there are some alternative commands that can be used instead of the Dos TYPE command. These include the MORE command, which displays the contents of a text file one screen at a time, and the COPY command, which can be used to create a copy of a text file without displaying its contents.

Similar threads

  • Programming and Computer Science
Replies
12
Views
9K
  • Programming and Computer Science
Replies
4
Views
5K
  • Programming and Computer Science
Replies
1
Views
3K
Replies
16
Views
2K
  • Programming and Computer Science
Replies
10
Views
4K
  • Programming and Computer Science
Replies
16
Views
1K
  • Programming and Computer Science
Replies
1
Views
1K
  • Programming and Computer Science
Replies
2
Views
1K
  • Engineering and Comp Sci Homework Help
Replies
5
Views
2K
  • Programming and Computer Science
Replies
1
Views
3K
Back
Top