rloew

I don't know about OS/2 but the others do recognize more than one Primary Partition. Microsoft even published a specific sequence they use for enumerating them as follows: 1. Active Primary Partition on each Drive. 2. All Logical Partitions in an Extended Partition on each Drive in succession. 3. All Inactive Primary Partitions on each Drive in succession.

Presumably. It is part of the Patches that I have made to IO.SYS for my TeraByte Plus Package.It is intended for use with my RFDISK Multi-Boot Partiting Tool. You don't need more than one Extended Partition to have an unlimited number of Logical Partitions. I don't know which Partitioning tools would even allow more than one.

As far as I can tell ONTRACKD.SYS is a Block Device Driver not a DDO. It translates Sector Requests to Extended INT 13 Calls. It would probably need a DDO as well if the BIOS does not support INT 13 Extensions. EZ-DRIVE is a DDO. It would be of little use to you. You can create more than 3 Logical Partitions. The limit of 4 applies to the number of Primary and Extended Partitions. One Extended Partition can contain an unlimited number of Logical Partitions. Standard DOS only recognizes one Extended Partition per Drive. FDISK allows one Primary and One Extended Partition. My RFDISK allows more. I have a Patch that allows DOS to see more than one Extended Partition as well.

The Ontrack DDO is the one that gave DDOs a bad name. It offset all Disk accesses making the Drive unreadable unless you booted through it. Windows 9x has specific code to work with Ontrack. Other DDOs, such as EZ-DRIVE and my BOOTMAN series, do not offset Disk Accesses so no Reformatting is required. I wrote my DDO a long time ago so it was a bit crude. It would have required rebuilding the Partitions above 8GB. It is not be hard to write a Partition Driver that can mount Partitions above the 8GB limit. I assume Ontrack did.

I did it with a Drive Splitting DDO but that required very specific Partitioning to work.

You could try an USB Adapter or Enclosure if you have one. If you have a duplicator dock, you could rewrite it. I would hotplug it and use tools I wrote to get RAW access and clear it.

I have. I created such situations in some of my experiments. Slave it to XP and remove the Partition. Refresh the MBR as well. Then you should be able to access it from DOS. Use the DOS FDISK to recreate the Partition. Connecting a SATA Drive can disable Windows 98 if it does not have the proper SATA support. This would not affect DOS though.

Version 5.0 of my Patch is fairly old. I sent update notices to all my customers. With more RAM and newer Hardware and Software, the /M Option is becoming more and more important. The /M Option was added in Version 6.0. E-Mail me for an update.

I am not aware of a protection Fault issue with PCI-E Cards in general. If the problem I identifed is the cause, then the Patch will fix it.

512MB Graphics Cards have proven to be problematical when used with Windows 9x. I ran some tests with a nVidia 7200GS and a nVidia 7950GT on various Motherboards to determine why. Apparently nVidia decided to change their design approach after releasing some 512MB Cards. Previously they provided access to the entire Video RAM through the Memory Mapped I/O Space. This approach unfortunately limits the amount of System RAM that can be used by 32-Bit OSes. With the later 512MB Cards they decided to Bank Memory access through a smaller MMIO Space, typically 256MB. Starting with the 8xxx series they also implemented a Memory Page Mapper similar to the MMU in the CPU. The 7200GS is an example of the earlier design. The 7950GT is an example of the later one. The 82.69 nVidia Driver does not recognize the difference between the reported amount of Video RAM and the size of the MMIO Space allocated to the Card. The Driver overwrites the MMIO Space above the Video Card's allocation. Depending upon what is in the next 256MB of MMIO Space, your Computer can crash or other Devices, such as USB, can malfunction. A few people have been lucky enough not to have anything important in this space so they have been able to use a 7950GT although they only get 256MB. Others have not been so lucky. I have developed two solutions for this problem. 1. A Patch to the 82.69 Driver to make it recognize the smaller MMIO Space. 2. A BIOS Patcher for the nVidia BIOS ROM to increase the amount of MMIO Space it claims. The first is more universal but limits the Video RAM typically to 256MB. The second provides the full 512MB Video RAM of the Card. I am preparing a Package to put on my Website.

My SATA Patch is needed for the JMicron Controller even in IDE Mode.

From http://www.mdgx.com/INF_web/destdirs.htm 24 Root of drive containing the Windows directory [usually C:\ root]

I'm using an IDE SSD on the IDE port. Does your patch handle that? Yes. I also have a TRIM Program that supports FAT32 and can be run from DOS.

My SATA Patch eliminates these issues and lets SATA Drives be recognized by Windows 9x.

My SATA Patch can handle these Controllers.

The 512MB 7200GS appears to be stable as well. I am investigating the higher 7xxx 512MB at this time.

Research in progress. No price set. Reverting Gravity will take a bit longer.

Although listed in 82.69, no one had been able to get any 8xxx series Cards to work. 512MB 7xxx series Cards above 7200 have also proved problematical.

Yes.

I downloaded Dolphin 3.0 from the link in Post #1. To remove the 406D1388 RaiseException, Patch DOLPHIN.EXE: 16B1E0 55 -> C3

The second PC should handle Windows 98 without a problem. I have a computer with that Chipset.

Windows 95, 98 or ME will NOT support the 8400GS.

Have you tried changing the USB to PS/2 Adapter?

This suggests that you have an issue that is dependent upon something else. It is possible that this may also be related to your reported need to Patch Message 25h. When your system is shutting down properly, change the sixth byte of the long Patch from 25h to 4 and see if this brings back the Shutdown problem.

Odd. I haven't seen adding the Message 4 bypass cause any problems even when it is not needed.Also, I have no idea why it would stop working if it had worked for days. Try the following: Put back the triple Patch currently shown in Post #1. If it brings back the Shutdown problem, change the second byte of the long Patch from 4 to 25h and see if that fixes it.