Projanglez wrote on Today, 15:07:

Interesting discussions... I'll come back to that later. […]
Show full quote

Interesting discussions... I'll come back to that later.

But in the meantime:

FTP4DOS v1.1.0 is out!

• New feature: Self-Update function
  • Downloads latest binaries from GitHub
  • Optional automatic update check (opt-in)
  • Updates are cryptographically signed using RSA-2048, preventing man-in-the-middle attacks and compensating for the lack of HTTPS support on retro platforms

Download here:
https://github.com/Projanglez/FTP4DOS/releases/tag/v1.1.0

It is expected but I'm telling anyway: this new version still fails to load the remote server pane after a successful connection on my PC. There is no error message only an empty blue pane and an <empty> label at the status area.

Falcosoft wrote on Today, 15:44:

It is expected but I'm telling anyway: this new version still fails to load the remote server pane after a successful connection on my PC. There is no error message only an empty blue pane and an <empty> label at the status area.

Yes, I can confirm your problem - it's due to insufficient conventional memory.
I tried to eat various amounts of RAM using RAMDRIVE.SYS, and found when FTP4DOS begins to fail:

1Memory Type        Total       Used       Free
2----------------  --------   --------   --------
3Conventional          640K       162K       478K
4Upper                   0K         0K         0K
5Reserved              384K       384K         0K
6Extended (XMS)     64,512K        68K    64,444K
7----------------  --------   --------   --------
8Total memory       65,536K       614K    64,922K
9
10Total under 1 MB      640K       162K       478K
11
12Largest executable program size       478K (489,472 bytes)
13Largest free upper memory block         0K       (0 bytes)
14MS-DOS is resident in the high memory area.

Grzyb wrote on Today, 17:13:

Yes, I can confirm your problem - it's due to insufficient conventional memory. I tried to eat various amounts of RAM using RAMD […]
Show full quote

Falcosoft wrote on Today, 15:44:

It is expected but I'm telling anyway: this new version still fails to load the remote server pane after a successful connection on my PC. There is no error message only an empty blue pane and an <empty> label at the status area.

Yes, I can confirm your problem - it's due to insufficient conventional memory.
I tried to eat various amounts of RAM using RAMDRIVE.SYS, and found when FTP4DOS begins to fail:

Copy code to clipboard

1Memory Type        Total       Used       Free
2----------------  --------   --------   --------
3Conventional          640K       162K       478K
4Upper                   0K         0K         0K
5Reserved              384K       384K         0K
6Extended (XMS)     64,512K        68K    64,444K
7----------------  --------   --------   --------
8Total memory       65,536K       614K    64,922K
9
10Total under 1 MB      640K       162K       478K
11
12Largest executable program size       478K (489,472 bytes)
13Largest free upper memory block         0K       (0 bytes)
14MS-DOS is resident in the high memory area.

Thanks!
Yep, as I said before I only have about ~450 KB free conventional memory after both network stacks are loaded.