OnLearning

These are overview comparison for understanding characteristic of storage.

Credit to: http://debaffle.net

Source : www.brandywineschools.org

The simplest way to get those information are through GUI by using several application such as CPU-Z. In my case, I consider not to install additional software in my machine in order to get those information (RAM).

My searching end up with Windows Management Instrumentation Command-line (WMIC) tool that can extract variety of information. In my case, RAM.

Using wmic through command-line (cmd), just key in memorychip command and press Enter (1).

It will displays BankLabel, Capacity, Caption, CreationClassName, DataWidth, Description, DeviceLocator, FormFactor, HotSwappable, InstallDate, InterleaveDataDepth, InterleavePosition, Manufacturer, MemoryType, Model, Name, OtherIdentifyingInfo, PartNumber, PositionInRow, PoweredOn, Removable, Replaceable, SerialNumber, SKU, Speed, Status, Tag, TotalWidth, TypeDetail and Version. Definitely in one long output.

If you just only need selected information from above, just key in memorychip get capacity,devicelocator,tag  and press Enter.

If you want to extract all above information to text file, simply enter command  wmic memorychip get >ram-info.txt (2).

**you can change text filename (ram-info.txt) based on your desire. 

If you mess up with the profile in SnagIt and want to restore back the original profile, the process are quit simple.

1. Make sure all related with the program Snagit (Snagit32.exe and SnagitEditor.exe) are closed by killing the process.
2. Open Registry Editor as Administrator and navigate to HKEY_CURRENT_USER\Software\TechSmith\SnagIt\12\Profiles and delete the "Profiles" folder.
   • Just delete the "Profiles" folder.
3. Run SnagIt program again and the default "Profiles" will appear back.

You may want to try the latest driver version 19.1.0 since some users reported it solved the issue for them. Also make sure your access point has the latest firmware installed.

Intel® PROSet/ Wireless Software Downloads

http://www.intel.com

Eventually, it's quite possible to create backdated for new tickets from the osTicket Web-based because this are the supposed thing to be done. But sometime, we forgot to log to the system. When we trying to do that, the system did not allow it.  

There are 3 table involved when creating new tickets, which are;

ticket_event : Displaying in dashboard. ticket_thread ticket

These 3 table need to be change accordingly so that the report that going to be produced will be accurate.

Hopefully, this tips will going to help you guys...

This is caused by one of 2 major things (from my experience):

1. The system is unable to connect to the database.
2. The system is unable to load the config info from the database.

Make sure your database connection info in the osTicket config file is correct.

Make sure the config database table has not become damaged or corrupted.

By the way, location configuration file for both issues located at ../include/ost-config.php

Thanks to  http://osticket.com

Let say, after throwing ping command to target, the return result is shown as follows;

Actually the time value indicate that either the target accessible smoothly or not. The indicator as follows.

	A	An excellent result! Expect all Internet applications to work very well assuming you have sufficient bandwidth. MOS greater than 4.37 (Example - a ping below 50 ms with 0% packet loss)
	B	Very good! Your connection should work well for any Internet application. Some online games may not perform optimally. MOS between 4.28 and 4.37 (Example - a ping around 90 ms with 0% packet loss)
	C	Acceptable. Your VoIP quality will suffer some, and you will have a disadvantage in many online games. Most streaming media will be fine. You should try testing again to another server close to you. MOS between 4.00 and 4.27 (Example - a ping around 150 ms with 1% packet loss)
	D	Concerning. Most online applications will not perform well but should function in some capacity. Try testing to other servers to verify the result. You might need to contact your ISP for help. MOS between 2.50 and 3.99 (Example - a ping around 300 ms with 3% packet loss)
	F	Very poor. Real-time Internet application performance will suffer greatly on such a connection. Test to other servers to confirm the result, but definitely talk to your ISP about troubleshooting the issue. MOS lower than 2.50 (Example - a ping above 500 ms with 20% packet loss)

Source : http://www.pingtest.net/

Basic knowledge between 

Hi there, just became aware of your blog through Google, and found that it is really informative. I am gonna watch out for brussels. I will be grateful if you continue this in future. Numerous people will be benefited from your writing. Cheers!