WinXP_64/Server2003_64 + crash of 790a-32

Discussion and questions - donor version.
Message
Author
DrOli
Posts: 9
Joined: 01.12.2019, 20:52

WinXP_64/Server2003_64 + crash of 790a-32

#1 Post by DrOli » 01.12.2019, 21:06

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-01, 11:49:33, 843ms
computer name :
user name :
registered owner :
operating system : Windows XP x64 Service Pack 2 build 3790
system language : English
system up time : 1 hour 36 minutes
program up time : 493 milliseconds
processors : 4x Dual-Core AMD Opteron(tm) Processor 2216 HE
physical memory : 14096/16383 MB (free/total)
free disk space : (C:) 3.84 GB (D:) 5.03 GB
display mode : 1440x900, 32 bit
process id : $39c
allocated memory : 18.11 MB
largest free block : 941.62 MB
executable : FreeCommander.exe
exec. date/time : 2019-01-05 17:29
version : 2019.0.0.790
compiled with : Delphi 10.2 Tokyo
madExcept version : 4.0.20
callstack crc : $6753cc31, $bc3f52fc, $bc3f52fc
exception number : 1
exception class : EExternalException
exception message : External exception C06D007F.

main thread ($948):
7d4e21b6 +04e kernel32.dll RaiseException
00413829 +2a5 FreeCommander.exe SysInit @_delayLoadHelper2
00474b69 +005 FreeCommander.exe Winapi.ShlObj shell32.dll
00cb98ef +02f FreeCommander.exe funShellLibrary 109 +4 SHIsShellLibrary
00fe2d17 +117 FreeCommander.exe fcFileSystemLocator 309 +27 TfcFileSystemLocator.SetIdList
0097bc60 +034 FreeCommander.exe fcFilePidDataSupplier 476 +4 TfcFilePidDataSupplier.PopulateFiles
00c99750 +0f4 FreeCommander.exe fcVirtualDriveList 737 +21 TfcVirtualDriveList.BuildDriveList
00c98fe0 +000 FreeCommander.exe fcVirtualDriveList 557 +0 TfcVirtualDriveList.RefreshDriveList
0104904a +2a2 FreeCommander.exe FcMain 1569 +64 TFcFormMain.DoFormCreate
01048b92 +202 FreeCommander.exe FcMain 1433 +76 TFcFormMain.FormCreate
006c9f95 +031 FreeCommander.exe Vcl.Forms TCustomForm.DoCreate
006c9bb1 +011 FreeCommander.exe Vcl.Forms TCustomForm.AfterConstruction
0040a359 +01d FreeCommander.exe System 29 +0 @AfterConstruction
006c9b63 +19b FreeCommander.exe Vcl.Forms TCustomForm.Create
006d5016 +076 FreeCommander.exe Vcl.Forms TApplication.CreateForm
0107610c +2f4 FreeCommander.exe FreeCommander 511 +122 initialization

thread $a04:
7d4d8c98 +82 kernel32.dll WaitForSingleObjectEx
7d4d8c08 +0d kernel32.dll WaitForSingleObject

