Forum unknown
· Programming
#Software Error Requeste
7 messages in this thread
I've experimented a little more, and its dos.library complaining about an
unexpected packet (AN_AsyncPkt in alerts.h). It appears to be something in the
way that SetExcept (and exceptions in general work). Have posted a detailed
query on BIX (Byte magazine's thingie). Hope to get an answer. Thanks for your
input, though…
Anything that makes a DOS call must be a PROCESS, not a TASK. This is because
CreateProc() sets up a more elaborate control block (TCB) that DOS uses. Lots
of folks are having this problem. Apparently, you can do the TASK things on
PROCESSES (Like set priorities, etc). This area of the machine is pretty
ragged, document-wise. I have been told that it all works, though. Use
CreateProc instead of CreateTask and lots of your problems will go away. You
probably found out all this on BIX….. -Larry-
Here's a question for you:
when I type
1> prog-name
is the program executing in a new process (this is what the UNIX shell does)
or am I just a subtask of the CLI (In which case, how does hello.c even work?).
This seems to be a source for lots of misunderstanding, since AmigaDOS is
UNIX-y enough to make developer's believe things work alike.
I believe that (you didn't type the 1> part) prog-name is launched as a
sub-task of the CLI. However, the program can open its own windows, etc. This
can be demonstrated with (say) ED. If you say ED <filename>, you get a new
window which can be shrunk till you see the CLI behind it. But the cursor is
not in the CLI window, nor can you put it there.
On the other hand, if you say RUN prog-name, it actually spawns a new
CLI process and you can switch between that and the old CLI. (by clicking on
the windows).
Most C programs that use stdin and stdout get/put their stuff in the
CLI window they were launched from. So it is different from UNIX, apparently,
but then what does UNIX have to say about Windows?
I believe that (you didn't type the 1> part) prog-name is launched as a
sub-task of the CLI. However, the program can open its own windows, etc. This
can be demonstrated with (say) ED. If you say ED <filename>, you get a new
window which can be shrunk till you see the CLI behind it. But the cursor is
not in the CLI window, nor can you put it there.
On the other hand, if you say RUN prog-name, it actually spawns a new
CLI process and you can switch between that and the old CLI. (by clicking on
the windows).
Most C programs that use stdin and stdout get/put their stuff in the
CLI window they were launched from. So it is different from UNIX, apparently,
but then what does UNIX have to say about Windows?
Here's a question for you:
when I type
1> prog-name
is the program executing in a new process (this is what the UNIX shell does)
or am I just a subtask of the CLI (In which case, how does hello.c even work?).
This seems to be a source for lots of misunderstanding, since AmigaDOS is
UNIX-y enough to make developer's believe things work alike.
Anything that makes a DOS call must be a PROCESS, not a TASK. This is because
CreateProc() sets up a more elaborate control block (TCB) that DOS uses. Lots
of folks are having this problem. Apparently, you can do the TASK things on
PROCESSES (Like set priorities, etc). This area of the machine is pretty
ragged, document-wise. I have been told that it all works, though. Use
CreateProc instead of CreateTask and lots of your problems will go away. You
probably found out all this on BIX….. -Larry-