Cannot read from Standard CD drives

[A.J.]

I currently use ECDC 5.1.2600.5512 Platinum installed on my Dell Windows XP machine. The program works fine until I tell ECDC to finalize the disk so it can be read in standard CD rom drives, which it appears to do and ejects the CD. When I try put the finished CD in my standard CD drive I get the blue screen of death and I have to shut the computer down. The completed disk can be read and used successfully on my CR-W drive. My computer is current with security and program updates that microsoft recommends.

 

Any suggestions would be helpful as I really enjoy ECDC 5 and don't enjoy the blue screen of death.

[cdanteek]

I currently use ECDC 5.1.2600.5512 Platinum installed on my Dell Windows XP machine. The program works fine until I tell ECDC to finalize the disk so it can be read in standard CD rom drives, which it appears to do and ejects the CD. When I try put the finished CD in my standard CD drive I get the blue screen of death and I have to shut the computer down. The completed disk can be read and used successfully on my CR-W drive. My computer is current with security and program updates that microsoft recommends.

 

Any suggestions would be helpful as I really enjoy ECDC 5 and don't enjoy the blue screen of death.

Quietly now, was the disc burned and closed using the application (directCD) top one in the picture shown below?

 

 

cd

 

 

[lynn98109]

Quietly now, was the disc burned and closed using the application (directCD) top one in the picture shown below?

 

cd

Actually, CD, I did think of that.

 

However, when my Win98 SE CD-ROM drive was given a burned disc to read, either it read it, or said to insert a disc.

 

The first CD-ROM was old enough it didn't know a recordable disc from a piece of paper. It's replacement usually read closed data discs. I hadn't closed a DirectCD disc before the disc failed, so can't speak to that. Since I don't use the Win98 SE anymore, and all drives in the Win2K and WinXP are either CD burners or Combo drives, there isn't a problem.

 

I considered answering, but the BSOD isn't part of my experience with drive/media combination.

 

Lynn

[A.J.]

To answer your question - yes. I used the Direct CD portion of the application after disk was formated using ECDC. The data was burned/copied to the disk using windows explorer and closed the normal way. There has not been any problem doing this sequence prior to just recently after updating my system.

[lynn98109]

To answer your question - yes. I used the Direct CD portion of the application after disk was formated using ECDC. The data was burned/copied to the disk using windows explorer and closed the normal way. There has not been any problem doing this sequence prior to just recently after updating my system.

It is possible that the Packet-Writing application (DirectCD) has failed on that disc.

 

It is possible your update of Windows (if it includes a higher Version of IE than IE 6, or WinPlayer than IE 9) could have caused the problem.

 

If the disc is RW media, it is possible it has gotten to the point the disc has failed.

 

The common point is something has failed.

 

