sandbox for Win16 and DOS applications

Here you can discuss ReactOS related topics.

Moderator: Moderator Team

user222
Posts: 62
Joined: Thu Mar 03, 2005 1:21 pm

sandbox for Win16 and DOS applications

Post by user222 » Sun Mar 13, 2005 6:58 am

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.

Dr. Fred
Developer
Posts: 607
Joined: Wed Dec 22, 2004 10:09 pm
Location: Amsterdam

Post by Dr. Fred » Sun Mar 13, 2005 11:36 am

A sandbox for all kinds of apps would be nice. Of cause as a option not running automatically :)

AcetoliNe
Posts: 115
Joined: Wed Jan 05, 2005 10:53 pm
Location: a thousand miles from Hinterland
Contact:

Post by AcetoliNe » Sun Mar 13, 2005 12:31 pm

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.

user222
Posts: 62
Joined: Thu Mar 03, 2005 1:21 pm

Re: sandbox for Win16 and DOS applications

Post by user222 » Tue Mar 15, 2005 4:02 pm

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.
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.

Harteex
Posts: 224
Joined: Fri Nov 26, 2004 9:21 pm
Location: Sweden
Contact:

Post by Harteex » Tue Mar 15, 2005 4:06 pm

Just wondering, what makes 16bit apps more dangerous to the system folder and registry than 32bit apps?

Meklort
Posts: 175
Joined: Sat Mar 05, 2005 11:53 pm
Location: Colorado
Contact:

Post by Meklort » Tue Mar 15, 2005 4:10 pm

Harteex wrote:Just wondering, what makes 16bit apps more dangerous to the system folder and registry than 32bit apps?
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.

Mollyzkoubou
Posts: 5
Joined: Sat Jan 15, 2005 1:46 pm
Contact:

Post by Mollyzkoubou » Tue Mar 15, 2005 9:06 pm

Then emulate the hardware access. That's what DOSEMU does, and I believe NTVDM as well.

Moll.

Delfi
Posts: 76
Joined: Sat Nov 27, 2004 8:45 pm

Post by Delfi » Tue Mar 15, 2005 11:13 pm

meklort wrote:
Harteex wrote:Just wondering, what makes 16bit apps more dangerous to the system folder and registry than 32bit apps?
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.


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.

A-v-S
Posts: 91
Joined: Mon Dec 06, 2004 8:37 pm
Location: BAEK CITY (Beek, Limburg, The Netherlands, Europe, Earth)
Contact:

Post by A-v-S » Tue Mar 15, 2005 11:33 pm

ReactOS is a Microsoft Windows NT 4.0 clone ,WINNT supports windows 16 bit programs
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

Harteex
Posts: 224
Joined: Fri Nov 26, 2004 9:21 pm
Location: Sweden
Contact:

Post by Harteex » Wed Mar 16, 2005 4:33 am

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.

GvG
Posts: 499
Joined: Mon Nov 22, 2004 10:50 pm
Location: The Netherlands

Post by GvG » Wed Mar 16, 2005 9:15 am

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'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.

user222
Posts: 62
Joined: Thu Mar 03, 2005 1:21 pm

Post by user222 » Wed Mar 16, 2005 3:14 pm

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.
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
Posts: 224
Joined: Fri Nov 26, 2004 9:21 pm
Location: Sweden
Contact:

Post by Harteex » Wed Mar 16, 2005 5:55 pm

GvG 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 had gotten another impression before, but that's nice to hear :)
I also agree that things like that are of higher priority.
Anyway, then there is hope for the future ;)
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.
Ok I see.

user222
Posts: 62
Joined: Thu Mar 03, 2005 1:21 pm

Post by user222 » Thu Mar 17, 2005 9:11 am

Dr. Fred wrote:A sandbox for all kinds of apps would be nice. Of cause as a option not running automatically :)
I agree with you. Why implement a sandbox only for 16-bit applications? There should be one for 32-bit applications also.

Sarocet
Posts: 93
Joined: Thu Dec 23, 2004 9:06 pm
Location: España (Spain)

Post by Sarocet » Thu Mar 17, 2005 8:22 pm

Yes, i think it's a good idea to have a sandbox for every kind of app. However, i suppose you would need to write a specific sandbox for Win16 and other for Win32 (or a double-size program). What do you think?

Post Reply

Who is online

Users browsing this forum: Bing [Bot], Yandex [Bot] and 2 guests