System Info of windows

[krovit]

I am in trouble to determine the version of windows in use.

ENVIRON$ behaves differently depending on the version of windows and use GetVersion() is Microsoft depreciated...
batch files?

Can you give me some info?

Thanks!

[FellippeHeitor]

Sounds like a job for @SpriggsySpriggs!

[SMcNeill]

Shell out to: systeminfo | findstr /B /C:"OS Name" /C:"OS Version"

All you'll need to do is pipe the info there to clipboard, or to a file, and then read it in.  (change quotes to CHR$(34) characters for the SHELL statement to avoid issues.)

Results look like this (for Win 10):

systeminfo | findstr /B /C:"OS Name" /C:"OS Version"      <-- the command
OS Name:                   Microsoft Windows 10 Pro   <-- it's output
OS Version:                10.0.18363 N/A Build 18363  <-- on two lines... other OS versions may have more lines of information for you.


You can also just stick to the simple old VER command...

Code: [Select]

SHELL "ver>temp.txt"
OPEN "temp.txt" FOR INPUT AS #1
LINE INPUT #1, blank$ 'output is a blank line
LINE INPUT #1, ver$ 'and then the version, for some odd reason
PRINT ver$
CLOSE
KILL "temp.txt"


[krovit]

Thank you SMcNeill

I actually hoped that there would be a system to get that information without using the dear batch files, that is, without writing anything, but that's fine too. your example is complete and comprehensive.

[SpriggsySpriggs]

I actually hoped that there would be a system to get that information without using the dear batch files, that is, without writing anything, but that's fine too

@krovit
Here is some code that doesn't require writing to a file. This is generally faster than most regular SHELLs as well. Download the attached "pipecom.h" file and put it with your code.

Code: QB64: [Select]

1. OPTION _EXPLICIT
2.  
3. DECLARE LIBRARY ".\pipecom"
4.     FUNCTION pipecom$ (cmd AS STRING)
5. END DECLARE
6.  
7. DIM ver AS STRING
8. ver = MID$(pipecom("ver"), 2)
9. PRINT ver

[FellippeHeitor]

Important reminder: once compiled, the .h file doesn't have to be shipped with your exe, if that's a concern.

[krovit]

Hey! Thank you! now I can choose the method between the BAT file and your routine

I only have one question... I'm almost ashamed...
The *.h file seems to me to be a script in C or Java or similar languages. I saw that he goes to look for it in the same folder as the . Bas.
You tell me to import it into my code, but actually don't like that.

The fact is that no experience with the .h and QB64 files: I need a little teaching to figure out how to do in these cases...

[TempodiBasic]

Hi Krovit
in my little experience the .h files is like a DLL but GCC++ accepts it as sourceCcode at the place of a compiled file DLL.
All you need at compiling time is that the .h file must be in the QB64.exe folder and a declaration of it into the code like an external library as it does the code of Spriggsy.
At runtime you needn't the .h file, so you can think it more like a .BM file than a DLL because it has been included into the .EXE  got by compilation.

PS: have you joined to Discord for QB64?
I have tried it and I find it cool!

[krovit]

Grazie TempoDiBasic

Thank you now it's very clear the help that these little routines can give to qb64.

"Discord"...? I don't know what it is!

[bplus]

"Discord"...? I don't know what it is!

QB64 chat room on Internet, see our Home Page Announcements (at bottom) 2nd Board or just link https://discord.com/invite/2t9HTYK

[SpriggsySpriggs]

@krovit I have some new code posted here that makes the Windows version operate better. No more console window popping up.

https://www.qb64.org/forum/index.php?topic=3168.msg124345#msg124345

[bplus]

Have you checked Wiki:
https://www.qb64.org/wiki/ENVIRON$

[FellippeHeitor]

Have you checked Wiki:
https://www.qb64.org/wiki/ENVIRON$

He says so in the first post.

[bplus]

Man if it's not in here?

Code: QB64: [Select]

1. DO
2.   i = i + 1
3.   setting$ = ENVIRON$(i) ' get a setting from the list
4.   PRINT setting$
5.   IF i MOD 20 = 0 THEN PRINT "Press a key": SLEEP: CLS
6. LOOP UNTIL setting$ = ""
7.  

[luke]

Quick question, what do you need the windows version for?