IF you can still get the data off the disc using your burner drive, transfer it to your Hard Drive and make a Data CD (using the method in cd's picture listed BELOW DirectCD).

 

Packet-Writing is ok for short-term use, such as transferring files from one computer to another while the original is still safely on the original computer, but it is NOT a good choice for long-term archiving.

 

Nobody could tell me that, and I learned the hard way - i.e., the data that wasn't still also on the Hard Drive was permanently lost.

 

Lynn

[cdanteek]

I considered answering, but the BSOD isn't part of my experience with drive/media combination.

 

 

To answer your question - yes. I used the Direct CD portion of the application after disk was formated using ECDC. The data was burned/copied to the disk using windows explorer and closed the normal way. There has not been any problem doing this sequence prior to just recently after updating my system.

 

Ok you used a CD and formatted it with Direct CD? You dragged and dropped files in Explorer to the Formatted Direct CD?

 

Would you explain in detail "closed the normal way"?

 

After updating the PC the disc works in the same PC on a CD/RW Drive but not a CD-Rom Drive?

 

Do other disc's work fine in the CD-Rom Drive?

 

What recent updating did you do to the Dell Windows XP machine?

 

cd

 

[A.J.]

When I was finished copying/dragging all the data I needed using windows explorer I had three options to choose from when I went to eject the disk. I chose the option that states disk can be read and used in most CD Rom drives. The action was completed and disk was ejected.

 

All other disks work fine on my CD Rom drive and so does music CD that I have created useing ECDC.

 

The updates I refer to are security updates, Windows XP updates, Net framework updates, internet explorer security updates - all recommended updates from the microsoft update site. I am using Internet Explorer 6.0 and media player 11.

 

I have a duplicate Dell XP machine in another location and the result is the same and both machines are mirror copies of each other.

[Brendon]

A.J.,

 

You can ignore the poster who is merely reminiscing in posts #3 and #5, but you haven't answered an important question from Cdanteek.

"After updating the PC the disc works in the same PC on a CD/RW Drive but not a CD-Rom Drive?"

 

Would you answer that one, please? It's important to know if the BSOD is provoked by using a CD-ROM, but the discs work okay in a CD/RW drive.

 

Does this happen with all Direct CD discs, or just ones finalized since your updates?

 

Can you tell me what error number is reported in the BSOD, please?

 

Regards,

Brendon

[A.J.]

Still working to find out problem. And hopefully I can explain it completely.

 

I have created several disks over the years - both CD-R and CD-RW disks using ECDC 5.

 

When I place CD-R disks in the CD-Rom drive I get the BSOD. It doesn't matter if I try use a CD-R disk created in 2004, last fall or just recently - the result is the same - BSOD.

 

When I place a CD-R or a CD-RW disk in the CD-RW drive that I have created, they work just fine. Note that these disks were also created using ECDC 5 over time.

 

The BSOD message I get is as follows:

 

BAD POOL HEADER

 

Technical Info: 0x00000019 (0x00000020, 0xFF50CE28, 0xff50CE40, 0x1A030000

 

 

This problem basically has began after I started to updated my PC about 3 weeks ago.

 

[A.J.]

Sorry Guys but I just found a post about Media Player 11 and Internet explorer 7 breaking ECDC 5.

 

I have undated to Media Player 11 and this may be the problem. If I un-install Medial Player 11 and go back to Media Player 10 might this help?? I use Internet explorer 6.0 not 7.

 

Uninstall Media Player 11 - install Media Player 10 - re-install ECDC 5?

 

Thanks for all your imput.

[Brendon]

A.J.

 

It is quite unlikely to be Media Player 11 which has broken your Direct CD. The poster who suggested that, and who also suggested that your disc had failed, was guessing and has very little if any experience with the inner works of Direct CD.

 

If you can hold for a few hours I will go and install Windows Media Player 11 onto my ECDC 5 system and see if it does cause a BSOD. There's no substitute for actually running the software to see.

I also have a couple more ideas for updating your installation, which I'll try out while I'm away.

 

I don't know how long this will take because I do have a family but I'll be back as soon as I can.

 

Regards,

Brendon

[Brendon]

Okay, I'm back.

 

I can confirm:

-that Windows Media Player 11 doesn't produce this error

-that the packet-writing application hasn't failed on that disc

-that the disc itself hasn't failed

-that all the data on it are still available

-that the BSOD isn't part of Lyn's experience with drive/media combination

 

A pool header problem is a problem with Windows memory allocation, and the usual suspects are device drivers. If you look at the notice you get when ejecting a disc from your writer, it should look something like this notice I get from version 5.3.5.10

 

Notice that it mentions you need the UDF reader installed to read the disc in a ROM drive. I suspect that some update you have done has got tangled up with the UDF reader and causes the BSOD when it's called.

Media Player 11 can upset many of the other parts of Easy CD Creator, but Direct CD - the system which lets you write to disc through Windows Explorer - is a different system. It still kept working properly when I installed Media Player 11.

 

You're using ECDC 5.1, and it's working okay, except you get the BSOD when trying to read a formatted disc in your ROM drive. If that needs to be fixed, I'd suggest you update your ECDC to version 5.3.5.10, which is still available here. I have two reasons for that. [1] I couldn't produce a BSOD when using 5.3.5.10, and [2] if your problem is caused by an update over-writing an Adaptec/Roxio driver then there's a good chance the ECDC updater will correct that with a Roxio driver again. When getting the updater, select the Platinum one. You shouldn't need the web updater for drive recognition.

 

I'm afraid there are no guarantees here. This software worked well with the operating system in its time, but applying Microsoft updates and changes might have done something which can't be corrected. The last Roxio updates are many years old. Your choices are to put up with not being able to use your ROM drive, or trying the update in the hope it might help. Good luck whichever way you go.

 

If you haven't killed it with updates, you might find Creator itself is a better choice of writing system. It makes standard discs which can be read almost anywhere without a UDF reader, and is more stable than many of the packet-writers such as Direct CD.

 

Regards,

Brendon

[A.J.]

Brendon:

 

Thank you very much for all the time and effort trying to help this novice out. Your explanations have been very helpful in trying to figure out my problems.

 

I did download and install the ECDC update to version 5.3.5.10 as you suggested and I still get the BSOD screen when I try access my CD-ROM drive - CD-RW works fine.

 

What I thought of trying next was to un-install ECDC completely and re-intall from my original disk and then do the updates. Do you see any problems in doing this other than the same problem happening and the BSOD and then getting a newer Creator program.

 

What version of Creator (2009 or 2010) do you suggest I get and install as I am not familiar with either and my PC is an older model (2003).

 

Again thank you for all your help.

[lynn98109]

Brendon:

 

Thank you very much for all the time and effort trying to help this novice out. Your explanations have been very helpful in trying to figure out my problems.

 

I did download and install the ECDC update to version 5.3.5.10 as you suggested and I still get the BSOD screen when I try access my CD-ROM drive - CD-RW works fine.

 

What I thought of trying next was to un-install ECDC completely and re-intall from my original disk and then do the updates. Do you see any problems in doing this other than the same problem happening and the BSOD and then getting a newer Creator program.

 

What version of Creator (2009 or 2010) do you suggest I get and install as I am not familiar with either and my PC is an older model (2003).

 

Again thank you for all your help.

Note that in the end, despite Brendon's hobby of denouncing me, he gave the same advice - use a Sessions-based data disc for archiving the data, not Packet-Writing (DirectCD).

 

I am far from the only person who has lost data to Packet-Writing, and there are a number of posts from people frantically trying to "recover" data, ranging from business documents or baby pictures of their children.

 

However, in order for Brendon to answer your question about upgrading more easily (since he's on the other side of the world and won't be up for a bit yet), what are the specifications of your computer? Operating system, processing power, amount of RAM, size of Hard Drive, type of burners? (cdanteek and Brendon have such info in their signature)

 

Lynn

[Brendon]

A.J.,

The last line in my signature is the most important.

 

 

I would suggest, in order of preference:

 

- If you don't have to use your ROM drive, just carry on as you are now using your burner drive.

- Weighing it against a slight possibility that ECDC might stop working, completely uninstall it; then use the Roxizap uninstaller to clean the fragments out; then reinstall and re-update ECDC.

- Get another burner drive to replace your ROM - preferably the same as your first burner, even a second-hand older model - because it will likely be much cheaper than the latest software

- Get new software

 

Getting new software will be "interesting" for you. You may well find that the newest versions [Creator 2009 and 2010] won't run well on your older machine, and anyway they don't have the Direct CD / Drag-to-Disc program that you're using. It was dropped from the Roxio suites once the Operating Systems [Vista and Windows 7] started providing it built-in as their default writing system. There's no point in Roxio providing it if Microsoft is already doing that for free. The system requirements for Creator 2010 are outlined HERE.

 

If you absolutely have to have new software I'd suggest the best thing to get would be a pre-loved Easy Media Creator 9.

EMC 9 was the last version to have Drag-to-Disc, and I've found EMC 9 to be pretty robust. You can probably still get it from eBay and other such sites for a very small cost.

 

Regards,

Brendon