XDVD does not (seem to) launch batch

[curioffl]

I have installed xdvd (the patch, daemon tools, vlc, etc..) and I think it does not launch the batch file (and am wondering if I missed something obvious - like the "allow batch files" checkbox) (I know I know, never that easy).

Using GBPVR from the computer console, picking VOBs and trying to play them has no discernable effect.
However, if I try to run the ARMAAN VOB_02_01.vob from within GBPVR (nothing happens) but then I launch, by hand:

C:\Progra~1\VideoLAN\VLC\vlc.exe --sout=# transcode{acodec=mpga,ab=128,channels=2}:duplicate{dst=std{access=file,mux=ps,ur
l="i:\dvd.mpg"}} dvdsimple://I:\DVDDecrypter\ARMAAN\video_ts\VTS_02_1.VOB :dvdna
v-caching=7000 --sout-ffmpeg-strict 1 -I dummy --dummy-quiet --one-instance

...it counts to 150 (in chunks) and starts playing.
If I change playmvpdvdfiles.bat to contain only:

echo %1 %2 %3 >> c:\output.txt

...no c:\output.txt file is ever created.

...so I think that the batch does the right thing but gbpvr never causes it to launch.

Thanks for your thoughts.

[HtV]

Maybe it is a similar problem as in this thread: http://forums.nextpvr.com/showthread.php?t=3589&page=30 post 295.

And it surely is connected to this one: http://forums.nextpvr.com/showthread.php?t=22991

Maybe you should combine threads and forces.

[curioffl]

Say man that second link is this post...did you have an actual second posting?

Thanks a lot.

[HtV]

Probably got confused in c & p.
I meant this thread:
http://forums.nextpvr.com/showthread.php?t=22960

[curioffl]

Found it. XDVD looks for those batches in c:\program files\devnz\gbpvr. My gbpvr is installed on i:\gbpvr and the xdvd installer put them in i:\gbpvr but it looks for them in c:\program files\devnz\gbpvr (which I should have suspected all along because I noticed that it created that path on c: but it didn't put any files in it). I copied just the batches there and it appears to be working now.

[hick]

I suspect this is the problem I was having as well. XDVD didn't used to have the batch files path hard-coded and would run them when they were in my non-default install directory. Hmmm, perhaps the sql patch for xdvd caused this.