modules:
00400000 FreeCommander.exe 2019.0.0.790 D:\Utilities\FreeCommander XE
038d0000 NTMARTA.DLL 5.2.3790.3959 C:\WINDOWS\system32
051c0000 Normaliz.dll 6.0.5441.0 C:\WINDOWS\syswow64
403f0000 wininet.dll 8.0.6001.23942 C:\WINDOWS\syswow64
40a90000 iertutil.dll 8.0.6001.23942 C:\WINDOWS\syswow64
4b3c0000 MSCTF.dll 5.2.3790.5528 C:\WINDOWS\SysWOW64
4dc30000 msctfime.ime 5.2.3790.3959 C:\WINDOWS\system32
53000000 windowscodecs.dll 6.0.5840.16388 C:\WINDOWS\system32
5e9a0000 olepro32.dll 5.2.3790.3959 C:\WINDOWS\system32
6bc00000 DrvTrNTm.dll 8.6.0.0 C:\WINDOWS\system32
6bc20000 DrvTrNTl.dll 8.6.0.0 C:\WINDOWS\system32
6f350000 urlmon.dll 8.0.6001.23942 C:\WINDOWS\syswow64
71bb0000 wsock32.dll 5.2.3790.0 C:\WINDOWS\system32
71bd0000 mpr.dll 5.2.3790.3959 C:\WINDOWS\syswow64
71bf0000 WS2HELP.dll 5.2.3790.1830 C:\WINDOWS\system32
71c00000 WS2_32.dll 5.2.3790.3959 C:\WINDOWS\system32
71c40000 netapi32.dll 5.2.3790.5030 C:\WINDOWS\system32
73070000 winspool.drv 5.2.3790.3959 C:\WINDOWS\system32
73ac0000 avifil32.dll 5.2.3790.4625 C:\WINDOWS\system32
75e60000 apphelp.dll 5.2.3790.3959 C:\WINDOWS\system32
75fc0000 MSVFW32.dll 5.2.3790.1830 C:\WINDOWS\system32
762b0000 comdlg32.dll 6.0.3790.3959 C:\WINDOWS\syswow64
76520000 CSCDLL.dll 5.2.3790.3959 C:\WINDOWS\System32
76920000 Userenv.dll 5.2.3790.5491 C:\WINDOWS\system32
76aa0000 winmm.dll 5.2.3790.4916 C:\WINDOWS\system32
76f00000 wtsapi32.dll 5.2.3790.3959 C:\WINDOWS\system32
76f10000 WLDAP32.dll 5.2.3790.3959 C:\WINDOWS\syswow64
77010000 COMRes.dll 2001.12.4720.3959 C:\WINDOWS\system32
770e0000 SETUPAPI.dll 5.2.3790.3959 C:\WINDOWS\system32
771f0000 WINSTA.dll 5.2.3790.3959 C:\WINDOWS\system32
77670000 ole32.dll 5.2.3790.5663 C:\WINDOWS\syswow64
777b0000 CLBCatQ.DLL 2001.12.4720.3959 C:\WINDOWS\system32
77b00000 cscui.dll 5.2.3790.3959 C:\WINDOWS\System32
77b70000 MSACM32.dll 5.2.3790.3959 C:\WINDOWS\system32
77b90000 version.dll 5.2.3790.1830 C:\WINDOWS\syswow64
77ba0000 msvcrt.dll 7.0.3790.3959 C:\WINDOWS\syswow64
7c8d0000 shell32.dll 6.0.3790.5558 C:\WINDOWS\syswow64
7d0e0000 oleaut32.dll 5.2.3790.5488 C:\WINDOWS\syswow64
7d180000 SHLWAPI.dll 6.0.3790.5318 C:\WINDOWS\syswow64
7d1e0000 ADVAPI32.dll 5.2.3790.5669 C:\WINDOWS\syswow64
7d4c0000 kernel32.dll 5.2.3790.5295 C:\WINDOWS\syswow64
7d600000 ntdll.dll 5.2.3790.5583 C:\WINDOWS\system32
7d800000 GDI32.dll 5.2.3790.6022 C:\WINDOWS\syswow64
7d8d0000 Secur32.dll 5.2.3790.4530 C:\WINDOWS\syswow64
7d930000 USER32.dll 5.2.3790.4033 C:\WINDOWS\syswow64
7da20000 RPCRT4.dll 5.2.3790.5669 C:\WINDOWS\syswow64
7dbd0000 comctl32.dll 6.0.3790.5190 C:\WINDOWS\WinSxS\WOW64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.5190_x-ww_B8C2A5B7
7dee0000 IMM32.DLL 5.2.3790.3959 C:\WINDOWS\system32
7df50000 uxtheme.dll 6.0.3790.3959 C:\WINDOWS\system32
7e020000 SAMLIB.dll 5.2.3790.3959 C:\WINDOWS\system32

