Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!cvedc!gssc!bradd
From: bradd@gssc.UUCP (Brad Davis)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: 4DOS 3.02 and MS Windows 3.0
Keywords: 4DOS Windows problems
Message-ID: <6635@gssc.UUCP>
Date: 11 Apr 91 03:25:38 GMT
Organization: Graphic Software Systems, Inc. Beaverton, Or.
Lines: 48

hartung@crl.ucsd.edu (Jeff Hartung) writes:
>Many other responses to my initial article were posted and/or sent
>e-mail.  Several people reported never having seen the problem.  I have
>seen it show up on two different machines (a 12 MHz 286 and a 20 MHz
>386).

[Problem with 4DOS not sharing extended memory with "Smart Cache" deleted]

I'm another person who has not seen this problem on any of the five
4DOS-equipped, Windows-using machines that I use or know of.  In particular,
neither of the 386s I use everyday have this problem.  Both run 4DOS as
their primary shells, both run Smart DRIVE in extended memory, both use XMS
swapping.  Both machines spend most of their time in Windows.

The above is true with both HIMEM.SYS and with QEMM.  I normally use QEMM
but I spent several weeks with HIMEM.SYS recently and that worked fine too.

>The other problem, that SETUP doesn't run properly, is not a major
>problem since, as was pointed out by someone, it isn't a frequent
>operation ...
>  Others have reported similar problems to me since my
>initial article.  It may be bios specific (AWARD), or it may be
>something else.

I've had no problems with my AMI and Phoenix BIOS machines.

>Again, I think (especially since I heard this from others) that the
>problem is real, and not due to "something else," as has been
>suggested, but I am willing to acknowledge that the conflict may
>involve a particular hardware/ bios/device driver combination.
>
>Comments?

You are looking in the wrong place.  Get down to a 5 or so line CONFIG.SYS
(FILES, BUFFERS, HIMEM, SMARTDRV and SHELL) and no AUTOEXEC.BAT.  Allow
4DOS to use it's defaults.  If that doesn't do the trick, you have a
hardware compatibility problem.  Check the Windows README.TXT at about
line 185 where they talk about HIMEM.SYS and systems that have strange
methods of handling the A20 address line.

Best of luck,
Brad
                                          _________
Random drivel from the keyboard of:      |       |.|
  Brad Davis, GSS Inc, Beaverton OR      | bradd |:|
  bradd@gssc         (503) 671-8431   ___|_______|_|___       _________
Disclaimer: The boss disavows        |[]gssc| _-_  _-_ |    @|#########|
  all knowledge of my actions.       |______|__________|@@@@ +---------+