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!

> 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

> hell..why don't you
> have at least one single valid romname in your rompaths when you run a batch ;)
>
> Roman Scherzer
> ClrMamePro
>

Hehe, occasionally several DATs are used for a single enormous package, and if I'm trying to rebuild I may not know if I have any valid ROMs in my addpaths for each and every DAT in the package.. so I let it rebuild as part of the batch anyway, just in case..

I strongly feel, however, that such laziness on my part could be rewarded, and I wouldn't feel bad about that. :)

> Hehe, occasionally several DATs are used for a single enormous package, and if
> I'm trying to rebuild I may not know if I have any valid ROMs in my addpaths for
> each and every DAT in the package




??? The warning appears if there is not even one valid named romset in a rompath. The addpaths don't play any role.

Roman Scherzer
ClrMamePro

> 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.


It works fine here. I unchecked 'use addpath' from some profiles and kept the source empty. Running the batch with 'use addpaths as source' works like a charm.

Roman Scherzer
ClrMamePro

> > 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.
>
>
> It works fine here. I unchecked 'use addpath' from some profiles and kept the
> source empty. Running the batch with 'use addpaths as source' works like a
> charm.
>
> Roman Scherzer
> ClrMamePro
>




grah....you talk about the rebuilder destination. Addpaths replace the destination source and have nothing to do with the destination. The destination not set error appears, since a profile got no set default rebuilder destination. The default to the 1st rompath is just a gimmick by the rebuilder window.

Roman Scherzer
ClrMamePro