|Subject:||Re: Windows NT 4.0|
|Date:||Wed, 1 Mar 2023 16:41:48 +0100|
|User-agent:||Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:5.2) Goanna/20221030 Epyrus/2.0.0|
On 2023-02-08 14:55, Wilson Birney wrote:|
I have a windows NT 4.0 raw image that when converted with qemu-img to qcow2 or vmdk fails to boot in qemu with no obvious error using the following:Check the virtual hard disk interface. The NT 4.0 boot process relies on some files
in the root directory providing details of that hardware, for example the driver for
virtio-scsi or vmware-scsi. Or an indication to use standard IDE/SATA drivers. This
also includes which partition contains Windows. Some of this is in the text file
BOOT.INI, other parts are in code files in the root, such as a .SYS file for the SCSI
As a result, any virtual disk for running NT 4.0 under virtualization will be specific to
the disk, display and CPU hardware of that VM configuration.
Fortunately however, there are qemu utilities to mount the virtual disk under the host
OS, where an appropriate file system driver can access the FAT, NTFS or HPFS contents
for r/w and thus potentially change of this hardware information. To access registry
settings it is more practical to mount the disk as a secondary disk in a VM that boots
from a minimalist Windows system such as WinPE, from which the secondary disk
registry files can be mounted elsewhere in the registry tree for editing.
Jakob Bohm, CIO, partner, WiseMo A/S. https://www.wisemo.com
Transformervej 29, 2860 Soborg, Denmark. direct: +45 31 13 16 10
This message is only for its intended recipient, delete if misaddressed.
WiseMo - Remote Service Management for PCs, Phones and Embedded
|[Prev in Thread]||Current Thread||[Next in Thread]|