Text 1061, 67 rader
Skriven 2004-12-13 14:17:35 av Mark Lewis (1:3634/12.0)
     Kommentar till en text av Gerald Miller
Ärende: EMM386
==============
-=> Gerald Miller wrote to Dan Ceppa <=-

 GM>> If this line is not added to Config.sys (and reboot the system),
 GM>> then any of the supplemental disk programs that you might run
 GM>> will probably issue a "Incorrect DOS version" error message.
 GM>> Setver will make allowances and fool Command.com into "thinking"
 GM>> these programs are okay to run and you won't see the error
 GM>> message.

 DC> I've been using SETVER a lot, lately!

 GM> A fact of using Winnie, I guess.

i can't say that... this system was installed 4 years ago (almost to the
day) and as far as i can tell, setver hasn't been run on it at all...

[trim]

 GM>> Right now, I'm struggling with trying to get 4DOS v7.50 to work
 GM>> in 98SE.  I have to figure out what memory tweaks are necessary
 GM>> in the 4DOS.PIF properties.  Memmaker can't help me here...
 GM>> <sigh>

 DC> I'm working with 4DOS, too.  And, I've got messages out in the
 DC> 4DOS Echo as well!

 GM> I had to go into Config.sys and REM out the 4DOS shell
 GM> statement that the 4DOS installation put in.  I found that when
 GM> I formatted a system diskette with 4DOS as the command
 GM> processor, 4DOS.COM was being copied onto the diskette as
 GM> Command.com and of course the diskette wouldn't boot -- that
 GM> was one of many things I found to be inconsistent with 4DOS.

that's not an inconsistency with 4DOS... is it actually WAD (Working As
Designed) from MS... it is the job of FORMAT and SYS to put the command
interpreter on the disk when you tell it to put the system files on
it... since you told the machine that 4DOS was your command interpreter,
it used that as it didn't know about anything else... the reason it
wouldn't boot was because 4DOS.EXE was not renamed to COMMAND.COM which
the boot files look for and there was no CONFIG.SYS file with a SHELL=
statement to tell the system anything any different...

 GM> When I try the 4DOS shell box on the W98SE system, I get four
 GM> error messages all relating to the lack of Upper memory blocks
 GM> and everything is loaded into Low memory -- BAH!!!  I can
 GM> probably live without 4DOS on the W98SE box (or until I can
 GM> find a way to map some of the extended memory)...

upper memory or high memory?

 GM> When I first tried installing Windows for Workgroup v3.11 on my
 GM> DOS box, I was running 4DOS as the command processor.  I could
 GM> not get WfW to install, no matter what I did.  I finally copied
 GM> an old Autoexec.bat and matching Config.sys that had
 GM> Command.com as the command processor shell and the WfW
 GM> installation went as it should.  I can't remember the
 GM> installation error message (at the time), but I felt it was
 GM> rather cryptic in details and cursed the Microsoft install.

that was due to MS' messing around and playing proprietary games trying
to keep everyone rounded up in their ballpark... it is just more
evidence of their monopolistic practises and additional proof that they
started that stuff a lot further back than people want to admit to...

)\/(ark

 * Origin:  (1:3634/12)