Messages

1

Beta / Re: Testing build #275

« on: March 12, 2011, 05:08:52 AM »

hello,
+ the upload filter mask don't work
if you use one,  all will be N/A

i want to put a files size limit + uploal filter mask on a PUBLIC ANONYMOUS UPLOAD folder but it is not possible? how it could be??
to make a simple hosting image server from hfs

other strange reaction on the upload list result excepted with IE.
it show the previous file uploaded in the result list.

try to send 2 files here
http://82.239.5.248/files/

using the back buton.... something is not normal in the showed result. (it should show only one file).

ps :miss the "http:" google api js tag in the last default template

2

Beta / lock icon is lost

« on: January 23, 2011, 04:31:19 AM »

hello everybody.

i have encounter another trouble about permission

if you move a locked sub folder to another unlocked folder parent location.

it loose the locks icon in hfs, when the properties of the file show it is still locked,
you need to unlock+ok lock again+ok to make the change visible and show the locked icon on it.

move a locked children folders make something on the permission like a lost parent address trouble.

3

Beta / Re: Testing build #272

« on: November 23, 2010, 06:31:17 AM »

Hello
i discover a strange surprise using the last mcafee stinger...on it.(normally nothing wrong with HFS)




i have destroy the suspicious file and check a scan from a new downloaded exe to see what happend.
the time to load the vfs...and scan, but it is idem.

i hope i am the only one unlucky...  

4

Beta / Re: Testing build #265

« on: August 04, 2010, 04:11:37 PM »

the hfs265.exe  virusscan.org report:
http://virscan.org/report/f73e4c7788f1ad882e77ec468acd882b.html

bitdefender say nothing like all others. HFS is CLEAN.

5

Everything else / défouloir pour WE ARE WAITING FOR ...

« on: July 15, 2010, 08:42:04 AM »

never say WE ARE WAITING FOR,
it is not serious.

6

Beta / Re: Testing build #250

« on: December 03, 2009, 06:46:54 AM »

just in time, now it is ok for the test. even the HFS download link is no more reactive.

7

Beta / Re: Testing build #250

« on: December 03, 2009, 05:24:47 AM »

i don't know why but today avast give me an alert on HFS249 and 250  Win32:Delf-MZG [Trj]
and don't let me download the new version.

The Alwil Software daily joke, a bug reported on many usual applications. (details from a french forum)
http://www.overclocking-pc.fr/forums/showthread.php?t=10414

i submitted hfs250.exe to the false positive report
because for today and until a new database update, all avast users will not be able to open hfs.

8

Beta / Re: Testing build #249

« on: November 30, 2009, 05:00:12 PM »

no folder archive link (excepted from the hfs menu)
no parent and root folder archivable in my template but a lot of archivable children sub folders

9

Beta / Re: Testing build #249

« on: November 24, 2009, 06:35:27 AM »

after a machine crash on v249 before closing it but saving the vfs v249.
with a kernel check error alert on a first reboot.

it opened again on the vfs v248, it need to load the vfs v249, close HFS to take and write the change. (as usual)

i reverted to 248 because it was giving a better response time than 249 (before the first close).
from this page:
http://audio-planet-deluxe.eu (a 1&1 domain hosting normally not too far)

about 5mn using 249
30s using 248

Updating to 249, save the vfs, close hfs and open it again seems to work better now.

Maybe a few bot sensible on start,
65.36.241.76 internetseer.com is not cool for HFS
china telecom use also a lot of slots on many ports at the same time and it freeze HFS during few minutes.

cut the internet connection need a few time to reset HFS when it freeze, but it is faster than close and load again the vfs.

10

Beta / Re: Testing build #249

« on: November 23, 2009, 04:07:42 AM »

5mn to simply access the root,
from the machine where HFS is running.
web users will go anywhere else.

this one is super slow to show the pages, 23s for a only 6 folder page.

11

Beta / stability

« on: November 01, 2009, 06:58:53 AM »

(it freezes with the 'non responding' message)

especially when a bot send the GET request, some are more reactive.
also during a recursive listing request.

HFS is not manageable during this step, you only must wait the response from HFS to continue your changes.

if 3 people ask a recursive listing at the same time + use a download manager with unlimited slot option on.
sure it will not be cool to administrate.

12

HFS ~ HTTP File Server / Re: archivable

« on: October 22, 2009, 08:04:06 PM »

Thank you for the help,
i  found a lot of sub folders "archivables" from older HFS versions use, before the recursively hidden Flags option use.
it was to make them visible in the recursive listing if i remember.

13

HFS ~ HTTP File Server / Re: archivable

« on: October 22, 2009, 06:50:59 AM »

Thank you but,

My root flag say not archivable,
the only thing unusual is that i use a HFS short link called Home placed at the root,
were i place the Home page HTML code in the comments.

i will try to use physical real folders more than virtual folders to see what it say.

14

HFS ~ HTTP File Server / archivable

« on: October 21, 2009, 03:00:54 AM »

hello,
i have a little problem on virtual public folders normally not archivable from a "member of" account.
nothing to disable the tar download of a public folder

15

Beta / Re: Testing build #242

« on: August 14, 2009, 05:10:33 PM »

HFS limit options used,
Max simultaneous downloads from single adress
+
Speed limit for single adress

the .tar speed limit off occur sometime when HFS and flashget are running together,
due to a bug sometime on a torrent download when HFS is opened. (in a custom use, tracker link off)
now it seems to be better.
i only found 2 time the same error on the hfs ini (ban ip+slot limit) after a machine crash or a power cut,
reverted to previous data. (saved in HFS close/open only ?)

Robots visit also make the server slow or bad reacting to mouse during a few moment.
impossible to admin server folders when you are visited, you only have too wait the finished request.