|
jsntydx
新手上路
积分 16
发帖 5
注册 2009-6-6
状态 离线
|
『楼 主』:
win98 为何不能启动
使用 LLM 解释/回答一下
在vmware里做实验， 我在第一扩展区(hd0,4),用ghost的系统（放在hd0，0能启动）装了windows98，hd0,0 是dos98， grub为grub4dos 最新版。在菜单中增加如下：
map --in-situ (hd0,4)+1 (hd0)
map --hook
root (hd0,0)
chainloader +1
启动后进win98，就是不能到桌面状态，死机了。 不知哪位做过win98启动，请指教。
Doing experiments in VMware, I installed Windows 98 in the first extended partition (hd0,4) using a Ghost system (which can boot from hd0,0). hd0,0 is DOS 98, and GRUB is the latest version of grub4dos. I added the following in the menu:
map --in-situ (hd0,4)+1 (hd0)
map --hook
root (hd0,0)
chainloader +1
After booting into Win 98, it just freezes and doesn't reach the desktop. I wonder if anyone has done Win 98 booting. Please give me some advice.
|
|
 2009-6-26 07:30 |
|
|
不点
银牌会员
不甘寂寞的人
积分 2491
发帖 1115
注册 2003-9-24
状态 离线
|
『第 2 楼』:
使用 LLM 解释/回答一下
windows(至少98系列)有个特性，它会记住它的系统文件在哪个盘符上。如果你的 98 安装在 D 盘上，那么它启动后也只去 D 盘寻找系统文件，找不到就死机或者蓝屏。如果你此时把 D 盘仿真为 C 盘，那么 win98 去 D 盘寻找系统文件就可能失败，就要出问题了。
仿真只在万不得已的时候才使用，如果能够以不仿真的方式达到目的，那就不要使用仿真。
比如说，假如你的 98 安装在 D 盘，可以正常使用，那么，当克隆到其他机器之后，你无须使用仿真技术，只需适当隐藏掉一些导致盘符错乱的分区（或者增加一个 FAT 格式的 C 分区，如果没有的话）（保证 98 启动后能够在 D 这个盘符上找到系统文件以及system.ini, system.dat 等相关配置文件和注册表文件），然后，直接用 chainloader 来启动 IO.SYS 便可。有时候，COMMAND.COM 是在扩展分区上，这一点，微软的启动程序是不承认的，win98 的启动程序只能从主分区启动 COMMAND.COM。所以，其实只需要把 command.com（以及 config.sys 等） 复制一份放在（没有隐藏的第一个FAT）主分区便可。
Windows (at least the 98 series) has a feature that it remembers which drive letter its system files are on. If your 98 is installed on drive D, then after it starts, it will only look for system files on drive D. If it can't find them, it will crash or blue screen. If you simulate drive D as drive C at this time, then Windows 98 may fail to find the system files on drive D, and problems will occur.
Simulation should only be used as a last resort. If you can achieve the goal without simulation, then do not use simulation.
For example, if your 98 is installed on drive D and can be used normally, then when cloning to other machines, you don't need to use simulation technology. You just need to properly hide some partitions that cause drive letter confusion (or add a FAT - formatted drive C partition if there isn't one) (to ensure that after Windows 98 starts, it can find the system files and related configuration files such as system.ini, system.dat, and registry files on drive D), and then directly use chainloader to start IO.SYS. Sometimes, COMMAND.COM is on an extended partition. This is not recognized by Microsoft's boot program. Windows 98's boot program can only start COMMAND.COM from the primary partition. So, actually, you only need to copy COMMAND.COM (and config.sys, etc.) to the (unhidden first FAT) primary partition.
|
因为我们亲手创建，这个世界更加美丽。 |
|
|
2009-6-28 03:14 |
|
|
xuantian
高级用户
积分 587
发帖 282
注册 2006-4-10
状态 离线
|
|
|
2009-7-31 22:05 |
|
|
tusheng
中级用户
积分 213
发帖 104
注册 2007-8-31
状态 离线
|
『第 4 楼』:
使用 LLM 解释/回答一下
Originally posted by 不点 at 2009-6-28 03:14 AM:
windows(至少98系列)有个特性，它会记住它的系统文件在哪个盘符上。如果你的 98 安装在 D 盘上，那么它启动后也只去 D 盘寻找系统文件，找不到就死机 ...
command.com在d盘应该没关系，关键应该是io.sys和msdos.sys不应该在d盘的。这2个只有在活主才可以启动
Originally posted by Budian at 2009-6-28 03:14 AM:
Windows (at least the 98 series) has a feature that it will remember which drive letter its system files are on. If your 98 is installed on drive D, then after it boots, it will only look for system files on drive D. If it can't find them, it will crash...
command.com being on drive D is okay. The key point is that io.sys and msdos.sys should not be on drive D. These two can only boot if they are on the active primary partition.
|
|
|
2009-11-22 10:38 |
|
|
