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.
- Make sure all related with the program Snagit (Snagit32.exe and SnagitEditor.exe) are closed by killing the process.
- 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.
- Run SnagIt program again and the default "Profiles" will appear back.
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;
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):
- The system is unable to connect to the database.
- 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.
An excellent result!
Source : http://www.pingtest.net/