Forum Rules - Formats - Spotlights  -  Home - Library - New Additions

NT 3.51 download corrupt?

ArmacadiaArmacadia
in Site Issues
Specifically it's this file:
https://winworldpc.com/download/41720064-18c3-9a11-c3a4-e284a2c3a570

Tried redownloading it multiple times and always got the exactly same file with checksum not matching what the page says.


Trying to install it fails on random files, too.

Comments

  • 02k-guy02k-guy
    When you did a "Test Archive" with 7zip, what did it report? Because that's the part that matters.

    I've located several places where that file has been stored. Here's is one - and it too does not match what shows on the WinWorld download page, but checks out with 7zip.

    https://os.arf20.com/Windows/NT 3.51/Microsoft Windows NT 3.51 Workstation (3.51.1057.1).7z
  • ArmacadiaArmacadia
    Testing doesn't yield any errors, but there's definitely something with the ISO. One time the Setup had complained about beep.sys being corrupt, I extracted it manually with 7-Zip, compared checksums with the problematic copy, they did not match. Tried to install again and it was a different file with the same issue.
  • SomeGuySomeGuy
    Well, my local copy also has an SHA1 of fd49a828b15bf61247ffe12ded50b2d0f099253f (I don't know why some download have a longer checksum. My upload process uses SHA1 and I never got any memo that we were supposed to change it. The checksums are not quite as important now that were are using HTTPS for the downloads. It extracts without errors, so I'll update the checksum.
  • ArmacadiaArmacadia
    They are important though, as someone working in tech support I know people just tend to download files over bad connections/onto corrupt drives and wonder why nothing is working as expected. :)
    I'm now trying the Server edition where the checksum matches with what the page says, and am running into the same error.

    After some googling, this seems to be a bug in Virtual PC: https://msfn.org/board/topic/171615-problems-installing-windows-nt-351-in-virtual-pc-2007/
  • 02k-guy02k-guy
    The SHA1 of the Link I posted is same as SomeGuy results.

    And this is the SHA1 of the ISO:
    Name: en_winnt_3.51.wks.iso
    Size: 272793600 bytes (260 MiB)
    SHA1: f791d6edf5f157ef9cbe8c17aa6a613efc1104e6

    Once the file is on your drive, not much can go wrong with consistency of the ISO.

    I took a looksee with a hexer, and it's a straight-up ISO 9660 image, mastered with Microsoft CDIMAGE 2.03, no 3rd party ISO artifacts, no crap in the sectors between files, etc.

    There are too many variables concerning the environment you are working from and the environment you are attempting to install it to - to blame it on the ISO out of hand.

    The early versions of NT had a tough go even back when it was mainstream.

    Finally, regarding "BEEP.SYS". In the ISO\i386 dir, in it's compressed state, it's:
    Name: BEEP.SY_
    Size: 2122 bytes (2 KiB)
    SHA1: dadfc1407757b5a8908c81d4b1654e398fe8a73f

    Extracted/expanded, it becomes:
    Name: beep.sys
    Size: 4016 bytes (3 KiB)
    SHA1: 073bda2c719ab3e0b9540a533613bf08ddb86e90

    This is from the i386 directory, I did not check what the Alpha, MIPS, or PPC directories have.
Sign In or Register to comment.