Good point Doug! This highlights part of the issue to be solved: if a race has not yet been assembled or re-loaded if previously assembled, when the tote moves on to the next race the race gets loaded/assembled and tote data fetched, correctly. This is what you see on your 2nd RDSS instance - IF you did not load all races, merely watched the current race move on to the next and the next ...
On your main RDSS however, presuming you Assembled/re-loaded all races (or several races), when the tote moves to the next race and finds the race already loaded in RDSS - it does not switch focus to that next active race and begin fetching tote info (for reasons best known to the programmer years ago ...
). Working on it ...!
Meanwhile - your suggestion does seem to work! Reminder: to load another instance of RDSS - or several - either a) right-click on the RDSS icon in the Windows Taskbar or Desktop and launch it again, or b) from the RDSS Exit/Restart dialog, choose Start Another. You can Start as many copies of RDSS as your computer memory can handle: at some point, new separate instances will just refuse to Start (or slow down to a c.r.a.w.l) - that's how you know how many your computer memory can handle!
Ted