Strange string in command.com

[Jack2000]

wow !:eek::eek::eek:
illhostit.com - Command.com.jpg




this is :
\edit.com command.com

just take a look ....

[Refalm]

On Windows 98, open an HTML file, type this:


And open the HTML file

[Kintaro]

Get a hexeditor you fucking n00b.

[Jack2000]

You dont need a hex editor to see just that


/dev/con

yeah and then they say they do not steal

[Kintaro]

Its a binary file, you should use a hexeditor.

[Aloone_Jonez]

I can't see anything strange here, this sort of thing is very common in MS-DOS.

[Jack2000]

Cmon this is obviusly the section where the startup files are listed
why whould it have /dev/con string!
the other two are with :\ and \ indicating that it should load them
from the def driver where command.com is located
even the slashes on it are the other direction !!!!!
can't you see the connection it is just some trash part left
from an Unix based sys !!!

[WMD]

MS-DOS has always had Unix-like device commands.  You never see them, but they're there and always have been.

/dev/con
/dev/nul
/dev/clock$
/dev/lpt1
/dev/prn
/dev/com1

Those I can remember off-hand.  It's no mystery that DOS is a poorly-conceived, single user Unix clone.

[noob]

the lying bastards.

[hm_murdock]

Actually, it's a crudely constructed CP/M clone that was made for Apple IIs and old 8080 machines. Quick and Dirty Operating System. I think it was done by a guy at a software firm to see if he could. MS bought this hack and sold it as MS-DOS.

I've heard stories that the original author built it in one afternoon while dropping acid. I wonder about the validity of the one afternoon bit, but some amount of LSD would be required to make DOS.

[Kintaro]

Dos was never based on Unix, in fact, its so different to Unix that the notion of it is Insane.

The /dev/ bit is probably what tells the system that it is a device, but opening a file with the typical API called "Con", "Aux", etc is basically opening a device. Dos has no /dev/ directory on the filename, no such thing as device nodes, just a crude API for input/serial/printer devices.

It is NOT unix. Also, CP/M had the same thing.

[Aloone_Jonez]

I know that but they did borrow some UNIX concepts like redirection and pipes which is possibly where the devices /CON /NUL came from.

[Jenda]

Actually, it's a crudely constructed CP/M clone that was made for Apple IIs and old 8080 machines. Quick and Dirty Operating System. I think it was done by a guy at a software firm to see if he could. MS bought this hack and sold it as MS-DOS.

They just removed the "quick" part.

[Kintaro]

I know that but they did borrow some UNIX concepts like redirection and pipes which is possibly where the devices /CON /NUL came from.

I don't think pipes were in CP/M, just QDOS and MSDOS. However I am not sure, I know they were in MP/M. In fact when you read on MP/M you wonder why the hell it didn't blow MSDOS out of the water.

[anphanax]

Hey, you've got XP or 2K laying around, check this out (this stuff doesn't exist in WinDOS 9x):


con\prn\nul\aux\com#\lpt# are just the tip of a much bigger iceberg .

For instance, although stupid, you can make your floppy drive light up by typing this in cmd.exe:
"more < \\.\GLOBALROOT\DEVICE\Floppy0"

If I recall correctly, those are all in some sort of kernel namespace (\..\?), and a lot of that junk isn't accessible in user-mode windows (in other words, I think some stuff, like the contents of the "Drivers" path, is only accessible in kernel-mode). Also, I believe there's a specialized undocumented API for working with kernel objects on NT. "NtQueryObject" from NTDLL.DLL comes to mind, for one.