Search options

Included with the SATA Controller package was a CD loaded with several dozen Silicon Image drivers.
After examining all those drivers, I knew this inexpensive card would finally resolve my problem with
the Pioneer optical drive.

IT WORKED!!!          YIPPEE!!!

To anyone who may find this thread while performing a Google seach, please be careful when you buy
a cheap SATA Controller Card.  Revision 1.0 supports a maximum data transfer rate of 150 MBYTES/SEC
which is more than adequate for an optical drive.  I purchased this card exclusively for my CD/DVD
burner.  If you need extra SATA ports for a hard drive or SSD optimized for the latest Revisions (3.0, 3.1,
and 3.2) make sure the controller card matches your requirements.

Thank you Jeff.

I always keep spare PSUs.  I pulled the PSU and connected it to a load box for six hours. I built this box
to constantly vary the load, simulating sudden load changes.  It passed the test. Nevertheless, I installed
a new PSU. I'll keep the old unit as a backup.

I tried removing a few items from Device Manager in Safe Mode.  No change.  When you say "optionally
remove all devices" do you mean that literally?  Just go down the list and remove everything?  Actually,
that sounds like a good idea!

Everything in the tower is SATA, except the floppy disk drive.

My first thought was to buy a new SATA optical drive.  Besides BartPE, I've got numerous bootable CDs.
They all run perfectly from the CMOS Boot Menu.  It's obvious that the Pioneer burner is 100% good.

The big question is, what's going to happen if I buy and install a new burner?

I always wear an antistatic wrist strap when I'm working in a computer tower, so I'm not concerned about
static discharge from my body.  However, I can't help thinking that something may have been damaged
when I replaced that CMOS battery.  Not very likely, but if the chipset on the mobo is good, why did the
burner vanish from XP after replacing the battery?

I guess buying a new SATA optical drive is a good idea.  Since I don't know why the Pioneer burner vanished,
I can't be certain a new optical drive will be recognized by the XP.

One last thought about this problem.  Most backup imaging apps, like Acronis will not work with a RAID
configuration unless it's added to a preinstalled environment like BartPE.  If you look in Device Manager
it's listed as hardware with its own drivers.  This may be a crazy thought, but are there any CD/DVD
burning apps that install hardware drivers in Device Manager?  If so, those additional drivers could fix
the Pioneer optical drive.

If there are any generic drivers for internal CD/DVD drives, provide a link and I'll give them a try.

Thanks again, OverFlow.

The person I was referring to is accused of copyright theft.
Apparently, many people at this other forum collectively
developed some really excellent "open source" plugins.
As soon as this guy had a good collection he created a new
site and started selling them.

I purchased two of them.  Why, you may ask?  Because
Acronis provides lousy free plugins, or intructions for
creating plugins that don't work.  For ten bucks I got two
Acronis plugins that work very well.  At the time I made
the purchase I knew nothing about this raging conflict
going on at this other forum.

As for myself, I fell into a sinkhole of hardware and
software conflicts with a new desktop.  I could not get
XP Pro_SP3 to write to several new eSATA drives without
a "delayed write failed" error message.  Microsoft was
very aware of this problem.  None of their solutions
worked.  Updating numerous chipset and sata drivers
finally fixed all the problems.

Because I had setup a RAID 0 system, none of the usual
boot media created by backup software worked.  I had
never heard of Bart, until someone suggested that I could
run my backup apps from a Bart disk, with the RAID 0
driver included.

I had no desire to become a Bart expert.  Getting all those
other drivers onto a Bart CD so it could access my eSATA
drives was a nightmare for me.  Your collection of driverpacks
is the final option.

I Googled about this problem with adpenc.inf.  Sure enough,
there were other posts with simple solutions. 

I'll try burning a CD.  If there are any more probems I'll consider
your DriverPacks BASE.

I've been building computers for a very long time.  I go back to
those primitive kits sold in hobby magazines like Radio and
Popular Electronics. 

Bart deserves all the attention its getting.  It's a remarkable
program.  I keep asking myself, how many more hours do
I want to devote to this app?  In the end, it may be easier to
junk some of my expensive hardware and use a different
operating system.  I've played around with Linux distros, but
never seriously considered dumping Windows.  The best
thing I ever did was not switching to Vista.  What a mess!
Who knows what Windows 7 will be like.  Like all Microsoft
systems, it will probably take years and a couple of service
packs before most of the bugs are patched.  I'm don't have
the time anymore to wait for Microsoft to fix things.  I've
got to go down a different road.  Maybe this set of awful
problems with Windows is the kick in the rear end I needed
to make a change.