-
Notifications
You must be signed in to change notification settings - Fork 710
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help not working #353
Comments
it seems it just can't find the file. i downloaded WINFILE.CHM from this github (winfile/help) and it works fine, tho idk how to let the program itself be able to open it |
I believe potential solution (and the source of the problem) have been mentioned here: #60 .hlp files have been deprecated in Windows 10, but .chm still work properly |
Note there's PR #211 to use HTML help, which is the easy part. The harder part is we have a .hlp file from NT 4 that's a fair predecessor to the current code, and a .chm file from Windows 98 which didn't include any of the NT enhancements, and seems much less comprehensive in general. Making help work "well" means decomposing the .hlp file into HTML parts and assembling a .chm file from it. |
@malxau I managed to open that .hlp file and it does seem mostly still up to date imo, do u think its possible to convert it to a more modern format? and maybe its possible to find a more recent/up to date help file? Sorry if i dont rly know what im talking about, i just found the help menu doesnt work and dove into a rabbit hole :p |
The Windows ME one will be similar to the .CHM in Windows 98. I thought the .HLP one here was the one from NT 4. I don't know of good tools for this conversion, although they probably exist. .HLP files were created from .RTF files that contain a lot of footnotes which get compiled into .HLP. .CHM is a compressed HTML archive. Doing this without a tool seems very painful (you'd need to navigate each page, copy/paste, and recreate all the links.) So automation seems essentially mandatory. |
So I took the liberty of converting the old "WINFILE.HLP" file into plain html format. I used HELPDECO to convert the original HLP file into .rtf format and then I used Microsoft HTML Help Workshop to generate the .htm files. Following this I did some manual editing by adding the navigation buttons (Contents, Back, Forward), changing hyperlinks to teal color (for better look and similarity to the old HLP format) and some cleanup. I made no attempt to add any new information or to check for possibly redundant old information in the text. But at the very least these .htm files could provided a basis for further help file updates... Programs used:
|
Thanks for looking into it. I took this to see what it would take to make a I noticed this when trying to construct an I think this file must have come from an early NT beta. One thing that made me laugh is "Names of Open Windows NT" in "Window Menu Commands." This doesn't appear in any of the released versions. |
Oh, I see what you mean now! Attached are the Microsoft HTML Help Workshop project files for the "hopefully" more recent Windows NT 4.0 HLP file converted to .chm with the raw .htm files included. |
P.S. Microsft HTML Workshop used to be available here: You can get it still from Internet Archive by searching for the direct dl link and selecting one of the older dates like 2007 for example. |
I updated the html help files a bit to remove the obsolete information and update some other parts. These help files should now be usable although they still lack text for the new features and could be made richer in content. I believe using plain html (.htm) files would be the best choice for future compatibility as .chm files may also stop working at some point like .hlp and editing them may also require old and obsolete software. My latest edits to the Winfile html help files can now be found here: P.S. Also I think the 'Search for Help on...' and 'How to Use Help' menu entries can be removed leaving only the 'Contents' option to open the help in the web browser (of course F1 key will also work). |
Trying to open help from here:
Or from here:
Results in:
The text was updated successfully, but these errors were encountered: