1
HFS ~ HTTP File Server / Re: Download Speed Problems
« on: February 25, 2011, 05:47:21 PM »
What is your maximum internet 'upload speed'? (Yes, I said upload not download speed). If you don't know contact your ISP and let us know.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
HTML & templates / Re: search feature in 2.2f
« on: January 28, 2011, 07:56:01 AM »
That's not 2.2f.
3
HTML & templates / Re: Upload form needs improvement
« on: January 09, 2011, 12:05:48 PM »Thanks Maverick
%symbols% problem goes back past 253 here. I was going to go back to
240 but it wont run on wine here. I like your progress page, does it close
when the upload finished page appears?
Yes.
The only reason why I used build 240 was because it was the oldest build I had available on my drive.
@ MarkV
Thanks. Looks like this problem was reported on and has been around for a while. Strange that there wasn't a priority in fixing it.
4
HTML & templates / Re: Upload form needs improvement
« on: January 09, 2011, 08:24:09 AM »
I agree with r][m there is a symbol problem with build 272 and probably other builds as well.
This is the first time I checked the upload progress for quite some time. I also wasn't using the latest build before checking this today. This was all done locally.
Build 240 - no problems
Build 272 - problems - I should also note that every upload I tried to make with this build FAILED. Log reason was file NOT ALLOWED in Upload folder. Have no idea why.
I didn't try to determine what build the problem started in. I just don't have the time right now. But it is definitely somewhere between build 240 & 272.
I'm attaching a couple of screen shots (one for each build I tried) that clearly show the results.
I use a customized template with absolutely NO javascript or ajax.
This is the first time I checked the upload progress for quite some time. I also wasn't using the latest build before checking this today. This was all done locally.
Build 240 - no problems
Build 272 - problems - I should also note that every upload I tried to make with this build FAILED. Log reason was file NOT ALLOWED in Upload folder. Have no idea why.
I didn't try to determine what build the problem started in. I just don't have the time right now. But it is definitely somewhere between build 240 & 272.
I'm attaching a couple of screen shots (one for each build I tried) that clearly show the results.
I use a customized template with absolutely NO javascript or ajax.
5
Beta / Re: experiment
« on: October 18, 2010, 04:36:55 PM »
Login and logout also works with new default template in Opera.
I wouldn't mind adding a logout function to my customized template, but have no idea what is needed to add ajax to it.
I wouldn't mind adding a logout function to my customized template, but have no idea what is needed to add ajax to it.
6
HFS ~ HTTP File Server / Re: Favicon not showing in IE or Opera & others - Works fine in FireFox
« on: August 23, 2010, 05:29:32 AM »
Two things... Maybe enable animated images is turned off in those browsers if animated favicons needs that enabled. Or maybe those browsers don't support animated favicons to begin with.
7
HFS ~ HTTP File Server / Re: Suggestion about save options
« on: August 13, 2010, 02:32:41 PM »
rejetto,
As you know I have been running hfs (all versions and the various beta builds) for about 5 years now. I have never experienced any kind of loss by saving to file and have never saved to the registry.
From what I can recall reading is from new users that have lost their vfs or their ini because they weren't saved even once before shutting hfs down. As nothing was saved they had to start over the next time they re-started hfs.
Saving to file is doing the job it is supposed to do for me and I also backup the ini with a script. I don't think saving to file is a cause of data loss.
As you know I have been running hfs (all versions and the various beta builds) for about 5 years now. I have never experienced any kind of loss by saving to file and have never saved to the registry.
From what I can recall reading is from new users that have lost their vfs or their ini because they weren't saved even once before shutting hfs down. As nothing was saved they had to start over the next time they re-started hfs.
Saving to file is doing the job it is supposed to do for me and I also backup the ini with a script. I don't think saving to file is a cause of data loss.
8
HFS ~ HTTP File Server / Re: Suggestion about save options
« on: August 13, 2010, 12:52:57 AM »- saving to file is currently not safe (saving to registry is safe instead, AFAIK)
This is the first time I have heard anyone say that "saving to file" is not safe. This is now coming from rejetto without any explanation as to why it is not safe.
Please explain yourself.If there is a security issue by saving to file, I consider this to be a bad bug that has to be fixed.
Comments.
9
HFS ~ HTTP File Server / Re: hfs.exe disappears on reboot
« on: August 08, 2010, 07:16:15 AM »
and ... save settings to file
10
HFS ~ HTTP File Server / Re: Locking Files
« on: July 19, 2010, 05:30:28 AM »How do I indicate to HFS that file xyz.abc is the one which should no longer be downloadable but only listed.
What you can do is move the files that should no longer be downloadable to a real folder, then in properties for that folder flag "no download". The file list will still appear but the files won't be downloadable.
11
router & port problems / RE: psl_: Self Test Passing, But Can't Connect From Any Other Computer
« on: July 06, 2010, 05:25:21 PM »Quote
I have everything setup correctly and HFS is telling me that the port forward is not set up correctly
All the information you need to set can be found here ... http://portforward.com/
12
HFS ~ HTTP File Server / Re: how can I perform a selftest?
« on: July 03, 2010, 03:03:16 PM »How can I do a test myself,to see HFS is working correctly?
Go to a friend's house and connect to your server from there.
13
Bug reports / Re: HFS 2.3 disk is made accessible to other users on the network as real folders
« on: June 29, 2010, 04:34:30 PM »HFS (2.3 Bild 260) hard disks = real folders
big folders> 7 GB is not visible,
Just a thought... in the virtual file system of HFS, right click on a big folder that contains files >7 GB. Select Properties. Did you give access to people you wanted to have access to those files/folders? If people don't have access, they won't see the folder in the browser (if menu -> virtual file system -> list protected items only for allowed users is selected).
14
HFS ~ HTTP File Server / Re: I used AppToService to make hfs.exe run as a service. I cannot access hfs site
« on: June 23, 2010, 02:31:55 PM »
Check these HFS menu settings....
1. Menu -> load recent files -> select -> 'share.vfs'
2. Menu -> start/exit -> select -> 'reload on startup VFS file previously open' and select -> 'auto-save vfs on exit'
1. Menu -> load recent files -> select -> 'share.vfs'
2. Menu -> start/exit -> select -> 'reload on startup VFS file previously open' and select -> 'auto-save vfs on exit'
15
HFS ~ HTTP File Server / Re: I used AppToService to make hfs.exe run as a service. I cannot access hfs site
« on: June 23, 2010, 08:04:38 AM »
First of all, look at the following HFS menu items in expert mode...
1. menu -> start/exit -> make sure 'only 1 instance' is checked.
2. menu -> tray icons -> make sure 'show main tray icon is checked.
One of the very first things that should happen when you bootup is you should see the HFS popup loading the virtual file system. You aren't seeing this.
When you double click on hfs.exe you are actually bypassing apptoservice by running another copy of HFS and that is probably the one that shows up on port 80 because port 80 is the default. This other copy isn't configured to use port 8888. That is not what you should do. Make those menu changes I mention above which includes 'only one instance'.
You have to many things going on here that are causing your problems and they have to do with installation and configuration.
I would suggest you START OVER.
1. Save your virtual file system to a file and Exit from HFS. If HFS works correctly with IP localhost on port 8888 and there is no problem with your virtual file system you should be ok there. If there are problems with HFS or your virtual file system, re-install it.
2. Remove the app2service from services and re-configure it. Reboot to clear the cache. Make sure that the path to the HFS working directory is correct. Otherwise, your computer won't be able to find your virtual file system to load at bootup. If that doesn't happen you will have the same type of problem.
3. It might be a good idea to move the HFS working directory to another drive like c:\
4. When finished configuring apptoservice, Reboot. Go to Windows Services and make sure apptoservice is set to 'automatic' in properties. Also in properties check the path to see if it is correct.
5. Reboot again and cross your fingers that it works.
1. menu -> start/exit -> make sure 'only 1 instance' is checked.
2. menu -> tray icons -> make sure 'show main tray icon is checked.
One of the very first things that should happen when you bootup is you should see the HFS popup loading the virtual file system. You aren't seeing this.
When you double click on hfs.exe you are actually bypassing apptoservice by running another copy of HFS and that is probably the one that shows up on port 80 because port 80 is the default. This other copy isn't configured to use port 8888. That is not what you should do. Make those menu changes I mention above which includes 'only one instance'.
You have to many things going on here that are causing your problems and they have to do with installation and configuration.
I would suggest you START OVER.
1. Save your virtual file system to a file and Exit from HFS. If HFS works correctly with IP localhost on port 8888 and there is no problem with your virtual file system you should be ok there. If there are problems with HFS or your virtual file system, re-install it.
2. Remove the app2service from services and re-configure it. Reboot to clear the cache. Make sure that the path to the HFS working directory is correct. Otherwise, your computer won't be able to find your virtual file system to load at bootup. If that doesn't happen you will have the same type of problem.
3. It might be a good idea to move the HFS working directory to another drive like c:\
4. When finished configuring apptoservice, Reboot. Go to Windows Services and make sure apptoservice is set to 'automatic' in properties. Also in properties check the path to see if it is correct.
5. Reboot again and cross your fingers that it works.