Search found 218 matches

by colinw
Fri Oct 31, 2025 12:32 pm
Forum: General AmigaOS
Topic: AmigaOS 4.1 Update 2 and 3 changed semantics of AssignLock DOS call
Replies: 5
Views: 2773

Re: AmigaOS 4.1 Update 2 and 3 changed semantics of AssignLock DOS call

Yes, absolutely.
Every new SDK release always has the latest includes and autodocs.
by colinw
Fri Oct 31, 2025 11:39 am
Forum: General AmigaOS
Topic: AmigaOS 4.1 Update 2 and 3 changed semantics of AssignLock DOS call
Replies: 5
Views: 2773

Re: AmigaOS 4.1 Update 2 and 3 changed semantics of AssignLock DOS call


document this in the Autodoc. Breaking fixes/changes should be documented in Autodoc.
add a corresponding error code to IoErr(). Because reason 0 is not helpful.
and maybe fix the translations for the assign error message. Because abbrechen != remove.


Now you make good points here;

1 ...
by colinw
Fri Oct 31, 2025 10:53 am
Forum: General Developer Support
Topic: WinFrame / ACTION_CHANGE_SIGNAL
Replies: 4
Views: 2746

Re: WinFrame / ACTION_CHANGE_SIGNAL

So what else would you expect with an unterminated taglist pointing to
random stack memory. ?

Seriously !!
by colinw
Fri Oct 31, 2025 10:43 am
Forum: General AmigaOS
Topic: AmigaOS 4.1 Update 2 and 3 changed semantics of AssignLock DOS call
Replies: 5
Views: 2773

Re: AmigaOS 4.1 Update 2 and 3 changed semantics of AssignLock DOS call

This was actually a long standing bug and was fixed back in 54.81 -- That's 7 years ago. !!

If I remember corectly, it was noticed by someone when using the "Assign" command
where it failed to return an appropriate return code for; "Assign foo: REMOVE"
Where the REMOVE option was added as a ...
by colinw
Sun Oct 19, 2025 9:58 am
Forum: General Developer Support
Topic: Asynchronous err = SystemTags() and error return
Replies: 3
Views: 2078

Re: Asynchronous err = SystemTags() and error return

Basically true, as it says;
; Asynchronous commands cause this function to return immediately,
; while Synchronous commands will wait until command execution finishes.

So, it's pretty difficult to return the result of the command if the spawning shell
process returns immediately before the ...
by colinw
Sat Oct 18, 2025 4:57 am
Forum: General Developer Support
Topic: Asynchronous err = SystemTags() and error return
Replies: 3
Views: 2078

Re: Asynchronous err = SystemTags() and error return

dos.library/System 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 error ...
by colinw
Mon Mar 17, 2025 12:03 am
Forum: General Developer Support
Topic: Crash when reading from a PIPE:
Replies: 13
Views: 90862

Re: Crash when reading from a PIPE:

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 ...
by colinw
Thu Mar 13, 2025 12:38 pm
Forum: General Developer Support
Topic: Crash when reading from a PIPE:
Replies: 13
Views: 90862

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 ...
by colinw
Sun Mar 02, 2025 10:52 pm
Forum: General Developer Support
Topic: ACTION_DISK_INFO and console
Replies: 1
Views: 17086

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.
by colinw
Wed Feb 26, 2025 5:21 am
Forum: General Developer Support
Topic: Crash when reading from a PIPE:
Replies: 13
Views: 90862

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 ...