BetaArchive Logo
Navigation Home Database Screenshots Gallery Image Uploader Server Info FTP Servers Wiki Forum RSS Feed Rules Please Donate
UP: 31d, 18h, 43m | CPU: 22% | MEM: 5782MB of 12287MB used
{The community for beta collectors}

Post new topic Reply to topic  [ 32 posts ]  Go to page Previous  1, 2
Author Message
 PostPost subject: Re: [Guide] How to identify the build of other OS:es        Posted: Wed Oct 08, 2014 4:06 pm 
Reply with quote
FTP Access
User avatar
Offline

Joined
Thu May 01, 2014 10:26 pm

Posts
1475

Location
Inside the space between . and I

Favourite OS
Nashville 4.00.83
IBM OS/2 Warp:
(also works with OS/2 2.x - untested with 1.30 Extended Edition)
1. Open the install (disk 0) img dump and drag the os2krnli file to the desktop.
2. Open os2krnli with notepad (or textedit if on a mac).
3. Do a search for "Internal revision". Next to that phrase is the revision/build number.
Image

_________________
Image


Top  Profile
 PostPost subject: Re: [Guide] How to identify the build of other OS:es        Posted: Sat Nov 22, 2014 9:11 am 
Reply with quote
Donator
User avatar
Offline

Joined
Sun Dec 30, 2007 8:12 am

Posts
1145

Location
Brisbane, Queensland

Favourite OS
OS/2 Wrp 3.0
Most of the recent (ie 2.1 and later) OS/2 versions give the build on ver /r at the command prompt.

Note the cmd line for vers a.b gives 2.ab.1234 where 1234 is the OS level.

Take command/os2 gives OS/2 Warp Connect as 3.1, and since there is an OS/2 Warp, i use 3.1 to refer to the latter build.

Regarding DOS.

MS-DOS generally returns the value from the interrupt, as jj.mm (major-minor). Some exceptions apply

msdos 6.21 returns jj.21
msdos 7.xx and later return a string embedded in command.com, eg 4.10.2222. You can edit this yourself.
ntdos returns jj.mm.500, where jj.mm is the underlying DOS version.

PC-DOS from 6.0 returns a string embedded in command.com.
os2 dos returns 2.jm but answers to 20.jm to a DOSVER interrupt test.

You are better to run some third-party utility that intercepts the underlying interrupts, rather than reading command.com.

Winver returns a windows version, as does shell.dll (eg notepad -> help|about ). I've seen non-released versions here, eg WinOS2 3.11 (ie from the winos2 shell.dll running on top of windows 3.11).


Top  Profile  WWW
 PostPost subject: Re: [Guide] How to identify the build of other OS:es        Posted: Wed Dec 24, 2014 10:25 am 
Reply with quote
FTP Access
User avatar
Offline

Joined
Thu Oct 18, 2012 1:59 pm

Posts
1001

Location
Avalon

Favourite OS
6.0.4083
Linux (Kernel Version):

Open a terminal, and enter the command:

Code:
uname -r


The resulting output will be the version of the Linux kernel used on the system.

Image

Image

_________________
Linux/BSD Distribution Betas
Enabling Aero in Windows Vista 50xx+ (VMware)


Top  Profile
 PostPost subject: Re: [Guide] How to identify the build of other OS:es        Posted: Sun Dec 28, 2014 1:07 pm 
Reply with quote
Donator
User avatar
Offline

Joined
Sun Dec 30, 2007 8:12 am

Posts
1145

Location
Brisbane, Queensland

Favourite OS
OS/2 Wrp 3.0
MS-DOS and PC-DOS. xx.yy

"ver" generally returns the dos version. Some differences are known.

DOS 4.01 returns xx.(yy+1)
MS-DOS 6.21 returns xx.21
WinNT DOS returns xx.yy.500 (where xx.yy is typically 5.50)

PC-DOS 6.x and later returns a string embedded in COMMAND.COM
DOS95 returns a string embedded late in COMMAND.COM

