今時のPCにWindows NTをインストールしないと出られない部屋 (Intel Core-i7 2600K 編)

今時のPCにWindows NTをインストールしないと出られない部屋 (Intel Core-i7 2600K 編)

Ha! Where on earth am I? I’m sure I was filming a video at home! Wake up, Tsumugi! I can’t scan maitake mushrooms!? Wake up! Ha! …Huh…? Where am I…? I was watching an anime just now, but… is there something ringing? It sounds like a projector. A projector? I can’t exorcise ghosts. It looks like you’ve woken up. Who are you!? Show yourself! That’s it! I can’t fulfill your request, but for the sake of convenience, you can call me “R.” What exactly is your purpose? The challenge I’ve set for you is to install Windows NT 4.0 on a computer with a 2600K. If you succeed, you’ll be freed. But if you fail… you’ll be left staring at a broken Windows Me forever. I’ve had enough of that! Stop it! Zundamon’s mental life is already at zero!!! All you have to do is succeed. And that’s true. Is it that simple? Maybe it will work? I don’t think it will work on my current PC… No way. Everyone is still using NT. That’s a lie. Windows 10 and 11, though. Are they still NT? The basic design hasn’t changed since NT 3.1. It’s called NT 10.0. That’s amazing. Now, let’s get started. I wish you all the best. First, let’s take a look at the PC. That’s right. It looks like this. It’s the usual one. It looks like it was brought along . Let’s check the contents. It looks like this. The wiring is as artistic as ever . Mysterious art? It’s not an LS-120, but a regular floppy disk. Other than that, it’s the same as always. Here’s the overall configuration. Pause if you want to take a closer look. Actually, it’s explained in the description below. By the way, NT 4.0 cannot use USB. That’s very inconvenient. I need a PS/2 keyboard and mouse, but this motherboard only supports one . It doesn’t support splitter cables. Splitter cables don’t work, either . If I connect both, only the keyboard responds. That’s a bit lazy. Fortunately, there’s an emulation function. It’s possible to disguise a USB keyboard as a PS/2. That’s a good thing. The mouse is PS/2 and the keyboard is USB. I bought a water-damaged one and replaced the switches. I also upgraded it to white switches, which aren’t sold in stores. A few LEDs are broken. They won’t be noticeable if they’re all lit pink. So, I booted it up. It clicked. I quickly pressed the delete key. The BIOS screen appeared, but it was all blurry and hard to see. It must be the BIOS screen effects. That’s not good. Since I can’t see the screen, I’ll take a screenshot. So, here’s the BIOS screen. As you can see, the CPU is an i7-2600K. It has 8GB of RAM. Is that really all that usable? It’s probably possible to use the 32-bit range. First, reduce the number of cores in the CPU settings. Why reduce it? If there are multiple cores, the installation will stop. So we’ll limit it to a single core until halfway through. I see. We’ll also disable hyperthreading. This is for the same reason. Performance will decrease if a logical core is selected. We don’t need that. Next, we’ll configure the storage. Change the SATA controller to IDE mode. Why? SATA didn’t exist back then, so AHCI mode wouldn’t work. So we need to make it appear as an IDE connection. This is important. By the way, only SATA ports 0 through 3 can be used as IDE. So only four can be used? Sometimes the rest can be used as SATA. Does it depend on the model? Now that the settings are complete, save and exit. Are we ready? Here’s the NT4.0 installation CD. I put it in the CD drive. First, turn on the power. It’s a click away. NT4.0 is a bootable CD, so the installer should start. That’s a convenient feature. Even with 95, 98, and Me, OEM versions may work. Is that true? It depends on the product. It rebooted somehow . Actually, this won’t boot. Why? The CPU identifier is too new, so it’s not considered a compatible CPU. Which CPUs will it work with? It’s impossible to say for certain generations of CPUs. It’s a problem with the CPUID acquisition mechanism. I don’t really understand. For more information, there’s a link to an explanation in the description below. It’s in English, though. That’s fine. This issue will be fixed in Service Pack 6. Install it now. To install Service Pack 6, you need to install NT4.0 first. What? It’s like a can opener in a can. ｡ﾟ(ﾟ^∀^ﾟ)ﾟ｡GAHAHAHAHA!! This is no laughing matter. Someone overseas has created a workaround , so I’ll use that this time. Thank you. I found the floppy disk I inserted here. What a convenient twist. It’s a modified MS-DOS boot disk. The settings look something like this. It’s very short. There are no drivers included. It’s just the bare minimum. Why do I need an MS-DOS floppy disk? The countermeasure tool is MS-DOS software, so you need to start MS-DOS first. I see. By the way, the countermeasure tool spoofs the CPUID. Spoofing it causes problems with multi-CPU. What kind of problem is it? It stops halfway through if you don’t set it to single-core. That’s why I set it on the BIOS screen? If you run it with multi-core enabled, this error will be displayed for a few frames and then the system will restart. Can a fighting game player read this? The error message is roughly translated as follows: There’s no way this CPU can be multi-core. Impossible! (※Is it really impossible?!) It means something like this. Oh, right… insert a floppy disk and try booting. It works when you insert it into the floppy drive. I know about it. There’s probably a generation that doesn’t know about it. Only about 10% of people use it. Turn it on, wait a while, and MS-DOS will boot from the floppy disk. It’s always pretty plain looking. So, MS-DOS has booted. Run the setcpuid command. It’s a workaround tool I downloaded. Various explanations are displayed, but you generally don’t need to do anything. It will rewrite the CPUID and start booting from the CD. What’s this pattern? When the blue screen appears, a grid pattern appears for some reason. It’s strange. Anyway, it booted this time. That ‘s all good, it seems to be working fine. Oh, it seems to have stopped. Why did it stop this time? Here’s the screen I see when I zoom in. It says “Boot device inaccessible.” Boot device? Usually, that means the hard disk. During installation, it also includes the boot CD. Hmm , it looks like the IDE controller isn’t compatible. Or maybe the capacity is too large? This problem itself has been around since the ’90s. So, let’s find a solution. The most well-known method is to press the F6 key. Pressing F6 during bootup brings up the Add Driver screen. You can load a new driver from a floppy disk. So, let’s try that. I’m doing that now, but it seems to load the original IDE driver as well, causing a crash. It ‘s pointless. The solution is to replace the installer’s IDE driver with the one from Service Pack 4. How do you do that? The first way is to extract the contents of the CD, overwrite the driver files, and burn it to a CD-R disc. Are there any other ways? The second way is to use the MS-DOS installer. It copies the contents of the CD to your hard drive, so you can overwrite it while it’s copying. Which is better? Let’s create a disc this time. Here’s the NT4.0 CD. Copy the contents to a random location. Extract it? It will take about 20 minutes, so fast forward. 128x speed! It looks like the copy is complete. The contents of the CD are now in this folder. What do we do next? Next, we’ll update the IDE driver. Remove the NT4.0 CD and insert the Service Pack 4 CD. The disks have been swapped. Open the CD drive and search for the IDE driver. The file name is “ATAPI.SYS.” Why did I find multiple files? NT4.0 supports a variety of CPUs, so there are multiple driver files. I see. This time, I’ll only use the AT-compatible version. Let’s overwrite everything for now. Everything was overwritten. Now we’re ready to burn. We need to extract the boot image. Replace the NT4.0 CD with the NT4.0 CD again. We’ll use ImgBurn as the burning software. Select “Burn Files and Folders.” Open the Advanced tab on the right and open the Bootable Disc tab. From here, we can extract the CD boot image. Select the CD drive and press the floppy button. Save it in an easy-to-find location. Something’s popping up? You’ll be asked if you want to use the boot image now. Press the Yes button and it will be set up automatically. This will create a bootable CD. This is a very convenient feature. Select the files copied from the CD and add them to the list of files to burn. Something else popped up? This looks like an OS installation file, so it will become unusable unless you change the settings. Press the Yes button and it will be automatically corrected. It’s very easy. Once the files are registered, you’re ready to go. Insert a blank disc. Press the Burn button and the ISO image creation will begin. You can leave the volume label as it is . Just press the Yes button. This is the information about the completed ISO image. For some reason, the size is over 700MB, so I can’t burn it because I don’t have an 800MB CD-R. It was about 500MB before I extracted it . I don’t know why, but it increased after I extracted it. I have no choice but to burn it to a DVD. That’s a luxury. It takes about 20 minutes, so I’ll speed it up. It’s 128x speed. Burning is complete. So, can I install with this? So what do you think? Here’s the finished DVD. I chose the erasable type because I don’t want to waste it. That’s eco-friendly. So, let’s try booting again. It’s a click away. MS-DOS boots from the floppy disk. It’s as simple as ever. MS-DOS boots. It starts setcpuid. No action is required, just watch. It spoofs the CPUID and automatically boots from the CD. It’s started. This time, it doesn’t stop. It’s progressed further than before. I’m sure you’ve all experienced the normal NT4.0 installation. I’ll just fast forward through it. That doesn’t seem like it. It allocates space here, but please use an empty hard disk. Otherwise, it may hang during boot. An SSD would be fine. So, the first stage of the installation is complete. It says to remove the floppy disk. But you can’t . Removing it will result in endless reboots. Anyway, press the return key to reboot. The reboot is complete. It starts setcpuid. It’s a familiar thing. By the way, pressing any key will abort it. It will automatically boot from the hard disk. Something has started? The conversion to NTFS has begun. At first, the files are written in FAT16, and then converted to NTFS on the first boot. Why do they do that? You can read and write NTFS if you boot from a CD, but this is a consideration for people installing from MS-DOS. Well, there’s nothing I can do about it. It will reboot once the conversion is complete. The reboot is complete. Launch setcpuid. This is a regular occurrence. The process moves to the hard disk. It says the conversion to NTFS is complete. The screen changes to green. You’re in GUI mode. Now the actual installation begins. Since you’re familiar with this, I’ll fast forward through it. Are there any scenes that aren’t accelerated? Network configuration is required. You can configure it later, but after a service pack, it’s a double effort. Why bother? When configuring the network, an unnamed file is inserted. This means you’ll need to update again. Is it pretty crappy? Sound is the same. Incidentally, support for it ended ages ago. We cannot be held responsible if it’s hacked after you connect it. This is an important point. Network configuration is now complete. Installation is complete. Press the button to reboot. Finally done. Not yet. Now that the installation is complete, let’s take a look at the outside world. It’s a click away. MS-DOS has started. Launch setcpuid. Just a little more after the usual. The hard disk boot loader has taken over. The NT kernel is starting. I’ll switch to the capture screen. Something’s wrong with the colors? It’s 16 colors because there’s no graphics driver. There’s no sound driver either, so there’s no sound. That’s not good. Let’s look at the system properties. The CPUs are listed as 6, 10, and 7. It’s Intel Pentium III “Coppermine.” It’s properly disguised. The memory is about 3.2GB. That’s the limit for a 32-bit x86 environment. Why isn’t it 4GB? It’s occupied by device IO space, so it’s unusable. That’s a shame. Let’s also look at Task Manager. It’s currently in single-CPU mode. Still not working? It won’t work until the disguise is removed. That means we need Service Pack 6. So let’s install it. Before installing 6, we need to install 4. First, let’s set up the folder options. The default settings are inconvenient. That’s important. Here’s the Service Pack 4 CD. What’s going on? The IE 3.0 browser will automatically launch. There’s a link on the left, so open it. If you don’t have a CD, run the provided file. The installation will begin. Service Pack 4 installation is complete. It says so here, too. You have to reinstall Service Pack 4 every time you install a new component . It’s an inconvenient feature. This is the era before WinSxS. It can’t be helped. There’s no version control for system files, so they’re overwritten at will every time you install something. It’s a pain. After rebooting, I run setcpuid. It’s been a while since I lost my temper. I had no choice but to cut it out. Has something changed? I forgot to take a picture, so here’s a separate one. Anyway, I’ll continue working. Next, I’ll integrate IE4. Some people say it’s unnecessary, but it’s inconvenient without it. Is it just a browser? It’s not just a browser, it’s a powerful Explorer. It ‘ll be as easy to use as Windows 98. It seems necessary. I heard that installing it on Windows 95 slowed things down and made things unstable. That’s not a good idea. That’s not the case with NT4.0. It seems the OS itself is designed differently. Is that why it’s doomed? It looks like the installation is complete. Pressing the OK button will reboot the computer. Now that it’s rebooted, run setcpuid. By the way, this is probably the last step. Is it finally finished? The video continues. When I log on, the IE4 installation is complete. The desktop appears. Has the appearance changed? Since IE4 is integrated, I can use Quick Launch. Let’s take a look at Explorer. After installing Service Pack 4, the floppy disk was recognized. The controller was too new. File information has been added to the left. There’s even a pie chart for the drive. Open Folder Options. There have been quite a few changes here, too. New settings have been added, making it almost identical to Windows 2000. That’s a good thing. It’s time to install Service Pack 6. I swapped CDs. The properties have also been improved. It’s just a detour. I put it on this CD, so I’ll open it. Run update.exe and it will start. Super fast! There’s a warning here, too. It says to reapply every time a component is added. It’s the same as always. File protection was implemented starting with Windows 2000, but it wasn’t until Vista that different versions of system files were stored and a fundamental solution was finally implemented. It’s still a long way off. So, let’s reboot. Now, let’s boot up. We don’t need the floppy disk anymore, so remove it. Bye-bye. Let’s power it on. Just a click! Disable the core limit in the BIOS screen. Hyper-threading remains disabled. It’s a bit hard to see, but it varies by model anyway. That’s not a problem. The settings have been saved, so the system will reboot. By the way, this is the last part, so it’s uncut. It booted up successfully. Finally, we can leave the room. It’ll go on a little longer. I’m logged in. First, I’ll close the Welcome screen, since it’s distracting. I don’t need the web view on the desktop, so I’ll turn it off. Let’s look at the system properties. The CPU is listed as 6, 10, and 7. It’s Intel Pentium III “Coppermine.” It’s the same as before, though. It doesn’t recognize future CPUs. What’s going on? It just ignores the excess bits in CPUID. It works, but it’s not accurate. What it is depends on the original CPUID. Naturally, it will be different for an AMD CPU. I see. Well, it’s a big improvement that it even works. That’s true. Next, let’s look at Task Manager. There are two CPU meters. It’s properly recognized. Since it’s a workstation, it has two CPUs, but with a server license, it can use four CPUs. In other words, it can use all four cores of the 2600K. That looks powerful. So, I installed Service Pack 6, but the networking is still not up to date. How do I get it up to date? Installing IE6 will update it. Installing IE6 will also update the networking. Apparently, the integrated Explorer will also be faster. That’s a good thing. So, I’ll install it. Incidentally, there’s a problem with this on a multi-CPU system. It takes about 30 seconds to verify file signatures. It’s per file, not the whole system. On a single CPU, it takes less than a second. Why does it take so long? It’s a mystery. Don’t you understand? I think there was a bug with encryption at the time … Anyway, it seems to be complete. I pressed the Finish button and restarted … It went very smoothly. Continuing with the installation of IE6. The installation is complete. What do I do next? Now that the browser is installed, I have no choice but to do that. Huh? First, I’ll check if I’m connected to the LAN. It looks like it’s open. That’s the most important thing. If it’s connected to the LAN, that’s also possible. That’s impossible… so it’s Hiroshi Abe’s homepage. As expected . It displayed successfully. The colors are also strange here. It’s the 16-color version because there’s no video driver. By the way, it seems like it will soon stop displaying. Why? It seems the server where it’s hosted will be forcing HTTPS. It will no longer be able to be opened with browsers that don’t support HTTPS. Even if it does support HTTPS, the certificate has expired in older environments. That’s not good. Well, there seems to be a grace period until June next year. It could also be a topic for a countermeasure video. Is there a demand for it? Regardless, connecting to the Internet with an older OS is dangerous. Good kids, don’t try this at home. It’s dangerous, so don’t do it. Don’t worry, neither good kids nor bad kids are watching. By default, the computer doesn’t automatically shut off. That’s inconvenient. It shuts off after you replace the file, though. Multiprocessors often don’t work. It’s a no-brainer. Let’s wrap things up. NT4.0 can be installed on modern computers. However, you need to spoof the CPUID. This can be done using setcpuid. It may not boot in multi-core mode. This is necessary until Service Pack 6 is installed. Booting every time is a pain. It’s highly likely the storage won’t be recognized. It can be used with SATA in IDE compatibility mode. It won’t boot unless ATAPI.SYS is updated. Creating a disc is a pain. The biggest problem is the lack of drivers, especially for graphics, sound, and networking. Incidentally, USB isn’t supported by default. Modern onboard features are generally unavailable. Graphics works at 640×480 and 16 colors, but the colors are poor and acceleration isn’t effective. Is there a solution? A PCI bus would be fine. I don’t think there are any motherboards these days that have one. I think I’ll talk about that next time. So, maybe it will continue with the practical application part? Is it a continuation? If I find something good, I’ll continue. So, thank you for watching. I’ll watch again.

