Register RichTx32.Ocx in Windows 7 64 bit - windows

I am trying to register RichTx32.Ocx for an application I am working on in Access 2010 (File Format 2003 mdb). I have been updated to Windows 7 64 bit (from Windows XP SP3 32 bit) and can't get the ActiveX OCX to register.
I have put the file in the system32 folder and get the following message: "The module "RICHTX32.OCX" may not compatible with the version of Windows that you're running. Check if the module is compatible with an x86 (32-bit) or x64 (64-bit) version of regsvr32.exe"
When I put the file in the SysWOW64 folder and run regsvr32 to that location, I get the following error message: "The moduile "C:\Windows\SysWOW64\RICHTX32.OCX" was loaded but the call to DllRegisterServer failed with error code 0x8002801c."

There are three obvious possibilities for this problem:
You are running the 64 bit version of regsvr32.
You have UAC enabled and when the OCX self-registers, its attempts to write to HKLM fail.
The OCX does not run under Windows 7.
I think the latter is unlikely and anyway I can't do much to help!
To get around issues 1&2 I do the following:
Open a Command Prompt as administrator (right click on a shortcut to the Command Prompt and select "Run as Administrator").
Run this command: C:\Windows\SysWOW64\regsvr32 C:\Windows\SysWOW64\RICHTX32.OCX

Did the following and seems to have worked. Aperently, I had to run CMD in Administrator Mode, even though I am a local administrator.
(1) First, you must perform this on EVERY computer that has 2010
(2) Copy RichTx32.ocx to the following directory: C:\Windows\SysWoW64
(3) Click the Windows 7 Start Button and in the Search area, type "command"
(4) The search will bring up a number of items, including "Command Prompt" at the top
(5) Right click the "Command Prompt" banner, and select "Run as Administrator"
(6) At the command prompt, enter: %systemroot%\SysWoW64\regsvr32.exe RichTx32.ocx
(7) This should successfully register your OCX.
Thanks to:
Rich Locus Logicwurks, LLC www.logicwurks.com

my english not good,so i hope you understand.
Ran that command C:\Windows\SysWOW64\regsvr32 C:\Windows\SysWOW64\RICHTX32.OCX and got the error: "The module "C:\Windows\SysWOW64\RICKTX32.OCX" was loaded but the call to DllRegisterServer failed with error code 0x8002801c." – Rick Jun 13 '11 at 20:18
ok in windows7 you need do this "user account control settings -----than "Never notice
"
---than reset ,
•Run this command: C:\Windows\SysWOW64\regsvr32 C:\Windows\SysWOW64\RICHTX32.OCX
it's gone be ok!

Related

Compiled Visual Basic Application gets Runtime Error 52 in Windows 8

