Win9x : Utility to dynamic mapping TEMP to memory ?

#11 September 12th 04, 06:19 AM

PCR Sat, 11 Sep 2004 17:13:39 -0400 wrote ...

I was just about to apologize, BUT I see Blanton has a concern. Right!
Don't wipe %TEMP%, until after a fresh reboot. (I believe you can put a
shortcut to a .bat (which is a .pif) into "C:\WINDOWS\Start
Menu\Programs\StartUp" to do it, IF you must.)

And don't start an MVP war around here!

It sounds as a good idea.
But there is still option to temporary disable
utility when install...
But Bill is right about some editors....

P.S.: Dear PCR, why that exclamation ?
it is not the our first newsgroup topic.

I could know I am far from any war. ;-)

I just like to know the facts about circumtances
while using mentioned utility.
If I have a question about answer, I ask.

--
"Libor the Wanderer"
Sorry for my english in case of such troubles.
As dialup user I am sorry for late response.
ForPrivateResponseRemoveDelAndThisFromAboveAddress .

#12 September 12th 04, 06:33 AM

Bill Blanton Sat, 11 Sep 2004 19:44:50 -
0400 wrote ...

"Libor Striz" wrote in message ...
Bill Blanton Sat, 11 Sep 2004 11:06:46 -
0400 wrote ...

Does system expect %temp% content
is boot persistent ?

Not for all content, but %temp% is sometimes used for installs. There
may be other reasons for not wanting to have it cleared.

If I would persuaded in spite of that using such utility,
I could disable it before install, but now I am in a doubt.

my editor keeps a running backup in %temp%, which I can get at if
there is a power outage.

I see, it good reason.

I'd also have to question whether it would be wise based on memory
considerations. You will be taking from the memory pool, and as a
consequence will be causing more paging to disk.

I do not think so.

it should ( according to readme file ) write temp files to disk,
if system or apps demands its allocated memory, or size of temp dir
becomes too large. And you would write these files to disk
without vramdir too..

Are you sure the reboot part of installs
rely on it ?

Not all, but some. Wininit.ini is mainly for "in use" system files. Whether
the program uses the %temp% dir is up to the program.

Thats another case. Here I must take it in the account,
if I should use the utility.
I will ask the authors.
Now I will disable it when was going to install...

--
"Libor the Wanderer"
Sorry for my english in case of such troubles.
As dialup user I am sorry for late response.
ForPrivateResponseRemoveDelAndThisFromAboveAddress .

#13 September 12th 04, 07:51 PM

I am almost always trying to be funny, which is why I use exclamation
points. Seriously, I don't know much about "vramdir". But careful not to
delete %TEMP% too soon. And doing it in Autoexec.bat is too soon. It can
be done from where I said, but then it will be tough to keep an eye out
for suspicious characters showing up in there.

Also, I have read here that a RAM Disk will prevent Windows from making
full use of available RAM. What is it that you wish to use the RAM Disk
for?

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Libor Striz" wrote in message
...
| PCR Sat, 11 Sep 2004 17:13:39 -0400 wrote ...
|
| I was just about to apologize, BUT I see Blanton has a concern.
Right!
| Don't wipe %TEMP%, until after a fresh reboot. (I believe you can put
a
| shortcut to a .bat (which is a .pif) into "C:\WINDOWS\Start
| Menu\Programs\StartUp" to do it, IF you must.)
|
| And don't start an MVP war around here!
|
| It sounds as a good idea.
| But there is still option to temporary disable
| utility when install...
| But Bill is right about some editors....
|
| P.S.: Dear PCR, why that exclamation ?
| it is not the our first newsgroup topic.
|
| I could know I am far from any war. ;-)
|
| I just like to know the facts about circumtances
| while using mentioned utility.
| If I have a question about answer, I ask.
|
|
| --
| "Libor the Wanderer"
| Sorry for my english in case of such troubles.
| As dialup user I am sorry for late response.
| ForPrivateResponseRemoveDelAndThisFromAboveAddress .

#14 September 13th 04, 05:51 AM

#15 September 13th 04, 09:00 PM

#16 September 14th 04, 04:58 AM

