[RFMaster]

RFMaster, I hope that you and your loved ones are safe from the flooding in Serbia.

Thank you for your concern, i'm good because i'm in an area that is not devastated by flooding.

[Steven W]

Method 1 = The way I did it?
Method 2 = Use German VMM32.vxd?



Good, I'm glad you're safe!

[RFMaster]

>Method 1 = The way I did it?
>Method 2 = Use German VMM32.vxd?
>

Method 1 = The way you did it.
Method 2 = The way i did it. - this is new (patched vmm32.vxd without need to rebuild it )
Method 3 = Use German VMM32.vxd?

I'm working on a new patcher...

[Steven W]

We'd be lost with out you, bro!

[TmEE]

I am out for few weeks and all kind of new and awesome pops up

[PROBLEMCHYLD]

@ RFMaster

The new method by patching the VMM32.VXD is the best because then we don't need a patched VCACHE.VXD or VMM.VXD. The only reason I was asking you patch VMM.VXD 4.10.2226, is because I thought thats what the VMM32.VXD patch was doing to the VMM.VXD inside of VMM32.VXD from the Win98 CD. Thanks again, you are awesome

[PROBLEMCHYLD]

I also just realize that even though M$ created the VMM.VXD 4.10.2226 hotfix, it is useless to patch because the ram lies within VMM32.VXD file and not the hotfix. As long as VMM32.VXD is patch, then the other VXDs don't matter, patched or not. We can't use the hotfix as a standalone solution therefore its pointless to have patch, same goes for the Vcache patch.

[Steven W]

@PROBLEMCHYLD I get your saying but, not at all pointless if your willing to "do it yourself" (with RFMaster's patches).

[Steven W]

Who knows too, perhaps and updater/patcher could be accomplished.

[RFMaster]

...it is useless to patch because the ram lies within VMM32.VXD file and not the hotfix. As long as VMM32.VXD is patch, then the other VXDs don't matter, patched or not. ...

Watch what happens when you put not patched VMM.VXD from qfe288430. System is frozen ->

qfe288430.gif (2.4 MiB) Viewed 7925 times