You can do it that way, but if you don't specify then by default PS
will use your systems swap file.
You can do it that way, but if you don't specify then by default PS
will use your systems swap file.
--Steve
> >*Theoretically*, Windows won't recognize a swap file bigger than 256 Mb,
but
> >the chipheads over on the flite sim forums will angrily disagree (some
> >problems w. B-17 can seemingly *only* be solved with a s.f. > 300
Mb...and
> >an AGP aperature of 64 Mb).
> Can you point me to any sites that state this to be true?
> >You don't want to leave it open ended, because, as said, Win will start
> >fragging it all over the disk, which will really slow it down, thus
killing
> >the idea for having it in the first place.
> With a fixed min and no max you won't see fragmenting in most cases,
> but will be ensured that you won't run into any problems if a game
> does require more than your fixed min. I can post urls that back this
> theory up if required.
As this is a brand new system and not overclocked, and has a huge heatsink
with two fans on it, I never gave the "heat" issue a thought. While messing
around on the net, I found that Gigabyte had a program for watching chip
temp along with some other resources. I down loaded it, installed it, ran
it, and there it was! chip temp 96c. Got it cooled to 70c now and its
working good.
I also had to install new VIA drivers which takes care of an issue with the
sound blaster live and the VIA KT133 chipset.
Thanks again Tom.
Mike
WHOA!!!! You're one lucky bloke, must've been a smidge away from a
fried CPU. What's the system temp? Must be pretty damn high to give
you such huge temps. There's still something not quite right at that
temp, the highest you should be looking at is a CPU temp in the 50's.
At first I thought you must've meant fareinheit, then I saw the c on
the end, and realised you were raosting CPU's!
Rafe Mc
Once the swap file reaches a specified max, you WILL get proggy
crashes. It won't "overwrite" older data that is still in use at the
start, only data that is no longer in use. Run any monitoring proggy,
like windows' "system monitor", use the "swap file in use" monitor,
and start opening programs. It'll increase it's usage within the file,
even tho the size remains static, the drop it (albeit more slowly tho)
as you close programs. If you hit the max, then you'll get out of
memory errors.
I don't think that an "open" sf is such a bad option, even though I
wouldn't use it personally. As long as the minimum is large enough so
as to be reached very infrequently (like 300-500mb). If the minimum is
never reached, then it'll act the same as a static sf anyway, more or
less. It could be defragged quite easily as long as it remains at it's
minimum size. I agree it'd fragment quickly as soon as the minimum was
breached however.
Like I said, I'll stick to my static sf tho. Each one to their own,
eh?
Rafe Mc
On Mon, 09 Jul 2001 20:55:12 GMT, "Stephen Smith"
>--Steve
>> On Sun, 08 Jul 2001 20:19:54 GMT, "Stephen Smith"
>> >*Theoretically*, Windows won't recognize a swap file bigger than 256 Mb,
>but
>> >the chipheads over on the flite sim forums will angrily disagree (some
>> >problems w. B-17 can seemingly *only* be solved with a s.f. > 300
>Mb...and
>> >an AGP aperature of 64 Mb).
>> Can you point me to any sites that state this to be true?
>> >You don't want to leave it open ended, because, as said, Win will start
>> >fragging it all over the disk, which will really slow it down, thus
>killing
>> >the idea for having it in the first place.
>> With a fixed min and no max you won't see fragmenting in most cases,
>> but will be ensured that you won't run into any problems if a game
>> does require more than your fixed min. I can post urls that back this
>> theory up if required.
>> Besides, if you don't specify a maximum, it's a
>>>little hard to get yer defragger to put *some* of it (how much?) at the
>>>front of the disk, eh?
>Why? If you specify a minimum you will see a permannet swap file on
>your hard drive just like if you have specified a min/max. If you use
>a defragger like Norton you can also specify where on the HD this file
>resides. As I said, make it big enough so that you rarely, if ever, go
>over this amount. I find using 300mb is working well for me. I just
>read about this method recently so haven't been using it for long, but
>I like it so far because it doesn't fragment and still protects me
>from possible out of memory errors.
> **GeForce 2 (MX, GTS, ULTRA) and GeForce 3***
> "Tweaks and Settings" for N4
> ****************
> General Settings
> ****************
> **Desktop Color: Set to 16-bit color.
> **DirectX: Use a DX 8.0 compatible driver(NvRef drivers 7.0 or higher,
12.0
> and up for GF3 cards).
> **OpenGL or D3D?: Run OpenGL for N4 in "XXXX"x16 (use a res compatible
with
> your CPU speed and ram).
> **Monitor: Obtain the latest drivers for your monitor...DO NOT USE
Windows
> "Plug and Play" monitor drivers! Set your refresh rate at the highest
> setting you are allowed for your monitor at the specific screen res you
run
> N4 at.
> ********************************
> Advanced Settings Tab For OpenGL
> ********************************
> In The Scroll Down Box:
> [*]Enable Buffer Region Extension. (Checked)
> [*]Allow the dual planes extension to us local video memory. (Checked)
> [*]Use fast linear-mipmap-linear filtering. (Checked)
> [ ]Enable anistropic filtering. (Unchecked)
> Individual Scroll Down Boxes:
> Default Color Depth for Textures: [Always Use 16 bpp]
> Buffer Flipping Mode: [Use page flip]
> Vertical sync: [Always off]
> Full Scene Antialiasing Method: [Always off]
> (note: this is not here on a GF3 card which has its own antialiasing
> screen)
> Use up to [62] MB of system memory for textures in PCI mode.
> **************************
> Mother Board BIOS Settings
> **************************
> Video BIOS Shadow............[Disabled]
> Video BIOS Cache.............[Disabled]
> Palette Snoop................[Disabled]
> AGP Turbo (or Fast Write)....[Enabled]*
> AGP Aperture Size (MB).......[128]*
> AGP ISA Aliasing.............[Disabled]*
> AGP Secondary Lat Timer......[20h]*
> AGP Data Transfer Mode.......[4x]*
> K7 Clk_Cntrl Select..........[Optimal]*
> PnP Aware OS.................[Yes]
> Resources Controlled by......[Auto]
> Assign IRQ to VGA............[Yes]
> Note: (*) Items above will appear only on mobos with 2x compliant AGP bus.
> If you don't have one of these mobos now, DO NOT waste your time and money
> to purchase a fast Nvidia card....its a complete waste!
> DO NOT FLASH or upgrade your system BIOS UNLESS YOU ARE HAVING PROBLEMS
WITH
> YOUR MOBO....that are **specifically addressed** in the BIOS upgrade (see
> the Readme.txt file for your BIOS flash upgrade). Flashing your system
BIOS
> is risky business....and you can render your mobo completely inoperable if
> you screw even the slightest thing up in following the steps. You've been
> warned! Ask Dave Henrie!
> ********************
> Mobo Chipset Drivers
> ********************
> Your mobo contains two "chips" similar to your CPU chip (but smaller) that
> control all the functions of your mobo (system bus, AGP bus, IDE
> controllers, etc.). The one located closest to the CPU is called the
> "northbridge" chip, and the one furthest away is called the "southbridge"
> chip. The northbrigde chip is very important for video graphics since it
> controls the system bus and AGP bus (among others). THE SINGLE MOST
> IMPORTANT THING YOU CAN DO FOR YOUR GRAPHIC'S CARD SPEED AND STABLE
> OPERATION IS INSTALL AND MAINTAIN THE CHIPSET DRIVERS IN THE LATEST
**DRIVER
> VERSION**. This applies to Intel and AMD platforms, but is critical in
all
> AMD platforms!
> There are several "chipset" manufacturers and you must determine which one
> you have on your mobo. I can tell you that VIA is the most popular, but
ALI
> and AMD also make chipsets. Once you've determined which you have, go to
> that manufacturer's website (bookmark it...you will need to check for
> version updates atleast monthly). Download and very carefully install the
> latest chipset drivers for your mobo. This is an area where I have seen
the
> most improvement in frame rates and graphic quality. DO NOT DO THIS
> CASUALLY.....READ AND FULLY UNDERSTAND WHAT AND HOW YOU ARE TO INSTALL
THESE
> CHIPSET DRIVERS!
> Chipset drivers can easily get corrupted with normal
> operations....especially running a lot of pc games. I install mine every
> week.....whether needed or not. You can "over-write" install them....its
> very simple to do once you have the routine down.
> *******************************
> Windows Virtual Memory Settings
> *******************************
> Many sim racers have had problems with "screen stutter"....usually
occuring
> as the car is entering a turn. This happens at this point because the FPS
> slows....just as the requirements for a faster FPS are greater (when
> turning...the screen is rapidly changing the scenery and background). If
> your system is at the same time accessing the Windows Swap file (located
on
> your hard-drive)....you can get this screen stutter (a brief, usually less
> than a second "freeze" of the screen). This can occur independently of
the
> type of video card you use....and the amount of system RAM (although that
> doesn't totally make sense to me....but I get this screen stutter on both
my
> systems, one has 512 MB of ram, the other has 738 MB of ram...so go
> figure?).
> One way to reduce or eliminate this problem is to remove Windows from
> control of your Virtual Memory (that's the swap file). Windows will
> increase and decrease it as needed (on your hard drive)....and as that
area
> of your hard drive becomes fragmented, Windows doesn't clean it up for you
> (nor does defragmenting your hard drive....that only defragments the area
of
> the hard drive outside of this swap file)...it will just keep taking more
> and more drive space to satisfy its (often incorrect) evaluation of how
much
> "virtual memory" it needs for the ops you are running.
> The **Quick Fix**.....is to take control of your Swap File hard drive
space
> allocation. To do this, follow these directions:
> 1. Go to the "Windows Virtual Memory" settings box (right click "My
> Computer" -select- "Properties" - select- "Performance Tab" -select-
> "Virtual Memory" [button] on lower right side of box.
> 2. Select "Let me specify my own Virtual Memory settings." bullet.
> 3. Set the Minimum and Maximum **to the same value**....this is very
> important! [This will keep the swap file from being re-sized all the
time.]
> 4. Set the value at something between 2x to 4x your physical RAM memory
> (remember the Value is entered in KB, not MB). Example: With 128 MB ram,
at
> 2.5xRAM = 320 MB (entered as: 3200 KB in the box).
> 5. Restart your computer as Windows requests.
> 6. Go back and make sure the settings you made are still there....and
> check this regularly. Windows has a nasty habit of deleting this stuff
all
> the time....and taking back over the management of VM. I've never been
able
> to figure out a "pattern" for when Windows does this....I just know that
> half the time....when I check this.....Windows has taken back control of
VM
> and I have to reset it to the above settings.
> ***DOING THIS WILL SOLVE THE N4 FRAME STUTTER......assuming you have no
> other "issues" with IRQ sharing and so forth. I also found this solves
the
> same problem in GPL...when using the high-res cockpits and race tracks.
> The **Long-Term Fix**.....is to purchase software that will allow you to
> defragment the area of your hard-drive that is allocated for the swap
file.
> These programs can also allow you to partition your HD so you can locate
the
> swap file in this partition, which will reduce resizing and fragmentation
> even further. There are several programs to do this, ask around. I don't
> use them, because I just "fdisk" and "format C" my HD regularly....having
a
> "clone" of my "race box" system and programs on a CD. Its much easier,
and
> completely refreshes my system (I usually do this monthly).
> ***********************************************************
> HEAT....It Is Now A Major Issue - What You Can Do About It!
> ***********************************************************
> This has become a major issue, even though the computer manufacturers do
not
> want to make that public. If you are regularly playing 3D games, or sim
> racing weekly or daily.....the biggest favor you can do for yourself is
deal
> with the heat issue now!
> The Heat Rule: The hotter your computer runs (CPU, mobo circuitry, video
> card chips and circuitry, other PCI card chips and circuitry)....THE
SLOWER
> YOUR COMPUTER RUNS!
> I don't mean "a little slower" either....its a BIG-Time a lot slower!
> Example: My systems gets scores of around 9200 on 3DMark2000. If I turn
> off all my fans (except the CPU fan...never turn it off)....wait 10 mins,
> then run 3DMark2000.....the best score I get is in the low 7000's. If you
> think "heat" is not an issue...you are kidding yourself.
> If you are running an AMD platform, and an Nvidia GF2 or GF3.....if you
> don't adequately cool your cards and CPU case....you are just wasting time
> and money.....go buy a Compaq or HP computer and write email to
> someone.....stop sim racing! .....lol.... Your system will be "buggy and
> slow"....for ever (until it fails).
> ****The Good News Is You Don't Have To Be A Computer "Techy" To Fix
> This****
> This stuff is NOT....high-tech stuff. First of all, I buy all my fans and
> cooling devices, temp gauges etc. at one place. www.3dfxcool.com Its a
> small company, run from home (Seattle). I have been buying fans from Bart
> and his wife since the late 90's and they are the best...and best value.
> You can purchase fans anywhere, and its not a "high-dollar" item anyway.
> The better the fan, the more air it pushes, the longer it lasts, and the
> quieter it is. The worst 90mm case fan you can
read more »
**************************