The product was developed in the days when slow machines needed all the help
they could get. It was specifically targeted at installation procedures that
unzipped installation files to a TEMP folder and then installed from the
unzipped files. Installing large applications (like some of the development
environments) could benefit enormously from forcing the unzipped files to a
TEMP folder in RAM, especially with the W95 memory management algorithms,
which tended to hang onto old data and not cache new files (which, after
all, are only being written once and read once, and do not appear to be a
good candidate for caching). For special purposes, the difference between
slow disk and fast RAM made VRAMDIR a worthwhile tool. Now that machines
have faster disks, and with more RAM available and better caching rules, the
purpose has pretty much disappeared, but it may still have a role in special
cases.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"PCR" wrote in message
...
| Another option is copy such content to other dir before rebooting,
| and after that in autoexec move it back.

This is getting too convoluted now. I can't recall whether I personally
ever had MBs of data in %TEMP%. If so, one day I must have deleted it
all. Others certainly have posted they DID find MBs of folders/files in
there. Surely, something is wrong if they ever come back in that
quantity after deletion. Now/then, fine, McAfee will put a slew of
folders in there, each holding a single file. And it does keep
"WebPoolFileFile" & "Delta.ini" more/less permanently there. There is an
URL shortcut that pops into TEMP occasionally, probably from an MS site.
And I've seen one of those-- or was it an icon file?-- mentioning BootIt
NG.

Other than that, a few MS & other installations do put temporary files
in there. It isn't too big a deal to keep an eye on it & to delete the
ones left behind. I can't tell whether "Vramdir" will properly handle
%TEMP% from the write-up...

....Quote of Vramdir.....
| In Windows 95/98, run INSTALL.BAT. This copies files into the
| Windows system directory and modifies system settings. It
| automatically sets the directories pointed to by the TEMP and
| TMP environment variables to be handled by vRamDir.
|
| After Windows restarts, all newly created files and sub-
| directories under the TEMP directories will be in RAM.
| Previously existing files and directories will still be on the
| hard-disks.
....EOQ...of Vramdir.....

It could be %TEMP% is not actually deleted, but will be there for
Windows to access as necessary. It will be in RAM instead of on HDD, if
that is the case. But I can't really tell.