These dos versions differ from the box-name. Command,com reports the version from a string in the exe file.
DOS 4.01 is actually 4.00
PC-DOS 6.10 is actually 6.00
MS-DOS 6.21 is actually 6.00
OS/2 DOS reports 20.xy where x.y is the OS/2 version. vers 1.x reports 10.xy.
DR-DOS returns the emulated DOS, but this is the default OSVER variable. Internally it uses a different build number.

MSD or 4DOS reports the dos by int30 call etc.


Top  Profile  WWW
 PostPost subject: Re: [Guide] How to identify the build of other OS:es        Posted: Sun Dec 28, 2014 5:08 pm 
Reply with quote
FTP Access
User avatar
Offline

Joined
Mon Oct 14, 2013 2:13 am

Posts
481

Location
Los Angeles, CA

Favourite OS
Windows 8.1 6.3.9600.16497
For Windows Vista and above, won't "slmgr.vbs /dlv" work?

_________________
XDA-Developers: mr_verystock
Facebook: ___ ___ng
Skype: hellohellohello148
Google +: okcn .aline
Tom's Hardware : okcnaline
OSBetaArchive: ExplicitNuM5


Top  Profile
 PostPost subject: Re: [Guide] How to identify the build of other OS:es        Posted: Fri May 06, 2016 9:56 am 
Reply with quote
FTP Access
Offline

Joined
Mon Jan 04, 2016 11:24 pm

Posts
26

Favourite OS
OS/2
DiskingRound wrote:
IBM OS/2 Warp:
(also works with OS/2 2.x - untested with 1.30 Extended Edition)
1. Open the install (disk 0) img dump and drag the os2krnli file to the desktop.
2. Open os2krnli with notepad (or textedit if on a mac).
3. Do a search for "Internal revision". Next to that phrase is the revision/build number.


It does work with OS/2 1.3x, however, the build number sequence is a bit odd.

For 1.30.x the build numbers seem to be 7.2xx

For 2.xx the build numbers seem to be 6.3xx

For 3.x the build numbers seem to be 8.xxx

There is no internal revision comment in OS/2 1.1x or OS/2 1.2x.


Top  Profile
 PostPost subject: Re: [Guide] How to identify the build of other OS:es        Posted: Fri May 06, 2016 3:04 pm 
Reply with quote
Donator
User avatar
Offline

Joined
Fri May 14, 2010 1:29 pm

Posts
825

Location
Southern Germany

Favourite OS
IRIX 5.3
for OpenVMS, the command is
Code:
$ SHOW SYSTEM/NOPROCESS
OpenVMS V7.3  on node MYVAX   6-MAY-2016 15:06:39.90  Uptime  0 00:01:39


Some more details can be seen during boot:
Code:
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
%SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
   OpenVMS (TM) VAX Version V7.3     Major version id = 1 Minor version id = 0
%DECnet-I-LOADED, network base image loaded, version = 05.0E.00


From 7.3 onward, additional layered products and their versions can be seen by
Code:
$ PRODUCT SHOW PRODUCT/FULL
----------------------------------- ----------- ------------ ----------------------------------- -----------------------------------
PRODUCT                             KIT TYPE    STATE        MAINTENANCE                         REFERENCED BY
----------------------------------- ----------- ------------ ----------------------------------- -----------------------------------
DEC VAXVMS DECNET_OSI V7.3          Full LP     Installed
DEC VAXVMS TCPIP V5.1-15            Full LP     Installed
DEC VAXVMS VMS V7.3                 Transition  Installed                                        DEC VAXVMS DECNET_OSI V7.3
                                                                                                 DEC VAXVMS TCPIP V5.1-15
----------------------------------- ----------- ------------ ----------------------------------- -----------------------------------

3 items found


Edit: Bruce Hamilton's UNIX Rosetta Stone Website might also be helpful for some...

_________________
I upload stuff to archive.org from time to time. See here for everything that doesn't fit BA


Top  Profile
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 32 posts ]  Go to page Previous  1, 2




Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  

All views expressed in these forums are those of the author and do not necessarily represent the views of the BetaArchive site owner.

Powered by phpBB® Forum Software © phpBB Group

Copyright © 2006-2019

 

Sitemap | XML | RSS