|
|
OpenNT
May 14, 2016 16:12:56 GMT -8
Post by powerplayer on May 14, 2016 16:12:56 GMT -8
|
|
|
|
OpenNT
May 31, 2016 21:08:43 GMT -8
Post by R.O.B. on May 31, 2016 21:08:43 GMT -8
Sorry I didn't reply to this earlier. The only problem I see with this is the potential legal issues we could potentially run into. But I won't dismiss it just yet.
|
|
freedom7341
Freshman Member
The Windows NT Program Manager
Posts: 69
OS: Windows Vista Ultimate x64
Theme: NT Style
CPU: i7 3740QM
RAM: 14GB DDR3
GPU: Radeon 7770M
|
OpenNT
Jun 10, 2022 12:59:16 GMT -8
Post by freedom7341 on Jun 10, 2022 12:59:16 GMT -8
Has anyone looked into doing this yet? Or had a successful attempt doing this with either OpenNT or NT 4 source?
|
|
|
|
OpenNT
Jun 15, 2022 18:34:39 GMT -8
Post by nonameneeded on Jun 15, 2022 18:34:39 GMT -8
This OpenNT seems to be pretty dead.
But even if it wasn't, what's the idea behind it?
Using an old version of explorer.exe (so old that it certainly wouldn't work with Windows 10) wouldn't make much sense.
|
|
herit://that1cutie
Sophomore Member
sad girl times
Posts: 164 
OS: Windows 10
Theme: Shitbox Edition
|
OpenNT
Jun 16, 2022 18:25:27 GMT -8
Post by herit://that1cutie on Jun 16, 2022 18:25:27 GMT -8
OpenNT turned into ReactOS. The explorer from ReactOS has been ported, but not the shell32.dll to my knowledge. This post was made I believe before OpenNT became ReactOS. I don't have a link to the ReactOS explorer Windows port, but you can find it here on these forums without much searching.
On another note I am very interested in creating a 64 bit version of Windows 2000 with (or a themed version of Windows 10) which would be simply called Windows Classic. Unfortunately I don't know enough about the subject to actually create my own OS without help. The main point I want to achieve is compatibility. 80s DOS program compatibility, 90s DOS program compatibility, Windows 3.1 program compatibility, Windows 9x program compatibility, and Windows XP program compatibility. Particularly also compatible with modern windows 10 softwares as well including DX12 Ultimate. Again, don't know how to do this. Closest I've gotten is theming my particular Windows build and adding both NTVDMx64 and OTVDM which allows me to use DOS and Win3.1 programs on my 64 bit machine without external tools like DOSBox.
|
|
|
|
OpenNT
Jun 17, 2022 6:49:51 GMT -8
Post by nonameneeded on Jun 17, 2022 6:49:51 GMT -8
ReactOS has been around since the late 90s, so if OpenNT turned into ReactOS it must have been an additional component, which I doubt because NT is an OS already (at least that's what the name implies) Additionally, I think you mix a few things up. You wouldn't be able to run MS DOS programs on a 64Bit OS, at least not natively. It's probably not possible to create an OS that is compatible with all kinds of software (from the 80s, 90s, 2000s etc.) That's why there are emulators and things like that. BTW: If you want to run 16bit Windows applications (Win 3.1) on 64Bit OSes, give OTVDM a try. It's been improved quite a bit over the last years, even Office applications like Word (6.0) can be used on 64Bit OSes thanks to OTVDM. ci.appveyor.com/project/otya128/winevdm/build/job/67quxqb49scw3jl9/artifacts |
|
|
|
OpenNT
Jun 17, 2022 10:00:52 GMT -8
Post by OrthodoxWin32 on Jun 17, 2022 10:00:52 GMT -8
OpenNT turned into ReactOS. The explorer from ReactOS has been ported, but not the shell32.dll to my knowledge. This post was made I believe before OpenNT became ReactOS. I don't have a link to the ReactOS explorer Windows port, but you can find it here on these forums without much searching. On another note I am very interested in creating a 64 bit version of Windows 2000 with (or a themed version of Windows 10) which would be simply called Windows Classic. Unfortunately I don't know enough about the subject to actually create my own OS without help. The main point I want to achieve is compatibility. 80s DOS program compatibility, 90s DOS program compatibility, Windows 3.1 program compatibility, Windows 9x program compatibility, and Windows XP program compatibility. Particularly also compatible with modern windows 10 softwares as well including DX12 Ultimate. Again, don't know how to do this. Closest I've gotten is theming my particular Windows build and adding both NTVDMx64 and OTVDM which allows me to use DOS and Win3.1 programs on my 64 bit machine without external tools like DOSBox. Reactos has little to do with Open. Reactos is an attempt at retro-engineering of the Windows NT code (Server 2003), while OpenNT is an attempt to continue the development of Windows NT4 from its source code (since its illegal disclosure). As for your project, I did not understand very well. Do you want to create a personalized image of Windows 10, or a personalized image of Windows 2000 ? Regarding compatibility, the main point to improve is NTVDMX64, which still lacks stability (but the project progresses well). Regarding the compatibility of 9X programs, most 9X programs (and NT programs), are completely compatibly with current standards, with the exception of the programs installed by default on old Windows. |
|
|
|
OpenNT
Jun 17, 2022 10:07:33 GMT -8
Post by OrthodoxWin32 on Jun 17, 2022 10:07:33 GMT -8
Has anyone looked into doing this yet? Or had a successful attempt doing this with either OpenNT or NT 4 source? I think the advantages of adapting the explorer of NT4 are numerous. This also includes performance and stability (the current explorer is completely bloated). I even think that it is theoretically possible to create a version with features that appeared later in the history of Windows, but much cleaner than Microsoft has done. |
|
freedom7341
Freshman Member
The Windows NT Program Manager
Posts: 69
OS: Windows Vista Ultimate x64
Theme: NT Style
CPU: i7 3740QM
RAM: 14GB DDR3
GPU: Radeon 7770M
|
OpenNT
Jun 17, 2022 13:31:52 GMT -8
Post by freedom7341 on Jun 17, 2022 13:31:52 GMT -8
Given not only the NT 4 but also, through special means, other Windows version sources, one could adapt the explorer source code for compilation on newer systems similar to how I have done with Program Manager. Was only curious to see if anyone else had done so.
|
|
herit://that1cutie
Sophomore Member
sad girl times
Posts: 164
OS: Windows 10
Theme: Shitbox Edition
|
OpenNT
Jun 17, 2022 14:03:08 GMT -8
Post by herit://that1cutie on Jun 17, 2022 14:03:08 GMT -8
ReactOS has been around since the late 90s, so if OpenNT turned into ReactOS it must have been an additional component, which I doubt because NT is an OS already (at least that's what the name implies) Additionally, I think you mix a few things up. You wouldn't be able to run MS DOS programs on a 64Bit OS, at least not natively. It's probably not possible to create an OS that is compatible with all kinds of software (from the 80s, 90s, 2000s etc.) That's why there are emulators and things like that. BTW: If you want to run 16bit Windows applications (Win 3.1) on 64Bit OSes, give OTVDM a try. It's been improved quite a bit over the last years, even Office applications like Word (6.0) can be used on 64Bit OSes thanks to OTVDM. ci.appveyor.com/project/otya128/winevdm/build/job/67quxqb49scw3jl9/artifactsSeems I was misinformed on things. I am using OTVDM and NTVDMx64 for DOS and Windows 3.1 programs respectively. It is effectively the "real mode" that is missing from Windows 64 bit. I did not now ReactOS was that old. I want my project to likely be a themed Windows 10 revolving around Classic theme and compatibility. Could be based off a Linux distro for all I care as long as it works. |
|
