k-stone wrote:

So cant I do something to help?

I have sent you and email.

A few investigative clicks later:

- neither RegMon nor FileMon show abnormalities, 4.04 just gets a FINAL_CLOSE from kernel32 before it really gets some action.

So what about netapi32.dll?
- netapi32.dll (winXP) size 333 kB with lots of exports and functions in it, wow!
- netapi32.dll (win98) size 20 kB (as a zip-file just 1 kB, because it consists almost entirely of 0x00s), hardly any function at all.
- so netapi32.dll of win 98 apparently cannot "do" anything even if WinSCP 4.04 hopes it does.
- so what _does_ WinSCP hope in 4.04 it did not in 4.03?

- by the way: netapi32(XP) does not work in win98 without upgrading 98 to XP... 8)

martin wrote:

Can anyone who is having the problem contact me?

Hi there,
I'm working with 4.02 Build 344 on Windows 98 SE which works fine.
Downloaded 4.04 on another computer and it failed with the error messages already discussed here.
So cant I do something to help?
k-stone

Can anyone who is having the problem contact me?

This problem will be solved in the next release.

The two previous posters mentioned that they had the following error when upgrading from version 4.03 to 4.04 of WinSCP:

The WINSCP.EXE file is linked to missing export NETAPI32.DLL:NetApiBufferFree

I also got this error when I tried to run the program a _second_ time after I got the message indicated in my original posting. I discovered that another copy of WinSCP was running in the process list, but was not running on the screen/taskbar.

When I closed down the runaway WinSCP process and tried to execute the program again, the error message ending in "NetApiBuffer" went away and the original error message ending in "NetUseGetInfo" reappeared.

RFSharpe

I chime in with both the praise of this program as well as the above mentioned error msg.

On my Win98SE system I get the NetApiBufferFree msg, too, when trying to start 4.0.4.

In my Win System folder there's a Netapi32.dll version 4.10.1998

With 4.0.3 WinSCP starts without problems.
On WinXP (Home) 4.0.4 has no problems.

ardik

PS:
I do appreciate it very much that WinSCP now supports plain FTP, too!

I encountered a similar error when installing on WinME machine.

The second window is the same, the first window is similar but says

The WINSCP.EXE file is linked to missing export NETAPI32.DLL:NetApiBufferFree.

I also echo the previous post. This is a great program and I look forward to the correction of this bug. I will step back to an earlier version of 4.x. I was in the process of upgrading from 3.x.

I run ME on a laptop. I can't really update the operating system on this hardware, but it does what I need, so I haven't replaced it.

I attempted to do an upgrade of WinSCP from version 4.03 to version 4.04. This installation was on a Windows 98se computer. I am using the Norton Commander Interface.

The first time I tried to upgrade, I used the "Installation Package." I selectd the default "Full upgrade (recommended)." The progress bar on the "Setup - WinSCP" dialog box appeared completed. Another dialog titled "Setup - WinSCP" appeared and indicated the following:

Unable to execute file:
C:\Program Files\WinSCP\WinSCP.exe

CreateProcess failed: code 31.
A device attached to the system in not functioning.

Another dialog box appeared that was titled "Error Starting Program." This dialog box contained the following error message:

The WinSCP.exe file is linked to missing export NETAPI32.dll:NetUseGetInfo

When I looked in the C:\Windows\System a file named NETAPI32.DLL was present. When I looked at the properties of this file, it indicated that the version number was 4.10.1998.

When I tried to run the program (after the failed install) I got the same series of error messages.

I then uninstalled the WinSCP and installed the standalone version of WinSCP, with the exact same results.

I resolved the problem by reinstalling version 4.03 of WinSCP and the program ran with no errors.

prikryl - Thank you for a great program and thank you for looking into this problem.

I have not had this problem on any of the WinXP Pro machines that I have installed WinSCP on... It is likely a result of me not being able (or too lazy) to get rid of this Win98se computer.

RFSharpe