Recent content by c567591

I started with that Writeln atricle, thats how this process began. I haven't seen that other article, so I will give that a shot. I appreciate you sticking this out to help me.

Were you using a global (at least to those functions) variable?

Panels might work too.

No, that's still doing a new window. Any idea how to get the handle of the parent process?

Even if that does work (will try in a bit), it is still not in the original command window.

Did you try the download page? http://www.indyproject.org/Sockets/wizard/DownloadWizard.EN.aspx

I see it in a new window that flashes up and immediately closes. stdout/stderr both do same thing. Somehow I need the stdout/stderr of the parent process I guess.

I want to output the command line parameters & its help to the console that opened it. That way they can see the commands and correct them as needed. Normally, yes a TMemo is a great way, but for this, it is not what I am after. There are a lot of command line parameters and it is very helpful...

How do I output text to the same console that started the process? If I use: void writeln(String text) { // fprintf(stderr, "%s\n", text.c_str()); static HANDLE handle; if (!handle) { AllocConsole(); handle = GetStdHandle(STD_OUTPUT_HANDLE); } text += "\n"...

What a stupid concept! WTF was RH thinking?! [thumbsdown] Jeez, lets see how many places we can hide an IP. [thumbsdown] Thanks for the help all. I changed all occurances of 192.168.0.132 in /etc to the proper external IP. This fixed it.

What is the difference between the following locations: bad ip: /etc/sysconfig/networking/devices/ifcfg-eth0 /etc/sysconfig/networking/profiles/default/ifcfg-eth0 good ip: /etc/sysconfig/network-scripts/ifcfg-eth0 Other than the obvious. I can change them, but I need to understand the...

I am running RedHat v9 I setup a server to be a mail server and used an internal IP when I set it up in house. I have since moved it to our hosted environment and have tried to set the IP to the new public IP. This will take, but be forgotten on subsequent reboots. I have tried using RH's setup...

Yep that was it. The goofy broadcast address was messing things up. Thanks for pointing me in the right direction. :)

Here it is: net0: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.9.206.9 netmask ffffff00 broadcast 192.9.206.201 perf. params: recv size: 24576; send size: 24576; full-size frames: 1 ether 00:08:c7:9f:ad:6f...

It does from the windows workstations. Even still, why is the wrong machine responding or appearing to respond?