#TDI's CreateProc()
4 messages in this thread
Steve – Did you ever run into a problem with TDI's CreateProc()? No matter what
I do it returns a NULL address (actually a NULL BPTR – in spite of what the
def. listing says). DeviceProc(), on the other hand, returns an address no
matter what I feed it. Dissassembly of the lnk. file indicates all is being
called properly, taht is, if the lib offset is correct. They don't shift the
return value to give an ADDRESS but that's the only problem I could see. Any
help would be appreciated. I have access to BM so I might give the code a shot
with that compiler and see if it's my code but based on the C source I'm
translating it'd be pretty hard to screw it up.
Erv, DeviceProc() should return an address for everything except a non-existent
device (like "foo:"), after you click CANCEL in the "Please insert volume foo"
requester; and for "nil:". Given a directory or file name, existent or not, you
will get the address of the file-handler for the device where the current
directory is located; given a device name, you'll get the address of the
handler for that device.
Nick
Sorry, but I never got a chance to play around with CreateProc or DeviceProc.
– Steve –
I found the problem, at least with CreateProc(). Had a bad lib offset. Got
everything working just fine, much to my surprise. Actually encountering such
problems tends to be very beneficial for me. I dig through so much
documentation trying to come up with a cure I come across lots of things I
hadn't discoverd before. Sure is frustrating in the interim though.