[Steven W]

Certainly. I apologize too RFMaster, I know there's some catches to all of this and I should test for myself. I will wait for a while before reinstalling 98 SE and look forward to the end result of your work.

[PROBLEMCHYLD]

I didn't take anything personal guys. Things were getting a little heated though, but we are all adults. There was a lot of misunderstanding. We are all geeks and computer savvy, so I'm not sure where we went wrong. All bullshit aside

Here is what I did

1) Copied the entire Win98 CD to the hard drive.
2) I extracted the original VMM32.VXD file from the Win98 CD.
3) Patched VMM32.VXD with G-VMM32 Patcher.exe. (RFMaster Patch)
4) Copied patched VCACHE.VXD 4.10.2223 to C:WindowsSystemVmm32 folder
5) Rebuilt patched VMM32.VXD with only patched VCACHE.VXD 4.10.2223 inside of it. VMM.VXD is there by default.
6) Copied patched VMM32.VXD file to the root folder. (Where all the cab files are located)
7) Burned a new Win98 CD.

Now whenever I do a clean install, I don't need to patch anything, remove any ram sticks, make settings to SYSTEM.INI, patch files in safemode etc.... My Windows 98 machine will recognize all ram right out the box. Windows will always used the patched VMM32.VXD by default on clean installs. I could then build my tiny VMM32.VXD from the patched version. The VMM.VXD 4.10.2226 is only for laptops and that is all have to test on. I don't own any desktops anymore.

[Steven W]

By itself the file (VMM.VXD 4.10.2226) works on Desktops, but is probably completely unnecessary.

[RFMaster]

^Steven W
Yes, VMM.VXD 4.10.2226 is completely unnecessary for desktops.

^PROBLEMCHYLD

1. Install Win98se(eng) and your SP3. if you allready did this, then skip this step.
2. make backup of your C:windowssystemvmm32.vxd
3. make new folder C: mp
4. extract all VXDs from your C:windowssystemvmm32.vxd to C: mp
5. extract vmm32.vxd from 98se CD to C: mp
6. go to folder C: mp and change attributes of vmm32.vxd and vcache.vxd from "Read-only" to "Archive"
7. copy my patchers (vcache patcher and gvmm32 patcher) to C: mp
8. start both patchers and press the button "Patch it!"
9. delete patchers from C: mp
10. combine all files in C: mp to make new vmm32.vxd
11. copy new rebuilded vmm32.vxd from C: mp to C:windowssystem
12. delete C:windowssystemvmm32vmm.vxd
13. copy patched vmm.vxd (v4.10.2226) to C:windowssystemvmm32
That's all.

[I, user.]

Sorry if I rub you guys the wrong way now but this is why you need to open source your patcher. What if something happens to you tomorrow? No one can improve on the patch. No one knows what the heck that patch is doing. What if the original file gets hacked and altered?

You don't take money or sell this patch so why not just release the source code?

[Steven W]

I, user, while not dismissing what RFMaster has done, his patch (as of now) simply changes bytes. If you would compare a patched file to a non-patched file someone could fairly simply create a program that does the same thing. I think there's even some programs to automate that. Look for a program called "patch" from KanastaCorp.

[I, user.]

Yes, I see your point but I still think that it would be very nice to actually see the code. What's a line or two of code between friends? I'm always very curious on the way people code, how they write their code (style of code) and which language they use.

Anyway, sorry for being a nag.

[Steven W]

Don't shoot me for linking to neowin, but

http://www.neowin.net/forum/topic/10215 ... =594272288

[RFMaster]

^Steven W
What is common to all patchers is: They are changing some bytes in some files. And therefore pathers itself are not a big deal.
The most important and most difficult thing is to find what and why needs to be changed.

^I, user
>I'm always very curious on the way people code, how they write their code (style of code) and which language they use.

I use vb5/vb6, C/C++ and sometimes asm.

I also know some other languages like VB .NET, C#, Java, Pascal but almost never use them...

[Steven W]

^Steven W...
The most important and most difficult thing is to find what and why needs to be changed.

AMEN!