Pioneer 105 is Disc-at-once incapable!

P

pwygant

1
...Any Pioneer 105 owners, please chime in...

I am posting this in this section since this is what I was burning...

I have had the Pioneer 105 for about 8 months and I have been extremely happy with it. Since last night, the nightmare began and it has to do with the problems of Disc-at-once writing on Pioneer drives.

You can follow my original post here:

http://www.burnatonce.com/forums/in...9&showtopic=614

I got this drive for the new and improved use of DAO recording on DVD-R Pioneers. I found this piece of software called Burnatonce and it worked flawlessly on everything I threw at it. In this case, I cannot write .cue and .bin files anymore due to the following error message:

Starting write at speed 4...
Turning BURN-Proof on
Executing power calibration...
Power calibration successful.
ERROR: Drive does not accept any cue sheet variant - please report.
ERROR: Writing failed.

In this case I was writing an SVCD and every time again I get this error message from any (NERO-BAO-CLONE) etc. What gives? I have not installed any new software, changed anything on my computer, the Pioneer just reverted to the faulty 104's and cannot write Disc at once anymore. Another thing I tried was to use NERO and burn the disc using Disc at once/96 and this actually worked, however for a perfectionist like me, this is irritating!

If you do a search around the web for this problem, many, if not all pioneer users are having some of the same issues. Some can burn and some cannot.

Any ideas?

P.S Running Windows XP SP1 and the 105 still writes flawless CDR's as ISO's, DVD-R's but not through bin and cue's. Very frustrating!

Cheers Mates!

P.S I sent this to "The -Poacher" as well since he loves his 105 as well!
 
The-poacher

The-poacher

1
Sorry cant really help <> I have never burnt anything other than DVD's with my 105 & I only use Recordnowmax & Alcohol.Im sure others will be able to help (I have no idea why this should happen)
 
ChickenMan

ChickenMan

1
How have you prepared your Cue/Bin files ? If your used VCDEasy have you selected BIN/CUE or BIN/Detailed CUE ? Change it from what ever you have selected and try that.
 
woody

woody

1
I had the exact same error with my A05.I would like to know the cause too.I was using BAO too.Could very well be the firmware,Scarecrow.Would like to know for sure.I tried the same cuesheet with My Plextor,and BAO.It burned flawlessly. :confused:
 
ChickenMan

ChickenMan

1
I have never ever tried burning a Cue/Bin file or any other file to a CDR in my 105, shit I bought it to burn DVD's not CDR's. A A$70 LiteOn is all thats needs for burning CDR's.
 
The-poacher

The-poacher

1
ChickenMan said:
I have never ever tried burning a Cue/Bin file or any other file to a CDR in my 105, shit I bought it to burn DVD's not CDR's. A A$70 LiteOn is all thats needs for burning CDR's.
Click to expand...
Couldnt have put it better myself :D:D:D
 
P

pwygant

1
The-poacher said:
Couldnt have put it better myself :D:D:D
Click to expand...
:confused:

The purpose of this forum is to discuss and help people out with small annoyances and problems. I think this justifies as an annoyance since this problem on Pioneer drives is a well known documented problem with no solution. My biggest concern was the fact that how can something work so great for so long and then one day it doesn't work anymore with no chaneg to the OS or installment of software?

That was the purpose of the post. Any person would understand that when I bought my first DVD-R drive the purpose of the drive is to burn DVD-r's. However, we still burn Cdr's don't we? I don't think a week goes by I don't backup something on CD'r!

For us that disposed of our old CD-RW's drives when they break I thought this would be a great debate and hoped to learn what other people have done hoping to have an all in one solution. I am set up with a DVD rom drive as slave and my DVD-r as primary so I don't have the luxury of just popping it into the other CD-RW but I guess I'll have to get one.

Cheers!
 
zver

zver

1
Thats a well known problem>>saw it many times.....It cannot be fixed........Only if new firmware comes out....
 
P

pwygant

1
roadworker said:
Check your .cue file with notepad to see if the .bin is a mode 2/2352 bytes with multiple sessions/tracks...
Click to expand...
FILE "movie.bin" BINARY
TRACK 01 MODE2/2352
FLAGS DCP
INDEX 01 00:00:00
TRACK 02 MODE2/2352
FLAGS DCP
INDEX 00 00:04:00
INDEX 01 00:06:00
INDEX 02 00:06:01
INDEX 03 17:36:62
INDEX 04 34:28:47
INDEX 05 53:27:46
INDEX 06 72:15:34
 
roadworker

roadworker

