sandbox for Win16 and DOS applications
Moderator: Moderator Team
sandbox for Win16 and DOS applications
Microsoft does not provide a sandbox for Win16 and DOS applications. Win16 applications can still modify the registry, or add files to the system directory. Win16 task mangers can even see Win32 processes. I don't think this is a good thing. I hope ReactOS would have a sandbox for Win16 and DOS applications.
-
- Posts: 115
- Joined: Wed Jan 05, 2005 10:53 pm
- Location: a thousand miles from Hinterland
- Contact:
maybe, but you have to realize that doing such a thing would be hard work. Creating a sandbox for Win16 processes would mean a whole lot of modifications to the architecture of ReactOS. This is one of those things that would be nice to implement in the future, but definately not at this time.
caveman LIKES chocolate.
we shall reinvent the wheel until it turns properly.
we shall reinvent the wheel until it turns properly.
Re: sandbox for Win16 and DOS applications
It's even worse. NTVDM even maps Win16 variables to their Win32 equivalents. Win16 applications can even modify Windows color scheme or the default Windows shell. Some examples are "Workplace Shell for Windows"; it modifies the "Shell" started by "Winlogon", and the Windows 3.11 tutorial; it modifies the Windows color scheme.user222 wrote:Microsoft does not provide a sandbox for Win16 and DOS applications. Win16 applications can still modify the registry, or add files to the system directory. Win16 task mangers can even see Win32 processes. I don't think this is a good thing. I hope ReactOS would have a sandbox for Win16 and DOS applications.
-
- Posts: 5
- Joined: Sat Jan 15, 2005 1:46 pm
- Contact:
meklort wrote:I'm not sure if there is anything bad about that, but i do know lots of 16bit apps try and access the hardware directly wich is not allowed.Harteex wrote:Just wondering, what makes 16bit apps more dangerous to the system folder and registry than 32bit apps?
so lets block them like windows does..
you have to ask yourself WHY those apps use hardware directly:
- lack of drivers
- faster code
- usually they access com and lpt ports, no big deal if you ask to me..
so why do you want to run 16 bit apps aniway?
thy practicly died-out.
-
- Posts: 91
- Joined: Mon Dec 06, 2004 8:37 pm
- Location: BAEK CITY (Beek, Limburg, The Netherlands, Europe, Earth)
- Contact:
ReactOS is a Microsoft Windows NT 4.0 clone ,WINNT supports windows 16 bit programs
then i think ROS should do so too.
then i think ROS should do so too.
"you laugh at me because I'm different, I laugh at you because you're all the same"
http://www.il.fontys.nl/~andre
http://www.il.fontys.nl/~andre
Yes, of course they can't access the hardware directly. So that has to be emulated/blocked.
I hope ReactOS will run 16 bit apps in the future, though it looks like none of the current team is interested in it.
But the things user222 posted about is the registry, the system directory and the ability for 16 bit apps to see 32 bit processes.
I don't really see the problem with that.
I hope ReactOS will run 16 bit apps in the future, though it looks like none of the current team is interested in it.
But the things user222 posted about is the registry, the system directory and the ability for 16 bit apps to see 32 bit processes.
I don't really see the problem with that.
It's not so much that I'm not interested, it's more that there are so many other things to do. If I have to choose between (to name a few) getting FireFox running, implementing DirectX and implementing a 16 bit subsystem, then the 16 bit subsystem is going to loose.Harteex wrote:I hope ReactOS will run 16 bit apps in the future, though it looks like none of the current team is interested in it.
It is because many times a Win16 task manager would not function correctly with Win32 processes. They sometimes see the windows belonging to one Win32 process as separate processes.Harteex wrote: But the things user222 posted about is the registry, the system directory and the ability for 16 bit apps to see 32 bit processes.
I don't really see the problem with that.
I had gotten another impression before, but that's nice to hearGvG wrote: It's not so much that I'm not interested, it's more that there are so many other things to do. If I have to choose between (to name a few) getting FireFox running, implementing DirectX and implementing a 16 bit subsystem, then the 16 bit subsystem is going to loose.
I also agree that things like that are of higher priority.
Anyway, then there is hope for the future
Ok I see.user222 wrote:It is because many times a Win16 task manager would not function correctly with Win32 processes. They sometimes see the windows belonging to one Win32 process as separate processes.
Who is online
Users browsing this forum: Ahrefs [Bot] and 41 guests