I will sort out a way to add a switch to allow GUI or the old display. I was trying to move away from the old display because at some point there will not be enough space to show everything. As for the unexpected '0' error i have not a clue where that coming from! The gui is language independent it just shows the text file created. regardless of character set.
Have ran it several times on a VM (win7) never failed to show the GUI display. The GUI reader I have even tried dragging a non text file to it and it will display random letters/numbers but it not crash so i not think it to do with some odd character. I will recheck the GUI's code.
I have an idea it may be a font issue. I was using Consolas which has been in windows since Vista, but i think it may of been tweaked for 7 onward. I have to use a monospaced font or the display looks really messed up as 'i' takes up less space than 'O' so it squeezes the characters together and makes the display look ugly. as can be seen on picture attached!
but consolas not cover certain dialects which i think is causing the grief, not 100% sure but it has to be the GUI that causing the error. Code: FontName Typeface Languages Since Consolas Regular, Bold, Italic, Bold Italic Latin, Greek, Cyrillic Vista Lucida Console Regular Latin, Greek, Cyrillic 98 Courier New Regular, Bold, Italic, Bold Italic Latin, Greek, Cyrillic, Arabic, Hebrew 3.1 Might try 'Courier New' as that covers a lot of areas.
ok have now done checks for those three fonts in the OS, it will pick one that is available, if none are then you will get a msgbox appear saying no font available. Just got to compile it all again and test in the QT itself...
Just sorting it all out, wont be long before i upload. Made a little change the GUI will show the Font used in the title area. If no available font then you will see an error box pop up. For some reason the exit error codes are not being passed back to the QT will have to investigate that. But hopefully this time the QT will show the GUI.
QT 62.2 uploaded, 2nd post updated with new download link, password and hashes. GUI checks for required font if not found, will try two others then if nothing available it will present an error box. Fingers crossed this one works! If not then it will be plan C... But that wont be at this moment as just after midnight here in Britain and its too damn hot to be sitting up all night coding.
probably because the FRead.exe program uses UPX to compress it. Can remove UPX it but it will make it a larger file.
OK.. QT v62.3 No longer using UPX compression so the QT will be larger in size. You will be asked if you want to use the new GUI results display or not. If not then the old display will show for the display results like it used to. Either method when saving the report it will automatically go to your Desktop and close the QT.
QTv62.3 uploaded, 2nd post updated with new download link, password and hashes. I have to go out to do a laptop screen cable replacement, so i will be away for an hour or two as it one of those units that have millions of screws and fiddly bits to remove or get at. At least now you have a choice again with the QT, but it may change in the future when display space is no longer available. Spoiler: QT 62.3 summary - 62.1 and 62.2 pulled as not fixed. + You are now asked if you want to use the new GUI or old way for displayed results. Hopefully this fixes the glitch on Windows 7 (on some languages) that the GUI does not show and either gives an error or is a blank display. Checks for certain Fonts available. + The saved report will be created on your desktop regardless unless an Antivirus (Defender usually) removes certain files required. The QT should also revert to the old style DOS box window if the new GUI cannot be used. But this is experimental and may fail to work due to the hybrid GUI.
40+ downloads and no reports of problems? Plan C was to abandon the GUI reader and to use 'Notepad.exe' instead, as long as it is not spelt different with other languages at least it will have a GUI, not as nicely colored but cant have everything. Have done a test QT and Notepad shows the display text.. Will wait and see if any problems with 62.3 and then try the notepad route. One way or another the QT will move forward.
IMHO, the Consolas font is much easier on my Tired OLD Eyes than Courier New for the GUI... Just say'n...
ah but it may not be present on all systems in the same way, as after Vista m$ altered Consolas font slightly and it not include some certain characters, not that those are used in the QT it depends on the language. But the Notepad version will use Consolas or native font so its a compromise of sorts. Will see if the GUI display fails again first then take it from there.
Plan C (Notepad) version seems to be working perfectly. If you have changed the font in Notepad then the text may look compressed up, but usually notepad is set to a mono spaced font (consolas or other) by default so it will look ok if the font not altered. Will await for any results from the current 62.3 QT and if still no go with my GUI then i will upload this 62.4 version that should work, if for some reason notepad can't be used then it will default back to the older QT way, command window with the ask to save at bottom. Will have to add more checking so that if new information added later pushes the command window too far then i can make the QT not show certain unimportant lines to make it fit the display version. The saved one will always show everything (apart from MSDM Keys etc for post-able version.). The added advantage with the notepad version is you can save the display one WITH any keys for your personal use. Just don't go posting it please!
Old GUI font is more clear to me, also when using old GUI MRP in temp don't get deleted only files inside except Disp.txt but the folder get deleted with the new GUI QTLog.log also not deleted in temp folder outside MRP folder I can post the images for Old and New GUI if you want to see how font look with me on Win10 1709
The QT log is for when the QT crashes it is by design that it is removed if the QT completes. Because of the way the command window works i will not be continuing with that method for much longer, there is just not enough space. At the moment it is 'ok' but in future it won't be, so i am moving away from that way now in readiness. I cannot please everyone and i won't even try to. There comes a point when certain methods cannot not be sustained and it is getting very close to that now -- things have to move on.