PDItool - enhanced PDIxtract with GUI

[DMagic1]

Originally posted by schlaufer
Hi Dmagic1,
the only reason I can think of is a modification of directory structure in this file. Can you provide me with first 200kByte of the first .pdi-file? This chunk should compress very well.

Sorry, I don't have them anymore. If I get that error again I will post it.

[Doggiedaddy]

schlaufer
Thanks so much for the installer. I had 2 machines go down and had to do a complete re-install on both. These 2 were unfortunately not yet on my automated recovery HDS so it was a Windows from scratch rebuild. I could not get any of your VERY useful programs to load properly [In Windows]until the installer, looks like a few of the .dll were missing or older and the installer fixed.

Anyway, THANKS for a great job.
Dd

[goober22]

Originally posted by schlaufer
Hi goober22,

the only difference in handling of small and large files is that large files are read in huge (i.e. 20 MB) chunks. It may be possible, that the combination of MB, chipset driver, and harddisk does not like so huge reads/writes. To verify this assumption, I've put a slightly modified version on my web-space: pdixtract with reduced buffersize (http://www.freewebs.com/schlaufer/pdixtract-smallbuf.zip) . This version reduces the maximum size of single reads or write command to 2MB. Replace the pdixtract.exe shiped with PDITool with the one in the archive.

This is for testing purposes only! If it works out, I consider upgrading your drivers.

Cheers,
schlaufer

Hi schlaufer,

I'll try it out but it may be 2-3 days before I can. I don't know about the driver issue. My MB is a Soyo and is 2 months old with an AMD 2100+. I have updated to the latest Via drivers and already run the latest bios. I don't have the problem with any other extraction or converting software, just this one. It seems to work okay on small files but locks up on larger ones. But it is hit-pr-miss. Some dvd's work fine and some don't.

Oh well, I'll give it a try and post back later. I'll try the regular version until it locks up and then switch to the amll buffer one and see how that goes.

Goob

[goober22]

Originally posted by schlaufer
Hi goober22,

the only difference in handling of small and large files is that large files are read in huge (i.e. 20 MB) chunks. It may be possible, that the combination of MB, chipset driver, and harddisk does not like so huge reads/writes. To verify this assumption, I've put a slightly modified version on my web-space: pdixtract with reduced buffersize (http://www.freewebs.com/schlaufer/pdixtract-smallbuf.zip) . This version reduces the maximum size of single reads or write command to 2MB. Replace the pdixtract.exe shiped with PDITool with the one in the archive.

This is for testing purposes only! If it works out, I consider upgrading your drivers.

Cheers,
schlaufer

@schlaufer

Hi, just posting an update to my little problem. I ran IC on "I Spy". I then ran pditool with the original pdixtract. This disc has both wide/full versions. It extracted okay until it got to the last vob set (#13). There, it locked up on the vob file. It still had the bup to extract as well.

I had to force a reboot. I replaced the pdixtract file with the one you supplied and ran pditool again. I extracted all files and this time it worked okay. I then ran it on "The man with the golden gun". It extracted all just fine as well.

The original version extracted the large files okay this time but locked up on the last vob, about 56,000 in size. The test version you posted so far, is doing okay for me.

FWIW.