Hi there
is it possible that you forget your own posts, or stop reading the answers?
Already answered you this question once, here
THX
Chaos
Hi there
OK, thats a good reason to start a new post.
But i dont know a program to automate this, except phoco.
Maybe you should ask zorro if he can create a little tool, that is somekind off a stripped down version of phoco, which can only create the connection of the widcomm audio-thing.
I just imagine something like a little script or a small .exe you could put in your autostart. But i am not a programmer, so i dont know if this is easy, or possible.
Just an idea, cause i have no other clue how to solve this problem.
THX
Chaos
Ok well i got it workiing....but for some reason the other end ofthe phone call has an echo. I dont know what causes that. THey hear an echo in "there" voice. ANybody else get this?
Skinning to go... VisualDesigner2!
Ahh .. I installed this and my computer wouldn't boot up. Luckily google turned up something and I was able to fix it (I haven't tested to see if the bt drivers work yet.. but my comp works).
The error: As soon as windows booted (before login) it dispalyed my background with the following two errors:
Services.exe: Entry Point Not Found
The procedure entry point _resetstkoflw could not be located in the dynamic link library Msvcrt.dll.
Followed by:
Services.exe: Entry Point Not Found
The procedure entry point _resetstkoflw could not be located in the dynamic link library Msvcrt.dll.
I was able to resolve this error by booting the win xp setup cd and went to recovery mode (by pressing r after the long wait). I selected my console and typed my admin password and I was at a c:\windows prompt.
I took the Msvcrt.dll file off of the xp cd and put it in my system 32 file by typing the following:
1. cd system32 [Enter]
2. ren Msvcrt.dll Msvcrt.old [Enter]
3. e: [Enter] (my cd drive)
4. cd i386 [Enter]
5. expand msvcrt.dl_ c:\windows\system32 [Enter]
6. exit [Enter]
It worked.. I'll edit this post and tell ya'll if the bt drivers worked.\
Edit: Reinstallign except this time it's taking like 20 minutes.. so I stoped it and retried.. still taking 20 minutes.. so if I wouldn't have stopped it.. it probably would be working.... Anyways. I think there is a problem with this software..(that has an ez fix) unless everyone else has got it to work fine...\
Nope didn't work.. looks like I'm going back to .700.
-z0rz
Car PC Status: [XX|xxxxxxxx] 20% Done
Waiting on Lilliput to come in
My Worklog Site My Worklog Post
I have found the problem at last (I have been delayed, waiting for my dead hard drive and screen to be replaced)
Before you install, go into the SVCPACK directory and make sure the file is called btneighborhood.dll. Both me and Chaos got it wrong it seems!
If you have already installed, then you will need to rename the file as above, then copy it into Windows\System32 via safe mode.
Apologies for the inconvinience
I'm not sure why, but nothing over .700 works for me - I have a CSR Bluetooth Radio, and they all say "no Bluetooth device detected".
Anyone have any idea why?
Doko ni datte, hito wa tsunagatte iru...
My BMW 335xi install
My Subaru Impreza install (now retired...)
Realtime audio freestyle hiphop battles online - www.letsbeef.com!
Jeez I'm realy going crazy out here... pff. I tried .700 , .1500 and .2101 now (currently using .1500) and can't get "the serial connection" to work.
The installation works fine... detection of my bluetooth adapter is fine... etc. etc. Bluetooth file transfer and network connection works flawless.
But now... I really can't get the serial connection to work! with all the 3 the versions!
When I run for example the Wizard and select wich services I want to share.. when I click on configure on the serial connection, I see windows quickly recognizing the bluetooth com port, installing it, and sais it's correctly installed.
But when I look at the property box of the serial connection, it only lists COM0 as com-port. Can't change it.
The same problem when I look at "My Device" in the Bluetooth neighborhood. It lists 10 services, but the serial got a little cross. When I want to enable it, I see windows recognizing the "new" COM port and installing it again... but it still isn't enabled.
In my Device Manager I see that the Bluetooth adapter is correctly installed (with the Widcomm driver), and 6 Bluetooth COM-ports with the Widcomm driver too.
So if there is anybody who could help...please![]()
Bookmarks