OPEN NT 4.5 编译方法和源代码下载

OPEN NT 4.5（源代码编译方法）

编译Windows NT 4.0到操作系统的详细方法

OPEN 4.5 ​​​​​​下载 ：https://download.csdn.net/download/MYMOTOE6/88786570

ISO https://download.csdn.net/download/MYMOTOE6/88786572

OPEN NT 4.5（源代码）

作者 斯特凡诺斯

主题 开放NT
语言 英语
虽然一开始并不明显，但 ISO 中有一个自述文件，提供了如何编译它的说明。基本上可以归结为几个要点：

x 将 CD 复制到“W”驱动器上，或将任何其他驱动器替换为“W”，因为显然构建过程要求它位于 W 上。我是否提到过需要将 CD 复制
到 W 驱动器上？
运行“setup.cmd”文件来配置环境并准备好构建过程
运行 zTESTBUILD 并进行干净的构建。它会运行并最终失败。
再次运行 zTESTBUILD，但不要执行干净构建，它应该完成
运行 \cdimg\genall 创建 ISO 映像
事后基本上弄清楚了这些要点，让我们开始吧！

要做的第一件事是创建一个虚拟机来编译它，或者只是 xcopy 并运行。但最大的要求是它必须是 32 位版本的 Windows，因为构建
过程的一部分需要能够使用 NTVDM。为了简单起见，我选择了 Windows 2000 服务器，这样我就可以分配 2GB RAM 和 4 个 CPU 核
心。在构建过程中，它不会使用那么多内存，在构建的各个阶段，核心更为重要，它们似乎可以使用任何和所有核心，而其他各个
部分仅在单个核心上运行。

构建后的 OpenNT 磁盘空间。
我选择为 2000 VM 使用单独的“C”驱动器和“W”驱动器。由于不知道要给它多少空间，我设置了一个 32GB W 驱动器，构建后占用的
空间略低于 4GB。  

安装 VM、格式化 W 驱动器并复制 CD 的内容后，就可以开始构建了。

阶段1
所以基本上你只需对 zTESTBUILD.cmd 回答“Y”，它就会完成它的事情。对我来说，它运行了大约 42 分钟，直到失败，正如预期的
那样。

构建 MVDM 失败
查看 \binaries\nt 目录，目前已构建了 1,274 个文件。当然，如果失败的话，这并不是一个完整的构建。

开始第二阶段
发生此故障后，您可以重新运行 zTESTBUILD.cmd，但这次对干净构建回答“否”。

此步骤大约需要 15 分钟才能完成。

\binaries\nt 目录现在有 1293 个文件。
检查 binaries\nt 目录，现在有 1,293 个文件，查看整个目录，有 2,624 个文件，占用大约 120MB 的空间。

编译操作系统后，剩下的就是创建安装 CD 并启动它。运行 \cdimg\genall.cmd 将创建 ISO 映像。

使用 CDIMAGE 2.47 创建 ISO
这将压缩几乎所有文件，并且又花了 15 分钟来创建 CD。完成这一切后，只需设置虚拟机来运行 NT45Wks.iso 文件即可。

OpenNT 4.5 启动蓝屏
您注意到的第一件事是与 NT 4.0 的零售版本相比，OpenNT 4.5 上有额外的横幅。

OpenNT项目
当然还有设置过程中的不同品牌。OpenNT 的优点之一是它可以将文件系统直接格式化为 NTFS，而不是先创建 FAT 分区，然后将其
转换为 NTFS 的旧方法。这应该可以绕过旧 NT 的磁盘/分区大小的所有限制。

哇崩溃
在 VMWare 上运行 OpenNT 4.5 似乎可以正常运行 Win32 内容，尽管 Win16/WOW 内容立即崩溃，并且 MS-DOS 由于屏幕重绘问题
而速度极其缓慢。我知道 SP 6 之前的 NT 4.0 版本在许多较新的仿真/虚拟机管理程序方面存在问题，即使 CPU 级别设置为常规
Pentium 也是如此。

