rejetto forum
Software => HFS ~ HTTP File Server => Topic started by: Alons0 on September 18, 2007, 07:03:43 AM
-
Hfs was working fine, but after a restart it cannot start. I tryied restarting again and there's no result
-
I blame the wallpaper.
Also.
Backup your HFS setup, delete all traces of HFS then download and start a clean HFS install. IF that works then uno its maybe your config file corrupt or something... other than that i have no idea.
-
i delete rejetto/hfs/ from registry and then it starts but i can't load my .vfs save file. Look at where's the problem:
-
If what TSG said to try doesn't work then maybe try a system restore to when your computer last created a restore point? (maybe windows downlaoded updates that are affecting it?)
Also try and old version of HFS and see if it is just happening with build 135.
-
that error is issued by the Zlib
i don't think your vfs got corrupted, because HFS does CRC on it should detect data corruption.
maybe i can reproduce the problem if you send me your vfs file (it may contain private information).
-
that error is issued by the Zlib
i don't think your vfs got corrupted, because HFS does CRC on it should detect data corruption.
maybe i can reproduce the problem if you send me your vfs file (it may contain private information).
rejetto this morning i reinstalled my windows and hfs started but the problem with loading is again here. Now when i try to open hfs (131, 134 or 135), i view don't send window. Tell me what to do and whre i can upload my vfs file ::) :'(
-
you can contact me at rejetto@@@@@rejetto.....com
-
rejetto@xxxxxxxxxx.com ?
-
please, THINK before you do
-
please, THINK before you do
I wrote here the right mail but the forum change it to "xxxxxx.com", look at and your previous post how it is shown
p.s. i send you mail at rejetto [aaaaaaaaaaaaaaaaaat] rejetto [dot] com
-
have you EVER heard about spam?
i give up
-
PERSONAL MESSAGES, are handy for that kinda thing.
-
TSG your frickin hilarious, thats exactly what I was gonna say. (The wallpaper)
Another waste of a post :)
-Kurt
-
bug fixed in next build