How to flush disk cache?

"SFB - KB3MM" wrote in message
...
This is from the Wn 98 Resource Kit. Search for Locked and then
click
Installable File System from the list:

The 32-bit VFAT works with a 32-bit, protected-mode cache driver
(VCACHE).
This driver replaces the 16-bit, real-mode SMARTDrive disk cache
software
provided with MS-DOS and Windows 3.1. The VCACHE driver features
better
caching algorithms than SMARTDrive, to cache information read from
or
written to a disk drive. The VCACHE driver also manages the cache
pool for
the Universal Disk Format File System (UDF) and the 32-bit network
redirectors provided with Windows 98.

Another big improvement in VCACHE over SMARTDrive is that the memory
pool
used for the cache is dynamic and is based on the amount of
available free
system memory. Users no longer need to allocate a block of memory as
a disk
cache. The system automatically allocates or deallocates memory used
for the
cache, based on system use.

For example, as you perform a large number of activities on the
network,
Windows 98 increases the size of the cache. As network activity
decreases
and more applications are started, Windows 98 decreases the cache
size.

Another improvement made to VCACHE in Windows 98 is the ability of
VCACHE
and the memory manager to execute applications that are present in
the
cache, directly out of the cache memory. This is referred to as
cache
mapping and improves the efficiency of memory utilization.

Remember you can monitor locked pages via System Monitor.

And the point??

"SFB - KB3MM" wrote in message
...
This is from the Wn 98 Resource Kit. Search for Locked and then
click
Installable File System from the list:

The 32-bit VFAT works with a 32-bit, protected-mode cache driver
(VCACHE).
This driver replaces the 16-bit, real-mode SMARTDrive disk cache
software
provided with MS-DOS and Windows 3.1. The VCACHE driver features
better
caching algorithms than SMARTDrive, to cache information read from
or
written to a disk drive. The VCACHE driver also manages the cache
pool for
the Universal Disk Format File System (UDF) and the 32-bit network
redirectors provided with Windows 98.

Another big improvement in VCACHE over SMARTDrive is that the memory
pool
used for the cache is dynamic and is based on the amount of
available free
system memory. Users no longer need to allocate a block of memory as
a disk
cache. The system automatically allocates or deallocates memory used
for the
cache, based on system use.

For example, as you perform a large number of activities on the
network,
Windows 98 increases the size of the cache. As network activity
decreases
and more applications are started, Windows 98 decreases the cache
size.

Another improvement made to VCACHE in Windows 98 is the ability of
VCACHE
and the memory manager to execute applications that are present in
the
cache, directly out of the cache memory. This is referred to as
cache
mapping and improves the efficiency of memory utilization.

Remember you can monitor locked pages via System Monitor.

And the point??

VCACHE buffers live in LOCKED RAM.

"Buffalo" wrote in message
news:Jnt0d.413669$%_6.59668@attbi_s01...

"SFB - KB3MM" wrote in message
...
This is from the Wn 98 Resource Kit. Search for Locked and then
click
Installable File System from the list:

The 32-bit VFAT works with a 32-bit, protected-mode cache driver
(VCACHE).
This driver replaces the 16-bit, real-mode SMARTDrive disk cache
software
provided with MS-DOS and Windows 3.1. The VCACHE driver features
better
caching algorithms than SMARTDrive, to cache information read from
or
written to a disk drive. The VCACHE driver also manages the cache
pool for
the Universal Disk Format File System (UDF) and the 32-bit network
redirectors provided with Windows 98.

Another big improvement in VCACHE over SMARTDrive is that the memory
pool
used for the cache is dynamic and is based on the amount of
available free
system memory. Users no longer need to allocate a block of memory as
a disk
cache. The system automatically allocates or deallocates memory used
for the
cache, based on system use.

For example, as you perform a large number of activities on the
network,
Windows 98 increases the size of the cache. As network activity
decreases
and more applications are started, Windows 98 decreases the cache
size.

Another improvement made to VCACHE in Windows 98 is the ability of
VCACHE
and the memory manager to execute applications that are present in
the
cache, directly out of the cache memory. This is referred to as
cache
mapping and improves the efficiency of memory utilization.

Remember you can monitor locked pages via System Monitor.

And the point??

VCACHE buffers live in LOCKED RAM.

"Buffalo" wrote in message
news:Jnt0d.413669$%_6.59668@attbi_s01...

"SFB - KB3MM" wrote in message
...
This is from the Wn 98 Resource Kit. Search for Locked and then
click
Installable File System from the list:

