Not "PM" bits, we hedge and leave that available in case more bits pop through
the wire this evening:
- Tweak3D reviews the UltraTNT2
and there's a Voodoo 3 2000 Review @
BXBoards.
- Still more follow up on the Win98 VXD patch dealie (story and original follow-up). I received the following from someone I consider a
credible source. There is also a post up there by Mr.N Natural, creator of the patch to
answer questions and concerns, but to give an example of what they are, I'll pass the
email I received along (don't be offended by the bit about "non-advanced users"
he's referring to someone other than you specifically):
VMM32.VXD is a file built during Windows Setup. All of the VXD's people
say Microsoft forgot are actually rolled up into this file. VMM32 is a required file to
boot Windows. Why roll them up into one big file? Boot performance. It's
better to load one VXD at boot time than load 30. There are reports on Anandtech of
people not booting after installing the "patch" or coming up with
viruses. Other people have run dedicated system benchmarks and seen no performance
gains. Others have said they see gains but have not posted anything but a timedemo
score or, in one case, a 3d benchmark score. As to why anyone would get a
performance gain from this, I don't know. But messing with the system VXD's (you
know, the ones that load Ebios, Vcache, Vfat, Vcomm, and so forth) is not a wise thing to
do for anyone but an advanced user. And a lot of non-advanced users read your page.
Here is a post from
someone on Anandtechs BBS (called Cyprus) who contacted Microsoft about the
"patch":
"there is no reason to put these files into your windows\system directory.
win98 did NOT forget to put them there, and vmm32.vxd is not some generic replacement for
all the other files. This vmm32.vxd file isn't even one file, it is all the other files
specific to your machine grouped together into one file to speed up load times. This file
is built at setup time. If you manually copy all the files into windows\system, you're not
helping anything, and unnecessarily causing load/boot times to increase..."