Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!rutgers!orstcs!mist!abukarb
From: abukarb@mist.cs.orst.edu (Bassam A. Abu-Karroum)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Multitasking on PCs
Keywords: multitasking switching, desqview, software carousel, VM386
Message-ID: <18903@orstcs.CS.ORST.EDU>
Date: 15 Jun 90 03:29:51 GMT
References: <4633@mit-caf.MIT.EDU> <1086@helps.cactus.org>
Sender: usenet@orstcs.CS.ORST.EDU
Reply-To: abukarb@mist.UUCP (Bassam A. Abu-Karroum)
Distribution: na
Organization: Oregon State University, Corvallis
Lines: 35

In article <1086@helps.cactus.org> jhoward@helps.cactus.org (James Howard) writes:
>In article <4633@mit-caf.MIT.EDU> gavin@mit-caf.UUCP (Gavin C. H. Zau) writes:
>>
>>	I recently posted a request for information on softwarer for
>>...
>>	Windows 3.0
>>...
>
>Will McClatchy in Information Week, June 11, 1990, page 15 writes:
>
>  "Early users of Microsoft Corp.'s Windows 3.0 software say it will
>   destory data and crash hard disks that have not been formatted with
>   MS-DOS 4.01.  What's more, some users say the company knew about
    ^^^^^^^^^^^^
I'm sorry, but this is not true. I'm running Win3.0 on my 286 machine with
DOS version 3.30 with no problems at all. What the article didn't mention is 
that most of those users are using a non-standard disk partitioning utilities
such as disk-manager and speeddstor that are not "compatible" with Windows
3.0.
>   the problem but has not done enough to alert them...."

On the original disks, I don't recall which one, there is a text file that
discusses such situations and offers a workaround for the problem. The
workaround involves modifying the WIN.INI file by adding a couple of lines
(the changes included in the text file) to allow Windows/3.0 and disk
partitioning utilities to co-exist. The problems is mainly with disk drives
with cylinders > 1024 AND partitioned by *some" 3rd party methods. 

From my personla experience, if you need to work > 1024 cylinders disk, use
DOS 4.01 to save you the headache and worries.


NO, I don't own shares in Microsoft.

Sam.