VCDXBuild stall may be machine related?

[Revhead]

I have been having a problem with D2S stalling in the bin/cue creation stage.
VCDXBuild starts but then just sits there and does nothing.
I think others have been having this problem too from what I have read.
Anyway, I just wanted to share one experience which leads me to believe the problem may be machine specific.
After the last time it happened I copied all the files from that machine to another and then used the second machine with same version of D2S (B3 1c) and TMPG to finish the job.
But first I had to edit all the drive letter references to reflect the new drive structure of the second machine so it could find everything it needed.
To cut a long story short it worked!
Any ideas what may be getting in the way on the first machine?
It's a 1.2G Duron, 256M DDR, 40G HD, W2K PRO SP2.

[UltimateDBZ]

If in fact it is machine related, it could be any number of factors. It's unlikely that the main specs (cpu speed, ram, etc.) would be the problem. It would be something more specific, but I really have no idea what it could be.

[idbirch2]

It could be machine specific, but the problems i have with VCDXBuild (crashes whole PC while creating images) cannot be recreated - they are random. Using the 'recover' option creates images fine and i can encode a movie and have it crash, then re-encode the same movie and it'll work. Buggered if I know - only thing I can possibly imagine it could be is HDD (yet I have a WD 60GB which is a damn good drive and never has probs with any other proggies)

Oh well, I don't think anyone's going to figure this one out. I Just hope a new version of VCDXBuild comes out soon - has anyone else noticed that if you go to VCDXBuild's website it states that this version (included with DVD2SVCD) is unstable? - seems a bit dodgy to me......

[Revhead]

Two other things I noticed.
When you uninstall and reinstall D2S, it doesn't remove the VCDImager folder nor some of the files in it. In fact, to get rid of them you have to do a restart or they remain locked.
The other thing is that if you close and reopen D2S after it stalls, then have a look in task manager and you'll see a couple of instances of VCDXBuild still running. Again you need to do a restart to get rid of them.
I'm wondering whether the problem might have something to do with the directory structure being too complex for the program to follow because the term verbose appears in the initialisation string for VCDXBuild?
PS.
Found this in the accompanying bugs.txt file:

vcdimager/vcdxbuild
~~~~~~~~~~~~~~~~~~~
*) scantable creation/playing time detection still not accurate enough
*) mpeg analyzation doesn't detect all non-conforming parameters
*) memleaks exist