Fallen at the first hurdle: after downloading apup.zip and unpacking it, running autopatcher gives this error message:
Yikes.
What Autopatcher was trying to do: error occurred while AP was trying to get commandline arguments
Where: mdlInitialization.Main()
Error Code: 0x174: Failed to load control 'RichTextBox' from RICHTX32.ocx ....
Anyone knows about this? My system is an AMD Athlon 64 X2 on a Gigabyte M55plus motherboard, nothing special really
Error: 0x174: Failed to load control 'RichTextBox' from RICHTX32.OCX
Started by resac, Sep 13 2008 06:13 PM
4 replies to this topic
#1
Posted 13 September 2008 - 06:13 PM
#2
Posted 13 September 2008 - 07:44 PM
Hi resac
Can you please give some more information. This is not a hardware problem, but a software problem.
I assume you must have run APUP after downloading it, otherwise how did you get AutoPatcher.exe?
apup.exe itself does not use RICHTX32.OCX.
What version of Windows are you running? Are you running as an Administrator?
--
Can you please give some more information. This is not a hardware problem, but a software problem.
I assume you must have run APUP after downloading it, otherwise how did you get AutoPatcher.exe?
apup.exe itself does not use RICHTX32.OCX.
What version of Windows are you running? Are you running as an Administrator?
--
#3
Posted 13 September 2008 - 10:29 PM
James, on Sep 13 2008, 08:44 PM, said:
Hi resac
Can you please give some more information. This is not a hardware problem, but a software problem.
I assume you must have run APUP after downloading it, otherwise how did you get AutoPatcher.exe?
apup.exe itself does not use RICHTX32.OCX.
What version of Windows are you running? Are you running as an Administrator?
--
Can you please give some more information. This is not a hardware problem, but a software problem.
I assume you must have run APUP after downloading it, otherwise how did you get AutoPatcher.exe?
apup.exe itself does not use RICHTX32.OCX.
What version of Windows are you running? Are you running as an Administrator?
--
Thanks for your message.
I am running Windows XP SP2 on my AMD/Gigabyte hardware, with 1.5 GB memory. As usual, I am running with a computer administrator account.
I downloaded apup.zip and unzipped it in a temporary folder. It expands into autopatcher.exe and a number of folders ( apup_bin, bin, tools, translations and win9znt). The file RICHTX32.ocx is in the folder: bin. On the first run of autopatcher.exe, the message as quoted above, is the first and only result ; OK closes the box and the program.
I would agree that this is alikely to be a software rather than hardware problem, although I wonder could if be something to do with my graphics card (a card with an Nvidia Geforce 7200 GS chip)?
#4
Posted 15 September 2008 - 08:14 AM
Thanks for the further information. It looks like you have an ActiveX file conflict. Also (as I said last time) you cannot have all those folders by just downloading and installing APUP. Either you ran it, or you have added APUP to an older version of AutoPatcher.
To resolve your problem you will need to unregister the richtx32.ocx file, delete it, and update both the files apup.exe and autopatcher.exe.
Please follow the steps below to do this:
1. Open a command prompt by selecting, Start > Run..., typing "cmd" (without the quotes) and clicking OK;
2. Change directories to the directory in which the richtx32.ocx resides (on Windows XP) by entering the following command:
cd C:\WINDOWS\system32
3. Unregister the file richtx32.ocx by entering the following command:
regsvr32 /u richtx32.ocx
4. Once the "DllUnregisterServer in richtx32.ocx succeeded" message appears, click OK
5. Delete the the existing richtx32.ocx by entering the following command:
del richtx32.ocx
6. Close the command prompt
7. Run the file apup.exe to update just itself and autopatcher.exe.
[indent]First, make sure you have just the first two items selected:
AutoPatcher Updater 1.0.5
AutoPatcher Engine 5.6.81
Second, make sure that nothing else is selected.
Third, click Next[/indent]
When APUP has finished, check that autopatcher now works and then run apup again to bring it fully up-to-date
--
To resolve your problem you will need to unregister the richtx32.ocx file, delete it, and update both the files apup.exe and autopatcher.exe.
Please follow the steps below to do this:
1. Open a command prompt by selecting, Start > Run..., typing "cmd" (without the quotes) and clicking OK;
2. Change directories to the directory in which the richtx32.ocx resides (on Windows XP) by entering the following command:
cd C:\WINDOWS\system32
3. Unregister the file richtx32.ocx by entering the following command:
regsvr32 /u richtx32.ocx
4. Once the "DllUnregisterServer in richtx32.ocx succeeded" message appears, click OK
5. Delete the the existing richtx32.ocx by entering the following command:
del richtx32.ocx
6. Close the command prompt
7. Run the file apup.exe to update just itself and autopatcher.exe.
[indent]First, make sure you have just the first two items selected:
AutoPatcher Updater 1.0.5
AutoPatcher Engine 5.6.81
Second, make sure that nothing else is selected.
Third, click Next[/indent]
When APUP has finished, check that autopatcher now works and then run apup again to bring it fully up-to-date
--
#5
Posted 15 September 2008 - 10:57 PM
Thanks James - I followed your instructions and the AP installed and ran - even though the AP first updates ended in a error:
Application Error: permission denied in prjUpdate.mdScriptparser.executeAction at line 252
This did not stop the thing from working OK, and after updating the AP for XP SP2 which I am running, I can now download the required updates.
Thanks for your help, and my compliments to your perspicacity in diagnosis. Cheers!
By the way, this was obviously not a bug, and maybe I should not have posted it under bug reports; it must have been my own error during installation. Sorry.
Application Error: permission denied in prjUpdate.mdScriptparser.executeAction at line 252
This did not stop the thing from working OK, and after updating the AP for XP SP2 which I am running, I can now download the required updates.
Thanks for your help, and my compliments to your perspicacity in diagnosis. Cheers!
By the way, this was obviously not a bug, and maybe I should not have posted it under bug reports; it must have been my own error during installation. Sorry.
Edited by resac, 15 September 2008 - 11:13 PM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











