rloew

In this case, I would patch the relevant files and burn a new CD.

I focus more on Windows 9x Applications. NTFS TRIM Programs already existed. I don't have enough documentation on NTFS to write one. You can TRIM a NTFS Partition by Zero filling it and then use the Zero TRIM Mode in my Program.

I am not aware of a NVME driver for XP. Also I have not seen a CSM based NVME Boot. Are you sure you are using NVME not SATA or AHCI?

XP SP3 does support PAE. Only support for 64-Bit RAM was dropped.

Gmail blocks all executables, even in renamed zips. I had to develop my own encoding to send my Patches to my Gmail Customers.

I have a test driver that you can use. You can reach me at rloew@hotmail.com to arrange transfer and discuss methods.

I patched the AHCIX86 Driver to be generic. It works with AMD and Intel CPUs. It has not been tested with any Ryzen boards.

Only 4Kn Internal Drives need Windows 7. These are normally used only in servers. 512e Drives require proper partitioning or formatting to be used efficiently but run just fine in XP. 512n is the format used by older Drives and does not require any special considerations.

Ten years? A few days ago I saw an article that said 4 year old computers are obsolete and should be replaced. I only have one computer that is less than 4 years old and it is the one I use least.

The name KERNELXP.DLL is used in Dibya's Extended Kernel. Either the Extended Kernel is expected, or it will conflict with the Extended kernel. I would need to know what specific APIs are being used in KERNELXP.DLL to check the Extended Kernel.

No. DLLHOOK is an User API redirector similar to KernelEx. It only works for Windows 9x. My WDMEX is the Kernel Mode equivalent. The tool the OP needs is called MODEXP. It allows you to modify the Export Table of a DLL and add space for new code. I have not put it on my Website so far. Dibya uses it to build his Extended Kernel.

I have a tool that can help with that.

Implementing 48-Bit LBA is not a particularly difficult task but there doesn't seem to be much interest. Only one person was interested in my Package for Windows 2000.

Halfway to Christmas, still only one.

I spend most of my time on XP so I can browse easily. XP is compatible with my development tools so I can stay in it while writing and compiling 9x software. I don't need to switch OS to use other software and projects that are OS independent. I switch to 98SE to test or use 9x only software, software only installed in 9x, access files in my 4TB Hard Drive, or experiment with hardware ports. Once there, I will stay until I need to browse difficult websites, access NTFS Filesystems or XP specific software.. I can also multi-boot to access DOS, 95, ME, 7, 8, or 10 as needed. Except for DOS, I use the other OSes less than once per month.

Unfortunately, I have never succeeded doing this with any Ethernet Driver so far.

You made the driver think you have a RT2800, so it installed and now initializes upon boot causing the VFAT problem. Gigabit Ethernet often causes VFAT to crash, this is why I added the /M option to my Patch. No guarantees that the Driver will actually work.

His later response suggests the latter. Installing USB Drivers while using USB Keyboards and Mice are a major headache with 9x. I haven't tried with 2K.

It is unclear if the OP's problem is during the Text-Mode Setup where no USB Drivers would be loaded, or later where @bluebolt's posts are relevant.

The Windows 2000 Installer should work with an USB Keyboard. Mine does. Make sure that USB Legacy Mode is enabled for the Keyboard in the BIOS.

How many PS/2 ports does your computer have? If two, are they both damaged or just one. How many USB ports?

The Hex 24 '$' characters are the end of string delimiter used by DOS Calls such as INT 2109.

It can be a nuisance. Between this and other problems I have had with SETUP, I no longer use it for normal Installations. When I do a long run of experiments with SETUP, I don't bother to restore my MBR until I have completed the entire set.

The Scripts rebuild the entire set of CAB Files. They cannot rebuild a single CAB or just a few CABs.

The CAB Files are linked in a sequence and have many files split between successive CABs. This makes it difficult to change one or more CABs without rebuilding all of them or using special tools.