Wednesday, March 30, 2011

IRS Form CO69

This is a proposal, and it may need to be undertaken by the public and supported by juries before it is honored by our governments.  I have written this proposal for the federal government, but it should be relatively easy to adapt it to state and local governments.  This is Conscientious Objector Form 69, a standard mechanism through which taxpayers can avoid paying for programs to which they have conscientious objections.

Because I have children and believe that our federal government will take me away from them if I lead the way in using this form, I can't do it.  I think it's a great idea, and I'm looking for information on how the brave citizens who use it can prepare for the attack on them from the IRS that may result from filing form CO69.

The form consists of the following seven fields.  You may use more than one form.

Line 1, Source: Enter the document from the government that you used for your amounts.

Line 2, Explanation: If the revenue department of your country offers a code for explanations, you can use the code.  Otherwise, enter an explanation of how you used the source document to gather the amounts entered in the next three fields

Line 3, Total Expense: Enter the total of what the government spent, according to the source document listed in Line 1.

Line 4, Unsupported Expense: Enter the total spent by the department, branch, or program which you do not support, according to the source document listed in Line 1.

Line 5, Unsupported Percentage: Divide Line 4 by Line 3 and multiply by 100.

Line 6, Your Total Tax: Enter your Total Tax (line 60 on the 2010 form 1040)

Line 7, Tax Credit: Divide Line 6 by 100 and then multiply by Line 5

On tax return (Line 71 of your 1040), you would include the sum of all the Line 7 amounts from your various form CO69, and you'd have to add a note indicating the credits are from form CO69, and attach that form to your return.

Wednesday, March 23, 2011

Running a batch file on your IIS 6 server

You'll probably run into the same problem I did:

Microsoft VBScript runtime error '800a0046'  

Permission denied  
/<file>.asp, line <line>

MS discusses it a little here, but they say to make sure the windows account have access to all the files necessary to execute the code without identifying what files those are.  The ultimate solution that worked for me, after giving IUSR and IIS_WPG and NETWORK SERVICE access to everything I could think of, was to give IUSR and NETWORK SERVICE access to cmd.exe.  I don't have time to mess with it, but I suspect that IUSR hands the task off to NETWORK SERVICE and doesn't need permission on all the other items.  Maybe I'll play with it later to figure it out.