cramer@optilink.UUCP (Clayton Cramer) (12/14/90)
I mentioned a few days ago some problems I was having with the
HIMEM.SYS and SMARTDRV.SYS drivers distributed with Windows 3.0.
Here's some more details.
The HIMEM.SYS V2.60 and SMARTDRV.SYS V3.03 drivers come with
Windows 3.0. The two of them combined result in a system lockup
immediately after the SMARTDRV.SYS driver has installed.
If I use the HIMEM.SYS V1.1 driver that came with Windows 2.1
and SMARTDRV.SYS V3.03, the system will at least boot, but
SMARTDrive says, "No extended memory available". (Not surprising --
the documents say to use HIMEM and SMARTDRV that come together).
Using HIMEM.SYS V2.60 without SMARTDRV.SYS seems to work -- until
you enter Windows. Then my system reboots. (The system is a
Club AT (Everex motherboard) 10 Mhz 286 system with 1 MB of RAM and an
AMI BIOS).
I spoke to Microsoft Customer Support this morning, and I was
told that using the DOS FASTOPEN command would corrupt the Windows
files when installed, and that I should reinstall Windows with
FASTOPEN turned off. I did this. Same results as above.
Does anyone have a solution to this? Windows 2.1 worked on
my hardware -- Windows 3.0 doesn't. I would be tempted to put
more RAM on my system for extended memory, but if Windows can't
even get to the 384K of extended memory I have, it's not worth
it.
--
Clayton E. Cramer {pyramid,pixar,tekbspa}!optilink!cramer
Self-defense is the most basic of human rights. Lacking the right to defend
yourself today can make it very hard to exercise any other rights tomorrow.
You must be kidding! No company would hold opinions like mine!