MSCOMCTL.OCX for 64 bit Windows 7 & Vista


 

MSCOMCTL.OCX

 

MSCOMCTL.OCX  is a windows file needed by many old application in order to control serial communications through the RS32 port. This OCX will not simply register as most of know, by placing it in the system32 folder and typing the command “regsvr32 MSCOMCTL.OCX”. With newer 64 bit systems it is a bit tricky. Here is how to do it

1. download the file here

2. Copy it to c:\\windows\\syswow64

3. type the following “Run” command :   “regsvr32 c:\\windows\\syswow64\\MSCOMCTL.OCX” and yes, you have to type the full path to the file, not just the file name.

4. That’s it, it should work now.

HyperTerminal For windows 7, How to get it

Windows 7 has removed our good old HyperTerminal, an utility used to as a terminal console over telephone or serial RS32 links. These all may seem like old features that need to be taken out and shot. But believe me, real geeks and communication professionals would love to have HyperTerminal back to windows.

Hyperterminal is not even available through the add remove windows features like telnet. To get it back you will have to follow one of these plans:

How to get HyperTerminal in Windows 7?

Option 1: copy hyperterminal executables from an XP machine to your Program Files > Windows NT these files are: hypertrm.exe and htrn_jis.dll, if you don’t have an XP machine near you, you may follow this link to get them http://www.filefactory.com/file/c0b15cf/n/Hyperterminal.rar

 

Option 2. Forget HyperTerminal, and start using PuTTY. PuTTy, is much better than Hyperterminal, it offers SSH and Telnet as well. And it is free.

That’s it, now you have your Hyperterminal features back.

comdlg32.ocx for 64 bit Windows 7 & Vista

comdlg32.ocx is a file required by many old application in order to display dialogs . This OCX will not register as most of know, by putting in in the system32 folder and typing the command “regsvr32 comdlg32.ocx”. With newer 64 bit systems it is a bit tricky. Here is how to do it

1. download the file here

2. Copy it to c:\windows\syswow64

3. type the following “Run” command “CMD” then right click the command prompt search result and hit “run as administrator”, in the command prompt type:                            “regsvr32 c:\windows\syswow64\comdlg32.ocx” and yes, you must type the full path to the file, not just the name.

4. That’s it it should work now.

+1 if this helped you.

comctl32.OCX for 64 bit Windows 7 & Vista

comctl32.ocx is a file required by many old application in order to work with serial ports . This OCX will not register as most of know, by putting in in the system32 folder and typing the command “regsvr32 comctl32.OCX”. With newer 64 bit systems it is a bit tricky. Here is how to do it

1. download the file here

2. Copy it to c:\windows\syswow64

3. type the following “Run” command “CMD” then right click the command prompt search result and hit “run as administrator”, in the command prompt type:                            “regsvr32 c:\windows\syswow64\comctl32.OCX” and yes, you must type the full path to the file, not just the name.

4. That’s it it should work now.

Enabling TELNET and SSH in windows 7

Windows 7 doesn’t support TELNET by default. and no windows version ever supported ssh.

For telnet there is an easy way to enable it, and it is by going to Start, Control Panel, Programs And Features, Turn Windows features on or off
and select the Telnet Client.

But here we are going to do a neat trick to enable both telnet and ssh using the amazing  PuTTY instead.

1. download PuTTY from here

2. copy putty.exe to your system32 folder.

3. inside system32. create two new files telnet.bat and ssh.bat

4. Edit these two file at follows :

telnet.bat:

putty.exe -telnet %1

ssh.bat:

putty.exe -ssh %1

save everything and close.

Now you can run telnet or SSH from the command prompt or even the start menu search box as follows:

c:\> tenet 192.168.1.5

c:\> ssh 192.168.1.5

as if you were using a good old Linux terminal.

If you want to know how to make your command prompt look like this check this post

MSINET.OCX for 64 bit Windows 7 & Vista