I don't know how to evaluate the full product. They certainly make it
sound advantageous. But I think it adds a layer of uncertainty to
Windows, which already has enough of it's own. Certainly, better get a
UPS (Uninterruptible Power Supply)-- well, whether or not you do go with
Vramdir.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Libor Striz" wrote in message
...
| PCR Sun, 12 Sep 2004 14:51:21 -0400 wrote ...
|
| I am almost always trying to be funny, which is why I use exclamation
| points.
|
| I like that approach. Life is too serious for not making jokes about
| it ( and myself too ). :-)
|
| Seriously, I don't know much about "vramdir". But careful not to
| delete %TEMP% too soon. And doing it in Autoexec.bat is too soon. It
can
| be done from where I said, but then it will be tough to keep an eye
out
| for suspicious characters showing up in there.
|
| Also, I have read here that a RAM Disk will prevent Windows from
making
| full use of available RAM. What is it that you wish to use the RAM
Disk
| for?
|
| I still using JV16 powertols for cleaning unwanting files
| after some delay in access time. I am now keeping my eye
| at TEMP content while PC si to be restarted, still nothing
| not to be deleted.
|
| Another option is copy such content to other dir before rebooting,
| and after that in autoexec move it back.
|
| VRamDir id not real ramdisk. It does not create disk letter at all.
| And it does not allocate itsel not memory but 4 kB.
| If sth is created in temp, that space is dynamically allocated.
| And released if TEMP content is deleted.
|
| You can use Vramdir for any dir, e.g. C:\RAM
| for short time temporary files.
| Maybe temporary uncopressed archive content.
| And even using swap, if fixed size, i should be faster
| then writing files on disk by normal way.
| (No work with FAT, directory items, disk head fiddling )
|
| After that accupied memory is some kB again.
|
| I was attached Vramdir readme file, maybe not too log for you.
|
|
| -----------------------------------
|
|
|
| ===========================
| vRamDir 1.10
| for Microsoft Windows 95/98
| ===========================
|
|
| Copyright 1996-1998
| Virtual Software Corporation
| 15016 SE 63 St.
| Bellevue, WA 98006-4634
| http://www.virtusoft.com/
|
| Fax: (425)649-8277
|
|
| vRamDir is a dynamic 32-bit virtual RAM file system driver for
| Windows 95/98.
|
|
| A. Introduction
| B. Advantages of vRamDir over Hard-disks
| C. Advantages of vRamDir over RAM-disks
| D. Advantages of vRamDir over Disk-Cache
| E. Installation
| F. Usage
| G. Benchmarks
| H. Where to Get the FREE Trial Version of vRamDir
| I. Limit of the Trial Version
| J. How to Order vRamDir
| K. Technical Support
| L. License and Disclaimer
|
|
| ============
| A. Introduction
| ============
|
| vRamDir is a dynamic 32-bit virtual RAM file system driver for
| Windows 95/98. It is to replace RAM-disk and speed up hard-disk
| related operations. vRamDir is over 30 times faster than hard-
| disks, 5 times faster than RAM-disks, and 2 times faster than
| disk-cache. vRamDir also keeps hard-disks less fragmented,
| saves hard-disk wears and tears, and saves battery power on
| notebook computers.
|
| vRamDir does not pre-allocate any memory, and it has no
| practical limit on the amount of files it can hold. No matter
| how much RAM your system has, vRamDir puts it into more
| efficient use and speeds up the system. If the system has more
| than 32MB RAM, vRamDir prevents the RAM from being wasted; if
| the system has less than 16MB RAM, it is important to use
| vRamDir to increase system speed.
|
|
| =====================================
| B. Advantages of vRamDir over Hard-disks
| =====================================
|
| vRamDir is tens and thousands of times faster than hard-disks.
|
| vRamDir creates file systems in Random Access Memory (RAM) to
| simulate hard-disks.
|
| In access time, RAM is thousands of times faster than hard-
| disks. Locating an address in RAM takes 50-100ns, while
| seeking to a sector on a hard-disk takes 5-20ms. So RAM access
| is about 100,000 times faster.
|
| In throughput, RAM is tens of times faster than hard-disk.
| Reading/writing one block of data in RAM is about 20-100MB/s,
| while on hard-disks it is 1-2MB/s. So RAM throughput is 10-100
| times faster.
|
| By using vRamDir file systems, file operations are tens and
| thousands of times faster than hard-disks.
|
| vRamDir keeps the hard-disks less fragmented. Without vRamDir,
| temporary files scatter around on hard-disks. This can be
| prevented by creating the temporary files in vRamDir. Less
| fragmented hard-disks result in faster hard-disk access.
|
| vRamDir saves wears and tears of hard-disks. Hard-disks have
| mechanical parts and thus have much shorter life-spans than
| RAM. When accessing files in vRamDir, hard-disks are not
| accessed. Thus hard-disks are less probable to fail, and hard-
| disks live longer, hence it is less likely to lose your data
| on hard-disks.
|
| vRamDir saves battery power on notebook computers. When hard-
| disks are less often accessed because of vRamDir, less power
| is consumed by hard-disks, and the battery runs longer.
|
|
| =============================================
| C. Advantages of vRamDir over RAM-Disk Utilities
| =============================================
|
| vRamDir is several times faster than RAM-disk utilities.
|
| vRamDir is a 32-bit protected-mode Windows 95/98 native virtual
| device driver (VxD), while RAM-disk utilities are 16-bit real-
| mode DOS device drivers. With RAM-disks, Windows 95/98 needs to
| switch forth and back between 16-bit real-mode and 32-bit
| protected-mode. This very time consuming mode switching is
| avoided in vRamDir. For example, when benchmarked against
| RAMDRIVE, vRamDir is more than 4 times faster.
|
| vRamDir is dynamic. When there is no file in vRamDir, vRamDir
| does not allocate any memory. RAM-disks, on the other hand,
| pre-allocate fixed amount of memory. Even when the memory is
| not used by files on a RAM-disk, the memory is no longer
| available to system and application programs. With vRamDir, no
| extra memory is taken, more memory is available to the system,
| and the system runs faster.
|
| When more files need to be on RAM-disk than the fixed amount
| pre-allocated, RAM-disk is not able to hold them. The
| operation will fail, and your application or even the system
| may crash as a result. With vRamDir, it expands on demand.
| There is no practical limit on the number of files and the
| size of files that can fit into vRamDir. (The limit is the
| total amount of physical memory plus the free hard-disk space
| in your system, which is even larger than what is available
| without vRamDir, the free hard-disk space alone.)
|
| vRamDir is virtual. vRamDir can return memory back to the
| system, while RAM-disks can never do that. When other
| applications need more memory, files in vRamDir can be saved
| onto hard-disks and memory is returned to system. You never
| need to worry about vRamDir using too much memory. vRamDir
| makes sure that it always puts memory into the best use and
| that the system runs as fast as possible.
|
| vRamDir creates virtual file systems, while RAM-disks create
| disk images on which to build FAT file systems. Disks are
| block devices and have limitations. For example, on a disk
| even when only 1-byte is used in a block, the rest is not
| available to other files. RAM is different from disks. It is
| not efficient to use RAM in the same block manner as disks.
| FAT file system has further limitations. In RAM-disks, e.g.,
| space needs to be pre-allocated for File Allocation Tables
| (FAT), the block size and the number of entries in the root
| directory, etc., needs to be pre-determined. vRamDir avoids
| the limitations of block devices and the FAT system. vRamDir=3Fs
| file system is virtual and much more efficient. There is no
| setting needs to be fine-tuned.
|
| vRamDir maps directories into RAM, while RAM-disks create new
| drives. With vRamDir, it is easy to map existing directories,
| e.g., TEMP directories, into RAM. There is no new drive letter
| to worry about. Existing settings for the system and
| applications do not need to be changed to point to the new
| drive letter. vRamDir is very easy to set up, and the system
| runs exactly like before, except that with vRamDir it will be
| much faster.
|
| vRamDir supports Long File Name, while RAM-disks only support
| short name.
|
|
| ===============================================
| D. Advantages of vRamDir over Disk-Cache Utilities
| ===============================================
|
| vRamDir is several times faster than disk-cache utilities.
|
| vRamDir is not designed to replace disk-cache, but vRamDir
| does something that disk-cache can not do. Disk cache cannot
| replace vRamDir. They are used for different purposes.
|
| Disk-cache keeps most recently accessed files in memory. You
| do not have control of what to keep in the cache and what not.
| vRamDir let you control what to be put in RAM. vRamDir is
| designed to speed up temporary file access.
|
| vRamDir is much faster than disk-cache in the best
| circumstances. Many applications create temporary files on
| hard-disks. With disk-cache, when a temporary file is created,
| it will stay in memory for a short while. Then within, e.g., 1
| second, disk cache will write the file out to hard-disks,
| which is very slow. With vRamDir, files can stay in memory
| much longer. A temporary file may stay in memory during its
| entire existence, from the point it is created, to the point
| it is deleted. Hard-disks may never need to be accessed in
| these temporary file operations.
|
| vRamDir is still several times faster than disk-cache overall,
| even in the worst situations. For example, WINBENCH=3Fs disk/mix
| test, which emulates popular applications=3F disk operations,
| reads/writes over 100MB of files. When the test is run on a
| Pentium 100 with 32MB RAM, vRamDir needs to swap a lot of data
| to the disk. This is one of the worst scenario for vRamDir.
| But running the test on vRamDir is still over 2 times faster
| than VCACHE.
|
|
| ============
| E. Installation
| ============
|
| If applicable, Unzip VRAM110T.ZIP or VRAMD110.ZIP into a
| directory, e.g., C:\vRamDir
|
| Switch to the directory, e.g., C:, CD C:\vRamDir
|
| In Windows 95/98, run INSTALL.BAT. This copies files into the
| Windows system directory and modifies system settings. It
| automatically sets the directories pointed to by the TEMP and
| TMP environment variables to be handled by vRamDir.
|
| After Windows restarts, all newly created files and sub-
| directories under the TEMP directories will be in RAM.
| Previously existing files and directories will still be on the
| hard-disks.
|
| You can run the control panel vRamDir configuration utility to
| change the list of directories to be handled by vRamDir.
|
| If you want to temporarily disable vRamDir, you can remove all
| the directories in the list using the vRamDir configuration
| utility in control panel.
|
| If you want to completely uninstall vRamDir, you can run
| Control Panel - Add/Remove Programs - Install/Uninstall,
| select vRamDir, then press Add/Remove.
|
|
| =====
| F. Usage
| =====
|
| IMPORTANT: Files in RAM will be deleted after Windows is shut
| down or restarted. So only temporary files should be put under
| vRamDir. If you put other files in vRamDir for faster
| operations on them, remember to move them out to non-vRamDir
| directories after you finish working with them, if you want to
| save them on the hard-disk.
|
| When vRamDir is first installed, it will automatically put
| TEMP and TMP directories under vRamDir. You can later use
| vRamDir configuration utility in control panel to edit the
| list.
|
| When you delete vRamDir files in Windows Explorer, if you say
| YES to put the files into Recycle Bin, the files will be
| written onto disk in Recycle Bin, which can be slow. If this
| is not what you want, you can delete the files without saving
| them into Recycle Bin by holding down the SHIFT key when you
| press DELETE in Windows Explorer.
|
| If an application queries for the amount of free space in a
| vRamDir directory, the free space of the hard-disk that host
| the directory is returned. If the application complains about
| not enough space, more space on the hard-disk need to be
| freed. Most likely, vRamDir does not need the free space on
| the hard-disk, and vRamDir is able to hold more files than
| what the hard-disk free space indicates. For example, if the
| hard-disk has 10MB free, after 5MB of new files are created in
| vRamDir, the hard-disk may still have 10MB free, instead of
| 5MB.
|
| Directories mapped to vRamDir can not be deleted or renamed.
| For example, if C:\WIN95\TEMP is mapped to vRamDir, C:\WIN95
| can not be deleted, nor can it be renamed, e.g., to
| C:\WINDOWS. If you want to delete or rename such directories,
| you should unmap the vRamDir directory first, e.g., unmap
| C:\WIN95\TEMP in the control panel vRamDir configuration
| utility.
|
| You can get vRamDir performance statistics from System
| Monitor:
|
| vRamDir - Memory Allocated: the total amount of virtual memory
| allocated by vRamDir at the moment.
|
| vRamDir - Bytes Read/Written: the total number of bytes
| read/written in vRamDir from system boot-up.
|
| vRamDir - Operations Performed: the total number of file
| operations performed by vRamDir.
|
|
| ==========
| G. Benchmarks
| ==========
|
| Wintune 95, WINDOWS Magazine's test and tune-up kit,
| http://www.winmag.com/software/wt95.htm
|
| WinBench 96, PC Magazine,
| http://www.zdnet.com/zdbop/winbench/winbench.html
|
| MDB95,
| http://ourworld.compuserve.com/homep...ebel/mdb95.htm
|
| To test vRamDir speed with these benchmarks, you need to map a
| root directory to vRamDir, e.g., D:\. You should select a
| drive with the fewest files. Remember to remove the mapping
| after you finish benchmarking. Otherwise, all new files on
| that drive will be in RAM and will not be saved onto the hard-
| disk.
|
| For the true speed of hard-disks, you need to look at the
| uncached benchmark number in MDB or Wintune.
|
| To get the true speed of vRamDir, you need 3MB free memory to
| run Wintune, or enough free memory to hold the test file in
| MDB. Before you run the benchmarks, you can check the amount
| of free memory using System Monitor. To make more free memory
| available, you can limit VCACHE size by putting the following
| in SYSTEM.INI, e.g.:
|
| [vcache]
| MinFileCache = 1000
| MaxFileCache = 1000
|
| You can remove these settings after you finish benchmarking.
|
| To get the real life speed difference between vRamDir and
| cached hard-disks, you can run the Disk WinMark in WinBench,
| which emulates disk file operations in 13 popular Windows
| applications.
|
| For example, the results of the benchmarks on a Gateway 2000
| Pentium 100:
|
| MDB 16MB file:
|
| Hard-disk: 1.4 MB/s
| RAMDRIVE: 9.0 MB/s
| vRamDir: 35.0 MB/s
|
| WinBench Disk WinMark:
|
| VCACHE: 0.7 MB/s
| vRamDir: 1.5 MB/s
|
|
| ==============================================
| H. Where to Get the FREE Trial Version of vRamDir
| ==============================================
|
| http://www.virtusoft.com/
|
|
| ==========================
| I. Limit of the Trial Version
| ==========================
|
| If you have not paid Virtual Software Corporation for vRamDir,
| you are running a trial version of vRamDir. After you
| experienced the advantages provided by vRamDir, you can order
| the full version from Virtual Software Corporation.
|
| The trial version is time limited to 30 minutes. After 30
| minutes, the files will be written to hard-disks instead of in
| vRamDir. The system will function as before. If you need more
| time to evaluate vRamDir, you can restart Windows and vRamDir
| will run for another 30-minute. If you buy the full version,
| there will be no time limit, and vRamDir will function all the
| time.
|
| After 30 minutes, a message box will pop up signaling the
| expiration of the trial period. If the display is blanked into
| power-saving mode when the message box pop up, the message box
| will not be visible. Just press SPACE to get rid of the
| invisible message box.
|
| In the trial version, sub-directories under vRamDir are
| created on the hard-disks, while files under vRamDir are in
| RAM. If you buy the full version, all files and sub-
| directories under vRamDir will be in RAM.
|
| The full version is a little bit faster than the trial
| version.
|
|
| ====================
| J. How to Order vRamDir
| ====================
|
| If you have an email account, we can send you a UUENCODED
| VRAMD110.ZIP file through email. It costs US$10. Fill out
| ORDER.TXT form. Please make sure to include your email
| address.
|
| If you prefer to receive a floppy disk, it costs US$15 for an
| address in US, and US$20 for outside US. Fill out ORDER.TXT
| form.
|
| European users who do not have a credit card may order it from
| BTSoftware using local currencies. Check with BTSoftwa
|
| BTSoftware
| Postbus 4911
| 5604 CC Eindhoven
| The Netherlands
|
| Tel: 040-2631259
| Fax: 040-2906460
| Email:
| Web: http://www.BTSoftware.com
|
|
| =================
| K. Technical Support
| =================
|
| WWW: http://www.virtusoft.com/
|
| email:
|
| Fax: (425)649-8277
|
| Postal mail:
| Virtual Software Corporation
| 15016 SE 63 St.
| Bellevue, WA 98006-4634
| USA
|
|
| ======================
| L. License and Disclaimer
| ======================
|
| One copy of vRamDir can only be installed on one workstation
| computer. It can NOT be put on network servers to be shared by
| workstations. The full version of vRamDir can NOT be
| distributed or copied to any other people in any way.
|
| Anyone distributing the trial version of vRamDir must first
| contact Virtual Software Corporation for authorization.
|
| Users of vRamDir must accept this disclaimer of warranty:
|
| vRamDir is supplied as is. The author disclaims all
| warranties, expressed or implied, including, without
| limitation, the warranties of merchantability and of fitness
| for any purpose. The author assumes no liability for damages,
| direct or consequential, which may result from the use of
| vRamDir.
|
|
|
| -----------------------------------
|
| --
| "Libor the Wanderer"
|
| Sorry for my english in case of such troubles.
| Any offense is because of bad english
| and was not intended.
| ForPrivateResponseRemoveDelAndThisFromAboveAddress .

