> Hello,
> I've encountered two issues with Profile Batchrun using 3.64b
>
> 1. checking 'use addpaths as source' in batch rebuilder options does not work
> unless you have first entered the rebuilder menu from the main toolbar for each
> profile in the batch and checked the use add-paths as source option there.
> Otherwise you get the 'no destination set' error during the batch rebuild
> process even though you have add-paths set in the profile settings for each
> profile. If you do check the use add-paths box in the rebuilder settings for
> each profile, it works. so maybe the batch rebuilder option isn't preempting
> correctly.
>
> 2. if no files are found in the destination rom path for a profile during the
> scan part of the batch process, the 'no sets found, maybe the wrong paths were
> selected' error will appear, halting the batch process unless you click to
> acknowledge it. It would be better if it didn't halt.
>
> Thank you very much for this tool!
>



Will recheck the 1st issue later tonight. Thanks for reporting. For the second...well...SalmonKing already reported it down below...hell..why don't you have at least one single valid romname in your rompaths when you run a batch ;)

Roman Scherzer
ClrMamePro