processes:
000 Idle 0 0
004 System 0 0 normal
10c smss.exe 0 0 normal
140 csrss.exe 0 0
158 winlogon.exe 47 14 high
188 services.exe 4 2 normal
194 lsass.exe 6 2 normal
23c svchost.exe 4 0 normal
2c4 svchost.exe 0 0
2f0 svchost.exe 11 22 normal
320 svchost.exe 4 0 normal
368 svchost.exe 0 0
3b4 svchost.exe 0 0
3f4 spoolsv.exe 4 5 normal
42c CTAudSvc.exe 4 3 high C:\Program Files (x86)\Creative\Shared Files
47c svchost.exe 0 0
4b4 CALoadService.exe 4 1 normal
508 CSHelper64.exe 4 1 normal
518 svchost.exe 4 1 normal
57c mdm.exe 4 3 normal C:\Program Files (x86)\Common Files\Microsoft Shared\VS7Debug
5bc nvsvc64.exe 4 5 normal
5f4 sqlbrowser.exe 0 0
634 sqlwriter.exe 4 2 normal
694 svchost.exe 0 0
6a0 NTService.exe 4 2 normal C:\Program Files (x86)\SUPERMICRO\SDIII
250 wmiprvse.exe 0 0
374 alg.exe 0 0
900 explorer.exe 256 126 normal
990 usb3Monitor.exe 15 11 normal C:\Program Files\VIA XHCI UASP Utility
9a0 RoboTaskBarIcon.exe 103 55 normal C:\Program Files (x86)\Siber Systems\AI RoboForm
9b0 WizMouse.exe 17 10 realtime D:\Utilities\WizMouse
9b8 ctfmon.exe 17 11 normal
8b0 ctfmon.exe 10 8 normal C:\WINDOWS\SysWOW64
4d4 Rundll32.exe 13 8 normal C:\WINDOWS\system32
220 taskmgr.exe 113 99 high
be0 Clock.exe 22 12 normal
aa0 MagicDisc.exe 52 30 normal C:\Program Files (x86)\MagicDisc
afc msoffice.exe 179 48 normal D:\Apps\MSO\Office10
a34 SuperoDoctor.exe 478 275 normal C:\Program Files (x86)\SUPERMICRO\SDIII
a90 OUTLOOK.EXE 367 228 normal D:\Apps\MSO\Office10
984 siMain.exe 33 21 normal D:\Apps\OutLook AddIns\Spam Inspector
128 siSpamFilterEngine.exe 26 19 normal D:\Apps\OutLook AddIns\Spam Inspector
18c firefox.exe 318 109 normal C:\Program Files (x86)\Mozilla Firefox
39c FreeCommander.exe 156 80 normal D:\Utilities\FreeCommander XE

