New InstallShield script format?

Originally Posted by WhoCares

for binary files, use feof() function, don't use EOF macro.

What the reason for such recommendation? According to MSDN

To indicate a read error or end-of-file condition, getc and getchar return EOF

I've used EOF for more that 10 years in multiple progs, and never encountered any problem.

@Dmit:
For me TYPE only truncates the output if it is directed to the console. As soon as it is redirected to any other file or any other program, it fully copies the filecontents. My BC++ compiled copy worked with the TYPE command just like the other way.

The VC++ and DMC copies truncated the file somewhere after 100kb or something (each one at the different position), so I guess (and tested) that there was at least one 0x1A before that file position.

@wasq:
For me it works with 0xF1 as XOR value. Using 0x0E gives me the wrong output.

[sackpower]

@ wasq: 0xF1 is the right XOR value.

I started a small project and decrypted a setup.inx with ISDHelper,
then I worked on it with SID (Sexy InstallShield Decompiler) and
rebuild the original crypted setup.inx. All worked fine.

Here is my solution for rebuilding the crypted INX:

//Usage: ISDGoBack.exe <newsetup.inx> setup.inx

#include <stdio.h>
#include <fcntl.h>
#include <io.h>
#define XOR_VAL 0xF1

void main (void) 
{
	int i, c;
	unsigned char b;
	// Set "stdin" and "stdout" to have binary mode
	setmode (_fileno (stdin), _O_BINARY);
	setmode (_fileno (stdout), _O_BINARY);
	// Rebuild the crypted INX
	for (i = 0; (c = getchar ()) != EOF; i++)
	{
            int d, e;

            d = 0x00;

            do
            {
                e = d;
	        e ^= XOR_VAL;
		b = (unsigned char)((e >> 2) | (e << 6)) - (i % 71);
                if (b == c)
                {
		    putchar (d);
                }
                else d++;
            } while (b != c && d <= 0xFF);
	}
}

I don't know if there is a better solution, but it works.

[WhoCares]

Originally Posted by Dmit

What the reason for such recommendation? According to MSDN

I've used EOF for more that 10 years in multiple progs, and never encountered any problem.

You are right. sorry