Author Archive for Malgent
Specification number, or S-spec number, is a five character code that uniquely identifies such CPU characteristics as core frequency, bus frequency, the size of level 2 cache, thermal design power, and so on. Specification numbers always start from letter ‘S’ and are usually printed on the top of the CPU. Intel Pentium, Pentium MMX and Celeron processors in plastic PPGA package have specification numbers printed on the bottom of the CPU. To find out processor characteristics from the specification number please use “Search by S-Spec” form on this page. We also recommend to use Intel processor finder tool.
Some examples of specification numbers: SL92C, SL7PW, SL3XX
NOTE: Intel engineering and qualification samples are marked with specification numbers that start from ‘Q’ - these are so called QDF numbers, and they are used to identify qualification and engineering samples.
Processor model numbers are used to distinguish between microprocessors with different sets of features and different characteristics, such as speed, level 1 and level 2 cache, etc. The model numbers can be used to identify only basic features and most important characteristics, and may not be used to identify all features/parameters of the CPU. For example, model numbers never identify CPU ID, core stepping, core voltage, maximum CPU temperature and a few other parameters. If you need to find out all details on specific processor please use sSpec numbers for Intel processors or order product numbers for AMD microprocessors.
For more information on Intel model numbers please see Intel processor (model) numbers.
For more information on AMD model number please see Athlon XP, Athlon 64, Sempron and Turion model number and Opteron model numbers.
This post is just to show the images and some additional information for a few items I have decided to part with. If you have any questions please refer to the listing that led you here. Sorry but I will not be answering questions from here.
Inline linking (also known as hotlinking, leeching, piggy-backing, direct linking, offsite image grabs and bandwidth theft) is the use of a linked object, often an image, from one site into a web page belonging to a second site. The second site is said to have an inline link to the site where the object is located.
Inline Linking and the HTTP Protocol
The technology behind the World Wide Web, the Hypertext Transfer Protocol (HTTP), does not make any distinction of types of links-all links are functionally equal. Resources may be located on any server at any location.
When a web site, such as Malagent’s Sandbox, is visited, the browser first downloads the textual content in the form of an HTML document. The downloaded HTML document may call for other HTML and/or stylesheet files to be processed. These files may contain <img> tags which supply the URLs which allow images to display on the page. The HTML code generally does not specify a server, meaning that the web browser should use the same server as the parent code (<img src=”picture.jpg” />). It also permits absolute URLs that refer to images hosted on other servers (<img src=”http://www.example.com/picture.jpg” />).
When a browser downloads an HTML page containing such an image, the browser will contact the remote server to request the image content. Continue reading ‘What is Inline linking?’
Mean time between failures (MTBF) is the mean (average) time between failures of a system, and is often attributed to the “useful life” of the device i.e. not including ‘infant mortality’ or ‘end of life’ if the device is not repairable. Calculations of MTBF assume that a system is “renewed”, i.e. fixed, after each failure, and then returned to service immediately after failure. The average time between failing and being returned to service is termed mean down time (MDT) or mean time to repair (MTTR).
Mathematically, the MTBF is the sum of the MTTF (mean time to failure) and MTTR (mean time to repair). The MTTF is simply the reciprocal of the failure rate, Continue reading ‘Mean time between failures’
As a technician, system administrator and all around super geek, I have told others over and over again to back up their data. Sometimes my own advice is a bit hard to follow, ya know how it is - you get busy looking through Flickr, debating politics or whatever and the next thing you know. ZAP, just like that, all your really important irreplaceable data that you just happen to need right now is gone.
This normally would not be an issue for me, but this drive is not usually on my Mac protected by the Leopard’s Time Machine. This drive comes from a Windows 2003 Server from my little data center. At least the Mac is letting me copy the data whereas Windows just freaks out and goes into a BSOD spewing tantrum.
So there they sit, billions and billions of useless ones and zeros doing nothing but making me mad.
So I’m off to wait on 280GB of data to copy (I wonder how long I’m gonna waste burning 64 DVDs?) so I can rip this damn drive out and smash it to pieces with a hammer. Then I will kick myself a few times for failing to practice what I preach. Oh, and don’t forget to back up your data, you never know when you are going to learn the meanings of MTBF, MDT, and MTTR.







