• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

When your buring a CD does your system just about "freeze"?

J

joe4324

Senior member
I mean, I have a LiteOn 52x24x52 Burner in my system, And There seems to be very little speed difference between burning at 24x vs 48x. Both settings basicaly make my system unuseable for everything (including browsing) when they are burning. is this normal? I got a gig of ram and a 2Ghz AXP.... I dont think I'm lacking the power here, If my system has a hard time burning at 24x, who can burn at 52x? Is there something wrong with my settings? What are common mistakes made by people when running a burner? I'm not sure if DMA is enabled or not... what else can make a difference?

Anyone else have this problem? it sucks when you cant even play an mp3... is it just a priority issue?
 
Neither RAM size nor CPU speed help this any. It is all about I/O bandwidth and throughput.

My Duron-600 here lets me continue to work smoothly whilst burning at any speed. It's a Linux box, and it's all SCSI. As I said, it's an I/O throughput thing.
 
Go to Device Manager/HD#/Properties and check/enable DMA.

I use Nero set to run the burn from a large (full size=750Mb) cache. Make sure that burner is on a separate channel and jumpered correctly. I run a 1Gig Celeron and 384Mb memory and have no probs with responsiveness in XP.
 
You definitely shouldn't have a problem burning on that box. I have similar specs on my system and a Lite on drive that might be your exact one (52x24x52) and i can burn a cd and a dvd on my dvd rw drive and be encoding a dvd and still be doing plenty of other work w/ my grid program (DC like seti) putting all proc usage to 100% without feeling any lag (obviously the grid program throttles itself when necessary).
 
Originally posted by: Bassyhead
Sounds like your drive is operating in PIO mode, which uses a lot more CPU power than DMA.
Click to expand...

ehhh

no

see, PIO isnt related to cpu power, its related to data throughput on the IDE bus iirc, so the drive isnt working as fast and efficient as it should

bah
 
Are you burning from files on your hard drive? Or burning from a cd?
If burning from a cd, if you have your cdrom and your burner on the same ide channel, i believe that could be the problem.
Have you checked to make sure DMA is enabled on your hard drive?
Are you running win xp?
 
Originally posted by: xSauronx
Originally posted by: Bassyhead
Sounds like your drive is operating in PIO mode, which uses a lot more CPU power than DMA.
Click to expand...

ehhh

no

see, PIO isnt related to cpu power, its related to data throughput on the IDE bus iirc, so the drive isnt working as fast and efficient as it should

bah
Click to expand...

http://www.compguystechweb.com/troubleshooting/hardware/dma-pio.html

What is the PIO mode? When the system needs to access hard disk data, the CPU delivers input/output (I/O) orders through the chipset on the motherboard to the hard disk drive, and then puts this data into the system memory.
Click to expand...

http://www.veritest.com/bi/cont1998/199807/piodma.asp?visitor=

Programmable I/O (PIO) uses port I/O to transfer data to and from the drive. This method uses the processor continuously for the exchange. Direct Memory Access uses the disk controller to move data directly to memory without tying up the processor.
Click to expand...

PIO does require more CPU power than DMA?
 
PIO, as the name says, is Programmed I/O. The CPU does the data shoveling, and is 100 percent busy until it is done.

DMA, Direct Memory Access, lets the storage controller do the data movement. The CPU is notified of a finished transfer through an interrupt signal, and can go do other stuff meanwhile.
 
the cache size is the biggest reason after DMA not being set correctly. I use a gig on my rig. Made a lot of coasters before that and burnproof.
 
I'm still fighting with this, in my Bios DMA is set to "AUTO" I'm not in PIO mode, and my cache is 1024mb...

its pretty frustrating, all my jumpers are set to CS

not sure what to do here.
 
Change to jumper from CS to it's appropriate value (ie Master, Slave).
Look for an updated firmware.
Check you cables/connectors
Try different CDR's
Try different software
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top