Comments on: Goodbye Visual C++

By: ititit

ititit — Sat, 27 Dec 2008 07:05:00 +0000

use gcc it could do anything if you
know how to use it all of linux is
compiled with gcc so i think that cff explorer could be compiled with
gcc

By: Ntoskrnl

Ntoskrnl — Mon, 22 Sep 2008 21:24:00 +0000

Well thanks torial, I guess sooner or later I’ll have to go back at VC++, since I already noticed that compiling python on windows with mingw is a mess. So, most certainly I’ll go back to that and will look into you just said. This post should be taken more as a rant than something serious, but it’s true that in the last months I managed to work with gcc only.

By: Torial

Torial — Mon, 22 Sep 2008 20:54:00 +0000

FWIW, if you use an older Edit Bin as part (e.g. not part of VS2008), and tie that to a post-build event, you can get it to work for NT. Can’t vouch for Windows 98.

By: Ntoskrnl

Ntoskrnl — Sat, 21 Jun 2008 21:56:00 +0000

snaury: well it's not totally ANSI, I guess, (the msvcr doesn't support it) and not only that, it doesn't work with fopen. If you look at the function it doesn't accept a FILE * argument. That's why I specified this factor in the post. I already saw that function. But thanks anyway.

edgar: it is a very short step to bring it to other system, even with GUI since the Qt framework works on every possible system (win, mac, linux, bsd etc). Not only that. I made the CFF endian aware. It could work on a power pc as well.

The ultimate goal would make the CFF run on many systems and adding support for many more formats other than PE.

By: Snaury

Snaury — Sat, 21 Jun 2008 21:40:00 +0000

Ouch, wrong man page. truncate and ftruncate are posix.

http://www.opengroup.org/onlinepubs/009695399/functions/ftruncate.html

By: edgar

edgar — Sat, 21 Jun 2008 21:37:00 +0000

Mmmh, if you go this way, maybe it
is also a short step to port it to different systems ?
A UI version and a none UI version ?

Sometimes (but maybe not for much peoples) it is important to have a tool which works in and also for different systems.

By: Snaury

Snaury — Sat, 21 Jun 2008 21:34:00 +0000

Actually, it seems there are functions ftruncate() and truncate(), at least they are present in both glibc and cygwin's newlib. Also, man ftruncate reveals some history:

The truncate() and ftruncate() function calls appeared in 4.2BSD.

It's just Microsoft not really supporting what all the other world uses. Be it fork() or a totally borked argument concatenation in exec*() and spawn*(). :-/ So I'm not surprised something so vital is missing, and mingw supports only those things that are exported from msvcrt.dll.

By: Ntoskrnl

Ntoskrnl — Sat, 21 Jun 2008 18:08:00 +0000

I have been running Vista x64 for quite some time. If you look, I wrote one of the first articles about Vista & x64. I'm not interested in Windows 98, much more in NT4. And EVEN IF, I expect Microsoft:

a) to give a full explanation for not supporting NT4
b) provide an alternate compiling with an older C runtime

From your comment I clearly understand that you didn't even bother reading the post, so why commenting at all?

Moreover, the CFF Explorer is an internals tool. I wouldn't recommend to use an old operating system, but the application itself should be able to run with a minimum of requisites (especially if it is possible).

By: cdman83

cdman83 — Sat, 21 Jun 2008 16:18:00 +0000

So why exactly should Microsoft support an antique operating platform? The Win 9x series is end of life for some time, using it makes no sense and you are exposing yourself and others to danger if you connect such a machine to the Intertubes (by adding one more zombie machine).

Microsoft made the right decision here and if you are still running Win 9x, you should really, really look for alternatives.