Recent Posts
But in a related vein, chocolate covered pretzels are incredible.-mouser (December 17, 2013, 10:30 AM)
You wouldn't. ... we're thinking the same lines, aka useless faux hardware. I just am not leet enough to have a Jornada.
<<Tao worships App for 17 minutes>>-TaoPhoenix (December 15, 2013, 06:02 PM)
Cell phone crashing at the airport.
At first I thought it was only slightly amusing, but as it went on I couldn't help smiling and laughing more and more.-Deozaan (December 15, 2013, 04:33 PM)
Now, that might be a reason for me to have a cell phone. I wouldn't even have to pay for service to do that.-app103 (December 15, 2013, 05:52 PM)
Heh yeah App, you can get a fake discarded cell phone for like ten bucks, right? "...Entertainment ... priceless!"
P.S. You can annoy Flight Attendants with it... when they ask you to "turn off your cell phone" you can rip it in half! "There. Satisfied??!" : )-TaoPhoenix (December 15, 2013, 05:54 PM)
Cell phone crashing at the airport.
At first I thought it was only slightly amusing, but as it went on I couldn't help smiling and laughing more and more.-Deozaan (December 15, 2013, 04:33 PM)
Remember: "It's not only the cream that rises to the top."-40hz (December 13, 2013, 05:49 PM)
Are you trying not to say shit floats?-Stoic Joker (December 13, 2013, 06:57 PM)
"Anti-malware for men: $25 for basic anti-malware, but for only $200 extra you can get path-programmable lasers; or an extra $25 on top of that for extra power lasers. Add another $50 for extreme-effect audible alerts. Or buy the Master-Defender Elite Lifetime Edition for only $500."-mouser (December 10, 2013, 12:36 PM)
Late last year, Panda Security released a Social Media Risk Index that shows Facebook was the leader in malware threats at 71.6 percent, YouTube came in at 41.2 percent and Twitter recorded a 51 percent risk for privacy violations. And 33 percent of SMBs who typically have security technology in place for their users report financial losses to their business as a result of social media-based malware infection. According to a new study from comScore, more women use social networking sites and spend more time on these sites than men do. The study concluded that 76 percent of women spent time on social media sites compared with 70 percent of men, and women spent 5.5 hours a month on these sites compared to only 4 hours a month for men.
Found on Chicalogic press release
I can see their logic from a business aspect to use the same appeal for woman products with security software to try and get more users to actually use some protection.-hollowlife1987 (December 10, 2013, 09:26 AM)
I'll bet these guys (you know they're guys) are really popular with the ladies and get invited to all the 'good parties' with an attitude like that.
-40hz (December 10, 2013, 10:15 AM)
Using Malwarebytes’s proven technology, ChicaPC-Shield™ was designed for women by employing straightforward language and processes to make installation and usability fast, simple and completely accessible.-40hz (December 10, 2013, 10:15 AM)
Note: showed the press release to my GF. She didn't say anything. But the expression on her face spoke volumes.-40hz (December 10, 2013, 10:15 AM)
I heard it was Strong Enough for a Man, Made for a Woman. If you run that av it's no sweat from then on.But how it works is a secret.
-MilesAhead (December 10, 2013, 09:50 AM)
The Password and NoDecompile options do nothing to prevent decompilation.-vbmark (December 04, 2013, 07:31 AM)
To be fair, they used to. Lexikos (current AHK dev) took out that functionality in v1.1.01+.-skwire (December 04, 2013, 08:31 AM)
(see attachment in previous post)-rgdot (December 02, 2013, 11:02 AM)
Someone needs to teach that kid that everything after the last slash is completely unnecessary.-app103 (December 02, 2013, 12:11 PM)
Maybe it's so he could get referral money from Santa also!-wraith808 (December 04, 2013, 06:09 AM)
A script compiler (courtesy of Jonathan Bennett's AutoIt v3 source code) is included with the program. AutoIt v2 scripts are not supported, so if necessary, first auto-convert your .aut file to .ahk.
Once a script is compiled, it becomes a standalone executable; that is, it can be used even on machines where AutoHotkey is not installed (and such EXEs can be distributed or sold with no restrictions). The compilation process compresses and encrypts all of the following: the script, any files it includes, and any files it has incorporated via the FileInstall command.
Compiling does not improve the performance of a script. In fact, a compiled script is slightly slower to launch because it must first be decrypted and decompressed into memory, after which it is optimized just like a normal script.
Ahk2Exe can be used in the following ways:
1. GUI Interface: Run the "Convert .ahk to .exe" item in the Start Menu. In v1.0.46.10+, the password N/A may be specified within the GUI interface to prevent exe2ahk from being able to decompile the script. This works only in the GUI interface; for the command line, use the /NoDecompile switch instead.
2. Right-click: Within an open Explorer window, you can right-click any .ahk file and select "Compile Script" (only available if the script compiler option was chosen when AutoHotkey was installed). This creates an EXE file of the same base filename as the script, which appears after a short time in the same directory. Note: The EXE file is produced using the same custom icon and compression level that was last used by Method #1 above and it will not have a password.
3. Command Line: The compiler can be run from the command line with the following parameters:
Ahk2exe.exe /in MyScript.ahk [/out MyScript.exe][/icon MyIcon.ico][/pass password][/NoDecompile]
For example:
Ahk2exe.exe /in "MyScript.ahk" /icon "MyIcon.ico" /pass "CustomPassword" /NoDecompile
Usage:
- Parameters containing spaces should be enclosed in double quotes.
- If the "out" file is omitted, the EXE will have the same base filename as the script itself.
- In v1.0.46.10+, the /NoDecompile switch (if present) prevents exe2ahk from being able to decompile the script even when the correct password is given. This provides an additional layer of protection that goes beyond having a long, elaborate password.
Notes:
- If you plan to distribute your EXE and don't want anyone to be able to view the source code of your script, you get the maximum protection by compiling at the command line with the /NoDecompile switch, and also specifying a long, elaborate password. A password's maximum length is 64 characters.
- The commands #NoTrayIcon and "Menu, Tray, ShowMainWindow" affect the behavior of compiled scripts.
- An EXE can be decompiled to retrieve the original script by downloading Exe2Ahk (this utility should be run from the command prompt). However, any comments originally present (semicolon or /**/) will be lost.
- Compiled scripts can be reduced in size by about 20 KB by placing this smaller version of the AutoHotkeySC.bin file in your AutoHotkey\Compiler folder (overwriting the existing file of the same name). Any compiled script produced in this fashion will be dependent on MSVCRT.dll. Although this DLL is always present on Windows 2000/XP or later, older operating systems do not necessarily have it.
- Custom version info (as seen in Explorer's file-properties dialog) can be added to your compiled scripts by using a utility such as Resource Hacker (freeware) to edit the file "AutoHotkeySC.bin". This file is contained in the "compiler" subfolder where AutoHotkey was installed. Note: Resource Hacker will corrupt compiled scripts, which is why only the AutoHotkeySC.bin file should be edited.
- The method above can also be used to change existing icons or add new ones to all compiled scripts.
- The built-in variable A_IsCompiled contains 1 if the script is running in compiled form. Otherwise, it is blank.
- If you do not wish your compiled scripts to be compressed, delete or rename the file "upx.exe" in AutoHotkey's "Compiler" folder.
- When parameters are passed to Ahk2Exe, a message indicating the success or failure of the compiling process is written to stdout. Although the message will not appear at the command prompt, it can be "caught" by means such as redirecting output to a file. [v1.0.43+]
(see attachment in previous post)-rgdot (December 02, 2013, 11:02 AM)
What is the responsibility here?
If I know processed meat is bad for me, researched and told by government panel or even not, but can't afford to buy non-processed/organic everybody should remain silent about it until the end of time? Will the company producing the processed version do me the favor without a push?-rgdot (November 25, 2013, 05:08 PM)
In 1985, concern developed in the U.S. public over the use of Alar on apples, over fears that the residues of the chemical detected in apple juice and applesauce might harm people. The outcry led some manufacturers and supermarket chains to announce they would not accept Alar-treated apples.
The Natural Resources Defense Council had for years urged the EPA to ban daminozide and in a 1989 report, largely using the government's own figures, they reported that on the basis of a two-year peer reviewed study children were at "intolerable risk" from a wide variety of potentially lethal chemicals, including daminozide, that they ingest in legally permissible quantity. By their estimate "the average pre-schooler's exposure was estimated to result in a cancer risk 240 times greater than the cancer risk considered acceptable by E.P.A. following a full lifetime of exposure."[4]
In February, 1989 there was a broadcast by CBS's 60 Minutes highlighting a report by the Natural Resources Defense Council highlighting problems with Alar (daminozide).
This followed years of background work. According to Environmental Working Group:
Prior to 1989, five separate, peer-reviewed studies of Alar and its chemical breakdown product, unsymmetrical dimethylhydrazine (UDMH), had found a correlation between exposure to the chemicals and cancerous tumors in lab animals. In 1984 and again in 1987, the EPA classified Alar as a probable human carcinogen. In 1986, the American Academy of Pediatrics urged the EPA to ban it. Well before the 60 Minutes broadcast, public concern had already led six national grocery chains and nine major food processors to stop accepting apples treated with Alar. Washington State growers had pledged to voluntarily stop using it (although tests later revealed that many did not). Maine and Massachusetts had banned it outright.[5]
In 1989, following the CBS broadcast, the United States Environmental Protection Agency (EPA) decided to ban Alar on the grounds that "long-term exposure" posed "unacceptable risks to public health." However before the EPA's preliminary decision to ban all food uses of Alar went into effect, Uniroyal, the sole manufacturer of Alar, agreed in June 1989 to halt voluntarily all domestic sales of Alar for food uses.[6]
Apple growers in Washington filed a libel suit against CBS, NRDC and Fenton Communications, claiming the scare cost them $100 million.
