New WMI query columns not appearing in results
7 posts · Closed
I've got a bit of a bug that appears every now and then. If I've got a results file already populated with multiple WMI query results, then go in and add a new WMI query, every so often when I add one, a new column for it won't appear, despite it being selected. If I go to the 'Visible Columns' dialog window, it doesn't appear as an option either.
If, however, I reorder the WMI queries and move the newly created entry above an existing (and visible) one, the column name appears with the previously-positioned columns' results, and the previously visible column heading now disappears... for example (in which I only have built-in "options" selected, and custom WMI queries)...
[image: http://www.users.on.net/~ajackson/netscan/ex1.png]
All columns are selected to be visible in the 'Visible Columns' dialog - however, if I open the WMI selection window, there are two additional queries at the bottom that are missing columns (both valid queries, both don't show in the 'Visible Columns' screen either)...
[image: http://www.users.on.net/~ajackson/netscan/ex2.png]
If I move the two missing entries from the bottom to above some existing columns...
[image: http://www.users.on.net/~ajackson/netscan/ex3.png]
The column headings adjust on the results screen (but the existing remain where they are, instead of moving with the heading), with the two newer column headings now visible, but now the two WMI queries that are at the bottom of the list are missing...
[image: http://www.users.on.net/~ajackson/netscan/ex4.png]
The only way I've been able to get this to work once columns start disappearing is to blow away the current config and create it all from scratch again :( Any ideas on this one?
It's merely a limitation of the Network Scanner's internal design. Columns are pre-created on startup and by default only 10 of each type are created (e.g. 10 x WMI, 10 x Remote Registry, etc).
This can be changed by launching the app with the /maxcols:20 or /maxcols:30 command line switch. It can be made permanent by specifying this parameter in a shortcut. The downside of this is slower startup time and higher memory usage.
I guess we'll take a look to see whether it can re-designed or otherwise improved.
Thanks for the quick reply - makes sense! Don't need to worry about it too much - the /maxcols command does the trick :)
This happens to me all the time. I run NetScan from several shares I sometimes I forget the columns. Could you just add the MAXCOLS value in the GUI in Options? -WS
Sorry, it can't be done easily - the columns are pre-created even before a config is loaded. I may be able to increase the default maximum number though. Would 20 columns of each type suffice?
Twenty would work for me :)
Yes 20 is good, may we ask of 30 as the default? Thanks -WS