#17 September 14th 04, 06:16 PM

Jeff Richards Tue, 14 Sep 2004 13:58:26 +1000
wrote ...

The product was developed in the days when slow machines needed all the help
they could get. It was specifically targeted at installation procedures that
unzipped installation files to a TEMP folder and then installed from the
unzipped files. Installing large applications (like some of the development
environments) could benefit enormously from forcing the unzipped files to a
TEMP folder in RAM, especially with the W95 memory management algorithms,
which tended to hang onto old data and not cache new files (which, after
all, are only being written once and read once, and do not appear to be a
good candidate for caching). For special purposes, the difference between
slow disk and fast RAM made VRAMDIR a worthwhile tool. Now that machines
have faster disks, and with more RAM available and better caching rules, the
purpose has pretty much disappeared, but it may still have a role in special
cases.

Thank for detailed explanation..

I think it is still useful for some programs, creating really
short life temporary files, like some archievers
while updating archives.
Utility is not limited for TEMP dir.

e.g. I like rather outdated but very clever archiver jar32
by http://www.arjsoft.com
I have created c:\RAM directory memory mapped by vramdir
and redirect jar temporary files there. Much faster :-)

--
"Libor the Wanderer"

Sorry for my english in case of such troubles.
Any offense is because of bad english
and was not intended.
ForPrivateResponseRemoveDelAndThisFromAboveAddress .