hardware:
+ Computer
- ACPI Multiprocessor x64-based PC
+ Disk drives
- FUJITSU MAS3735NP SCSI Disk Device
- MAXTOR ATLAS10K4_73WLS SCSI Disk Device
- MAXTOR ATLAS15K2_146WLS SCSI Disk Device
- SEAGATE ST373307LW SCSI Disk Device
- SEAGATE ST373455LW SCSI Disk Device
- ST3250410AS
- WDC WD1003FZEX-00K3CA0
- WDC WD1003FZEX-00MK2A0
- WDC WD2003FZEX-00SRLA0
+ Display adapters
- ATI ES1000 (driver 8.24.3.0)
- NVIDIA Quadro NVS 290 (driver 6.14.11.7813)
+ DVD/CD-ROM drives
- HL-DT-ST DVDRAM GSA-H62L
+ Floppy disk controllers
- Standard floppy disk controller
+ Floppy disk drives
- Floppy disk drive
+ IDE ATA/ATAPI controllers
- NVIDIA nForce 590/570/550 Serial ATA Controller (driver 5.10.2600.687)
- NVIDIA nForce 590/570/550 Serial ATA Controller (driver 5.10.2600.687)
- NVIDIA nForce 590/570/550 Serial ATA Controller (driver 5.10.2600.687)
- Primary IDE Channel
- Secondary IDE Channel
- Standard Dual Channel PCI IDE Controller
+ IEEE 1394 Bus host controllers
- OHCI Compliant IEEE 1394 Host Controller
+ Keyboards
- Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
+ Mice and other pointing devices
- Microsoft PS/2 Mouse
+ Monitors
- Default Monitor
- Default Monitor
- Default Monitor
- SyncMaster T220HD/T220MD(Analog) (driver 3.0.0.0)
+ Network adapters
- 1394 Net Adapter
- Direct Parallel
- NVIDIA nForce Networking Controller (driver 65.3.1.0)
- NVIDIA nForce Networking Controller #2 (driver 65.3.1.0)
- NVIDIA nForce Networking Controller #2 - Packet Scheduler Miniport
- NVIDIA nForce Networking Controller - Packet Scheduler Miniport
- SAMSUNG Mobile USB Remote NDIS Network Device - Packet Scheduler Miniport
- WAN Miniport (IP)
- WAN Miniport (IP) - Packet Scheduler Miniport
- WAN Miniport (L2TP)
- WAN Miniport (PPPOE)
- WAN Miniport (PPTP)
+ NVIDIA Network Bus Enumerator
- NVIDIA Network Bus Enumerator (driver 65.3.1.0)
- NVIDIA Network Bus Enumerator (driver 65.3.1.0)
+ Ports (COM & LPT)
- Communications Port (COM1)
- Communications Port (COM2)
+ Processors
- Dual-Core AMD Opteron(tm) Processor 2216 HE (driver 1.3.2.0)
- Dual-Core AMD Opteron(tm) Processor 2216 HE (driver 1.3.2.0)
- Dual-Core AMD Opteron(tm) Processor 2216 HE (driver 1.3.2.0)
- Dual-Core AMD Opteron(tm) Processor 2216 HE (driver 1.3.2.0)
+ SCSI and RAID controllers
- Adaptec AIC-7902B - Ultra320 SCSI (driver 3.0.0.0)
- Adaptec Embedded SCSI HostRAID Controller (driver 2.0.0.201)
- Adaptec HostRAID Management Processor Device for U320 (driver 2.0.0.201)
- MagicISO SCSI Host Controller (driver 2.7.106.0)
+ Sound, video and game controllers
- Audio Codecs
- Creative Game Port (driver 8-25-2006)
- Creative SB Audigy 2 ZS (WDM) (driver 6.0.1.1377)
- Legacy Audio Drivers
- Legacy Video Capture Devices
- Media Control Devices
- Total Recorder WDM audio driver (driver 8.6.0.0)
- Video Codecs
+ System devices
- ACPI Fixed Feature Button
- ACPI Power Button
- AMD Address Map Configuration
- AMD Address Map Configuration
- AMD DRAM and HyperTransport(tm) Trace Mode Configuration
- AMD DRAM and HyperTransport(tm) Trace Mode Configuration
- AMD HyperTransport(tm) Configuration
- AMD HyperTransport(tm) Configuration
- AMD Miscellaneous Configuration
- AMD Miscellaneous Configuration
- Direct memory access controller
- Logical Disk Manager
- Microcode Update Device
- Microsoft ACPI-Compliant System
- Microsoft System Management BIOS Driver
- Motherboard resources
- Motherboard resources
- Motherboard resources
- Motherboard resources
- Numeric data processor
- NVIDIA nForce System Management (driver 4.5.7.0)
- PCI bus
- PCI standard ISA bridge
- PCI standard PCI-to-PCI bridge
- PCI standard PCI-to-PCI bridge
- PCI standard PCI-to-PCI bridge
- PCI standard PCI-to-PCI bridge
- PCI standard PCI-to-PCI bridge
- PCI standard PCI-to-PCI bridge
- PCI standard PCI-to-PCI bridge
- PCI standard RAM Controller
- Plug and Play Software Device Enumerator
- Programmable interrupt controller
- System board
- System CMOS/real time clock
- System speaker
- System timer
- Terminal Server Device Redirector
- Terminal Server Keyboard Driver
- Terminal Server Mouse Driver
- Volume Manager
+ Universal Serial Bus controllers
- Standard Enhanced PCI to USB Host Controller
- Standard OpenHCD USB Host Controller
- USB Root Hub
- USB Root Hub
- VIA USB 2 Hub (driver 6.1.7600.4402)
- VIA USB 3 Root Hub (driver 6.1.7600.4402)
- VIA USB eXtensible Host Controller (driver 6.1.7600.4402)

cpu registers:
eax = 017afc94
ebx = 7c8d0000
ecx = 00000000
edx = 017afd08
esi = 017afd50
edi = 00000000
eip = 7d4e21b6
esp = 017afc90
ebp = 017afce4

