I have bought a Samsung SHG-Z560 HSDPA handset on a web n walk contract from T-Mobile to get broadband access to my laptop via my mobile handset.
This seemed a more logical choice than a data card since I have devices with PCMCIA and Express card form factors using varying MS OS's (namely XP and Vista).
For Vista I simply plugged in the handset via the supplied usb and allowed it to download and install the required drivers from the web.
I then followed
these instructions to create the modem connection item and I am very happy to report it rocks and I didn't have to install any dodgy Samsung PCStudio apps etc.
I would point out though that I am using this phone purely as a modem so syncing contacts etc is not required hence no need for PCStudio ;0)
I recently bought a Dell XPS M1210 (fab laptop btw) and have been trying to get the damn thing to sync with my iPAQ hw6915 via bluetooth.
The recurring issue was that even after configuring WMDC to accept bluetooth connections my iPaq could not find the necessary service to create the bluetooth sync.
I found the answer
here:
Follow the instructions and
reboot to get the serial port visible and then just use the WM5 wizard to create a new bluetooth activesync connection and you're away!
I have been researching developing Sidebar gadgets for Windows Vista recently and came across this
great article.
Basically, it allows you to use a .Net Interop Component to consume .Net assemblies directly within the scripting files for your gadget.
This basically unlocks the full potential of .Net within the sidebar. Kudos, Acoustic!
I frequently require to setup several web applications on my development box and for convenience almost without fail will use host headers to distinguish between them rather than configure and maintain multiple IPs.
This approach serves well until secure http is required and I need to assign SSL certificates to my web applications.
If you have ever tried this you will know that the IIS Manager does not have anywhere to allow you to specify a host header when configuring the SSL for the web application.
The solution I use goes as follows:
1) Install the IIS Resource Kit for IIS 6.0 - it comes packaged with a selfssl utility to generate self-signed certificates. (Of course, feel free to generate them with Perl scripts or any other method since they are not from trusted sources they're only useful for dev and testing purposes anyways.)
2) Create/extend the required web applications using the Administration interface of MOSS (ensuring to select 'Use SSL').
3) Use the selfssl utility to generate and assign a certificate to the first of your web applications as follows:
selfssl /N:CN=*.mydomain.com /K:1024 /V:3650 /S:site id of your first site from IIS /P:443
This will generate a 3650 day certificate with a 1024 bit key and assign it to the web application with the site id supplied.
4) Use IIS Manager to assign the same certificate to the other web applications.
5) If you restart IIS at this point only 1 of your sites will actually start - you still need to manually configure the secure bindings for the remaining sites:
cscript.exe C:\Inetpub\AdminScripts\adsutil.vbs set /w3svc/site id/SecureBindings ":443:host header"
This will set the secure bindings for the site identified on the supplied host header.
6) If you wish you can also now configure the web applications in IIS Manager to require SSL.
7)
iisreset and you're done....