Quote:
Originally Posted by StainlessS
You have to install VDub2 on problem machine.
Could connect to problem machine and run test script in VDub2. [and get sensible error message]
Taking wild guesses at problem is not the way to go, and a waste of time asking for assistance on D9 without any clues at all.
(maybe RipBot sends error message to log file - no error report at all would seem like a serious flaw in RipBot)
|
As far as I know the only "checking" feature in RipBot is if you run a "new" script thru AVSMeter...sometimes it will hint as where the error might be, but rarely give details.
Doubt there is a log, hiding somewhere.
And like you suggest, I should install VD2, and get use to it
Cheers