I have always heard beautiful things about BAO and have decided to give it a try. I have screwed a DVD-R in Nero 6 and have uninstalled it, installed ForceASPI and installed BAO 0.99b.
I was going to burn 6 movies (DiVX) in a DVD-R on my Pioneer A04 drive. I have done everything and started burning...
I then moved the BAO windows to a side in my screen and while doing this I noticed that THE LIGHT ON THE DVD-R DRIVE went OFF! I begin to panic and released the left mouse button. The disk is still burning but I am starting to think that it is going to be a cosater
Question: How a so critical program (I mean, burning is a critical function) gets blocked because the user moves its GUI window???? The last time that I saw this behavor was LONG TIME AGO in the first days of Windows 98 and with Adaptec EZ CD Cremator! Since then I have used several burning applications (Nero, Clone, Alcohol and others) and NEVER moving the GUI window affects the burning process. This looks to me like a real and BIG bug in the program. I am no developer, but it seems quite logical that the program window must be totally independent of the burning process, and it must not be perturbed by anything happening on the screen.
I would like to see your opinion about this, sure that you could say "just DON'T play with the program window while burning" but I think that it should not affect.
This is the log from BAO, not aparent errors here, the burning process is over but I have not tested the disc yet:
(I wonder why Burn free was turned off as shown by the log)
---------------------
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to <warly@mandrakesoft.com>.
Note: The author of cdrecord is not to be bothered with problems in this version.
TOC Type: 1 = CD-ROM
Using libscg version 'rs-0.7+'
Driveropts: 'burnfree'
atapi: -1
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'PIONEER '
Identifikation : 'DVD-RW DVR-104 '
Revision : '1.41'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0011
Profile: 0x0014
Profile: 0x0013
Profile: 0x0011 (current)
Profile: 0x0010
Profile: 0x000A
Profile: 0x0009
Profile: 0x0008
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags : SWABAUDIO BURNFREE
Supported modes: PACKET SAO
Drive buf size : 1638400 = 1600 KB
FIFO size : 180633600 = 176400 KB
Track 01: data 4445 MB
Total size: 5105 MB (505:49.30) = 2276198 sectors
Lout start: 5105 MB (505:51/23) = 2276198 sectors
Current Secsize: 2048
ATIP start of lead in: -150 (00:00/00)
Disk type: unknown dye (reserved id code)
Manuf. index: -1
Manufacturer: unknown (not in table)
Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 22298
Starting to write CD/DVD at speed 2 in real SAO mode for single session.
Waiting for reader process to fill input buffer ... Turning BURN-Free on
input buffer ready.
trackno=0
BURN-Free is ON.
Turning BURN-Free off
BURN-Free is OFF.
Performing OPC...
Sending CUE sheet...
Starting new track at sector: 0
Track 01: Total bytes read/written: 4661653504/4661653504 (2276198 sectors).
Writing time: 1674.336s
Average write speed 18.2x.
Min drive buffer fill was 68%
Fixating...
Fixating time: 48.041s
fifo had 73426 puts and 73426 gets.
fifo was 0 times empty and 17889 times full, min fill was 96%.
---------------------
I was going to burn 6 movies (DiVX) in a DVD-R on my Pioneer A04 drive. I have done everything and started burning...
I then moved the BAO windows to a side in my screen and while doing this I noticed that THE LIGHT ON THE DVD-R DRIVE went OFF! I begin to panic and released the left mouse button. The disk is still burning but I am starting to think that it is going to be a cosater
Question: How a so critical program (I mean, burning is a critical function) gets blocked because the user moves its GUI window???? The last time that I saw this behavor was LONG TIME AGO in the first days of Windows 98 and with Adaptec EZ CD Cremator! Since then I have used several burning applications (Nero, Clone, Alcohol and others) and NEVER moving the GUI window affects the burning process. This looks to me like a real and BIG bug in the program. I am no developer, but it seems quite logical that the program window must be totally independent of the burning process, and it must not be perturbed by anything happening on the screen.
I would like to see your opinion about this, sure that you could say "just DON'T play with the program window while burning" but I think that it should not affect.
This is the log from BAO, not aparent errors here, the burning process is over but I have not tested the disc yet:
(I wonder why Burn free was turned off as shown by the log)
---------------------
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to <warly@mandrakesoft.com>.
Note: The author of cdrecord is not to be bothered with problems in this version.
TOC Type: 1 = CD-ROM
Using libscg version 'rs-0.7+'
Driveropts: 'burnfree'
atapi: -1
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'PIONEER '
Identifikation : 'DVD-RW DVR-104 '
Revision : '1.41'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0011
Profile: 0x0014
Profile: 0x0013
Profile: 0x0011 (current)
Profile: 0x0010
Profile: 0x000A
Profile: 0x0009
Profile: 0x0008
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags : SWABAUDIO BURNFREE
Supported modes: PACKET SAO
Drive buf size : 1638400 = 1600 KB
FIFO size : 180633600 = 176400 KB
Track 01: data 4445 MB
Total size: 5105 MB (505:49.30) = 2276198 sectors
Lout start: 5105 MB (505:51/23) = 2276198 sectors
Current Secsize: 2048
ATIP start of lead in: -150 (00:00/00)
Disk type: unknown dye (reserved id code)
Manuf. index: -1
Manufacturer: unknown (not in table)
Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 22298
Starting to write CD/DVD at speed 2 in real SAO mode for single session.
Waiting for reader process to fill input buffer ... Turning BURN-Free on
input buffer ready.
trackno=0
BURN-Free is ON.
Turning BURN-Free off
BURN-Free is OFF.
Performing OPC...
Sending CUE sheet...
Starting new track at sector: 0
Track 01: Total bytes read/written: 4661653504/4661653504 (2276198 sectors).
Writing time: 1674.336s
Average write speed 18.2x.
Min drive buffer fill was 68%
Fixating...
Fixating time: 48.041s
fifo had 73426 puts and 73426 gets.
fifo was 0 times empty and 17889 times full, min fill was 96%.
---------------------
Last edited: