Usually when opening a console the cmd line is 'C:\Windows\System32\cmd.exe',
while when double clicking a bat the cmd line is 'C:\WINDOWS\system32\cmd.exe /c "<path to batch fie>" ',
which might result in different defaults beeing loaded.
You might check the default values by:
- creating a link to 'cmd.exe', double click it, then right click the window icon on the top left and click properties in the menue poping up.
- creating a batch file that doesn't immediately close (for example use pause), double click it, then right click the window icon on the top left and click properties in the menue poping up.
Usually the mode command sets the lines and columns of the console screen buffer and then tries to resize the console window to display as much as possible.
I'm not familiar with cmdwiz.exe, but i assume using the parameter 'setbuffersize' probably exclusively sets the buffer size without trying to ressize the window to fit, so i wouldn't expect any changes (no matter whether or not it tries to resize the window), because the mode command already did that.
It's somewhat unusual, that the mode command doesn't set the window screen height to the desired value, when it's possible for other console window instances, though.
What comes to my mind ad hoc is, that the bigger window is smaller than the windows desktop size, but bigger than the desktop height minus the taskbar height; a little bit unusual for a screen height of 27 (but possible, for example when you are using an unusual big font height).
Another possibility is that your laptop is using a TrueType font and the screen width/height calculation is a little bit off (which might happen for various reasons, such as windows rejecting to set specific sizes for whatever reason, silently adding 1 or 2 pixels, or characters ignoring any metrics of the TrueType font like the top side bearing). Note that using TrueType fonts in the console always bears the risk that the line heights and widths might vary depending on the characters beeing displayed (because it#s always possible that a character ignores the Trytype font's default sizes or spacings.
Alternatively there might be other explanations for that, which i didn't think of.
In case consolewiz is able to set the window size (though probably set in pixels in case it is able to) you could try that as well, but it most probably will fail, if any user's windows gets to the conclusion that the desktop dimension is too small (for whatever reasons).
I'm not sure whether or not cmdwiz is able to change a TrueType font to a raster font (in case your batch doesn't need to use TrueType fonts), in case that's the issue - mentioning those issues in your documentation would be sufficient in my eyes, but you are not me and might have a different opinion on that, which is perfectly fine.
penpen
