Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Callithumpian]

Again in the "Can anyone else duplicate this"

I bought a number of new CDs this week and I had an archive CD with 300Mb of stuff on it.  So I thought I would fill it up with the recent rips.

During the burn process MJ flashed up that it was "Importing Previous Session"
However when complete the TOC of the newly burned disc shows ONLY the files burned in the last session. The earlier sessions of 300Mb had been deleted from the Table of Contents.

As further investigation, I put another half-full CD and clicked the "Burn CD" toolbar icon.
MJ goes into "Gathering information..." then correctly displays the files on the CD.
But in the status section of the MJ CD Burner it says "Ready for Writing" and "0.0Mb Used - 680.1 Mb Left"
In other words MJ is treating it like an blank disc despite the fact that it has just read it and found it to contain data.

I have an old 2x4x6 Yamaha Burner which MJ correctly detects and with which MJ has worked well in the past.
I do not use the generic driver because it truncates filenames unacceptably.
I use the burner quite regularly with a variety of other software - hitch free.


Media Jukebox PLUS 8.0.284
Install Path: C:\Program Files\Media Jukebox\

CPU: Intel Pentium III 803 MHz MMX
Memory: Total - 130 MB, Free - 9 MB
OS: Microsoft Windows Me

Internet Explorer: 6.0.2600.0000
ComCtl32.dll: 5.50.4704.1100
Shlwapi.dll: 6.00.2600.0000
Shell32.dll: 5.50.4134.100
wnaspi32.dll: 4.57 (1014) , ASPI for Win32 (95/NT) DLL, Copyright © 1989-1998 Adaptec, Inc.
Aspi32.sys: N/A

[JimH]

It could be our bug.

Was the old disk burned with 7.2?

Your best bet is to burn 70 cents (Australian) on a new CD each time you make a disk.

[Callithumpian]

Nah, disc was burned with V8 - about .227 (a very good build) or so.

I am OK to do a full disc at a time but am still hopeful that the problem can be identified and corrected.

It's a bit of bummer having burning software that indicates to you that it's reading the previous session(s) then just wipes them out.

Earlier builds definitely behaved better on this hardware profile which is what made me think it was a recent build problem.