stack dump:
017afc90 20 81 1b 01 7f 00 6d c0 - 02 00 00 00 00 00 00 00 .....m.........
017afca0 b6 21 4e 7d 01 00 00 00 - 08 fd 7a 01 38 72 62 7d .!N}......z.8rb}
017afcb0 8c fd 7a 01 18 f2 61 7d - 1a 89 1b 01 7f 00 00 00 ..z...a}........
017afcc0 d0 fc 7a 01 51 8d 4d 7d - 7f 00 00 00 20 81 1b 01 ..z.Q.M}.... ...
017afcd0 ec fc 7a 01 18 c7 4d 7d - 39 01 00 c0 00 00 00 00 ..z...M}9.......
017afce0 00 00 8d 7c 60 fd 7a 01 - 2e 38 41 00 7f 00 6d c0 ...|`.z..8A...m.
017afcf0 00 00 00 00 01 00 00 00 - 4c fd 7a 01 d8 76 7f 03 ........L.z..v..
017afd00 b0 c9 32 00 00 00 00 00 - 24 00 00 00 20 81 1b 01 ..2.....$... ...
017afd10 9c 82 1b 01 a6 88 1b 01 - 01 00 00 00 1a 89 1b 01 ................
017afd20 00 00 8d 7c 00 00 00 00 - 7f 00 00 00 01 00 00 00 ...|............
017afd30 a6 88 1b 01 24 82 1b 01 - 8c 82 1b 01 e0 83 1b 01 ....$...........
017afd40 ec 84 1b 01 e0 85 1b 01 - 00 00 00 00 08 fd 7a 01 ..............z.
017afd50 30 ca 32 00 00 00 00 00 - 04 00 00 00 00 00 00 00 0.2.............
017afd60 a4 fd 7a 01 6e 4b 47 00 - 20 81 1b 01 9c 82 1b 01 ..z.nKG. .......
017afd70 00 00 00 00 e8 c9 07 01 - c0 da 32 00 f4 98 cb 00 ..........2.....
017afd80 c0 da 32 00 e8 c9 07 01 - a0 fd 7a 01 ac fd 7a 01 ..2.......z...z.
017afd90 e4 b0 40 00 a4 fd 7a 01 - 10 0c 8c 03 00 00 00 00 ..@...z.........
017afda0 00 00 00 00 cc fd 7a 01 - 1c 2d fe 00 d4 fd 7a 01 ......z..-....z.
017afdb0 e4 b0 40 00 cc fd 7a 01 - 00 c0 89 03 00 00 00 00 ..@...z.........
017afdc0 00 00 00 00 00 00 00 00 - 00 00 00 00 f4 fd 7a 01 ..............z.

disassembling:
[...]
00cb98e3 109 lea edx, [ebp-4]
00cb98e6 push edx
00cb98e7 mov edx, [$1138378]
00cb98ed push edx
00cb98ee push eax
00cb98ef > call -$844d70 ($474b84) ; Winapi.ShlObj.SHCreateItemFromIDList
00cb98f4 test eax, $80000000
00cb98f9 setz al
00cb98fc test al, al
00cb98fe jz loc_cb9936
00cb9900 110 lea edx, [ebp-8]
[...]


DrOli
Posts: 9
Joined: 01.12.2019, 20:52

Re: WinXP_64/Server2003_64 + crash of 790a-32

#3 Post by DrOli » 01.12.2019, 21:23

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?

Marek
Author
Author
Posts: 2761
Joined: 10.04.2006, 07:48
Location: Germany
Contact:

Re: WinXP_64/Server2003_64 + crash of 790a-32

#4 Post by Marek » 01.12.2019, 21:35

If 804 32 bit beta works then it is very likely that the current donor version 806 64 bit works too.

DrOli
Posts: 9
Joined: 01.12.2019, 20:52

Re: WinXP_64/Server2003_64 + crash of 790a-32

#5 Post by DrOli » 01.12.2019, 21:48

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?

Marek
Author
Author
Posts: 2761
Joined: 10.04.2006, 07:48
Location: Germany
Contact:

Re: WinXP_64/Server2003_64 + crash of 790a-32

#6 Post by Marek » 01.12.2019, 21:55

Please read attentive the rules https://freecommander.com/en/donor-downloads-rules/.
With "One year" or "Liftime" payment you have access to all versions.

DrOli
Posts: 9
Joined: 01.12.2019, 20:52

Re: WinXP_64/Server2003_64 + crash of 790a-32

#7 Post by DrOli » 01.12.2019, 22:28

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 least that far, and then use the update ... no joy.

Please advise on access to 80x 64-bit

Cheers

DrO

DrOli
Posts: 9
Joined: 01.12.2019, 20:52

Re: WinXP_64/Server2003_64 + crash of 790a-32

#8 Post by DrOli » 02.12.2019, 16:01

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 on 64, as per above).

Eventually, we did find an email with links to the donor/member site, and found 80x 64's. May we suggest not sending multiple emails with conflicting information.

Unfortunately, they failed also: tried both 804 64, and 806 64 under WinXP64, each failed to launch on the error - failed entry point for GetTickCount64 in Kernel32.dll.

After that we did not try other versions.

The correct entry point, and you are welcome to the dependency walker read out, is GetTickCount (i.e. without the 64) in Kernel32 ver 5.2.3790.5295.

This is a common problem with developers cross-compiling for WinXX 64, since those entry points are only in later versions of Win (I believe after Vista??).

Any chance on cross-compiling with an "overloaded" version, or whatever, so that it will actually work with WinXP64 etc?

Cheers

DrO

horst.epp
Posts: 162
Joined: 15.11.2008, 19:18

Re: WinXP_64/Server2003_64 + crash of 790a-32

#9 Post by horst.epp » 02.12.2019, 18:17

What would be the benefit to compile or debug a tool for such an exotic and unsupported OS as WinXP x64 ?
Windows 10 Home x64 May 2020 Update, Version 2004 (OS Build 19041.329)
Intel(R) Core(TM) i7-4770 CPU @ 3.40GH, 16GB RAM
Total Commander 9.51 x64 / x86, Everything 1.4.1.983 (x64)
FreeCommander XE 2020 Build 822 64-bit donor

Karol
Posts: 761
Joined: 19.08.2007, 10:05

Re: WinXP_64/Server2003_64 + crash of 790a-32

#10 Post by Karol » 02.12.2019, 19:32

You could try 806 32 bit.

Marek
Author
Author
Posts: 2761
Joined: 10.04.2006, 07:48
Location: Germany
Contact:

Re: WinXP_64/Server2003_64 + crash of 790a-32

#11 Post by Marek » 02.12.2019, 19:51

I have made change for the next release: GetTickCount64 is used for Vista+.

DrOli
Posts: 9
Joined: 01.12.2019, 20:52

Re: WinXP_64/Server2003_64 + crash of 790a-32

#12 Post by DrOli » 02.12.2019, 20:44

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 results further underscoring the need for a 64 bit version.

We would add, it would seem a little unfair to end up without a 64 bit version, since:

1) The product is advertised as supported for both WinXP 32 - 64

2) This entire discussion began and continued with the explicit question of WinXP_64/Server03_64 support. Our consideration of testing/using FC was explicitly predicated on that.

We continue to assume it was not your intention to "string us along" had you known at the outset the product did not support the specific objective.

3) Your condemnation of WinXP64 is misplaced, and also wrong. WinXP64 is a slightly de-tuned version of Server03_64 (cf. anything actually resembling WinXP32). It is a common mistake to conflate those. Server03 etc is still in some reasonably wide use. Also, in-spite of the "unsupported" assertion, it continues to be supported. For example, there were updates provided every year, up to and including this year.

Even MS is it not so stupid as to "screw over" the server community, as MS's does with its standard practice in connection with the retail community.

Should you change your mind about WinXP_64/Server03_64 support, which is your privilege, our preference would be: do not advertise or cause (unintentionally even) anyone to make payments or invest substantial resources/time on what has been promised/discussed, but not delivered

We look forward to the fix.

Ta

DrO

Marek
Author
Author
Posts: 2761
Joined: 10.04.2006, 07:48
Location: Germany
Contact:

Re: WinXP_64/Server2003_64 + crash of 790a-32

#13 Post by Marek » 03.12.2019, 20:33

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.
Please try the 807 release.

DrOli
Posts: 9
Joined: 01.12.2019, 20:52

Re: WinXP_64/Server2003_64 + crash of 790a-32

#14 Post by DrOli » 04.12.2019, 20:45

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 expertise. So, we would not presume to tell you how to manage such things, but it is possible that the manner in which GetTickCount64 was left in the package, while it may not actually be called explicitly via 807 under Server03_64, may still cause FC to look for it in Kernel32 as part of its "check libs/entries" process.

If you like, and If you are willing to let us know what language/env etc you are using, and what specific implementation you use (e.g. compiler pre-proc, overloading, cross-comp, or whatever ..), we might be able to make a contribution (where "might" is being careful to manage expectations :-).

Ta

DrO

DrOli
Posts: 9
Joined: 01.12.2019, 20:52

Re: WinXP_64/Server2003_64 + crash of 790a-32

#15 Post by DrOli » 12.12.2019, 19:05

Hi

Just wondering how things are going on the matter.

Please advise

DrO

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 7 guests