home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!PKSMRVM.VNET.IBM.COM!KENKAHN
- From: KENKAHN@PKSMRVM.VNET.IBM.COM ("Kenneth A. Kahn")
- Newsgroups: comp.os.os2.misc
- Subject: Re: Autoexec.bat (problem?)
- Message-ID: <9208311815.AA09490@ucbvax.Berkeley.EDU>
- Date: 31 Aug 92 18:02:58 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Lines: 26
-
- Organization: Staff of IBM Fellow - NetWork Computing
- Disclaimer: This posting represents the poster's views, not those of IBM
- News-Software: UReply 3.0
- X-X-From: KENKAHN@PKSMRVM.VNET.IBM.COM (Ken Kahn)
- References: <1992Aug31.133951.3736@spcvxb.spc.edu>
-
- In <1992Aug31.133951.3736@spcvxb.spc.edu> mauritz_c@spcvxb.spc.edu writes:
- >Hello!
- >
- >I've noticed that when I run an OS/2 fullscreen session, the
- >autoexec.bat file does not get executed automatically. Is this
- >normal behavior? If so, how do I make it execute when I start
- >an OS/2 session?
- >
-
- The AUTOEXEC.BAT file is *only* run when starting a DOS Session, not an OS/2
- session. If you want certain actions performed when starting an OS/2 Window
- or Full Screen session, edit the SESSION parameters for the associated object
- and where it says optional parameters, add "/K xxxxxx" where xxxxx is one or
- more OS/2 commands separated by &; just like you can for a regular OS/2
- command prompt.
-
- Example: /K (MODE CO80,50) & (CD E:\TEST)
-
- This will start the session in 50 line mode and the default directory will be
- E:\TEST
-