VMM32files lists, anyone?

If you're willing, please post an export of your W98 registry branch:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\VMM32Files
(Also, if you're willing, state the mainboard make and model, though that
might not matter so much as I'm after a statistically useful base).

I'm looking to see what if any VXD files I ought to add to a generic
VMM32.VXD build. This is usually built per system at install time, but I
suspect a generic one can be viable, and even if not it's easier to know what
might be added to the VMM32 directory if I have some idea what turns up often
even if my own system isn't using it.

On Fri, 20 May 2011 10:37:05 -0500, Lostgallifreyan
put finger to keyboard and composed:

If you're willing, please post an export of your W98 registry branch:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contr ol\VMM32Files

REGEDIT4

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\VMM32Files]
"vdd.vxd"=hex:00
"vflatd.vxd"=hex:00
"vshare.vxd"=hex:00
"vwin32.vxd"=hex:00
"vfbackup.vxd"=hex:00
"vcomm.vxd"=hex:00
"combuff.vxd"=hex:00
"vcd.vxd"=hex:00
"vpd.vxd"=hex:00
"spooler.vxd"=hex:00
"udf.vxd"=hex:00
"vfat.vxd"=hex:00
"vcache.vxd"=hex:00
"vcond.vxd"=hex:00
"vcdfsd.vxd"=hex:00
"int13.vxd"=hex:00
"vxdldr.vxd"=hex:00
"vdef.vxd"=hex:00
"dynapage.vxd"=hex:00
"configmg.vxd"=hex:00
"ntkern.vxd"=hex:00
"ebios.vxd"=hex:00
"vmd.vxd"=hex:00
"dosnet.vxd"=hex:00
"vpicd.vxd"=hex:00
"vtd.vxd"=hex:00
"reboot.vxd"=hex:00
"vdmad.vxd"=hex:00
"vsd.vxd"=hex:00
"v86mmgr.vxd"=hex:00
"pageswap.vxd"=hex:00
"dosmgr.vxd"=hex:00
"vmpoll.vxd"=hex:00
"shell.vxd"=hex:00
"parity.vxd"=hex:00
"biosxlat.vxd"=hex:00
"vmcpd.vxd"=hex:00
"vtdapi.vxd"=hex:00
"perf.vxd"=hex:00
"vkd.vxd"=hex:00
"vmouse.vxd"=hex:00
"mtrr.vxd"=hex:00
"enable.vxd"=hex:00

Mainboard is PCChips M571 socket 7 (this is my Internet box).

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

Franc Zabkar wrote in
:

On Fri, 20 May 2011 10:37:05 -0500, Lostgallifreyan
put finger to keyboard and composed:

If you're willing, please post an export of your W98 registry branch:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Cont rol\VMM32Files
[list]


- Franc Zabkar

Good stuff. Thanks. Anyone else? The more I see, the more any important
differences can be taken into account so this core works for more people.

Franc Zabkar wrote:

"enable.vxd"=hex:00

Lostgallifreyan wrote:

Good stuff. Thanks. Anyone else?

Mine is exactly the same as Franc's, except that Franc has "enable.vxd"
- I don't have that.

98 Guy wrote in :

Franc Zabkar wrote:

"enable.vxd"=hex:00

Lostgallifreyan wrote:

Good stuff. Thanks. Anyone else?

Mine is exactly the same as Franc's, except that Franc has "enable.vxd"
- I don't have that.


Cool, I noticed that too, is the ONLY difference here too, and what's more, I
was thinking of adding it anyway, for MouseKeys, as a fallback for broken
mice.

This is interesting stuff! I read all over the net that VMM32.VXD is custom
built for each machine. But every instance I encounter so far is damn near
identical. Of course, this makes it even more important when differences
arise, soI want to see if they do....

On May 22, 5:51*pm, Lostgallifreyan wrote:
98 Guy wrote :

Franc Zabkar wrote:

"enable.vxd"=hex:00

Lostgallifreyan wrote:

Good stuff. Thanks. Anyone else?

Mine is exactly the same as Franc's, except that Franc has "enable.vxd"
- I don't have that.

Cool, I noticed that too, is the ONLY difference here too, and what's more, I
was thinking of adding it anyway, for MouseKeys, as a fallback for broken
mice.

This is interesting stuff! I read all over the net that VMM32.VXD is custom
built for each machine. But every instance I encounter so far is damn near
identical. Of course, this makes it even more important when differences
arise, soI want to see if they do....

They won't. What your hear is so much horse pucky, the vmm32.vxd file
is created the same for every machine because it comes from the same
inf file at install time. How they ever said it was a custom deal is
beyond me. What we need to do is grill Franc on what he did to get
enable.vxd!

It could be a customizable file but it hardly ever is?
C:\WINDOWS\INF\SUBASE.INF
and then search for 'CombineVxDs'
same file, every machine.

Lee wrote in news:d57d1990-60af-426d-bc75-
:

They won't. What your hear is so much horse pucky, the vmm32.vxd file
is created the same for every machine because it comes from the same
inf file at install time. How they ever said it was a custom deal is
beyond me. What we need to do is grill Franc on what he did to get
enable.vxd!

It could be a customizable file but it hardly ever is?
C:\WINDOWS\INF\SUBASE.INF
and then search for 'CombineVxDs'
same file, every machine.


True, but that's why I want to know. My generic build can use later versions
of the static VXD's IF they truly are generic. And they clearly are, near
enough.

I can tell you how Franc got his Enable VXD in there. He asked for it at
install time, in the options. This works by requesting that XVD and another
of similar name that I think is dynamically loaded, for example when MouseKey
is loaded during boot. By calling for the accessibility optional components
at install time, the Enable.vxd gets copied to the VMM32 directory along with
all the others, and Wininit.ini is prepared so after the first reboot the
next thing that happens is the compilation of VMM32.VXD, and this is clearly
a good way to get a working start point for our own scripts, or to slide in
our own chosen versions of static VXD's into an install because it doesn't do
any version checking.


Note that the Inf file is just a source of info. WHile it limits the superset
of possible items the subset might be defined by a lot of hardware specific
stuffs. But in practise most machines have to offer the same system services,
so I see no reason not to compile a larger-than-usual VMM32.VXD if I have to.
It still beats having loose files in the VMM32 directory, especially as I
want to compile anyway to get late version fixes in there.

On Wed, 1 Jun 2011 23:58:16 -0700 (PDT), Lee put
finger to keyboard and composed:

What we need to do is grill Franc on what he did to get
enable.vxd!

This KB article would suggest that it is related to the Accessibility
Options in Windows Setup:
http://support.microsoft.com/kb/q165454/

I did install these options, but I don't know why. Maybe it was to
help me with my memory problems. ;-)

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

In message , Franc Zabkar
writes:
On Wed, 1 Jun 2011 23:58:16 -0700 (PDT), Lee put
finger to keyboard and composed:

What we need to do is grill Franc on what he did to get
enable.vxd!

This KB article would suggest that it is related to the Accessibility
Options in Windows Setup:
http://support.microsoft.com/kb/q165454/

I did install these options, but I don't know why. Maybe it was to
help me with my memory problems. ;-)

- Franc Zabkar

I find it _very_ useful to have the beep that tells me when I've
accidentally hit caps lock (usually when going for A).
--
J. P. Gilliver. UMRA: 1960/1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf

So, Heresy be damned (well, it would be, wouldn't it?).
Radio Times 24-30 July 2010 (page 24)