Hyperion Entertainment Message Boards

blmara wrote: ...
But here I don't understand the CONST_ part,

There is a detailed explanation of this halfway down in the include file; exec/types.h

Yes, you must pass only an open filehandle to GetFileSize(). The IoErr() code [ERROR_OBJECT_WRONG_TYPE] should have indicated this. What you need in your situation is something like the following pseudocode; ==================================================== BPTR BHandle = IDOS->Lock(passedfilenam...

@colinw Ok. I allready use the SafeSignal() to send the ctrl-c to my process. I get the PID from IDOS->IoErr() as documented in the CreateNewProcTags() description. There is no IDOS->GetPID in the current SDK, [...] I will just do as colinw suggested. do { done = safeSignalNotifyProcess(libBase); I...

gazelle wrote: (...)
There is no IDOS->GetPID in the current SDK,

Ok, that's not good, i'll try and remedy that with management ASAP.

These features basically require that you know what task is going to persist to receive the deathmessage or deathsignal. Unfortunately, from a library context, that's the one thing you can't know in advance. So these are not going to help you a lot here, sorry. So, may I suggest that you just put th...

I have no control over the calling process. I'll try another approach. Solution: I'm now creating my own "notify process" which installes the hook and stays alive as long as the library is not expunged. Simpler solution: Do it in libInit(). Then the calling process is "ramlib" a...

For this function, the hook is always called from a different context. If the notification is added to the internal list, and the name matches, the hook will be called from the process that is modifying the variable. Be aware that if the process that initiated the notification ends, and it still has...

I have just tested the variable notification function and it is working correctly.

Please test it by typing the following in a shell; setenv testvar xxx

Also, please tell me what dos library version you are using.

By the way, I only just noticed... FreeDeviceproc() must be called for each GetDeviceProc(), INSIDE the volume list loop. As it is shown above, it's returning the deviceproc for each volume and just orphaning the devproc memory, except for the last one when it falls out of the loop and calls FreeDev...

While the wiki is currently being updated and contains mostly older documentation and methods. ALWAYS refer to the latest dos.doc autodocs for the latest release info, it will be merged into the wiki as time permits. For example; Please revisit the dos autodocs and DO note that notifications should ...