|
PureBytes Links
Trading Reference Links
|
<x-html><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<META content='"MSHTML 4.72.3612.1700"' name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT color=#000000 size=2>Guy,</FONT></DIV>
<DIV><FONT color=#000000 size=2></FONT><FONT size=2>
Jumping quicker to take a profit when you are trading against a trend does make
sense to me. Also, short moves tend to be hard and fast so taking a good
profit when you have it also makes sense there. The dumb move was mine,
closing AOL and SCH early when I was trading with the trend <G>. I
jumped back in this morning, but at a much higher level than I got
out.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>JimG</FONT></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: 5px">
<DIV><FONT face=Arial size=2><B>-----Original Message-----</B><BR><B>From:
</B>Guy Tann <<A
href="mailto:grt@xxxxxxxxxxxx";>grt@xxxxxxxxxxxx</A>><BR><B>To: </B><A
href="mailto:metastock@xxxxxxxxxxxxx";>metastock@xxxxxxxxxxxxx</A> <<A
href="mailto:metastock@xxxxxxxxxxxxx";>metastock@xxxxxxxxxxxxx</A>><BR><B>Date:
</B>Wednesday, March 24, 1999 6:00 PM<BR><B>Subject: </B>RE: 50%
Cash<BR><BR></DIV></FONT>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999>JimG</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999>Even a blind squirrel can stumble over an acorn in
the forest once in a while. <BG></SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999>After the way the market dropped, I worried that I
had taken my profits too soon. Now it's back to 1.40 points of where I
got out (basis close), so I won't have to listen to my brother about pulling
the trigger too fast.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999>The more I think about it, grabbing those early
profits when trading against our intermediate term trend makes a lot of
sense. At least you grab the money and don't have to sit there and
watch those paper profits evaporate. This was a real hard decision for
me as it's contrary to our paradigm that we've established over the last 40
years or so. Always in the market (unless stopped out), either long or
short, but always in. I guess all of us can learn. Meanwhile,
back with the 8 year old...</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999>Took Evan and the new puppy to the doggie park and
tried to tire them both out. Finally got to look at my e-mails around
4:30 PST. I don't know if I can make it through a 2 week Spring Break.
<G> Tomorrow's another busy day with no time to work on my
stuff. Porsche and BMW are both going in for service (BMW providing
the loaner) and then off to the new aquarium in Long Beach. Friday
will probably be Universal Studios since all of the other schools are still
in session. I'm tired just thinking about it.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999>Regards</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999>Guy</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999>Regards</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999>Guy</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999>Guy</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=840193101-25031999></SPAN></FONT> </DIV>
<DIV class=OutlookMessageHeader><FONT face="Times New Roman"
size=2>-----Original Message-----<BR><B>From:</B>
owner-metastock@xxxxxxxxxxxxx [mailto:owner-metastock@xxxxxxxxxxxxx]<B>On
Behalf Of</B> Jim Greening<BR><B>Sent:</B> Wednesday, March 24, 1999 7:08
PM<BR><B>To:</B> Metastock<BR><B>Subject:</B> 50% Cash<BR><BR></FONT></DIV>
<DIV><FONT color=#000000 size=2>All,</FONT></DIV>
<DIV><FONT color=#000000 size=2> I was stopped out
of AMZN and WMT this morning. I didn't like the look of the market so
I decided to go to 50% cash and also closed AOL and SCH. Judging by
the close, I may have over reacted and made a mistake. The good news
is that I can always get back in <G>.</FONT></DIV>
<DIV><FONT color=#000000 size=2> Guy, that was a
great short call. Let me know when you go back
long.</FONT></DIV>
<DIV><FONT color=#000000 size=2></FONT> </DIV>
<DIV><FONT color=#000000 size=2>JimG</FONT></DIV></BLOCKQUOTE></BODY></HTML>
</x-html>From ???@??? Fri Mar 26 05:11:35 1999
Received: from listserv.equis.com (204.246.137.2)
by mail02.rapidsite.net (RS ver 1.0.2) with SMTP id 7686
for <neal@xxxxxxxxxxxxx>; Fri, 26 Mar 1999 00:06:28 -0500 (EST)
Received: (from majordom@xxxxxxxxx)
by listserv.equis.com (8.8.7/8.8.7) id MAA00948
for metastock-outgoing; Fri, 26 Mar 1999 12:41:50 -0700
X-Authentication-Warning: listserv.equis.com: majordom set sender to owner-metastock@xxxxxxxxxxxxx using -f
Received: from freeze.metastock.com (freeze.metastock.com [204.246.137.5])
by listserv.equis.com (8.8.7/8.8.7) with ESMTP id MAA00945
for <metastock@xxxxxxxxxxxxxxxxxx>; Fri, 26 Mar 1999 12:41:48 -0700
Received: from send205.yahoomail.com (web131.yahoomail.com [205.180.60.174])
by freeze.metastock.com (8.8.5/8.8.5) with SMTP id VAA04146
for <metastock@xxxxxxxxxxxxx>; Thu, 25 Mar 1999 21:35:02 -0700 (MST)
Message-ID: <19990326042344.1884.rocketmail@xxxxxxxxxxxxxxxxxxxxx>
Received: from [205.180.60.175] by web131.yahoomail.com; Thu, 25 Mar 1999 20:23:44 PST
Date: Thu, 25 Mar 1999 20:23:44 -0800 (PST)
From: Rajat Bose <rajatkbose@xxxxxxxxx>
Subject: Re: General Protection fault - FM. South Africa
To: metastock@xxxxxxxxxxxxx
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-metastock@xxxxxxxxxxxxx
Precedence: bulk
Reply-To: metastock@xxxxxxxxxxxxx
X-Loop-Detect: 1
X-UIDL: ed20f863660b8a5f85179eb8fb33d74f.50
Thanks Ton, for your illuminating letter. It would also help me since I
still do face this problem sometimes.
Regards,
Rajat K Bose
--- "A.J. Maas" <anthmaas@xxxxxx> wrote:
> Since your attempt here to explain the Windows OS
> environment is
> somewhat right but not exactly precise, find some of
> the "corrected"
> parts below.
>
> Regards,
> Ton Maas
> ms-irb@xxxxxx
>
> ----- Original Message -----
> From: Rajat Bose <rajatkbose@xxxxxxxxx>
> To: <metastock@xxxxxxxxxxxxx>
> Sent: donderdag 25 maart 1999 5:49
> Subject: Re: General Protection fault - FM. South
> Africa
>
>
> > Hi NAD,
> >
> > Regarding your first problem I think others have
> already solved the
> > problem. I would like to share some of my findings
> about your second
> > problem: Genral Protection Fault (GPF).
> >
> > This is a fairly common problem with all versions
> of Windows. Though you
> > would get the message that the program has
> performed some illegal
> > operation and Windows is closing down or a straight
> GPF message at
> > certain memory address.
>
> This is not a fairly common problem in the Windows
> Operating System,
> but is ONLY related to problems caused by OTHER
> software programs using the
> Windows OS-environment and happen when these programs
> are "attacking"
> on the processor's memory pages capacities or
> auto-create invalid actions
> (like closing down "writing" problems) that would
> cause damages done to
> the Processor and/or to the BIOS and/or to the NTSF /
> FAT-files(eg the hard-disc
> file, depending on the OS being used).
> These "malfunctioning" other programs' actions are
> rightious PROTECTED by the
> Windows' OS and this is explicitely present to saving
> you, the user, from any costly
> damages done to the "hardware", that can lead into
> replacing the costly hardware
> (bios, processor, disc) or having to re-install the
> discs' OS again.
>
> >One reapeated occurrence, you are asked to contact
> the program vendor.
>
> Right you should, if any of your own attempts in
> trying to fix the core problem(s) that
> have caused or are causing the invalid action(GPF),
> in the first place, have failed.
>
> > However, the problem lies more with any other
> software than the software
> > in question. In Windows memory allocation system
> certain hierarchies are
> > there for different types of programs. When a
> program normally meant for
> > lower hierarchy memory address tries to access or
> have already accessed
> > a higher level memory address the problem occurs.
>
> Apart from the above described reason as to why GPF's
> or invalid actions ocure,
> it then happens to/on any OS system, no matter what
> system is being used, eg will
> it be the BIOS, old DOS, UNIX, Linux, Apple etc., as
> they (the OS) are at that time
> "the controlers" over the hardware and (only
> policing) their environment.
>
> > There is no cure for this problem as of now.
>
> Ofcourse there is a cure !!!
> Cure is to find out the reason why the GPF or invalid
> actions are caused in the first
> place. These GPF or invalid actions can for instance
> happen, when you try to save
> a file, and the saving here should be read as 1.
> writing to disc and 2. shutting down
> the program.
> Then from this saving, if your file contains your own
> "faulty" instructions, eg instructions
> that are impossible to be processed, eg the illegal
> operations, these then can be due
> to your "impossible at that time" wrong alterations
> made to the to be saved file and/or
> due to your program manufacturers' faulty "writing
> the code", eg program code with
> "faulty" instructions.
> For example, the very first Metastock "Patch-up to
> 6.52a" failure editions(1+2) patched
> up files contained the wrong writing code (Apart from
> the Patch's process themselves),
> and results were GPF or invalid actions (and other
> missing "this and thats").
>
> > As of now, all you can do is to have larger RAM
> available
>
> There is a limit as to how much larger RAM will still
> work as a solution for systems'
> memory shortage only. Basicaly, installing 128Mb for
> Win95 is installing 64Mb too many.
> The overflow-ing Memory RAM larger than 64Mb will
> automaticaly (see below) have it
> dump the "overflow" (get written) in (to) the
> "Win386.swp" file, eg the SWAP-file also
> known as (the) virtual memory (file-found in the
> Drive's Main folder).
>
> > and load less of memory resident programs.
>
> This is only one way of freeing some of the OS's
> system resources(memory) that
> would otherwise be in use, but is not the cure to
> solve GPF or invalid actions(see above).
>
> > Increase RAM so far as practicable. Second, have
> atleast four
> > times of free hard disk space in which Windows
> creates its swap file.
>
> Increase RAM to maximum of 64Mb(for Win95 OS) only,
> more will not be used
> (at all or not that often) by the OS.
> The maximum free available space required for the
> virtual memory file(SWAP-file,
> see above) only has to be twice(2x) the size of the
> installed physical RAM(see above),
> eg 64Mb RAM is always a maximum SWAP-file's size of
> 128Mb.
> Alternatively, you can also set the maximum virtual
> memory(SWAP-file) size, by
> switching off the control that Win95 standard
> automaticaly has over this (virtual
> memory) feature, this can be done on the Performance
> TAB (Control Panel|System|
> Performance|Virtual Memory) and use the option that
> is given to manualy control
> the SWAP-file's size to a fixed setting, eg the 128Mb
> can here then be set to 150Mb,
> and can even be set to a seperate <for the SWAP-file
> alone> partition, eg a Drive X
> of 150Mb (max).
> Microsoft does not recommend untrained users to alter
> this option, other than to
> keep it at the standard Automaticaly (maintained by
> Win95 OS) pre-set option,
> installed by the Windows 95 Set-Up program. (source
> Microsoft Knowledge Base).
>
> > I was facing this problem with MetaStock 6.5 while
> using that on a
> > Compaq Presario 2200 with 44MB RAM and 160 MB free
> space on the disk.
> > This problem becomes severe when you are using
> other big programs like
> > MS EXCEL and/or MS WORD along with MetaStock 6.5
> and you switch among
> > them quite often.
>
> Excel,Word, (any Picture Programs)
> Scanner,Printer,Image and Graphical like
> Metastock are standard basicaly memory consuming
> programs (these programs'
> operating program files alone are stack-filled with
> the enourmous amount of "writing+
> codes", eg the instructions for these programs'
> (executionable) general usages.
> But also very memory consuming are their "other" (the
> working files+contents) that
> are being/getting loaded, eg the working file(s) that
> are then being used for viewing
> or altering etc. purposes.
>
> > If you require more technical details, I can
> provide that to the extent
> > I can. If my suggestion helps it would be very
> nice.
> >
> > Thanks
> >
> > Rajat K Bose
>
> ===========================================
> > --- NAD <nad@xxxxxxxxxxx> wrote:
> > > Please can u assist. I have just tried to
=== message truncated ===
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|