PDItool - enhanced PDIxtract with GUI

[schlaufer]

Hi everybody,

after a few busy days WPELLE and I are proud to present PDItool (http://members.chello.se/jonas.thornqvist/PDITOOL.zip).

PDItool contains an enhanced version of pdixtract from schlaufer together with a GUI frontend from WPELLE. PDItool can

has a nice, easy to understand and comfortable to use GUI
shows you the contents of a .pdi file set
convert .pdi file sets to .iso files, which can be mounted by daemon tools or alchol and which can be burnt by your favorite DVDR toaster program.
extract all or only selected files from an .pdi file set
keep disk space requirements to a minimum, i.e. it is possible to let the first segments of a .pdi set be deleted while it is still extracting the later ones.


Just extract the attached .zip archive to a location of your choice and start the program PDITool. Be sure to extract both programs to the same directory.

For those of you, who are interested in the structure of .pdi files or want to use it under a non-Microsoft OS, the source code of pdixtract is included.

PDItool should be attached to this post after moderator approval and can be downloaded here (http://members.chello.se/jonas.thornqvist/PDITOOL.zip) or here (http://www.freewebs.com/schlaufer/PDITOOL.zip).

If you get errors about missing components and libraries, you propably need the Visual basic runtime libraries, get them here (http://www.karenware.com/progs/vbrun60-setup.exe), if this does not help, try the PDITool installer (http://members.chello.se/jonas.thornqvist/PDITOOLINSTALLER.zip). Please use this as last resort to safe bandwidth for other users.

[lusid]

This tool breaks if you have spaces in your paths.

[WPELLE]

I am working on that right now...

EDIT: Problem solved, fixed version can be downloaded here (http://members.chello.se/jonas.thornqvist/PDITOOL.zip) until the attachment has been updated.

[-=ViBeZ=-]

Cool. I like the convert to iso feature. I'll try in out on my next rip. Do we need to use dos freindly names? Such as everything in CAPITALS?

[WPELLE]

Originally posted by -=ViBeZ=-
Cool. I like the convert to iso feature. I'll try in out on my next rip. Do we need to use dos freindly names? Such as everything in CAPITALS?

Nope you can use any file/pathname you want now.

[mrbass]

thanks schlaufer and wpelle for your hard work. This will be a huge boon to many. I've updated my guide to reflect new tool. So far it works perfect for me.
suggestion: maybe worthless
how about add something like this since probably most rip in file mode I'm guessing.

Create VIDEO_TS and AUDIO_TS directories.
or would this just complicate matters more perhaps.
I'll have to test this out...but if one rips in ISO mode then checks AUDIO_TS would PDITOOL create/extract the AUDIO_TS folder too from the .pdi file set?

[-=ViBeZ=-]

I'm getting a 'component comdlg32.oxc no registered error'

Any ideas?

I'm running xp pro

[schlaufer]

You propably need the Visual basic runtime libraries, get them here (http://www.karenware.com/progs/vbrun60-setup.exe).

[marcovan]

Same error here. Installed runtime libs and still got it.

[WPELLE]

how about add something like this since probably most rip in file mode I'm guessing.

Create VIDEO_TS and AUDIO_TS directories.
or would this just complicate matters more perhaps.
I'll have to test this out...but if one rips in ISO mode then checks AUDIO_TS would PDITOOL create/extract the AUDIO_TS folder too from the .pdi file set?


I guess it would be quite easy for it to also create an AUDIO_TS directory.

When using the Convert to Iso button the checkbox for VIDEO_TS has no effect.

[WPELLE]

Originally posted by marcovan
Same error here. Installed runtime libs and still got it.

We first thought we'd not have to post this, but since some of you are having problems i've uploaded a installer that installs PDITool + all runtimes and dll's needed. It's alot larger than the zip-file (2MB).

You can find it here (http://members.chello.se/jonas.thornqvist/PDITOOLINSTALLER.zip)

[BIACS]

I'm not getting any runtime errors but it stops extracting after the first vob. I used IC to backup Three Kings and wanted to extract them locally so I could test with Power DVD prior to burning. There is plenty of space on the drive for the extracted files and any temp's created during the extraction. When I run the PDITool and set the directories I've tried Extract All and Extract Files, it appears to stop after the initial .pdi and doesn't pick up on the spanned files. The directory I'm using does have a space but when I browse to it in the main part of PDITool it does display the directory with a ~ so I didn't think that should matter.

Has anyone else had this problem? I'm running XP Pro, VB files are installed, drive is NTFS. I have also only selected the 2nd main vob while using Extract Files option and it creates the filename in the extraction folder but it is 0kb and PDITool closes. There are no error messages displayed on the screen when it closes either.

Tks

BIACS

[schlaufer]

Hi,

I guess the space inside the directory name could be really the problem. I fear, that the DOS-mangling of the filenames done by PDITool is not compatible with the way, pdixtract builds the filenames for the spawned .pdi parts.

To verify this assumption, can you please do the following:
[list=1]
rename all directories in the path to contain no spaces
rename the .pdi files so that their name contain no spaces
enter the unmangled filename (full path) by hand into the PDITool dialog
extract some files
[/list=1]

Please report your results.
TIA,
schlaufer

[mpucoder]

If you are using the DOS Prompt, and not real DOS (For Win9x users who still have a real DOS) you can enclose file names in quotes. This fixes the problem of spaces being parsed as seperators.

[BIACS]

Originally posted by schlaufer

To verify this assumption, can you please do the following:
[list=1]
rename all directories in the path to contain no spaces
rename the .pdi files so that their name contain no spaces
enter the unmangled filename (full path) by hand into the PDITool dialog
extract some files
[/list=1]


I've done that now and still receive the same result. My source folder was DVD Rips and has been renamed to DVDRips, the files were under a folder named Output and their names have been changed to ThreeKings. When PDITool is run it extracts the VIDEO_TS.IFO, VIDEO_TS.BUP, VTS_01.0.IFO, VTS_01_0.VOB, AND VTS_01_1.VOB but then the command window goes away. The PDITool and List Files windows are still open but the processing stops. There are a total of 5 pdi's also, ThreeKings.pdi (pdi01, pdi02, pdi03, and pdi04) all in the same directory.

I've also now burned a RW from InstantCopy using the pdi's it created. I wanted to be sure they weren't corrupted and that was causing PDITool to crash. The movie burned fine and works fine. I'm using PDITool version 0.4, is that the most current or could that be my problem.

I tried selecting (one at a time) the VTS_02 and VTS_03 files, PDITool does create the file name in the destination directory but they are 0kb. The command window flashes up and back off as soon as it pops up when I press Extract files.

Tks,

BIACS

[Richk50]

Worked great. Thank you, for your hard work.

[schlaufer]

Originally posted by BIACS
There are a total of 5 pdi's also, ThreeKings.pdi (pdi01, pdi02, pdi03, and pdi04) all in the same directory.

Aaah, I gues it is still the mangling. Please rename the files in a way, thjat the stem is not longer than 8 characters, i.e. 3kings.pdi...

Cheers,
Schlaufer

[WPELLE]

Sorry about that dos-mangling thingie that isn't working so well.
I've uploaded an updated version which uses quotes around the filenames as mpucoder and schlaufer suggested.

It can be downloaded here until all mirrors have been updated (http://members.chello.se/jonas.thornqvist/PDITOOL.zip)

[mrbass]

ok I've updated my mirror with new version ...it still says 0.4 though. Anyway thanks for the update.

[Sockpuppet-uk]

Very useful little app...I am trying Instantcopy over my usual way of ripping and this is most helpful.
Thanks very much.

[BIACS]

Thanks schlaufer and WPELLE the new tool is working great, processes all of the files in the set.

[WPELLE]

Originally posted by BIACS
Thanks schlaufer and WPELLE the new tool is working great, processes all of the files in the set.

Glad to hear that it's working now.

ok I've updated my mirror with new version ...it still says 0.4 though. Anyway thanks for the update.

Whoops, forgot to change the version nr. I updated the file again with the proper version number (0.5).

[mrbass]

ok thanks...I put 0.5 up there

[nawo69]

Thanks for creating this great program but I have found a problem with it, I use a separate Hard drive for all my DVD stuff H:\ so I installed your program there and it runs fine but the problem is when i try and extract the files to the H: drive it does'nt work the dos box flash on then off if i do it to the C:\ drive it work fine.

The create ISO works fine to H:\ also.

Cheers

Andy

[schlaufer]

Hi nawo69,

I use PDITool/pdixtract with different hard drives too, but without any problems. Therefore the information you given is insufficient for me or WPELLE to track down the error and fix it.

To help you to provide us with all useful information, I've attached a special debug aid version of pdixtract to this posting. Please replace the pdixtract that shipped with PDITool with the one attached to this post.

If an error occurs during extraction or listing generation, the program beeps and command window stays open until you hit the RETURN key.

Please redo the erroneous operation and post the output of pdixtract here with your error report. You can copy the contents of the command window by right clicking on its title bar and selecting 'Edit->Mark all, Edit->Copy'. Then paste it into your browser window, enclosed in CODE tags like this:

[ code ]
'C:\VideoTools\PDITool\pdixtract.exe' '-gb' 'C:\pdilist.txt' 'D:\princess_menu.pdi'
$Id: pdixtract.c,v 1.5 2003/02/27 15:08:50 smurf Exp smurf $

D:\princess_menu.pdi: Permission denied
Hit <RETURN> to continue
[ /code ]


The above error results from an attempt to access a .pdi file set that is currently in use by InstantCopy.

Until the attachment is approved, you can retrieve the debugging executable from this location (http://www.freewebs.com/schlaufer/pdixtract.exe).

[nawo69]

Ok, I have tried that and the same thing happens it just flashs up and disapears.

But futher testing I have found if I select a folder on the H drive (H:\test\) it will work fine, its just if I select output directry as the root of the drive (ie H:\) I get the same error if I select the output as C:\.

Cheers

Andy

[schlaufer]

Originally posted by nawo69
Ok, I have tried that and the same thing happens it just flashs up and disapears.

But futher testing I have found if I select a folder on the H drive (H:\test\) it will work fine, its just if I select output directry as the root of the drive (ie H:\) I get the same error if I select the output as C:\.

Cheers

Andy

That was the hint I needed. I just added another wait after the "wrong parameters passed" error, and voila:

'C:\VideoTools\PDITool\pdixtract.exe' '-v' '-m' 'F:" D:\princess_menu.pdi VTS_06_0.BUP'

It seems that Visual Basic has messed up the command line. The right command line would have been:

'C:\VideoTools\PDITool\pdixtract.exe' '-v' '-m' 'F:\' 'D:\princess_menu.pdi' 'VTS_06_0.BUP'


You have to wait for WPELLE to look after it since he is the master of the GUI. In the meantime you have to obey the following rules concerning:

do not extract files into the root dir of a drive (i.e. C:\)
do not use spaces in your file names

If you are bound to either of the mentioned constraints, you have to call pdixtract "by hand":

usage: pdixtract [options] <pdi-file-name>[.pdi] [files...]

options:
-l list only (directory mode)
-i <iso> convert .pdi-file-set into .iso-image <iso>[.iso]
-r remove .pdi files as soon as possible
-d <dir> extract files to directory <dir>
-m <dir> create directory <dir> and extract files int it
-v create VIDEO_TS directory and extract files into it
-x same as -r -m <pdi-file-name> -v

a trailing '*' may be used as wildcard for file selection,
e.g. pdixtract -d C:\ -v "E:\movie has blanks" vts_01*
extracts Video Title Set 1 from movie has blanks.pdi* to dir C:\VIDEO_TS

[WPELLE]

I don't really know why it replaced the \ with a " but I managed to fix it another way.

I uploaded the fixed version (0.6) at the usual place (here (http://members.chello.se/jonas.thornqvist/PDITOOL.zip))

Now it's possible to extract directly into C: D: F: etc and spaces in filenames should work perfectly.

[goober22]

@schlaufer

I had been having trouble with pditools, pdixtract & pdi2iso all crashing out a various stages during extraction (posted in a different thread)

Just to let you know, I downloaded .06 version of pditools and tried it on a pdi set I still had on the HD. This was a set that it had locked up on earlier.

It worked just fine. I don't know what changed but it seems to do okay for me now. (I was extracting to the same drive, different folder, no spaces in name). At least it works now. I did download the debug version (just in case :D ).

[DVD Maniac]

Thanks Guys for your hard work! This tool has really turned Instant Copy into a useable and practical solution for 1:1's. I have had no problems. Just a minor point - your full install version also installs MS messenger (part of the .NET pack?) which I have had to disable to stop annoying messages appearing when on-line! I cannot seem to get rid of it - no Control panel uninstall. If its safe to remove it - can advise how please (assume this is one for Wpelle).

PS - Suggest you open a Paypal - you might get some donations for all your hard work!

[nawo69]

Thanks Guys that works a treat.

Cheers

Andy

[WPELLE]

Originally posted by DVD Maniac
Thanks Guys for your hard work! This tool has really turned Instant Copy into a useable and practical solution for 1:1's. I have had no problems. Just a minor point - your full install version also installs MS messenger (part of the .NET pack?) which I have had to disable to stop annoying messages appearing when on-line! I cannot seem to get rid of it - no Control panel uninstall. If its safe to remove it - can advise how please (assume this is one for Wpelle).

PS - Suggest you open a Paypal - you might get some donations for all your hard work!

Hmm, that's strange. Have you tried just uninstalling PDITool and using the zipped version instead?

On a sidenote, I found and fixed a small bug so there's a new version out (0.7).

Grab it here (http://members.chello.se/jonas.thornqvist/PDITOOL.zip)

EDIT: DVD Maniac, here's a guide on how to disable the messenger service
http://www.lantalk.net/disable_messenger.php

[DVD Maniac]

I have followed the instructions and all appears to be OK now. Any reason why Messenger service needs to be there in your Installer - I never would need it anyway.

[WPELLE]

Originally posted by DVD Maniac
I have followed the instructions and all appears to be OK now. Any reason why Messenger service needs to be there in your Installer - I never would need it anyway.

It seems to be a part of the VB6-runtimes that are included in the installer. The messenger service is actually installed by default if one is using Win2k/XP.

[DVD Maniac]

There appear to be a number of different VB6 runtimes around. The one I used before when your tools were separate did not include Messenger - you might want to see if you can get the basic VB6 runtimes without the clutter.

If you set up a Paypal I will be happy to donate a few bucks for all your hard work.

[WPELLE]

Originally posted by DVD Maniac
There appear to be a number of different VB6 runtimes around. The one I used before when your tools were separate did not include Messenger - you might want to see if you can get the basic VB6 runtimes without the clutter.

If you set up a Paypal I will be happy to donate a few bucks for all your hard work.

I'll check if I can replace the runtimes in the installer with the ones in the other runtime-package.

If you really want to donate I have a paypal with the e-mailadress:
jonas.thornqvist@chello.se
I'll transfer most of the money to schlaufer since he did the hard part of this project :)

Thanks in advance.

[WPELLE]

I noticed that the version of PDITool included in the installer was out-of-date so it has been updated with version 0.7 which so far is bugfree.

[digisei]

Hi there!

I am trying to extract all files out of a pdi-file with your great tool but I have the following problem:
It analyzes and starts working well, extracting all small file (*.ifo and *.bup) but when it starts extracting vts_01_1.vob it crashes after 925MB repeatedly? What is the cause?
I tried using the installer you posted earlier but on every setup it asks to reboot the system after altering system files. If I do that it keeps on asking the same question... so I just used the plain version that worked until the reported bug.

Any suggestions?

Thanx digisei

[schlaufer]

Hi,

what is the version of PDITool and what is the (full) name of your .pdi file?

Please, if you encounter any problems, give us at least the following information:
[list=1]
The version number of PDITool (shown in it's title bar)
The output of pdixtract including it's version number. I've written in an earlier post (http://forum.doom9.org/showthread.php?s=&postid=271743#post271743) of this thread how to copy and paste it into a forum post.
[/list=1]
If it was not clear enough before: You only need the installer, if and only if, parts of the VB runtime are missing on your system. If you can start the "plain version" of PDITool, you do not need the installer.

Cheers,
schlaufer

[mpucoder]

You might want to check free space on the target hard drive, too.

[b_1_2_3]

Win2K os. getting:
Component 'Comdlg32.ocx' or one of its dependancies not correctly registered: a file is missing or invalid

I tried to install VB runtime you link in this thread: no work.

Also tried the installer you link: no work.

Install reports:

setup can not continue becuase some system files are out of date on your system. Click OK if you would like setup to update these files for you now. You will need to restat Windows...

I do that, re-boot. same message again.

IDEAS? i really wanna use this program :)

bq

[DVD Maniac]

I have WinXP and have had similar problems with MS VB runtimes. The only way to cure it was to do a fresh system build - something I do every couple of months anyway. Not that the two OS's are the same of course. Maybe the program writers can offer a less extreme solution - but I always recommend a system rebuild when you start experiencing problems loading MS software as it indicates that your registries are screwed up (something which Norton and others will NEVER fix 100% I assure you). Sorry I a cannot offer a quick fix.

[schlaufer]

Originally posted by b_1_2_3
Win2K os. getting:
Component 'Comdlg32.ocx' or one of its dependancies not correctly registered: a file is missing or invalid

I tried to install VB runtime you link in this thread: no work.

Also tried the installer you link: no work.

Install reports:

setup can not continue becuase some system files are out of date on your system. Click OK if you would like setup to update these files for you now. You will need to restat Windows...

I do that, re-boot. same message again.

IDEAS? i really wanna use this program :)

bq
First check, if there is a file named comdlg32.ocx in your Windows\System32 directory. If not, make a google search for it, there are plenty locations on the net having it.

If it is there, try to register it with the following command:
%WINDIR%\system32\regsvr32.exe /s
%WINDIR%\system32\commdlg32.ocx
(open a a command shell with "Start->Run: cmd.exe" and type the command).

If this does not enable the GUI you can still use PDIxtract as commandline tool, it does not rely on external libraries.

Cheers,
schlaufer

[b_1_2_3]

Originally posted by schlaufer
If this does not enable the GUI you can still use PDIxtract as commandline tool, it does not rely on external libraries.

Yup, I got command line working right after posting.
Gave up on the windows nonsense. Im a command line guy at heart anyway.

Great program. InstantCopy is useless without this.

Thanks!

bq

[goober22]

Well this tool is no longer working for me. It just dies on a 1gig vob file and locks up. It will extract the small files but when it hits a large vob, it dies. It leaves a 0 size file in the folder. I have to do a hard reboot because it locks my pc up.

I guess I'll be back to MrWGT's iso coverter tool and then extract from the iso. There is something in schlaufer's programs that does not like my pc! It seems hit-or-miss. Some movies extract okay and some lock up. :mad:

WinXP Pro SP1, Radeon AIW, 1gig ram, no spaces in folder names, 100gig HD - 60gig free :confused:

[Doggiedaddy]

If you guys are still getting the comdlg32.ocx error try this site they should have the ocx file. I had the file on another machine and just copied it to the system 32 folder and program now works great
hope this helps

Dd

http://www.webattack.com/help/missingfiles.html

[DMagic1]

It worked fine for another movie I did. Today it says that my 4 new pdi files(4.2gb) dont contain any data. Strange... so I used pdi2iso and it worked fine. Strange...?

[goober22]

Originally posted by Doggiedaddy
If you guys are still getting the comdlg32.ocx error try this site they should have the ocx file. I had the file on another machine and just copied it to the system 32 folder and program now works great
hope this helps

No errors for me. It looks like it is working but just locks up tight. Some movies it extracts okay, most it just locks up when it hits the first big vob (around 1gig in size). I locks up even when I just try to extract that single vob. :confused:

[schlaufer]

Originally posted by DMagic1
It worked fine for another movie I did. Today it says that my 4 new pdi files(4.2gb) dont contain any data. Strange... so I used pdi2iso and it worked fine. Strange...?

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.

[schlaufer]

Originally posted by goober22
No errors for me. It looks like it is working but just locks up tight. Some movies it extracts okay, most it just locks up when it hits the first big vob (around 1gig in size). I locks up even when I just try to extract that single vob. :confused:

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