|
|
Post by Chuck Elliot on Nov 6, 2014 8:17:52 GMT -5
Let me get through this first implementation which is written in Visual Basic 6. IMO it is the language that MS should never have killed in favor of VB.NET. It's very fast to prototype and test!
I've found many holes and missing things in the protocol. Most I can work around. Some I can't. I will explore other methods in the future.
|
|
|
|
Post by ÈlTwo on Nov 6, 2014 8:40:19 GMT -5
Great work, Chuck. Thanks for picking up the ball and running with it!
|
|
|
|
Post by gregd on Nov 6, 2014 12:00:08 GMT -5
Let me get through this first implementation which is written in Visual Basic 6. IMO it is the language that MS should never have killed in favor of VB.NET. It's very fast to prototype and test! I'm a Java fan myself, as I use both Linux and Windows. But no language is fast unless you are already up-to-speed using it. Cool idea. |
|
|
|
Post by Chuck Elliot on Nov 8, 2014 14:59:43 GMT -5
Almost done! Doing testing and some cosmetic improvements.  |
|
|
|
Post by LuisV on Nov 8, 2014 16:03:35 GMT -5
Nice Chuck! Can't wait to try it out.  |
|
|
|
Post by Chuck Elliot on Nov 9, 2014 8:18:42 GMT -5
Could I ask a favor of some of you guys?
Could you see if these files are on your system:
MSWINSCK.ocx
msvbvm60.dll
These should be located in either:
C:\Windows\SysWOW64 (64 bit windows)
or
C:\Windows\system32 (32 bit windows)
This will be the difference between my having to create an installation package or just distributing the programs exe file.
I believe Windows 7 and up includes these files.
Also let me know your windows version.
|
|
|
|
Post by jblnut on Nov 9, 2014 8:59:37 GMT -5
Hi Chuck,
looking good.
I have msvbvm60.dll in specified location but can't locate the other file (Win7/64)
|
|
hemster
Global Moderator 
Particle Manufacturer
...still listening... still watching
Posts: 51,951
|
Post by hemster on Nov 9, 2014 9:29:38 GMT -5
Chuck, I have Windows 7 64-bit and have both MSWINSCK.ocx and msvbvm60.dll in C:\Windows\SysWOW64. jblnut, are you sure that you don't have MSWINSCK.ocx? ("MSWINSCK" displays in upper case). |
|
|
|
Post by geebo on Nov 9, 2014 10:16:11 GMT -5
Could I ask a favor of some of you guys? Could you see if these files are on your system: MSWINSCK.ocx msvbvm60.dll These should be located in either: C:\Windows\SysWOW64 (64 bit windows) or C:\Windows\system32 (32 bit windows) This will be the difference between my having to create an installation package or just distributing the programs exe file. I believe Windows 7 and up includes these files. Also let me know your windows version. Chuck, My Windows 8 64 bit system has msvbvm60.dll but does not have MSWINSCK.ocx |
|
|
|
Post by ÈlTwo on Nov 9, 2014 11:49:42 GMT -5
Win7 64 bit:
msvbvm60.dll File version 6.0.98.15
mswinsck.ocx File Version 6.0.89.88
|
|
|
|
Post by ÈlTwo on Nov 9, 2014 12:37:36 GMT -5
Chuck,
mswinsck.ocx is not included with Win8, it would have to be downloaded and registered.
Win8 users will have to open a command prompt and run as administrator, and then enter the command "typeregsvr32 c:\windows\syswow64\MSWINSCK.OCX." It's case sensitive so if your file is lowercase
then you'd have to type "typeregsvr32 c:\windows\syswow64\mswinsck.ocx" at the prompt.
I would recommend a batch file, but it has to have administrator privileges.
|
|
|
|
Post by Chuck Elliot on Nov 9, 2014 12:40:56 GMT -5
Chuck, mswinsck.ocx is not included with Win8, it would have to be downloaded and registered. Win8 users will have to open a command prompt and run as administrator, and then enter the command "typeregsvr32 c:\windows\syswow64\MSWINSCK.OCX." It's case sensitive so if your file is lowercase then you'd have to type "typeregsvr32 c:\windows\syswow64\mswinsck.ocx" at the prompt. I would recommend a batch file, but it has to have administrator privileges. I'm writing a package installer that will take care of all........... |
|
|
|
Post by rogersch on Nov 9, 2014 13:50:12 GMT -5
Hi Chuck,
I've got Windows 7 64 bit version.
msvbvm60.dll File version 6.0.98.15 is available
The other file is not present.
|
|
|
|
Post by LuisV on Nov 9, 2014 13:56:17 GMT -5
I'm writing a package installer that will take care of all........... Cool as mswinsck.ocx is missing from both my XP and Windows 7 64Bit VMs. |
|
|
|
Post by Axis on Nov 9, 2014 14:05:55 GMT -5
This is why I like you Chuck. Not just talk but do ! Press on with pride Dude !
|
|
riscy
Minor Hero
Posts: 28
|
Post by riscy on Nov 9, 2014 14:09:30 GMT -5
Wow - glad you/they have the mojo to lay hands on this!! I'm a little hacked off to see the July date on this document... I've been asking tech support for this protocol description for months with nothing but blank stares and shrugs for a response. I'll play around and see what I can do from a Roomie Remote perspective. Maybe play with it on a Mac, as well. Either way, thanks for the post and the hard work!! |
|
|
|
Post by DellaDog on Nov 9, 2014 15:11:59 GMT -5
Chuck,
If you'd like I could recompile with VS2013 which would require no additional distro files - framework already installed on Win 8 computers.
Also this thread might do better on the processor board - much more traffic/exposure.
I stumbled into this interesting thread.
|
|
|
|
Post by Chuck Elliot on Nov 9, 2014 15:23:18 GMT -5
Chuck, If you'd like I could recompile with VS2013 which would require no additional distro files - framework already installed on Win 8 computers. Also this thread might do better on the processor board - much more traffic/exposure. I stumbled into this interesting thread. VS2013 does not include VB6. VB.NET is far different from VB6. I'm using NSIS which is a great package installer creator. App is out to a few "beta" people. It should be up shortly depending on what turns up! |
|
|
|
Post by DellaDog on Nov 9, 2014 15:35:15 GMT -5
Chuck, If you'd like I could recompile with VS2013 which would require no additional distro files - framework already installed on Win 8 computers. Also this thread might do better on the processor board - much more traffic/exposure. I stumbled into this interesting thread. VS2013 does not include VB6. VB.NET is far different from VB6. I'm using NSIS which is a great package installer creator. App is out to a few "beta" people. It should be up shortly depending on what turns up! I realize that Chuck. Point being I would change as needed. I'd offer the source up to others - just didn't want to have to start from scratch. It's light years ahead of VB6, BTW. |
|
|
|
Post by Chuck Elliot on Nov 9, 2014 15:45:02 GMT -5
VS2013 does not include VB6. VB.NET is far different from VB6. I'm using NSIS which is a great package installer creator. App is out to a few "beta" people. It should be up shortly depending on what turns up! I realize that Chuck. Point being I would change as needed. I'd offer the source up to others - just didn't want to have to start from scratch. It's light years ahead of VB6, BTW. Yes I understand. But, as I said previously, I find VB6 faster to prototype. I have had little problem making VB6 do anything I want. If VB6 doesn't have it, I just go to the WINAPI. This comes from years of supporting VB6 legacy programs. I plan to re-write the final app in C#. |
|