#18 September 14th 04, 06:22 PM

Bill Blanton Sat, 11 Sep 2004 19:44:50 -
0400 wrote ...

Not for all content, but %temp% is sometimes used for installs. There
may be other reasons for not wanting to have it cleared. For example
my editor keeps a running backup in %temp%, which I can get at if
there is a power outage.

Some batch / script can copy %temp% to another dir in such case.
And autoexec would return it back.

I'd also have to question whether it would be wise based on memory
considerations. You will be taking from the memory pool, and as a
consequence will be causing more paging to disk.

Even paging in the worst case of heavy use of vramdir,
is not page file the fastest way how to write to/read for disk ?
Instead of creating many small files ?

But usually free RAM or extra cache size is pretty more then enough,
it is seldom more them some MB of demanded size....

Not all, but some. Wininit.ini is mainly for "in use" system files. Whether
the program uses the %temp% dir is up to the program.

Those replaced files mentioned in wininit.ini file are usually in
win/system or drivers(32) dirs.

--
"Libor the Wanderer"

Sorry for my english in case of such troubles.
Any offense is because of bad english
and was not intended.
ForPrivateResponseRemoveDelAndThisFromAboveAddress .

#19 September 14th 04, 10:24 PM

Well, I must admit, I myself was nearly hypnotized by that Vramdir
write-up, all those many advantages & all. And I have empathy for the
programmer(s) who must have labored hard at it. I tend to think they
must have gotten %TEMP% processing correct, as that would be a blunder
of immense proportions. Surely, toss it, if they didn't.

