rloew

Member
  • Content count

    1,368
  • Joined

  • Last visited

Community Reputation

53 Excellent

About rloew

Contact Methods

  • Website URL
    http://rloew1.no-ip.com

Profile Information

  • OS
    98SE
  • Country

Recent Profile Visitors

1,674 profile views
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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).
  6. WDMEX is still in development, so there are no guarantees, but updates are free. These specific Drivers do not currently work even with WDMEX or I would already have them on my Website. WDMEX can be used along with a debugger to help find a solution. Feedback is always welcome and customizations to facilitate debugging will be considered.
  7. Newer Hardware Advantages: 1. Faster CPUs with more instructions. 2. Multiple Cores. 3. Bigger and faster RAM. 4. Bigger and faster hard drives. 5. Better performance when virtualized. 6. Can be multi-booted with other OSes that can take better advantage of the above features. Disadvantages: 1. Needs my Patches to run 9x and to use bigger hard drives. 2. Needs my APIs to take advantage of bigger RAM and Multiple Cores. 3. Need to be a programmer to use those APIs or wait for me to write an App. 4. Built-In functionality becoming unusable such as Video, Audio and often Ethernet. 5. Tweaking often required. 6. Loss of legacy hardware such as Floppy, Serial Port, Parallel Port, Joystick, P/S 2 Ports, PATA support, etc. 7. Totally unusable systems for 9x are right around the corner. Some laptops are already there. If you are not a programmer, don't need extreme performance, multi-boot or virtualize, go back at least a decade and you should do just fine.
  8. Seriously. What I sell is a tool. If you buy a wrench, you still need to do "work" to use it. Of course you are welcome to try to loosen nuts with your fingers or drop forge your own wrench. Incidentally WDMEX has over 100 Functions and I keep adding more as the need arises.
  9. For the Video Card probably. There isn't a single one still available at my local Micro Center. The USB Sound and Ethernet Adapters and PCI Sound Cards are still available new. I'm not sure about new PCI Ethernet Cards.
  10. I quick formatted a 4GB Giga Bank Hard Drive with one Partition from My Computer. It produced the problem so I had not tried any other combinations. I just tried using the FORMAT Command and a "removable" drive. Same problem.
  11. In addition to the Patches already mentioned, you would probably need the following to make a useable system. 1. 9x compatible Video Card. 2. USB Sound Adapter or PCI Card. 3. USB Ethernet Adapter or PCI Card. There is a driver for modern Realtek 8111 NICs but only at 10/100 speeds.
  12. The problem occurs, as reported previously, when quick formatting a USB Drive from My Computer. There is some activity. Then it appears to trash the first Sector of the PBR. Then it hangs. Cancelling the Format produces an error and leaves the device locked out. System will not shutdown properly afterwards. I have not determined the precise nature of the problem. Reading and Writing from anywhere in my 32GB of RAM works fine. It may have to do with one of the other SCSI commands. The only solution I know of is to replace USBPORT.SYS with the Windows 2003 Version as reported earlier. USBHUB.SYS does not seem to need replacement.
  13. I ran some experiments to isolate the USB formatting problem. The problem is not in the Patches. It is in the USBPORT.SYS Driver. Using the HAL.DLL from SP1 did not solve the problem even though it supports >4GiB. Microsoft was correct about buggy Drivers being a problem with using 64-Bit RAM. Of course they did not mention that they wrote the buggy Drivers. As everyone knows by now, Microsoft's standard operating procedure is to limit functionality to avoid a problem rather than putting effort into fixing the cause. At least until up-sell time. The simple Patch may be overkill as it causes double buffering all the time, but it does not have much impact because Windows seems to use the 64-Bit memory first. Even with only 4GiB of total RAM (less than 1 GiB of 64-Bit RAM) the USB Driver was already being Double buffered.
  14. USB devices do not use VEN/DEV numbers. They use VID/PID numbers. Basic USB Audio devices should work with the built-in USB Composite Drivers.
  15. "It's about API compatibility. Some newer APIs coming from the NT family may require or return Unicode strings instead of ANSI, others may require or return different structure sizes or formats and - knowing M$ - some may even directly call code in the middle of other libraries that may not match the intended ones." I have found numerous examples of these issues while examining their code. The third one is particularly egregious and is definitely not good programming practice since they could have easily added more Exports.