New
#11
Thanks a lot Kimio!
I'll do it asap, and I'll tell you the result.
Best regards,
Bruno
Thanks a lot Kimio!
I'll do it asap, and I'll tell you the result.
Best regards,
Bruno
If you don't want to do all of that work, here is a copy of the Windows XP 32-bit winhlp32.exe file:
And the Virustotal report to prove that this is not a virus or fake copy: https://www.virustotal.com/en/file/f...is/1441147593/
A 64-bit Winhlp32.exe file will be posted soon!
(You'd better be grateful because I am installing XP x64 in a VM just for this! :P)
I'm not sure if this will work for all hlp files and if it does, you will have to manually find the hlp file, but I was able to open a hlp file by dragging and dropping it over winhlp32.exe. Or you could do what the other guy said to do, which is essentially taking ownership of the fake winhlp32.exe in the Windows folder and replacing it with the one from Windows XP.
SUPPLEMENT-3:
(1) First, get a file for Windows XP (x64) by,
[REMOVED UNAUTHORIZED DOWNLOAD LINK]
Note:
Press the "Download" button (light blue button), locating below the item "Windows XP 64 Bit ISO Free Download."
You can get one downloaded file (*) (by waiting roughly 4 minutes),
(*): Windows_XP_64Bit_Pro.zip
(2) Then, de-compress the "zip" file (i.e. Windows_XP_64Bit_Pro.zip), by using some un-zipping tool.
You can get the "Windows_XP_Professional_64-bit.iso."
(3) Check the contents of this "iso" file (i.e. Windows_XP_Professional_64-bit.iso), by using some tool (for looking the contents of an “iso” file).
(4) You can find "WWINHELP32.EX_" in the "I386" folder of this "iso" file.
Note:
Be careful NOT "WINHELP32.EX_"
(5) Copy this “WWINHELP32.EX_” into a temporary folder on your HDD.
(6) Open the “Command Prompt” window, and then move the prompt to the temporary folder (in which the “WWINHELP32.EX_” exists).
(7) Execute following command in the temporary folder (in which the “WWINHELP32.EX_” exists);
expand wwinhlp32.ex_ winhlp32.exe
Note:
Be careful "wwinhlp32.ex_" and "winhlp32.exe"
By this execution, you can get “winhlp32.exe” (which has been de-compressed from “WWINHELP32.EX_”).
As a result, you can use this “winhlp32.exe.”
[IMPORTANT NOTE]
If an old help file (*.hlp) can not be opened on Windows XP/2000/ME/98/98SE, this kind of old help file (*.hlp) can not be opened on Windows 10, even if replacing "winhlp32.exe" (exsiting in Windows 10) with the "winhlp32.exe" of Windows XP.
Last edited by derekimo; 02 Sep 2015 at 00:58.
Can someone compare the winhlp32 EXE from a fully updated Windows 8.1 computer with the to the ones provided in this thread? Thx.
Comparison between the "winhlp32.exe" for Windows 8.1 Eng x64 (*1) and the "winhlp32.exe" for Windows XP Eng x64 (*2):
(*1) = The "winhlp32.exe" for Windows 8.1 Eng x64, which can properly open an old help file (*.hlp) on Windows 8.1 Eng x64. Inother words, this "winhlp32.exe" is as same as that provided by "Windows8.1-KB917607-x64.msu."
(*2) = The "winhlp32.exe" for Windows XP(SP2) Eng x64, which can open an old help file (*.hlp) on Windows XP(SP2) Eng x64. This "winhlp32.exe" is used as the "winhlp32.exe" which is replaced with the original "winhlp32.exe" in Windows 10 Eng x64.
Please refer to the following picture.
Note:
These two "winhlp32.exe" files have completely different file-structure, when comparing them by using a certain binary editor. Therefore, showing the difference between two files (as a binary list) is meaningless.
I upgraded just a couple of days ago, successfully solved problems with LAN printer and DVD drives not showing up. Now I came across the fact that the older (hlp) files are handled by new winhlp32.exe that is merely a stub that opens a web site explaining that you are trying the impossible :-(. Hmm, not quite sure what MICROSOFT policy exactly is, but thinking that people stop using legacy apps just because MICROSOFT wants to push the new Windows version that is not compatible is naive. The old (win XP, win 7) winhlp32.exe version is still present in c:\windows.old\windows folder, but cannot be associated with HLP files (why?) and copying it to different location and running it gives the error 9009 (why?). For the time being I wrote myself a simple windows console application that launches the old winhlp32.exe located in c:\windows.old\windows folder and passes it the path to the HLP file as the 1st argument. I associated HLP files with my console application. I hope that MICROSOFT is going to do something with this problem soon or I shall make a fortune with this app