Search found 9 matches
- 14.12.2019, 02:02
- Forum: Discussion
- Topic: WinXP_64/Server2003_64 + crash of 790a-32
- Replies: 16
- Views: 23070
Re: WinXP_64/Server2003_64 + crash of 790a-32
Cheers for that. We respect your decision, though it might have been better to know at the outset when we asked the question. If you change your mind, and wish to consider having us go at compiling a compatible version, please feel free to let us know (we understand sensitivities relating to distrib...
- 12.12.2019, 20:05
- Forum: Discussion
- Topic: WinXP_64/Server2003_64 + crash of 790a-32
- Replies: 16
- Views: 23070
Re: WinXP_64/Server2003_64 + crash of 790a-32
Hi
Just wondering how things are going on the matter.
Please advise
DrO
Just wondering how things are going on the matter.
Please advise
DrO
- 04.12.2019, 21:45
- Forum: Discussion
- Topic: WinXP_64/Server2003_64 + crash of 790a-32
- Replies: 16
- Views: 23070
Re: WinXP_64/Server2003_64 + crash of 790a-32
Cheers for that. ... alas, no joy, FCXE.exe is still looking for the GetTickCount64 entry, and fails. Running Agent Ransack shows GetTickCount64 showing up in both FreeCommanderXE.exe and ielib64.dll (though GetTickCount, without the "64", is also there). We expect you have considerable ex...
- 02.12.2019, 21:44
- Forum: Discussion
- Topic: WinXP_64/Server2003_64 + crash of 790a-32
- Replies: 16
- Views: 23070
Re: WinXP_64/Server2003_64 + crash of 790a-32
Cheers for that Though we are not sure if what you mean by making changes to the next release. Does that mean a WinXP-64/Server03_64 compatible version? Please advise. We had tried the 32 bit version, but only to confirm that 806 works at that level (as per earlier exchanges). Those tests show resul...
- 02.12.2019, 17:01
- Forum: Discussion
- Topic: WinXP_64/Server2003_64 + crash of 790a-32
- Replies: 16
- Views: 23070
Re: WinXP_64/Server2003_64 + crash of 790a-32
Well, made some progress. There were multiple emails rec'd following "donation", in part due to FastSprings "complications", in part to FC's emails. The immediate email provided a direct dload link to the donor version (which was 790a, already known to fail in 32, but failed also...
- 01.12.2019, 23:28
- Forum: Discussion
- Topic: WinXP_64/Server2003_64 + crash of 790a-32
- Replies: 16
- Views: 23070
Re: WinXP_64/Server2003_64 + crash of 790a-32
UGH. OK, so went for 1-year w/update. But that provides 790a 64, which, what a surprise, fails to work at all. It won't launch, and it doesn't even appear in TaskManager (at least with 790a 32 there was basic Interface (not much worked) and a TaskManager entry. I thought I would be able to get at le...
- 01.12.2019, 22:48
- Forum: Discussion
- Topic: WinXP_64/Server2003_64 + crash of 790a-32
- Replies: 16
- Views: 23070
Re: WinXP_64/Server2003_64 + crash of 790a-32
Again, many thanks.
Though when I click donate, it states that the download (and I copy/paste from their page) is: FreeCommander XE 2019 Build 790 64-bit $8.25 CAD
... that looks like v790, which is crashed. Where would the 804/806 etc 64 bit be found?
Though when I click donate, it states that the download (and I copy/paste from their page) is: FreeCommander XE 2019 Build 790 64-bit $8.25 CAD
... that looks like v790, which is crashed. Where would the 804/806 etc 64 bit be found?
- 01.12.2019, 22:23
- Forum: Discussion
- Topic: WinXP_64/Server2003_64 + crash of 790a-32
- Replies: 16
- Views: 23070
Re: WinXP_64/Server2003_64 + crash of 790a-32
Cheers for that 804 beta works on WinXP64 (at least following only a cursory test).
Still, is that either a necessary or sufficient condition that "donor 64bit" will work?
Still, is that either a necessary or sufficient condition that "donor 64bit" will work?
- 01.12.2019, 22:06
- Forum: Discussion
- Topic: WinXP_64/Server2003_64 + crash of 790a-32
- Replies: 16
- Views: 23070
WinXP_64/Server2003_64 + crash of 790a-32
Does the 64-bit donor version work with WinXP_64/Server2003_64? I am happy to make a donation, but the public 790a 32-bit version crashes on launch (it launches with an error message and fails to work, and must be exited by deleting in TaskManager). Here is its error report/log date/time : 2019-12-0...