After seeing everyone make so many DOS boot disks, my eyes got a little dazzled, so I left the computer and took a shower. In the shower room I suddenly had some thoughts about DOS and WINDOWS, and wanted to write them down for everyone to see.
I started using computers in 1996. Back then DOS ruled the world, very gloriously. Later, as WINDOWS became widespread, DOS began to retreat. First it coexisted with WIN95 and WIN98, then with WINME, WIN2000, WINXP, DOS gradually disappeared from most people's sight. WINDOWS really is a foolproof operating system, and we have to admit its advantages. My dad is 55, and he still chats with me on QQ every day!
Everyone has made so many boot disks — what are they for? In the past I only used them when reinstalling DOS. Now I guess everyone surely wouldn't be doing this so enthusiastically just for that purpose alone. I think it's for actually “using” DOS. I put quotation marks around "using" just to say that without a boot disk, it seems we can't use it quite so smoothly, right!
Everyone here is unwilling to give up WINDOWS, and of course also unwilling to give up DOS. With a very sincere attitude, I want to ask everyone: can we win DOS back a position of equal standing? There are many experts here, maybe this problem really can be solved.
Can we win back half the hard disk for DOS??? And not have to rely on rebooting and inserting a DOS boot disk every time we want to use DOS.
In the past WIN95 could coexist with DOS. I remember that back then there were two sets of boot files in my C drive, with the extensions DOS and WIN, and they could be switched back and forth. Now I'm using WINME, and I feel it treats DOS unfairly,
so I tried to change it. Aren't there patches online? So I tried one. Now I can enter WINME's “pure” DOS. I put quotation marks around pure to show that it isn't pure. I guess the principle is that it separates WINME's boot process
, so that the final WIN command that loads the GUI does not execute automatically, but waits for your command, like using WIN3.X.
In the past WIN95 and DOS each booted the system on their own, along two different lines, from IO.SYS, MSDOS.SYS to COMMAND.COM, CONFIG.SYS, AUTOEXEC.BAT. By the time of WINME, Microsoft got crafty. From how it feels after my modifications, they seem to have strengthened the role of IO.SYS, establishing its own unique position inside that file, so that the WINDOWS system gained control and squeezed DOS out.
The reason I say the modified WINME pure DOS is not pure is because on that basis I used Wengier's boot disk setup to make the config files. After booting the DOS system, I used MEM to check, and the first resident program in memory was SYSTEM. That is obviously from WINDOWS! I think the main culprit is its IO.SYS, because looking through the other boot files, there is nothing about SYSTEM. I don't know much about the contents of IO.SYS, but I suppose there must be things in it that restrict DOS. So yesterday I was asking what could be used to view and modify IO.SYS.
Wengier should know a lot about this, right? You must have modified the IO.SYS in your boot disk. I wonder whether focusing on IO.SYS could solve the problem of booting DOS from the hard disk?! Please think it over, experts!
I'm almost done writing. Looking back on it, it's possible that I'm just ignorant and inexperienced, and that in fact everyone has already solved this problem, and everyone's DOS now can already coexist with WINDOWS? If so, then please don't laugh at me, just tell me the method! If it is still an unsolved problem, then please give it some thought!!!
Thank you, everyone!!!
I started using computers in 1996. Back then DOS ruled the world, very gloriously. Later, as WINDOWS became widespread, DOS began to retreat. First it coexisted with WIN95 and WIN98, then with WINME, WIN2000, WINXP, DOS gradually disappeared from most people's sight. WINDOWS really is a foolproof operating system, and we have to admit its advantages. My dad is 55, and he still chats with me on QQ every day!
Everyone has made so many boot disks — what are they for? In the past I only used them when reinstalling DOS. Now I guess everyone surely wouldn't be doing this so enthusiastically just for that purpose alone. I think it's for actually “using” DOS. I put quotation marks around "using" just to say that without a boot disk, it seems we can't use it quite so smoothly, right!
Everyone here is unwilling to give up WINDOWS, and of course also unwilling to give up DOS. With a very sincere attitude, I want to ask everyone: can we win DOS back a position of equal standing? There are many experts here, maybe this problem really can be solved.
Can we win back half the hard disk for DOS??? And not have to rely on rebooting and inserting a DOS boot disk every time we want to use DOS.
In the past WIN95 could coexist with DOS. I remember that back then there were two sets of boot files in my C drive, with the extensions DOS and WIN, and they could be switched back and forth. Now I'm using WINME, and I feel it treats DOS unfairly,
so I tried to change it. Aren't there patches online? So I tried one. Now I can enter WINME's “pure” DOS. I put quotation marks around pure to show that it isn't pure. I guess the principle is that it separates WINME's boot process
, so that the final WIN command that loads the GUI does not execute automatically, but waits for your command, like using WIN3.X.
In the past WIN95 and DOS each booted the system on their own, along two different lines, from IO.SYS, MSDOS.SYS to COMMAND.COM, CONFIG.SYS, AUTOEXEC.BAT. By the time of WINME, Microsoft got crafty. From how it feels after my modifications, they seem to have strengthened the role of IO.SYS, establishing its own unique position inside that file, so that the WINDOWS system gained control and squeezed DOS out.
The reason I say the modified WINME pure DOS is not pure is because on that basis I used Wengier's boot disk setup to make the config files. After booting the DOS system, I used MEM to check, and the first resident program in memory was SYSTEM. That is obviously from WINDOWS! I think the main culprit is its IO.SYS, because looking through the other boot files, there is nothing about SYSTEM. I don't know much about the contents of IO.SYS, but I suppose there must be things in it that restrict DOS. So yesterday I was asking what could be used to view and modify IO.SYS.
Wengier should know a lot about this, right? You must have modified the IO.SYS in your boot disk. I wonder whether focusing on IO.SYS could solve the problem of booting DOS from the hard disk?! Please think it over, experts!
I'm almost done writing. Looking back on it, it's possible that I'm just ignorant and inexperienced, and that in fact everyone has already solved this problem, and everyone's DOS now can already coexist with WINDOWS? If so, then please don't laugh at me, just tell me the method! If it is still an unsolved problem, then please give it some thought!!!
Thank you, everyone!!!
