HFS not able to start.

[Zoremeth]

I really love using HFS when sharing files with friends. However, the latest build, #300 just does not want to seem to start.

When opening it gives the following error:

Code: [Select]

Application Error:
Exception EKdlError in module hfs.exe at 000A4DB0.
K.D.L initialization error.
Please put uFreeLocalizer before UTF8VCL in an uses clause of Application.

For the record, I am using Windows 10 Home. There are HFS files except the exe itself in the folder. Also, I tried the hfs24b4 version which also did not work.
Screenshot here: http://prntscr.com/l503sm

[LeoNeeson]

Hi! and welcome to the forum...

That's a weird error, since HFS it's not using "UTF8VCL" (although it seems to be related to "Kryvich's Delphi Localizer", but you are the first person to report a problem). Are you using some translated version of HFS? (like this version).

Please do this: try running HFS v2.3k Build #299 Spanish Beta and see if it gives you the same error or if it starts normally, but run it on a separate (different) folder (this is very important), without copying any personal file there (if you have another HFS version running, please close it before running this other version). Just unzip it to some folder, and run hfs.exe without adding or deleting any other file (and do not update it to the last version, just for doing this test). If the error continues, try closing any other software you have open (like for example: keynote-nf or any other software). Then please report the results here.

Cheers,
Leo.-

[Zoremeth]

Hi! and welcome to the forum...

That's a weird error, since HFS it's not using "UTF8VCL" (although it seems to be related to "Kryvich's Delphi Localizer", but you are the first person to report a problem). Are you using some translated version of HFS? (like this version).

Please do this: try running HFS v2.3k Build #299 Spanish Beta and see if it gives you the same error or if it starts normally, but run it on a separate (different) folder (this is very important), without copying any personal file there (if you have another HFS version running, please close it before running this other version). Just unzip it to some folder, and run hfs.exe without adding or deleting any other file (and do not update it to the last version, just for doing this test). If the error continues, try closing any other software you have open (like for example: keynote-nf or any other software). Then please report the results here.

Cheers,
Leo.-

Hi Leo,

I went and followed your steps. I downloaded the version you linked, put it in a separate empty folder and ran it. It still gives me the same error. After getting the error again, I closed off some programs and tried again. Still the same error.

