🚀 go-pugleaf

rsl11@kuhub.cc.ukans.edu writes:
>
>2. I have aproblem with the path statement of dos.
>If I type the following statement in the dos prompt
>PATH = C:\DOS; C:\WINDOWS; C:\STACKER;
>in capital letters it works but if I put it in a batch file such as the
>autoexec.bat file it tells me "Too many parameters". Does anybody have any
>ideas as to what the problem might be?

First, ditch the spaces.  Second, leave off the last semicolon; you only
need it between paths, not after each path.  Case should be irrelevant; DOS
shifts everything to upper case before parsing it.

Try this:

Path=C:\DOS;C:\Windows;C:\Stacker

Good Luck.
-- 
------------------------------------------------------------------------------
Rick Rutledge              {hoptoad|ucsfcca}!wet!rick            rick@wet.UUCP
"Voici le secret." dit le renard.  "On ne voit bien qu'avec le coeur.
L'essentiel est invisible aux yeux." -Antoine de St. Exupery, _le Petit Prince_

> 2. I have aproblem with the path statement of dos.
> If I type the following statement in the dos prompt
> PATH = C:\DOS; C:\WINDOWS; C:\STACKER;
> in capital letters it works but if I put it in a batch file such as the
> autoexec.bat file it tells me "Too many parameters". Does anybody have any

I think your problem is the trailing semi-colon.  I tried it just the way 
you have it and got the same response.  If I took out the trailing 
semi-colon, it worked just fine.


Mark Grant
----------
Internet:  grant@valinor.mystical.com   |  Prodigy:  XWXP36A
UUCP    :  uunet!valinor!grant          |  AOL    :  beachenguy
FidoNet :  1:366/48                     |  If that ain't enough!
----------
Communications...the first sign of brain activity!

rsl11@kuhub.cc.ukans.edu writes:

> a) devicehigh=c:\smartdrv.sys     in the config.sys file or
> b) loadhigh=c:\smartdrv.exe       in the autoexec.bat file

> What is the difference between the 2 statements?

SMARTDRV.SYS is an older version of SmartDrive.  SMARTDRV.EXE is the
latest version.  You should use the later version if you want enhanced
performance (using write caching).  However, you should NOT use the
LOADHIGH command, because SmartDrive will automatically load high, and
you should let it do that itself.

> Also, how much cache would be recommended to have with a total of 4MB ram when
> you run windows?

The default is 2 MB outside of Windows, 0.5 MB inside Windows.  This is
reasonable, but you can change it around if your applications are
different.

>2. I have aproblem with the path statement of dos.
>If I type the following statement in the dos prompt
>PATH = C:\DOS; C:\WINDOWS; C:\STACKER;
>in capital letters it works but if I put it in a batch file such as the
>autoexec.bat file it tells me "Too many parameters".

Remove the spaces after the semicolons (;), and remove the last
semicolon.  The equal sign (=) is also not necessary.

-- 
#ifdef TRUE        | Fuzzy Fox (a.k.a. David DeSimone)       fuzzy@netcom.com
#define  TRUE   0  |
#define  FALSE  1  |  "911 Emergency Rescue Service - Can you hold, please?"
#endif             |

In article <1993Jan11.164955.5961@rei.com> fox@rei.com (Fuzzy Fox) writes:
>rsl11@kuhub.cc.ukans.edu writes:
>
>> a) devicehigh=c:\smartdrv.sys     in the config.sys file or
>> b) loadhigh=c:\smartdrv.exe       in the autoexec.bat file
...
People have complained about the trailing semicolon in the orig poster's msg.
However, I have often heard rumors to the effect that it was a "Good Thing"
to have a trailing semicolon in your PATH - that there was some
bug/feature of DOS that made it parse the PATH faster if every
component, including the last, ended with a semicolon.  I have heard
this from "reputable sources", but I have never tested it.  I, myself,
don't like it - always thought the trailing semicolon was ugly.  I can't
however, imagine that it could cause a problem.  (Translation: I think
those people referred to in the first sentence of this paragraph have
been smoking something...)

>LOADHIGH command, because SmartDrive will automatically load high, and
>you should let it do that itself.

What about if you are using QEMM and its LOADHI command?  I know for a
fact that SMARTDRV.EXE (the one bundled with Windoze 3.1) does not
auto-loadhi under DOS 3.31 with QEMM.  (N.B. Some TSRs do so
auto-load-themselves-high; its not hard to do).

In that case, is it safe to LOADHI it?  (I have done so, mostly out of
fear... Disk caches scare me in general.)

************************************************************************
The Zapruder film was a snuff film.

	- pynq@quads.uchicago.edu, who is still costing the net
	  hundreds, if not thousands, of dollars, every time he posts -
************************************************************************

FYI, the Windows Resource Kit manual to Win 3.1 reccomends that you
Smartdrive be 1.5x the amount of RAM on your machine.
--Andrew