Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.msdos.batch.nt    |    Fun with Windows NT batch files    |    68,980 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 68,852 of 68,980    |
|    Tom Del Rosso to All    |
|    Re: Finding names of computers in networ    |
|    27 Sep 24 04:17:21    |
      From: fizzbintuesday@that-google-mail-domain.com              JJ wrote:       >       > I think this is a problem in the network communication part, where the       > response timeout is too low. The problem is common in Windows (all       > versions; even if power management is not interfering), but rarely       > occur in Linux. So if there is a setting for that timeout, it would       > be my prime suspect.              Windows has a timeout that's too short? Incredible.              Most Windows timeouts seem to be like Robocopy, which defaults to       re-trying to copy a file every 30 seconds if it is unable to read it. It       does this a default 1 million times, so unless you specify different       numbers on the command line, it will retry a file for a few days less       than a year before going on to the next file.                     --       Defund the Thought Police              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca