Burning takes up CPU

[Jessica]

Whenever I use CloneCD to create an Image or burn an image (no my mom's computer)...it goes psycho. And it eats up every bit of processing it can. It wasnt like this a few days ago..The only thing that changed was the proxy on the other computer.

Also when burning w/ nero it eats up every bit it can too.

It makes doing anything while its brning ....rough.


AMD XP 1600
256MB DDR (-32 for video)
its a REALLY fast burner, which is why i use it...like 32x :P

anyway...its an emachin t1600 running
winXP pro on NTFS.....

any ideas?

[kamikazee]

Check your aspi layer, check and make sure DMA is enabled, and last but not least defragment your HD. and keep the multitasking down



Last edited by kamikazee at Sep 20 2002, 01:11 PM

[ecperez]

the higher the speed your burning the more resources will eat up...

[tubebuoy]

"Whenever I use CloneCD to create an Image or burn an image (no my mom's computer)...it goes psycho. And it eats up every bit of processing it can. It wasnt like this a few days ago..The only thing that changed was the proxy on the other computer."

I quote "It wasnt like this a few days ago..The only thing that changed was the proxy on the other computer."

So your Moms computer now screws up because you changed a proxy on another computer? Or did you change the proxy on your Moms computer? Please elaborate. Also, try to disable ALL other apps including your/her ISP and see what happens.

}---:?

[Sephiroth]

sounds like DMA isn't cut on on the burner, so try that :P

[FreeUS]

its just like ecperez said. When the cdrw run faster, more resources take. Try to use a 'normal' speed like x4 or x8

[kamikazee]

DMA is what allows you to burn without using cpu resources if this is unchecked then everything you burn is being helped and controlled by the cpu.. If you are using a via chipset then you may want to try the via 4 in 1 drivers, if you are using an intel chipset then you will need to try the intel application accelerator...along with everything else stated above

[just_do_IT]

Jessica,

If the only thing that changed was the proxy, then I would look there. The other suggestions are valid also - enable DMA to allow the data to be written directly from memory is alway a good thing to do. Diabling all unnecessary background programs and apps is a good idea as well.

Whatever you did with the proxy, reverse it and I bet your problem will be resolved. Did you change the ttl settings by any chance?