Thread: Help with Bluetooth commands

Update:
I can talk to the phone using HyperTerm and FreeFone, but every time I try to send a command to the phone, my machine power cycles its-self. Any ideas? Could someone please help me, even the correct port parameters for a GSM modem would be a huge help.
-=ew

Ill see if I have the code for the app I wrote. (See this thread for details simple bluetooth dialer )

If it works I'll see if I can find the code, its not on this PC, but I can grab it off another one that I have it on.

In the meantime if you want post a little of your code, maybe there is something we can catch in there.

As well just another thought, do you have any other serial device you can try to connect to in VB, maybe there is something wrong with your VB6 install?

I have code for both a serial XM reciver and serial control of my directTV receiver.

There really isnt any code, hell even just "MSComm1.Output = "AT"& vbCRLF reboots my PC . . .
Strange thing is that FreeFon works without a problem. Any help would be very appricated

Are you able to open the com port successfully? ( MSComm1.PortOpen = True) or does that reboot too?

Ican open the port without problem . . . tray icon shows connected. Its when I send data it reboots. I tested with your app and it also rebooted my PC. Im pretty sure CDr also used the mscomm and his works. Damn him

Haha wow, well if my app was doing the same thing, I would tend to lean towards a software issue with VB maybe? Sorry I can't be of much more help. but you've got me stumped

is sounds like a port issue. I'd try uninstalling your BT adapter and removing all the devices that it installs, reboot, and reinstall the adapter. The other thing you can try is to disable the automatic reboot on system failure if you are using XP. Right-click "My Computer" and select "Properties". Click on the advanced tab, and then the "Settings" button under the Startup and recovery section. Uncheck the box that says "Automatically Restart on System Failure", and click OK, then OK again and reboot. Now instead of rebooting, your machine should display a BSoD with an error number. That might help you narrow your issue to a specific file or driver.