🚀 go-pugleaf

In article <2367@gara.une.oz.au> rbennet1@gara.une.oz.au (Ethyl the Aardvark) goes quantity surveying:
$     Could someone please tell me how to create .SYS files in MS-DOS so I can
$run certain software I have written myself from config.sys.Most of my 
$programming is done in Turbo Pascal 5.5,with a little done in Turbo C. 

   Get yourself a copy of _Advanced MS-DOS_ by Ray Duncan.  He discusses
how to write device drivers in a good level of detail.  You probably
won't be able to use Pascal for it, though, and I don't know how hard it
is in C.
-- 
   /Nikebo \ Nikebo says "Nikebo knows how to post.  Just do it."\silver@xrtll/
  /---------\_____________________________________________________\----------/
 /yunexus!xrtll!silver (L, not 1)\ Hi Ho Silver \   just silver for short   /
/Silver:  Ever Searching for SNTF \  Life sucks. \  someone buy me a BEER! /

In article <2367@gara.une.oz.au>, rbennet1@gara.une.oz.au (Ethyl the Aardvark) writes:
> 
>      Could someone please tell me how to create .SYS files in MS-DOS so I can
> run certain software I have written myself from config.sys.Most of my 
> programming is done in Turbo Pascal 5.5,with a little done in Turbo C. 
I am not sure I understand you request, but if all you want to do is run
an executable file that you have written, you could use the install command
which is in MS-DOS 4.01.  I don't know if other versions have it.

	install=[drive:][path]filename [parms]

That command will run the file.

-- cj

cjp@beartrk.beartrack.com (CJ Pilzer) writes:
$rbennet1@gara.une.oz.au (Ethyl the Aardvark) goes quantity surveying:
$>    Could someone please tell me how to create .SYS files in MS-DOS so I can
$> run certain software I have written myself from config.sys.Most of my 
$> programming is done in Turbo Pascal 5.5,with a little done in Turbo C. 
$I am not sure I understand you request, but if all you want to do is run
$an executable file that you have written, you could use the install command
$which is in MS-DOS 4.01.  I don't know if other versions have it.

   No, it's new in MS-DOS V4.  However, you can't just load in any file that
way.  There are some rules which must be followed; if you can find a book
that covers programming for DOS 4 at a technical level (the latest copy of
Duncan may do this), it will probably be able to help you out.
-- 
   /Nikebo \ Nikebo says "Nikebo knows how to post.  Just do it."\silver@xrtll/
  /---------\_____________________________________________________\----------/
 /yunexus!xrtll!silver (L, not 1)\ Hi Ho Silver \   just silver for short   /
/Silver:  Ever Searching for SNTF \  Life sucks. \  someone buy me a BEER! /

In article <1990Jul2.010333.268@xrtll.uucp>, silver@xrtll.uucp (Hi Ho Silver)
says:
>
>cjp@beartrk.beartrack.com (CJ Pilzer) writes:
>$rbennet1@gara.une.oz.au (Ethyl the Aardvark) goes quantity surveying:
>$>    Could someone please tell me how to create .SYS files in MS-DOS so I can
>$> run certain software I have written myself from config.sys.Most of my

Why do you want to run it from inside config.sys instead of autoexec.bat?

Anyway, I know you can invoke 1 program simply by doing

shell=progname

in Dos versions 3.X on up. I bet doing:

Shell=prog1
Shell=prog2
Shell=command.com ...

will work (as long as prog1 and prog2 terminate normally, but I can't swear
to it.) If it does work, Its a lot simpler than some other things mentioned.

Jeff

In article <90184.125712JXS118@psuvm.psu.edu> JXS118@psuvm.psu.edu (Jeff Siegel, Op from Atherton Hall) writes:

>   in Dos versions 3.X on up. I bet doing:
>
>   Shell=prog1
>   Shell=prog2
>   Shell=command.com ...
>
>   will work (as long as prog1 and prog2 terminate normally, but I can't swear
>   to it.) If it does work, Its a lot simpler than some other things mentioned.

Well, I've tried it long ago and it doesn't.  When config.sys is run,
the shell lines are the only ones which aren't carried out
immediately, instead they are copied to a buffer, every one overwritig
the last one so you only run the last shell

On dos 4.XX you can do:

Install=prog1
Install=prog2
Shell=command.com
--
Jose Pina Coelho        | BITNET/Internet: jpc@fctunl.rccn.pt
Rua Jau N 1, 2 Dto      | UUCP: jpc@unl.uucp
1300 Lisboa, PORTUGAL   | ARPA: jpc%hara.fctunl.rccn.pt@mitvma.mit.edu
Home phone: (+351) (1) 640767

