Link to home
Start Free TrialLog in
Avatar of gron
gronFlag for Canada

asked on

Windows 7, VB5, mscom32.ocx

I have a US Robotics 56K PCI Fax modem in a Windows 7 PC.
Windows recognized it and installed a driver.
Device Manager says it is working properly.
With Hyperterminal, I can dialog with it and dial out.
I can use Windows FAX and Scan to send a fax.
So what's the problem?
I have a VB5 app with MsComm (mscom32.ocx) which does not work.
The key command is : MSComm1.Output = DialString$
In development mode, if I put a stop before this command, and proceed step by step, it works.
Thinking it was a timing problem, I tried DoEvents and a Timer delay, to no avail.
Avatar of gron
gron
Flag of Canada image

ASKER

I forgot to mention this app was working for several years under W2K.
I have seen s similar issue recently...
I think the problem is in the generic drivers windows install
for the modem.You must try and get the US Robotics ones.
But even then, it is questionable if  VB5 app. will work.
Especially since W7 have no IDE support for VB5 (not even for 6).
ASKER CERTIFIED SOLUTION
Avatar of senad
senad
Flag of Slovenia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Have a look here :
http://www.msfn.org/board/mscomm32-ocx-t90715.html
its for VB6 issue but ....
Avatar of gron

ASKER

Thanks for all those ideas. Tried them all with no change.
I think it is definitely a timing problem.
Now if I place a MsgBox just before the dial command, it works when I click OK, even as a compiled program.
Avatar of gron

ASKER

Thanks senad for your suggestions.
I have solved the problem as follows:
Dim delay as boolean
Insert a 1-second Timer, enabled = false
Delay = True after 1 sec.
Add this code just before the dial command:
Timer2.Enabled = True
Do
If delay = True Then Exit Do
DoEvents
Loop
Timer2.Enabled = False

The everything works fine
This baffles me indeed ....why the delay ??
Why not connect ?
Avatar of gron

ASKER

I can only assume that my new CPU speed of 3.3Ghz is too fast for the old modem.
As I now have a working solution, I won't press further.