Re: [Freedos-devel] FreeDOS 1.2 and 2.0 roadmap discussion

2015-01-04 Thread Christopher Evans
+1 backwards compatibility model is a must more so than 32bit support, measuring stick should be compared to a average stock 6.22/win98 dos system. -- -Chris Evans Computer Consultant, Systems Administrator, Programmer, PC technician Digitalatoll Solutions Group (Tawhaki Software) Cell. : 916

Re: [Freedos-devel] FreeDOS 1.2 and 2.0 roadmap discussion

2015-01-04 Thread Jim Hall
I'm traveling, and likely won't be able to check email again or update the roadmap on the wiki until Wednesday. With a few disagreements, it looks like the consensus remains this: *- "FreeDOS 1.2" should be an update/refresh from FreeDOS 1.1. No major changes. Improved installer is a good idea.*

Re: [Freedos-devel] LOCK and multiuser

2015-01-04 Thread Jim Hall
On Sunday, January 4, 2015, JAYDEN CHARBONNEAU wrote: > Hello,everyone!I am creating a new security feature for the new > distribution.It is a password lockout,and can only be unlocked by the > same computer.(Meaning that you cant unlock it on another > computer).Along with this program called LO

[Freedos-devel] FreeDOS 1.2

2015-01-04 Thread JAYDEN CHARBONNEAU
Hello,everyone!I am creating a new security feature for the new distribution.It is a password lockout,and can only be unlocked by the same computer.(Meaning that you cant unlock it on another computer).Along with this program called LOCK.EXE,I've also worked on a multi-user system for freeDOS.While

Re: [Freedos-devel] Working on FreeDOS 1.2

2015-01-04 Thread Jim Hall
I thought to try something new with the updated installer. Rather than have one big program that does everything, why not create a few simple tools that can be used in an INSTALL.BAT to install FreeDOS? Enhanced Batch File tools already exist, I suppose, but I wanted free software tools. And of cou

Re: [Freedos-devel] Trying to get TVision to work on OW

2015-01-04 Thread Jim Hall
On Sat, Jan 3, 2015 at 5:52 PM, Rugxulo wrote: > > P.S. You might do better with TxWin (LGPL, C), which does explicitly > support DOS via OW: http://trac.netlabs.org/txwin/ > > Argh, his download link is broken. You might have to email him > directly (although I also seem to have a local .ZIP co

Re: [Freedos-devel] FreeDOS 1.2 and 2.0 roadmap discussion

2015-01-04 Thread Jim Hall
On Sat, Jan 3, 2015 at 10:15 PM, Michael Brutman wrote: > > If you want to run multiple virtual DOS machines at the same time use an > existing solution that already has the Virtual 8086 mode, or even an entire > virtual machine. I really can't see the advantage that you would be > getting by rei

Re: [Freedos-devel] FreeDOS 1.2 and 2.0 roadmap discussion

2015-01-04 Thread Christopher Evans
I getting better at it. Recently, made a picture viewer in visual studio, and have to play with it some more. I settled on 30 an hour for coding an app. -- -Chris Evans Computer Consultant, Systems Administrator, Programmer, PC technician Digitalatoll Solutions Group (Tawhaki Software) Cell. : 9

Re: [Freedos-devel] FreeDOS 1.2 and 2.0 roadmap discussion

2015-01-04 Thread Tom Ehlert
> I don't think I missed anything.  In his most recent post Mercury > Thirteen spoke of multiple 16 bit programs running at the same time. > That it's not EMM386 ... that is a supervisor layer for multiple virtual DOS > machines. multitasking is certainly far from trivial, but will not fill a fl

Re: [Freedos-devel] FreeDOS 1.2 and 2.0 roadmap discussion

2015-01-04 Thread Michael Brutman
I don't think I missed anything. In his most recent post Mercury Thirteen spoke of multiple 16 bit programs running at the same time. That it's not EMM386 ... that is a supervisor layer for multiple virtual DOS machines.

Re: [Freedos-devel] FreeDOS 1.2 and 2.0 roadmap discussion

2015-01-04 Thread Tom Ehlert
> The part about a kernel sensing the hardware it is on and being > able to decide to boot in classic 16 bit mode or go full 32 bit and > behave as a supervisor is technically feasible.  But I don't think > it's going to fit on a floppy disk.  you are missing the fact that device= EMM386.EXE