Jump to content

Recommended Posts

Posted

Since I don't work with iso's very much , the build mode really made the program much more useful, however this guide

needs to be expanded to include output > device(build on the fly?)

 

http://forum.imgburn.com/index.php?showtopic=1778

 

or a more detailed single layer guide like the dual layer guide

 

it's hard to switch someone over from programs that ask you what you want to burn and then you just add files

 

 

Is booktyping included in the burn log of the beta?

 

Is there a conflict when using the test feature and having disable media change notification enabled and/or having autoinsert

notification disabled?

 

It completely locked up my benq 1620 and imgburn after cycling tray.

Posted

Single layer and double layer ones are the same apart from the layer break box that pops up.

 

Just as building an image file / buring direct are the same, all you do really is change the output.

 

I guess if enough people really don't understand it, we should indeed do some extra guides.

 

No booktyping isn't mentioned in the log and probably won't be. It doesn't really add anything useful and if it's not set, it's too late anyway!

 

No there's no conflict.

Posted

well I noticed that verify does list the booktype so I guess that's good enough in troubleshooting a beginner's log

 

No there's no conflict.

 

I still can't figure that one out, I will return the settings made with clonecd and imgburn to default and retest with the lone tyg02 blank I have left

Posted

I think he was pulling my leg, that's ok noobs :whistling: should use verify till they get the bugs out :thumbup: and the log shows bitsetting then

Posted (edited)

well I returned settings to default in imgburn and same for clonecd with autoinsert/autoplay

 

rebooted and put my tyg02 back in my benq 1620

 

did a build and set output to device, checked test mode and let her rip

 

Imgburn did the test, cycled tray and then the drive just kept blinking, after a couple of minutes it stopped, imgburn had no log and no program would see the empty disk, after cycling tray manually the drive light would blink forever.

 

After removing disk and a cold restart(shut down/boot) the drive and disk would work???????????????????????

 

BENQ DVD DD DW1620 B7W9 (ATA)

Current Profile: DVD-R

 

Disc Information:

Status: Empty

Erasable: No

Free Sectors: 2,298,496

Free Space: 4,707,319,808 bytes

Free Time: 510:48:46 (MM:SS:FF)

 

Pre-recorded Information:

Manufacturer ID: TYG02

 

Physical Format Information (Last Recorded):

Book Type: DVD-R

Part Version: 5

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 1

Track Path: Parallel Track Path (PTP)

Linear Density: 0.267 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 0

Last Physical Sector in Layer 0: 0

 

testing with nec 3550 next

Edited by chewy
Posted

ImgBurn doesn't rely on autoinsert *at all*. It does it's own polling to see if the drive is 'ready' or not.

 

Same goes for most programs I expect - apart from Explorer itself of course.

 

So if ImgBurn couldn't see the disc afterwards I'd have to say the drive or drivers messed up somewhere along the way. If the light is flickering non-stop, I'd lean towards the drive.

Posted (edited)

I 06:05:03 ImgBurn Version 2.3.2.0 started!

I 06:05:03 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 06:05:03 Total Physical Memory: 523,764 KB - Available: 331,436 KB

I 06:05:03 Initialising SPTI...

I 06:05:03 Searching for SCSI / ATAPI devices...

I 06:05:03 Found 2 DVD±RWs!

I 06:05:50 Operation Started!

I 06:05:50 Building Image Tree...

I 06:05:56 Checking Directory Depth...

I 06:05:56 Calculating Totals...

I 06:05:56 Preparing Image...

I 06:05:56 Checking Path Length...

I 06:05:56 Image Size: 4,362,797,056 bytes

I 06:05:56 Image Sectors: 2,130,272

I 06:05:58 Operation Successfully Completed! - Duration: 00:00:08

I 06:05:58 Operation Started!

I 06:05:58 Source File: -==/\/[bUILD IMAGE]\/\==-

I 06:05:58 Source File Sectors: 2,130,272 (MODE1/2048)

I 06:05:58 Source File Size: 4,362,797,056 bytes

I 06:05:58 Source File Volume Identifier: tsm

I 06:05:58 Source File Application Identifier: IMGBURN V2.3.2.0 - THE ULTIMATE IMAGE BURNER!

I 06:05:58 Source File Implementation Identifier: ImgBurn

I 06:05:58 Source File File System(s): ISO9660, UDF (1.02)

I 06:05:58 Destination Device: [1:0:0] _NEC DVD_RW ND-3550A 1.Y6 (G:) (ATA)

I 06:05:58 Destination Media Type: DVD-R (Disc ID: TYG02) (Speeds: 2x, 4x, 6x, 8x, 12x)

I 06:05:58 Destination Media Sectors: 2,297,888

I 06:05:58 Write Mode: DVD

I 06:05:58 Write Type: DAO

I 06:05:58 Write Speed: 8x

