Can't add files

[rado]

Hi,

I just bought the Beyond Compare Pro version. I'm having a strange problem -I can add files via drag and drop, but not via the file dialogs or typing in the filenames. I can open the file dialogs and select files, but they never show up in the panes. It's not possible to type anything in the filename fields either.

Am I doing something wrong or is there a problem here?

Also, the program crashes when I have a file loaded in the left pane in Hex compare and select Close Tab from the file menu. I can reproduce this (sent an error report about it also via the program).

thanks,
rado

[Michael Bulgrien]

Those are, indeed, strange symptoms. What platform are you running BC3 on? Windows or Linux? If Windows, are there any errors in the application event log? Do you have administrative rights on the system? Have you tried uninstalling BC3 and re-installing it? If so, also try a portable install. Does it have the same issues?

[rado]

It's Windows XP Pro SP3. Admin rights.

I found one error message in Event viewer. I've just reproduced the crash error a few times but no new error messages show up. Maybe it's a different error that is shown in event log, don't recall exactly all that happened yesterday.

Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 2008-09-19
Time: 21:02:07
User: N/A
Computer: ALPHA
Description:
Hanging application BCompare.exe, version 3.0.4.8855, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Pretty useless anyway, I guess...

But by accident I actually found out what causes the file dialog problems - it's a program called File-Ex, a file dialog add-on:

http://www.cottonwoodsw.com/

As soon as I close this program, the file dialogs in BC works allright. So there must be a conflict here. I'm not aware of any other conflicts caused by this program though despite having used if for years and having tons of other programs and several other explorer extensions installed.

As for the problem with typing the filename, there is no problem actually. I can type in filenames, also when File-Ex is running, I was just confused by the sort of (compared to most other input fields) abnormal behaviour of the input field. Sorry.

But the crash problem is not related to File-Ex, as it also happens when it's shut down. BC simply shuts down without further notice as soon as I select Close Tab or press ctrl+W.

rado

[Zoë]

Hi Rado,

The next release (3.0.8) will have the incompatibility with File-Ex fixed. In the meantime, if you hold shift while clicking the browse button, File-Ex will allow you to disable it for BC.

I wasn't able to find the crash you sent in or reproduce it here. Can you email support to let us know what email address you used to submit it?

[rado]

Sorry for the delay....

Hi Rado,

The next release (3.0.8) will have the incompatibility with File-Ex fixed. In the meantime, if you hold shift while clicking the browse button, File-Ex will allow you to disable it for BC.

OK, that works yes, thanks!

I wasn't able to find the crash you sent in or reproduce it here. Can you email support to let us know what email address you used to submit it?

Well if you haven't received it may not have been sent. I recall there was a second crash during the sending process, so that may have crashed itself before the report was sent, might be that which was reported in Event Viewer. The program has not tried to send any reports since then when it crashes on Close Tab, it simply shuts down without further notice, so it may have been something else that caused the attempt to send the report anyway.

I have a completely identical machine also with XP Pro SP3 but with different software installed except for a few programs, just tried to test it there but it also crashes on that machine on Close Tab, with no attempt to send error report. Both has an Intel DG965WH board, Q6600 CPU, 2 GB RAM (tested recently), Adaptec 1225SA eSATA controller, Promise Ultra133 TX2 controller, same monitor/driver. Mouse and keyboard the same, uses XP standard PS2 controller. So it might a conflict with a mainboard or some other driver, or one of the shared programs. All drivers have been updated not long ago btw.

rado