From: gazelle@shell.xmission.com   
      
   In article ,   
   Robert Roland   wrote:   
   ...   
   >The issue of different locales around the world is a spectacular can   
   >of worms. Making a batch file that works with every possible   
   >combination of language and locale is a LOT more difficult that making   
   >it work on your own computer only.   
      
   I have 3 distinct comments to make on this thread.   
      
   >In addition to the multitude for formats for date and time, the   
   >response text from the NET command is translated to the language of   
   >the Windows GUI. On a Norwegian Windows, it looks like this:   
   >   
   >---   
   >C:\test>net time \\localhost   
      
   1) For whatever reason, it didn't work on my system with "localhost" (I   
   tried that first), but it works with 127.0.0.1.   
      
   2) Shouldn't this be: "netto tid \\lokalvert"?   
      
   >Gjeldende tid p \\localhost er 07.11.2020 14:35:17   
   >   
   >Kommandoen er fullfrt.   
      
   3) In a way, I'm surprised that the general solution advanced in this   
   thread actually works.  If you think about it, the most common scenario for   
   this sort of "time faking" thing is people wanting to beat software   
   licensing arrangements based on the date.   
      
   A company I used to work for routinely did this (changed their system   
   times, in the era before widespread availability of the Internet) for a   
   short period of time after the beginning of each calendar year, for a   
   certain well-known software product, before the bean counters got around to   
   authorizing the money to renew the licenses.  It was more or less done with   
   the tacit acceptance of the software vendor, since everybody understood   
   what was going on and why.   
      
   The point of all this is that nowadays, faking the local system time   
   doesn't do any good if the software can just go out on the Internet and get   
   the real date/time.  So, the upshot of this last observation is that in   
   order to be effective, any "time faking" software should trap calls out to   
   the Internet (and, in fact, also to any local hosts such as 127.0.0.1 and   
   anything else on the local LAN) and deal with those as well.  Doing this in   
   full generality is, of course, tricky, and, probably, ultimately,   
   impossible.   
      
   Thus, the fact that this hack (the one being advanced in this thread) does   
   actually seem to work, implies that the "time faking" software used by OP   
   doesn't do everything it needs to, to handle its most common use case.   
      
   Interesting, that.   
      
   --   
   b w r w g y b r y b   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)