『楼 主』:
转贴：多重启动经验谈
使用 LLM 解释/回答一下
多重启动经验谈
||→相关下载>>>System Commander 2000 Pro 5.04
System Commander 2000 Update 5.06
system Commander Deluxe 4.03
操作系统发展到今天，类型有了好多种，有DOS系列，Windows系列，Unix系列等等，还有
一些诸如BeOS等偏门，因而，喜欢尝试新鲜和因工作学习需要的家伙，就必须在自己的机
器中装上至少2个的OS，所以，多重启动就产生了。
进行多重启动，就必须使用多重启动系统引导软件，有些软件是OS系统本身自带的，比如
Linux的lilo，Windows的NTloader，还有的就是第三方的引导软件，比如V communica-
tions，.inc的System Commander系列，PowerQuest Corporration的BootMagic等等都是很
好的选择。
对于一般的PC用户来说，Windows是最常用的OS，所以下文谨就Windows谈谈笔者在多重启
动上的一些经验教训。
一、使用Windows自带的引导软件
很多精通95/98的玩家都知道，他们可以和DOS6.22及之前的版本共存，通过98/95的启动菜
单进行双引导，只要按照，先安装DOS，再安装95/98的顺序，并在安装95/98过程中选择保
留以前的操作系统，就会在启动菜单中多一项"以前的操作系统"选项（如果看不到启动菜
单，只要在启动时按下F8就可以，或者编辑MSDOS.SYS文件，增加一行:bootmenu=1即可）。
但是，如果你是要在已经安装的95/98的硬盘上追加安装DOS的话，就必须使用第三方引导
软件，或者在安装好DOS之后，覆盖安装一遍95/98。
自从有了Windows2000（WindowsNT），M$在系统中附带了一个NTloader，可以很好的解决
多重引导，一般来说，只要按照DOS->95/98->Linux->win2K这种的版本由低到高的顺序安
装系统，就可以完美的，由系统自动的建立多重引导环境，win2K在安装过程中能自动识别
旧有的系统。
值得一提的是，win2K的NTloader允许你在机器上安装数个win2K，不管是想同版本的还是不
同版本的，也就是说，可以同时安装pro，server，Advance Server在你的硬盘上，还可以
安装多个Pro，或者多个Server/Advance Server在你的硬盘上，甚至，如果你愿意的话，可
以安装N个Pro，M个Server，O个Adserver在你的硬盘上，而不必担心无法引导或者系统文件
混在一起。
至于NTloader有没有上限，这我就不知道了，也没那个功夫和精力去作这种试验。
有些同志发现，如果先安装2000，之后不通过第三方的引导软件直接安装DOS/98/95后，
NT-loader的引导菜单没有了，启动机器就直接进入DOS/98/95，2000无法启动了，是不是
2000的系统文件坏了?回答是否定的，原因的NTloader被后安装的DOS/98/95搞坏了，修复
很简单，拿来你的2000的安装盘（如果你的机器上有多个版本2000，随便那个版本的安装
盘都可以），安装中，按"R"选择"修复安装"，然后安装过程会象完全安装那样copy文件，
之后重新启动，你会发现，重新启动中，NTloader的引导菜单会一闪而过，到这里，就有2个办法了：
1、启动中不停的按上/下的方向键，取消2000在安装过程中默认的极短的的引导菜单显示
时间，会看到，在除了最下面的一个选项是Windows2000 Install/Upgrade，上面的选项就
是你原先的选项。实际上，到此为止，你的NTloader已经修复了，完全可以不必将修复安
装过程继续下去，而后面将要进行的修复过程不过是修复2000的系统文件，即winnt目录里
面的文件。所以，你可以选择正常的2000启动选项，进入到2000中，然后删除硬盘上2000
安装过程copy的$win_nt$.~sl和$win_nt$.~BT目录，再修改boot.ini文件，将Windows 2000
Install/Upgrade选项删除，并将默认的启动菜单显示时间和默认的启动系统改为自己所
希望的就可以了。
2、你可以在重启之后继续以后的修复过程直到结束，但必须要提醒大家注意的是，后面的
系统文件修复过程会报告说XXXXX文件不是安装系统时由安装过程复制到系统文件夹的，是
否要修复？此时，除非你的2000系统中没有安装过任何的软件或者SP，否则就不要选择修
复，按ESC忽略，因为很多软件都会向系统文件夹中添加自己的文件，如果修复了（实际上
就是删除），会造成这些软件无法运行。
还有NTloader一个小毛病要告诉大家，如果你先安装的一个中文版的2000后，再安装英文
版的2000，结果会发现NTloader的显示语种就变成了英文（语种和后安装的系统保持一
致），而且会有一些乱码，虽然不影响启动，但看着不舒服，你可以按照上面的方法，用
中文版2000修复安装就可以了。
但是，有一个一举两得的办法，非常简单有效，不必删除什么文件修改什么boot.ini，是
什么呢？
告诉大家，只要在中文版的2000中安装SP2就可以了，至于SP1是否可以，我没有试过？
NTloader的好处就是，不管你启动硬盘上有没有Fat/Fat32的Primary Partition，都可以
实现多系统引导，但是，如果没有Fat/Fat32的Primary Partition，是无法实现DOS/98/95
系统引导启动的，因为他们不支持NTFS格式。由于DOS/98/95的启动文件是必须在C:即激活
的主分区（虽然可以经系统文件安装在别的盘上），如果你的2000要使用NTFS的话，就一
定不能将其安装在C:，即，必须将C:留出来用Fat/Fat32，用于DOS/98/95的安装启动。C:
以外的用NTFS就不要紧了，顶多98/95不能直接访问而以，借助一些其他的软件还是可以读
取NTFS的文件。
二、使用第三方的多系统启动引导软件
目前比较流行的是BootMagic和System Commander，他们有一个局限性就是，必须安装在第一
块硬盘（如果你有多块硬盘的话）的Fat/Fat32的Primary Partition（不管是否激活）。
使用这种软件的好处之一是，你可以设置在启动某一系统时隐藏其他操作系统所在的分区，
以免他们被破坏，维护系统文件的安全。
由于本文不是第三方引导软件的使用说明，所以仅谈谈鄙人的使用经验。
如果第三方的多系统启动引导软件的文件遭到破坏，导致机器无法启动;或者在没有先
uninstall他们的情况下就format他们所在的硬盘，导致机器无法启动，可以用98/95/DOS的
启动盘启动机器后，用fdisk/mbr重写硬盘的分区表，即可解决问题。我用下来感觉System
Commander比较坚固，即便直接format他所在的硬盘，仍然可以启动机器，只不过在启动时
报错说无法启动System Commander，然后列表硬盘主分区，让你选择从哪个分区启动。
其次，BootMagic仅仅是个启动引导软件，必须配合PQmagic使用，而System Commander则包
括了整个的硬盘分区操作功能?但是，System Commander如果要进行分区操作和通过他添加新
的系统，必须要求硬盘上有95/98/ME系统，否则无法进行。
BootMagic可以在Windows环境下安装（包括95/98/ME/2000），提供Windows下的配置界面。
但是在2000下安装可能会出现一些问题，包括uninstall无法顺利完成和安装后的BootMagic
无法在启动时Load（我都遇到过）等等。
System Commander必须在DOS实模式下进行安装，借就是说，2000/ME/98系统中不能安装，必
须用98/DOS启动盘启动后安装，这对DOS不熟悉的使用者来说是个障碍。
System Commander最大的特点（笔者认为）是:启动选项中有"从A:启动"，也就是说不必去修
改BIOS，即便第一启动是HDD-0，通过System Commander，仍然可以从软盘启动，非常便利。
Bootmagic是没有这个功能的。
使用第三方引导软件可以实现多个98类型的操作系统并存，这是NTLoader无法作到的，因为
NT-loader并不改变在启动是用于激活的盘，而第三方引导软件就是通过即时激活启动分区达
到这个目的。
由于鄙人对System Commander使用的比较多，颇有好感，所以推荐大家使用，需要注意的是，
低版本的System Commander不支持ME，目前最新的版本为System Commander 2000 5.05
----------------------
以上均是鄙人在多重启动使用上的一些经验和体验，恐多有谬误，还请大家斧正。
倘若能对一些人有所帮助，不胜欣喜矣？
Multi-Boot Experience
||→Related Downloads>>>System Commander 2000 Pro 5.04
System Commander 2000 Update 5.06
system Commander Deluxe 4.03
By now, there are many types of operating systems, such as the DOS series, Windows series, Unix series, and some niche ones like BeOS. Therefore, those who like to try something new or need it for work and study must install at least 2 OSes on their own machines, thus multi-booting comes into being.
To perform multi-booting, one must use multi-boot system boot software. Some software is built into the OS itself, such as Linux's lilo, Windows' NTloader. There are also third-party boot software, like V communications,.inc's System Commander series, PowerQuest Corporration's BootMagic, etc., which are all good choices.
For general PC users, Windows is the most commonly used OS. So the following will talk about the author's experiences and lessons regarding multi-booting with Windows.
### 1. Using Windows' Built-in Boot Software
Many players proficient in 95/98 know that they can coexist with DOS 6.22 and earlier versions. Through the boot menu of 98/95, a dual-boot can be achieved. As long as DOS is installed first, then 95/98 in that order, and during the installation of 95/98, select to retain the previous operating system, there will be an option "Previous operating system" in the boot menu. (If the boot menu is not visible, just press F8 during startup, or edit the MSDOS.SYS file and add a line: bootmenu=1.) However, if you want to additionally install DOS on an already installed 95/98 hard drive, you must use a third-party boot software or reinstall 95/98 after installing DOS.
Since Windows 2000 (Windows NT) came out, M$ has included an NTloader in the system, which can well solve multi-booting. Generally speaking, as long as you install the systems in the order of DOS->95/98->Linux->win2K from low to high version, a multi-boot environment can be perfectly and automatically established by the system. win2K can automatically identify the old system during installation.
It is worth mentioning that the NTloader of win2K allows you to install several win2Ks on the machine, whether they are the same version or different versions. That is to say, you can install pro, server, Advance Server on your hard drive at the same time, or install multiple Pros, or multiple Servers/Advance Servers, and even, if you want, install N Pros, M Servers, O Adservers, without worrying about being unable to boot or system files being mixed up.
As for whether there is an upper limit for NTloader, I don't know, and I don't have the time and energy to conduct such experiments.
Some comrades find that if you install 2000 first, and then directly install DOS/98/95 without using a third-party boot software, the boot menu of NT-loader disappears, and the machine directly enters DOS/98/95, and 2000 cannot be started. Is the system file of 2000 damaged? The answer is no. The reason is that the NTloader is damaged by the later-installed DOS/98/95. The repair is very simple. Take out your 2000 installation disc (if there are multiple versions of 2000 on your machine, any version's installation disc is okay), during installation, press "R" to select "repair installation", then the installation process will copy files like a complete installation, and then restart. You will find that during the restart, the boot menu of NTloader will flash by. Here, there are 2 methods:
1. Keep pressing the up/down arrow keys during startup to cancel the extremely short display time of the boot menu defaulted by 2000 during installation. You will see that the option at the bottom is Windows 2000 Install/Upgrade, and the options above are your original ones. In fact, by this time, your NTloader has been repaired. You can completely not continue the repair installation process. The subsequent repair process is just to repair the system files of 2000, that is, the files in the winnt directory. So you can choose the normal 2000 startup option, enter 2000, then delete the $win_nt$.~sl and $win_nt$.~BT directories copied by the 2000 installation process on the hard drive, and then modify the boot.ini file, delete the Windows 2000 Install/Upgrade option, and change the default boot menu display time and default boot system to what you want.
2. You can continue the subsequent repair process after restarting until the end. But you must remind everyone to pay attention that the subsequent system file repair process will report that XXXXX file is not copied to the system folder by the installation process during system installation. Do you want to repair it? At this time, unless no software or SP is installed in your 2000 system, otherwise do not choose to repair, press ESC to ignore, because many software will add their own files to the system folder. If you repair (actually delete), these software will not be able to run.
There is also a small problem with NTloader to tell everyone. If you install a Chinese version of 2000 first, and then install an English version of 2000, you will find that the display language of NTloader becomes English (the language is consistent with the later-installed system), and there will be some garbled characters. Although it does not affect startup, it is uncomfortable to look at. You can use the Chinese version of 2000 repair installation according to the above method.
But there is a kill-two-birds-with-one-stone method, which is very simple and effective. You don't need to delete any files or modify any boot.ini. What is it?
Tell everyone, as long as you install SP2 in the Chinese version of 2000. Whether SP1 can do it, I haven't tried it?
The advantage of NTloader is that it can achieve multi-system booting regardless of whether there is a Fat/Fat32 Primary Partition on the startup hard drive. However, if there is no Fat/Fat32 Primary Partition, it is impossible to boot the DOS/98/95 system, because they do not support the NTFS format. Since the boot files of DOS/98/95 must be on C: that is, the activated primary partition (although they can be installed on other disks through system files), if your 2000 wants to use NTFS, you must not install it on C:, that is, C: must be left for Fat/Fat32 for the installation and startup of DOS/98/95. It doesn't matter if other drives besides C: use NTFS. At most, 98/95 can't access it directly, but with some other software, you can still read the files in NTFS.
### 2. Using Third-Party Multi-System Boot Boot Software
Currently, BootMagic and System Commander are more popular. They have a limitation that they must be installed in the Fat/Fat32 Primary Partition (whether activated or not) of the first hard drive (if you have multiple hard drives). One of the advantages of using such software is that you can set to hide the partitions where other operating systems are located when booting a certain system, so as not to damage them and maintain the safety of system files.
Since this article is not an instruction manual for third-party boot software, only the author's usage experience will be talked about.
If the files of the third-party multi-system boot boot software are damaged, resulting in the machine being unable to boot; or if you format the hard drive where they are located without first uninstalling them, resulting in the machine being unable to boot, you can use the boot disk of 98/95/DOS to start the machine, and then use fdisk/mbr to rewrite the partition table of the hard drive, which can solve the problem. I have found that System Commander is relatively robust. Even if you directly format the hard drive where it is located, the machine can still start. It just reports an error during startup saying that System Commander cannot be started, and then lists the primary partitions of the hard drive, allowing you to choose which partition to start from.
Secondly, BootMagic is just a boot boot software and must be used with PQmagic, while System Commander includes the entire hard drive partition operation function. However, if System Commander wants to perform partition operations and add new systems through it, it must require that there is a 95/98/ME system on the hard drive, otherwise it cannot be done.
BootMagic can be installed in the Windows environment (including 95/98/ME/2000), providing a configuration interface under Windows. But there may be some problems when installing in 2000, including that the uninstall cannot be completed smoothly and the installed BootMagic cannot be loaded during startup (I have encountered both).
System Commander must be installed in real DOS mode, that is, it cannot be installed in 2000/ME/98 systems. It must be installed after booting with a 98/DOS boot disk. This is an obstacle for users who are not familiar with DOS.
The biggest feature of System Commander (the author thinks) is: there is "Boot from A:" in the boot options, that is, you don't need to modify the BIOS. Even if the first boot is HDD-0, you can still boot from the floppy disk through System Commander, which is very convenient. Bootmagic does not have this function.
Using a third-party boot software can realize the coexistence of multiple 98-type operating systems, which is what NTLoader cannot do, because NT-loader does not change the disk used for activation during startup, and the third-party boot software achieves this purpose by activating the startup partition in real time.
Since the author has used System Commander more and has a good impression of it, it is recommended that everyone use it. It should be noted that the low-version System Commander does not support ME, and the latest version is System Commander 2000 5.05
----------------------
The above are all the author's experiences and experiences in multi-booting. There may be many errors, and I hope everyone can correct them. If it can be helpful to some people, I will be very happy.
|
