Compiler generate no hex file

[jmswu1243]

Hi

I am trying to compile some old code. I don't see to generate any hex file. I can see it generated a 0 byte .$$$ file and 2 bytes .err file. But now .HEX file.

Any suggestion?

I am running win11 if that's matter.

Here is my command:

[Ttelmah]

The options should be before the filename.

ccsc +FM +DF +O8 +T -A +M +Z +Y=9 +EA .\file.c

It is currently not compiling anything.

[jmswu1243]

[Ttelmah]

Are you serious!.....
That is so old, I haven't even got it to test. The oldest compiler I have is
20 years old. However looking at the help, the optimisation command
should be +Y9 no equals. You are looking at possibly about a 2002-2003
compiler.
Failing that, I think you should try a clean re-install. I know that historically
sometimes the compiler could get a hiccup where it would not compile,
and this was the fix. Obviously also how are you calling this?. What is the
path statement for the command line you are using?. The compiler might
fail if is cannot find an include file, because the path is wrong, but I
would have expected an error message.

[temtronic]

Here's one I found that might be of that 'era'.

Executing: "C:\Program Files\PICC\Ccsc.exe" "DTCV2.C" +FM +DF +LN +T -A
+M +Z +Y=9 +EA

I know it compiles !
Ill have the OPs compiler version 'somewhere'....as I go back to 2.5xx....
..just have to locate it...wasn't too 'organized' back then though. When I upgraded harddrives, I'd copy the old one as a subfolder..

[Ttelmah]

I have a note here, that it doesn't like the .\file format at this time.
I think '\', if not inside inverted commas, is treated as an escape.
So you either have to have inverted commas, or not use a \ in the filename.

I like you go back to V 2.x compilers, but I tidied up all the stuff older
than about 20 years a while ago. Do have them on an optical disk
somewhere, but not on my current system.

One other caveat, is to check if there is a CCSC.INI file in the directory
with the compiler. If this is present, it is read before the commands on
the command line. Could be screwing things up......