Hanging on Filling Buffer

[gilgatex]

I did a quick search of the forums and I can't find anyone else with my problem. I'm trying to copy a CD. I've created the image successfully and now I'm trying to burn it back to a blank CD. They're both 700MB CDs

 

It gets to filling buffer about 54% and then nothing else happens. Any ideas?

 

 

I 09:37:57 Operation Started!

I 09:37:57 Source File: E:\Bullocks111109.cue

I 09:37:57 Source File Sectors: 19,961 (MODE2/FORM1/2352)

I 09:37:57 Source File Size: 46,948,272 bytes

I 09:37:57 Source File Volume Identifier: Bullocks111109

I 09:37:57 Source File File System(s): ISO9660, Joliet

I 09:37:57 Destination Device: [2:1:0] Optiarc DVD+-RW AD-5170S 101B (D:) (ATAPI)

I 09:37:57 Destination Media Type: CD-R (Disc ID: 97m24s16f, Sony Corp.)

I 09:37:57 Destination Media Supported Write Speeds: 8x, 16x, 24x, 32x

I 09:37:57 Destination Media Sectors: 359,847

I 09:37:57 Write Mode: CD

I 09:37:57 Write Type: SAO

I 09:37:57 Write Speed: MAX

I 09:37:57 Lock Volume: Yes

I 09:37:57 Test Mode: No

I 09:37:57 OPC: No

I 09:37:57 BURN-Proof: Enabled

I 09:37:57 Write Speed Successfully Set! - Effective: 5,645 KB/s (32x)

I 09:37:57 Filling Buffer... (80 MB)

I 09:49:41 Abort Request Acknowledged

I 09:49:41 Synchronising Cache...

W 09:49:47 User opted to skip the 'Close Track/Session/Disc' functions.

E 09:49:47 Failed to Write Image!

E 09:49:47 Operation Aborted! - Duration: 00:11:50

I 09:49:47 Average Write Rate: N/A - Maximum Write Rate: N/A

[LIGHTNING UK!]

Open the cue file in notepad and copy + paste its contents please.

[gilgatex]

FILE "Bullocks111109.bin" BINARY

TRACK 01 MODE2/2352

INDEX 01 00:00:00

REM TAOGAP 00:00:02

REM LEAD-OUT 04:26:11

[LIGHTNING UK!]

Thanks.

 

Now can you tell me the exact size of the bin file in bytes please. (Right click it and hit properties)

[gilgatex]

46,943,568 bytes

[LIGHTNING UK!]

Ok, for now, delete the cue file and just burn the bin instead.

 

It's probably to do with it waiting for some extra data that isn't ever going to arrive.

 

Changing the buffer to something below 40mb would probably work too.