Search the Community
Showing results for tags 'Windows NT 4.0'.
Found 5 results
-
Majority of people downgrade their VMware version to 5.0 for the legacy sound driver,Which is the SB128. But you also lose some features that were introduced in newer versions. This is a way to install the current sound driver, Which is the Ensoniq ES1370. Sound Driver for the ES1370. Supported: Windows 95/98/Me 1.Download and drag and drop the driver to your 9x VM. 1b.If that dosen't work, or if you do not want to install VMware Tools,Create a ISO/CD using a program such as ImgBurn/UltraISO etc with the driver in it. 2. Open and install the driver. It should be quick. If everything goes well,You will see a found new hardware dialog with the ES1370. 2b. On 95/98, You may see a 'Please insert this disk' error. It is ok to close that message. 3.Reboot and enjoy! If it dosen't work? If it dosen't work, Check your temp folder (Which can be accesed with %temp% in the run box) and there may be a folder with the drivers. Copy this folder to your desktop and try installing it using the 'Add new hardware wizard' control panel item. PROS: Full compabitlity with VMware, Possibly better sound. CONS: No MIDI support. I can't remember if it also dosen't work on SB128. Annoying message about no MIDI support. It's a dialog box at logon. Windows NT 4 also has a version of this driver. NT 4/Alternate CD Version In theory the installation process is close to the 9x driver. Comment below if there's any problems. -Nerdulater -
Note: VMware Workstation 16 used. Most people say that Windows NT 4 has a limit of 4GB and it is impossible to exceed that limit, However this can be exceeded. You will need: Windows NT 4 (For obvious reasons) Service Pack 6 (High Encryption required for server) A Partitioning/Hard disk utility (Such as Gparted) 1 (If you are doing a clean install) 1. Start installing Windows NT 4. Once at the partitioning screen create a partition. (4095 MB is the maximum you are allowed to create for now) 1b. Format the partition as NTFS. FAT does not work. 2. Finish installing NT 4. 2b. Don't worry if you see a conversion screen, It's normal. 3. Once installed, Install Service Pack 6. (Again, Make sure it's high encryption (128) if your using NT 4 Server) 3b. If you do not install Service Pack 6, NT will fail to boot after partitioning. 4. After installation, Install or boot a partition/hard disk utility (Note: Not all of them may work) (You can even use a Windows Vista and above CD\DVD\ISO) 5. Once in, change the partition size to however you like! (I used 20GB) 5b. If you use a Windows Vista and above CD\DVD\ISO, Use the extend option (Which is at the choose partition screen) to change the size. 5c. If you get error code 0xE0000100, you should consider changing to IDE, or load your SCSI Drivers. (Which for VMware, is in the VMware Tools CD) 5d. If you change to IDE, It should be ok to switch back after 6. After all of that, It should all be done! If you already have installed NT 4, all you have to do is make sure you have converted your partition to NTFS. Some FAT/FAT32 recovery/antivirus software may also not work, However this is kind of obvious. Tell me any question below and I will try to respond. -Nerdulater
-
I'm trying to setup mirroring on my Windows NT 4 server with SCSI drives. I plugged in a new drive and booted. For some reason it put the new, blank drive as drive 0. How can I set which drive is Drive 0? If I use jumper will that screw up the mirroring? -
Hi, I have an old NT4 server with mirrored SCSI drives. I got a message that the mirroring had failed. I accidentally destroyed the boot partition on one of the drives while trying to fix it. The drive that will boot is old and out of date. I do have a series of up-to-date tape backup. (The booting drive does not have drivers for the tape drive and I'm having trouble finding drivers for it.) Is it possible to fix the boot partition on the up-to-date drive? If not, how would you recommend I recover the system because it is critical for my business? Thanks
-
Has anyone run Windows NT 3.51, Windows NT 4.0 or Windows 2000 under Bochs with networking support successfully? Well, the latest SVN revision is 2014-01-05 and according to therock247uk from the Vogons DOSBox forums, Bochs has working Slirp support on Windows. So far, in the official release of Bochs 2.6.2, there is no networking support. Even with WinPcap installed, networking hasn't been working correctly for years, niclist.exe network detection remains broken and Slirp doesn't work in the official Windows release. Furthermore, if I try to enable Slirp support in the Windows NT 4.0 test VM on Bochs in the settings.bxrc config file, this log with error messages get displayed: Has anyone compiled Bochs 2.6.2 with Slirp support using the SVN 2014-01-05 revision? If so, I would like to grab a copy of the complied version and try to get networking working. Also, the lowest processor that Bochs will be able to emulate is a Pentium MMX. I would also love to see Bochs compiled to run either on a 80386, 80486 or original Pentium. Windows NT 3.51 and Windows NT 4.0 ran on these processors very well. If you would like more information on this, please let me know.
