hfs
hfs copied to clipboard
HFS not opening
In my computer HFS3 open and close without any information:
https://github.com/rejetto/hfs/assets/74371138/d855cf8c-e7fa-4e58-9974-8c38b5e8354f
Windows 10 22H2 x64 clean install.
If any useful message is displayed, it is lost when the window is closed. Can you run it from the command prompt?
Ok, i run with a batch file:
@echo off hfs.exe echo. pause
Wow, that's...nothing. 🫠 I have no clue. No error message, and that's a bit expected as the debug file was empty.
Yes, I also found it very strange, I tried removing the plugins folder and the behavior is the same.
Ola Bom dia,
Tambem estou com msm problema
Same situation on Tiny10 (custom lite version of Windows 10). For me it started occuring since 0.52.3. Version 0.52.2 works fine.
are you saying that you tried 0.52.2 AFTER 0.52.3 failed? i studied changes changes between these 2 versions, and i don't think there's anything that may cause that
I tried latest version first and when it didn't work started going back untill I found the working one. Yes, 0.52.3 was the version where this issue was first introduced.
thank you for the clarification! this info is an excellent starting point, but sadly i still cannot fathom what could be the cause. i may only attempt a test, where i give you like 3 intermediary versions betwen .2 and .3, attached here, and you tell me what of them start, so i can further narrow the circle. would you be available?
another question: do you have another Windows (not "tiny") so that you can tell me if new versions run?
Sure, I can test it for you and I do have another PCs with both Windows 10 and 11.
cool, does hfs run on the other computer?
Yes, with both Win10 and Win11 on other PCs. I suspect that this issue occurs only in older versions of Win10 and if that's true it will probably be the same in Win8/8.1.
I also have the same phenomenon. It's Windows Server 2012 R2. Currently using 0.52.0 and stops immediately after startup in all versions of 0.52.1 or later. However, on Windows 10 1809 PCs, it operates normally after 0.52.1.
I also have the same phenomenon. It's Windows Server 2012 R2. Currently using 0.52.0 and stops immediately after startup in all versions of 0.52.1 or later. However, on Windows 10 1809 PCs, it operates normally after 0.52.1.
i'm sorry for the late reply, i had lost track of your message. While i'm not sure if Windows 2012 is officially supported by node.js (HFS is based on), i studied changes between 0.52.0 and 0.52.1, and I cannot find any possible reason for it to not work. Let me know if the problem persists with most recent version of HFS.
I tried the latest version, but it was in the same state. I still use 0.52.0.
https://github.com/user-attachments/assets/eb3c9df3-2361-42a0-bae7-b0ff57320e62
thank you for your report. i studied some more the changes between 0.52.0 and 0.52.1 and i still cannot find anything useful to explain. anyway, my suggestion for you is to NOT use an old version of hfs, as it's not wise to use unmantained server software. You can instead install node.js (18 or newer) and follow these simple instructions https://github.com/rejetto/hfs?tab=readme-ov-file#other-systems
@yb1536 i saw that you have a file "debug.log". That may contain useful information.
In my case debug.log was empty.
in your video i see 1KB
The log is as shown in the picture.
Same behaviour in my setup. v0.52.2 is the last one working. In Process Monitor I see this entry:
D:\Tools\HFS\crc32.win32-x64-msvc.node NAME NOT FOUND
D:\Tools\HFS\node_modules\@node-rs\crc32\crc32.win32-x64-msvc.node PATH NOT FOUND
D:\Tools\HFS\@node-rs\crc32\crc32.win32-x64-msvc.node PATH NOT FOUND
D:\Tools\node_modules\@node-rs\crc32\crc32.win32-x64-msvc.node PATH NOT FOUND
D:\Tools\@node-rs\crc32\crc32.win32-x64-msvc.node PATH NOT FOUND
D:\node_modules\@node-rs\crc32\crc32.win32-x64-msvc.node PATH NOT FOUND
D:\@node-rs\crc32\crc32.win32-x64-msvc.node PATH NOT FOUND
Using Firefox 115.21.0esr (64-bit).
@MostlyOffline what is your Windows version?
@rejetto: Windows 10 version: 22H2 OS build:19045.3930
@MostlyOffline are you running hfs.exe or using npx ?
@rejetto Only running hfs.exe.
@MostlyOffline try this
- install node.js (version 20 or greater)
- execute at command line
npx hfs@latest
@rejetto Reluctantly. I may say, I had to install a bunch of stuff like Visual Studio thingies, but for the test purposes I did all that. The npx takes ages to load but same result, it just exits without any message. Again Proc Monitor somewhere towards the end has an entry:
..\AppData\Local\npm-cache\_npx\95660a09cc333978\node_modules\@node-rs\crc32\crc32.win32-x64-msvc.node NAME NOT FOUND
..\AppData\Local\npm-cache\_npx\95660a09cc333978\node_modules\@node-rs\crc32\crc32.win32-x64-msvc.node.js NAME NOT FOUND
..\AppData\Local\npm-cache\_npx\95660a09cc333978\node_modules\@node-rs\crc32\crc32.win32-x64-msvc.node.json NAME NOT FOUND
..\AppData\Local\npm-cache\_npx\95660a09cc333978\node_modules\@node-rs\crc32\crc32.win32-x64-msvc.node.node NAME NOT FOUND
..\AppData\Local\npm-cache\_npx\95660a09cc333978\node_modules\@node-rs\crc32\node_modules NAME NOT FOUND
..\AppData\Local\npm-cache\_npx\95660a09cc333978\node_modules\@node-rs\node_modules NAME NOT FOUND
@MostlyOffline i'm sorry you had to install that stuff, i didn't expect it. it is possible that i made my tests on machines where those things were already installed. i'm quite sure that the same procedure on linux machines doesn't require additional stuff.
- is your Windows anything special, like some "lite" version?
- do you have another Windows machine?
- is your cpu ARM ?
@rejetto
- It's Windows Pro but I installed the X-Lite version, if you've heard of it. It's kind of a lite edition without some MS stuff like Microsoft Edge.
- This is my only machine.
- It's an old AMD Phenom II X4 955. I just don't get why the 0.52.2 works but the 0.52.3 doesn't. What changed between those two? Maybe that's where you can pinpoint the issue. Do they use some different node.js version? Maybe they changed something. Just throwing thoughts..
EDIT: Surprisingly enough, 0.52.2 doesn't work with node.js. I don't know if something didn't install properly. Used: npx [email protected] and it does the same "cycle" before exiting.
My Windows is Microsoft original (not lite version), but no any updates installed. HFS opens and close. Version 10 22H2 19045.2006.
It seems that there is a missing runtime that is necessary for giving these errors in lite versions or versions without updates, what would that runtime be?