VOGONS


First post, by fxm

User metadata
Rank Newbie
Rank
Newbie

A "dir" in an empty directory shows no files, as it should.

A "dir NUL" in the same directory, however, shows the pseudo-file NUL [which DOS "pretends" exists in every directory] as an actual zero-byte file.

I must admit that it has been almost 20 years since I worked intensively with actual DOS, but I don't recall that it displayed NUL like a real file.

Reply 1 of 2, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Where is the problem?

Reply 2 of 2, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

It's the same for all/most DOS devices that DOSBox emulates (CON, PRN, etc.)

In both real DOS and DOSBox the DIR command internally uses the FindFirst function, which does find devices, but DIR in DOS nonetheless reports "File not found" for a filespec of a device name. This difference seems unlikely to cause problems, but it's trivial to implement.