Archived from groups: microsoft.public.win98.gen_discussion (More info?)
ISSUE RESOLVED!
After uninstalling a couple of excess DVD ripping/burning apps all discs
placed in either drive are immediately recognized.
I can't thank you enough for your patient help with this. I believe that if
it weren't for the great help found in newsgroups, all computing in the
world would grind to a halt. Well, anyway, all MY computing!
Randy
"Gary S. Terhune" <grystnews@mvps.org> wrote in message
news:eF8qUy9rFHA.1252@TK2MSFTNGP09.phx.gbl...
> Don't worry. I live here.
>
> Yes, CD burning software is notorious for messing up CD drives and burner
> behavior. Particularly packet writers (InCD, DirectCD, etc.) My personal
> recommendation is to never install such apps. Regular burning utilities
are
> usually fine, but even they can cause odd issues like yours.
>
> --
> Gary S. Terhune
> MS-MVP Shell/User
>
> "Randwill" <rwilliams4254@triad.rr.com> wrote in message
> news:kPYRe.85876$WN5.68406@fe02.news.easynews.com...
> > No, I haven't had a chance to do the latest suggestions, but if you
think
> > it's related to my burning software I think I'll do your most recent
> > suggestions AND re-install Nero.
> >
> > Won't be able to get to this until the weekend and as this thread is
> > getting
> > longer and lower - don't abandon me!
> >
> > Thanks.
> >
> > Randy
> >
> >
> > "Gary S. Terhune" <grystnews@mvps.org> wrote in message
> > news:%23UIxNF3rFHA.332@tk2msftngp13.phx.gbl...
> >> No, it's not the OS. Or rather, it's not *just* the OS if it's the OS
at
> >> all. It's much more likely your burning software. Do you have InCD
> >> installed? Do you use it? Have you updated your Nero software recently?
> > (And
> >> I take it you've not yet done any of the stuff I suggested a little
while
> >> ago?)
> >>
> >> --
> >> Gary S. Terhune
> >> MS-MVP Shell/User
> >>
> >> "Randwill" <rwilliams4254@triad.rr.com> wrote in message
> >> news:zzPRe.69704$w74.67219@fe03.news.easynews.com...
> >> >I just tried an experiment. I put a video DVD into F DVD drive (the
> > reader
> >> > only) and ripped it. But when I tried to burn it with Nero using E
> >> > drive
> >> > (the burner) Nero didn't see the blank DVD. I rebooted, leaving the
> > blank
> >> > in E drive, and now Nero saw it and burned the disc. However when I
> >> > opened
> >> > the disc to look at it's contents, I didn't get the "drive not
> > accessible"
> >> > error but no contents showed in the box. This is in the same drive
> >> > that
> >> > just burned it. Placing it in the reader (F) yeilded the usual
"drive
> > not
> >> > accessible" error.
> >> >
> >> > To sum up F read the disc, reboot, E burned the disc. F saw nothing
on
> >> > disc,
> >> > E didn't see disc at all.
> >> >
> >> > I've been thinking of upgrading to XP, I'm beginning to wonder if now
> >> > might
> >> > be the time. Both drives obviously work correctly, it's the
operating
> >> > system that's not dancing with them, right?
> >> >
> >> > Randy
> >> >
> >> >
> >> >
> >> > .
> >> > "Randwill" <rwilliams4254@triad.rr.com> wrote in message
> >> > news:LHORe.89364$gI2.60964@fe12.news.easynews.com...
> >> >> Followed all instructions but when CD is placed in either drive and
I
> >> > click
> >> >> on it I get the same "drive is not accessible. The device is not
> > ready"
> >> >> error message.
> >> >>
> >> >> Here's the list of devices from the System section and the number of
> >> >> times
> >> >> they are listed:
> >> >>
> >> >> ACPI Fan
> >> >> ACPI IRQ Holder for PCI IRQ Steering (8)
> >> >> ACPI Power Button
> >> >> ACPI System Button
> >> >> Advanced Configuration and Power Interface (ACPI) BIOS
> >> >> Composite Power Search
> >> >> Direct memory access controller
> >> >> IO read data port for ISA Plug and Play enumerator
> >> >> Motherboard resourcer (2)
> >> >> Numeric data processor
> >> >> PCI standard host CPU bridge
> >> >> PCI standard ISA bridge
> >> >> PCI standard PCI to PCI bridge (2)
> >> >> Plug and Play Software Device Enumerator
> >> >> PnP BIOS Extension
> >> >> Processor support
> >> >> Programmable interrupt controller
> >> >> SCI IRQ used by ACPI bus
> >> >> System board
> >> >> System board extension for ACPI BIOS
> >> >> Sysytem CMOS / real time clock
> >> >> System speaker
> >> >> System timer
> >> >>
> >> >> So unless you see something here that may be causing Windows to not
> >> >> see
> >> > the
> >> >> CDs in the drives am I out of luck?
> >> >> How far am I from a complete re-formatting?
> >> >>
> >> >> Randy Williams
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> "Gary S. Terhune" <grystnews@mvps.org> wrote in message
> >> >> news:uLVqkQyrFHA.1172@TK2MSFTNGP11.phx.gbl...
> >> >> > OK, assuming both drives check out OK in DOS copy procedures,
let's
> >> >> > move
> >> >> on.
> >> >> >
> >> >> > Are both of these drives DVD-ROM? Is neither one of them a burner?
> >> >> > If
> >> > one
> >> >> is
> >> >> > a burner, make it the Secondary Master drive. Make the other drive
> > the
> >> >> > Slave.
> >> >> >
> >> >> > Once you have the drives connected properly, and both have worked
OK
> > in
> >> >> DOS,
> >> >> > restart the system and repeatedly press the Ctrl key until the
> > Startup
> >> >> Menu
> >> >> > comes up (holding it down will prompt a stuck-key error). Choose
> >> >> > Safe
> >> >> Mode.
> >> >> > In Safe Mode, go to Device Manager. Delete ALL drives and ALL
> >> > controllers
> >> >> > (you won't be able to remove FIFOs, don't worry, it's OK.) Also
look
> > in
> >> >> the
> >> >> > System section and delete the PCI Bus. While you're there, review
> >> >> > the
> >> >> entire
> >> >> > list for devices you recognize as having been physically removed
> >> >> > from
> >> > the
> >> >> > system in the past. Also look for duplicate entries. Must be
*exact*
> >> >> > duplicates. Make a list of these, name and the number of times it
> >> > appears.
> >> >> > Post back here with that info when it's convenient.
> >> >> >
> >> >> > After removing the IDE chain (drives, controllers, etc.) restart
and
> >> >> > let
> >> >> > Windows reinstall the devices. You'll need to reboot at least
once.
> >> >> >
> >> >> > That should do it. Let us know.
> >> >> >
> >> >> > --
> >> >> > Gary S. Terhune
> >> >> > MS-MVP Shell/User
> >> >> >
> >> >> >
> >> >> > "Randwill" <rwilliams4254@triad.rr.com> wrote in message
> >> >> > news:w9HRe.65095$WN5.46332@fe02.news.easynews.com...
> >> >> > > Okay thanks guys. I have successfully copied several files from
> > one
> >> > DVD
> >> >> > > drive. (All caps with the period worked.)
> >> >> > >
> >> >> > > So we know both drives and their contents are seen in DOS mode
and
> > I
> >> > can
> >> >> > > copy from one of them. I'll do the copy test on the other drive
> > now.
> >> >> > > Meanwhile, what's the next step?
> >> >> > >
> >> >> > > Thanks.
> >> >> > >
> >> >> > > Randy
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>
ISSUE RESOLVED!
After uninstalling a couple of excess DVD ripping/burning apps all discs
placed in either drive are immediately recognized.
I can't thank you enough for your patient help with this. I believe that if
it weren't for the great help found in newsgroups, all computing in the
world would grind to a halt. Well, anyway, all MY computing!
Randy
"Gary S. Terhune" <grystnews@mvps.org> wrote in message
news:eF8qUy9rFHA.1252@TK2MSFTNGP09.phx.gbl...
> Don't worry. I live here.
>
> Yes, CD burning software is notorious for messing up CD drives and burner
> behavior. Particularly packet writers (InCD, DirectCD, etc.) My personal
> recommendation is to never install such apps. Regular burning utilities
are
> usually fine, but even they can cause odd issues like yours.
>
> --
> Gary S. Terhune
> MS-MVP Shell/User
>
> "Randwill" <rwilliams4254@triad.rr.com> wrote in message
> news:kPYRe.85876$WN5.68406@fe02.news.easynews.com...
> > No, I haven't had a chance to do the latest suggestions, but if you
think
> > it's related to my burning software I think I'll do your most recent
> > suggestions AND re-install Nero.
> >
> > Won't be able to get to this until the weekend and as this thread is
> > getting
> > longer and lower - don't abandon me!
> >
> > Thanks.
> >
> > Randy
> >
> >
> > "Gary S. Terhune" <grystnews@mvps.org> wrote in message
> > news:%23UIxNF3rFHA.332@tk2msftngp13.phx.gbl...
> >> No, it's not the OS. Or rather, it's not *just* the OS if it's the OS
at
> >> all. It's much more likely your burning software. Do you have InCD
> >> installed? Do you use it? Have you updated your Nero software recently?
> > (And
> >> I take it you've not yet done any of the stuff I suggested a little
while
> >> ago?)
> >>
> >> --
> >> Gary S. Terhune
> >> MS-MVP Shell/User
> >>
> >> "Randwill" <rwilliams4254@triad.rr.com> wrote in message
> >> news:zzPRe.69704$w74.67219@fe03.news.easynews.com...
> >> >I just tried an experiment. I put a video DVD into F DVD drive (the
> > reader
> >> > only) and ripped it. But when I tried to burn it with Nero using E
> >> > drive
> >> > (the burner) Nero didn't see the blank DVD. I rebooted, leaving the
> > blank
> >> > in E drive, and now Nero saw it and burned the disc. However when I
> >> > opened
> >> > the disc to look at it's contents, I didn't get the "drive not
> > accessible"
> >> > error but no contents showed in the box. This is in the same drive
> >> > that
> >> > just burned it. Placing it in the reader (F) yeilded the usual
"drive
> > not
> >> > accessible" error.
> >> >
> >> > To sum up F read the disc, reboot, E burned the disc. F saw nothing
on
> >> > disc,
> >> > E didn't see disc at all.
> >> >
> >> > I've been thinking of upgrading to XP, I'm beginning to wonder if now
> >> > might
> >> > be the time. Both drives obviously work correctly, it's the
operating
> >> > system that's not dancing with them, right?
> >> >
> >> > Randy
> >> >
> >> >
> >> >
> >> > .
> >> > "Randwill" <rwilliams4254@triad.rr.com> wrote in message
> >> > news:LHORe.89364$gI2.60964@fe12.news.easynews.com...
> >> >> Followed all instructions but when CD is placed in either drive and
I
> >> > click
> >> >> on it I get the same "drive is not accessible. The device is not
> > ready"
> >> >> error message.
> >> >>
> >> >> Here's the list of devices from the System section and the number of
> >> >> times
> >> >> they are listed:
> >> >>
> >> >> ACPI Fan
> >> >> ACPI IRQ Holder for PCI IRQ Steering (8)
> >> >> ACPI Power Button
> >> >> ACPI System Button
> >> >> Advanced Configuration and Power Interface (ACPI) BIOS
> >> >> Composite Power Search
> >> >> Direct memory access controller
> >> >> IO read data port for ISA Plug and Play enumerator
> >> >> Motherboard resourcer (2)
> >> >> Numeric data processor
> >> >> PCI standard host CPU bridge
> >> >> PCI standard ISA bridge
> >> >> PCI standard PCI to PCI bridge (2)
> >> >> Plug and Play Software Device Enumerator
> >> >> PnP BIOS Extension
> >> >> Processor support
> >> >> Programmable interrupt controller
> >> >> SCI IRQ used by ACPI bus
> >> >> System board
> >> >> System board extension for ACPI BIOS
> >> >> Sysytem CMOS / real time clock
> >> >> System speaker
> >> >> System timer
> >> >>
> >> >> So unless you see something here that may be causing Windows to not
> >> >> see
> >> > the
> >> >> CDs in the drives am I out of luck?
> >> >> How far am I from a complete re-formatting?
> >> >>
> >> >> Randy Williams
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> "Gary S. Terhune" <grystnews@mvps.org> wrote in message
> >> >> news:uLVqkQyrFHA.1172@TK2MSFTNGP11.phx.gbl...
> >> >> > OK, assuming both drives check out OK in DOS copy procedures,
let's
> >> >> > move
> >> >> on.
> >> >> >
> >> >> > Are both of these drives DVD-ROM? Is neither one of them a burner?
> >> >> > If
> >> > one
> >> >> is
> >> >> > a burner, make it the Secondary Master drive. Make the other drive
> > the
> >> >> > Slave.
> >> >> >
> >> >> > Once you have the drives connected properly, and both have worked
OK
> > in
> >> >> DOS,
> >> >> > restart the system and repeatedly press the Ctrl key until the
> > Startup
> >> >> Menu
> >> >> > comes up (holding it down will prompt a stuck-key error). Choose
> >> >> > Safe
> >> >> Mode.
> >> >> > In Safe Mode, go to Device Manager. Delete ALL drives and ALL
> >> > controllers
> >> >> > (you won't be able to remove FIFOs, don't worry, it's OK.) Also
look
> > in
> >> >> the
> >> >> > System section and delete the PCI Bus. While you're there, review
> >> >> > the
> >> >> entire
> >> >> > list for devices you recognize as having been physically removed
> >> >> > from
> >> > the
> >> >> > system in the past. Also look for duplicate entries. Must be
*exact*
> >> >> > duplicates. Make a list of these, name and the number of times it
> >> > appears.
> >> >> > Post back here with that info when it's convenient.
> >> >> >
> >> >> > After removing the IDE chain (drives, controllers, etc.) restart
and
> >> >> > let
> >> >> > Windows reinstall the devices. You'll need to reboot at least
once.
> >> >> >
> >> >> > That should do it. Let us know.
> >> >> >
> >> >> > --
> >> >> > Gary S. Terhune
> >> >> > MS-MVP Shell/User
> >> >> >
> >> >> >
> >> >> > "Randwill" <rwilliams4254@triad.rr.com> wrote in message
> >> >> > news:w9HRe.65095$WN5.46332@fe02.news.easynews.com...
> >> >> > > Okay thanks guys. I have successfully copied several files from
> > one
> >> > DVD
> >> >> > > drive. (All caps with the period worked.)
> >> >> > >
> >> >> > > So we know both drives and their contents are seen in DOS mode
and
> > I
> >> > can
> >> >> > > copy from one of them. I'll do the copy test on the other drive
> > now.
> >> >> > > Meanwhile, what's the next step?
> >> >> > >
> >> >> > > Thanks.
> >> >> > >
> >> >> > > Randy
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>
Facebook
Twitter
Instagram