Richards (thanks) has influenced me not to read it again, though,
especially as all seems well & quick enough in this Compaq 7470, with
the exception of internet travel usually. Even that, I, I, I DO believe
is, uh, quicker when working offline from TIFs. (Well, once, I think I
saw the MSKB was STILL slow EVEN offline. But how can that be? Must have
been my imagination!)

OK, that's the best evaluation I can do of Vramdir.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Libor Striz" wrote in message
...
| Jeff Richards Tue, 14 Sep 2004 13:58:26 +1000
| wrote ...
|
| The product was developed in the days when slow machines needed all
the help
| they could get. It was specifically targeted at installation
procedures that
| unzipped installation files to a TEMP folder and then installed from
the
| unzipped files. Installing large applications (like some of the
development
| environments) could benefit enormously from forcing the unzipped
files to a
| TEMP folder in RAM, especially with the W95 memory management
algorithms,
| which tended to hang onto old data and not cache new files (which,
after
| all, are only being written once and read once, and do not appear to
be a
| good candidate for caching). For special purposes, the difference
between
| slow disk and fast RAM made VRAMDIR a worthwhile tool. Now that
machines
| have faster disks, and with more RAM available and better caching
rules, the
| purpose has pretty much disappeared, but it may still have a role in
special
| cases.
|
|
| Thank for detailed explanation..
|
| I think it is still useful for some programs, creating really
| short life temporary files, like some archievers
| while updating archives.
| Utility is not limited for TEMP dir.
|
| e.g. I like rather outdated but very clever archiver jar32
| by http://www.arjsoft.com
| I have created c:\RAM directory memory mapped by vramdir
| and redirect jar temporary files there. Much faster :-)
|
|
| --
| "Libor the Wanderer"
|
| Sorry for my english in case of such troubles.
| Any offense is because of bad english
| and was not intended.
| ForPrivateResponseRemoveDelAndThisFromAboveAddress .

