More troubleshooting info (testing new tools here)
Posted by: rodocop
Date: November 15, 2017 02:04AM

So I'm glad to present you my first macro using new tools, described previously.

Let's start with just one of them - CHP.

We'll get some sysinfo for deeper troubleshooting (not only with KM but it may be used - and SHOULD be used - while asking for ANY support for your PC!)

So the Troubleshooting menu is now populated with 3-commands menu - being used to get and manage (well, too big words for that stuff, but let it be) OS information.

No trick or hard background work - this info is provided by single console command 'SYSTEMINFO' .

We only catch it using clipboard and place into txt-file. Just to open it immediately in new tab!

So every user can get his basic system info there on 'webpage', save it as html (txt is already saved on disk) or just copy needed parts of the report and send it by copypaste to the helper specialist.

So easy.

Just try and [at least] you'll know a lot of interesting about your own machine!

Also this will be good testing for macro itself. Please, pay attention to whether all toolbars and menus are in place with new macro as well as any other details of your UX (user experience) with it.

Your feedback, folks, is VERY APPRECIATED!



Macro attached as package (some folders are just empty now, but they will be populated if this macro will have any sense!)

Attachments: OSinfo.7z (3.7 KB)  
Re: More troubleshooting info (testing new tools here)
Posted by: J.G.
Date: November 15, 2017 12:08PM

Hello @rodocop,

imho this macro gets too much information and someone could talk about any kind of privacy or security related issues. However, what kind of info from systeminfo would be considered relevant for Kmeleon troubleshooting? Again imho, I like more the way of @siria's macro what gets concise info only. I meant that it could be more interesting to get some info about required *.dll, flashplayer, shockwave, java and so forth. Just my two cents, of course. Regards, J.G. smiling smiley



Edited 2 time(s). Last edit at 11/15/2017 12:11PM by J.G..

Re: More troubleshooting info (testing new tools here)
Posted by: rodocop
Date: November 15, 2017 12:19PM

J.G.

nobody sees this info except user itself. It can use it to answer standard questions about his OS and PC architecture for example.

Just copypaste non very private part of info - and still hold all the control on what is going on. ;-)

Power users and also helpers can use it to get needed info in fast and easy way. We even could create special troubleshooting browser build for system admins and techs for example - as we are able to incorporate almost any system info output that way.

Wow! It's great idea, I see!



Edited 1 time(s). Last edit at 11/15/2017 12:23PM by rodocop.

Re: More troubleshooting info (testing new tools here)
Posted by: J.G.
Date: November 15, 2017 12:42PM

Quote
rodocop
J.G.
nobody sees this info except user itself.
(...)

Very good point, thanks! :cool:

Re: More troubleshooting info (testing new tools here)
Posted by: siria
Date: November 15, 2017 12:45PM

What shall I say, you've known me for awhile, we just have different personal preferences. It sure can be handy for people who like, who prefer their browser to be an all-purpose "suite", but personally I'd rather have my browser to do browser stuff only and handle system stuff with system tools. And so far am only rarely needing complicated extensions/addons (like ExExcept), and no AutoIt so far. Occasionally could have needed one of those extended functions in a macro in the past, but oh well. Perhaps one day necessary again, then I'll probably be glad that you prepared those tools already smiling smiley

K-Meleon forum is powered by Phorum.