rloew

What's going to change in 2020? 1. You will probably need a 2160p monitor. 2. RAM Patches still won't be free. 3. Browsers will perform even worse. 4. UEFI will be even more pervasive. 5. Microsoft is going to care even less. USB 3 has proven difficult to debug so no guarantees there. I have no opinion on NVMe as I have no hardware, so it is a maybe.

I don't think GCDROM will work with most SATA Adapters. I had to modify GCDROM to support a larger range of Devices to use my SATA Adapter.

I'm not sure that would be considered an exception. The Front Panel Module probably contains an amplifier. I also said "may" not be enough for headphones. Some do fine, others are kind of weak. Unless explicitly specified for Headphones, there are no guarantees.

Sound cards don't normally provide enough power for Speakers and may not even be enough for Headphones. They are intended for use with external amplifiers. That is why the Jacks are labelled "Line Out" rather then "Speaker".

I found that most of the official updates want to restart the system but it is not necessary to restart in between them more than once. I bundled my update package into two parts. I can run the first part, reboot, then run the second part and reboot to finish.

Running MSCDEX from the CONFIG.SYS File requires the use of the INSTALL or INSTALLHIGH Command, not LH. The LH Command can only be used in Batch Files such as AUTOEXEC.BAT. Real Mode CD/DVD Drivers can be used but are not needed, nor recommended, unless the Protected Mode Windows Driver is not working.

As I said before, 40000 is NOT OK. If you use a value that is too low, Windows will ignore it and keep the setting at 819200 (800MiB) which is too high.

I said the minimum MaxFileCache is 1/24th of the RAM, not 1/25th. For 1GiB of RAM that would be MaxPhysPage=43691. Neither 4300 nor 40000 would be enough.

I have 2 AM3+ Motherboards running Windows 98SE. There are no drivers for the built-in Audio or Video. There is an Ethernet Driver but it only works at 10/100Mb and puts up an error message on every boot. A number of my Patches are needed to support Windows 9x. So far I have only seen a couple of Laptops that are truly incompatable with Windows 9x. The 7950GT is the most powerful GPU I know of. The 7950 GX2 is technically more powerful but Windows 9x will only use one GPU so it will act the same. The GX2 may be of some value in a dual boot system with XP or later.

Windows 95 requires the FIX95CPU Patches to run on fast processors. It is freely available. The best way to answer the other questions is to search for an user manual for the specific model of Computer. The boot options may be described as Hard Disk Priority settings.

Using Hot Swap Trays for this purpose creates a lot of wear and tear and is overkill. You can usually switch Boot Drives in the BIOS. There are also Multi-boot methods to select the Boot Drive or to boot all three OSes from a single larger Drive. i have written tools that can do this either way. You will need my RAM Limitation Patch to use more than 1GiB of RAM in Windows 95 and 98. Using a Hard Disk larger than 137GB requires another Patch for Windows 95 and 98.

IE is not a Detection Manager Option, nor is IP. The correct way of combining the two options is as follows: SETUP /IP /p i

Vcache is a cache for data read off of a Hard Drive. This allows the system to reread data from RAM rather than having to reread the data from the Disk. It speeds up Disk accesses. It is definitely not for low RAM systems. Although the vcache is managed dynamically to avoid interfering with other users of RAM, the System Arena address space reservation is fixed. The default is to map up to 800MiB of RAM for vcache when there is more RAM. This causes the System Arena to shrink to unacceptable levels. The maximum vcache depends somewhat on configuration but 512MiB is OK in most instances. This is the default I use in my RAM Limitation Patch. Some people suggest 384MiB. You may want to go lower if you do a lot of writing to USB sticks as it will smooth out the transfers. The minimum Windows allows is 1/24 times the total RAM, so for 1GiB of RAM, I wouldn't go below 50MiB. I know of no reason to set MinFileCache.

Setting MaxFileCache to 0 does not cause an error. It is simply ignored. This leaves you at risk for problems when using a lot of RAM.

There are a lot more missing functions in the latest iperf3 version. I already implemented AttachConsole in my Wrapper Libraries but there still were many others missing.

Those settings will not work. You cannot set MaxFileCache to 0.

With 1GiB of RAM you don't get the early "not enough memory" crash that occurs with more RAM. But, you are still subject to crashing due to System Arena starvation because of the over aggressive File Cache. At a minimum you need to add the MaxFileCache Workaround to the SYSTEM.INI File. The Memory Address shown above is a garbage address usually resulting from a Stack Fault or corrupted Pointer.

Code 2 indicates an INF Problem, not the Driver itself.

My Catalog is for products that I think would be of general interest. It is by no means comprehensive. I had not identified enough applications for WDMEX to put it in the Catalog. If Mercury127's work opens up opportunities for it, I will add it to the Catalog. In any case, it is available by name.

I have observed a problem with GParted that it will set the Partition Types of some Primary Partitions to CHS values rather than LBA values even when above the 8GB limit for CHS. New Operating Systems don't seem to care. DOS and 9x definitely do. XP i'm not sure. It is possible to create Primary and Logical Partitions that meet both the Cylinder and 1MB alignments. I already have done so for my Windows 10 experiments.

The "unofficial" 82.69 Package is a mixture of different versions of "official" nVidia software. The Kernel Mode Drivers and a few other files are official 82.69 Files. Most of the other executables are official 82.16 Files. One is an official 77.72 File. The .XML and .NVU text files are compacted versions of the 82.69 Versions. The .INF File is substantially rewritten.

When I ran my experiments, I revised the INF Files as needed to make them 9x compatible, so that was not an issue. ME has a few more Functions than 98SE but otherwise is built more like 9x than 2K. My WDMEX completely bridges the gap between 98SE and ME but still hasn't solved the problem.

256MB vs. 512MB is not important for Video playback. I didn't even see much difference in 3DMARK until I went down to 64MB using a 7950GT. I have a 6200 PCI Card. It is definitely not adequate for 1080 or even 720 in full screen mode. AGP would be faster. The 7200GS will play 1080 fine in 9x or XP. In Windows 10, even the 7200 is not enough.

Some 512MB nVidia Cards only Allocate 256MB of PCI space and use Memory banking to access the upper half. This causes a problem with the 9x Drivers. My nVidia Patch Package has two options. One is to patch the Driver to only report the less of the two sizes so that the upper half of Video RAM is ignored. The other is a Patch to the Video Card BIOS to enable the full 512MB to be accessed through the PCI Bus. With the 8400, you will have no Driver support so you will by default get the standard VGA Driver which only supports 640x480x4 Video. VBEMP may give you more resolution but does not provide acceleration and typically crashes when opening a console windows such as a DOS Box. 768MB of RAM is not a problem with any nVidia Card, even 512MB ones. Any problem would be due to the issues above. The 512MB 7200GS for example would work fine. I'm not sure about the 6800. You can download the free NVCHECK Program from my Website to see if you need my Patch.

The nVidia 8 series uses a newer architecture. There is no known driver for 9x that supports it properly, Patch or no Patch. The RAM limitation, 1.15 GB without my Patch, does not include Video RAM. You can have 1GB of RAM and a 512MB Video Card. Only users of my RAM Limitation Patch see a reduction of usable RAM with a large Video Card due to the limit of 4GiB - 2x(Video Card RAM).