- If all men were brothers, would you let one marry your sister ?

In article <90184.125712JXS118@psuvm.psu.edu> JXS118@psuvm.psu.edu (Jeff Siegel, Op from Atherton Hall) writes:
>in Dos versions 3.X on up. I bet doing:
>
>Shell=prog1
>Shell=prog2
>Shell=command.com ...
>
>will work (as long as prog1 and prog2 terminate normally, but I can't swear
>to it.) If it does work, Its a lot simpler than some other things mentioned.

Nope, this will not invoke prog1 or prog2.  I have lots of ``shell=''
lines in my config.sys and only the last one is used.  I move them
around when I want to boot with a different shell.
-- 
Andy Toy, Mortice Kern Systems Inc.,       Internet: andy@mks.com
  35 King Street North, Waterloo,       UUCP: uunet!watmath!mks!andy
      Ontario, CANADA N2J 2W9      Phone: 519-884-2251  FAX: 519-884-8861

In article <90184.125712JXS118@psuvm.psu.edu>, JXS118@psuvm.psu.edu
(Jeff Siegel, Op from Atherton Hall) writes:

[...]

> Anyway, I know you can invoke 1 program simply by doing
> 
> shell=progname
> 
> in Dos versions 3.X on up. I bet doing:
> 
> Shell=prog1
> Shell=prog2
> Shell=command.com ...
> 
> will work (as long as prog1 and prog2 terminate normally, but I can't swear
> to it.) If it does work, Its a lot simpler than some other things mentioned.
> 
> Jeff

I'm tired of these perfectly useless postings!

I wonder if you realise the number of people that will actually have to read
your message?  If you did, you would (I hope) avoid to publish your misunder-
standing of the meaning of the posting you were `following up' to, as well as
your wild guesses of `possiblie solutions'!

Your readers will fall into at least two categories:

1) those who will know that you don't know what you're talking about (they
   should simply skip your posting),
2) those who will think ``hey, that's a good thing to know!'' (before seeing
   your magnificient `... but I can't swear to it', that is.)  The day they
   will try to use your beautiful `undocumented feature', they will find out
   it doesn't work.

To both categories, your message has been useless and time-consuming.

As it turns out, you don't ``invoke'' a programm with `shell', you simply tell
what you want to execute *after* config' is done.  Guess you've lost your bet
(what do I win? :-)  (BTW: what is the `install' (DOS 4.0) command for?)

My point is simple enough:  Why didn't YOU try your `solution' before making
a fool of yourself worldwide?  Don't you understand that you're saying as much
as ``try the command `set PRN=filename' to redirect printer output to a file!
I bet it works (but I can't swear to it.)  If it does work, it's a lot simpler
than some other things mentioned.''

Sorry, bad mood today.


Markus Fischer     ---       fisher@sc2a.unige.ch or fisher@cgeuge52.bitnet

On the subject of the "shell=..." statement in config.sys -- is this
present before version 3.0?  I ask because it is described in the
Toshiba T1000 manual for the built-in DOS 2.11, but attemps to use it
have not seemed to work.
-- 

--R. T. Bumby ** Math ** Rutgers ** New Brunswick ** NJ08903 ** USA --
  above postal address abbreviated by internet to bumby@math.rutgers.edu
  voice communication unreliable -- telephone ignored -- please use Email

In article <Jul.6.15.00.32.1990.1996@math.rutgers.edu> bumby@math.rutgers.edu (Richard Bumby) writes:
>On the subject of the "shell=..." statement in config.sys -- is this
>present before version 3.0?  I ask because it is described in the
>Toshiba T1000 manual for the built-in DOS 2.11, but attemps to use it
>have not seemed to work.

I know that it has existed since DOS 2.0 and I am fairly certain that
DOS 1.x did not have it, but I don't have a DOS 1.x manual handy to
check it out.  `SHELL=' definitely works on a Toshiba T1000 because that
is what I have.  This is what I have in my CONFIG.SYS file and it works
(note that I use / for path delimiters since DOS 2.11 allows it in
config.sys and setting the switch character using the `switchar='
statement to some character other than / or \ in config.sys causes other
DOS commands to allow / too):

	switchar=-
	device=c:/dos/ansi.sys
	shell=a:/bin/sh.exe -L
-- 
Andy Toy, Mortice Kern Systems Inc.,       Internet: andy@mks.com
  35 King Street North, Waterloo,       UUCP: uunet!watmath!mks!andy
      Ontario, CANADA N2J 2W9      Phone: 519-884-2251  FAX: 519-884-8861