IO Magic 24x10x40 - Page 2

gh0sth@cker · #16 21-04-2002, 03:43

Quote:

Originally posted by samcboy

If burning takes long in x24 (which should take just over a minute)

It needs at least three minutes (and that really is MINIMUM if we are considering a full cd)

Maths:

1X = 150kb/s
24X = 3600kb/s

700Mb = 700,000Kb

700,000/3600 = 194.44444444444444444444444444444sec
that's 3mins and 14sec

and that's not taking into account that most drives write at 16X for the first few minutes of the disk, then move up to 20X, then move up to 24X. Then there's also lead in and lead out and the buffer underruns that may occur.
Rough estimate = 4mins 10sec for a 24X burn.

I believe your 20min burns at 24X are due to your slow system, but even when I was getting 300 buffer underruns it still only took about 10mins. Maybe the 10min difference is to do with out different drives. After ungrading my system it was cured - give it a go.

ryu2cool · #17 21-04-2002, 11:40

Ungrading your system? How did you ungrade it?

I took down some information while i was burning. I burned a data cd with 692 Mb or stuff w/ a TDK 80min/700Mb upto 24x CD.

So i burned one @ 24x, it took me around 13mins 21 sec. But buffer underrun was avoided 270 times.

Then i burned the exact same cd, except this time i burned it @ 20x. Which took about 13mins 22 secs. But with no buffer underruns.

Does that sound normal enough?

gh0sth@cker · #18 22-04-2002, 11:19

Quote:

Originally posted by ryu2cool
Ungrading your system? How did you ungrade it?

Added more memory, new processor, new motherboard, hell I stripped it all except for the hard drive (which is gonna go soon as I'm running out of space, 2Gb left outta 18Gb).

The 20X burn w/out buffer underruns at 13mins is not normal at all. Using the above calculation, the minimum burn for 20X would be 3mins 53sec (that's bear min)

podunkviller · #19 23-04-2002, 04:51

just to nitpick with you ghosthacker

1 KB = 1024 (2^10) bytes
1 MB = 1024*1024 (2^20)bytes

700 MB = 1024 * 700 KB

might change your math a bit

we damned engineers are detail people

gh0sth@cker · #20 23-04-2002, 10:45

1024 - true

samcboy · #21 23-04-2002, 20:26

The main rulz:

Don't have the CD Writer on the same channel as your source file. i.e have Hard drive on Primary master and nothing on slave, have writer on Secondary master and anything that u won't be using much if any on Secondary Slave

Reboot with blank CDR in writer, all other CDROM's empty, as soon as windows loads wait until it settles and then
launch writing software, write from compiled image file.

If you have any software that auto runs when windows starts, you should stop them by cutting them from the
start-up folder and pasting elsewhere.

Advanced rule, you can always try changing your system.ini VCACHE so that the system does'nt waste ram on junk file cache instead of CDROM cache.

podunkviller · #22 23-04-2002, 23:24

its a good 1 time fix.

ryu2cool · #23 24-04-2002, 06:42

Don't have the CD Writer on the same channel as your source file. i.e have Hard
drive on Primary master and nothing on slave, have writer on Secondary master
and anything that u won't be using much if any on Secondary Slave

Reboot with blank CDR in writer, all other CDROM's empty, as soon as windows
loads wait until it settles and then
launch writing software, write from compiled image file.

Huh?

Anyone care to explain?

podunkviller · #24 24-04-2002, 19:20

channel as in IDE cable, which are the things inside that you plug into your writers and hard drive to make sure they all communicate with your mobo. be specific about what you dont get please