What operating system / graphics system are you using? If it's Xinerama, I can help, but I'm getting the feeling it's running under some flavour of windows? (The precise flavour may be relvent - can you supply that?)

Watch out with Digimarc, and other 'invisible' watermarking software. They will not deter copyright infingers. They only make it easier to find and prosecute. To deter such behaviour, you need to have something that is obvious. And which would you prefer: To not have something taken at all, or to be in a stronger position for taking them to court? Digimarc is fantastic if the second is what you are looking for. I'm just not sure that that is what most independant artists are looking for.

Sign it. Bottom right (or left, but right is more conventional), sitck your name / logo there. Just like all the old canvas based artists used to do. That will force people to remove / edit out that part of the picture. Makes copyright infringment more difficult, and acts as a deterrent. Also it's good for artist identification, and will help build a 'brand' identity. Anything else is doomed to fail. There is no way to stop me from saving images of your website, if I want to do it. There can't be - to view the thing, I have to be able to get it - that's the way the web works.

Um, remember that DirectX works in kernelspace / hardware. It's not a seperate program, per se. Therefore, in order to snoop the data flow, you will have to work at the kernel level. If I need to point out the problems that entails, understand that this will be a long project. Also, I'm not convinced that the DirectX implementation uses a pipe - I think it's more stongly coupled than that, involving many calls. However, there is an alternative to kenerl snooping - run the program in an emulator, and modify the emulator to dump all the DirectX calls (and arguments) to a log. This is, I think the optimal solution, becuase there exists a DirectX capable emulator. Wine, which can be run on a unix environment such as Linux, is such an emulator. It won't be too much work to stick loggin gcode around each DirectX (Strictly, you only need the Direct3D calls, the other parts of DirectX are not relevent here). Other options are to run a debugger, or other stepwise execution environment on the program, and extract the models before they are executed. Either way, it's not straightforward. If you are just looking for models for a specific game engine, you may find that they are held in seperate files, and that might be the best way to approach the problem, leaving DirectX out of it.

Well.... I can think of lots of reasons. The most likely is that it's nothing to do with the disk space. When confused, Poser tends to run home, and blame the hard disk space. So if it says out of disk space, and you have some left (and I'm assuming you've made sure that some [at least, say, 10 Meg] is free), then treat it as an unknown error. The best bet is that some file it exepcts is missing, but, like thgeisel said above, you'll need to give more details on what you are doing before anyone can pin it down more than that.