rejetto forum
Software => HFS ~ HTTP File Server => Bug reports => Topic started by: Guest on November 20, 2006, 02:44:15 AM
-
Anyone had any problems with 2.1 build # 61 ?
I'm using Win 98se and have never had any real problems
untill now. Build 61 locked my computer up, and the only
way out was the "off" button. Tried it twice. Sorry,
couldn't get any log or error messages due to the lock
up. Went back to #60 and everything is OK.
-
so strange
can someone tell more?
-
Is there any way that the build # could be shown some where in HFS ?
After the lockup I went back to an older version, but I can't be
sure now if it was #60.
I downloaded #61 again, to the desk top, and it will run from there,
of course with no files, etc. When I move it to the usual folder with
the vfs and ini, and try to run it, it still locks me up. Push the off
button time, no other way out. As I said in the first post, when I went
back to the older version (what ever it is), it works just like before,
great !
Its a first for me, been following HFS with no real problems since the
early 2.0b days.
-
menu -> about
if you send me your vfs and ini, i can see the bug and fix it.
-
On checking I find I went back to #57. #60 locks up also. Don't have
# 58 or 59.
I think there is more problem than just vfs or ini. I tried to set up #61
fresh, new files, etc, in different directory. As I add folders I get "Access violation
at address 004d0f86 in modlue hfs.exe. Read of address FFFFFFFF". I also see a
Stop sign and "Abort File Addition" in the title bar. Never noticed it before? Thats
with no vfs or ini created yet? At this point it doesn't lock me up, though.
Yet my # 57 still works great ?
I don't see the means to send vfs & ini except attach here in forum ? Unless they
could help you in some way, I question their usefullness, because they work. I can't
create in #61 to send.
-
you told me those vfs&ini were able to block the last HFS.
i told you i can use those files to see the bug, and then fix it.
if i'm not able to see/reproduce the problem, i can't fix it.
saying "add folders" is not a way, because everyone on this forum adds folders, and no error comes up. there is something more to know to reproduce the problem.
of course it is not a good idea to attach your files in the forum, but you can write me privately, also email if you want.
and of course i'm not sure those files will be useful, i can only hope so.
-
Sent ini & vfs by email.
-
Tried shutting down all running processes, except Explorer, systray, starter & stimon.
No luck.
Moved working HFS #57 to backup and deleted off my HD.
Executed #61 on desktop. It loads, and shows port that is still
forwarded in my router, without my setting the port in HFS ?
Found this odd ? Always before when a new copy was setup in a
different directory port was default. Port forwarded had to be specified.
Added folders with files, and set some options. Saved options
and ini was created on desktop. Set to save options and vfs on exit.
Did a manual vfs save to desktop. It would not, got error message,
"Access violation". With folders/files still showing I tried self test.
It passed, says working OK, but can not access hfs via internal
address, nor local host.
Port is correct, router is correct.
Toward the end of this test, it dumped all files/folders that had been added.
It will not save vfs on exit.
It seems to me, that I should have been able to set up and start new
but couldn't, although I'd been able to in the past.
Logic says that, since I have not added any software nor made any changes
to my system from build 57 to build 61 the problem likely is in vfs.
I have ini from 61, but cannot create vfs.
Reminds me of the problem related in thread "could it be my os?"
Don't know what else to try (yet).
-
please answer
1. if you NOW use build #057, is it all ok and working?
2. tell me the address specified after "access violation"
3. to ensure HFS is clean, hold the SHIFT key while it starts. this will skip any pre-configuration. using this clean HFS, does the problem occur?
-
I have problems on one of my (older) systems with build #61, too. The system in question is a Win95C system. Ran build #57 'till now, NO problems at all.
Now with #61 I can't save my VFS...Access violation at address 004D0F86 in module 'HFS.EXE'. Read of address FFFFFFFF.
Renamed my VFS and settings, and tried again. No way. Can't save VFS...
MarkV
-
read email
-
1. Yes, build 57 works perfect, as I have it configured.
2. More than one at different times. 004FC4ED, 004D0F86 and another.
I will email two .jpg screen shots.
3. When I held shift and loaded, ini disappeared, but still couldn't
create vfs. Second screenshot is of the result of trying to load vfs
used with 57.
When 61 is executed I can access it with browser on lan address.
When files are added, cannot, yet self test says OK, then cannot save
vfs. This was with default template, no index page, etc.
-
i meant: check your email, i sent you a test build
-
Build #62 seems to have fixed the problem for me.
What was the problem, if I may ask? I have no problem if Win95 may not be supported in future, these machines operate HFS only in LAN...
MarkV
-
i found a "line" that should not be.
an error made moving the code.
i will soon publish build #062.
-
Replaced 57 with 62 in my HFS directory, and gave it a quick
run through. Looks like it works great ! No problem with existing
ini or vfs, and it manually saved vfs with no problem.
Looks like problem solved on Win 98se !
Outstanding.....Many thanks !
-
great, i will publish build 62 then
-
Yep, had the same Prob on my Win98SE machine. I'll wait for #62 :)