次の動画 まだなのだ
前の動画 https://youtu.be/jXgDcuEHTws

すこし元気になったずんだもんと
すこしウザいつむぎちゃんです。

今回は、Sandy Bridgeの自作PCにWindows NT 4.0をインストールします。
探しても仮想マシンから移植する方法ばかりなので自分でやります。

【目次なのだ】
00:00 オープニング
02:15 スペック紹介
03:53 BIOSの設定
05:45 CPUが無理
10:26 IDEが無理
11:30 インストールCDの改造
15:10 インストール 1
16:30 インストール 2
18:68 起動してみる。
20:43 ServicePack4
21:47 Internet Explorer 4.0
22:59 ServicePack4
24:51 Internet Explorer 6.0
28:43 阿部寛のホームページ
30:40 まとめ

【今回のスペック】
マザーボード: AsRock Z77 Extreme6
CPU: Intel Core-i7 2600K
メモリ: DDR3ー1600 4GB X2
SSD: Crucial Real SSD C300 64GB
BD-RE: Panasonic SW-5584
FDD: TEAC FD-235HG
電源: CORSAIR AX760
LAN: Realtek RTL8139/PCI

再生リスト https://youtube.com/playlist?list=PLvDNfPLQdtLucLOO2ccLckllyDmIML0C9&si=TtaZI2lCZQgaJG3y

チャンネル登録するのだ https://youtube.com/channel/UCvKTsSuwBZepPd2VMTtio9g?sub_confirmation=1

↓権利表記等

ボイス
VOICEVOX ずんだもん
VOICEVOX 春日部つむぎ

画像素材
坂本アヒル式 ずんだもん立ち絵素材2.3
坂本アヒル式 春日部つむぎ立ち絵素材3.0

wikipedia
ニコニ・コモンズ

音楽素材
ニコニ・コモンズ
フリーBGM・ MusMus
魔王魂

#ずんだもん #ゆっくり解説 #パソコン #ジャンク #自作PC #WindowsNT #SSD #FDD #90年代 #レトロPC #水冷PC