Correction [Re: [Mingw-msys] How to find MSYS]

[<jw...@bi...>]

> Sorry, but not thinking at all,  "merely a cartic of the common understanding".
Correction: cartic is cathartic.

---- "jw...@bi..." <jw...@bi...> wrote: 
> Sorry guys.
> That Strategy is called MAD: Mutually Assured Destruction.
> "Ignore history and you are doomed to relive it".
> It may not be illegal reverse engineering practice in the strictest sence.
> But it is still too close for comfort and bad practice.
> Microsoft software design engineers use Data flow and Process Flow and UML: Unified Modelling Language to create these "rat-runs". 
> It actually involves the exhaustive searching of a maze of corridors to find an Exit.
> Human intelligence is not up to it.
> To get an idea of the effort involved download the free SqueakNOS (No Operating System) image onto a floppy. Then at the cursor enter say:
> 	20 fatorial
> Then keep incrementing the value up or down.
> Just how mush time do you have? and then you still have no certainty.
> It is just not good logical thinking. 
> Sorry, but not thinking at all,  "merely a cartic of the common understanding".
> Now search on "what is carthic".
> If it is any comfort, I still do it myself.
> JW
> 
> ---- Leif W <war...@us...> wrote: 
> > > From: "Lennart Borgman" <len...@st...>
> > > Sent: 2005 October 03 Monday 08:24
> > >
> > 
> > >I just realized how to find MSYS when you do not know if it is 
> > >installed
> > 
> > [snip]
> > 
> > > Look in the Windows Registry at
> > >
> > > 
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
> > >
> > > There should be a key named something like
> > >
> > >    MSYS-1.0_is1
> > >
> > > if MSYS is installed. This in its turn has a string value with the 
> > > name
> > >
> > >    Inno Setup: App Path
> > >
> > > which tells where MSYS is installed. (Or you can look at 
> > > UninstallString.)
> > 
> > That may work fine for the current version of the installer, but the 
> > keys and strings may change for different versions of MSYS, or different 
> > installer tools (NSIS versus Inno Setup).  Maybe there's a more generic 
> > approach, or an installer convention that could be conceived?  Need to 
> > know if it's installed, perhaps status (e.g. ok, not configured, broken 
> > or half installed), location (drive or unc and path), and for MinGW with 
> > many optional components, perhaps the name of a file containing what's 
> > installed, along with some of this other info I mention.
> > 
> > Well, of course all of this assumes MSYS was installed with an 
> > installer, when conceivably it could be custom built and copied, or 
> > otherwise unarchived somewhere, in which case it's just guessing at 
> > standard path names across all drives or uncs, which is anybody's guess.
> > 
> > Anyways that's all speculative on my part.
> > 
> > Leif
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by:
> > Power Architecture Resource Center: Free content, downloads, discussions,
> > and more. http://solutions.newsforge.com/ibmarch.tmpl
> > _______________________________________________
> > Mingw-msys mailing list
> > Min...@li...
> > https://lists.sourceforge.net/lists/listinfo/mingw-msys
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Mingw-msys mailing list
> Min...@li...
> https://lists.sourceforge.net/lists/listinfo/mingw-msys