• Priest of the Order of the Butterfly
    Priest of the Order of the Butterfly
    ausPPC
    Posts: 543 from 2007/8/6
    From: Pending...
    I'm starting to regret giving away my RKMs... Can anyone recommend a good discussion or primer on process initialisation as it applies to MorphOS? My goal is to create a new process that doesn't have to initialise itself any differently to a 'normal', user-started process.

    I'm particularly interested to know how to initialise the following tags marked with a '*'. Is it acceptable for the parent process to simply copy certain fields from its own process structure to pair with these tags?

    Code:
    NP_Seglist
    NP_FreeSeglist
    NP_Entry
    NP_Input *
    NP_Output *
    NP_CloseInput *
    NP_CloseOutput *
    NP_Error *
    NP_CloseError *
    NP_CurrentDir *
    NP_StackSize
    NP_Name
    NP_Priority
    NP_ConsoleTask * (How is this different to NP_Cli ?)
    NP_WindowPtr * (Just out of curiousity, can a parent and child process draw to the same window?)
    NP_HomeDir *
    NP_CopyVars * (How is this used?)
    NP_Cli *
    NP_Path *
    NP_CommandName
    NP_Arguments * (Is this just a string pointer?)

    NP_NotifyOnDeath
    NP_Synchronous
    NP_ExitCode
    NP_ExitData

    NP_SeglistArray
    NP_UserData
    NP_StartupMsg
    NP_TaskMsgPort * (Does the parent create this or is it handled by process creation?)
    NP_TaskFlags

    NP_CodeType
    NP_PPC_Arg1
    NP_PPC_Arg2
    NP_PPC_Arg3
    NP_PPC_Arg4
    NP_PPC_Arg5
    NP_PPC_Arg6
    NP_PPC_Arg7
    NP_PPC_Arg8
    NP_PPCStackSize
    PPC assembly ain't so bad... ;)
  • »07.03.16 - 23:00
    Profile Visit Website