Get some of Vista Eye Candy ... on XP

http://www.otakusoftware.com/topdesk/

Powered by ScribeFire.

RCS - Revision Control System. Everyone should use this.

Do you edit /etc files or .inis or .confs? If you're like me, you have tons of .old or .mmddyy or .1, .2, etc. files cluttering up your directory.

If you're further like me, you have trouble sometimes to determine which one of the filename.ext~ or filename.old or filename.old.2 that you'd need to go back to if you screw something up.

RCS helps this lots.



http://galton.uchicago.edu/~gosset/Compdocs/rcs.html

Perpetual Kid?

I’m not sure what to think about this, but I think it’s something to think about when I’m not thinking about anything else.
Perpetual Kid - Unique Gifts to Entertain Your Inner Child

Exchange 2003 Outlook Mobile Access 1801 error

OK, There is absolutely almost no answer on the web for the MSExchangeOMA 1801 error. That’s because stock users of Exchange and IIS won’t have the issue that I had.

The very short answer: WebDav defaults to checking for stuff via IIS http on port 80.

If your IIS has another HTTP (not SSL/HTTPS) port as all it’s listening on, OMA/Outlook Mobile Access will not work. Make sure port 80 is listened to by IIS.

Why I had Internet Information Server on another port:

It was a legacy issue. I had OWA/Outlook Web Access through a firewall on a non-standard port. OWA does NOT like firewall port not matching IIS port. So HTTP port on IIS was chosen to match the firewall port for IIS for NON-SSL traffic. Later, I didn’t need non-SSL traffic for OWA and didn’t bother to change the IIS port. When OMA came up with

Unable to connect to your mailbox on server Servername. Please try again later. If the problem persists contact your administrator.

It was because it was attempting to contact internally via WebDAV on WebDAV’s default connection: http://Servername:80/Exchange/mailbox

the :80 (hidden, but the default port for web) was not accessible because my default http port on IIS wasn’t listening on port 80. This caused the same error from outside my firewall all the way to trying the OMA connection at localhost on my exchange server.

Thanks to
http://www.petri.co.il/configure_oma.htm
http://www.petri.co.il/configure_ssl_on_oma.htm
http://www.petri.co.il/test_oma_in_exchange_2003.htm

for knocking me in the head about things I didn’t realize I hadn’t done.

Care to share? for free?

Zolved.com has a free sharing app... Well, if you’re going to share for computer help, this is one way to do it at no charge. Windows only, and "alpha" right now, but I’m posting it here because of its potential usefulness.

mmm. Gotta get me one of these.

No big fan of McDonald’s, I, but wow. This + bacon would be awesome. Unfortunately, it appears to only be available in Japan. http://www.mcdonalds.co.jp/sales/new/teritama/index.html

Can you hear your arteries clogging? Well, if you can’t make it to Japan, you can try the Royal Red Robin Burger, described thusly:

This is the aristocrat of all burgers because we crown it with a fresh fried egg. In addition, topped with three strips of hickory-maple smoked bacon, American cheese, crisp lettuce, tomatoes and mayo.

Too bad I’m focusing on a Fish-n-Foul diet. Sushi rocks.

Is that process running?

Did you know you can query a process directly by pid and without grep?

I didn't.

ps -p `cat pidfile` -o args=

Returns something like

perl assp.pl


Is it running? Yes. Is it running the same thing as it's supposed to run? Yes.
An explanation:
ps show processes
-p show process of a specific id
`cat pidfile` the ` "backticks" mean to execute what's in between them and use it in the command line as text. cat means the same thing as type in Windows: output the contents of the file. pidfile is the filename that holds the pid/process ID of the application that's running.
-o show only what I want to show
args= show the full execution line of the process. The = is to give a column name to the "args" column. If you specify no column name, it doesn't list one.