Using DVD2SVCD with KT266A Chipset

[Caliber]

Is anybody doing this? I'm having issues with ripping the DVD. I get errors in the ripped movie, this causes AVISynth to crash. It's not in the same place everytime I rip it - I've ripped and encoded this movie on another machine before so I assume it is not the DVD itself. I am having other issues with my DVD-Rom drive reading data and things. I am guessing it is some drivers issue - I thought maybe some others could share what drivers they have found to work well. I am using WinXP and currently have the Via 4in1 1.37a Drivers installed.
I hope this isn't 'off topic'.
Thanks!

[DDogg]

Kinda off topic but it is a slow day. I am moving it to basic as that is now the place for most things. See the sticky at the top on forums. It has some very basic guidelines.

I do two or three encodes a day sometimes on my 266A Epox 8KHA+. However, if I increase my fsb just ONE numeral from 150 to 151, CCE will bite the big one inside of 1 minute of encoding. Just to show you what a barometer it is. Er, I kinda think your machine is not using stock settings? Come on, fess up :)

[markrb]

Many of us are using it with a 266a chipset with no problems.
Go over to www.viahardware.com and grab the PCI lantency patch by George Breese. This might help, but I think the problem maybe elsewhere.
Try swapping the position of the DVD drive on the chain. If it's a master drive make it the slave and vice versa.
If you are overclocking drop it back to spec and see if it corrupts the files at this speed.

Are you using the drive with a seperate PCI controller like the Promise by any chance? There are known issues with all non intergrated controllers and the 266a chipset.
Is the drive SCSI? Same problem as with the Promise controller.

Does it happen with all DVD's or have you just tested one?

Really sounds like a DVD-ROM issue. Try rolling back the 4 in 1's to the version that came with XP (4.32).

You might be better off asking something like this at www.amdb.com or www.anandtech.com or www.viahardware.com in their forums.

Mark

[Caliber]

Thanks for moving the post, I wasn't sure where it belongs.
It really isn't overclocked at all - I want to get it working normal before I start tweaking it all. I did up the voltage a lil' because somebody said it may help (the vcore), but it didn't.
The drive is currently set as slave with the CDRW as master. I will try moving those around. The controller being used is the onboard one - specifically the second ide connector. The setup is:
IDE1: 60GB WD (Master) 40GB IBM (Slave)
IDE2: HP CDRW (Master) Toshiba DVD (Slave)
I was thinking of also trying each device on it's own ide channel.
I will try it with some other DVDs also...I suppose I should have done so before asking for help, but I know this DVD worked on the DVD-Rom in another comptuer - different mobo/proc/ram though.
And I did rollback the driver this morning to the XP default, but still no luck. I'll try the other things and the PCI Latency Patch tomorrow or Wed.
Thanks for the ideas!!!

[machura]

I'm using both my IBM HDD on Promise drivers on MS K7T266Pro2RU( IDE3: IBM30GB, IDE4: IBM40GB) and no problems. / DVD is on IDE2 and CDRW on IDE1. /

But I'm ripping with SmartRipper 2.41 => DVD isn't so long time in DVD-ROM and DVD-ROM isn't so long stressed.

I cannot find PCI lantency patch by George Breese on viahardware. There is not "search" ?

[markrb]

Look on the lefthand side of the viahardware page one of the items is PCI latency patch.

Mark

[Caliber]

Well the good and the bad news is the same: I fixed it. All I had to do was change the DVD-ROM from UDMA to PIO Mode.
What exactly is the difference? I think PIO uses more processor or something, but I'm not sure of other differences. Oh well...at least it works now :|
Thanks everybody

[DDogg]

If you have the time please run my little stress test in the advanced forum

[chainsaw135]

Here is a brief answer to your question.

PIO= Programmable I/O which uses port I/O to transfer data from the drive. This method uses the processor continuously for the exchange.

DMA=Direct Memory Access uses the disk controller to move data directly to memory without tying up the processor

Each of these two methods has a range of modes. For example, PIO modes range from 0 (transfer rate of 3.33MB/second) to 4 (16.66MB/second).

(DMA mode 2) up to 33MB/s

(DMA mode 4)UP TO 66 MB/s)

(DMA mode 5) up to 100 MB/s)

There is more to this then i put in here but this is really not the place for that so..hope this helps you understand a bit more.