|
PureBytes Links
Trading Reference Links
|
Thanks, Rajat and Ton, this is good stuff. Please keep the discussion going
I'm sure the majority of us are learning from this.
Regards,
Ed
-----Original Message-----
From: A.J. Maas <anthmaas@xxxxxx>
To: metastock@xxxxxxxxxxxxx <metastock@xxxxxxxxxxxxx>
Date: Friday, 26 March 1999 10:32
Subject: Re: General Protection fault - FM. South Africa
>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 download
>> > (3days) when I get this information window showing
>> > that it is going to download 64 days.
>> > However, when retrieving a chart the data in the
>> > chart show until the last update i.e.. 3 days ago.
>> > It can not find a certain file and therefor trying to
>> > download the last 64 days. I have had this problem
>> > before , but can not remember how I fixed it, must
>> > have been by pure luck!!!
>> > If I just try to update from the Update Utility the
>> > following error message
>> > General Protection Fault :Metastoc.dll@xxxx:ocif
>> > running Metatstock 6.5 on Windows 95
>> > Please can u assist
>> > Thanks
>> > Dee
>> > South Africa
>> >
>> <HR>
>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
>> <HTML>
>> <HEAD>
>>
>> <META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
>> <META content='"MSHTML 4.72.2106.6"' name=GENERATOR>
>> </HEAD>
>> <BODY bgColor=#ffffff>
>> <DIV><FONT color=#000000 size=2>Please can u assist. I have just
>> tried to
>> download (3days) when I get this information window showing that it is
>> going to
>> download 64 days.</FONT></DIV>
>> <DIV><FONT color=#000000 size=2>However, when retrieving a chart the
>> data in the
>> chart show until the last update i.e.. 3 days ago.</FONT></DIV>
>> <DIV><FONT size=2>It can not find a certain file and therefor trying to
>> download
>> the last 64 days. I have had this problem before , but can not remember
>> how I
>> fixed it, must have been by pure luck!!!</FONT></DIV>
>> <DIV><FONT size=2>If I just try to update from the Update Utility the
>> following
>> error message</FONT></DIV>
>> <DIV><FONT size=2> General Protection Fault
>> :Metastoc.dll@xxxx:ocif</FONT></DIV>
>> <DIV><FONT size=2>running Metatstock 6.5 on Windows 95</FONT></DIV>
>> <DIV><FONT size=2>Please can u assist</FONT></DIV>
>> <DIV><FONT size=2>Thanks</FONT></DIV>
>> <DIV><FONT size=2>Dee</FONT></DIV>
>> <DIV><FONT size=2>South Africa</FONT></DIV></BODY></HTML>
>>
>>
>> _________________________________________________________
>> Do You Yahoo!?
>> Get your free @yahoo.com address at http://mail.yahoo.com
>>
>>
>
>
>
>
|