Jump to content


Photo

server directories bug in 980


This topic has been archived. This means that you cannot reply to this topic.
5 replies to this topic

#1 wkitty42

wkitty42
  • Members
  • 4 posts

Posted 12 February 2004 - 01:08 AM

i've been running release 978 for quite a while and not having any problems... i felt lucky the other day and "upgraded" ;) well, as things go, stuff broke... logging into my server worked but i was unable to access any of the directories... i'm not sure how to describe the problem... the folder icons weren't being shown... instead there was the traditional unknown icon in its place... i could manually CWD around the site but none of the GUI stuff was working as far as being able to click on directory links...

i verified the bug on several systems as well as after several installs and reboots...

i don't see this bug described in the known bugs list...

i've looked through the existing bugs reports and not seen this particular bug mentioned...

[edited - added]
i just located the 981.5 development build and the bug still exists in there...
[/edited - end of addition]

my original installation was from the non-msi full install version of 978... i installed the msi version of 980 over that so that i could use the automatic update function... i've also removed 978 and installed 980 clean and still have the same problem... i'm assuming that you want the system info from the broken version so here that is...

+- System -----------------------------

Microsoft Windows 98 SE

Total Memory : 261336 KB
Free Memory : 9220 KB

+- SmartFTP ---------------------------

Version : 1.0.980.1
Time Stamp : 2003-12-13 01:25:08

+- Application DLL --------------------

controls.dll : 1.6.980.1
ftpapi.dll : 2.0.980.1
language.dll : 1.0.980.1
reseng.dll : 1.3.980.1
smarthook.dll : 1.0.2.1

+- System DLL -------------------------

unicows.dll : 1.0.4018.0
shell32.dll : 4.72.3812.600
shlwapi.dll : 6.00.2800.1400
comctl32.dll : 5.81
riched20.dll : 5.30.23.1200
schannel.dll : 5.00.1878.13

+- Internet Explorer ------------------

Version : 6.0.2800.1106

+- Winsock ----------------------------

Winsock : 2.2

=====

step by step instructions? easy, ftp over to ftp.wpusa.dynip.com and you'll see it immediately... you can't get into any of the directories listed... here's an example of the session log...

=====
227 Entering passive mode (162,39,98,148,15,10)
Opening data connection IP: 162,39,98,148,15,10 PORT: 3850.
RETR p ----- 0 Apr 15 2000 pub
550 File not available.
=====

ummm... say what??

i think that covers all the stuff listed in your bug reporting guidelines... if you need more info, just ask 8)

#2 mb

mb

    Developer

  • Administrators
  • 11521 posts

Posted 12 February 2004 - 04:01 AM

What FTP server are you running?

The FTP server identifies itself as running on OS/2 but the directory listing is in a *NIX format.

-Mat
SmartFTP.com

#3 mb

mb

    Developer

  • Administrators
  • 11521 posts

Posted 12 February 2004 - 04:51 AM

Hello ..

The workaround is available in build 1.0.981.8
http://www.smartftp....get/SFTPDev.exe

-Mat
SmartFTP.com

#4 wkitty42

wkitty42
  • Members
  • 4 posts

Posted 12 February 2004 - 02:09 PM

What FTP server are you running?

the software is called ftpser...

The FTP server identifies itself as running on OS/2 but the directory listing is in a *NIX format.

yes, it is running on OS/2... i guess the author of ftpser used the *nix format because its the most common... OS/2 doesn't really have its own format... well it does but it resembles the DOS format...

FWIW: for those that don't know or remember, OS/2 is IBM's GUI OS that microsoft worked on with them... then microsoft threw a hissy and left and developed win95 from what they had... OS/2 was known as Warp and is now found as eCOM Station...

#5 wkitty42

wkitty42
  • Members
  • 4 posts

Posted 12 February 2004 - 02:10 PM

The workaround is available in build 1.0.981.8

thanks, i will download, verify and report back...

#6 wkitty42

wkitty42
  • Members
  • 4 posts

Posted 12 February 2004 - 02:51 PM

The workaround is available in build 1.0.981.8

and it works as desired... thanks again! 8)