The 32-bit VFAT works with a 32-bit, protected-mode cache driver
(VCACHE).
This driver replaces the 16-bit, real-mode SMARTDrive disk cache
software
provided with MS-DOS and Windows 3.1. The VCACHE driver features
better
caching algorithms than SMARTDrive, to cache information read from
or
written to a disk drive. The VCACHE driver also manages the cache
pool for
the Universal Disk Format File System (UDF) and the 32-bit network
redirectors provided with Windows 98.

Another big improvement in VCACHE over SMARTDrive is that the memory
pool
used for the cache is dynamic and is based on the amount of
available free
system memory. Users no longer need to allocate a block of memory as
a disk
cache. The system automatically allocates or deallocates memory used
for the
cache, based on system use.

For example, as you perform a large number of activities on the
network,
Windows 98 increases the size of the cache. As network activity
decreases
and more applications are started, Windows 98 decreases the cache
size.

Another improvement made to VCACHE in Windows 98 is the ability of
VCACHE
and the memory manager to execute applications that are present in
the
cache, directly out of the cache memory. This is referred to as
cache
mapping and improves the efficiency of memory utilization.

Remember you can monitor locked pages via System Monitor.

And the point??

On Sat, 11 Sep 2004 00:04:29 -0000, "SFB - KB3MM" in
microsoft.public.win98.performance wrote:

"Buffalo" wrote in message
news:FIp0d.412779$%_6.226960@attbi_s01...
I believe it 'lives' in win386.swp .

I note that you put "lives" in quotes.

Maybe it is out of favor now, but that is an old programmers' description of
data files, especially dynamic ones. Many of the files just lay around the
DASD farm unless you wake them up. :-) Has to do with the [once?]
anthropomorphism of the computer.

Just curious here, if I said that memory had apparently been walked on
causing the error, would that seem quaint or unintelligible?

FACE

On Sat, 11 Sep 2004 00:04:29 -0000, "SFB - KB3MM" in
microsoft.public.win98.performance wrote:

"Buffalo" wrote in message
news:FIp0d.412779$%_6.226960@attbi_s01...
I believe it 'lives' in win386.swp .

I note that you put "lives" in quotes.

Maybe it is out of favor now, but that is an old programmers' description of
data files, especially dynamic ones. Many of the files just lay around the
DASD farm unless you wake them up. :-) Has to do with the [once?]
anthropomorphism of the computer.

Just curious here, if I said that memory had apparently been walked on
causing the error, would that seem quaint or unintelligible?

FACE

Maybe he said that because VCACHE buffers ARE a dynamic and living thing
VBG

"FACE" wrote in message
...
On Sat, 11 Sep 2004 00:04:29 -0000, "SFB - KB3MM"
in
microsoft.public.win98.performance wrote:

"Buffalo" wrote in message
news:FIp0d.412779$%_6.226960@attbi_s01...
I believe it 'lives' in win386.swp .

I note that you put "lives" in quotes.

Maybe it is out of favor now, but that is an old programmers' description
of
data files, especially dynamic ones. Many of the files just lay around
the
DASD farm unless you wake them up. :-) Has to do with the [once?]
anthropomorphism of the computer.

Just curious here, if I said that memory had apparently been walked on
causing the error, would that seem quaint or unintelligible?

FACE

Maybe he said that because VCACHE buffers ARE a dynamic and living thing
VBG

"FACE" wrote in message
...
On Sat, 11 Sep 2004 00:04:29 -0000, "SFB - KB3MM"
in
microsoft.public.win98.performance wrote:

"Buffalo" wrote in message
news:FIp0d.412779$%_6.226960@attbi_s01...
I believe it 'lives' in win386.swp .

I note that you put "lives" in quotes.

Maybe it is out of favor now, but that is an old programmers' description
of
data files, especially dynamic ones. Many of the files just lay around
the
DASD farm unless you wake them up. :-) Has to do with the [once?]
anthropomorphism of the computer.

Just curious here, if I said that memory had apparently been walked on
causing the error, would that seem quaint or unintelligible?

FACE

"SFB - KB3MM" wrote:

What does the Paging file have to do with VCACHE ?

Absolutely nothing


Where does VCACHE's data live?

In RAM. vcache is the Windows 95/98/Me replacement/enhancement for
Smartdrive.


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."

"SFB - KB3MM" wrote:

What does the Paging file have to do with VCACHE ?

Absolutely nothing


Where does VCACHE's data live?

In RAM. vcache is the Windows 95/98/Me replacement/enhancement for
Smartdrive.


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."