After seeing the LZ's post and everyone's replies, I have some thoughts to share and just join in the fun.
No matter what kind of labor it is, no matter how big or small the role, as long as one has done something, they should be respected. Liu Shaoqi said to Shi Chuanxiang, "You who clean toilets and I who am the president of the country are all doing things in the same way." Shouldn't everyone learn from this?
DOS888 did not respect others' labor, and even belittled or nearly slandered it. This is no longer a technical issue. This should also be the main reason for the public anger and dissatisfaction.
Resources are very limited, and forum websites have investments. Everyone should cherish them. If overly emotional and unhelpful remarks about discussing issues waste resources, DOS888 may be mainly responsible? But if the forum needs such emotional conflicts to increase the visit rate, that's another matter. However, tdj's "knockdown" still has a bit of literary flavor, which is another story.
Let's talk about the serious matter below.
The LZ said that if you are really an expert, you should develop China's OS, and proposing to make our own OS is originally a good thing, and I think it is also the dream of all Chinese people. However, here, I don't want to talk about whether it can be realized first. What I want to say is, can we use our own subjective standards to measure others' hard work? Everyone also has different ways and pursuits. This forum provides a platform for everyone to communicate and learn. Moreover, the new DOS era also provides a large number of systematic learning articles and free software tool downloads, which have solved many problems. I have learned a lot here.
As for developing an OS for Chinese people, I think someone must be thinking about it, at least hiding this dream in their heart. But Rome wasn't built in a day. Why did the brilliant Liu Bang, who knew that going to the Hongmen Banquet was like walking a tightrope, still risk his head? Because he understood that he was an egg and others were a boulder! Can a newly born eagle compete with a hen for food?
Wasn't Windows also once attached to the fence of the former DOS, humbly acting as an interface for the master and being at the master's beck and call, and then later became the daughter-in-law who finally got her due?
Is DOS still useful? What is its future?
I think if it is understood from the three aspects of narrow sense, virtual sense, and broad sense, there may be unexpected gains.
1. Narrow-sense DOS
Of course, the narrow-sense DOS I mentioned refers to the DOS operating system itself. It has been mainly eliminated now, but due to technical (kernel) reasons, Windows still can't get rid of it. For example, when Windows crashes and can't enter the system, it has to turn to the old ancestor DOS. Although Microsoft often boasts that "the new generation of Windows XP will rarely have problems with not being able to enter the system", and has canceled the ERD (Emergency Repair Disk) of 2000 and the function of repairing system files during installation, and also canceled the function of repairing the registry. In the DOS of 98, you can use SCANREG /RESTORE to repair the registry, but even in the fault recovery console of XP, there are no commands to restore the registry. Microsoft thinks there is a backup in the system, and when the system changes and is in danger, it extracts the backup to restore, but it still often has failures and can't enter the system. Although 2000 XP also has a digital signature verification tool (SIGVERIF, signature verification) to verify whether system files are legal, and still retains the system file checker (SFC, system file checker) of 98 to restore system files from the installation CD. But once I ran it when the system was normal, it suddenly had a blue screen warning "a hardware error occurred" and had to be cold-booted to recover! Another time, I played a joke on it: put a small sand in its eye and see if it can open its eye?
This is how it is:
I changed windows\system32\config\sam to 2sam
Then it said the security account manager failed and couldn't enter. Doesn't the system have a "legal" backup of SAM? Why doesn't it extract and restore? I was very disappointed. It turned out that XP was as fragile as a house of cards!
In 2000 XP, it still equips with making an MSDOS boot disk (actually a WINME boot disk, when formatting a floppy disk). The file format of Windows XP 2000 still retains FAT. When you can't enter the system, you can use a DOS boot disk to enter and access to solve serious system problems. At this time, one or two simple DOS commands can bring XP back to life!
There are still a large number of DOS games and software that are still popular. On the one hand, it is inertia. I believe there are other reasons that make them continue to be popular among some people and in certain occasions forever. That is the unique charm and style of classic DOS games: they occupy extremely few resources, generally a few tens of KB, have extremely low requirements for system configuration, are very popular, and have strong survivability. They eat grass and give out milk. Simple, implicit, quiet, exquisitely conceived, short but rich in connotation, with a symbolic meaning, leaving room for imagination in the simple dot matrix graphic outlines.
If Windows high-definition large-action games are like a group of noisy naked dancers in a nightclub, then classic DOS games are like a shy girl who accidentally meets and is wearing a thin veil after bathing.
Just as as long as there are Chinese people, those
************** Sun and Moon
************** Horizon and Cape
************** The beginning of man, nature is good
************** A graceful lady, a gentleman's good catch
************** To see further than ever, climb a bit higher
************** People have joys and sorrows, the moon has wax and wane
************** The setting sun flies with the lone wild duck, the autumn water merges with the long sky
and so on. will always be intoxicating and passed down. In this regard, I have actually discovered a seemingly irrelevant similarity: Is there a mysterious coincidence between this Western technological product of DOS and the aesthetic taste of the Eastern Chinese people?
2. Virtual DOS
In order to be compatible with DOS, Microsoft developed a virtual platform (DOS VM). It can directly run many DOS games and software. In order to try to solve some incompatibility problems, Windows 2000 XP still retains two original DOS configuration files (config.sys autoexec.bat, but change sys bat to nt and put them in windows\system32). Users need to set it up before running DOS software. You can refer to the "XP Complete Manual" compiled by Americans. After setting it up, running games is almost the same as in DOS. Some software can be run directly by clicking, and some need to be run in the command prompt (2000 XP's prompt also has two types: the newer version of CMD.EXE can be compatible with some older versions of COMMAND.COM (still seems to be this name)). In the virtual DOS, scripts that can't be run in Windows can also be run.
3. Broad-sense DOS
Personally, I think the soul of DOS (including UNIX, LINUX, etc.) is commands (command line interface CLI, command line interface; compared to graphic user interface GUI, graphic user interface). Commands are languages and symbols. In this regard, it can be said that DOS is a symbol. The competition between Windows and DOS should not be the competition between themselves but the competition between GUI and TLI. Essentially, it is the competition between "graphics and symbols (of course including languages)". From this sense, this competition still continues "inside Windows" and will never disappear. Because if we don't understand it this way, we will have such a question: "Are commands like regedt32 msconfig gpedit.msc mmc wmic and so on DOS or Windows?" In fact, since the beginning of human history, such a competition has been continuing. Language originally was pictures, knotted ropes, completely pictographic characters, and finally evolved into abstract symbolic language. But does human beings not need graphics? Obviously, graphics and symbols are brothers, just like Zeus and Poseidon respectively controlling the sky and the sea, they control the two needs of human beings.
So personally, I think that in a broad sense, this battle between symbols and graphics is not about one killing the other and replacing each other, but about each getting their proper place and each showing their strengths. This is exactly the result of human wisdom.
The power of symbols is concentrated in scripts. Windows programmers and advanced users need scripts to realize their intentions. The Windows script host WSH (WINDOWS SCRIPT HOST) has two ways: Wscript.exe Cscript.exe (probably). They are all in the SYSTEM32 directory. Some scripts can't be run in Windows and can only be run in the DOS window opened by CSCRIPT.EXE. In this sense, Windows is DOS, and they are no different. Or, DOS has merged into Windows, and blood has merged with water. Or, a shield-like indestructible alloy has been forged. Or, it is a genetic recombination. Not only on the local machine, but also in network remote operations, when effective work is needed, graphics are fragile and symbols soar.
Latest commands to control the whole situation in XP
Although now it is the world of graphic user interface GUI (Graphic User Interface), to manage the system more conveniently, quickly, and deeply into the bottom layer, and to solve difficulties, one still has to rely on abstract and powerful commands.
As we all know, the truly multi-tasking and multi-user large-scale local area management mainstream operating system UNIX with tenacious vitality is built with commands!
XP has strengthened old commands such as DOS5.0-6.22!
XP has not only not abandoned DOS commands but also strengthened them. For example, APPEND, EDLIN (these need to be used in the compatible old version command line, type COMMAND in the run, not CMD, CMD is the new version.), EXPAND, MOVE, REPLACE, TREE, XCOPY, etc. These can be used in the new version command line, and some have added switches. Also, the FOR command has added many powerful switches.
FOR /F /R /L can be compared, and there must be gains.
In order to repair the system when it is paralyzed, 2000 XP has added the recovery console RECOVERY CONSOLE, which is actually equivalent to simulating the DOS platform. It has the main original DOS commands built-in, and some newly added life-saving straws, such as FIXMBR, FIXBOOT, DISKPART (manage partitions), MAP (view disks), etc.
What is even more incredible is that while Mr. GATE was desperately driving away the DOS kernel and advocating GUI (WIN95 WIN98 ME NT 2000 XP 2003), in the current 2000 XP 2003, as long as you type WMIC in the run or command line, the WMIC:ROOT\CLI>_ will appear, and typing /? will show commands to control the whole system! There are masses of them.
It can be seen that due to the function of the unique kernel, commands will never die! As long as the system is there, the commands are there. With the development of the Internet, this point will be more prominent!
Attach the global commands:
Microsoft Windows XP
(C) Copyright 1985-2001 Microsoft Corp.
C:\>wmic
wmic:root\cli>
The effective global switches are:
/NAMESPACE The namespace path used by the alias.
/ROLE The role path containing this alias definition.
/NODE The server used by the alias.
/IMPLEVEL The client impersonation level.
/AUTHLEVEL The client authentication level.
/LOCALE The language identifier applied by the client.
/PRIVILEGES Enable or disable all privileges.
/TRACE Output debug information to stderr.
/RECORD Write all input commands and output to a log.
/INTERACTIVE Set or reset the interactive mode.
/FAILFAST Set or reset the FailFast mode.
/USER The user used during the session.
/PASSWORD The password used for session login.
/OUTPUT Specify the mode for output redirection.
/APPEND Specify the mode for output redirection.
/AGGREGATE Set or reset the aggregation mode.
/? Usage information.
For information about specific global switches, enter: switch-name /?
The current role has the following aliases.:
ALIAS - Access aliases on the local machine
BASEBOARD - Management of the baseboard (also called the motherboard or system board).
BIOS - Management of the basic input/output service (BIOS).
BOOTCONFIG - Management of the boot configuration.
CDROM - Management of CD-ROM.
COMPUTERSYSTEM - Management of the computer system.
CPU - Management of the CPU.
CSPRODUCT - Computer system product information of SMBIOS.
DATAFILE - Management of DataFile.
DCOMAPP - Management of DCOM programs.
DESKTOP - Management of the user desktop.
DESKTOPMONITOR - Management of the monitor.
DEVICEMEMORYADDRESS - Management of device memory addresses.
DISKDRIVE - Management of physical disk drives.
DISKQUOTA - NTFS volume disk space usage.
DMACHANNEL - Management of direct memory access (DMA) channels.
ENVIRONMENT - Management of system environment settings.
FSDIR - Management of file directory system items.
GROUP - Management of group accounts.
IDECONTROLLER - Management of IDE controllers.
IRQ - Management of interrupt request lines (IRQ).
JOB - Provides access to jobs scheduled using the scheduling service.
LOADORDER - Management of defining system services that execute dependently.
LOGICALDISK - Management of local storage devices.
LOGON - Login sessions.
MEMCACHE - Management of cache memory.
MEMLOGICAL - Management of system memory (configuration layout and memory availability).
MEMPHYSICAL - Management of physical memory of the computer system.
NETCLIENT - Management of network clients.
NETLOGIN - Management of network login information (of a certain user).
NETPROTOCOL - Management of protocols (and their network characteristics).
NETUSE - Management of active network connections.
NIC - Management of network interface controllers (NIC).
NICCONFIG - Management of network adapters.
NTDOMAIN - Management of NT domains.
NTEVENT - Items of the NT event log
NTEVENTLOG - Management of NT time log files.
ONBOARDDEVICE - Management of common adapter devices built-in on the motherboard (system board).
OS - Management of the installed operating system.
PAGEFILE - Management of virtual memory file swapping.
PAGEFILESET - Management of page file settings.
PARTITION - Management of physical disk partition areas.
PORT - Management of I/O ports.
PORTCONNECTOR - Management of physical connection ports.
PRINTER - Management of printer devices.
PRINTERCONFIG - Management of printer device configurations.
PRINTJOB - Management of print jobs.
PROCESS - Management of processes.
PRODUCT - Management of installation package tasks.
QFE - Quick troubleshooting.
QUOTASETTING - Setting disk quota information for a volume.
RECOVEROS - When the operating system fails, the information collected from memory.
REGISTRY - Management of the computer system registry.
SCSICONTROLLER - Management of SCSI controllers.
SERVER - Management of server information.
SERVICE - Management of service programs.
SHARE - Management of shared resources.
SOFTWAREELEMENT - Management of software product elements installed on the system.
SOFTWAREFEATURE - Management of software product components of SoftwareElement.
SOUNDDEV - Management of sound devices.
STARTUP - Management of commands that automatically run when a user logs in to the computer system.
SYSACCOUNT - Management of system accounts.
SYSDRIVER - Management of system drivers for basic services.
SYSTEMENCLOSURE - Management of physical system enclosures.
SYSTEMSLOT - Management of physical connection points including ports, sockets, accessories, and main connection points.
TAPEDRIVE - Management of tape drives.
TEMPERATURE - Management of data from temperature sensors (electronic thermometers).
TIMEZONE - Management of time zone data.
UPS - Management of uninterruptible power supplies (UPS).
USERACCOUNT - Management of user accounts.
VOLTAGE - Management of data from voltage sensors (electronic ammeters).
VOLUMEQUOTASETTING - Associating a certain disk volume with disk quota settings.
WMISET - Management of WMI service operation parameters.
For information about specific aliases, enter: alias /?
CLASS - Press the ESC key to return to the complete WMI architecture.
PATH - Press the ESC key to return to the complete WMI object path.
CONTEXT - Display the status of all global switches.
QUIT/EXIT - Exit this program.
For more information about CLASS/PATH/CONTEXT, enter: (CLASS | PATH | CONTEXT) /?
I also hope that the experts will further correct and supplement in this regard to improve together!