----- Original Message -----
From: "Adriano Camargo Rodrigues da Cunha"
<adriano(_en_)alsoftware(_punto_)com(_punto_)br>
To: <hispamsx(_en_)yahoogroups(_punto_)com>
Sent: Saturday, March 27, 2004 10:44 PM
Subject: Re: [hispamsx] Hello World !!!! para MNBIOS
between tasks. And if you save them in a shared area, you`re mixing
shared
data with process data. If an process crashes, it can crash other
process
as well, and it`s very very bad.
Not mixing nothing... sharing. is the ability to distribute resources.
?!?!?!?!?!??!?!?!
Are you sure you read my message and replyed the correct text????
Distribute resources != program data.
Distribute resources != sharing data.
Will you `distribute` the stack of current foreground process with the
stalled
processes??? I don` think so.
If you are trying to say that you save current process data on a shared
area,
it`s not `distributing resources` or `sharing data`. It`s a bad design
decision.
Should I explain why?
I think the discussion here is over... we both are talking in a secondary
lenguage and i detect some confusion some times, and i not want repeat or
confuse me and you more... i will left this point.
So MNBIOS application can output data to screen only when they`re
foreground
tasks? Hum... So MNBIOS applications must conform to some sort of
`model-view-
presentation` scheme, that makes things harder for programmers...
Mainly
when
you`re talking about ASM programming.
Is structure programming, MNBIOS is a structure OS.
You didn`t reply my question and now you introduced a new type of
operating
system... :) `structured OS` doesn`t mean nothing. Even a Pascal program
is
structured. If you`re saying that `MNBIOS applications must conform to a
structure`, it`s also obvious, because all applications must do this (for
all OS,
or even for a machine without an OS).
Sorry, i try to explan than the old way to programming, as "stand alone
programming" (like the structure of a MSX-BASIC program) is bad decision...
because that kind of program are not well structured at all... generally use
a lot of GOTO and in a OS like MNBIOS, programming in that way will be a lot
of problem.
I`m sorry, but I really didn`t understand what you tried to explain.
Please read the manual, on the first chatper (or second), you will learn
how
to structure a program under MNBIOS...
Ok, ok.
If I read this manual, I hope you guys are prepared for a lot of english
comments. :)))
And if background applications can never output data to screen
YES, for the moment YES... about SCREEN. I need check if is possible to
change the active window on the BackGround proccess and restore it
before
exit, that for allow to output chrs to the windows....
Virtual screens? Hum... This will need a lot of memory... And video
functions
will be slowed...
MNBIOS not got obviously "VIRTUALs screenS". Got a windowing manager..
So in kernel mode the system cannot be interrupted?
No to run background process, yes for interrupt BIOS tasks.
But that`s bad. You may get reentrant BIOS calls and even corrupt
current processing of a BIOS call if it`s interrupted by a user request...
no, you are confused.... sorry...i think lenguage wall!...i re-read that i
wrote and .... my english suck
No to run background process, yes for interrupt BIOS tasks.
is an attempt to say : No, for run background process, but YES for do the
interrupt BIOS things like READ the KEYBOARD.
You`re confusing basic concepts of OS. `Kernel mode` and `user mode`
doesn`t
means security, but mainly two different operating modes. If you don`t
have them,
you don`t have an OS, specially if talking about a multitask OS.
That is not true...you know that as all know that is the definition of
an
OS.
This sentence is a bit confuse. I didn`t understand it, and it doesn`t
seems to
refute what I wrote. I`m not talking about the definition of an OS. I`m
talking
about operating modes of an OS.
Maybe you not understand what i mean because you only are thinking in
the
UZIX way.
No. I disagree because you confused `security` with `operating mode`.
I not understand at all what you are trying to say...
if you want please use the MSN... you already got my msn.
Regards,
Adriano
*HispaMSX. La mailing-list de MSX en castellano*
Para cualquier duda: hispamsx-owner(_en_)yahoogroups(_punto_)com
Web de lista: http://www.hispamsx.org
Enlaces a Yahoo! Grupos
Para visitar tu grupo en la web, accede a:
http://es.groups.yahoo.com/group/hispamsx/
Para cancelar tu suscripción en este grupo, envía
un mensaje en blanco a:
hispamsx-unsubscribe(_en_)yahoogroups(_punto_)com
El uso que hagas de Yahoo! Grupos está sujeto a
las Condiciones del servicio de Yahoo!:
http://es.docs.yahoo.com/info/utos.html
