Search the Community
Showing results for tags 'nt 4.0'.
Found 4 results
-
Precursor: *SKIP IF UNINTERESTED* I have a multibooted computer with 13+ entries in the bootloader. Currently, they go as follows: Win 11, 10, 8.1, 7, Vista, XP, 2K, NT 4.0, ME, 98 SE, 95, 3.1, and an Ubuntu install. All of them boot correctly (now after much disarray), and are neatly put into a single boot menu running without metro UI but on the modern BCD framework. I use 5 real mode boot sectors for ME, 98 SE, 95, 3.1, and Ubuntu using modified versions of generated files from easy bcd (based on grub4dos 0.4.6a). For NT 4.0, 2K, and XP, I also use Easy BCD (this time unmodified) to boot into them. Each operating system works fine. All operating systems above 2K have fully fledged drivers for everything, the base board is an IPIBL-LB (random HP board) with 4 drives + a CD drive. *** SKIP TO: Here's the problem: If I follow these steps, things go wrong: Boot into NT 4.0 (no issues) Restart (no issues) Boot into Windows 7 (no issues*) Once into Windows 7, after fully started, Windows 7 (but not any other operating system [ex 8.1]) will become super sluggish and slow. All drives are accessible except for the ones accessed by NT 4.0 during its boot (any time in the past, even hundreds of power cycles ago), mainly NT 4.0 itself as well as Vista and 2K. The FAT (non NTFS) drives accessed by NT 4.0 remain accessible, but NTFS drives accessed become unreadable/uninitialized in only windows 7. Trying to start a disk check on those volumes fails, and the UAC prompt takes forever to come up anyway. The system is unable to shutdown too. The current only way to fix this is to boot into another operating system and disk check anything accessed by NT 4.0. Here's what I want: Windows 7 can access all drives and not be sluggish after booting into NT 4.0 any time in the past Windows 7 can still see all partitions on all drives Here's what I don't care about: NT 4.0 not being able to see any other partition (actually ideally it shouldn't be able to) Here's my idea: NT 4.0 does not have disk drivers. It sees the drives (500+ GB) as 131 GB (No lba 48 support) - I have a disk driver I could install, but doing so seems redundant since it will only be a nightmare to reletter each drive and fix the USB drivers as well as making more partitions accessible from NT to further break 7 - If I could maybe get Vista to unletter from NT 4.0 and install NT on FAT, then it would maybe fix the issue? However I can't unletter Vista. I would also need guidance on installing NT 4.0 on FAT. Other than that I'm clueless Other info: I have removed all drive letters from NT 4.0 besides itself (now C:) and Vista (Z:) (it won't let me remove Vista as "boot drives MUST have letters" [this makes me confused]) NT 4.0 can only see 2 drives (technically 3 but it doesn't read the third), of which the picture has the layout. The full disk manager layout from 8.1 can be seen as well. This is NT 4.0 built 1381 SP6 I would really appreciate some guidance! I'm lost. Genuinely no idea where to start or how one or two partitions ruins 7 completely. Clueless, however much I might know. Sincerely, RU-B **Don't want any "Give up" vibes please**
-
Hello, everyone. I recently did a fresh install of Microsoft Windows NT 4.0 Workstation inside Virtual PC 2004, allocated 64 MB memory to the VM, created a fixed 4 GB hard disk (4,095 MB) image, partitioned and formatted the hard disk as NTFS v1.2 file system. Windows NT 4.0 installed without a hitch. However, when I used a disk mounting utility called IMDisk to view the contents of the partition formatted as NTFS, Windows 2000, the host OS upgraded the NTFS partition to version 3.0. After I unmounted the hard disk image, I powered up the Windows NT 4.0 Workstation VM again and when I attempted to run the CHKDSK command, I get this error message: I looked at this page regarding Windows NT 4.0 CHKDSK refusing to check NTFS v3.0/v3.1 volumes (KB196707) and it wasn't very much of a help at all. What baffles me is that I looked at this forum thread, NT4 NTFS Versions by nt4-ever on 2007-07-19 and it mentioned hacks and workarounds including NTFSCHK, a utility to run the Windows 2000 version of CHKDSK from Windows NT 4.0 and another utility called Mark4NTFS, a Windows NT 4.0 utility to revert the partition from NTFS v3.0 down to NTFS v1.2. I tried to download a utility called Mark4NTFS.zip and found that the site that was hosted on it was gone! There was also mention of the KB872952 hotfix, but I can't seem to find the hotfix available for download at all either. Are there any good utilities or disk hex editing hacks that will help fix this problem? I know that the consequences are that every time I attempt to mount a NTFS v1.2 formatted volume with IMDisk under Windows 2000 or Windows XP, it will upgrade the version of the file system on the mounted hard disk image. Let me know what you can come up with. -
I seem to be unable to create a "fully" working multiboot/install DVD using the "Create Windows 98/ME/NT/2K/XP/2003 all in one installation DVD" I replaced Windows 2003 with Windows 95 (Version C) as I planned to put 2003 on a different DVD with newer versions of windows on it. When I try booting any of the disk I put on there they show an error about not being able to find the setup/installation files. For some reason Win 95 - ME will still work if I type "setup" (D:\WinME\setup for Windows ME installer) and continue normally. Windows NT 4.0 doesn't boot at all and when I attempt editing the iso and add the I386 for WinNT to the root folder it will boot but BSDO when setup starts. Windows 2000 and XP both boot but fail to start at all giving me a "insert Win 2000/XP disk into drive A:" error and I can't find a way to fix that at all. I use UltraEdit (Version 22.0.0.66) and Oracle VirtualBox (Version 4.3.30 r 10610 64-Bit) on Windows 10 Tech Preview 64-Bit (Build 10270) to build/test the ISO. Message me for images/files if you need them. If anyone has any ideas please help or suggest another method of combining these disk to a DVD Iso or USB drive. Guide I used: http://www.magiciso.com/tutorials/miso-create-multi-os-cd.htm Link to images of the errors/iso: https://drive.google.com/open?id=0B9uFvN9K3tPWfnpmTVJ1VnkzdThQQTNjZ1NuUE53WFdZdk1jQWFTVUtocGZYY3E5Z0lTMms&authuser=0 P.S.: If I posted this to the wrong forum section, just feel free to tell me where it should be or move it there if possible. -
Okay, when I installed Windows NT 4.0 Workstation under VirtualPC, the 256 colour icons displayed on the desktop remained intact. With TweakUI installed, you could remove the annoying arrows from desktop shortcut icons and with the Desktop Themes from the Windows NT 4.0 Resource Kit, you had the ability to change desktop icons. However, installing Internet Explorer 4.01 SP2 with Active Desktop support broke the ability to add or remove the arrows on the desktop shortcut icons and eventually defeated the ability to use Desktop Themes to properly change desktop icons. To make matters worse, the security update KB313829 even broke the ability to properly remove annoying arrows from Desktop shortcut icons! While this is not a issue under all editions of Windows 95, I bet that this affected users running Windows NT 4.0 SP6a, Windows 98 and Windows Millennium Edition. Additionally after the updates to Windows 95 have been installed, you could always install Microsoft Plus! for Windows 95 to get the 256 colour desktop icons. The current version of SHELL32.DLL installed in the C:\WINDOWS\System32 directory is 4.72.3812.600 with the date stamp of 2001-12-06 14:23:20. I checked this page regarding the patched SHELL32.DLL bug and it doesn't seem to be too much of a help here. And the SHELL32.DLL fix is only designed for Windows 98 and may eventually not work correctly under Windows NT 4.0 as the size of the file is smaller. Is there a way to fix this complicated issue without having to re-install Windows NT 4.0? I know for sure that simply only removing the arrows is not going to be enough here.
