Jump to content


Digital Guru
  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Brendon

  1. Jim,


    If you have the original drive that the OEM software came with, it should work WITHOUT UPDATES being necessary.


    If it isn't working (and the drive's still okay) then the software has been broken by something or hasn't been installed successfully.


    Tell us more about your operating system, the drive, the machine, and the software history, so we can see where it broke.

  2. How do I post a question to the board. I am logged it, and it lets me ask a question, and then I send it, but I don't know where it is being sent to and what my answers are from anyone. Where is the board? I just got used of the old board.



    That's a good paradox, Judy.


    If you see my reply there was no need for it, because you found where your question was going to and where the answers were.


    If you don't see my reply, how can I tell you where to look?

  3. Dave said :"I'm really reluctant to do this to my machine because it is used for business purposes and I don't want to take a chance on screwing it up, so I'd like to find another solution. That solution apparently is to update the Roxio applet in MP9, which brings me back to my original question: How can I get an engine update from Roxio?"


    I have an idea that this was a conflict with the CDR4 module in WMP9, CDR4 being a Roxio module and one of the reasons why Windows Media Player conflicted with earlier versions of CD Creator.


    Roxio put out a fix file, UPDATECDR4_53_71.EXE which was 188,406 bytes, and I think this was to fix that problem.


    I haven't been able to find that file available from the Roxio site when I had a look just before, but I do have a copy of it from about a year ago. If you need, I can experiment on my Version 5 and see what that file does.

  4. There are two types of 4, Standard and DeLuxe. If you get a "file not found" error it's usually because you have the wrong sort of updater and it's testing for the presence of a file which your version doesn't have.


    [pssst! just quietly, there's no version 4.5 - the highest reached was 4.05 ]

  5. John,


    There are two main methods of writing CDs used by the Easy CD Creator suite.


    1) Direct CD, where you format a disc and drag 'n' drop files onto it. This is a proprietory format meant for local use, and it won't be readable by most other systems.


    2) CD Creator which writes a STANDARD CD ROM onto an unformatted CD.


    You should use method 2 if you want to produce CDs which can be reliably read by other people or even yourself if your system changes.

  6. Well, it isn't that the OEM version supports one of those drives while the others don't.


    Brad doesn't say which drive he's having problems with, but the LTR-16102C has been supported since ECDC version 4.03a, and the DVR-105 since


    As long as your ECDC is 5.3.1 or better you don't need to go all the way up to 5.3.5, and the DriveUp add-on is quite pointless.


    Brad, I can't advise further as "caused my OEM software to stop working" is pretty nebulous. You haven't even said which software has stopped, let alone what is happening.


    Have a read of Lynn's "Frequent answers" and you'll see the sort of information we need if we're to help you.

  7. The DriveUp patch is ONLY there to add new drives to the drive recognition table that ECDC5 maintains. It does NOT add any updates or enhancements to Easy CD Creator.


    If ECDC already recognizes your drive, DON'T use the DriveUp patch because that's just another thing which can go wrong and mess up your perfectly good installation.


    If you have a newish drive which NEEDS a DriveUp patch, install that after you've updated to 5.3.5 because the DriveUp is only an ADD-ON patch.


    If you need the platinum update, you might be SOL again. I just spent half an hour trying to get that updater or at least start it downloading, and I had no luck. Foreign updaters come down fine, but NOT the English one.


    I think there are a couple of servers running at the address you are sent to by the updates page, and at least one of them is unserviceable! If you keep stabbing the "refresh" button every few seconds you can eventually get through to the page at


    which tells you that Take Two has been disabled, and invites you to click a button to continue.


    (Please note you can't just jump to these addresses, you need to be refered to them by the previous pages in the updates section)


    At this point you're directed to


    and after a long timeout period you get a notice that this page is unavailable. It works fine for other language updaters (Different id= number) but not for 208, the English one.


    I think whoever is in charge of that download has died or is asleep at the wheel. It's very bad for business. I'd like to know which company hosts the downloads for Roxio.


    In the meantime you can get functionality by using a foreign language updater if you can understand the foreign language. You can return most of the foreign prompts (but not all of them) to English by searching for and deleting the foreign language localizer files which have an extension of .LOC

    There might be up to 15 of these .LOC files in a full installation and deleting or renaming them will give you back a lot (but not all) of the English prompts.


    Yes, it's bad. It shouldn't be necessary. But it helps in the meantime.

  8. :) I have this problem except the CD-R was over written with Direct CD. The files are still there but I cannot read them. Of course when I insert the CD-R it automatically starts with Direct CD. Is there any way I can bypass the index and reclaim these files? Explorer says there is 400 MB of space left on a 700 MB disc and less than 1 MB of data can be seen. I am using XP home with service pack 2 version 5.3 cd software.


    If the disc is a CD-R, I don't see how it could have been overwritten by Direct CD.


    If you have somehow managed to format with Direct CD the area of the disc that was unused (how ever did you manage that?) the disc is now going to be in an "unusual" state which I haven't seen before. No recovery can be guaranteed, but there are a couple of things worth trying.


    The Direct CD operation shouldn't have been able to destroy the data already written, since the CD-R can only be written once. If that's the case, it is just a matter of how to access the data.


    1) Disabling Direct CD either by uninstalling it or preventing it loading/running with something like MSCONFIG might enable you to see the non-UDF area of the disc. (no guarantees there)


    2) You may be able to recover files with a recovery utility such as CDRoller or ISObuster, which you can obtain off the web. They both allow a trial which will identify what files can be recovered, but you have to pay to get a version which will actually do the recovery.



    You have written a session without importing the indexes of the previous session. This can be corrected. If you're not using a CD-RW or Direct CD your data is safe.


    Quick explanation:


    When you write a session with CD Creator, an index is built up showing all the files and where they are on the CD.


    When you write the next session you should "import" the index from the previous session. Then when you burn, an incremental index of all previous sessions is recorded.


    Each time you write a further session you import the previous session, and your current session then lists all files on the CD. On this occasion you didn't do that, but instead wrote a "new volume" without the previous index.


    How to correct:

    [Read this through and don't do anything until you're confident you can see what we're going to do. Come back here with any questions if you're not happy.]


    1) Copy off all the files you can see on the CD back to your hard drive.

    2) Run CD Creator in a data project, and with that CD in the burner prepare to add one file (any old file will do)

    3) Go to the toolbar, Disc / Import session. You should be shown the sessions already on the CD, and asked which one you want to import.

    4) Import the session before the last one you burned. (The last one is the one you just copied back to the hard drive, and the one before that is the one you want.)

    This should go get the previous index you lost, and add it to the one file you're about to burn.

    5) Burn this latest session. It should be very quick, as it has only one file and the index to burn.


    Now, if you eject the CD and then reinsert it you should find that the session you copied off to your hard drive has now disappeared, but the previous stuff has all returned. At this point I would be inclined to copy it off, and then burn a fresh CD with everything on it in one session (session closed but CD left open for further burning).


    To prevent this happening again, go to FILE/ CD PROJECT PROPERTIES / GENERAL and check the box for "Automatically import previous session". It's very rare to have a use for not automatically importing the previous session.