Content Preview: rss
12 days ago
Ok I admit it, I’m a developer and configuring access to SQL Server is not my bag (baby). SQL 2005 had a nice big Surface Area Configuration button than just allowed access from clients, so I ignored what it was doing, pressed it and got on with my work. However, SQL 2008 seems to be have been targeted at me because it no longer has such a backdoor and forced me to find out what I should do. So I thought I’d write it down for others who prefer to search the web rather then read the documentation <oops>, First off you need to open the SQL Configuration Manager and check your favourite protocol is enabled, for me that would be TCP/IP. Double click that and select the IP Addresses tab. You’ll notice in there a list of possible IP addresses and ports for SQL to listen on. You can, if you maintain your (mine) lazy tendencies simply change the setting from dynamic to static and plug in port 1433. When clients attempt to connect to your server they attempt to use 1433. Now this ...
25 days ago
It’s still early days for the W3C Widget, but the idea of been able to write a little application that I can run on numerous devices and platforms without requiring any changes is interesting (well I spose you could call that Adobe Air, maybe even my beloved Silverlight at a stretch – but even they requires an additional plug-in). So knowing that in reality they’d be difference I set of downloading various SDKs. However, I hit a number of installations problems all of which I’m sure are down to dodgy installers, beta software and 64bit Windows – not a clever combination I admit. So I grabbed trusty WinMobile and started on that first. The first issues was getting Visual Studio to sync up with the emulators. No chance, there is no project for widgets you have do everything by hand. So here is my very quick guide to get you working; Install Win Mobile 6 SDK refresh Install Win Mobile 6.5 Dev Toolkit – you’ll now have the emulators available to the device manager Create a blank ...
37 days ago
My colleague and I ran into a problem today where an old ASP site had problems creating old VB6 components. So as not to forget what to do; In Win64 the registry is conceptually broken into two versions, one for 64 and one for 32 (or Wow). So when you register a 32bit COM component then it lives under HK_CLASSES_ROOT\Wow6432Node rather than just HK_CLASSES_ROOT. This is important because when we were profiled the registry access would could see that the call to create the object was failing because it couldn’t locate the prog id in CLASSES_ROOT. The reason it was looking there was the web site was running as a 64bit process and therefore was looking in the Wow section. The answer to the problem was hidden away in the Advanced Settings of site’s Application Pool in IIS. By turning on ‘Enable 32bit applications’ the OS was able to redirect the registry requests to the correct location and the object was successfully created.
37 days ago
I thought I’d show what happens when you’re attacked by a fake anti-virus scam… It starts off by popping up a message (note it says from webpage and not the OS) Then it looks like Windows Explorer but it’s really still just the browser. Also this is running Win7 and not XP as the fake page tries to look like Looks realistic though doesn’t? You can see why people have fallen for it. And now for the money… Yeah I think I’ll say no to that don’t you, thanks for asking. So be careful out there.
39 days ago
This confused me for a bit, they’ve moved the Network DTC Access dialog from the MSDTC tab to it’s own node… Select properties on the above node…