[ad#square]
MSINET.OCX is a file required by many old application in order to parse HTML pages . This OCX will not register as most of know, by putting in in the system32 folder and typing the command “regsvr32 MSINET.OCX”. With newer 64 bit systems it is a bit tricky. Here is how to do it

1. download the file here

2. Copy it to c:\windows\syswow64

3. type the following “Run” command “CMD” then right click the command prompt search result and hit “run as administrator”, in the command prompt type:                            “regsvr32 c:\windows\syswow64\MSINET.OCX” and yes, you must type the full path to the file, not just the name.

4. That’s it it should work now.

RICHTX32.OCX – 64 bit Windows 7 & Vista

RICHTX32.OCX is a file required by many old application in order to show rich text boxes . This OCX will not register as most of know, by putting in in the system32 folder and typing the command “regsvr32 RICHTX32.OCX”. With newer 64 bit systems it is a bit tricky. Here is how to do it

 

 

 

 

 

Downloading and installing  RICHTX32.OCX on Windows 64bit

1. download the file here

2. Copy it to c:/\windows/\syswow64

3. type the following “Run” command “CMD” then right click the command propmte search result and hit “run as administrator”, in the command prompt type:                            “regsvr32 c:/\windows/\syswow64/\RICHTX32.OCX” and yes, you must type the full path to the file, not just the name.

4. That’s  all you have to do, your ocx  should work now.

richtx32.ocx image

OPENSKY Connection Manager on Windows 7

Are you unable to connect to your Opensky satellite internet account on windows 7? the same thing happened to me, even though I was using the “Windows 7” version of the application.

Anyway, I found a way around to make it work.

1. insure that your satellite card is running, set on the right transponder, and the right PIDs are on.

2. Download and install the OPENSKY Connection Manager, enter all settings correctly and choose direct access. this is supposed to be it, but you will be unable to connect yet.

3. click the network icon near the clock on the task-bar of windows 7, then right click, properties, the OPENSKY direct access.

4. on the security tab select “Layer 2 tunneling protocol”

5.save everything, then try to connect, it should work!!

If you get connected but for some reason unable to browse, then the problem can be one of the following:

1.your satellite card tuner is off, not on the right transponder,  not on the right pids, or does not have a signal at all.

2. For some Magic reason, sometimes on windows 7, your cards MAC address will read as zeros, if that is your case, you must manually set your subscription MAC address  through the device manager, ask me if you need help doing that .

Hope this works for you. but always remember, satellite internet IS NOT SAFE, read about that here

Internet, files and printers sharing on a windows 7 computer

Windows 7 has brought a change in the Windows handles Internet sharing ( internet sharing is one computer is connected to the internet and the rest of the computers on the LAN connects to it to get online).
For windows XP and Vista, internet sharing is achieved by setting the IP of the computer’s network card to 192.168.0.1 then enabling a DHCP internal windows service to provide IP addresses to the rest of the computers. Windows 7 uses the following IP address instead : 192.168.137.1. I don’t know what’s so cool about 137 other than the fact that it is not zero, which is the sub network used by many network admins and that could create conflicts when a used starts internet sharing.

to get Windows 7 to share an Internet connection, just right click the modem/ network card that is connected to the internet select properties then sharing, enable sharing to your LAN, that’s it.

Things get more complicated if you try to share a windows 7 internet connection through a wireless access point. Usually access points have a dedicated network port to be connected to the internet source (that is the case with D-link). if you just plug that into your computer it will not work, not only because of the fact that you will need to use a crossover (needs testing to confirm) to switch the send\receive lines. but also you will be unable to get file and printer sharing normally from the server computer. because the IP that your computer is proving the access point will be considered a WAN IP, and the access point will not be able to DHCP the client computers to the same IP range as the WAN IP.

The solution here is to place a switch between the wireless AP and the computer, with DHCP off. the AP will get the wan IP from your computer, something like 192.168.137.100, then with the AP’s DHCP it will assign IPs in the range of 192.168.1.xxx to other wireless clients.

to get file and printer sharing you will need to directly connect to the server computers IP, as it will not appear as a regular computer in your network.

to create a shortcut to the server’s shared files :
right click your desktop, select new then click shortcut
for the address write :
\\192.168.137.1

If you have file sharing enabled through your windows 7, you will be able to access shared files and printers.

I also have another approach that is not that catholic, and that is to place a normal network cable between the AP’s LAN ports and the switch. this will create an irregularity where the AP tries to assign an IP to the server, and the server already has an IP and that is the WAN IP of the AP, if you are lucky, your server will appear as a regular computer with other wireless clients, but this is a very unstable method and I wouldn’t recommend it.

I also noticed that file sharing speed through this method is not that great, I will look some more into that.

Any Ideas, thoughts or discoveries? please share 🙂

MSWINSCK.OCX for 64 bit Windows 7 & Vista

 

mswinsck.ocx

[ad#square]

MSWINSCK.OCX  is a file required by many old application in order to listen to a certain port or just allow. network connections. This OCX will not register as most of know, by putting in in the system32 folder and typing the command “regsvr32 MSWINSCK.OCX”. With newer 64 bit systems it is a bit tricky. Here is how to do it

1. download the file here

2. Copy it to c:\\windows\\syswow64

3. type the following “Run” command :   “regsvr32 c:\\windows\\syswow64\\MSWINSCK.OCX” and yes, you must type the full path to the file, not just the name.

4. That’s it it should work now.