Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: burnatonce 0.99 (Read 6524 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

burnatonce 0.99

burnatonce 0.99 is a major update that should fix the device incompatibilities that some people experienced with 0.98.

Below is a list of the main additions:

- Read ID3v1.1 and APE Tags for MPC and Monkey Audio
- Option to verify integrity of Data CD/DVD Compilations
- Use folder name for DVD Video label
- Support combo CD Writer / DVD Readers
- Support Virtual Drives again
- Support devices on bus numbers above nine

Languages: Spanish, French, Norwegian, Chinese, Italian, Lithuanian, Russian and Polish.

www.burnatonce.com

burnatonce 0.99

Reply #1 –
*sigh* Startup-Errors are gone. But it still doesn't recognize my Teac CD-R55S as a Writer. Happens with SPTI checked and unchecked.

Using ASPI 4.6, Win2000 SP3

SCSI-Devices:
Initializing ASPI ... OK!
1,1,0: TEAC, CD-R55S, 1.0R
1,2,0: TEAC, CD-ROM CD-532S, 3.0A

Reverting back to 0.97a again.... i really was looking forward for this to be fixed :-(

- Lyx
I am arrogant and I can afford it because I deliver.

burnatonce 0.99

Reply #2 –
Maybe you must move your post to the burnatonce forums, don't you think? 

burnatonce 0.99

Reply #3 –
If your device was incorrectly detected as a reader with 0.98 then you'll need to delete the burnatonce.ini file before it will be deected correctly with 0.99.

And yes, AngelGR is correct:  if you don't report a problem how do you expect to get an answer or fix?!?   

Jamie

burnatonce 0.99

Reply #4 –
since i couldn't use 0.98 because of the errors (as i already mentioned) i was running 0.97a prior to 0.99.

I uninstalled 0.97a(which worked fine), and then installed 0.99.

About reporting bugs in your forum - sorry, maybe you could allow guests to post in the bug-forum - honestly, i don't want to register an account in a forum, just to report a single bug.

- Lyx
I am arrogant and I can afford it because I deliver.

burnatonce 0.99

Reply #5 –
Did you try deleting the ini file?  If you have ever had 0.98 on your system then the ini file may be holding invalid information about your device which will not be updated.

As for reporting the bug:  I guess your desire not to register exceeds your desire to use burnatonce, oh well.

Jamie

burnatonce 0.99

Reply #6 –
well, 90% of the software on my machine is non-commercial, and there are quite a lot of projects which i am following. If i encounter bugs, i report them and try to be as detailed as possible. But i really dont want to register on a dozen forums, just to make a single post every 2 months or so. Additionally, i dislike registrations in general and try to avoid them whereever possible - thats not an objective opinion, but rather a matter of taste and being paranoid

As for the ini-file...... there was no ini-file left, when i installed 0.99(at least not in the application-directory).... the uninstall was clean: it removed all files, except the application-dir itself.

I don't know if entries in the registry were removed corretly, but i can say that the application directory was completely empty, when i installed 0.99 - and no, i didn't install into a different path.

- Lyx
I am arrogant and I can afford it because I deliver.

burnatonce 0.99

Reply #7 –
If the install directory was clean then there should be no other trace left - burnatonce does not write to the registry.

Based on the information given to me there's not much I can do.  However, a command log from the first run of a clean installation would be helpful (get it before you close 0.99 though).

Unfortunately, where you are not prepared to register to a dozen forums, I cannot monitor a dozen forums so it's possible this issue will never be resolved.  You are welcome to continue use of 0.97a however. 

Jamie

burnatonce 0.99

Reply #8 –
command-log of 0.99-firstrun
===========================================
Cdrdao version 1.1.7 - © Andreas Mueller <andreas@daneb.de>
  SCSI interface library - © Joerg Schilling
  Paranoia DAE library - © Monty
  burnatonce extensions version 0.3 - © thop

Using libscg version 'rs-0.7t'
Initializing SPTI ... OK!

1,1,0: TEAC, CD-R55S, 1.0R
1,2,0: TEAC, CD-ROM CD-532S, 3.0A

after this, i unchecked SPTI-Interface, closed bao and started it again:
Cdrdao version 1.1.7 - © Andreas Mueller <andreas@daneb.de>
  SCSI interface library - © Joerg Schilling
  Paranoia DAE library - © Monty
  burnatonce extensions version 0.3 - © thop

Using libscg version 'rs-0.7t'
Initializing ASPI ... OK!
1,1,0: TEAC, CD-R55S, 1.0R
1,2,0: TEAC, CD-ROM CD-532S, 3.0A

============================================
As i mentioned above already, both devices can be selected as read-device, but the dropdown-menu in the writer-settings is empty.

i also tried to remove cdrdao.drivers or replacing them with the same file of 0.97a: same results.

- Lyx
I am arrogant and I can afford it because I deliver.

burnatonce 0.99

Reply #9 –
I'm sorry, I should have made it clear I require the file called 'commandlog.txt' that is created in burnatonce\external\temp.  Copy it before you close the program else it will be deleted.

Jamie

burnatonce 0.99

Reply #10 –
I suppose the line you're looking for is this one:
"ERROR: Cannot retrieve drive capabilities mode page. No drive information available."
applies to both drives, cd-rom and cd-writer

I'm not sure if BAO uses the correct SCSI-Driver - as far as i know, this is an old Tekram-PCI-Controler withouth BIOS(Symbios-Chipset if i remember right). SCSI-3 appears to be a bit heavy for my little controler
Also, it seems as if bao is continuing to search for a driver, although it has already found one - dont know.

Here's the full commandlog.txt:

Cdrdao version 1.1.7 - © Andreas Mueller <andreas@daneb.de>
  SCSI interface library - © Joerg Schilling
  Paranoia DAE library - © Monty
  burnatonce extensions version 0.3 - © thop

Using libscg version 'rs-0.7t'
Initializing ASPI ... OK!
1,1,0: TEAC, CD-R55S, 1.0R
1,2,0: TEAC, CD-ROM CD-532S, 3.0A

--------------------------------------------------------------

Cdrdao version 1.1.7 - © Andreas Mueller <andreas@daneb.de>
  SCSI interface library - © Joerg Schilling
  Paranoia DAE library - © Monty
  burnatonce extensions version 0.3 - © thop

Using libscg version 'rs-0.7t'
Initializing SPTI ... OK!

1,1,0: TEAC, CD-R55S, 1.0R
1,2,0: TEAC, CD-ROM CD-532S, 3.0A

--------------------------------------------------------------


Initializing SPTI ... OK!

Looking up TEAC CD-R55S ...
Driver found in driver table: teac-cdr55:0x0000

--------------------------------------------------------------


Initializing SPTI ... OK!

SPTI:1,1,0: TEAC CD-R55S   Rev: 1.0R
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)

ERROR: Cannot retrieve drive capabilities mode page.
No drive information available.

--------------------------------------------------------------


Initializing SPTI ... OK!

SPTI:1,1,0: TEAC CD-R55S   Rev: 1.0R
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)

