Page 1 of 1

R553: exe runs (in task manager) but FC does not display

Posted: 28.09.2011, 20:38
by ScottR
I had this problem a while back, but it has occurred again.

I first deleted anything I could find from previous installs
extracted release 553 files from Zip file to directory D:\Tools\FreeCommanderXEprealfa
Created a new settings directory in FreeCommanderXEprealfa directory
Created a blank freecommander.ini file in settings directory.

Click to run .exe and nothing happens
The freecommander.exe is listed as a process in task manager, but the window is not displayed.

Tried again after copying over my previous .ini file - still no luck.

Anything else I can try?

Re: R553: exe runs (in task manager) but FC does not display

Posted: 28.09.2011, 23:06
by Marek
Try to create blank freecommander.ini in D:\Tools\FreeCommanderXEprealfa.

Re: R553: exe runs (in task manager) but FC does not display

Posted: 30.11.2011, 17:36
by ScottR
Unsuccessful

blank or old freecommander.ini in D:\Tools\FreeCommanderXEprealfa did not work.

Re: R553: exe runs (in task manager) but FC does not display

Posted: 04.12.2011, 07:40
by ralfso
Do you have 2 Monitors or a Beamer as first monitor?

Try to start with the parameter

/NewIni=fc.ini

to create a new fc.ini.

FCXE then starts with this new fc.ini instead of the freecommander.ini.

Re: R553: exe runs (in task manager) but FC does not display

Posted: 05.12.2011, 16:26
by ScottR
Ralf,

I am running 2 monitors (w/ ultramon), so tried everything again with a single monitor.

I tried the /Newini parameter and that did not work either.
Freecommander shows up in task manager, but does not open.
A freecommanderxe sub-directory is created in "....\local settings\application data"
,but no .ini is created.


thanks for your help. Scott.

Re: R553: exe runs (in task manager) but FC does not display

Posted: 05.12.2011, 19:08
by ralfso
Strange problem,

what's your windows version?

Can you search your system for all freecommander.ini files (include hidden files) and list their path?

Don't know, why <path>\freecommander.exe /NewIni=fc.ini is not creating a new fc.ini
but I think somewhere a damaged freecommander.ini is annoying you.