[Freedos-user] The FreeDOS I hope to see
Hi everybody! i just joined the mailing list and I tried out FreeDOS. Im totally impressed that this exists hah! Im a web developer and UX designer, so I know javascript, python, html etc, so clearly my programming skills wont be much use until at least version 3.0. But I can totally see this as being a great solution for an embedded system. I saw opengem, and tried it out, but a great minimalistic interface would work really well for FreeDOS - something similar to what Windows 8 uses for it's start screen. I will be tinkering around with opengem to see if I can get something like that working. I would think it would be minimal enough to have it be natively included in the kernel. I also think FreeDOS could appeal more to the media and get more publicity in tech field, and therefore more developer support, if some modern esthetic aspects that we see in different touch devices etc were brought into the project. For example, if zoom were somehow made available by OS(regardless of the current program, even freecom/command.com. so maybe a zoom solution could be a change to the display?). Speaking of command.com, maybe touch/cutemouse support could be added. Another esthetic that could be added is utilizing some modern font options (think OpenDroid, or firefox's open fonts). Again some of these things are not actually important, but they could bring more developers into the project. Im not sure if any of these things can even be done without the kernel being natively loaded into protected mode? Maybe some of these, at least, can be emulated for fun to show potential developers some esthetic potential. Ok, so Im rambling now haha. These are just some of the ideas that flew through my head while poking around. I wish i knew more about memory and OS-level programming to really knock some things off the project's to-do list. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] The FreeDOS I hope to see
On Sat, Oct 26, 2013 at 3:20 PM, Joey Puopolo jwy...@gmail.com wrote: Hi everybody! i just joined the mailing list and I tried out FreeDOS. Im totally impressed that this exists hah! DOS isn't (quite) dead. Im not sure if any of these things can even be done without the kernel being natively loaded into protected mode? Maybe some of these, at least, can be emulated for fun to show potential developers some esthetic potential. Don't expect the latter. FreeDOS is a 16 bit application, intended to be compatible with MS-DOS. I don't expect it to ever become a 32 bit application. The OS is single-user and single tasking, Early DOS applications like WordStar and Lotus 1,2,3 were character mode, running in a console. Things like GUIs run as applications on top of DOS, and mouse support is implemented by a loadable driver installed in CONFIG.SYS. (Windows 1.X - 3.X and Win95 were multitasking shells running on top of DOS, and protected mode and multitaking support were implemented by the application. Win98 used DOS as a real mode loader for Windows as the OS, and once Windows was loaded, DOS was out of the loop.) MS-DOS originated on X86 CPUs that had a 1MB address space, of which 640KB was available to user programs. Memory above 1MB was made available by as XMS by HIMEM.SYS and EMS by EMM386.SYS, but not all applications could use it. Protected mode was not implemented by MS-DOS, (I use XMS in FreeDOS, and have drivers that make is available as a RAMdisk and disk cache.) FreeDOS can't even be run in a current system without jumping through hoops. Under 32 bit Windows (2K/XP/32 bit Win7) you can run 16 bit DOS applications (but not the FreeDOS kernel) in a console window. To run DOS itself you must boot into it using something like Grub. 64 bit Windows removed support for 16 bit applications, and you must either boot into FreeDOS directly, or run it or other 16 bit applications in a virtual machine like MS's, VMWare, or Virtual Box. It's a decent embedded system for low resource X86 based devices, as long as multitasking is not a requirement. Aside from Gem as base for a GUI you might also look at FLTK, which has a port that works under FreeDOS. Good luck on touch support: that's another thing that would require a driver to support it, and none exist. Know any hardware hackers that like to code in assembler? :-) __ Dennis -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] The FreeDOS I hope to see
I am moderatly skilled at 16/32bit assembler. Just not good file system design hence why nxdos dev is stalled. I still not solved how to load a 16bit fat table on a 64k segmented memory model.. On Saturday, October 26, 2013, dmccunney wrote: On Sat, Oct 26, 2013 at 3:20 PM, Joey Puopolo jwy...@gmail.comjavascript:; wrote: Hi everybody! i just joined the mailing list and I tried out FreeDOS. Im totally impressed that this exists hah! DOS isn't (quite) dead. Im not sure if any of these things can even be done without the kernel being natively loaded into protected mode? Maybe some of these, at least, can be emulated for fun to show potential developers some esthetic potential. Don't expect the latter. FreeDOS is a 16 bit application, intended to be compatible with MS-DOS. I don't expect it to ever become a 32 bit application. The OS is single-user and single tasking, Early DOS applications like WordStar and Lotus 1,2,3 were character mode, running in a console. Things like GUIs run as applications on top of DOS, and mouse support is implemented by a loadable driver installed in CONFIG.SYS. (Windows 1.X - 3.X and Win95 were multitasking shells running on top of DOS, and protected mode and multitaking support were implemented by the application. Win98 used DOS as a real mode loader for Windows as the OS, and once Windows was loaded, DOS was out of the loop.) MS-DOS originated on X86 CPUs that had a 1MB address space, of which 640KB was available to user programs. Memory above 1MB was made available by as XMS by HIMEM.SYS and EMS by EMM386.SYS, but not all applications could use it. Protected mode was not implemented by MS-DOS, (I use XMS in FreeDOS, and have drivers that make is available as a RAMdisk and disk cache.) FreeDOS can't even be run in a current system without jumping through hoops. Under 32 bit Windows (2K/XP/32 bit Win7) you can run 16 bit DOS applications (but not the FreeDOS kernel) in a console window. To run DOS itself you must boot into it using something like Grub. 64 bit Windows removed support for 16 bit applications, and you must either boot into FreeDOS directly, or run it or other 16 bit applications in a virtual machine like MS's, VMWare, or Virtual Box. It's a decent embedded system for low resource X86 based devices, as long as multitasking is not a requirement. Aside from Gem as base for a GUI you might also look at FLTK, which has a port that works under FreeDOS. Good luck on touch support: that's another thing that would require a driver to support it, and none exist. Know any hardware hackers that like to code in assembler? :-) __ Dennis -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net javascript:; https://lists.sourceforge.net/lists/listinfo/freedos-user -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
