Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Intel Corporation (INTC) -- Ignore unavailable to you. Want to Upgrade?

To: wanna_bmw who wrote (170467)	9/1/2002 12:39:02 PM
From: Win Smith	Read Replies (2) \| Respond to of 186894

Van gave precise directions for getting at what sysmark was actually doing in vanshardware.com How-to Really Unlock SysMark As I wrote above, Tom is not very "technical" and the instructions he gave to unlock SysMark, are predictably incorrect. Specifically, the commandline instructions necessary to run SysMark 2002 contain the same typographic error sent to all reviewers (so much for Tom's editing). Here are the two corrected commandlines: For Internet Content Creation, from the "Run" dialog enter: sysmgr -NOREBOOT -ICCSUITE=1 PROJNAME=icchacked For Office Productivity, from the "Run" dialog enter: sysmgr -NOREBOOT -OPSUITE=1 PROJNAME=ophacked The actual project names are not important. The key to "unlocking" SysMark 2001/2002 is to cause it to halt immediately prior to completion. SysMark logs the results from the individual tests in the temporary file "c:\Program Files\BAPCo\SysMark2002\Reports\_measurement.txt". By adding the bogus command "die" to the end of the execution scripts "SEQUENCE.txt" (one for each suite) you force SysMark to generate an error and halt, exposing "_measurement.txt" for examination. Somehow, I find his analysis more convincing than self-serving blather by Intel employees.