I hope someone can help me figure this out. I've created some data CDs
using EZCD Creator 5, and when I try to access the cd in the drive after
it's been written, I generally get the following message:
CDCHECK caused an exception 01H in module KERNEL32.DLL at 0177:bff712c5.
Registers:
EAX=0000036d CS=0177 EIP=bff712c5 EFLGS=00000246
EBX=000011c0 SS=017f ESP=0105f908 EBP=0105f918
ECX=00000001 DS=017f ESI=0105f934 FS=63ef
EDX=81d70001 ES=017f EDI=00c4ac18 GS=0000
Bytes at CS:EIP:
c3 55 8b ec 8b 45 08 ff 70 04 ff 30 8b 1d dc 9c
Stack dump:
bff7651f 00000000 00c4ac18 00c4abe8 0105fa60 bff7fdca 0105f934 000011c0
00c4ac18 00000000 00c4abe8 565c3a5a 6f697369 32303032 7475415c 6e75726f
This dump happens to be from when I ran CDCHECK against the disc. When I
try to run something from the disc, like SETUP.EXE, it kind of starts, then
disappears. If I try to access the disc from the Start Menu | Run | Browse
option, I get the same thing. The browse dialog disappears. Same thing
happens if I open Explorer, go to the disc, and try to run something from
the disc.
The problem is, I don't get the same problem when I run the disc on my
laptop. It runs it just fine without any problems.
Is there a problem with EZCD Creator 5.0 that would cause this? I ran ASPI
Check, and it looks fine. I switched off the following: read ahead
optimization, DMA. I checked under my Control Panel for any compatibility
problems with the drive and didn't find any. I'm using a MEMOREX CD-482E
to read the disc.
I have the following cd writing software on my system:
CDRWIN
NTI CDMAKER 3
CLONECD
DISCJUGGLER
Could someone please help me?!? This is driving me nuts.
Thanks for any advice or info you might be able to provide.
PS: If I access the CD on my laptop via a network from my desktop, the CD
runs fine. Dunno if this helps any.
Thanks,
Mike.
If the disc reads OK on another drive, then i'd suspect that either the
CDRW drive is dirty or going bad, or it doesn't work well with the
particular brand of CDR media that you're using...
Try cleaning the drive optics first, then if that doesn't help, try some
other brands of CDR media. If after all that, it still won't read them,
the laser diode in the CDRW drive is probably shot (insufficient read/
write power level). Does the contrast of the burned area of the media
look faint ("weak burn") in comparison to the burned area on any
older CDRs that you've previously written on this drive?
Can you still read the older CDRs in the drive?
- John (Technoid)
Hi John,
I doubt the CDRW drive is going bad because I burnt other discs using
CDRWIN and they didn't give me any problems. I also doubt it's the CDR
media because a) It happens with a CDRW and a CDR disc I have, b) I have
other CDRW/CDR of exact same media that work beautifully.
Reading older CDRs are fine, no problem.
The only thing the bum CDRW and CDR seem to have in common is the fact that
they were created using EZCD Creator 5.
That's starting to make more sense now, since CDRWIN works fine, and
since the CDR's work OK in the laptop, it does look like your EZCDC
installation is hosed.
Perhaps a complete uninstall of EZCDC (probably requiring a Registry
"search and destroy" mission as well to get all of it out :p), followed by a
fresh reinstall may fix it? If not, I'd recommend switching to Nero.
I'm using Nero 5.5 and CDRWIN, and have had absolutely no problems
at all with either of them.
(Personally, after seeing all of the problems that others have experienced
with it lately, I wouldn't touch EZCDC with a 29-1/2 foot pole)... O_o
Cheers!
- John (Technoid)
--
Signet
sig...@bellsouth.net
~~~~~~~~~~~~~~~~~~~~
"For every action there is an equal and opposite criticism."
"nontechnoid" <n...@all.com> wrote in message
news:Xns90F970604F7...@24.93.67.41...
One would have to research in archives - hardly worth the effort - or
have a news server which did not delete ancient posts - most unlikely.
In short, the post-er was clueless.
--
Signet
sig...@bellsouth.net
~~~~~~~~~~~~~~~~~~~~
"For every action there is an equal and opposite criticism."
"Mike Richter" <mric...@cpl.net> wrote in message
news:3B741E39...@cpl.net...