Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!ncar!boulder!ccncsu!longs.LANCE.ColoState.Edu!ms234210
From: ms234210@longs.LANCE.ColoState.Edu (Mark T. Spence)
Newsgroups: comp.windows.ms
Subject: Re: Colorado Tape Backup Software Barfs at Windows 3
Summary: CMS will work thru Windows 3.0
Keywords: DMABufferSize, CMS
Message-ID: <8425@ccncsu.ColoState.EDU>
Date: 11 Aug 90 17:30:13 GMT
References: <1990Aug8.180541.22232@agate.berkeley.edu> <3191@gmdzi.UUCP>
Sender: news@ccncsu.ColoState.EDU
Reply-To: ms234210@longs.LANCE.ColoState.Edu (Mark T. Spence)
Organization: Colorado State University, Fort Collins, CO  80523
Lines: 23

As a tech support engineer at Colorado Memory Systems I too was interested in
seeing whether our tape drive would run thru Windows or not. It will.

It *won't* run thru a window or in the background, but it will run as an
exclusive, full-windowed operation with DMABufferSize set to 32. I would
also reccomend increasing the operation's time-slice well up from 100.
It will run that way, but is a bit too slow for my tastes.

Any attempts to run our tape software as a window or in the background
will result in errors 90 or 92--tape sw incompatability/ non-responsive
floppy controller chip.

For point of interest, our sw engineers are currently working on our own
DOS-based, background software.  But for now the best way to run our tape
drive is still outside of Windows.


Attention all replies to: ms234210@longs.lance.colostate.edu

"You know, I could corrupt these children; over the years I could turn their
innocent minds toward a life of wrongdoing. Yes! I could mold them in my
image, hone them into criminal geniuses--the only ones capable of carrying
on my empire! Ah...but who's got the time--toss 'em in."  Fat Cat