|Date: ||Wed, 14 Feb 1996 11:03:15 EET|
|Reply-To: ||Arjen Raateland <raateland@VYH.FI>|
|Sender: ||"SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>|
|From: ||Arjen Raateland <raateland@VYH.FI>|
|Organization: ||National Board of Waters and the Environment|
|Subject: ||Re: The X statement under Windows|
In article <s11f90ea.048@GWSM.DOH.HEALTH.NSW.GOV.AU>, Tim CHURCHES
> When a DOS (i.e. non-Windows) programme is invoked using
> the X command or its equivalents ( i.e the system() function or
> the %sysexec macro call), the screen switches to
> full-screen text mode with an unpleasant click from some
> relays in my monitor, runs the DOS programme or command,
> then switches back to Windows graphs mode (more clicks
> and flickering). Ugly indeed. Windows NT and Windows 95
> don't do this - they pop up a DOS window but everything stays
> in graphics mode.
> My question: under Windows 3.x, is there a way making the X
> command start a DOS window in graphics mode rather than a
> full-screen text mode session? Windows 3.x is capable of
> doing this - if you "run" a PIF file which contains the DOS
> command you want to run and which has the "windowed"
> rather than the "full screen" check box selected, then all is
> well. However, you cannot invoke a PIF file using the SAS X
> command or equivalents.
I had to check just how I did it, but here it is:
Make a PIF-file called _default.pif and enter as the program name
_.bat. Press the In Window button under the Use heading. Perhaps there
is already a _default.pif file in your setup, but pressing the In
Window button does cause the X window to be a real window ...
The exact names of the items in the PIF editor may be different from
what I said above as I have only a Finnish language Windows.
--... ...-- -.. . --- .... ..--- --.. .- --..
Arjen Raateland, SAS Support
Finnish Environment Agency