View Full Version : IMGBurn and multiple burners
setarip_old
14th October 2008, 22:15
Can IMGburn burn to two (or more) burners concurrently?
Inventive Software
15th October 2008, 00:58
Haven't tried it, but I know Nero has the feature. Why don't you give it a go? :)
LoRd_MuldeR
15th October 2008, 02:19
I don't see any option to burn to two burners at the same time in ImgBurn. Or did I miss some secret option? ^^
However it should be possible to run two instances of ImgBurn concurrently. I did not try it though...
setarip_old
15th October 2008, 02:30
@Inventive Software
Hi!I know Nero has the feature. Why don't you give it a go?Yes, I'm aware of that - and use that feature with DVD5s. However, NERO is "less than a certainty" when it comes to DVD9s...
blutach
15th October 2008, 06:55
I think you can run 2 instances, one to each burner. Try it.
Regards
setarip_old
15th October 2008, 07:36
@LoRd MuldeR
Hi!However it should be possible to run two instances of ImgBurn concurrently.Too risky - The idea of having two iterations accessing the same data at the same time for writing to two DVD9s at the same time is not for me...
(I don't understand why Post #5 was made - It just repeats what you'd already suggested almost 5 hours earlier)
smok3
15th October 2008, 08:32
do copy an image to different hd then, and only then run 2 instances.
setarip_old
15th October 2008, 08:36
@smok3
Hi!
Thanks, but I'm not really seeking alternative solutions. I was simply asking if (one instance of) IMGburn can burn to two burners concurrently...
blutach
15th October 2008, 08:41
No.
Regards
setarip_old
15th October 2008, 17:29
No.Thank you...
RunningSkittle
15th October 2008, 17:37
Two instances would not work. The HDD would be tied up with random accesses.
setarip_old
15th October 2008, 22:33
@RunningSkittle
That's why I said (In Post#6 of this thread):Too risky - The idea of having two iterations accessing the same data at the same time for writing to two DVD9s at the same time is not for me...
LoRd_MuldeR
15th October 2008, 23:15
@RunningSkittle
That's why I said (In Post#6 of this thread):
Are you sure with that? Shouldn't the filesystem cache (device cache + RAM) prevent HDD thrashing?
Also the danger of buffer underun caused by HDD thrashing can be reduced significantly by using a lower burn speed.
And last but not least even in case of an occasional buffer underun, the disc won't be destroyed if Burn-Proof is on.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.