Xref: utzoo comp.sys.ibm.pc:52264 comp.windows.ms:2650
Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!munnari.oz.au!uhccux!todd
From: todd@uhccux.uhcc.Hawaii.Edu (Todd Ogasawara)
Newsgroups: comp.sys.ibm.pc,comp.windows.ms
Subject: Re: Problems with Windows/Disk Manager/1024+ cylinder hard drives
Keywords: Windows, Disk Manager, FDISK
Message-ID: <8139@uhccux.uhcc.Hawaii.Edu>
Date: 10 Jun 90 19:58:14 GMT
References: <18406@well.sf.ca.us>
Reply-To: todd@uhccux.UUCP (Todd Ogasawara)
Followup-To: comp.sys.ibm.pc
Distribution: comp
Organization: University of Hawaii
Lines: 27

In article <18406@well.sf.ca.us> phred@well.sf.ca.us (Fred Heutte) writes:
>   In July 1989, Microsoft released a limited-circulation memo which
>stated, in part:
>
>     Many non-standard (i.e. non-FDISK) disk partitioning schemes
>     will cause problems when used with Windows and/or the
>     SMARTDRV.SYS disk caching utility.  This information applies to
>     Windows/286, Windows/386, and Excel.  Specific partitioning
>     methods that will ALWAYS cause problems include the following:
>
>     -  Disk Manager by Ontrack & Seagate (DMDRVR.BIN) 

I use version of DMDRVR.BIN on both my work and home machines which have
various sizes of Seagate MFM type drives. I think a number of us have such
configurations in various work places. My question is: does anyone know if
the problem lies with Windows 3.0 itself or the combo of Win3.0 and the new
SMARTDRV.SYS?  If so, is something like PC-CACHE safer to use with DMDRVR
and Win3.0?

I've been having a lot of problems with PC-CACHE 6.0 (to the point of
falling back to version 5.5) and don't want to go through another set of
cache caused problems now that I've installed Win3.0 on my system.
-- 
Todd Ogasawara, U. of Hawaii
UUCP:		{uunet,ucbvax,dcdwest}!ucsd!nosc!uhccux!todd
ARPA:		uhccux!todd@nosc.MIL		BITNET: todd@uhccux
INTERNET:	todd@uhccux.UHCC.HAWAII.EDU