Oct. 31, 2007, 1:18 p.m.
You need to read <a href="http://weblogs.asp.net/rmclaws/archive/2003/07/31/22080.aspx">this blog post</a>. It might make you angry if you are trying to get .NET to emit XML that is not encoded in UTF-16, but it will give you a solution.
Oct. 12, 2007, 8:49 a.m.
Ok, I modified this. I thought you needed an adapter, but you do not. Simply remove the adapter from your Dell drive and put it on your new drive. Thanks to the helpful guy at GeekSquad who helped my sister get her laptop running again!
Oct. 1, 2007, 5:57 p.m.
I was looking for a good, stable PHP template framework. The last time I was writing a lot of PHP, it was 2000 and we were using FastTemplates. It looks like the project is still being maintained by somebody, but it also seems many people are using <a href="http://smarty.php.net">Smarty</a>, so I decided to try it. It installed relatively smoothly, until I went to try and actually render a template. Then I got an error about Smarty.class.php:1258 not finding a file. Everything I could find was conflicting: it's probably a permissions problem, but don't worry about permissions on Windows. Hmmm. Turns out, my Apache service is running as the local system user, which is what I expected. However, I didn't see that user had any explicit rights in one of the folders where Smarty needs to write files (templates_c, I think that's the compilation path). So, I gave the system user full control permissions on that folder and, voila! Templates! Now to actually do something useful... Now, I don't know for sure if this is the most secure method. I was thinking that a better way to do this would be to create a lower privileged user and change the service to logon as that user, then give that user permission to write to the compiled templates directory. Here's <a href="http://httpd.apache.org/docs/2.0/platform/windows.html#winsvc">the official take on it</a>.
Aug. 8, 2007, 11:48 a.m.
Here are some quick notes. The built-in SmtpClient class isn't going to work. Unity detects incoming VPIM messages <a href="http://www.google.com/search?hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&hs=cRo&q=Unity+VPIM+sink&btnG=Search">using an Exchange event sink</a>. The Unity event sink <a href="http://www.ciscounitytools.com/Applications/VPIM%20Transport%20Event%20Sink.doc">looks at the content type</a> of the incoming message. The SmtpClient class doesn't expose this header. There's no real way to change the content type for an outbound message using SmtpClient. I found <a href="http://www.eggheadcafe.com/articles/20030316.asp">some code</a> that will help. Note that you need to be very careful and make sure your message is formatted correctly. Things like screwing up a MIME boundary will result in the message being dropped by the Unity event sink, so it will get sent on to Exchange. Exchange won't understand the user name, and will respond back to the sender with a NDR. Very useful diagnostic logging can be <a href="http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_tech_note09186a00806f3780.shtml">turned on</a> and found in the directory for your Exchange server. You really need to use this log file if you run into any problems.
Aug. 7, 2007, 3:26 p.m.
Ok, so this cracked me up...but your mileage may vary. I've been researching VPIM, a standard used to send voice mails around using SMTP. I searched Google for "C# VPIM." <a href="http://del.icio.us/search/?fr=del_icio_us&p=vpim&type=user">My own del.icio.us tags</a> were tenth in the search results. Guess it's not a very popular topic yet.
July 17, 2007, 9:18 a.m.
Sometimes when you restart your ASA 5500, the Easy VPN configuration presents a problem. Even if you save the running configuration to the startup configuration. This is a known issue and there is a fix, but if you just want to Make it Work for now: <ul> <li>In the web interface, click "Configure," then "VPN," then "Easy VPN Remote."</li> <li>If the VPN light isn't on, it's not enabled. Check the box to enable it and hit "Apply."</li> <li>You will probably get a dialog telling you about conflicting configuration. Leave it open.</li> <li>Open a command prompt and telnet to your ASA 5500. Use the same password as you do to login via the web interface.</li> <li>Type <code>enable</code> and hit return. Use the same password.</li> <li>Type <code>configure terminal</code> and hit return.</li> <li>Type <code>show running-config</code> and hit return.</li> <li>Find the lines in your running configuration that are very similar to the ones in the ASDM dialog box.</li> <li>For each of those lines in your running configuration, type <code>no ...</code> where ... is the line of your running configuration. There might be more lines in your running config than your dialog box.</li> <li>Type "write memory" and hit return. Wait for it to finish.</li> <li>Go back to the ASDM applet, close the dialog, check "Enable" and hit "Apply" again.</li> </ul> It should work now.
June 27, 2007, 2:25 p.m.
And it has a <a href="http://cuaesdk.sourceforge.net">page on SourceForge</a>.
June 27, 2007, 2:11 p.m.
I need to be able to look at incoming messages in Exchange and maybe send them elsewhere if necessary. Exchange 2007 <a href="http://www.directionsonmicrosoft.com/sample/DOMIS/update/2007/03mar/0307egdo.htm">will introduce new APIs</a>, but I won't be using 2007...yet. So, it would appear the way to go would be write an Exchange message sink. <ul> <li><a href="http://www.microsoft.com/downloads/details.aspx?familyid=0cd7f344-cad6-416e-9bc1-0d7c214e1d0b&displaylang=en">Writing Managed Sinks for SMTP and Transport Events</a></li> <li><a href="http://msdn2.microsoft.com/en-us/library/ms877956.aspx">CDO for Workflow</a></li> <li><a href="http://www.microsoft.com/downloads/details.aspx?familyid=0cd7f344-cad6-416e-9bc1-0d7c214e1d0b&displaylang=en">Microsoft Windows 2000 SMTP Service Events</a></li> <li><a href="http://www.christopherlewis.com/ESA/ExchangeSpamAssassin.htm">SpamAssassin Sink for Exchange</a></li> </ul>
June 27, 2007, 12:26 p.m.
I forget exactly what I did, I think maybe boot into Vista, try to print, realize I hadn't added a printer, boot back into XP (where printing was working)...and then it happens. You get the Win32 "pointer in the eye" dialog: "Spooler SubSystem has encountered a problem and must close." <ul> <li>Delete the printer.</li> <li>Reboot.</li> <li>Reinstall the printer.</li> </ul> It should work. Again, I found this on the net somewhere yesterday and lost it.
June 27, 2007, 11:55 a.m.
I lost the post where I got this info from...but the crux to getting the networking, well, working was: <ul> <li>Install VMWare tools</li> <li>Reboot</li> <li>Install VMWare tools again (but don't have it automatically install and reboot) - you should now see C:\Program Files\VMWare\VMWare Tools.</li> <li>Open the Device Manager (Computer -> Properties).</li> <li>Right-click on the VMWare network adapter, go to the Driver tab and uninstall the driver. It will automatically reinstall.</li> <li>Reboot.</li>