I've been using this product with great success for a while now and I've just today solved a problem I was having with it simply stopping part way through a conversion. I realize I'm pretty far behind the PC power curve, but such is life and I thought this might help somebody. Not strictly overclocked, my CPU is running at 2340 MHz on stock voltage: I raised the FSB to 180. The fix for the stoppages (other than dropping the FSB back to 166) was to set my page file to zero on all drives. This is recommended only if you have at least 1GB RAM which I do. I couldn't tell you why, but on my machine this ended my problem. My computer: Abit KW7 motherboard AMD Athlon XP 3000+ 333 MHz FSB (running at 360) 1GB Corsair PC3200 value RAM Twin Seagate 320GB hard drives 8x AGP with 128MB Windows XP SP2 Fully patched
we are running similar systems I have the amd sempron 3000 2.ghz,with fsb set to 166 for 333mhz, I went from 1gb to 2gb ram pc27000 at 333mhz and wow my vso conversions take tops 1hr 15minutes or less depending on the movie and its size but it sure made and improvement my system is not overclocked at all. I haven't played with my paging file but being as I have enough ram mmmm might have to fiddle to see what I get.
@mystice what part removing paging files or fsb changes ? can you tell me I have never altered my paging files except when I wont to defrag them I turn them off and then back on for t that
It's best to have a page file (Virtual Memory), even if it's a small one. I actually have 2, one on my C drive (300MB) and another on my second HD (Windows managed). In actuality 'Virtual Memory' is always in operation and cannot be turned off. Eliminating the page file does not eliminate Virtual Memory calls by programs. The reason is that when programs ask for an allocation of Virtual Memory space, they usually ask for more than they ever actually ever need, kind of a cushion or reserve. These addresses have to be assigned somewhere by the system. Without a page file these calls are now stored in RAM. Doing this would waste a lot of the RAM which is better used for processing rather than Virtual Memory calls. If there is a page file available, the system can assign them to it (note many times these are not actually used or 'swapped' in and out they just take up space, the major exception being games), with no page file they have to be assigned to RAM, locking it out from any actual use. Back to your original post I admire your desire to share a solution to a problem with others here. I'm glad it's working for you, but I just don't quite understand how, and believe a page file of some sort, regardless of installed RAM is needed.
