Date format under Windows 10

Question

Hi all, 
 Just downloaded the latest Windows 10 64bit tech preview (Build 9926) Of course, the first thing I loaded up was gINT. I had the same problem as in my previous post about Windows 10 re. .NET 3.5 installation, but that was easily solved. The problem I have now is that when I fire up gINT I get the following error message:- 
 FATAL ERROR 
 gINT V8i was unable to change your Windows International Settings. Please adjust your international settings to use any character except a space as the time separator. 
 OK 
 After OKing the above I get 1) "FATAL ERROR Subscript out of range appMain.Form_Load PrinterShared.PrinterDCGet: gInt8a" then "gINT Run-time error '9': Subscript out of range" then "gINT Run-time error '5': Invalid procedure call or argument" then "gINT Run-time error '440': Automation error" 
 I have, of course, checked my date and time settings in windows, and the time setting for both long and short are using the colon as a separator, NOT a space. This was not the case in the previous build of Windows 10. I'm not expecting support for this as it's a Tech Preview build of an unreleased operating system. I'm just putting it out there in case anyone else as sad and geeky as me has come across the same issues (or not as the case may be) 
 
 Miles

Miles · Accepted Answer

Hi David, 
Here's an update for you. I had already tried running as an Admin (sorry, should have mentioned that in my initial post). I tried various compatibility modes etc on the main gINT.exe file with the same problem each time. I even tried installing a different printer because of the 2nd error message, but to no avail. In the end, I tried manually modifying the Time settings to use a "/" separator. Lo and behold, gINT started up fine! Being the wild and crazy daredevil that I am I then tried manually setting the Time setting back to ":" separator (by manually, I mean I typed the separator in, NOT selected it from the dropdown) and, would you believe it, gINT was more than happy with that and fired up fine. I must admit, I am now left scratching my head in confusion, but, at least it's now working???? 
FYI, I'm running the Win 10 preview as a virtual PC using VMWare Workstation 11 (latest build) Can't see that it would have any bearing on the situation, but... 
 
Miles

Kirk Johnson · Answer

Hi Miles, 
 
I do not have windows 10 , but out of curiosity lets see if it has something to do with permissions. right-click on the shortcut..go to properties..click on the shortcut tab ..click on advanced button and check the property.. run as admin. re-try starting gINT from the shortcut.