rloew

I have no idea if the DOS Driver for RTL8111E can share Interrupts when used in Windows. The limited Tenda Driver does appear to play nice. My SATA Patch shoiuld take care of Windows. The problems you have been seeing with EMM386 suggest that you might have your SATA 3 Controller set to AHCI mode. I am truly amazed at how poorly written BIOS AHCI Drivers are. They seem to be intended only to Boot Windows and little more.

Count me in the 1%. No Amdahls in the basement though. Too damp.

ASD appears to list most, if not all, Driver Nodes. It appears to be safe to remove entries. Look for ones with a Value of 01. These are the ones that are disabled. Delete the Entry or change the Value to 00.

The same thing happended with AOL 5.0 a while back. Same symptoms. It appears they routed me to a server that ran the old protocol just long enough to login, post the message and logout. I tried freezing the client to keep the connection open but was disconnected anyway.

USBD.SYS only needs to be copied to WINDOWS\SYSTEM32\DRIVERS. USBUI.DLL and HOTPLUG.DLL only needs to be copied to WINDOWS\SYSTEM. SYSTRAY.EXE needs to be copied to WINDOWS\SYSTEM and added to the Run List in the Registry. In some cases DBCLASS.SYS and DBFILTER.SYS may need to be copied. Merging USB.INF and USB2.INF is not a bad idea.

That wouldn't be hard to do. You can add files to the Layout and Copy INFs in the Precopy CABs. Because of the problems I have had with SETUP.EXE, I created a CD that has the first stage Install already completed. At that point it is easy to add other files to the CD and they are already present when I copy the CD to the Hard Drive.

I use a special CD that preloads all of the USB Drivers.

More than a guess.I preloaded USBD.SYS on my Z87 so I didn't see this problem but I was missing SYSTRAY and HOTPLUG which is also missing from the USB2.INF File.

I remember doing something like this on a system many years ago. The delay is not unusual. DHCP and other activities can take a while. If the Computer is not connected to anything, it can take quite a bit longer before it gives up. On my Z87, there are no USB 1.1 Controllers reported, only USB 2. It appears that the USB 2 Controller and Driver can handle USB 1.1 Devices. Yes. I am using the standard Windows 98SE USB 1.1 Drivers, the Windows ME USB Storage Drivers and the USB 2 Drivers from NUSB 3.3. I'm not sure what is causing your problem. I have seen quite a bit of weirdness with Intel Motherboards especially with AMI BIOSes. I tried my 8400GS Card after every Patch I developed. It did not help. The architecture is just too different.

That is the correct Version of RTLNIC.SYS. I did have to add the /M Option to my RAM Limitation Patch and even the SPLIT8MB program on my Z87 System. You can try my Free Demo RAM Limitation Patch with the /M Option to test. I have used it with both the RTL8111D and RTL8111E. If you are sure the SATA Drive is accessed via Ports 1F0-1F7 then it is in Legacy Mode.

LoneCrusader is referring to the Patches I developed to correct problems that occur with 512MB 7xxx series cards. I already tried modifying the RTENIC.SYS file but have not yet found the version check code, if any. The Tenda TEL9901G driver on their website appears to have been intended to support the RTL8111 but was abandoned at some point. The INF file has an entry for the RTL8111 but it is commented out. You will need to verify that the SATA3 Ports are in Legacy Mode not Native Mode.

The standard Windows 9x drivers don't support RTL8111D or RTL8111E. I found a driver that was intended for another product that works but throws a warning on every boot and only runs at 100MB not 1GB. AHCI Mode changes the Class Code so Windows 9x will not recognize it. It only works because you are in compatability mode. I'm not sure what is different between SATA3 and SATA2. Maybe one is in legacy Mode and the other in Native Mode.

Okay, so call me stupid but I've had very little to no experience in USB audio devices. Is that something that just plugs into the USB port, runs a driver, and then just works? That would be very useful in something like for example, a laptop that has nothing but high definition audio codecs.Yes, for the basic ones at least. A more complex one may not be compatabile. Check before you buy.

USB Audio generally works well with Windows 98SE. Even many of the new Devices are compatable.

No doubt about that. I have been testing a number of Intel Branded Motherboards with AMI BIOSes. Some of the BIOSes do a CHS Geometry test on each Drive. If the Drive does not show 255 Head Geometry, weirdness ensues. Either the Drive is switched to CHS Mode, limiting it to 32GB, or the BIOS crashes and you never even get to the initial Logo screen. A blank cursor after the BIOS Screen suggests the former. If fixing the Boot Sequence doesn't work, then you will have to erase the Drive and repartition the Drive in another Computer. This problem is NOT limited to SATA.

I have been using the HP Network Printer Wizard I got directed to by HP Tech Support shortly before they pulled the plug. It is called HPJSI.EXE and is Version 5.00.009.0

SATA Cards are generally not recognized by Windows 9x so they run in compastability mode and you can install 9x and provide the Driver later assuming there is one. Motherboard SATA Controllers are recognized incorrectly by the default Windows software so you are likely to crash before you can provide a Driver assuming one even exists. Most Motherboard SATA Controllers have no available 9x Drivers. Inserting the Driver into the Setup process, or an even more complicated procedure, is mandatory for the few that do.

That is possible. If the X700, X800, or X850 doesn't crash when installed with the Standard VGA Driver, write down the Memory Range Resources used and post them.

I have updated my Website. The Test Program is now on my Website.

The Patch is ready. I plan to update my website over the weekend. There will be a free test program that you can use to test your system before purchase. I haven't tested the BIOS Patch in XP as I have yet to put the one problematic card (7950GT) in a system with XP. I only have Windows 10 in a Laptop, so I cannot test that at this time. I did a BIOS Patch on a 256MB PCI 6200GS that claimed 512MB, the reverse of the 7950GT, and it works in XP. The main impact on Windows XP would be the maximum amount of 32-Bit RAM available. 64-Bit systems would be unaffected as the Memory is not lost but hoisted up into the 64-Bit space. Incidentally, the main Patch is for the nVidia Driver not the OS. I do include an OS Patch that fixes a separate problem that I have seen in some Intel branded Motherboards.

I've written programs to transfer files and run remote shells between any version of Windows and/or AmigaDOS. They are much more reliable then SMB. I recently added encryption to the Windows version of these programs for secure remote communication.

I'm afraid not. 8xxx and later cards use significantly different interfaces than the earlier ones. My Patches are mainly for 6xxx and 7xxx 512MB Cards. At this point I don't think there are any compatable cards available at my local retailers at all.

It should work with any IO.SYS 7 or unpacked IO.SYS 8. So Windows 95 and 98FE should be covered.

The link to the Patch is at the bottom of this page: http://www.msfn.org/board/topic/118119-patched-iosys-for-9xme/page-7 It appears that the file I attached PATCHPAR.ZIP is no longer available.

It doesn't use the logical partition as a FAT partition. It adds the offsets of the partitions together to produce an entirely spurious partition. This bug is well known. I posted a fix on this forum for it years ago.