In response to questions I received by E-mail I compiled a Frequently Asked Questions-list:

Can you keep me informed about PCOM beta releases?

Yes, look at this site twice a month and you're informed!

Will there be a Windows version of PCOM?

No, the overhead of Windows executable is so huge that we keep the PCOM executable only available for DOS. Thereby PCOM executables will run within Windows v3.X, Windows 95/98, Windows NT v3.51, Windows NT v4.0, OS/2 v2.X, Warp v3.0, Macintosh and Linux with DOS emulation (any others we left out?).

Why is PCOM still freeware?

When I build in any method of registration into PCOM, the first sample source you send me is a PCOM-crack ;-). But when you like the compiler, just send me an e-mail.

Can you build in a file back-up routine?

No, but why should I, you can use the following command: $run:copy file.exe file.bak > nul.

Does PCOM support long filenames?

Yes, finally it does! All you have to do is to use the -l option, which enables the long filename support. Doing this, the filesize of the created executable will increase.

Is there a possibility to create generic patches?

Yes, you can use the $far:xx>yy command of PCOM. The xx and yy must be hex notated. To change strings, translate them using the PCOM /t option. To find a single occurence use the $fnd:... command. By using the >xxxx:xxxx command you can skip parts of the inputfile and with the <xxxx:xxxx command you can move the filepointer position backwards.

I would like to protect my executales, do I need third party tools?

No, it is possible to protect your code in two ways. Using the -e option, this will encrypt your complete source. Or use the -i option which includes anti-hacker code into the output executable. You can use both to get the highest degree of protection.

I always use -e -i, is it possible to predefine the compiler settings?

Yes, you can use the PCOM.CFG file. This file can be in two locations, first the directory PCOM is located (somewhere in your path) or in the current directory. If both exist the one in the current directory will be used. When you use the -a option in your PCOM.CFG you can unselect this option by using -a- as argument. So PCOM RUNME -a- will deselect the -a used in the PCOM.CFG file. To check the current configuration you can use the /g option. This option will show the configuration of the found settings. The /g will act as a file, so you can use PCOM /g -i- -x and PCOM will responed with the created settings. Replace the /g with the filename and the source will be compiled in the way you ment. The file is a normal plain text file where you can use the ';' command for comments. The option may be in one or more lines. Example PCOM.CFG file:

;
; My configuration
;
-i -e
-x
;
; End of my configuration
;


Why does PCOM uses the .SCR extension?

Once I started building PCOM I had to use a extension. In those days I decided to call a PCOM source a script, which is actually incorrect. After compiling a PCOM source there is a standalone executable and the source (.SCR) may be deleted. BUT when you download a newer version of PCOM, ie. version 2.7 or higher, you must use the .SRC extension.

Why is the $FAR:...>... routine so slow?

Well, when I started the routine I used a buffer of 1024 bytes and the routine was fast. But using a buffer would increase the routine by 1k, so I removed the buffer.

My text doen't blink when I add 0x80?

In the early days there where 16 foregroundcolors and 7 backgroundcolors. When you added 0x80 (need I say 0x8 at the background part) the text would blink. Nowadays we have Microsoft Windows and the behavior of the blink is changed. There are 16 foreground and 16 backgroundcolors. From PCOM version 2.7 beta 9 and higher the /o option is changed, try it. . .