With some sort of process that can run programs,obviously.Unless that's not
what you wanted?
Would you be using NASM or something of the liking,or DIRECTLY inputting
assembly/machine statements into the CPU?
On Wed, Jun 15, 2016 at 6:57 PM, Jayden Charbonneau <
binarybyte....@gmail.com> wrote:
> I may be wrong on this,but couldn't we just strip down the code used for
> FreeDOS?Removing un-needed modules,drivers,and removing any COUT/PRINTF
> statements to the point where it's just the kernel itself should do it.
>
> On Wed, Jun 15, 2016 at 4:25 AM, Maarten Vermeulen <netraa...@gmail.com>
> wrote:
>
>> I think that can be done right? If we are finished with 1.2, then we (or
>> some of us) can make it. Unless, nobody wants to do such thing. So, yeah I
>> am volunteering. but it still needs an under layer right (for running
>> programs)?
>>
>> Maarten
>>
>> --
>>
>> 2016-06-15 9:23 GMT+02:00 Eric Auer <e.a...@jpberlin.de>:
>>
>>>
>>> >From Ben Hutchinson <benh...@gmail.com>
>>>
>>> By minimal, I mean that the boot sector program, and the kernel
>>> (kernel.sys), don't do any displaying of text. All they need to do is
>>> set up the DOS interrupt vectors (so that they behave correctly just as
>>> with MS-DOS), and then load and execute the first file, command.com. No
>>> displaying text at all. The screen should remain blank until something
>>> in command.com causes text or graphics to display. Such an absolute
>>> minimal version of FreeDOS would be useful for me, because it would
>>> allow me to write my own program in assembly language, call it
>>> command.com, and then copy that file to the disk, and use it to boot
>>> another computer directly into the software I've written. This minimal
>>> version of FreeDOS would be just a boot-loader for my own OS-level
>>> software, a launch-point for my application (my application existing in
>>> place of an OS, rather than being run from an OS), that would then run
>>> upon booting.
>>>
>>>
>> Project founder and developer of BirdOS by FeatherCode
>>
>>
>>
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning
>> reports.
>> http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
>> _______________________________________________
>> Freedos-devel mailing list
>> Freedos-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>>
>>
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
