Just wanted to confirm that the CLI structure returncodes are still valid
by the time the process cleanup() code is called (ie; exitcode() location)
I opened up a shell, did a dir of a bad path, it failed, then closed the shell
and this is what was in the cli structure when the process was being ...
Search found 212 matches
- Mon Mar 17, 2025 12:03 am
- Forum: General Developer Support
- Topic: Crash when reading from a PIPE:
- Replies: 13
- Views: 78333
- Thu Mar 13, 2025 12:38 pm
- Forum: General Developer Support
- Topic: Crash when reading from a PIPE:
- Replies: 13
- Views: 78333
Re: Crash when reading from a PIPE:
The NP_ExitCode and NP_ExitData are supported on both OS3 and OS4.
It's just that the 3rd argument(SysBase:A6) is not available for OS3,
I added that for OS4 in 53.38
The reason it works on OS4 is because I intentionally preserve the returncode
and result2 codes right up to the exitcode function ...
It's just that the 3rd argument(SysBase:A6) is not available for OS3,
I added that for OS4 in 53.38
The reason it works on OS4 is because I intentionally preserve the returncode
and result2 codes right up to the exitcode function ...
- Sun Mar 02, 2025 10:52 pm
- Forum: General Developer Support
- Topic: ACTION_DISK_INFO and console
- Replies: 1
- Views: 10608
Re: ACTION_DISK_INFO and console
See;
dos.library/ObtainConsoleData() and dos.library/ReleaseConsoleData()
Also See;
ACTION_OBTAIN_CON_INFO and ACTION_RELEASE_CON_INFO packets.
dos.library/ObtainConsoleData() and dos.library/ReleaseConsoleData()
Also See;
ACTION_OBTAIN_CON_INFO and ACTION_RELEASE_CON_INFO packets.
- Wed Feb 26, 2025 5:21 am
- Forum: General Developer Support
- Topic: Crash when reading from a PIPE:
- Replies: 13
- Views: 78333
Re: Crash when reading from a PIPE:
/****** dos.library/System ************
*
* NAME
* System -- Have a shell handler execute a command line. (V36)
*
* SYNOPSIS
* int32 error = System(CONST_STRPTR command,
* const struct TagItem *tags);
*
* int32 error = SystemTagList(CONST_STRPTR command,
* const struct TagItem *tags);
*
* int32 ...
*
* NAME
* System -- Have a shell handler execute a command line. (V36)
*
* SYNOPSIS
* int32 error = System(CONST_STRPTR command,
* const struct TagItem *tags);
*
* int32 error = SystemTagList(CONST_STRPTR command,
* const struct TagItem *tags);
*
* int32 ...
- Wed Feb 26, 2025 5:20 am
- Forum: General Developer Support
- Topic: Crash when reading from a PIPE:
- Replies: 13
- Views: 78333
Re: Crash when reading from a PIPE:
/****** commands/PIPE ********************************************************
*
* NAME
* PIPE - Connect input and output streams of shell commands
*
* FORMAT
* PIPE <command>
*
* TEMPLATE
* COMMAND/A/F
*
* PATH
* Internal
*
* FUNCTION
* The PIPE command function is used internally by the shell to ...
*
* NAME
* PIPE - Connect input and output streams of shell commands
*
* FORMAT
* PIPE <command>
*
* TEMPLATE
* COMMAND/A/F
*
* PATH
* Internal
*
* FUNCTION
* The PIPE command function is used internally by the shell to ...
- Wed Feb 26, 2025 5:19 am
- Forum: General Developer Support
- Topic: Crash when reading from a PIPE:
- Replies: 13
- Views: 78333
Re: Crash when reading from a PIPE:
I can't see any immediate reason why it can't be done.
All you need to remember is that if you can do it in a shell commandline,
(maybe with run), you can use the same basic commandline with SystemTags(),
that comes in handy when trying to debug something like this.
It's just the streams that you ...
All you need to remember is that if you can do it in a shell commandline,
(maybe with run), you can use the same basic commandline with SystemTags(),
that comes in handy when trying to debug something like this.
It's just the streams that you ...
- Sun Feb 16, 2025 2:17 am
- Forum: General Developer Support
- Topic: Crash when reading from a PIPE:
- Replies: 13
- Views: 78333
Re: Crash when reading from a PIPE:
I'm sorry, but I don't even know where to begin.
Firstly, it is never wise to mix DOS calls with CLIB calls, one doesn't know what the other
is doing with its streams and such.
Here's an initial problem I can see, the pipe streams are being opened with DOS calls,
they are being passed to a DOS ...
Firstly, it is never wise to mix DOS calls with CLIB calls, one doesn't know what the other
is doing with its streams and such.
Here's an initial problem I can see, the pipe streams are being opened with DOS calls,
they are being passed to a DOS ...
- Sat Feb 15, 2025 11:21 pm
- Forum: General Developer Support
- Topic: Bug or line flushing protocol changes from FEu0 to FEu2 [SOLVED]
- Replies: 5
- Views: 12698
Re: Bug or line flushing protocol changes from FEu0 to FEu2
Sorry, I have nothing to add via your PM.
The console-handler uses DOS Packets to communicate with DOS,
but you are not doing that in the example shown directly,
instead, the example is using getchar() and putchar() from clib.
Please remove all and any other extraneous layers between
you and the ...
The console-handler uses DOS Packets to communicate with DOS,
but you are not doing that in the example shown directly,
instead, the example is using getchar() and putchar() from clib.
Please remove all and any other extraneous layers between
you and the ...
- Sun Feb 09, 2025 11:20 pm
- Forum: General Developer Support
- Topic: Crash when reading from a PIPE:
- Replies: 13
- Views: 78333
Re: Crash when reading from a PIPE:
Where is the child process exit arbitration code ?
Who is handling the allocated resources ?
You can't just create a new distinct child process and have it go hurtling into
code that was loaded and unloaded by another process at any time without
some sort of exit or resource arbitration.
The ...
Who is handling the allocated resources ?
You can't just create a new distinct child process and have it go hurtling into
code that was loaded and unloaded by another process at any time without
some sort of exit or resource arbitration.
The ...
- Sun Feb 09, 2025 10:39 pm
- Forum: General AmigaOS
- Topic: AmigaDOS command Copy bug
- Replies: 2
- Views: 13511
Re: AmigaDOS command Copy bug
There is no "c:Copy" version of 54.?? yet.
The latest beta tester version is; Copy 53.13 (12/08/2020)
I know, because I added the entry in the releasenotes;
Copy 53.13 (12.08.2020) <cjw>
- The buffer=0 option now checks for the largest block of memory and limits
itself to half of that, or 2gig ...
The latest beta tester version is; Copy 53.13 (12/08/2020)
I know, because I added the entry in the releasenotes;
Copy 53.13 (12.08.2020) <cjw>
- The buffer=0 option now checks for the largest block of memory and limits
itself to half of that, or 2gig ...