XPost: alt.comp.os.windows-10, alt.comp.microsoft.windows   
   From: spam@nospam.com   
      
   Kerr-Mudd, John wrote:   
      
   > Glad you got to where you wanted to, though.   
      
   Sigh. The effort spent on providing an analogy failed. :(   
   So I'll have to simply spell out what is obvious to all who understood.   
      
   This is what happened...   
      
   1. *I asked to put a process in the background so I could kill it.*   
   2. *The team came up with a Windows batch method that killed the console.*   
   3. *That method worked fine with USB cables as the port was fixed at 5555.*   
      
   However...   
   4. *Unfortunately, the Wi-Fi method _requires_ prior knowledge of the*   
      *constantly changing Android Wireless debugging port assignment.*   
      
   OK... now _this_ is the important point for Windows batch processing!   
   a. *So, for USB, the batch file works fine (as the port is static!).*   
   b. *But for Wi-Fi, the batch file random port has to be changed daily.*   
      
   Do the basic details of the problem set sink in yet?   
      
   Clearly, my recent update gave _how_ to obtain that IP address and port   
   information (whether or not Curmudgeon or McCormick understood that fact).   
      
   What _both_ of those trolls clearly didn't do was _read_ the thread.   
   Of, if they did, they didn't comprehend a word that was said in the thread.   
      
   They both posted without even thinking about what the thread was about.   
   Even as they complained that they didn't understand what it was about.   
      
   It's not my fault they don't understand the progress we made in this   
   thread, nor is it my fault that they don't understand that the port is   
   static for USB but dynamic for Wi-Fi (which is a big deal in a script!).   
      
   Nonetheless, that's water under the bridge now that I've EXPLAINED to both   
   of them what they failed to grasp (first in analogy, second in actuality).   
      
   Moving forward...   
      
   BTW, what I'm working on now, to _improve_ that process, is determining   
   _how_ Vysor.exe figures out the Android port but why Scrcpy.exe does not.   
      
   That's critical to put in the batch script:   
   _Q: How does Vysor know the adb port but scrcpy does not know it?_   
      
   If I can figure _that_ out, then there is no longer a need to add the   
   explicit IP address and port to the Wi-Fi version of the scrcpy batch file   
   originally written by Herbert (note that the USB version doesn't have that   
   problem because the USB version of Herbert's scrcpy batch script only needs   
   the port 5555 in all cases - but the Wi-Fi version uses random ports!).   
      
   If the analogy failed, did the direct 4-step explanation sink in yet?   
   --   
   HINT: See the actual resulting batch file added in the prior sig,   
   which was posted to be provide in comments why daily modification is needed   
   when on Wi-Fi even as Herbert's batch file worked fine being static on USB.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)