This is the easiest and quickest way to solve the Halo Reach matchmaking server unavailability....all you need to do is...
1.go onto...Settings Tab, System settings then Network Settings
2.In network settings, choose configure network...
3.Select the IP address settings then change it to manual
4.Change the last few numbers on IP address to something above hundred (e.g. xxx.xxx.x.[xxx]) the things in the [ ] should be numbers above 100
5.type in your default subnet mask and default gateway then press done
6.Go and change the DNS server now...
7. change the DNS settings from auto to manual..
7a.Change Primary DNS to: 8.8.8.8
7b.Change secondary to: 8.8.4.4
8.Press done and go onto Halo Reach
9.It should work...Thanks for watching
Sunday, September 7, 2014
Saturday, March 31, 2012
Lesson Learned from Life
"A small return and a safe one is far more desirable than risk" I hope I can always remember this… (from The Richest Man in Babylon")
Monday, December 19, 2011
Friday, January 28, 2011
Market Notes
From Tim Wood:
“At the 1932 bear market bottom the yield was 10.50% and the P/E was just under 10. At the 1942 bear market bottom the yield was 8.71% and the P/E was 7.3. At the next great bear market bottom in 1974 the yield was 5.9% and with a P/E of 7.24. If we take this same reading at the 1982 low the yield was 6.2% and the P/E was 6.9. For the record, these P/E ratios are based on Generally Accepted Accounting Principles and not the bogus George Orwellian methods of today. At the 2009 low, the P/E was 26 with a dividend yield of 3.2, which is hardly at par. Therefore, based on this historical measure, there is also no indication that the 2009 low marked the bear market bottom. It is for this reason along with the historical bull and bear market relationship issues covered in the last post here that I continue to believe the rally out of the March 2009 low is a longer-term bear market rally much like was seen between 1966 and 1974.”
“At the 1932 bear market bottom the yield was 10.50% and the P/E was just under 10. At the 1942 bear market bottom the yield was 8.71% and the P/E was 7.3. At the next great bear market bottom in 1974 the yield was 5.9% and with a P/E of 7.24. If we take this same reading at the 1982 low the yield was 6.2% and the P/E was 6.9. For the record, these P/E ratios are based on Generally Accepted Accounting Principles and not the bogus George Orwellian methods of today. At the 2009 low, the P/E was 26 with a dividend yield of 3.2, which is hardly at par. Therefore, based on this historical measure, there is also no indication that the 2009 low marked the bear market bottom. It is for this reason along with the historical bull and bear market relationship issues covered in the last post here that I continue to believe the rally out of the March 2009 low is a longer-term bear market rally much like was seen between 1966 and 1974.”
Wednesday, January 20, 2010
Useful Windows Command Tools
I just found some useful windows tools you can use from the command line:
1. Tasklist: Allows you to see the list of tasks running on your local computer or on a remote computer. For instance, you can run:
Tasklist /S [computer name] /U [user name] /P [user password]
If you have Administrative rights, you can run it to see the tasks another user is running on another computer on your LAN.
2. Taskkill: Allows you to kill a remote task (process) running on your local computer or on a remote computer on the network (LAN). You can run:
Taskkill /S [computer name] /U [user name] /P [user password] /PID [process id number]
This is very handy if a remote computer is stuck and you cannot login to it.
3. Logoff: This is very handy if you want to use Terminal Services and all the sessions are used. You can logoff another user who has left his session open.
LOGOFF [sessionname | sessionid] [/SERVER:servername] [/V]
1. Tasklist: Allows you to see the list of tasks running on your local computer or on a remote computer. For instance, you can run:
Tasklist /S [computer name] /U [user name] /P [user password]
If you have Administrative rights, you can run it to see the tasks another user is running on another computer on your LAN.
2. Taskkill: Allows you to kill a remote task (process) running on your local computer or on a remote computer on the network (LAN). You can run:
Taskkill /S [computer name] /U [user name] /P [user password] /PID [process id number]
This is very handy if a remote computer is stuck and you cannot login to it.
3. Logoff: This is very handy if you want to use Terminal Services and all the sessions are used. You can logoff another user who has left his session open.
LOGOFF [sessionname | sessionid] [/SERVER:servername] [/V]
Tuesday, September 29, 2009
Taca Airlines Rips You
Don't buy from Taca airlines on-line when flying San Pedro Sula-Tegus, it costs you twice the regular value. One should buy through Isleña Airlines, same flight, half the cost!
Monday, September 28, 2009
Problem Connecting to Networks Using Intel Wireless
I finally found way to connect to networks requiring Device ownership password:
Control Panel->add or remove programs-> Intel(R) PROSet/Wireless Software -> Modify -> Unmarked WI-FI PROTECTED SETUP
Control Panel->add or remove programs-> Intel(R) PROSet/Wireless Software -> Modify -> Unmarked WI-FI PROTECTED SETUP
Subscribe to:
Posts (Atom)