I 06:05:58 Link Size: Auto

I 06:05:58 Test Mode: Yes

I 06:05:58 BURN-Proof: Enabled

I 06:05:59 Filling Buffer... (20 MB)

I 06:06:00 Writing LeadIn...

I 06:06:21 Writing Image... (LBA: 0 - 2130271)

I 06:14:49 Synchronising Cache...

I 06:15:08 Cycling Tray after Test Write...

I 06:15:26 Image MD5: c9037e23f310822bb931c7ecf5f2fba9

I 06:15:26 Operation Successfully Completed! - Duration: 00:09:27

I 06:15:26 Average Write Rate: 8,403 KB/s (6.1x) - Maximum Write Rate: 11,500 KB/s (8.3x)

 

thought it might be the damn nf2 chipset but they are running ms sp2 default drivers

Edited by chewy
Posted

forgot to turn verify on so I could check the function after tray cycling?

 

ImgBurn Version 2.3.2.0 - Log

; Monday, 13 August 2007, 06:27:56

; \\****************************************//

;

;

I 06:18:21 ImgBurn Version 2.3.2.0 started!

I 06:18:21 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 06:18:21 Total Physical Memory: 523,764 KB - Available: 332,816 KB

I 06:18:21 Initialising SPTI...

I 06:18:21 Searching for SCSI / ATAPI devices...

I 06:18:21 Found 2 DVD±RWs!

I 06:19:11 Operation Started!

I 06:19:11 Building Image Tree...

I 06:19:13 Checking Directory Depth...

I 06:19:13 Calculating Totals...

I 06:19:13 Preparing Image...

I 06:19:13 Checking Path Length...

I 06:19:13 Image Size: 4,521,295,872 bytes

I 06:19:13 Image Sectors: 2,207,664

I 06:19:15 Operation Successfully Completed! - Duration: 00:00:04

I 06:19:15 Operation Started!

I 06:19:15 Source File: -==/\/[bUILD IMAGE]\/\==-

I 06:19:15 Source File Sectors: 2,207,664 (MODE1/2048)

I 06:19:15 Source File Size: 4,521,295,872 bytes

I 06:19:15 Source File Volume Identifier: 300

I 06:19:15 Source File Application Identifier: IMGBURN V2.3.2.0 - THE ULTIMATE IMAGE BURNER!

I 06:19:15 Source File Implementation Identifier: ImgBurn

I 06:19:15 Source File File System(s): ISO9660, UDF (1.02)

I 06:19:15 Destination Device: [0:0:0] BENQ DVD DD DW1620 B7W9 (F:) (ATA)

I 06:19:15 Destination Media Type: DVD-R (Disc ID: TYG02) (Speeds: 2.4x, 4x, 8x, 12x, 16x)

I 06:19:15 Destination Media Sectors: 2,298,496

I 06:19:15 Write Mode: DVD

I 06:19:15 Write Type: DAO

I 06:19:15 Write Speed: 8x

I 06:19:15 Link Size: Auto

I 06:19:15 Test Mode: No

I 06:19:15 BURN-Proof: Enabled

I 06:19:15 Filling Buffer... (20 MB)

I 06:19:16 Writing LeadIn...

I 06:19:31 Writing Image... (LBA: 0 - 2207663)

I 06:26:52 Synchronising Cache...

I 06:27:17 Image MD5: 5f0e08333098916e664a9e305cc5020d

I 06:27:17 Operation Successfully Completed! - Duration: 00:08:01

I 06:27:17 Average Write Rate: 10,012 KB/s (7.2x) - Maximum Write Rate: 11,106 KB/s (8.0x)

I 06:27:56 Close Request Acknowledged

I 06:27:56 Closing Down...

I 06:27:56 Shutting down SPTI...

I 06:27:56 ImgBurn closed!

;

Posted (edited)
Think you may not get to bottom of it unless you have a clean install

 

now donta if you knew what it took to get this damn Sil 3112 raid chipset working right you wouldn't even joke about that,

it took sil 2-3 years to solve the driver problem

Edited by chewy
Posted

only thing? verify takes an extra minute with the drive??????

 

I 07:01:46 Average Verify Rate: 7,743 KB/s (5.6x) - Maximum Verify Rate: 11,154 KB/s (8.1x)

 

 

guess the drive doesn't like test mode at all

Posted

So basically you're saying the BenQ 1620 won't read the disc properly once you've done a burn with test mode enabled?

 

I don't really understand the significance of the other stuff you've posted.

Posted

I was trying to isolate the problem, seems like it's the drive not the computer, but the drive is burning and verifying ok?

 

what does imgburn do in test mode after cycling the tray?

Posted

Test mode is no different to normal. There's just one command sent at the start of the burn (set write parameters) that has the 'test mode' flag set to 1 rather than 0.

 

