Jevil7452
Sophomore Member
Win10toVista = Vista's "poor performance and stability" without feeling you're actually using Vista
Posts: 190
OS: Windows 10 1703 (15063)
Theme: WinTango Patcher (Shiki-Colors Noble)
CPU: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
RAM: 32GB
GPU: Intel Iris Xe Graphics G7 80EU
|
Post by Jevil7452 on Jul 27, 2022 10:47:04 GMT -8
As it's Windows NT 3.1's birthday I've decided to share a few apps from it. These are: Calculator Cardfile CD Player Character Map ClipBook Viewer Clock CMD Control Panel DDE Share FreeCell Notepad Object Packager PIF Editor Sound Recorder Volume Control Solitaire Terminal Chat Help Minesweeper Winver Attachments:NT31Apps.7z (583.62 KB)
|
|
|
|
Post by OrthodoxWin32 on Jul 27, 2022 15:28:51 GMT -8
As it's Windows NT 3.1's birthday I've decided to share a few apps from it. These are: Calculator Cardfile CD Player Character Map ClipBook Viewer Clock CMD Control Panel DDE Share FreeCell Notepad Object Packager PIF Editor Sound Recorder Volume Control Solitaire Terminal Chat Help Minesweeper Winver Impressive adaptation. Well done ! There is just a problem with paint opening in two color mode. I was able (for a year it seems to me, to adapt it correctly). I will post it soon. Also, I managed to run some of the Windows NT 3.51 Control Panel applets, and add them into the original Windows NT 3.51 Control Panel. I will post the method soon too. |
|
|
|
Post by anixx on Jul 28, 2022 8:58:50 GMT -8
I think, it is not adaptation, but original executables (they are from Windows NT 3.x).
|
|
|
|
Post by OrthodoxWin32 on Jul 28, 2022 15:13:31 GMT -8
I think, it is not adaptation, but original executables (they are from Windows NT 3.x). I meant an adaptation from the original executables (with the help of a hex editor) for programs that don't run with Windows 10 libraries. In French, adaptation does not mean quite the same thing. In French: adaptations. In English: ports. Hence my mistake. |
|
|
|
Post by anixx on Jul 28, 2022 22:35:29 GMT -8
I did not know that the original executables did not run on Windows 10. I think I have tried them once on Win8.1 and they worked.
|
|
Jevil7452
Sophomore Member
Win10toVista = Vista's "poor performance and stability" without feeling you're actually using Vista
Posts: 190
OS: Windows 10 1703 (15063)
Theme: WinTango Patcher (Shiki-Colors Noble)
CPU: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
RAM: 32GB
GPU: Intel Iris Xe Graphics G7 80EU
|
Post by Jevil7452 on Jul 29, 2022 4:04:20 GMT -8
I did not know that the original executables did not run on Windows 10. I think I have tried them once on Win8.1 and they worked. These are original executeables, they don't have any modifications. |
|
|
|
Post by OrthodoxWin32 on Jul 29, 2022 7:55:30 GMT -8
I did not know that the original executables did not run on Windows 10. I think I have tried them once on Win8.1 and they worked. These are original executeables, they don't have any modifications. It's strange, because some original executables don't run on my system (but your original executables run without problems). EDIT : I understood the problem. This is because I had left the programs in their system directory. If I copy the executables somewhere else, it works. |
|
|
|
Post by anixx on Jul 29, 2022 11:33:32 GMT -8
Honestly, I tried the executables from the beta versions as well, and beyond some build they do not work and display an error message about some dlls, and if to take even earlier builds, the Windows does not recognize the executable format at all.
|
|
|
|
Post by OrthodoxWin32 on Jul 29, 2022 11:52:52 GMT -8
Honestly, I tried the executables from the beta versions as well, and beyond some build they do not work and display an error message about some dlls, and if to take even earlier builds, the Windows does not recognize the executable format at all. In my case it was just because I was running the programs in the original Windows NT 3.51 system32 folder. If I take out the programs, it works. |
|
|
|
Post by anixx on Jul 30, 2022 0:11:35 GMT -8
Honestly, I tried the executables from the beta versions as well, and beyond some build they do not work and display an error message about some dlls, and if to take even earlier builds, the Windows does not recognize the executable format at all. In my case it was just because I was running the programs in the original Windows NT 3.51 system32 folder. If I take out the programs, it works. From all beta builds? This cannot be the case, the early betas had different exe format. The system does not recognize it as an executable. |
|
|
|
Post by OrthodoxWin32 on Jul 30, 2022 1:59:41 GMT -8
In my case it was just because I was running the programs in the original Windows NT 3.51 system32 folder. If I take out the programs, it works. From all beta builds? This cannot be the case, the early betas had different exe format. The system does not recognize it as an executable. No, in the final version. But it works when I take out the programs from the system folder. Because the programs look for the libraries in the system folder of NT 3.51, but if we move them outside the system folder, the programs use the libraries of Windows 10, and work. |
|
