One fine day, when I were viewing my photos in windows 7, I got shocked when I saw a yellowish tint or an overlayer that appeared on not only for one photo but all my photos!
I googled around and found out that this is a bug or issue caused by buggy/conflicting monitor profile with Windows 7.
And here’s the step-by-step procedures to solve it.
Extending a wireless network is not an easy task.
There are various way to extend your wireless network – you can connect a cable directly from one router to another and extend from there OR you can ‘join’ 2 wireless router via wireless means.The article here will talk about the second option. The correct term for this wireless-wireless setup is Wireless Distribution System (WDS).
By definition, a Wireless Distribution System (WDS) is a system that enables the wireless interconnection of access points in a wireless network.
It allows a wireless network to be expanded using multiple access points without the need for a wired backbone to link them, as is traditionally required.
Limitation (or Requirement) of WDS
My setup is quite a challenging one as I am not only extending 1 router but 2.
Due to the location of my furniture in my living room, I have to extend 2 routers to cater for both my xbox360 and my wired network printer.
In short, my overall wireless layout is as below.
The routers that I am using for my setup are
Some basic concept/setup for WDS to work
My setup
Coming soon: WDS setup part 2
omg, I had this ongoing “lag” issue in TF2 whereby my fps would drop dramatically in a fight in TF2 (team fortress 2) game.
Things get more frustrated when I recently upgrade my graphic card from the old 8600GT to the GTX260 and the lag problem does not go away!
Its only recently that I came across this thread in steam forum that suggest a fix to this problem.
if you have a similar setup like mine
and encounter the following symptoms…
for the following steam games…
perhaps you may want to try the following method and see if the problem would go away.
To display the default last 10 lines for a file…
tail error_log.txt
To display a specified no of lines for a file…
tail -15 error_log.txt
‘Premature end of scrip headers’ error message refers to the script being stopped for whatever reason before it actually return any output to the browser.
The first time to check is to ensure the below codes are output first
print "Content-type: text/html\n\n";
And then to debug the error, simply add the below line(preferably after the above code).
use CGI::Carp qw(fatalsToBrowser);
Recently came across a problem whereby the quartz scheduler could not recreate a new log4j FileAppender log when the job is call again.
Googled a bit and found out a couple of solutions such as using a custom log4j classes, which create a seperate thread when being called in quartz scheduler.
I find that it is too complex and had try several ways to recreate the log file inside Quartz.
And finally came up with this one line of code.
Before I begin, let’s take a look at my log4j config.
This log4j config will create a simple console system out logger and also a FileAppender logger.
For my case, I want to re-create a new log file whenever this job is run.
log4j.rootLogger=INFO, stdout log4j.additivity.stdout=false log4j.additivity.joblog=false log4j.appender.ROOT.layout.ConversionPattern=[%d] %t %c %-5p - %m%n #console log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%d %p - %m%n #per job execution log log4j.logger.com.yourcompany=INFO, joblog log4j.appender.joblog=org.apache.log4j.FileAppender log4j.appender.joblog.layout=org.apache.log4j.PatternLayout log4j.appender.joblog.File=../jobtemp.log log4j.appender.joblog.Append=false log4j.appender.joblog.layout.ConversionPattern=%d %p - %m%n
and here’s the schedule job
public class ScheduleJob implements StatefulJob {
private static Logger logger = Logger.getLogger(ScheduleJob.class);
public void startJob() throws SchedulerException{
Scheduler scheduler =
StdSchedulerFactory.getDefaultScheduler();
scheduler.start();
}
public void execute(JobExecutionContext context)
throws JobExecutionException {
//reset log4j config for FileAppender
PropertyConfigurator.configure("../conf/log4j.properties");
RunJobImmediately newJob = new RunJobImmediately();
newJob.performJob();
}
public static void main(String args[]){
try{
ScheduleJob scheduleJob = new ScheduleJob();
scheduleJob.startJob();
}catch(Exception e){
logger.error(e);
}
}
}
and finally the one line of code to recreate the log file.
Apparently, this line will somehow ‘reload’ the log4j utitlies, which thus recreate the FileAppender logger to re-create the log file.
PropertyConfigurator.configure("../conf/log4j.properties");
Feel free to let me know if there is any performance issues or it is not working at your side.