After the tray is cycled, it doesn't do anything. That's the end of the process.

 

I 12:44:41 ImgBurn Version 2.3.2.9 Beta started!

I 12:44:41 Microsoft Windows Server 2003, Standard Edition (5.2, Build 3790 : Service Pack 2)

I 12:44:41 Total Physical Memory: 3,406,216 KB - Available: 1,524,260 KB

I 12:44:41 Initialising SPTI...

I 12:44:41 Searching for SCSI / ATAPI devices...

I 12:44:42 Found 4 DVD-ROMs, 2 DVD±RWs and 4 DVD±RW/RAMs!

I 12:44:56 Operation Started!

I 12:44:56 Source File: -==/\/[DISCOVERY IMAGE]\/\==-

I 12:44:56 Source File Sectors: 2,298,496 (MODE1/2048)

I 12:44:56 Source File Size: 4,707,319,808 bytes

I 12:44:56 Source File Volume Identifier: DISCOVERY_IMAGE

I 12:44:56 Source File File System(s): None

I 12:44:56 Destination Device: [5:2:0] BENQ DVD LS DW1655 BCIB (I:) (SCSI)

I 12:44:56 Destination Media Type: DVD-R (Disc ID: TYG02) (Speeds: 2.4x, 4x, 8x)

I 12:44:56 Destination Media Sectors: 2,298,496

I 12:44:56 Write Mode: DVD

I 12:44:56 Write Type: DAO

I 12:44:56 Write Speed: 8x

I 12:44:56 Link Size: Auto

I 12:44:56 Test Mode: Yes

I 12:44:56 BURN-Proof: Enabled

I 12:44:56 Advanced Settings: [benQ] -> OverSpeed: No, Solid Burn (K/M): No, Solid Burn (U/M): Yes, WOPC: No

I 12:44:56 Filling Buffer... (40 MB)

I 12:44:56 Writing LeadIn...

I 12:45:09 Writing Session 1 of 1... (1 Track, LBA: 0 - 2298495)

I 12:45:09 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2298495)

I 12:52:17 Synchronising Cache...

I 12:52:51 Cycling Tray after Test Write...

I 12:52:56 Exporting Graph Data...

I 12:52:56 Graph Data File: C:\Documents and Settings\Administrator\Application Data\ImgBurn\IBG Files\BENQ_DVD_LS_DW1655_BCIB_13-AUGUST-2007_12-44_TYG02_8x.ibg

I 12:52:56 Export Successfully Completed!

I 12:52:56 Operation Successfully Completed! - Duration: 00:08:00

I 12:52:56 Average Write Rate: 10,765 KB/s (7.8x) - Maximum Write Rate: 11,185 KB/s (8.1x)

 

Info taken from the info panel after test mode burn

 

BENQ DVD LS DW1655 BCIB (SCSI)

Current Profile: DVD-R

 

Disc Information:

Status: Empty

Erasable: No

Free Sectors: 2,298,496

Free Space: 4,707,319,808 bytes

Free Time: 510:48:46 (MM:SS:FF)

Supported Write Speeds: 2.4x, 4x, 8x

 

Pre-recorded Information:

Manufacturer ID: TYG02

 

Physical Format Information (Last Recorded):

Book Type: DVD-R

Part Version: 5

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 1

Track Path: Parallel Track Path (PTP)

Linear Density: 0.267 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 0

Last Physical Sector in Layer 0: 0

Posted
I always verify. Noobs or not, I recommend it.

 

Regards

 

Good advice, I have always verified right back from when I started with ImgBurns predecessor, after all I am not so busy that I can't spare a few more minutes :)

Posted

with my old toshiba standalone player, I have found doing a pie/pif quality scan to be more reliable than a verify

 

a disk that verified would have a terrible scan and have playability problems

 

using premium media I have found both to be a waste of time

Posted

Yeah ? Mmm I don't see any problems with my setup on discs that have passed an ImgBurn verify, maybe if I did then I would I need to look at those again then. The way I work is that I use ImgBurn to burn and verify and then if there are problems I look at PI/PIF scans to see how bad things really are :)

Posted (edited)

my toshiba had gotten pretty dirty and I was using marginal blanks, noticed some artifacts when viewing the burn on the standalone.

 

my point about verify is also a disk may be a lousy burn and pass and then not play next year, the quality scan seems to be a better indicator of longevity, going on the assumption that disks degrade over time

 

what % of your burns fail verify?

Edited by chewy
Posted

Remember that the verify will spot issues a scan will not.

 

i.e. differences between the disc and the image. This could be due to bad memory, overclocking or some other corruption on the bus (cable maybe).

 

It's also much easier to understand that an error during verify means your disc is no use, rather than trying to understand what a scan shows with all the pretty graph colours and numerical values.

 

Verify also runs on all hardware, a scan does not.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.