Hi Ernst My system time is UTC It might have been that I wasnt running it at exactly 29 min past the hour too It all seems to be working now though Regards Graham

Graham, another explanation for your problem might be that above 23:59 in the script is UTC while your system time might be 1 hour off. Cheers, Ernst

Graham, first of all this is still a CMD script with some PowerShell commands. To run a CMD script like that in PowerShell is kind of an overkill. The same is true for your solution that makes CMD

Hi Ernst Without the explicit wget path it wouldnt work on my system I tested a few times by changing the reset time to be near my system time but is now reset to 23:59 I dont have wget set in my

Graham, the 2 line make (or should make) a double reset as proposed by David. The original code using your wget.exe under Windows was: :MidnightReset set

Hi Ernst Under Windows I had to change the following lines in order for the reset to work on my system Instead of :MidnightReset set

Alan, What processor, HDD and RAM does your 15 years old PC have? We could eventually set it up under GNU/Linux amd64 to compare the TBS5927 performance with what you get under Windows 10 now. If

Thanks David and Ernst, I found the USB-C connection was too flakey as It looks like the socket is too far recessed from the case preventing it from fully seating. I could cut the hole in the mini-PC

Graham, there is more to RTFM: <CITE> :: The script must be scheduled to run in a way that it hits 23:59 exactly :: Start at minute 29 plus every 30 minutes later gives 2 entries per hour :: Start at

Hi Ernst Sorry - yes it was a typo Will re-read the file Thanks Graham

Graham, I doubt you really want the above? Assuming this is just one of your typos: Everything is clearly documented in the parameter section of the script! <CITE> :: Numeric delimiter character: Set

Hi Ernst Here are my latest files Personally I would like to replace the current delimiter with a comma rather than the apostrophe like here 183,31,'404,454 rather than 183'312'404'454 Can you point

David and Alan, as usual it's either hardware (HW) or software (SW). HW may mean the USB box itself or the USB system HW of the PC. SW may mean the driver or in case of Windows 10 IP-Tool or

Alan, I know Ian Deans reported problems with the TBS5927. I found that there were inexplicable losses - either missed and recovered (which hide actual missed and recovered) or lost, which lead to

Thanks David, I've changed this and the ramdisk trimmer to run indefinite from a time now so all should be well. I've also just swapped my USB TBS5927 to run off a USB-C port as it was previously in a

Hello to the list, anyone has either the SR1 or the TBS for sale? Thanks 73 de Enzo IK8OZV EasyLog 5 BetaTester EasyLog PDA BetaTester WinBollet BetaTester D.C.I. CheckPoint Regione

[] Alan, Yes, running indefinitely starts correctly after a reboot (at least assuming the start date is /before/ the reboot. Internally all Windows systems run in UTC, and I would hope that

NODE: EumetcastPC_HVS-2 RECV: Quad Inverto Black Ultra TBS-6909X V2 PCIe card TelliCast client(s) 2.14.7 <--- I like it flush :-)DESC: Receives BASIC (MODCODS 8PSK 3/5) + HVS-1 + HVS-2 ...

Hi Ernst Got mine running - no problems so far Regards Graham

Ernst, Local time here is always 1 hour ahead or equal to UTC so it hopefully that shouldn't be a problem. The receiving PC doesn't do anything else but Tellicast so I could change it to UTC I