A Hidden Patch Issue

[boleyd]

Patches of any size create a new problem - fragmentation. All that patch stuff is placed in the next free area to appear under the read/write head of you hard disk. All the new things are therefore, scattered about the disc - fragmented. This will be especially true if you patched from 49222. So defragment. I now I saw a lot of stuttering even after I loaded the program and allowed it time to gather pieces of scenery. The defrag showed it would take many hours to put Humpty Dumpty Together Again.

 

[shaneturner12]

That's to be expected for any process that moves a lot of files, not just patching. (and it's a reason why my defrag program runs when the system is idle).

Shane

 

[JCitron]

This is why I defrag after using Trainz too especially for route editing. There are so many files opened and written that the drive data can become fragmented. This of course only applies to platter drives and not SSDs. For those you need to run their appropriate utilities otherwise performance degradation and lifespan reduction can occur.

John

 

[KingConrail76]

Patches of any size create a new problem - fragmentation. All that patch stuff is placed in the next free area to appear under the read/write head of you hard disk. All the new things are therefore, scattered about the disc - fragmented. This will be especially true if you patched from 49222. So defragment. I now I saw a lot of stuttering even after I loaded the program and allowed it time to gather pieces of scenery. The defrag showed it would take many hours to put Humpty Dumpty Together Again.

Many would consider basic funtions, such as "Defragment", Computer Basics 101.
--I mean really, it is a "built-in" feature of Windows for a reason...and when used properly, along side Task Scheduler, you'll generally never need to "actively" defragment your system, with the exception of situations like running the huge SP1 patch...never needed to for the smaller Hot Fixes.