Debian Codegraph @

README.W32

raw
1 Regina for Windows 2000/XP/Vista/7
2
3 This distribution contains 32 bit executables of the Regina Rexx interpreter
4 for Windows 2000/XP/Vista/7, and some sample programs, most of which are designed to test
5 new features of this interpreter.
6
7 Note that this version does not work on older versions of Windows such as Win9x/NT/Me.
8 This limitation is based on wanting to include support for handling files larger than 2gb
9 in size. To support this a recent version of the MS compiler was required and binaries
10 produced by that compiler do not support older versions of Windows.
11
12 Regina is distributed under the GNU Library General Public Licence.
13 See COPYING-LIB for details.
14
15 This port of Regina to Windows 2000/XP/Vista/7 differs from the port of Regina on the
16 Windows NT Resource Kit in two ways:
17
18 1) This port is sanctioned by the author of Regina, Anders Christensen.
19 2) This port does not provide any OLE or Win32 support nor does it
20 provide builtin access to the Registry. It does however, provide the
21 standard Rexx API. This enables C programs written under OS/2 and
22 Unix that use the standard API, to be easily ported to Windows 2000/XP/Vista/7.
23 It also means that C programs written using Quercus Rexx and Object
24 Rexx under Windows 2000/XP/Vista/7 to be recompiled using Regina, and C programs
25 written for Regina to be recompiled using Quercus Rexx or Object
26 Rexx.
27 The Win32 functions that were built into Regina on the Resource Kit are
28 available as an external function package from http://www.interlog.com/~ptjm
29
30 The files in this archive are:
31
32 README - this file
33 README.3x - readme files for 3.x releases of Regina
34 README_SAFE - details on using Regina is "safe" mode
35 COPYING-LIB - GNU Library General Public Licence
36 file_id.diz - Description file for BBS use
37 regina.exe - 32bit Regina Rexx interpreter executable
38 regina.dll - 32bit Regina Rexx interpreter dynamic library
39 rexx.exe - Regina executable - does not require regina.dll
40 regutil.dll - 32bit Regutil dynamic library
41 *.mtb - Native Language message files
42 msvcr100.dll - MS Visual C++ Runtime v10
43
44 ** The following are included if you requested demo programs option on install **
45 demo\rxtest1.dll - Sample external function packages; used by dynfunc.rexx
46 demo\rxtest2.dll demo Rexx program
47 demo\*.rexx - Sample Rexx programs
48
49 ** The following are included if you requested documentation option on install **
50 doc\regina.pdf - Regina documentation
51 doc\regutil.pdf - Regutil documentation
52
53 ** The following are included if you requested development option on install **
54 include\rexxsaa.h - Header file for access to regina.dll
55 lib\regina.lib - Import library for Visual C++
56 lib\rexx.lib - Static library for Visual C++
57
58 The remainder of this section is relevant only if you are not installing
59 Regina via the self-extracing installation.
60
61 Installation is simply a matter of copying the regina.exe and regina.dll
62 files into a directory specified in your PATH environment variable.
63
64 If you want to have Regina error messages displayed in you native
65 language, set the environment variable; REGINA_LANG to the two-character
66 language abbreviation (the first two chracters of a file in the NLS
67 directory), and set REGINA_LANG_DIR to the directory containing the
68 *.mtb files.
69
70 If you wish to be able to run Rexx programs automatically, ie without
71 specifying the regina.exe or the file extension, then run the following
72 Windows commands from a command prompt: (you only need to do this once)
73
74 C:\> ftype Regina=c:\regina\regina.exe "%1" %*
75 C:\> assoc .rexx=Regina
76 C:\> set PATHEXT=%PATHEXT%;.rexx
77
78 The above commands assume that regina.exe is in c:\regina and that you
79 only want to execute Rexx programs that have an extension of .rexx.
80 Add another ASSOC command to associate files with other extensions.
81
82 You will probably want to set the PATHEXT variable in the Environment
83 section of the System Control Panel applet.
84
85 Using this build of Regina with other Win32 Compilers
86 =====================================================
87 Nearly every C compiler on the Win32 platforms generates object code that
88 is incompatible with one another. So using this build of Regina with a
89 C compiler other than MS Visual C/C++ requires that you link with the
90 import library appropriate to your compiler. The following provides
91 instructions on how to build import libraries for a couple of Win32
92 compilers.
93 Run these commands from a directory other than where the original regina.lib file exists.
94 In the commands below that is assumed to be c:\regina.
95
96 Cygwin and MingW32
97 ------------------
98 Command:
99 dlltool -A -k --input-def c:\regina\regina_w32_dll.def --dllname c:\regina\regina.dll --output-lib libregina.a
100 Import Library:
101 libregina.a
102
103 Borland 5.5
104 -----------
105 Command:
106 impdef tmp.def c:\regina\regina.dll
107 -- you need to edit tmp.def with a text editor and remove lines containing a question mark: '?'
108 implib -w regina.lib tmp.def
109 Import Library:
110 regina.lib
111
112 ADRRESS WITH
113 ============
114 Redirection of program's input and/or output in general is relatively
115 predictable on most operating systems, however mention must be made of
116 behaviour specific to the Windows platform.
117
118 Windows and to a lesser degree OS/2, have techniques to hide windows,
119 to start programs in separate windows and other cool features. Florian
120 did some significant testing of this on all different Windows platforms
121 and there is bad news. There is no consistent mechanism to start external
122 programs without error and full control. Sounds strange, is strange.
123 We have the options to:
124
125 1) use the interpreter (ADDRESS SYSTEM) or not (ADDRESS PATH or CMD)
126 2) start GUI or text mode programs
127 3) choose the interpreter (CMD.EXE or COMMAND.COM)
128
129 The main goal was to start GUIs separately and text mode programs under the
130 control of the caller (GUI or text). Regina can be part of a GUI process
131 and must be treated as GUI in this case. Most people get upset with console
132 windows popping up showing nothing.
133
134 Some combinations of the interpreter, the target programs, and the options
135 we can pass along to the system lead to nonstarting, nonstopping, crashing
136 programs. Or we may loose control by means of broken communications to the
137 subprocess (ADDRESS WITH...).
138
139 ATTENTION: Your programs might crash or you may loose control either of the
140 called program or of Regina if you change the interpreter inside your Rexx
141 program. Never use
142 CALL VALUE 'COMSPEC', something, 'SYSTEM'
143 in your program if you don't know the consequences! Unpredictable behaviour
144 is likely to occur; use at your own peril!
145
146 Regina Resources
147 ================
148 For more information on Regina, visit the Regina Home page at
149 http://regina-rexx.sf.net
150
151
152 If building Regina from source, always unzip the source to convert the
153 Unix end of line characters to Win32 carriage return/end of line characters.
154 With InfoZip, this is "unzip -a".
155
156 Cheers, Mark.
157 ------------------------------------------------------------------------
158 * Mark Hessling, [email protected] http://www.rexx.org/
159 * Author of THE, a Free XEDIT/KEDIT editor and, Rexx/SQL, Rexx/CURL, etc.
160 * Maintainer of Regina Rexx interpreter and Rexx/Tk
161 * Use Rexx? join the Rexx Language Association: http://www.rexxla.org/
162 ------------------------------------------------------------------------