From owner-java@jp.FreeBSD.org Fri Mar  2 14:54:17 2007
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) id l225sHD12574;
	Fri, 2 Mar 2007 14:54:17 +0900 (JST)
	(envelope-from owner-java@jp.FreeBSD.org)
Received: from 202-177-154-253.sify.net (202-177-154-253.sify.net [202.177.154.253] (may be forged))
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) with ESMTP/inet id l225s2w12555
	for <java@jp.freebsd.org>; Fri, 2 Mar 2007 14:54:05 +0900 (JST)
	(envelope-from mistingaristarchus@siligom.com)
Received: from 72.14.247.27 (HELO alt2.aspmx.l.google.com)
     by smtp.siligom.com with (7.32.4/7.96.2) ESMTP id p160qxavyiujmc
     for java@jp.freebsd.org; Fri, 2 Mar 2007 05:54:07 -0330
From: "Matt Neylan" <mistingaristarchus@siligom.com>
To: <java@jp.FreeBSD.org>
Message-ID: <01c75c8f$31420f00$6c822ecf@mistingaristarchus>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Thread-Index: Aca8Q1oxg9a0w0pkfgkst158fig98p==
Reply-To: java@jp.FreeBSD.org
Precedence: list
Date: Fri, 2 Mar 2007 05:54:07 -0330
X-Sequence: java 2590
Subject: [java 2590] This one has unusial volume on thursday
Sender: owner-java@jp.FreeBSD.org
X-Originator: mistingaristarchus@siligom.com
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+060209

PUT THIS ONE ON YOUR HOT LIST.     
You don't saw what was happen ?
Thursday volume of ACEN has exceeded all records. 


Pick ACEN 
High $1.035    
Last sale on $0.75.  
Vol 561,673   



As you can see, investors finally valued the product and started to invest.   

Thursday morning it will start to increase again, because the company is too far from the real.  

Check your Level 2 market data.  You will see that this one is set for an explosion. 
With the huge publicity that is on the way THIS is where you want to be.    
Company news will come soon.   
























One more thing, this isn't the first, second, or even third major software problem has had at a big moment.  
> Why?  Why I ask?  Do you ask why?   
I hinted an earlier post that something might be very wrong with the software running larger tournaments.   
Mike is on the payroll, he gets paid to take the heat.  
Bad publicity can be a powerful thing especially when there are multiple complainers as in this case.  
There you want to catch your defects before they go into the field.  
(For example changing tables or some other behavior that causes a memory leak.)  
Especially if the tune is repetitive as is the case with.  