#20 September 15th 04, 05:46 AM

PCR Tue, 14 Sep 2004 17:24:09 -0400 wrote ...

Richards (thanks) has influenced me not to read it again, though,
especially as all seems well & quick enough in this Compaq 7470, with
the exception of internet travel usually. Even that, I, I, I DO believe
is, uh, quicker when working offline from TIFs. (Well, once, I think I
saw the MSKB was STILL slow EVEN offline. But how can that be? Must have
been my imagination!)

OK, that's the best evaluation I can do of Vramdir.

If I understand, TIF with vramdir works slower or not faster then
without ?

Note that files already existed in directory just attached to vramdir
stays still in hdd and are not mapped to memory.

---
One note about install: Recently I upgraded my Kerio firevall - MSI
installer. during installation there was plenty files in temp,
but when restart was demanded, only log files there ( forgotten I mean )

--
"Libor the Wanderer"

Sorry for my english in case of such troubles.
Any offense is because of bad english
and was not intended.
ForPrivateResponseRemoveDelAndThisFromAboveAddress .

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Interpretation of failures and delays at boot.	George	Improving Performance	48	September 9th 04 03:35 AM
RAM	Iqbal	Software & Applications	22	July 24th 04 09:04 AM
Please help! Display settings !!	Mitzi	Monitors & Displays	12	July 11th 04 05:19 AM
Virtual Memory	Jean	Improving Performance	2	June 19th 04 09:55 PM
Memory	Rush	General	2	June 18th 04 03:58 AM