Major new development in Windows 98 RAM memory capability patch has beendiscovered!

It appears that some combination of a Windows-98 hot-fix and some
hacking at least 4 years ago, possibly by some Germans, has resulted in
a very simple set of 2 files that can allow Windows 98 to use up to 4 gb
of ram.

As time goes on we'll learn more about how this patch originated, but it
seems to have been circulating in German-language windows forums up
until now.

Thanks to Dencorso and his obtuse and irrational censorship as he lords
over the Windows-98 Forums at MSFN.org, he indicated that such a German
patch existed, and he labeled it as "warez". I then began a discussion
on "FoolsDesign.org" and the location of the patch files was posted
thanks to a user there. That thread can be found he

http://www.foolsdesign.org/viewtopic.php?f=30&t=607

Once Dencorso found out about that thread, he removed his own MSFN post
where he described his censorship of the topic. He's so anal he even
censored himself!

Why on earth those moderators at MSFN think that Microsoft is in any way
concerned about Windows 9x today defies explanation. They are their own
worst enemies when it comes to helping advance and grow the Windows
9x/me enthusiast community. Their censorship efforts do nothing but
instill a culture of fear and intimidation and diminish the community at
MSFN. Hopefully more enthusiasts and win-98 users will discover the
free and uncensored windows 98 usenet groups and also the software forum
at foolsdesign.org.

Are you reading this Dencorso?

Will you and your other moderators change your ways and allow more free
and open discussion about how to advance Windows 9x/me - Microsoft be
damned?

Here is a link to the new VMM32.vxd and VMM.vxd files that allow Windows
98 to use all available ram on any motherboard you have, up to 4 gb:

http://www.freora.de/index.php?optio...id=3&Itemid=52

Scroll down to the last item, which is:

4 GB Hauptspeicher für WIN 98SE ( mit vmm98sed.zip )hot!

But don't click on it. Instead, click on the small little "Download"
button right beside the "Details" button.

What you will download is Vmm98sed.zip (about 1mb in size). When you
unpack it, you will find a reproduction of the Windows directory tree
that helps tell you where to put these files.

Inside WINDOWS\SYSTEM\ you will find VMM32.VXD and you will copy that
file to your own WINDOWS\SYSTEM directory, over-writing the existing
file which you should first rename to VMM32.vxd.old.

You will also see a subdirectory called VMM32 which contains VMM.VXD
(which you should copy to your WINDOWS\SYSTEM\VMM32\ directory, and
there will be no pre-existing file with that name.

There is some indicatation that a file called ENABLE.VXD should also be
placed in the WINDOWS\SYSTEM\VMM32\ directory. That file is not
normally found on win-9x systems, but it is on the win-98 CD. Here is a
link to that file:

http://filepost.com/files/98e56ddd/ENABLE.VXD/

The two files VMM32.VXD and VMM.VXD seem to have been in circulation
since January 2010 because they were submitted to virustotal.com on that
date for malware analysis. That was the first and only time they have
been seen by Virustotal until I submitted them yesterday. The scan 4
years ago was negative, and so was my scan, so they are clean as far as
53 Anti-virus programs are concerned.

I have varified that they work, as I have 2 gb ram on my system now and
Windows System Properties shows 2046 mb available memory.

Any questions? Comments?

Post them! No censorship here!

98 Guy wrote:
Inside WINDOWS\SYSTEM\ you will find VMM32.VXD and you will copy that
file to your own WINDOWS\SYSTEM directory, over-writing the existing
file which you should first rename to VMM32.vxd.old.

That vmm32.vxd carries a date of 2002-10-12 while my existing one is
newer, from 2006-10-26. I don't know where that came from. Should I
still risk overwriting it?

Axel

In microsoft.public.win98.gen_discussion Axel Berger wrote:
98 Guy wrote:
Inside WINDOWS\SYSTEM\ you will find VMM32.VXD and you will copy that
file to your own WINDOWS\SYSTEM directory, over-writing the existing
file which you should first rename to VMM32.vxd.old.

That vmm32.vxd carries a date of 2002-10-12 while my existing one is
newer, from 2006-10-26. I don't know where that came from. Should I
still risk overwriting it?

I'd compare the exact file sizes. If the same, it's almost a given that
the files are too. If not, it depends whether you have any problems with
what you've got.

--
__ __
#_ |\| | _#

Computer Nerd Kev wrote:

In microsoft.public.win98.gen_discussion Axel Berger
wrote:
98 Guy wrote:
Inside WINDOWS\SYSTEM\ you will find VMM32.VXD and you will copy that
file to your own WINDOWS\SYSTEM directory, over-writing the existing
file which you should first rename to VMM32.vxd.old.

That vmm32.vxd carries a date of 2002-10-12 while my existing one is
newer, from 2006-10-26. I don't know where that came from. Should I
still risk overwriting it?

I'd compare the exact file sizes. If the same, it's almost a given that
the files are too. If not, it depends whether you have any problems with
what you've got.

Better way to compare is to enter this from the command prompt:

fc /b vmm32.vxd vmm32.new

(Replace the file names with the correct ones, of course.) If it tells you
anything other than "no differences encountered" then they are not the same.
Simple.

--
Beauty is one of the rare things which does not lead to doubt of God.
-- Jean Anouilh

Auric__ wrote:

That vmm32.vxd carries a date of 2002-10-12 while my existing
one is newer, from 2006-10-26. I don't know where that came
from. Should I still risk overwriting it?

I'd compare the exact file sizes. If the same, it's almost a
given that the files are too. If not, it depends whether you
have any problems with what you've got.

Better way to compare is to enter this from the command prompt:

fc /b vmm32.vxd vmm32.new

(Replace the file names with the correct ones, of course.)

What on earth are you people blathering about?

We're talking about vmm32.vxd.

It's a file that is dynamically created by windows when windows is
installed and also when new hardware is detected. It's pointless to
compare file-size and file-date between two different vmm32.vxd files.

There is a default or initial vmm32.vxd that is on the windows 98 CD,
and that is used initially but it will not remain static during the
install process.

The modded version has some key bytes changed, so of course it will not
compare with the original CD version.

You will note that you won't see a Version tab when you right-click on
vmm32.vxd and select properties.

98 Guy wrote:
It's a file that is dynamically created by windows when windows is
installed and also when new hardware is detected. It's pointless to
compare file-size and file-date between two different vmm32.vxd files.

If that's so, don't I lose all the entries Windows has already made
there?

Axel

In microsoft.public.win98.gen_discussion 98 Guy "98"@guy. com wrote:

What on earth are you people blathering about?

We're talking about vmm32.vxd.

It's a file that is dynamically created by windows when windows is
installed and also when new hardware is detected. It's pointless to
compare file-size and file-date between two different vmm32.vxd files.

Ah OK, my mistake. I'm just one of those wierd guys who runs w98 on PCs
(well, a PC) from around 1998, so I haven't needed to look that deeply into
these aspects of the inner workings.


By the way, to those reading, 98guy posted this topic in the MSDOS newsgroups
(eg. comp.os.msdos.misc) too, so there is some more discussion to look at
there as well.

--
__ __
#_ |\| | _#

Axel Berger wrote:

That vmm32.vxd carries a date of 2002-10-12 while my existing one
is newer, from 2006-10-26. I don't know where that came from.
Should I still risk overwriting it?

Rename your existing file (put .old at the end). You can rename the
file while running windows (sometimes the OS locks your access to system
files, but not in this case).