Invalid Field in CDB - Problem burning game

[maxlamb1]

Hey y'all, I'm trying to burn Sega CD games using Verbatim CD-Rs, and I can't figure out what's happening with this message:

Close Track Failed!

Device: [0:0:0] ASUS DRW-24F1ST   c 1.00 (E:) (SATA)

Reason: Invalid Field in CDB

I've used the machine a few times before to burn games for the system, but these are both different kinds of discs and different cue files (ccd this time...does it work the same for ccd as it does for cue files?). Here's the log:
 

I 13:10:02 Operation Started!

I 13:10:02 Source File: C:\Users\Maxwell\Downloads\Advanced Dungeons & Dragons - Eye of the Beholder (USA)\Advanced Dungeons & Dragons - Eye of the Beholder (USA).ccd

I 13:10:02 Source File Sectors: 0 (AUDIO/2352)

I 13:10:02 Source File Size: 0 bytes

I 13:10:02 Source File File System(s): None

I 13:10:02 Destination Device: [0:0:0] ASUS DRW-24F1ST   c 1.00 (E:) (SATA)

I 13:10:02 Destination Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.)

I 13:10:02 Destination Media Supported Write Speeds: 16x, 24x, 32x, 40x, 48x

I 13:10:02 Destination Media Sectors: 359,844

I 13:10:02 Write Mode: CD

I 13:10:02 Write Type: SAO

I 13:10:02 Write Speed: 16x

I 13:10:02 Lock Volume: Yes

I 13:10:02 Test Mode: No

I 13:10:02 OPC: No

I 13:10:02 BURN-Proof: Enabled

I 13:10:02 Write Speed Successfully Set! - Effective: 2,823 KB/s (16x)

W 13:10:02 Write Type: TAO

I 13:10:02 Filling Buffer... (80 MiB)

I 13:10:02 Writing LeadIn...

I 13:10:02 Synchronising Cache...

I 13:10:03 Closing Track...

I 13:10:04 Synchronising Cache...

I 13:10:05 Closing Track...

W 13:10:05 Close Track Failed! - Reason: Invalid Field in CDB

W 13:10:05 Retrying (1 of 3)...

W 13:10:05 Retry Failed - Reason: Invalid Field in CDB

W 13:10:05 Retrying (2 of 3)...

W 13:10:06 Retry Failed - Reason: Invalid Field in CDB

W 13:10:06 Retrying (3 of 3)...

W 13:10:06 Retry Failed - Reason: Invalid Field in CDB

E 13:10:07 Close Track Failed! - Reason: Invalid Field in CDB

I 13:10:07 Closing Track (Last Attempt!)...

E 13:10:07 Close Track Failed! - Reason: Invalid Field in CDB

I 13:10:07 Synchronising Cache...

W 13:10:11 User opted to skip the 'Close Track/Session/Disc' functions.

E 13:10:11 Failed to Write Image!

E 13:10:11 Operation Failed! - Duration: 00:00:08

I 13:10:11 Average Write Rate: N/A - Maximum Write Rate: N/A

Any help would be appreciated! I browsed similar posts, but couldn't find an answer that quite matched my problem.

[LIGHTNING UK!]

Your image file seems invalid... look at the size of it.

[maxlamb1]

Ahhh. Weird. They're all giving the same message too. The ccd is supposed to act as a cue for the actual disc image, right?

[LIGHTNING UK!]

Yes. Do you have a valid .BIN file alongside your .CCD? (with the exact same name, excluding the extension)

 

How big is it?

[maxlamb1]

Hmmm...they all seem to be .img cd image files. There's a ccd worth 3kb, a disc image file worth anywhere from 200,000kb-600,000kb, and a .sub file worth about 15,000kb. They're all like this.

[maxlamb1]

Sorry, to clarify, "They're all like this" referring to the different games I'm trying to burn. They all came from the same directory and share the same file types.

[LIGHTNING UK!]

Oops sorry, you're talking about ccd files, so yes, the data should be in the .img file, not a .bin.

 

When you load the ccd in write mode, does the 'source' box get filled out with valid data / sizes?

[maxlamb1]

It doesn't appear to.

[LIGHTNING UK!]

Ok, I've located the image mentioned in your log and taken a look at it.

 

The CCD is missing some info that ImgBurn uses.

 

I've now tweaked my CCD related code to deal with such situations.

[maxlamb1]

Is there anything you recommend I do? Or should I try and locate different files?

[LIGHTNING UK!]

I found a bin and cue one before I found your one. That should work.

[maxlamb1]

Gotcha. The bummer is that I already downloaded 100 different game individually with these file types.  

Here we go again.

[LIGHTNING UK!]

You could always beta test the changes I've made and see if it works ok now?