ERROR: Cannot retrieve drive capabilities mode page.
No drive information available.

--------------------------------------------------------------


Initializing SPTI ... OK!

SPTI:1,1,0: TEAC CD-R55S   Rev: 1.0R
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)

ERROR: Cannot retrieve drive capabilities mode page.
No drive information available.

--------------------------------------------------------------

Initializing SPTI ... OK!

SPTI:1,1,0: TEAC CD-R55S   Rev: 1.0R
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)

ERROR: Cannot retrieve drive capabilities mode page.
No drive information available.

--------------------------------------------------------------

Initializing SPTI ... OK!

Looking up TEAC CD-ROM CD-532S ...
Driver found in driver table: plextor-scan:0x0003

--------------------------------------------------------------

Initializing SPTI ... OK!

SPTI:1,2,0: TEAC CD-ROM CD-532S   Rev: 3.0A
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)

ERROR: Cannot retrieve drive capabilities mode page.
No drive information available.

--------------------------------------------------------------

Initializing SPTI ... OK!

SPTI:1,2,0: TEAC CD-ROM CD-532S   Rev: 3.0A
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)

ERROR: Cannot retrieve drive capabilities mode page.
No drive information available.

--------------------------------------------------------------

Initializing SPTI ... OK!

SPTI:1,2,0: TEAC CD-ROM CD-532S   Rev: 3.0A
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)

