What is the equivalent function I should use for Windows 3.1/95/98?

According to MSDN WriteProcessMemory only works in Windows 2000 and up.

IIRC, all that Windows junk before 2000 don't have protected memory, just go ahead and write wherever you want to.

Oh, and replace your brackets in the link with %28 and %29.

Thanks! So I just have to find what address the process starts at?
Is there a function for doing this, or do I have to manually search through all memory for some string that exists in that process and hopefully no others?

Usually one would use an inter-process communication to pass addresses to each other before reading/writing the memory.

Oh, BTW, I'm not really sure about the old Windows stuff, so take what I say with due caution.

WriteProcessMemory is available on Win95. MSDN started to remove Win9x from the support list of many functions because that is way too smart.

revolution, I think that even programs in Win 3.0 can't write the memory of each other by simple passing a pointer (i.e., "stdcall communicate_pointer, [anotherProcess], seg:someLabel" won't work). In case I'm wrong about Win 3.0, I'm sure that on Win95 is not that simple as the virtual addresses below $80000000 are not shared across processes.

I don't get it.
The functions are too smart? Or MSDN is? Or Win95 is? Or the act of changing MSDN to say they are Win2000 only is? Or??






Anyways, since MSDN is no longer accurate, where should I look for function information from now on? Please advise..

I presume it was just a bit of sarcasm.

Yes but about what part?

About MSDN telling that Windows 2000 is the minimum OS supporting it when it isn't true (the same happens with CreateFile where clearly it can't be true).

You'll have to see the old Win32.HLP help file and press the quick info button to know if Win95 supports it.

Thanks, I'll use this from now on.

I'm curious though, why has the data on MSDN been corrupted like that? Did Microsoft really mess up their own website (on purpose), or did someone hack it without them knowing?


edit: typo

I suppose this is because of the end of product support, note they don't say NT 4.0 support CreateFile when again it can't be true but yet they removed NT 4.0 from the list even though it is a NT kernel.

I haven't checked but perhaps when they move the minimum requirements to some newer OS maybe they remove some remarks about some flags/whatever that are not supported on older versions. For example if a given flag started to be supported on Windows 2000, it won't be necessary to point that out anymore because the function is documented to be available since Windows 2000 instead of, say, Windows 98 SE. So, when they misinform like this, they are also simplifying the documentation while leaving those who want to program for deprecated and unsupported OSes misinformed.

Well I hope they stop doing this.



Thanks for explaining it though.