rejetto forum
Software => HFS ~ HTTP File Server => Topic started by: MarkV on March 18, 2008, 02:53:57 PM
-
I'm currently testing HFS under old OS again, and will document my findings here:
This is not a support request topic, we all knew the day would come. But it will be found through the search facility.
Windows NT4: HFS 2.3 beta build #180 broke compatibility with NT4, last working: #179
(I guess it's because of the 'Prevent standby' option).
Error message of #180(translated): 'Procedure entry point 'SetThreadExecutionState' could not be found in the Dynamic Link Library "kernel32.dll".'
Build #181-#183 fail to start silently (without error message) Use build #186, it works.
Windows 95C: Last working build is #179, all other builds behave exactly the same as on Windows NT4. Build #186 works again.
Windows 98SE: HFS 2.3 beta build #183 appears to work flawless. I guess ME will work, too.
So, the older OS are out cold now.
-
can you copy the kernel.dll to the hfs directory to make it work?
-
kernel32.dll is the windows kernel and depends on a whole lot of other DLLs. It is not transferrable between Windows versions. Though I may try it I'm almost shure it won't work.
edit: As I expected, no dice...
Like I said, HFS can't evolve and be compatible with all older OS at the same time. Sometimes you have to leave something behind... think about Windows and DOS. Nobody's missing DOS today (besides me, of course :)).
-
well, i think there is an easy way to make it compatible, since it's just for this dll function call.
i will work on it.
-
next build may solve this problem
-
Thanx, will definitely test this.
Edit: Tested Win95C so far, works with #168.
Edit2: WinNT4SP6a also works, great news.
As this topic now lost it's meaning, I close this now.