Summary of "Installing Windows NT on the '90s Mystery PC but Everything Goes Wrong..."
Summary of technological concepts, product features, and troubleshooting (from the subtitles)
Revisiting a “’90s mystery PC” build (Windows 98 era)
- The video resumes work on a custom-built 1990s system that has been:
- Physically and electrically unreliable
- Affected by a power supply failure
- Missing or damaged front panel components, including a broken front panel / CD drive faceplate
Power supply replacement + AT vs ATX compatibility
- The system uses an older AT-style motherboard, which differs from ATX in:
- Connector type
- Power switching behavior
- The creator replaces the system’s power supply with a modern ATX PSU and uses a custom ATX-to-AT adapter so the ATX supply can operate in an AT system.
- The host rewires the physical power switch wiring:
- In older AT systems, the external switch could route AC 110V through the switch for DC conversion.
- After ATX conversion, the external switch no longer routes AC for DC conversion.
- With the adapter, the external switch effectively becomes a “glorified paper clip.”
- ATX “turn-on” behavior is achieved by jumping PSU control lines, with the noted reference being green wire to black wire (PSU control signal to ground).
Power-on failures due to power distribution / wattage constraints
- Even after the switch wiring change, the system initially does not fully power on.
- Troubleshooting includes unplugging various devices from Molex connectors:
- With only the motherboard/CPU fan connected, the system powers successfully.
- Key insight:
- The “replacement” PSU mentioned (e.g., 250W, 300W) still cannot provide enough power for the full load.
- Resolution:
- A significantly higher-wattage PSU (around ~485W) is required from another system to power reliably:
- Motherboard
- HDD
- CD drive
- Tape drive
- Floppy drive
- Etc.
- A significantly higher-wattage PSU (around ~485W) is required from another system to power reliably:
- The video frames this as surprising for a mid-’90s machine, but it reflects real-world constraints such as:
- Power rail capacity
- Load handling
- Adapter limitations
Hard drive failure and Windows 98 bad sector recovery attempts
- Booting Windows 98 triggers SCANDISK errors indicating:
- Bad sectors
- Cluster read failures
- During surface scanning, progress stalls around ~32%, suggesting:
- Mechanical issues and/or
- Failing media
- The creator considers whether to wipe sensitive data found on the drive (e.g., QuickBooks data) and decides to wipe for privacy/security.
Using a bootable diagnostic environment (Hiren’s BootCD)
- To avoid wiping without evidence, the creator uses Hiren’s BootCD to run disk diagnostics:
- References Hard Disk Diagnostic version 2.10
- Mentions tools available via the CD’s diagnostic menu (e.g., “Bart’s” tools)
- Diagnostic interpretation:
- Some tests (read/seek/head select/ECC checks) show partial pass results.
- ECC test fails, and head-related tests indicate issues consistent with drive degradation.
- Conclusion:
- The goal is not recovery
- The drive should be replaced
Drive replacement complication: SATA-to-IDE / adapter usage
- Replacement plan:
- A Seagate Barracuda 40GB SATA drive
- Because the vintage system expects IDE, the creator uses a SATA-to-IDE adapter.
- The adapter is treated as a temporary fix to proceed with installation tasks.
- Outcomes:
- The new drive is detected successfully
- Further installation steps encounter formatting/setup problems
BIOS/boot order management
- The creator edits BIOS boot sequence settings to prioritize CD-ROM so the system can boot diagnostic/installation discs.
- Specific “Boot Sequence” options are mentioned in the BIOS menu context.
- The setup may not persist due to concerns around:
- BIOS battery (mentioned as a suspicion)
Windows NT 4 / FAT-NTFS partitioning workflow attempts
- The creator’s goal includes installing Windows NT (likely NT 4).
- Attempted workflow:
- Create/prepare partitions in DOS using Fdisk and format
- Use NT/installer support for large drives and NTFS-capable setup
- Issues encountered:
- Format/partitioning commands terminate unexpectedly
- “Setup cannot find required files” / “invalid system disc”-type flow confusion
- NTFS formatting fails due to partition size limitations (“partition too large”)
- Workaround:
- Create a smaller NTFS partition (around ~200MB) to satisfy NT/installer constraints
- The video ends early due to time/fatigue, leaving the NT installation unfinished
Peripheral/drive issues noted beyond the hard drive
- Floppy drive inconsistencies
- The Windows ME setup disc could not boot cleanly as expected after boot/config changes
- CD drive verification
- The CD drive is confirmed working after:
- Adjusting BIOS boot order
- Using the diagnostic disc
- The CD drive is confirmed working after:
Side note: recording/camera file corruption
- The creator reports video file corruption after copying from an iPhone.
- Fix attempts include using an AirPlay server + screen capture to preserve footage.
Sponsorship
- Leno (Linux-based virtual machines) is mentioned as a cloud-hosting option:
- Pricing example: starting at $5/month
- Includes a link offering a free $100 credit (as described in the subtitles)
Main speakers / sources
- Main speaker/source:
- The video’s primary creator/host (narrates and performs the build/troubleshooting throughout)
- Tools referenced as sources:
- SCANDISK
- Hiren’s BootCD
- Hard Disk Diagnostic 2.10 (diagnostic environment/tests from boot media)
Category
Technology
Share this summary
Is the summary off?
If you think the summary is inaccurate, you can reprocess it with the latest model.
Preparing reprocess...