Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Torsten

Profile Information

  • OS
    none specified
  • Country
  1. Hi! Yes, minimalistic WinNT4 installations on primary FAT drives are quite useful! I've installed such on every computer, in 511 MB partitions with 8192 byte sectors. @ #5: I wanted to explain why I had to place the HPFS-enabled disaster recovery WinNT4 SP1 onto a HPFS drive (the file system DLLs in the maintenance WinNT4 on drive C: are purely SP6a). My idea was that there might have been beta versions of OS Loader 5.10 or similar, which still allowed to boot from HPFS, instead of having to unpack an OS Loader 5.00 from an archive onto drive C: (faster than floppy boot), for starting the HPFS-enabled WinNT4. But, the HPFS disaster occured in November 2011. The curative WinNT4 SP1 is still there, but I haven't booted it for five years or so. This topic is really much less important, compared to lacking drivers. Greetings, Torsten
  2. Thanks for compliments, Jaclaz! The wishlist contains topics collected since January 2017. It was time to ask others for suggestions. @ #3 Good to know about FileDisk alternatives! Haven't yet tested them, in particular whether they (even) support 64/ 128 head disk layouts, as required by OS/2 (FileDisk r17p3 doesn't). For the assembly of such an image, ref. http://www.bttr-software.de/forum/forum_entry.php?id=15140 , I had to use SHSUFDRV for DOS and Linux' loop devices, instead. @ #5 An appropriate loader is required to start a WinNT4 SP1 setup capable to run CHKDSK /F on HPFS drives (just in case that OS/2 CHKDSK fails) from such drive, as mentioned here http://msfn.org/board/topic/169500-chkdsk-refuses-to-check-ntfs-volume-under-windows-nt-40/?do=findComment&comment=1090430 Due to employed WinNT351 file system DLLs, such WinNT4 won't boot from NTFS 3.1. Exchanging the OS Loader according to a a particular boot (5.00 for WinNT4/HPFS, 5.10 for WinXP/NTFS) is impractical. But I encountered OS/2 CHKDSK's failure on HPFS only once, the topic thus looses significance. Philip Nienhuis' page is great! A soulmate ... Sorry that he failed to get BeOS PE working, it's installation in VirtualBox is crucial, either. If someone was interested (again, a plug :) http://web.archive.org/web/20170728222113/http://torstenk.bplaced.net/BeOS_5.0_PE.tar.xz I am using the BUPDATE.EXE/ PINBALL.BDF hack mentioned by Philip since many years. No idea how it actually works. But it reminds me that I had forgotten to lauch a seventh topic. 7.) Device drivers for a specific hardware often vary in size, depending on the Windows version they were written for. They are not cross platform-compatible, i.e. a Win2k driver won't start in WinNT4 due to lacking kernel export functions. I have no idea about different device driver models in the respective versions, but I imagine that the higher version's one may request export functions for providing additional features (as "Entry point 'PoRequestPowerIrp' not found in driver 'ntoskrnl.exe?'"), not necessarily for basic I/O tasks. The BUPDATE.EXE/ PINBALL.BDF/ BS.DLL approach shows that cross-platform patches are possible. A downgraded Win2k driver for NIC chips to support WinNT4 would be interesting, e.g. for the famous RTL8111/8168, where no WinNT4 driver exists. The latest available Realtek WinNT4 driver, for the RTL8110/ 8169 will not run with it's successor (even patched), the chips are too different. But a somehow "castrated" Win2k RTL8111 driver on WinNT4? Other candidates may be Win2k's ATAPI.SYS (for the JMB363, which is unsupported by current UniATA v0.46b6), and UDF.SYS. Kind regards, Torsten
  3. Hello Forum, I'd like to share a bunch of Windows NT 4.0-related issues where I haven't yet found satisfactory solutions: 1.) Sysinternals' FAT32NT4 v1.06 FAT32 driver http://web.archive.org/web/20070128130628/http://download.sysinternals.com:80/Files/Fat32.exe comes with CHKFAT32.EXE, which reports errors on these volumes, but cannot fix them. Worse: CHKFAT32 *crashes* when checking larger drives with many files, making this tool completely useless. ReactOS 0.4.4 contains ChkDskX v1.0.1, which is based on sources by Mark Russinovich, and was ported by Emanuele Aliberti. This binary doesn't run in WinNT4, but it's sources seem to be available. Has someone probably ported them to WinNT4? 2.) In 1995, Matrox has released a slim, efficient DPMS screen saver for use with their graphic boards ftp://ftp.matrox.com/pub/mga/scrnsaver/estar.zip . For hardware from other manufacturers, DPMS screen savers by D-System may be used, e.g. http://www.dev-labs.com/dpms/dpms14.zip . These contain some gimmicks and are much bigger, even UPXed, v0.2 is about 150 KB, eight times the size of ESTAR.SCR. I guess the latter queries the hardware ID, to limit it's usage to Matrox cards. Suggestions how to remove this vendor query (binary patch) welcome, in order to make it usable on other hardware. 3.) Bo Brantén has developed a virtual disk driver which uses files to emulate physical hard and optical disks. FileDisk Release 14 from 2006 http://www.acc.umu.se/~bosse/filedisk/filedisk-14.zip is the last which works in Windows NT 4.0. The more recent Release 17p3 can mount partitions within images http://www.acc.umu.se/~bosse/filedisk/filedisk-17p3.rar . This and later releases are build with MS C/C++ 7.0, they would require a recompile for WinNT4 compatibility. I do not have the necessary tools, e.g. Visual Studio 2005, which still creates WinNT4 binaries. Can anybody help? Alas, when used with DVD Write Now by Alexander Telyatnikov ("Alter"), http://dwn.alter.org.ua/downloads/dwn_1_5_12_sp2.rar , FileDisk ISO mounts appear "empty" in certain setups, i.e. it cannot be used simultaneously with the DWN UDF driver. 4.) I'm using the popular IO Networks v4.06 USB driver stack for WinNT4 http://ftp1.digi.com/support/driver/i4usb406.exe with v4.20 update (in an "i420usb" archive available on several sites). It works fine with mass storage devices, but not with human interface devices. According to Calvin http://nt4ref.zcm.com.au/usb.htm , IONUSB's USBHID.SYS conflicts with PS/2 keyboard and mouse drivers. I failed to get it working on legacy-free systems. Does anyone know a setup where WinNT4 operates with USB input devices? The IO Networks stack contains an Edgeport driver, for USB-to-Ethernet devices, if I got things right. I wonder about the hardware supported by this driver: only particular units, or a wider variety of generic products? The Ethernet-over-USB approach is particularily interesting for embedded systems with unsupported onboard NIC chips (e.g. RTL8111/8168), where it may be the only way to establish network connections. 5.) Windows 2000's OS Loader 5.00 is the last version which permits to boot Windows NT 4.0 from HPFS drives (by means of PINBALL.SYS). However, it cannot boot Windows XP (reports "The 'osloadfilename' parameter does not point to a valid file. \system32\ ntoskrnl.exe."), which relies on it's proper OS Loader 5.10. I'm looking for an OS Loader with both capabilities, booting from HPFS and into WinXP. Ideas welcome. 6.) For years, Stefan Weil has ported the QEMU CPU emulator to Windows, ref. http://qemu.weilnetz.de/ . V2.70 is the latest version which runs in Windows XP (dummy builds of bcrypt.dll and dwmapi.dll required by newer versions fail). None of his earlier builds works in Windows NT 4.0, nor does the alternative ftp://kolibrios.org/users/Asper/Qemu/qemu- port. Stefan used the MinGW compiler for his builds. I doubt whether the incompatibility of current builds with WinNT4 is related to missing system functions, or rather to inadequate compiler settings. Does someone have experiences with the MinGW compiler, with WinNT4 as target platform? Feedback welcome, Regards Torsten
  4. Hi all, thank you for this great thread! I found it only recently, after an indication on Bearwindows' http://bearwindows.zcm.com.au/winnt4.htm Updating Windows NT 4.0 page. I've been affected (and bothered) by the "WinNT4 cannot CHKDSK /F NTFS 3.x volumes" issue, and choose a brute force approach to overcome it: I re-formatted any affected volume with NTFS 1.2, and restored "castrated" versions of Win2k and WinXP. Is to say, I removed their native NTFS.SYS drivers, and replaced them with NTFS40.SYS from Win2k which was (originally) intended for use with WinNT4 only. NTFS.SYS in the backup directory needs to replaced as well, in order to prevent it's automated restoring. Works fine for Win2k, which perfectly boots from NTFS 1.2. WinXP, by contrast, doesn't ... had to install an additional, FAT32-formatted disk for WinXP boot. Like WinNT4 and Win2k, it now accesses NTFS 1.2 volumes without tampering them. I didn't imagine that Microsoft might ever have fixed this! If I only had known this thread earlier ... Everything is there: Michael's Mark4NTFS hack (in 2011, a friend suggested that only a few bits in NTFS 1.2's structures might be altered to make them unCHKDSKable, but he didn't know about Mike's tool, neither), Mark Russinovich's NTFSCHK (rather a complicated workaround, I think), and even an official fix. Microsoft's hotfixes 195352 and 199796 (for KB 872952) are still available under the location mentioned by Dencorso on Dec 6, 2014, in a "Service Pack 7" directory :-) Although I requested localized versions (among a total of 72 fixes for different WinNT4 flavors, and languages), the binaries are in pure english. It seems that the hotfix hasn't been truly localized. Does anyone know whether hotfixes are cumulative, i.e. whether KB 872952 fixes the earlier KB 326643 "NTFS May Not Detect When a CD or a DVD Is Removed" issue as well? As the latter also comes with a modified NTFS.SYS, it may be mutually exclusive with NTFS40.SYS if this was required by the first. (WinNT SP6a NTFS.SYS and Win2k NTFS40.SYS both read/ write up to NTFS 3.1 file systems, but the latter is more recent and a bit smaller.) KB 872952's content (autochk.exe, chkdsk.exe & fmifs.dll) reminds me of a patch which can be applied to WinNT4 SP1: with the respective WinNT351 SP5 versions of these files, WinNT4 cannot only read (by means of PINBALL.SYS) HPFS volumes, but also CHKDSK them. Helped a lot when OS/2 CHKDSK once failed to repair a damaged drive. Must not be run on HPFS volumes larger than 4 GB, as PINBALL.SYS supports only 4 GB and CHKDSK /F destroys HPFS structures on larger ones. Just as a note, presumably less interesting for most people here. As said before, great thanks for the hints in this thread! Greetings, Torsten