Environment (OpenInsight 16-Bit Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
{{tag>category:"OpenInsight 16-Bit Specific"}}

[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== Environment (OpenInsight 16-Bit Specific) ====
=== At 13 JUN 2002 06:39:58PM Jonathan Bird wrote: ===
 
 
<QUOTE>
Short of using a batch file to pipe out the DOS environment to a file and reading the file, is there any way for OI to read environment variables?



J
</QUOTE>
----

=== At 13 JUN 2002 07:21PM Oystein Reigem wrote:  ===

<QUOTE>Jonathan,



There is a Windows function GETENVIRONMENTVARIABLE. Do a search.



- Oystein -



</QUOTE>

----

=== At 13 JUN 2002 08:29PM Richard Hunt wrote:  ===

<QUOTE>Jonathan,



You can call a DLL function (GetEnvironmentVariable or might be GetEnvironmentVariableA) from your stored proceedure (basic program). You might have to set up a DLL.



Follow these steps to crete the prototype record...



1) Create a row DLL_ONE (you can call it anything you want) by using the system editor. It should look like this...



KERNEL32

SHORT PASCAL GetEnvironmentVariableA(LPCHAR,LPCHAR,SHORT)



2) At the system editor exec line type RUN DECLARE_FCNS "DLL_ONE"



Now you can declare the function and call it like this...



DECLARE FUNCTION GETENVIRONMENTVARIABLEA

RESULT='DECLARE FUNCTION GETENVIRONMENTVARIABLEA

RESULT='

VARIABLE=windir':CHAR(0)

BUFFER=STR(CHAR(0),1000)

SIZE=1000

RESULT=GETENVIRONMENTVARIABLEA(VARIABLE,BUFFER,SIZE)



This will return...



RESULT=8

BUFFER=C:\WINNT' with CHAR(0)'s appended.

</QUOTE>

----

=== At 18 JUN 2002 07:36PM Jonathan Bird wrote:  ===

<QUOTE>Thanks Richard.

But calling kernel32 does not work from OI 16-bit. Is there another way, or another (16-bit) DLL to get the environment variables from?



J

</QUOTE>

----

=== At 19 JUN 2002 06:16AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:  ===

<QUOTE>Check out [url=http://www.revelation.com/__8525652b0066bfaf.nsf/0/dc2bd3d484db687d852568dc0045b6c9?OpenDocument&Highlight=2,GetDOSEnvironment]this link[/url]



[url=http://www.sprezzatura.com]The Sprezzatura Group[/url]

[i]World leaders in all things RevSoft[/i]

[img]http://www.sprezzatura.com/zz.jpg[/img]

</QUOTE>

----

=== At 19 JUN 2002 10:39PM Jonathan Bird wrote:  ===

<QUOTE>Yes, I already had a look at that link. Its all a bit Greek to me. How does it help? Perhaps I'm being a bit thick here ????



J

</QUOTE>

----

=== At 20 JUN 2002 09:36AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:  ===

<QUOTE>J,



Hey, I never realised I could speak Greek! :-)



OK, The first step is to prototype the GetDOSEnvironment function that's exported from the Windows Kernel which do you like so:



1) In the System Editor open the DLL_KERNEL record from the SYSPROCS table.

2) Add the following line:



   LPVOID PASCAL GetDOSEnvironment( VOID )



3) Save the record and in the system editor Exec line type



   RUN DECLARE_FCNS 'DLL_KERNEL'



and execute it.



You should now be able to call the GetDOSEnvironment function from Basic+.  Because of the way it works however you need to use some tricks to get the information back which is where the example function I wrote comes in:


<code>

declare function GetDOSEnvironment
envStr = ""
envLen = 2
lpEnv  = GetDOSEnvironment()
eof    = 0
loop
  envStr=getValue( lpEnv , Char, envLen )
  if envStr-2,2=\0000\ then
    // End of Environment variables
    eof=1
    envStr-2,2="
  end else
    envLen += 1
  end
until eof
repeat
convert \00\ to @Fm in envStr
* // EnvStr now contains a dynamic array of environment variables

</code>


Try it and see. What happens is that you get a pointer back that points to the start of the environment strings.  They are CHar(0) delimited and you know when you've got to the end because you come to two char(0)'s together.  As we are playing with pointers we have to use GetValue to de-reference them and get to the data they point at, but as we don't know the length we have to be careful we don't go too far and cause a GPF, hence checking 2 bytes at a time.



[url=http://www.sprezzatura.com]The Sprezzatura Group[/url]

[i]World leaders in all things RevSoft[/i]

[img]http://www.sprezzatura.com/zz.jpg[/img]

</QUOTE>

----

=== At 20 JUN 2002 05:43PM Jonathan Bird wrote:  ===

<QUOTE>Thanks,



My Greek is improving, a little. What I was missing was:

1) In the System Editor open the DLL_KERNEL record from the SYSPROCS table.

The rest made sense. Thanks a lot. All works now.



J

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=5D2F83EDD1E59A1C85256BD7007C8248|View this thread on the  forum...]]