jjlink
Well-known member
garygid said:Win7 also has a Windows\System32 folder.
I have not yet investigated how to do this in Win7,
but maybe you put the new MSCOMM32.OCX in the
System32 folder, or perhaps replace the existing file
in the other folder. Or, maybe the file you see is
an entirely new compilation. Perhaps compare byte
length and the file dates.
I would suggest doing a Byte-comparison of these files.
The original OCX file has the bytes 3D 10 00 in exactly
one place, and the 10 ihex s the max port number.
I replaced the hex 10 with hex 63 (99 decimal).
Please let us know what you discover.
Ok, the file on the E-drive is the original file from my system backup, the file on the C-Drive is the once that came with CanDo:
=============================
First file name: E:\Windows\SysWOW64\MSCOMM32.OCX
Second file name: c:\Windows\SysWOW64\MSCOMM32.OCX
1 : 1 Byte(s) diff
103743 Byte(s) match
103744 : 103744 Byte(s) total
=============================
MSCOMM32-OCX by JJLINK, on Flickr
So I am using the OCX file you sent now.
My understanding is 32bit apps on a 64bit Windows install would belong in \Windows\SysWOW64\ if its a 64bit app it would go in \Windows\System32\.
This was interesting:
http://social.msdn.microsoft.com/Forums/en/vbgeneral/thread/1f00d6cc-00a9-4ca0-9698-535e2487af31
"Also take a look at http://www.comm32.com which is an MSComm32 compatible OCX which has less hangups with Windows7."