SET XML ="%CD%\Pathtofile"
SET @ERROR_FUNC. > "%XML%"

The code is best used for clearing log files without the need for VBScript or CScript. Here’s sample code below clearing an XML log file:

@ECHO OFF
SET XML=%CD%\Project\Contents\Main\components.vxml
@ECHO Clearing %XML%\
CRASH_TEST > "%XML%"

@ECHO Writing file %XML%
(
    @ECHO ^<?xml version=^"1.0^" encoding=^"utf-16^"?^>
    @ECHO ^<components xmlns:xsi=^"http://www.w3.org/2001/XMLSchema-instance^" xmlns:xsd=^"http://www.w3.org/2001/XMLSchema^"^>
    @ECHO ^</components^>
) >>"%XML%"

@ECHO Done
PAUSE

This issues are posted by me in StackOverflow and ServerFault :

The server specifications are below and my notes on the issue:

Windows Server Standard on SP2
IIS 7 with ASP.NET 1.1
IIS 6 for SMTP

The server hosts many websites running ASP.NET 1.1. These websites use the built in SMTP server on IIS6.

The SMTP works fine for a while but after a few weeks or months, It will stop sending emails. I tried sending one via Telnet it seems fine so the SMTP server is not the issue.

I tried restarting the Application Pools but it had not effect whatsoever. I also tried restarting IIS 7.0 and IIS 6.0 it still will not send messages.

The only temporary way we found to fix this was to restart the server.

Is there an ASP.NET cache that we can clear or is causing this issue?

UPDATE:

Got the fix!

It was a hunch but I restarted the Print Spooler and DNS Client services in the server and now emails are sent successfully.

But I still do now know why this happens for ASP.NET 1.1 projects.

UPDATE 2:

Issue appeared again today! I got lucky I thought I had to wait weeks to test it again.

I started by restarting the DNS Client service. No effect still cannot send emails. I then restarted the Print Spooler service and to my surprise it was the culprit! ?????????

How is this even, what, why? huh?

I disabled the Print Spooler permanently. Email still works. I do not think we print anything or if the Print Spooler does any other tasks other than printing.

If it does do anything please comment below.

UPDATE 3:

The fix was temporary. I found out today that WINSOCK refused connections from ASP.NET but accepted connections via telnet mail.

Still trying to find out why this is happening.

UPDATE 4:

Well finally made a reboot with the WINSOCK corruption fixes applied. Hope this holds forever and the bug does not reappear.

FINAL UPDATE:

After a few weeks of debugging and fix finding the only workaround for this would be to either reboot the server regularly, move to System.Net.Mail instead of System.Web.Mail or use Microsoft SQL Server DBMail.

Here’s how I released the NSData class pointing to a response from NSURLConnection:


NSData *feedData;
feedData = [[NSData alloc] initWithData:[NSURLConnection sendSynchronousRequest:request returningResponse:nil error:&error]];
feedData = NULL;
[feedData release];

 

You just have to assign NULL to NSData before releasing it. It does work and it minimized my memory use when I checked it in the Leaks Performance Tool in XCode. Even though it works, I am not sure of is why NSData crashes with NSURLConnection explicitly declared as an owned object.

Here’s the first tip: Good motherboards will always be hard to find. No matter how much publicity you see for a motherboard it is always best to check the net for forums that have user opinions on the boards. Be careful though some companies use SEO tactics and do shameless self promotion with their products. A good tip would be to check the forum poster’s number of posts, the higher the posts the better.

Second Tip: If you are a computer enthusiast, a good motherboard for you would be one that is fully customizable. I can’t give out any suggestions on what motherboard brands to purchase but look for one that has good warranty coverage. This is so that you can relax easy while overclocking or concocting a new super computer that can rival Google’s servers.

Third Tip: If you are not a computer enthusiast and want a motherboard that is budget wise and will last for a long time, go for Intel motherboards, not motherboards with Intel chip sets but motherboards that are manufactured by Intel. I can assure you Intel boards, with regular maintenance (anti-virus, defragmenter) can last to more than 6 years based on personal experience. This is backed up by the fact that Intel has been producing server motherboards for IBM mainframes for a long, long, long time already.

Lastly: Picking the motherboard should be the task that will take you the most time when building a system. Keep in mind that the motherboard is the glue that will bind every component of the PC and so it is very important to choose carefully. I have always noticed since computers were sold as packages at stores here in Davao, store owners will not put the motherboard brand on the package list. They usually think that the system is good to sell as long as the CPU is fast, the hard drive is spacious, the monitor has a large and clear screen, the memory is high and the video card. I always end up asking “What’s the motherboard of this package?”

* I have owned this computer since May 2005, even though I have been quite abusive to the computer such as turning off the CPU by holding the power button and even pulling the plug immediately, I still have the original installation of Windows XP running on the machine from the day I purchased the system. (“Original Install Date: 5/7/2005, 11:24:05 PM” – You can check for your installation date by executing the “systeminfo” program in the command line of Windows XP.)