Just for testing sake, I looked around on the internet for an older build. To which I stumbled upon a download of 2.3j (#298). And funny enough, it totally works. No problems at all. Does not even matter what it is in.

Thanks for the warm welcome and let me know if you figure something out,
Zoremeth.

[bmartino1]

I've been trying to isolate your error. As Leo said, your the first to submit something  on this type of error. Out courisity, are you using a remote desktop to the machine?

As your error is pulling some for remote screen mirrored. And potentially netframework errors. (Hfs doesn't rely on net framework installation, but it's worth a check)...

I'm glad you at least found a working build for the moment.

From what I can tell/process from the error message given by windows is:

Windows is complaining about a missing dll file, or a older dll file on which when ran a memory handle exception occurred.

Also what windows 10 build are you running?
Cmd > winver

[Zoremeth]

I've been trying to isolate your error. As Leo said, your the first to submit something  on this type of error. Out courisity, are you using a remote desktop to the machine?

As your error is pulling some for remote screen mirrored. And potentially netframework errors. (Hfs doesn't rely on net framework installation, but it's worth a check)...

I'm glad you at least found a working build for the moment.

I am not using any related to remote desktop. As a matter of fact, Windows 10 Home does not even have support for RDP. I'll have an opportunity to try with another machine today, so I'll let you guys know.

Greetings,

Zoremeth.

[bmartino1]

Side note for a FYI, all windows machine including home have rep support for windows built in see here: https://www.google.com/amp/s/www.windowscentral.com/how-use-remove-desktop-app-connect-pc-windows-10-0%3famp

And there always third party tools such as TeamViewer.

Was a courisity.

[LeoNeeson]

I went and followed your steps. I downloaded the version you linked, put it in a separate empty folder and ran it. It still gives me the same error. After getting the error again, I closed off some programs and tried again. Still the same error.

OK, thanks for your report. I almost sure this is error is caused by some kind of incompatibility with other software you have installed (or with your current Windows build). I don't know if there is a way you could generate a 'debugger dump' to help Rejetto catch and fix this error (and see why this error happened on your PC and not on others). Like bmartino1 said, as a reference it would be nice to know the exact build number of Windows 10 that you run (to do this: press Win+R, write there "winver"). For the moment, keep using that old version 2.3j (#298).

@Rejetto: is there any 'debugger' that this user could run to generate a 'dump'? I was thinking on WinDbg, but I don't if that software generates a crash report that could help you to fix this error. Since I bet this error is 90% related to the "Kryvich's Delphi Localizer" component you added on HFS 2.3 Build 300, I was thinking if there is a way to make a 'conditional' load of this component (a simple check when HFS starts: if the 'hfs.lng' file exist, then load the component normally, but if that file does NOT exist, then the component is not loaded at all, since it's not needed). Perhaps that could be a temporal solution to this (but I don't know if it's feasible to do that).

[rejetto]

that's not possible AFAIK.
I'm trying to follow the error message, so i moved the uFreeLocalizer at the top of the 'uses' clause.
Just wait for the next beta to be published so you can test this possible solution.
and welcome Zoremeth!

[Zoremeth]

that's not possible AFAIK.
I'm trying to follow the error message, so i moved the uFreeLocalizer at the top of the 'uses' clause.
Just wait for the next beta to be published so you can test this possible solution.
and welcome Zoremeth!

Thanks for the warm welcome!
I already read this message a couple days ago, sorry for replying only now. Thanks for looking into this problem. I'll be eagerly awaiting the next beta. Just @/ping me in the beta topic when it's released and I'll let you know ASAP if it fixed the problem.

[LeoNeeson]

I'll be eagerly awaiting the next beta. Just @/ping me in the beta topic when it's released and I'll let you know ASAP if it fixed the problem.

Beta 5 was already released here.

http://www.rejetto.com/hfsfiles/hfs24b5.exe

Please test it and comment the results...

[Zoremeth]

Beta 5 was already released here.

http://www.rejetto.com/hfsfiles/hfs24b5.exe

Please test it and comment the results...

Hi, I just checked out Beta 5 and it gives a similar error:

Code: [Select]

Exception EKdlError in module hfs24b5.exe at 00092A28
K.D.L. initialization error.
Please put uFreeLocalizer before UTF8VCL in an uses clause of Application.

[rejetto]

that's bad, very bad.
do you have a "language" file ? are you using hfs translated someway?

[Zoremeth]

that's bad, very bad.
do you have a "language" file ? are you using hfs translated someway?

As far as I am aware not. I have my PC set in US English, If I recall correctly. Actually it might be set in "English (Dutch)". I will have a look tomorrow at my Windows language settings.

Greetings,

Zoremeth

[LeoNeeson]

@Zoremeth: I'm as much as you interested on solving this error, given I was who proposed adding a component to HFS to make it multilingual that could lead to this error (so I hope a solution could be found).

The background of this error seems to be not a direct HFS's bug, but an incompatibility of one component used by HFS (Kryvich's Delphi Localizer), with another component (UTF8VCL) used by other software you have installed. It seems to be a very specific error, that is triggered when HFS is running with another software using UTF8VCL. At least that's how I understand that error (perhaps the cause is another thing).

@Rejetto: I don't know if this could be useful, but on the 'uFreeLocalizer.pas' there is a 'aAutoTranslate' boolean and also a 'CheckUtf8vcl' boolean. Perhaps (on theory) a simple "if hfs.lng do not exists, then aAutoTranslate or CheckUtf8vcl disabled" could disable this when the localizer is not used (but I'm not sure if that solves that error). There is (also in 'uFreeLocalizer.pas'), on line 412, the source of that error message box: 'K.D.L. initialization error.' On line 408, you will find this:

Code: [Select]

begin
  if AnsiCP = 0 then
    AnsiCP := 1250;
  if AnsiCP = 65001 then
    raise EKdlError.Create('K.D.L. initialization error.'#13#10+
      'Please put uFreeLocalizer before UTF8VCL in an uses clause of Application');
(sorry, my programming knowledge is very limited to propose a solution to this error )

[LeoNeeson]

@Rejetto/Mars: I admit my Delphi knowledge is very basic and limited, but I was thinking if something like this could help on fixing that error:

In hfs.dpr you will find this:

  Application.Initialize();

  FreeLocalizer.AutoTranslate := True;
  FreeLocalizer.LanguageFile := 'hfs.lng';

Changing the code marked in red, to the green:

  Application.Initialize();

  if fileExists('hfs.lng') then
  begin
    FreeLocalizer.AutoTranslate := True;
  else
    FreeLocalizer.AutoTranslate := False;
  end
  FreeLocalizer.LanguageFile := 'hfs.lng';

Would this work? (if this doesn't work, we can always revert back to the original code). What do you think?...