A .prn file is just a raw dump of the commands sent to the printer; different printers use different command sets. GSview is an interpreter for PostScript files. If your DOS program has an option for printing to a PostScript printer (such as an Apple Laserwriter II), then use that option and GSview should be able to view it just fine (and convert it to a more useful format like PDF or PNG). - Mike

In VC, you can use the Tools:options and directories to configure the executable files (paths) that are searched for the compilers/linkers used in your makefile. Roger Allen Sonork 100.10016 I think I need a new quote, I am on the prowl, so look out for a soft cute furry looking animal, which is really a Hippo in disguise. Its probably me.

Ok, now I understood. And it helped. I'll go through the link later anyway, it seemed interesting. Thanks. -Janetta

I got it already.

Dont use TerminateThread or something like that... You must use a semaphore The semaphore is used to tell the thread that it must exit the thread must test the state of the semaphore in the ReadFile while and exit if the semaphore tells it to Casa.Sapo.pt

Steen Krogsgaard wrote: Do you do any CString::LockBuffer/CString::GetBuffer calls without matching CString::UnlockBuffer/CString::ReleaseBuffer? If I remember right, the things you mentioned should be ok. I can't get to the code right now, but I'll check when I can. Thanks! -Janetta

Problem solved. Thanks!:rose: -Janetta

But of course that was the problem:) Thanks! -Janetta

Thanks! I tried number two and it worked. -Janetta

Christian Graus wrote: I think I didn't make my deadline, but the article is up. Well, it's a good thing that we're not at school and I'm not your teacher:) I read the article and now I'll go through the code. The article seemed very useful, not only for this case, but also for the future. Thank you once again! -Janetta

Thanks a lot! It works now! It wasn't a big thing to do and now it seems obvious, but earlier it didn't. -Janetta

Janetta wrote: Could it be because of messing with C and C++? Yes it could. Try doing this: extern "C" { #include "header_written_in_C_used_from_c_plus_plus" } This will inform the C++ compilers to use C calling conventions, not C++ ones which are by default. Best regards, Alexandru Savescu

Create a project with the settings you want to use. Then select Export Makefile from the Project menu. Merge/plagerize the result with your makefile project.

It is very common, but there are many reasons why you get it. Maybe this mistake was trivial, but it was new to me. Thank you anyway:) -Janetta

You need to know who is the parend process (cmd.exe or explorer.exe), look for undocument function ntQueryInformationProcess in ntdll.dll :rose:

Thanks for both of you for your advice. I haven't found a solution yet, but I'll keep on fighting:) -Janetta