DVD Drive clash

Post by **garyb** » Wed Jun 13, 2007 2:42 pm

nope. you want sata in ide mode. your choices are ide or raid.

Kymeia · Post by **Kymeia** » Wed Jun 13, 2007 3:01 pm

Thanks. In the advanced tab there are 2 places it asks about RAId mode - one called ITE8212f controller where the options are IDE, RAID or disabled - I presume I set for IDE, and another called Silicon image Controller where the options are RAID mode, SATA mode or disabled - I presume SATA? Can't see anything else to change.

ps my mobo is an ASUS P5AD2 premium if that's any help.

Can't see anything that will make the DVDDrive DMA though.

I have disabled all the overclocking options though as the system keeps overheating (even with a huge Zalman cooler)

husker · Post by **husker** » Wed Jun 13, 2007 3:12 pm

This is a nasty problem in XP...if it gets multiple errors on a drive it will revert to PIO (even a dirty DVD can cause this!?!)

In PIO mode your PC will grind to halt when access the drive (as you describe)

http://support.microsoft.com/kb/817472

down the bottom of the page is a reg entry that will fix it (guaranteed!)

cheers

Kymeia · Post by **Kymeia** » Wed Jun 13, 2007 3:37 pm

Thanks - a lot of information there. Why can't they just provide the hotfix that does it automatically? It seems to be saying you need to run the hotfix and then edit the registry but further up under "workaround" it says you should uninstall the Ide channel driver and restart windows which will reinstall it.

It also says this fix is in SP2 which I already have so I'm confused as to why this is a problem and why it should only happen when Scope is running.

Kymeia · Post by **Kymeia** » Wed Jun 13, 2007 3:40 pm

I found a script to fix it but its in VB so I don't know how to run it:

http://winhlp.com/tools/resetdma.vbs

husker · Post by **husker** » Wed Jun 13, 2007 3:41 pm

yes...actually that link is the long story...the short story is this:

Run REGEDIT.
Go to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}
It has subkeys like 0000, 0001, 0002, etc. Normally 0001 is the primary IDE channel, 0002 the secondary, but other numbers can occur under certain circumstances. You have to go through these subkeys and check the DriverDesc value until you find the proper IDE channel.
Delete MasterIdDataChecksum or SlaveIdDataChecksum, depending on whether the device in question is attached as master or slave, but it can't actually hurt to delete both. Reboot. The drive DMA capabilities will be redetected.
Open Device Manager again and check whether the device is now actually using DMA mode. If so, congratulations, you've made it (at least until the next time Windows disables DMA)

husker · Post by **husker** » Wed Jun 13, 2007 3:42 pm

Kymeia wrote:I found a script to fix it but its in VB so I don't know how to run it:

http://winhlp.com/tools/resetdma.vbs

you should just be able to double click the file as Windows Scripting Host will run it...although virus checkers may stop you doing this 'for your own good'

Kymeia · Post by **Kymeia** » Wed Jun 13, 2007 3:53 pm

Fixed it - I did need to uninstall and reinstall the IDE driver. It was all here:

http://www.cdrom-guide.com/forums/showt ... p?t=121744

and now my DVDDrive plays while Scope is running. Still not sure why being in PIO mode should only cause a playback problem and system freeze with Scope running but not when it was off but obviously there's a connection somewhere.

Thanks all

husker · Post by **husker** » Wed Jun 13, 2007 3:57 pm

cool

PIO requires massive amounts of IRQ interrupts, and as Scope also requires interrupts they clash badly.

Post by **garyb** » Wed Jun 13, 2007 4:25 pm

nice one, glad it's working.

Kymeia · Post by **Kymeia** » Wed Jun 13, 2007 11:11 pm

For future reference I found this very useful thread on the subject. There's also a link to a utility called dmacheck:

http://sniptools.com/tipstricks/getting ... windows-xp

husker · Post by **husker** » Thu Jun 14, 2007 2:33 pm

yes it is very bizarre...i'm sure a large % of PC out there are crippled by this 'feature'....

obviously a conspiracy to force people to buy new PC's