ERROR: Cannot retrieve drive capabilities mode page.
No drive information available.

--------------------------------------------------------------


Initializing SPTI ... OK!

SPTI:1,2,0: TEAC CD-ROM CD-532S   Rev: 3.0A
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000)

ERROR: Cannot retrieve drive capabilities mode page.
No drive information available.


--------------------------------------------------------------

  burnatonce found the following external tools:

  Cdrdao for cd writing
  DVDRecord for dvd writing
  Mkisofs for iso creation
  WaveGain for ReplayGain
  MadPlay for mp3 decoding
  Ogg Decoder
  FLAC Decoder

--------------------------------------------------------------
I am arrogant and I can afford it because I deliver.

burnatonce 0.99

Reply #11 –
Here's the commandlog.txt of the old(working) 0.97a:

Cdrdao version 1.1.7 - © Andreas Mueller <andreas@daneb.de>
  SCSI interface library - © Joerg Schilling
  Paranoia DAE library - © Monty

Using libscg version 'andreas-0.5-UNIXWARE_Patch'

1,1,0: TEAC, CD-R55S, 1.0R
1,2,0: TEAC, CD-ROM CD-532S, 3.0A

--------------------------------------------------------------

Cdrdao version 1.1.7 - © Andreas Mueller <andreas@daneb.de>
  SCSI interface library - © Joerg Schilling
  Paranoia DAE library - © Monty

Using libscg version 'andreas-0.5-UNIXWARE_Patch'

Looking up TEAC CD-R55S ...
Driver found in driver table: teac-cdr55:0x0000

--------------------------------------------------------------

Cdrdao version 1.1.7 - © Andreas Mueller <andreas@daneb.de>
  SCSI interface library - © Joerg Schilling
  Paranoia DAE library - © Monty

Using libscg version 'andreas-0.5-UNIXWARE_Patch'

Looking up TEAC CD-ROM CD-532S ...
Driver found in driver table: plextor-scan:0x0003
I am arrogant and I can afford it because I deliver.

burnatonce 0.99

Reply #12 –
Ok, I see exactly what the problem is.  burnatonce 0.99 tries to query your device to find out some things about it but your devices do not respond to the generic-mmc driver so burnatonce assumes they are reading devices only - it has to do this since the device cannot supply further info that is required.

I'm really not sure what to do from here since thop at the burnatonce forums who programmed this interface tells me the generic-mmc driver should be used to do this no matter what driver should actually be used for writing.

I will alert thop to this thread - how old are the devices?

Jamie

burnatonce 0.99

Reply #13 –
quite old. I think aprox. 5 years.

I know that there are way better devices out there today - but it still does what i need. And till today i had only 1 buffer-underun in all those years - which was a result of my own stupidness. And both devices never ever messed up a single time when extracting audio, even in burst-mode. Slow and old but reliable 'till today
I am arrogant and I can afford it because I deliver.

burnatonce 0.99

Reply #14 –
Quote
quite old. I think aprox. 5 years.

Well, that would explain why they are not MMC compliant. 

Hopefully thop can come up with something but I'm afraid that you may not be able to use recent versions of burnatonce. 

Jamie

burnatonce 0.99

Reply #15 –
hmm, maybe a checkbox in the options "do not use MMC-Calls (for old devices)" ?

- Lyx
I am arrogant and I can afford it because I deliver.

burnatonce 0.99

Reply #16 –
Your drive doesn't reveal any information about itself, so thats the problem. I have an idea though, and if that doesn't work i will just make it display dummy information for old drives so that burnatonce will be happy, but the functionality will be like 0.97.
I will sent you a test version, please remind me via PM if you don't hear from me within a week.

burnatonce 0.99

Reply #17 –
thank you - on another note: i would also do some testing via "moonblade at nospammail.net" if this would be easier for you to send files and messages.
I am arrogant and I can afford it because I deliver.