|
PureBytes Links
Trading Reference Links
|
Thanks for tour well written mail. In my system I have the option of
placing the Swap file in any partition and or drive. What this means is
that it exists on the hard drive and the use of it involves transfer of
data back and forth from RAM and hard drive.
Is it logically to assume that the RAM disk is actually in RAM and if one
assigns the swap file to the partition that designates that portion namely
the RAM disk, then data would then be transferred from RAM to RAM. I would
think that transfer rate should be faster than going back and forth to the
hard drive.
Another alternate method I have tried has to assign the max and min values
to a fixed value for the swap file (usually 3 or 4 times ones RAM memory
size). Of course this value should be set high and then by trail and error
adjusted downward until the user sees loss of operational speed. This in my
experience has achieved an increase of speed by two or more times speed,
however Microsoft recommends that this not be done but they put it in the
software.
Perhaps A. J. Maas may have a comment on this approach.
-----Original Message-----
From: A.J. Maas [SMTP:anthmaas@xxxxxx]
Sent: Friday, June 18, 1999 4:30 PM
To: metastock@xxxxxxxxxxxxx
Subject: Re: Faster MS Win 6.5 Explorations Using Cache???
It is your Swap file !!
Root\filename.extension
(C:\Win386.swp)
RAM-Disc is (used to be) an add-in card (in slot on Motherboard) and
primarely used for RAM extension. A card with chip(s) on it, a virtual
disk,
fast accessable (and also like your video-card is an add-in card too).
Present Mem chips(RAM-chips), for speed and capacity, have outdated
these cards. In old DOS days, 4kB used to be the smallest first mem
capacity
available, and 1 Mb was unbelievable giganticly large, however soon became
to less/to short for the newer released applications and an extension to
mem was
made by adding a (virtual) disc, eg the on-card's chip).
Guy's indicator problems (in general) could be due to:
-their complexness (formulation - and calculation wise)
-the software application's file accessability (exe, dat, dll, ini etc.)
-the software system's operating environment + accessability (installed OS
+ disk access system)
-the PC hardware's accesability (installed Disk, Burst, RAM, Processor,
Motherboard)
-the read/write process (between Disk, RAM, Processor, Compilers for
translations etc.
and also v.v.) when running in the application(MetaStock) program
Regards,
Ton Maas
ms-irb@xxxxxxxxxxxxx
Dismiss the ".nospam" bit (including the dot) when replying.
----- Original Message -----
From: Christian Baude <BAUDECB@xxxxxxxxxxxxx>
To: <metastock@xxxxxxxxxxxxx>
Sent: donderdag 17 juni 1999 5:45
Subject: Re: Faster MS Win 6.5 Explorations Using Cache???
On Wed, 16 Jun 1999 20:32:17 -0700, Guy wrote:
>scratch area for calculations. In the WinDoze version, it appears that
they
>are using the hard disk for the scratch area (work area), and since I have
If someone knows where the scratch area is located, I may have a
solution (former TallTree systems Jet/RAMDISK user - I guess that
dates me <g>).
C:\WINDOWS\TEMP ?
-= Chris ? =-
Using MetaStock/FastTrack/FastRUBE/FastTools/EZPnF/TC2000/PSM
|