1
pwygant said:
FILE "movie.bin" BINARY
TRACK 01 MODE2/2352
FLAGS DCP
INDEX 01 00:00:00
TRACK 02 MODE2/2352
FLAGS DCP
INDEX 00 00:04:00
INDEX 01 00:06:00
INDEX 02 00:06:01
INDEX 03 17:36:62
INDEX 04 34:28:47
INDEX 05 53:27:46
INDEX 06 72:15:34
Click to expand...

That's the reason why it won't work.....multiple tracks and multiple index points.....Pioneer can't handle these...

Try a MODE 1/2352 bytes image....I think those images will work flawlessly...
 
S

scarecrow

1
Before doing what Roadworker suggested open the .cue file by a text editor and remove the two lines with the 'flags" commands- now check if it works.
By the book VCD standards the first track (data) should be mode1/2048 bytes, and the second one mode2/2336 bytes (VCDEasy can create such 100% book compliant VCD images). Nevertheless most programs create two mode2/2352 tracks (which are more prone to return media reading errors, as all error correction information is gone) for better hardware compatibility- however as you see this is not always the case...
 
P

pwygant

1
roadworker said:
That's the reason why it won't work.....multiple tracks and multiple index points.....Pioneer can't handle these...

Try a MODE 1/2352 bytes image....I think those images will work flawlessly...
Click to expand...
Thanks for the input. I have seen a lot of these comments about flags and/or differnt modes of .cue files. The fact of the matter is that it just frustrates me that it has worked great for so many months and now it doesn't anymore on the same .cue files.

For someone like myself this is really just an annoyance issue and I am just trying to figure out "WHY"!

Cheers!

P.S I'll test some of the recomendations and report back...
 
daveml

daveml

1
If it has suddenly stopped working and u havent installed any new firmware, then your drive is maybe showing the first signs of death!
I dont think Pioneer really bothered to put a decent cd burning engine in the 104 or 105. If anyone has to use their dvd drive for cdrs I would get a sony.
And thats from a happy pioneer customer.
I totally agree with poacher and CM tho. Unless u have no spare slot, dont use your dvd burner for cds.
Thats like driving a F1 car to the supermarket.
 
The-poacher

The-poacher

1
@pwygant
If U read my first answer U will note I said no idea how to cure it

& I reiterate I bought my 105 to burn DVD & wouldnt dream of burning to CDr with it

However I have asked a M8 who does burn CDR & he had burning probs (different to yours) & he cured it by
(i) uninstalling the hacked firmware & installing the latest "proper" firmware & it did the trick it now burns OK so scarecrow may well be right.:cool::cool:
 
woody

woody

1
This has become a very helpful thread,adressing a problem with the A05/105 cdr burning.

Computer hardware sometimes makes it necessary to use the A05/105 as a dvd ripper,and/or using it for cdr burning.It depends on how many 5.25 slots are available in your tower.Mini ATX cases being a big problem.Nice thread. ;)
 
roadworker

roadworker

1
Even Pioneer and Nec support have no idea what causes this behaviour,I've seen a lot of posts from people who had it from the beginning with their drive.......

scarecrow said:
Before doing what Roadworker suggested open the .cue file by a text editor and remove the two lines with the 'flags" commands- now check if it works.
Click to expand...
If scarecrow's solution doesn't work,edit your .cue like this:

FILE "movie.bin" BINARY
TRACK 01 MODE2/2352
INDEX 01 00:00:00
TRACK 02 MODE2/2352
INDEX 00 00:04:00

PS,do these things on a copy of the .cue and backup and replace your original ,so you have always the original .cue if needed...;)

If both scarecrow's and my solutions don't work,try to burn the original .cue with Alcohol 120%...:)
 
P

pwygant

1
:D

The most frustrating part of this entire problem is the fact that the problem arose all of a sudden without no interference on my part. (You never know about PC's though)

How can something go from working to not working by not doing anything? That is what is most frustrating! However, maybe I should just use it for burning DVD-R before it dies!

:)

P.S I never changed any firmware, hack or no hack, until after I found out it didn't work anymore yesterday. I upgraded to the 1.33, retail, to no use!

Cheers!
 
roadworker

roadworker

1
pwygant said:
:D
P.S I never changed any firmware, hack or no hack, until after I found out it didn't work anymore yesterday. I upgraded to the 1.33, retail, to no use!

Cheers!
Click to expand...

Have you tried to burn it with burnatonce in SPTI mode?It's possible that your aspi layer became corrupt,Nero uses it's own,maybe that's the reason why it works with Nero and not with (Adaptec's) aspi-dependent programs...
 
You must log in or register to reply here.
Top