The application that I compiled via Visual Basic 6 can run on my Windows XP computer. But when I execute the same executable on my other computer that runs Windows 8, I always get Runtime Error 52-Bad File name or number as soon as I launch it. I can't run the program even if there is no "Shell command" in that program which leads to a "Bad file name" error.
I used "Package and Deployment wizard" for the packaging process.
And also I registered the needed DLL's on the Windows 8 PC manually via the regsvr32 command line utility.
I also cleaned the whole registry via a registry cleaner (Wise Registry Cleaner). I used compatibility mode for Windows XP but nothing solved the problem.
Additional informations:
XP Version - SP 2
Windows 8 Version-8.1
VB - VB 6.0
Assuming that your code is
If Dir("C:/file.txt") = "" Then...
Change it to a backslash ("\")
After some research I found the answer for the problem. That was not a problem in the coding; it was ALL about windows 8 compatibility.
Go to the “Compatibility” tab of the properties window of the file and select “Windows XP SP2” under the “Compatibility mode”. That’s all
Windows 8 no longer allows you to write programmatically in the root of drive C:\ (and in many others 'system' folders like Program Files, Windows, System32, ...).
Try to use a sub-folder.

gflags dialog box doesn't open

I am currently trying to debug a memory leak in one of my applications (yeah, that crap again...), and trying to set gflags settings, but the dialog won't open up. I installed the Windows 10 SDK (I am on Windows 7 x64), but it said it works on Win7 as well in the description, so why can I not use it at all?
If I start gflags from command line, nothing at all happens, no error, no feedback, nothing.
Anybody an idea as to what might be happening on my system?
According to http://www.osronline.com/showThread.CFM?link=278979, you'll need to wait for a new version (that apparently doesn't exist as of Jan 2017) that contains gflagsui.dll
Known issue that will be fixed in an upcoming release. You should be able to use
the version of GFlags that is installed with any of the 8 or 8.1 kits, or copy
the gflagsui.dll from those.
You can also use GFlags via the command-line:
https://msdn.microsoft.com/en-us/library/windows/hardware/ff549566(v=vs.85).aspx
Try opening an elevated command prompt.
cd to install folder
(C:\Program Files (x86)\Windows Kits\10\Debuggers\x64)
Type gflags /?
It will probably tell you you only get the dialog box if gflagsui.dll is available, but there is no info how to get it.
(if you don't use an elevated command prompt you'll get UAC, then you'll see a console window open and quickly exit)
So for now you'll need to use the command line...

VB6 Legacy Code can't "Call Shell"

I am working on some legacy VB6 code and I am having my program break with this message:
and it then highlights this code:
I know that the specified locations exist per these screenshots:
I am running this Visual Studio 6.0 on a 64-bit Windows 7 machine. How can I make the program see shell?
command.com does not exist on 64 bit windows.
Try using C:\Windows\SysWOW64\cmd.exe instead. C:\Windows\SysWOW64 is a folder giving you backwards compatibility stuff for 32 bit.
But see the comment below (taken from Euro Micelli).
Really you should use %SYSTEMROOT\System32\cmd.exe instead. First, Windows is not always installed in C:\Windows; you should let the system figure that out. Second, using System32 is always correct for a 32-bit application: when running on Win32, it is the correct folder; when running on Win64, Windows will map %SYSTEMROOT%\System32 to %SYSTEMROOT%\SysWOW64
I use vb6 and windows 7.
I've done the same thing as you but I put the dos command in a bat file.
Login.bat
NET USE W: \\10.48.10.8\e$
Then in the code
Shell ("c:\login.bat")
The vb command is not correct for the OS that you are running. You need to check that that drive is not already mapped, and remove the command.com /c from the command that you are trying to execute.

App launches manually OK, but when launched from Installer it fails (error:an .OCX as Unregistered) Why?

Our installer (old version of the WISE installer) uses the ShellExecute to launch a program (MyApp.exe) it has installed. But when we do that Windows 7 balks and says that Richtx32.ocx is not registered or is missing a component.
-If I manually launch MyApp.exe from Explorer, it runs just fine.
-If I run a .Bat file that launches MyApp.exe, it runs just fine.
-If I move my installer to the same directory that MyApp.exe is in an run it from there I get the same error.
Windows 7, 32 bit.
An older RichTx32.ocx is installed in the \Windows\System directory.
In testing on VMware (Windows 7, 32 bit, without RichTxt32.ocx installed) this problem does NOT happen.
The RichTx32.ocx I install happens to have the o capitalized (.Ocx) and then the system reports the error it refers to my OCX (RichTx32.Ocx) or one of it's components being unregistered.
One thought I just had is that the installer may be running as the Admin user and maybe when it launches another app that app doesn't run as the same user, but if you launch from a .bat file it does?
That apper be an about access control and administrative privileges
Try changed
ShellExecute(NULL, "open", szGadgetSource, NULL, NULL, SW_SHOWNORMAL);
for
ShellExecute(NULL, NULL, szGadgetSource, NULL, NULL, SW_SHOWNORMAL);
or
turned out to access control
try compile it as an installer, not just and exe.., then install it in your system.., an installer package, not just an compiled exe file. some active controls/dll/active x will not be copied if you just save it as an exe file
After installing the RICHTX32.OCX into system directory.
1) try to run this code in the RUN regsvr32.exe c:\windows\system32\RICHTX32.OCX or drag the file to REGSVR32.EXE.
2) right click your EXE application, goto properties, compatibility, then check Run this program .... in the compatibility mode and privileged level.
hope that helps..,

ActiveMQ install issue

I am running win7 professional 64-bit. I have already installed java, and am trying to install ActiveMQ. The install worked perfectly on a Windows Server 2003 machine but now it is giving me issues on my win7 machine. I download ActiveMQ 5.3.2 extract the files and then try to run the installservice.bat file as administrator and it gives me the following error in command prompt: '"wrapper.exe"' is not recognized as an internal or external command, operable program or batch file.
I had the same issue when using Windows Explorer and right clicking on the InstallService.bat file and selecting "Run As Administrator".
However, this worked for me (without having to change my user control settings):
1) Open a command prompt (right clicking first with "run as administrator").
2) Then navigate to the folder where your batch file is and simply type InstallService.bat.
Ok I feel a little stupid answering my own question but here it goes. Turn off the user control settings in the control panel
I had the same issue with apache-activemq-5.6.0 and solved it this way:
Open cmd.exe as admin (click on Start, type in cmd, right click on the "cmd" program, and choose Run as administrator)
In the cmd.exe window, navigate to your apache-activemq-5.X.X root dir (which contains bin, conf, data, docs, ...)
From there, navigate to bin\win64
Your commmand prompt should show something like:
...\apache-activemq-5.6.0\bin\win64>
Still in the cmd.exe, run InstellService.bat
It does not work if you run something like win64\InstellService.bat while being in bin. You have to actually navigate to bin\win64 first.
The in case you are installing in win 64 bit 2012 Server too, run InstallService.bat under sys32.
Its little confusing but it works.

Resources