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

Windows NT 3.x 3.5

SystemSystem
edited December 2019 in Product Comments

imageWindows NT 3.x 3.5

WinWorld is an online museum dedicated to providing free and open access to one of the largest archives of abandonware software and information on the web.

Read the full story here


Comments

  • kk777kk777

    please upload korean windows nt 3.5 workstation and server

  • win32win32

    The source code of build 782 has leaked. I'm not going to link directly to it due to its sensitive nature but it's on an "archive" site.

  • MateoHidegMateoHideg

    @win32 said:
    The source code of build 782 has leaked. I'm not going to link directly to it due to its sensitive nature but it's on an "archive" site.

    Yup, but the problem is compiling it.

  • Yuds2003Yuds2003
    It was determined that build 854 is a very early build of 3.51, because of its features that are similar to build 896 (not available here). This happened after the leak of build 896.
  • DeFactoDeFacto
    This was further confirmed when build 889 leaked with the same feature set.
  • win32win32
    Apparently, NT 3.5 PPC is not supposed to exist:

    https://web.archive.org/web/20100604082534/http://www.winsupersite.com/reviews/winserver2k3_gold1.asp

    "Windows NT 3.51 was dubbed the Power PC release, because it was designed around the Power PC version of NT, which was originally supposed to ship in version 3.5. But IBM constantly delayed the Power PC chips, necessitating a separate NT release. "NT 3.51 was a very unrewarding release," Thompson said, contrasting it with Daytona. "After Daytona was completed, we basically sat around for 9 months fixing bugs while we waited for IBM to finish the Power PC hardware. But because of this, NT 3.51 was a solid release, and our customers loved it." NT 3.51 eventually shipped in May 1995."
  • DeFactoDeFacto
    Well, the IBM OEM release sure seems to exist.
  • Greenpickles987Greenpickles987
    wanted: floppy disks


  • ScaniaKing326ScaniaKing326
    NT 3.5 Server doesnt have a floppy disk so medium is unusable
  • KeishiKeishi
    You could always create your own for installation.
    Real issue with 3.5 Server ISO is that it also has modified files SETUP.IN_ and INITIAL.IN_ like it was recently discussed on NT 3.1 page. Is there any chance to have unmodified ISO?
  • helloisthispizzahuthelloisthispizzahut
    How do I install the Power PC version in QEMU?
  • thrsded2333thrsded2333
    bootcamp should have existed early because windows was also on the PPC platform. (lol)
  • Then_What58Then_What58
    edited January 2024
    doesn't work!
    says "setup is unable to locate the hard drive" even though its partitioned and formatted with ms-dos 6.22 floppy
    (3.50.807)
    but it happens only on 0:0
    on 1:0 it gives a bsod with kmode exception not handled
  • jonirobjonirob
    @Then_What58

    It works fine for me (in 86Box).


  • MrBetaSebiMrBetaSebi
    edited May 2024
    For those who have issues installing Microsoft Windows NT 3.50 Workstation 3.50.807:
    Firstly, don't try it via the boot floppies offered. They don't work (gives an error regarding the search of the hard drive failing)
    Instead, you need to install MS-DOS 6.22, then get the MSCDEX drive so that MS-DOS can detect CD-ROMs and then go to the i386 directory in the CD-ROM and run winnt.exe. Then make 3 blank 1.44 MB floppies and name them as setup says and insert them one by one in the way that setup specifies (typically from 3 to 1). Then try to boot with the floppies created.
    If it doesn't work, repeat the process until you arrive at i386 (the drive can be anything but it is mostly D or E) . Here, you can run winnt.exe /b instead to opt for a floppyless installation.
    This was tested in 86Box so I can't guarantee that it will be working, especially on other software (VirtualBox, VMware, PCEm, etc.) or with a different 86Box configuration.
  • thrsded2333thrsded2333
    edited August 2024
    when i used a msdos live floppy that used msdos 6.22 with cd rom support. it worked and i was able to install it (VBOX).
  • BishopBishop
    Windows NT at startup prompts you to press CTRL+ALT+DEL, but this causes the host system's Task Manager to open. How can this be solved?
  • 02k-guy02k-guy
    "Windows NT at startup prompts you to press CTRL+ALT+DEL, but this causes the host system's Task Manager to open. How can this be solved?"

    This is expected behavior. Never thought about circumventing it. Provides login security.
    Looking around the web, this caught my eye:
    https://green.cloud/docs/how-to-disable-ctrl-ezd_plus-alt-ezd_plus-delete-requirement-on-windows/

    "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
    You should see a DWORD (32-bit) entry named DisableCAD in the right pane. Double-click it and change its value from 0 to 1 -> click OK to save it."

  • BishopBishop
    @02k-guy Thank you. The problem is that to edit the registry you have to enter the system first.
  • 02k-guy02k-guy
    "Thank you. The problem is that to edit the registry you have to enter the system first."

    So, do that.

    Let me put it differently: what happens when YOU press c/a/d ?
  • BishopBishop
    @02k-guy The task manager of the host system opens. The guest system does not detect keystrokes.
  • 02k-guy02k-guy
    edited February 1
    "The task manager of the host system opens. The guest system does not detect keystrokes."

    Oh, not real hardware, but virtual.

    All I can tell you is that IF you enter the VM, then the keystrokes should affect only the VM. Otherwise, none of us would ever be able to use ANY OS in a VM, kapish?
  • SomeGuySomeGuy
    Read the manual for your VM or emulator. It should have a way to send "ctrl-alt-delete" to the guest OS, but they all do it differently.
  • 02k-guy02k-guy
    edited February 1
    "Read the manual for your VM or emulator." Words to win by.

    EDIT: good tut on installing NT 3.1 on VMWare. And it gets plus -points for mentioning WinWorld.


    I have only ever used VMWare for NT 3.1 and higher, and Win98 and above.
    My recollection is that as soon as I moved the mouse into the VM, all keystrokes went to the VM.

  • BishopBishop
    @SomeGuy & @02k-guy You are right. On Dosbox-x there are the special key combinations to send to the guest system: Main ---> Send special key ---> Send Ctrl+Alt+Del
  • 02k-guy02k-guy
    edited February 2
    Alrighty then! For others reading this in some future time:
    https://dosbox-x.com/wiki/DOSBox‐X’s-Drop‐Down-Menus

  • SlashNetSlashNet
    3.50.800.1 - what a strange build number. Isn't it 3.50.807?
Sign In or Register to comment.