Edge and Windows Vista
Edge and Windows Vista
When tring to load my edge onto my laptop with windows vista it all goes smoothly but when i execute the project i get the following error:
"component 'mscomm32.ocx' or one of its dependencies not correctly registered: a file is missing or invalid"
someone help please
"component 'mscomm32.ocx' or one of its dependencies not correctly registered: a file is missing or invalid"
someone help please
Originally Posted by polpilot
When tring to load my edge onto my laptop with windows vista it all goes smoothly but when i execute the project i get the following error:
"component 'mscomm32.ocx' or one of its dependencies not correctly registered: a file is missing or invalid"
someone help please
"component 'mscomm32.ocx' or one of its dependencies not correctly registered: a file is missing or invalid"
someone help please
Google that OCX, drop it into c:\windows\system32
At a command prompt run regsvr32 mscomm32.ocx
If that doesn't do it, wait fer Bill to mosey on over to help ya
Last edited by MGDfan; Oct 21, 2007 at 09:34 PM.
Originally Posted by MGDfan
You installed the Edge drivers correctly, right?
Google that OCX, drop it into c:\windows\system32
at a command prompt run regsvr32 mscomm32.ocx
Google that OCX, drop it into c:\windows\system32
at a command prompt run regsvr32 mscomm32.ocx
Originally Posted by polpilot
ive done that it shows fine. i used the cd that came with the edge and it updated then i connect the unit it comes up with the error.
Perhaps try unregistering that control then re-registering ( it's the /U switch)...
See (4th post down): http://forums.microsoft.com/MSDN/Sho...48335&SiteID=1
Also see: http://msdn2.microsoft.com/en-us/vbrun/ms788708.aspx
This OCX isn't shipped with Vista; MS says the app vendor needs to include it ... that would mean a call to Edge tech support - is there a Vista support statement issued by Edge Products? I know SCT is in a similar predicament with workarounds ...
BTW - Running as a user or as an Admin?
Last edited by MGDfan; Oct 21, 2007 at 10:17 PM. Reason: freakin' typos !!!
Originally Posted by MGDfan
Perhaps try unregistering that control then re-registering ( it's the /U switch)...
To unregister, you would run "regsvr32 /u c:\windows\system32\mscomm32.ocx" from the RUN dialog.
You might have to excuse my ignorance, as I refuse to give Microsoft any more money because they feel the need to increase their revenue by upgrading operating systems yet *AGAIN* to VISTA. Well, my XP works just fine, thankyouverymuch.
Anyway, I am under the assumption that there are still some basic configuration similarities, although I could be way off base. I am sure if you do a google for Vista and MSCOM32.OCX, something is bound to turn up. I did find this... http://forums.microsoft.com/MSDN/Sho...11412&SiteID=1
In any event, I'll get Edge's official standpoint tomorrow and post something here.
Good luck.
Bill
On EDIT:
According to a thread in a TurboTax Forum, Vista is having problems with how it handles VB controls (OCX files). Some have tried the "Run as Admin" fix and have still had some issues. However, one solution that seems to work is to actually UNREGISTER the stupid things controls. How's that for bass-ackwards! So, try the unregister command at the top of this post and it *SHOULD* get you going.
You might have to excuse my ignorance, as I refuse to give Microsoft any more money because they feel the need to increase their revenue by upgrading operating systems yet *AGAIN* to VISTA. Well, my XP works just fine, thankyouverymuch.
Anyway, I am under the assumption that there are still some basic configuration similarities, although I could be way off base. I am sure if you do a google for Vista and MSCOM32.OCX, something is bound to turn up. I did find this... http://forums.microsoft.com/MSDN/Sho...11412&SiteID=1
In any event, I'll get Edge's official standpoint tomorrow and post something here.
Good luck.
Bill
On EDIT:
According to a thread in a TurboTax Forum, Vista is having problems with how it handles VB controls (OCX files). Some have tried the "Run as Admin" fix and have still had some issues. However, one solution that seems to work is to actually UNREGISTER the stupid things controls. How's that for bass-ackwards! So, try the unregister command at the top of this post and it *SHOULD* get you going.
Last edited by ASEMechanic; Oct 21, 2007 at 10:23 PM. Reason: Added relevant link.
Trending Topics
Originally Posted by ASEMechanic
To unregister, you would run "regsvr32 /u c:\windows\system32\mscomm32.ocx" from the RUN dialog.
You might have to excuse my ignorance, as I refuse to give Microsoft any more money because they feel the need to increase their revenue by upgrading operating systems yet *AGAIN* to VISTA. Well, my XP works just fine, thankyouverymuch.
Anyway, I am under the assumption that there are still some basic configuration similarities, although I could be way off base. I am sure if you do a google for Vista and MSCOM32.OCX, something is bound to turn up. I did find this... http://forums.microsoft.com/MSDN/Sho...11412&SiteID=1
In any event, I'll get Edge's official standpoint tomorrow and post something here.
Good luck.
Bill
On EDIT:
According to a thread in a TurboTax Forum, Vista is having problems with how it handles VB controls (OCX files). The solution, it seems, is to actually UNREGISTER the stupid things. How that for bass-ackwards! So, thry the unregister command at the top of this post and it *SHOULD* get you going.
You might have to excuse my ignorance, as I refuse to give Microsoft any more money because they feel the need to increase their revenue by upgrading operating systems yet *AGAIN* to VISTA. Well, my XP works just fine, thankyouverymuch.
Anyway, I am under the assumption that there are still some basic configuration similarities, although I could be way off base. I am sure if you do a google for Vista and MSCOM32.OCX, something is bound to turn up. I did find this... http://forums.microsoft.com/MSDN/Sho...11412&SiteID=1
In any event, I'll get Edge's official standpoint tomorrow and post something here.
Good luck.
Bill
On EDIT:
According to a thread in a TurboTax Forum, Vista is having problems with how it handles VB controls (OCX files). The solution, it seems, is to actually UNREGISTER the stupid things. How that for bass-ackwards! So, thry the unregister command at the top of this post and it *SHOULD* get you going.


