Removable Media Drive Issues

[Anonymous]

So, I have this problem with my removable media drives (CD-RW drive and DVD-RW drive). The first time I enter a disc into one after rebooting, it loads up just fine, shows a logo in place of the CD picture if available, but doesn't run the autorun programs. When opened, everything's in order. From that point forward until I reboot, even if I remove the disc and/or put in another disc, the Windows XP explorer still calls the disc by the first disc's name and only shows the first disc's content. However, if a program calls on a file on one of the new CDs entered, it will be able to locate it. I just can't browse the contents of newly-inserted CDs or DVDs unless I restart.

So what the fuck is up with that, huh?

[Anonymous]

yeah weird I have that same problem. I just figured it's because my computer is a piece of shit

[FartinMowler]

I could be talking out of my ass here but, I'm alway's told to look up the manufacturer of your CD device and make sure you have the up-dated driver.

[AChimp]

All CD-ROMs have used practically identical drivers for the last seven years or so.

ATAPI in the hizouse.

[whoreable]

you could upgrade the firmware though. I doubt that will help, i bet it is a software problem.

[Anonymous]

I still need help with this. :<

I'm using an entirely different set of CD/DVD drives and still having this problem. Though, opening the drive in 'explore' mode does let me see the new content.

[AChimp]

Does the problem still occur when you reinstall Windows?

The problem obviously isn't with the drives themselves. The motherboard is probably starting to die. :(

[whoreable]

hm.. i had someone call about this same issue a few weeks ago. i dont remeber what i did though :/

[Anonymous]

i haven't tried to reinstall windows, no. I don't need the 9 million programs I have installed to forget they're there after the registry is wiped.

[Raize]

This has happened before:

http://216.239.41.104/search?q=cache:cwUFb6e0EocJ:forums.devshed.com/archive/t-168851+drive+contents+the+same+as+first+disc&hl=en

What I suggest is the following:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Cdrom

Change the "Autorun" to 0.

I'm assuming you know what that long line of stuff above is and how to use regedit. You'll want to log out and then back in. This will set your CD drive(s) to never autorun. You can also right-click and go to Properties and then look at the Autoplay tab and set each one to take no action, but the registry change is the easiest, IMHO.

Why this happens: I personally think it's because when the windows shell tries to load the autorun.ini something hangs and it never finishes. Which is why external apps to the shell, like Windows Explorer and software that needs files on the CD drive, work. Meanwhile, the explorer shell itself doesn't know what is going on and might even still be trying to autorun.

There, an entire length of help and I didn't insult anyone. Aren't you fsckers proud?

[Anonymous]

I'll avoid taking shots at you for being hardcore since you're actually trying to help here.

Just checked and Autorun was already set to 0 but I have some other entries in there that bother me. Like:

VN:
AutoRunAlwaysDisable
VD:
NEC MBR-7
NEC MBR-7.4
PIONEER CHANGR DRM-1804X
PIONEER CD-ROM DRM-6324X
PIONEER CD-ROM DRM-624X
TORiSAN CD-ROM CDR_C36

VN:
DependOnGroup
VD:
SCSI miniport

VN:
Group
VD:
SCSI CDROM class

I'm obviously not using a SCSI drive, nor are either of my cd/dvd drives products of NEC, Pioneer, or Torisan. (Using an LG 4040B DVD burner and a Sony 24x Power Burn CD-RW)

[xenosoul]

Mine used to do the exact same thing that yours is doing. The only difference is that my cd-rom started disapearing. I found out that one of the reasons it was doing so was cause the drivers from Clone-Cd (software burning prog) where interfering with the atapi windows drivers. Clone Cd would load some program at startup in the msconfig that was doing it.

Its probably some burning softwares drivers messing with ya.

[Anonymous]

I don't run any burner drivers. I've found that disabling/re-enabling the drive in the device manager reboots the drives, but that's a really lengthy process for something that should just be automatic.