MS-DOS DPMI 之类的东西（例如 DooM）非常慢，并且在启动时似乎会锁定。

奇怪的是，OS/2 子系统工作得很好。

这就是几乎消失的“OpenNT 4.5”。
添加日期 2024-01-15 11:26:54

----------------------------------------------------------------------------------------------------------------

 Open NT 45( Source)

by Stephanos

Topics OpenNT
Language English
While not obvious at first, there is a readme in the ISO that provides instructions on how to compile it.  
Basically it boils down to a few main points:

xcopy the CD onto a ‘W’ drive, or subst any other drive to ‘W’ as apparently the build process requires it to be on
W.  Did I mention that the CD needs to be copied onto the W drive?
Run the ‘setup.cmd’ file to configure the environment and get the build process ready
run zTESTBUILD and do a clean build.  It will run and eventually fail.
run zTESTBUILD again, but do not do the clean build, and it should finish
run \cdimg\genall to create the ISO image
So with those points basically figured out after the fact, let’s go!

The first thing to do is either create a VM to compile this in, or just xcopy and go.  The big requirement though
is that it must be a 32bit version of Windows, as part of the build process requires the ability to use NTVDM.  For
simplicity sake, I chose Windows 2000 server, so I could allocate 2GB of RAM, and 4 CPU cores.  During the build it
doesn’t use that much memory, cores are more so important during various phases of the build that can seemingly use
any and all cores, while various other parts only run on a single core.

OpenNT disk space after a build.
I chose to use a separate ‘C’ drive, and ‘W’ drive for the 2000 VM.  With no idea how much space to give it, I
setup a 32GB W drive, which after the build takes up just under 4GB of space.  

With the VM installed, and the W drive formatted, and the contents of the CD copied over, it’s time to start the
build.

Phase 1
So basically you just answer ‘Y’ to zTESTBUILD.cmd and it’ll do it’s thing.  For me this took about 42 minutes for
this to run until it failed, as expected.

Failure building MVDM
Looking at the \binaries\nt directory there was now 1,274 files currently built.  Naturally with the failure this
is not a complete build.

Starting phase 2
After this failure you then re-run zTESTBUILD.cmd but this time answer ‘No’ to the clean build.

This step took about 15 minutes to complete.

The \binaries\nt directory now has 1293 files.
Checking the binaries\nt directory there is now 1,293 files and looking at the entire directory there is 2,624
files taking up about 120MB of space.

With the OS compiled, all that remains is to create an install CD and boot it up.  running \cdimg\genall.cmd will
create the ISO image.

Creating the ISO with CDIMAGE 2.47
This will compress almost all the files, and took another 15 minutes to create the CD.  After this is all done it’s
just a matter of setting up a VM to run the NT45Wks.iso file.

Bluescreen bootup of OpenNT 4.5
The first thing you notice is the extra banners on OpenNT 4.5, when compared to a retail copy of NT 4.0.

OpenNT Project
And of course the different branding during setup.  One of the nice things about OpenNT is that it can format
filesystems directly as NTFS, instead of the old way of first creating a FAT partition, and converting it to NTFS.  
This ought to bypass all the limitations of disk/partition sizes for the older NT.

WOW Crash
Running OpenNT 4.5 on VMWare seemed to run the Win32 stuff okay, although Win16/WOW stuff immediately crashed, and
MS-DOS was incredibly slow with screen redraw issues. I know that NT 4.0 builds prior to SP 6 have issues with many
newer emulation/hypervisors even when CPU levels are set to regular Pentium.

MS-DOS DPMI stuff like DooM are incredibly slow, and seemingly lock up when launching.

Oddly enough the OS/2 subsystem works just fine.

So there it is, the nearly vanished ‘OpenNT 4.5’.
Addeddate 2024-01-15 11:26:54
Identifier open-nt-45-cdrom
Scanner Internet Archive HTML5 Uploader 1.7.0

https://archive.org/details/open-nt-45-cdrom