[PROBLEMCHYLD]

I finally understand what RFMaster is saying

1) You can use his patcher to patch VMM32.VXD as a solution.
2) You can use Xeno86 VCACHE.VXD 4.10.2223 as a solution.
3) You can use 1) and 2) together as a solution.
4) Patched VMM.VXD 4.10.2226 is only needed on laptops. You can use 1) 2) and 4) together as a solution
5) You can combine all the solutions above and have a working system. I just did it and rebuit my VMM32.VXD.

To some it might be overkill, and to others it might be extra cushion.
Because I don't have 4GB of ram, I really can't say which is the best method, so I combined them all just to be safe.

Have a fucked up day!

Just kidding

[RFMaster]

^PROBLEMCHYLD
>I finally understand what RFMaster is saying
>1) You can use his patcher to patch VMM32.VXD as a solution.
>2) You can use Xeno86 VCACHE.VXD 4.10.2223 as a solution.

No you still don't understand!

->1) You must patch the vmm32.vxd from winsys folder, but you can do it partially or fully! If you do it partially you can do it in a 5 diferent ways.
First way is to just partially patch vmm32.vxd & vcache (just like german did) in this case you must have patched vmm.vxd in your winsysvmm32 folder.

Second way is to patch just vmm32 without patching vcache in this case you must use you must have patched vcache in your winsysvmm32 folder!

Third way is to patch vmm32 and vcache, in this case you don't need to have patched vcache.vxd or vmm.vxd in your winsysvmm32 folder!

The fourth way is to patch vmm32 and vcache but without rebuilding, in this case you also don't need to have patched vcache.vxd or vmm.vxd in your winsysvmm32 folder!

The fifth way is: if you install Q288430 in this case new vmm.vxd will be installed in your sysvmm32 folder. So, then you need to patch that file too because
patched part of patched vmm32.vxd will be overrided at startup and then patch applied to vmm32.vxd will have no effect if vmm.vxd isn't patched too.

->2) No! It is a solution only if it is in combinaton with patched vmm32.vxd!

I'm so fucking tired!

[PROBLEMCHYLD]

I still don't understand. maybe I need to get drunk. This is what I did

I took the original VMM32.VXD and patched it with RFMaster's patch.
I took Xeno86 VCACHE.VXD 4.10.2223 added it to the patched VMM32.VXD
I took RFMaster's patched VMM.VXD 4.10.2226 and added it to the patched VMM32.VXD.

Now I have a rebuilt VMM32.VXD with all the patches inside it. Can anyone tell me what have I missed here?

[RFMaster]

You did everything right, except this ->

I took RFMaster's patched VMM.VXD 4.10.2226 and added it to the patched VMM32.VXD.

That damn thing is a special case! And therefore, that damn thing(patched VMM.VXD 4.10.2226) needs to be
placed in folder winsysvmm32

It can not be integrated in vmm32.vxd because it will freeze the system at startup.

[Steven W]

Would that statement be true if you were installing on a "clean" system with less than 1 GB RAM and not patching any files?

I hope that makes sense. In other words, is VMM.VXD 4.10.2226 by itself a "special case" and can't/shouldn't be built into VMM32.vxd even on a system not being patched for more than 1 GB?

[PROBLEMCHYLD]

If you had explained this damn shit the 1st time lol. Thanks again we really appreciate it. I respect your aggressiveness. Now I'm gonna go damn eat. Sarcasm.

[Steven W]

PROBLEMCHYLD, I understand you're being sarcastic, but do realize that there's a lot of nuances with this files and many ways to go about this. I wasn't trying to be rude or obtuse when I was saying 'patience' either, I reread some of my posts and now see how someone could take them that way -- I hope you didn't take them that way.

Anyway, you have a fucked up day too

[RFMaster]

Well, i explained what should be done

but apparently someone did not read/watched/understood



viewtopic.php?p=3555#p3555
^
>Now. Patched!
>But works(for more then 1gb) only if vmm32.vxd(From WindowsSystem) is patched too...


viewtopic.php?p=3639#p3639
^
this gif video explain things and showed the fact that original vmm.vxd v4.10.2226
is not compatible with this 4gb patch and this gif video showed the only possible way of
how to make it compatible.



viewtopic.php?p=3679#p3679
^
>if you install Q288430 in this case new vmm.vxd will be installed in your sysvmm32 folder. So, then you need to patch that file too because
>patched part of patched vmm32.vxd will be overrided at startup and then patch applied to vmm32.vxd will have no effect if vmm.vxd isn't patched too.


And now i can't figure out how and where did you get the idea to integrate that thing into vmm32.vxd???

[Steven W]

I can't speak for PROBLEMCHYLD, but I was just thinking of it because:

A) It's the first way I got it to work

B) Just poking around with VxDlib, Devlib and rplcldr thought I'd just roll everything up in one.

Yeah, I wanna marry it!

So it (integration) will work if patched?

So let me ask if this method will work:

use replcldr to replace VMM.vxd in VMM32.vxd (unpatched) off of CD and then apply the patch?

By the way, I have the utmost respect for both of you guys -- Don't let anything make you think otherwise!

[RFMaster]

Guys, i'm showing you more and more details and you become more and more confused.

I do not have energy explain these things any further.

Can't you wait just a few more days?

Soon i will finish the new patcher.

The new patcher will do all that is necessary, automatically, without your intervention.

You will only need to press the button.