PS: Lastly, the motherboard that I would not recommend you purchasing would be ASUS motherboards. Even though ASUS has good marketing, IMHO, I don’t think they produce high quality motherboards. I am saying this because I have a lot of friends who own ASUS motherboards and they always keep asking me for help on something such as unexpected restarts and BSOD which I will not be able to fix because I have traced the problem as part of the hardware. As a systems administrator, web developer and programmer I have used and fixed a lot of comptuers that run on ASUS motherboards one such example that would be easy enough is when I am updating the BIOS, I distinctly remember two units with ASUS motherboards failing the update and rebooting to the old BIOS. Another problem I have with ASUS motherboards is that when you try to check their website for drivers, most of the drivers are dated back when the motherboard was released. I would not even bother installing the auto updater that comes with the CD for the motherboard in the office because it would only be a waste of memory.

And if any ASUS motherboard fans are reading this here are two things to think about. ASUS produces about 15 to 30 new motherboards per year (this is due to the fact that they also produce motherboards for AMD) while on the other end, Intel produces about 5 to 9 new motherboards per year. Another thing, with that much marketing and publicity how much do you think they will have left for funding research and development?

Magic Jack is very easy to install in the first place. Just plug it in and then plug your phone to it. The executable or installer should run automatically, if not open the flash drive, find it and then run it. The next part will deal with firewalls and port settings.

I used Active Ports to find out what ports MagicJack was using and it turns out that it uses a lot of UDP ports and two TCP ports. Their website specifically states that the device only uses UDP ports 5060-5070 (reference: LINK (removed) – GOOGLE’S WEB CACHE OF THE PAGE UPDATE April 7, 2011:The knowledge base has been down for a while but I managed to retrieve Google’s cache of the site.) which I found out was clearly not true. I found this out by performing calls to a random list of phone numbers (except 911 numbers ^_^). I dialed at least 40 phone numbers repeatedly. After this, I was able to conclude that MagicJack uses random UDP ports in the high range. UDP ports might seem a bit less important than TCP ports but as a Systems Administrator this will create a highly unsecured and exposed network. I was only able to achieve 100% connectivity with the 40 phone numbers after opening a range of UDP ports.

I also stumbled upon a lot of sites and forum posts that tell magic jack users to setup port forwarding, this is NOT true!

Below is the exact list of the TCP and UDP Ports that I had to open in my firewall and router (NOT port forward) to achieve 100% connectivity:

TCP Ports List: 80 (HTTP), 443 (HTTPS)

UDP Ports List: 5060, 5070, 10000-65535

It is really strange why the device was designed like this. My guess is that the device is intended solely for home use and not commercial use.

Link to my post in RB: http://ragnaboards.levelupgames.ph/index.php?showtopic=123027&view=findpost&p=2984158

you will need to register before you can view the post.
 

There is already an official fix released for this, so just update your OpenKore to the latest version in this site:

http://openkore.collectskin.com/

All you have to do is download this file: http://openkore.collectskin.com/openkore_ready.zip and then if you’re in a hurry copy over your old configuration files to the new control folder or you could do a line by line copy, this is because the new version has some new configuration settings that might not be present in your old configuration file.

To make sure the above link is an official website and not some scam site just view this thread in the OpenKore’s official forum for their users in the Philippines:

http://darkmoon.ath.cx/viewtopic.php?f=8&t=1726&start=0#p16101

A. Before setting up, try to read a little about these topics:

1. RCA Cables
2. HDTV
3. Component Cables
4. Digital Theater System
5. Surround Sound
6. TOS-LINK Cables
7. TRS Connector

A. Understanding the common setup for Home Theater Systems

Before starting the setup you need to understand that in a home theater there are only two things you can experience, the audio experience and the video experience each of which gets data from a source, and so by putting this in mind it will be easier for you to understand how to create basic setups and troubleshoot problems.
 
Video Experience Devices:
– Television / HD Televisions
– Projectors
– Computer Monitors
 
Audio Experience Devices:
– Amplifiers
– Speakers
– Subwoofers
 
Possible Sources:
– DVD Players / Blu-ray Players / VCD Players
– Xbox 360
– PSP / PS3 / PS2
– Digital Camcorders
– Digital Cameras
– Personal Computers
– Cable TV
 
How do these devices work together/communicate?
After knowing these, the next thing to understand would be to learn how these devices communicate with each other. These devices communicate using IN/OUT jacks. No matter how complex the jack may look like (RCA,TOSLINK,DVI,HDMI) or how many there are (RED,WHITE) they only can only do one action. IN jacks receive data/video/audio signals from other devices while OUT jacks send data/video/audio signals to another device. Like the principle of north and south poles of a magnet they need to bind together.
 
 
Now that you have read about the basics on the next page I will be showing some examples and jack scenarios on basic Audio and Video Experience connections for home theaters. Don’t like HTPC? I will also include a scenario wherein your PC will be used as a source. ^_^
 
On to Page 2!