right, after fighting with the wireless technology known as bluetooth for a grand total of five hours i think i've got the hang of a part of the whole scenario, but not everything.
1) i managed to correctly establish the desired connection and finally be able to cut mp3's for ringtones and download them onto my phone without needing to borrow computers or PDAs.
2) this operation brought me back to at least 1999 if not before: lots of proprietary software/drivers that must be reconciled together, namely the bluetooth drivers provided by digicom (producer of the usb bluetooth radio), windows' chosen location of bluetooth neighborhood, and the sony ericsson apps designed to allow gprs connection via bluetooth.
3) the crux of the problem, that i took forever to figure out, was that the 'generic usb radio' driver that windows insisted to force on me was not compatible with my hardware, OS's protestations notwithstanding. actually i had to install something that goes by the pretty generic name of "CSR USB Bluetooth Device" and I happened to understand that by a mere stroke of luck, having tried to run the setup program provided by digicom without plugging the radio in order to avoid the dreaded hardware detection. of course the procedure didn't work on its own so i had to combine bits and pieces of different strategies, but now it's up.
4) i cannot connect to the internet, unfortunately. i have a GPRS service on my mobile and it works perfectly fine via WAP, but getting the phone to act as GPRS (packet, NOT dial-up) modem for the PC is terrible. first of all, i had to realize that the correct device wasn't the bluetooth modem, but the "serial modem", meaning that bluetooth emulates a serial port on COM4 and applications might be run with output on that port. (why the fuck is that?). with the "bluetooth modem" (proprietary and all, so it wasn't a question of wrong driver) it refused to work, citing hardware problems. the "serial modem" configuration encounters PPP problems every now and then, but the link is established - only, once i open my browser and type a site name i see that it's working (eg resolving names) but then it all goes awry, because information is sent and not received.
5) which brings me to the final question: HOW THE FUCK DOES THE THING WORK EXACTLY? i don't even have a manual - but i know that now my COM ports run up to 26 (!) because I performed several installations, and even if i uninstalled everything neatly and even removed the ports manually from the device manager they kept on coming back, the bastards. i think i might be more effective in both configuring the utilities and my hardware if i had any idea of how the damn virtual COM ports are defined and why. i mean - why don't other radio-based devices need so many ports? and how come the digicom software installed not one but TWO modem drivers (claiming to have found hardware of all things) when my mobile wasn't even switched on?
ehm, sorry for the rant.
and, spike: no, sp2 has nothing to do with this, but the installation made me waste more time, and i had to turn off all the ridiculous "security" thingies that were being forcefed to me. like i care about having a windows firewall (which probably bars everything but microsoft updates) or an anti-virus sponsored by them. "you don't appear to have an anti-virus software, click this box to solve the problem" my ass.