|
|
Winver
Oct 30, 2019 5:47:36 GMT -8
Post by anixx on Oct 30, 2019 5:47:36 GMT -8
|
|
|
|
Winver
Oct 30, 2019 8:28:36 GMT -8
Post by The Jackal on Oct 30, 2019 8:28:36 GMT -8
Very impressive. Quick question ~ is that an edit of the actual winver or one you made yourself? I've be dabbling in trying to make one myself from scratch but keep putting it on the backburner. |
|
|
|
Winver
Oct 30, 2019 8:40:34 GMT -8
Post by anixx on Oct 30, 2019 8:40:34 GMT -8
Very impressive. Quick question ~ is that an edit of the actual winver or one you made yourself? I've be dabbling in trying to make one myself from scratch but keep putting it on the backburner. Neither. It is an unmodified actual winver by Microsoft. |
|
|
|
Winver
Oct 30, 2019 12:26:54 GMT -8
Post by The Jackal on Oct 30, 2019 12:26:54 GMT -8
Interesting. How did you get it running on I assume is Windows 8? Every time I've tried to load a Winver regardless where it came from it pulled it's information from the resident shell32 on the system.
|
|
|
|
Winver
Oct 30, 2019 13:35:35 GMT -8
Post by anixx on Oct 30, 2019 13:35:35 GMT -8
Interesting. How did you get it running on I assume is Windows 8? Every time I've tried to load a Winver regardless where it came from it pulled it's information from the resident shell32 on the system. The system is Win8.1 and the version information is incorrect (should be 6.3 build 9600). All pre-Win 8.1 programs report wrong version (for instance, Vista's paint and Win7's task manager report the same as this winver). This is the earliest 32-bit Winver (taken from WinNT 3.1 beta) that can run on a modern version of Windows (its internal build version is 388). There are earlier winvers but all exes from those builds give error "no entry point found in a dll". Even earerlier exes have a different exe format and are not recognized as Win32 applications. |
|
|
|
Winver
Oct 30, 2019 16:25:22 GMT -8
Post by leet on Oct 30, 2019 16:25:22 GMT -8
This happens because the application manifest needs to specify support for Windows 8.1 specifically explicitly. Else it will return version 6.2. Same thing also happens with Windows 10. |
|
|
|
Winver
Oct 31, 2019 3:50:07 GMT -8
Post by anixx on Oct 31, 2019 3:50:07 GMT -8
Another interesting thing is that sound.cpl refers to the Workplace Shell:  |
|
|
|
Winver
Nov 2, 2019 7:12:10 GMT -8
Post by The Jackal on Nov 2, 2019 7:12:10 GMT -8
VirtualBox and VMWare both have issues with this build. Don't know why - is there specific settings to get it to install? Really want to dig into the files and see what goodies I can get from it.
|
|
|
|
Winver
Nov 2, 2019 22:51:02 GMT -8
Post by anixx on Nov 2, 2019 22:51:02 GMT -8
I did not install.
|
|
|
|
Winver
Nov 3, 2019 7:04:58 GMT -8
Post by The Jackal on Nov 3, 2019 7:04:58 GMT -8
OK, I getcha ya, the files are on the CD, I've located them but now I've run into another problem: I've got the wrong build and I can't find the specific one you've got. Gonna try and locate that as the usual two sites I use to find old Windows builds doesn't have it.
|
|
|
|
Winver
Nov 4, 2019 23:11:13 GMT -8
Post by powerplayer on Nov 4, 2019 23:11:13 GMT -8
|
|
|
|
Winver
Nov 5, 2019 4:47:01 GMT -8
Post by anixx on Nov 5, 2019 4:47:01 GMT -8
|
|
|
|
Winver
Jun 17, 2020 7:08:44 GMT -8
Post by The Jackal on Jun 17, 2020 7:08:44 GMT -8
 Been having a little fun with winevdm. Not checked out anything lower than W3.1 yet (the only NT builds I've plundered are 2k and above). |
|
|
|
Winver
Oct 13, 2020 17:06:38 GMT -8
Post by anixx on Oct 13, 2020 17:06:38 GMT -8
This happens because the application manifest needs to specify support for Windows 8.1 specifically explicitly. Else it will return version 6.2. Same thing also happens with Windows 10. Is it possible to add such manifest as a stand-alone file? |
|
|
|
Winver
Oct 14, 2020 3:59:04 GMT -8
via mobile
Post by leet on Oct 14, 2020 3:59:04 GMT -8
This happens because the application manifest needs to specify support for Windows 8.1 specifically explicitly. Else it will return version 6.2. Same thing also happens with Windows 10. Is it possible to add such manifest as a stand-alone file? Yes but I can’t recall how. You can also reshack the executable to add it there. |
|
