(from Sam Ewalt):
Thanks, Clarence. Maybe it's time to ask for a checkup of my
config.sys--I'm using MS-DOS 6.22 on a 386dx33 with 8 megs and
want to optimize for Arachne.
Attached is my config.sys.
Sam Ewalt
Croswell, Michigan
USA
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
Cannot read input file 'config.sys'!
--MIME-multipart-message-boundary-981664002
Content-Type: application/octet-stream ;name=config.sys
Content-Transfer-Encoding: base64
REVWSUNFPUM6XERPU1xTTUFSVERSVi5FWEUgL04gNDA5NiAwIC9FOjEwMjQgL1YNCkRFVklD
RT1DOlxET1NcSElNRU0uU1lTDQpERVZJQ0U9QzpcRE9TXEVNTTM4Ni5FWEUgTk9FTVMgST1C
MDAwLUI3RkYNCkJVRkZFUlM9NSwwDQpGSUxFUz03NQ0KRE9TPVVNQg0KTEFTVERSSVZFPUUN
CkZDQlM9NCwwDQpTSEVMTD1DOlxjb21tYW5kLmNvbSAvUC9lOjUxMg0KREVWSUNFSElHSCAv
TDoxLDEyMDQ4ID1DOlxET1NcU0VUVkVSLkVYRQ0KRE9TPUhJR0gNClNUQUNLUz05LDI1Ng0K
--MIME-multipart-message-boundary-981664002--
ÿ
(end of quote)
Where did that error message, "Cannot read input file 'config.sys'" come from?ÿ
It looks appropriate to me. I could use MUNPACK. Was it DOS or Arachne that
couldn't read config.sys? If Arachne, maybe she looked in Arachne directory, as
opposed to C:\, and didn't find any config.sys?
I would read in a file like config.sys and keep it straight text, avoiding
quoted-printable or base64. Maybe Arachne/Insight didn't know it was plain
text?
I see I have files=99, fcbs=4,4, no STACKS line in C:\CONFIG.SYS. files=99 was
for dBASE IV 1.5. New Deal would have wanted 120.
What happens if FCBS line is omitted, assuming one is not running ancient DOS 1
software? Does anybody still use FCBs? I see in DJGPP instructions, and
wonder why, regarding the FCBS part:
You need to update your C:\CONFIG.SYS to include the following lines
(edit the first to suit your installation, and if these lines already
exist, it's OK if they have larger numbers than these examples):
shell=c:\dos\command.com c:\dos /e:2048 /p
files=40
fcbs=40,0
You need to update your C:\AUTOEXEC.BAT to include the following
lines:
set PATH=C:\DJGPP\BIN;%PATH%
set DJGPP=C:\DJGPP\DJGPP.ENV
Note that the PATH statement should follow any other PATH statements,
or you may edit an existing PATH statement.
