HDTenEightyP/NetNews huggingface dataset:
From: charlesr@wspcrd.PeachtreeCityGA.ncr.com (Charles Rutledge)
Newsgroups: comp.os.msdos.misc,comp.sys.ibm.pc,comp.sys.ibm.pc.misc
Subject: Re: Quality of DR-DOS 6 (was BEWARE SUPERSTOR!!!!!!)
Keywords: DR DOS, SSTOR, SUPERSTOR
Date: 8 Oct 92 20:21:12 GMT
Reply-To: charlesr@wspcrd.PeachtreeCityGA.ncr.com (Charles Rutledge)
Distribution: na
Organization: NCR WSPC Peachtree City, Georgia

In article <Oct05.161446.25310@yuma.ACNS.ColoState.EDU> knepley@CS.ColoState.EDU (Ranseus (Jim Knepley)) writes:
> 
>Really, all this talk about the quality of DR DOS is pretty silly.  I've
>been running it for a while now and have had no problems with DR DOS at
>all.  There have been some other programs (such as SSTOR) that had the
>odd problem, but nothing I wasn't able to fix in 10-15 minutes.

I have no complaints at about the quality of DR DOS and feel it is much
better than any favor of MS-DOS.  My problem was adding in what I thought
would be an upgrade (SuperStor 2.0) to get all its features.  As it turns
out, SuperStor 2.0 is probably not an upgrade for the version packaged with
DR DOS.  Adstor probably could have mentioned this somewhere (or maybe they
did and I missed it -- live and learn).  But problems about getting programs
that should work together and don't are not silly to those of us that do
have problems.  I'm glad things worked out for you.  I had a bit more trouble,
and though all in all, I like DR DOS, I would like to think I come to Net
for help and to help pervent troubles for others.


-- 
Charles Rutledge  /  NCR Test Program Development   |      NCR Corporation 
Internet: Charles.Rutledge@PeachtreeCityGA.NCR.COM  |  The Networked Computing
ATT: (404) 487-7000 Ext 7523 / Fax: (404) 487-7089  |     Resource Of AT&T
Newsgroups: comp.os.msdos.misc
From: parry@yoyo.cc.monash.edu.au (Tom J Parry)
Subject: Re: MS-DOS 5.0 COPY bug?
Originator: parry@yoyo.cc.monash.edu.au
Organization: Monash University, Melb., Australia.
Date: Wed, 14 Oct 1992 05:13:34 GMT

Frank Slootweg CRC (franks@hpuamsa.neth.hp.com) wrote:
>   Recently I wanted to "backup" (copy) a file ZOMBIES.WP (a WordPerfect
> 5.1 document) to a diskette. Since I wanted to save several versions of
> the document, I wanted to name the copy ZOMBIES.WP0. Since I am a lazy
> typer, I typed
> 
> copy zombies.* a:zombies.wp0
> 
>   COPY dutifully responded with "ZOMBIES.WP" (because of the wildcard
> ("*")) and with "1 file(s) copied" and a prompt. So far so good. Since I
> am not only lazy, but also paranoid, I did a
> 
> comp zombies.* a:zombies.wp0
> 
>   COMP responded with "Files are different sizes". So I did a DIR for
> both files and found that ZOMBIES.WP was 44609 bytes, but A:ZOMBIES.WP0
> was only 930 bytes!
> 
>   Is this a bug in MS-DOS 5.0? If so, I think it is a very severe one,
> because you loose data without any indication (error message).

It is not a bug. It's just how copy works. If you specify multiple files as
the source and a single file as the destination (as opposed to a
directory), DOS adds all the wildcarded files together and copies them onto
that one single file. It does this even if the wildcard only matches one
file.

In your case this sounds as if it would work, if not for one thing. When
appending files together, DOS assumes ASCII mode and chops the files at the
first ^Z it finds. This means that your long file got chopped to 930 bytes
as that is the first EOF in the file.

You need to use the /b command line switch (after the wildcarded filename
if memory serves) to tell DOS that hte source file(s) are binary.

> 
> Notes:
> 
> - I think the syntax of the COPY command used is correct, because,
>   according to "COPY /?" source can contain wildcards.

Yes, but bear in mind the altered meaning of copy mentioned above when you
do this.

> 
> - The problem also occurs if the source is "zombies.wp*" or "zombies.w*".
Any wildcard will do it.
Also 'copy file1 + file2 file3' will result in a short file3 if file1 or
file2 have EOF's in the middle and you dont specify binary:
copy file1 /b + file2 /b file3
I think.

> 
> - The problem also occurs is the destination is "zombies.wp" (i.e. no
>   renaming).
Yes, the destination name won't change the behaviour unless it is a
directory.

> 
> - The problem does not occur for "copy zombies.* a:".
In this case DOS realises you want to copy multiple files to a single disk
as opposed to a single file.

> 
> - The problem does not occur for XCOPY.
XCOPY usually will ask if you mean the destination to be a directory.

> 
> - I did not check if the problem is related to the size and/or the
>   content of the source file.
Size: NO
Content: YES
> 
> Frank Slootweg

-- 
Tom J Parry.
Your reality is a figment of my imagination.
From: ry01@ns1.cc.lehigh.edu (ROBERT YUNG)
Newsgroups: comp.os.msdos.misc
Subject: Re: ONE gigabyte partition possible under MSDOS???
Date: 9 Oct 92 18:24:32 GMT
Organization: Lehigh University

In article <Bvt7LF.1oL@mentor.cc.purdue.edu>, ludwig@sage.cc.purdue.edu (Mark St
ephen Kidder) writes:
>In <bontchev.718549803@fbihh> bontchev@fbihh.informatik.uni-hamburg.de (Vesseli
n Bontchev) writes:
>
>-ry01@ns1.cc.lehigh.edu (ROBERT YUNG) writes:
>
>-> My friend has this gigabyte HD and he just wants one partition on it. The
>-> drive is SCSI and the controller is on an EISA bus. For now, he has a primar
y
>-> part. of 417mb via FDISK, and the rest (~5xx mb) is partitioned as an extend
ed
>-> part. via a Utility program.
>->    So is it possible to have just one partition.
>
>-No. The DOS filesystem supports volumes up to 512 Mb. And even this
>-can be achieved only with the newer DOS versions. The old ones (3.30-)
>-support volumes up to 32 Mb.
>
>Yes!  DOS 4.01's limit was 512 Mb; however DOS 5 can achieve 2 Gb
>partitions.  Isn't DOS 4.01 old?  And DOS 5 is in need of upgrading...
>

Are you sure? When Fdisk is run, it asks if I want the primary partition to be
the maximum, and the maximum it lists is 417mb! Okay, the HD is Fujitsu SCSI
1070 mb, and it's connected to a Mylex EISA SCSI controller on a Mylex 486/33.
( I wish I had my friend's problems... ). I am using MS-DOS 5.0. Any help?
Thanks!

-- 
       /~~~~~~~~~~~~~~~~~~~~~~~ILAN~~~~~~~~~~~~~~~~~~~~\
       \___(Robert) Bobby Yung_______RY01@Lehigh.Edu___/
Newsgroups: comp.os.msdos.misc
From: jenk@microsoft.com (Jen Kilmer)
Subject: Re: MS-DOS 5.0 COPY bug?
Date: 16 Oct 92 00:12:29 GMT
Organization: Microsoft Corporation

In article <27800028@hpuamsa.neth.hp.com> franks@hpuamsa.neth.hp.com (Frank Slootweg CRC) writes:
>copy zombies.* a:zombies.wp0

Frank, did you know that COPY is designed to combine files as well
as copy them? This command specifies that you want to combine all 
files that fit the filename zombie.* into 1 file called zombie.wp.

Thing is, when combining, copy defaults to copying files in ascii mode,
not binary, so copy quits reading the file when it hits an eof char,
not when it's read the whole file. Problem is, the file IS a binary file
need to copy it in binary mode. 

To force a binary-mode copy here, try:

copy /b zombies.* a:zombies.wp0

>both files and found that ZOMBIES.WP was 44609 bytes, but A:ZOMBIES.WP0
>was only 930 bytes!
>
>  Is this a bug in MS-DOS 5.0? If so, I think it is a very severe one,
>because you loose data without any indication (error message).

This is how MS-DOS has worked since verion 1.0. If you've ever wanted
to combine files, you'd agree it's pretty handy (and, btw, copy /b is 
the only way using plain DOS to combine binary files). I doubt if it will
be changed in the future. 

>- I think the syntax of the COPY command used is correct, because,
>  according to "COPY /?" source can contain wildcards.

Yes, this is true. But if the source contains wildcards and the target
specifies 1 destination file, then you're not copying, you're combining.

>- The problem does not occur for "copy zombies.* a:".

Correct, because then you're specifying that zombies.* should be copied
to a:zombies.*  -- multiple sourcefiles to multiple destinations, so
this is copying.

>- The problem does not occur for XCOPY.

No, I don't think XCOPY ever defaults to ascii copy. I'm not even
sure xcopy DOES ascii copy.

>- I did not check if the problem is related to the size and/or the
>  content of the source file.

The problem is related to the content of the source file. The reason
for the trunacation is that it hit an eof mark partway thru while
copying in ascii mode. Force it to binary with /b, it'll be fine.

>
>Frank Slootweg

-jen
MS-DOS product support engineer, ret.
Newsgroups: comp.os.msdos.misc
From: messina@netcom.com (Tony Porczyk)
Subject: Re: Urgent Out of Environment Space Problem
Organization: Messina Software
Date: Thu, 15 Oct 1992 02:15:35 GMT

chad.w.german.1@nd.edu (Chad W. German) writes:

>Using environment variable and PC's are running version 5.0 of DOS..... 
>Increasing the environment space to 1024 or 2048 does not seem to resolve 
>the problem.... Command using looks like
>shell=c:\command.com /p /e:1024.......
>Need help......

Could you kindly say exactly under what conditions the error occurs?  Hard
to determine the source without any data.
Anyway, if it occurs on the secondary shell, it's because COMMAND.COM does
does pass the size of the environment to it.
In any case, try to use 4DOS if possible, you will avoid those traps.

t.
Xref: sparky comp.os.msdos.4dos:24 comp.binaries.ibm.pc.d:3669
From: ljensen@plains.NoDak.edu (Lars Jensen)
Newsgroups: comp.os.msdos.4dos,comp.binaries.ibm.pc.d
Subject: Ghostscript386 and 4DOS.COM incompatible ?
Date: 15 Oct 92 16:17:15 GMT
Article-I.D.: ns1.Bw67wr.BJ0
Organization: North Dakota Higher Education Computing Network

Does GS386.EXE work with 4DOS.COM ? If not, is there a fix? 
(GS286.EXE seems to work fine with 4DOS.COM, and GS386.exe works fine with 
the usual COMMAND.COM .)

Thanks in advance for any answers.

                                         -Lars Jensen

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Department of Physics, University of North Dakota, Grand Forks ND 58202-8008
Telephone: (701) 777-2912 (Home: 436-4073).  E-mail:  Bitnet: ljensen@plains 
Uucp: plains!ljensen          or         Internet:  ljensen@plains.nodak.edu 
Xref: sparky comp.os.msdos.4dos:25 comp.binaries.ibm.pc.d:3681
From: arjen@disnet.uucp (Arjen Duursma)
Newsgroups: comp.os.msdos.4dos,comp.binaries.ibm.pc.d
Subject: Re: Ghostscript386 and 4DOS.COM incompatible ?
Date: 16 Oct 92 08:00:41 GMT
Organization: Disnet, IDE Maassluis, The Netherlands

ljensen@plains.NoDak.edu (Lars Jensen) writes:

>Does GS386.EXE work with 4DOS.COM ? If not, is there a fix? 
Works fine with me (both of them :-))
>(GS286.EXE seems to work fine with 4DOS.COM, and GS386.exe works fine with 
>the usual COMMAND.COM .)
What doesn't work according to you? Any symptoms.

Arjen

BTW. There are newsgroups voor ghostscript and 4dos, why not use them
instead.
From: parasite@jupiter.sun.csd.unb.ca (Leslie Mills)
Newsgroups: comp.os.msdos.programmer
Subject: Request: OAK VGA Board drivers for Windows
Date: 13 Oct 92 18:17:16 GMT
Organization: University of New Brunswick

A friend of mine has some OAK VGA boards.  Unfortunely, he
doesn't have any drivers that are compatable with MS Windows.
Does anyone know where he could download/order any legal
drivers?

Thanx in advance...
-- 
Leslie Mills

If you love something, set it free, if it doesn't come back to you,
Hunt it down, and kill it -- Thus sayeth a T-shirt
Newsgroups: comp.os.msdos.programmer
From: jt@fuw.edu.pl (Jerzy Tarasiuk)
Subject: Re: Borland C startup code (C0.ASM) question
Organization: Warsaw University Physics Dept.
Date: Fri, 9 Oct 1992 11:13:27 GMT

>>>>> On Thu, 8 Oct 1992 01:36:38 GMT, fs8j@uvacs.cs.Virginia.EDU (Fraser Street) said:
Fraser> I have one specific question and one general question about the
Fraser> Borland C startup code, namely C0.ASM.  I'm working in HUGE model - I
Fraser> know the .BAT file defines __HUGE__ and builds C0H.OBJ out of C0.ASM.

Fraser> Specifically, I notice IFNDEF's in C0.ASM on a symbol __BOSS__ .  A
Fraser> reference to it appears aroound line 100 of C0.ASM.  What is __BOSS__?
Fraser> What is it's significance?  

As I see, the __BOSS__ should be defined to make startup code which
allows Protected Mode execution (using DPMI). However, in BC 3.0 it
has bugs and, at least if used in Real Mode, can cause crash.

Fraser> In general, i'm faced with the unpleasant task of hacking my way
Fraser> through this code for a project i'm working on.  Does anyone know of
Fraser> any magazine articles or documentation (possibly from Borland)
Fraser> that I could get with info about C0.ASM, the things it's responsible 
Fraser> for doing, how it works, etc.

If not described in Borland C manuals, I don't know :-(.
Can try ask Sidney Markowitz <sidney@borland.com>, he may know
(his machine is frank.borland.com, do you remember stories
 about Frank Borland in old Borland's documentation ? :-).
Newsgroups: comp.os.msdos.programmer
From: tlhouse@nyx.cs.du.edu (Thomas House)
Subject: Re: How to Access 143 Column VGA Mode from TurboC?
X-Disclaimer: Nyx is a public access Unix system run by the University
	of Denver for the Denver community.  The University has neither
	control over nor responsibility for the opinions of users.
Organization: Nyx, Public Access Unix at U. of Denver Math/CS dept.
Date: Thu, 15 Oct 92 02:41:52 GMT


getting into 143 column mode using textmode() under Turbo 'C' doesn't work
because the 143 column mode isn't a "standard" text mode.  You'll have to
use BIOS calls (the easiest way) to get into the proper text mode.  I
can't seem to find any calls for 143 column mode .. tons for 132 column
mode .. but none for 143 .. unfortunately, you'll pretty much have to know
which card you're working with to trip the proper BIOS call for 132 column
mode vor your particlar video card .. if there is a general function of
interrupt 0x10 that initializes 132 column mode, or if its defined under
the VGA standard, I can't seem to find it .. if anyone knows, could you
tell us?

Newsgroups: comp.os.msdos.programmer
From: wstef@hubcap.clemson.edu (W. Gregg Stefancik)
Subject: COM3 and up interrupt handling
Organization: Clemson University
Date: Mon, 12 Oct 1992 12:23:25 GMT

Since COM ports 3 and up share the same interrupts as COM1 and COM2 what
is the proper way to write an interrupt handler which is aware of this
interrupt sharing?  Should the well behaved handler chain the COM
interrupts?  I currently have a driver for a TSR which handles COM1 and
COM2, but want to make sure that it doesn't screw up anything trying to
use COM3 or higher.

Please respond via e-mail.

-- 
W. Gregg Stefancik
wstef@hubcap.clemson.edu
Xref: sparky comp.os.msdos.programmer:9852 alt.msdos.programmer:2545
From: jdz1@Ra.MsState.Edu (John D. Zitterkopf)
Subject: Caches for either CDROM or Floppy disks only...
Summary: Forwarded from another newsgroup!
Organization: Mississippi State University
Distribution: usa
Date: Tue, 13 Oct 1992 05:20:51 GMT

Hi,
	I'm looking for a Cache that would:

	1) Allow me to specify the ONLY DISKs I want to Cache
	2) Work only for a CDROM.
      or
	3) The source on a Cache. 

I'm attempting to Cache a CDROM at speeds >600mS. I tried HyperDisk, but I 
didn't like it because:
	A) Either HD disks or ALL disks which included: FD & HDs.
     &
	B) I prefer PC-Cache...

I would like to be able to ONLY select the Drive(s) I wish to cache. Does anyone
have some source code to get me started? Or even some book/papers on the work-
ings of the CDROM and Caches.

Thank you for your time...
John

--
 ____________   _------_  |||IBM & |      EE majors Do it Best 8-)
  --------\\ ] ~-______-~ |||Atari |~~~~~~~~~John D. Zitterkopf~~~~~~~~~~~~~
     (~~~~~\\|_(__ ~~    / | \Rules!jdz1@ra.MsState.edu  jdz1@MsState.bitnet
      \______| (        /  |  \    |AOL: zitt@aol.com  jdz1@isis.MsState.edu 
Newsgroups: comp.os.msdos.programmer
From: jt@fuw.edu.pl (Jerzy Tarasiuk)
Subject: Re: SPEECH OUTPUT via PC speaker. HELP!
Organization: Warsaw University Physics Dept.
Date: Tue, 13 Oct 1992 17:39:19 GMT

>>>>> On 13 Oct 92 13:38:15 +1300, singlis@waikato.ac.nz said:
singlis> I have some sampled speech data (8Khz), mu-law as well as linear
singlis> (-8k to +8k).
singlis> How can I play this music back through the standard PC speaker...

A way to play music through PC speaker: program 8253 channel 2 for
mode 0, least significant byte, binary (out 43h,90h) and write
data to port 42h. Note data must have proper range, e.g. if written
at 19kHz, must not exceed 64. I don't know: you sampled 8000 times
per second or 16000 ? In first case, can output data at 24kHz, in
second at 32, making proper interpolation/rounding.
Note to get good quality need output data in timer interrupts which
must be set for proper frequency and must adjust memory refresh
frequency (it must be interrupt frequency or its multiply).
I have an assembly program for it, callable from Turbo Pascal.
From: unixlan+@pitt.edu (Wei-ming William Lin)
Newsgroups: comp.os.msdos.programmer
Subject: Wanted: MSC 6.0a (Yes, !! 6.0a !!) (Please read if you have
Date: 8 Oct 92 13:30:02 GMT
Organization: University of Pittsburgh


***************************************************************************
 Due to the system problem, the machine I posted this messages last
time won't accept your reply.  So please, if you got trouble, try to
reply to this account again: unixlan@unix.cis.pitt.edu.  Sorry for the trouble.
			     ^^^^^^^^^^^^^^^^^^^^^^^^^
***************************************************************************

Hi Folks,

I know this is not the best place to do so, but I need your help!!

Don't say I am crazy.  Yes, I need your olde version of MSC!!  My old libraries
can support nothing but MSC 6.0, so.....  If you have a copy of MSC 6.0a
gathering dust in your shelf, now is the best time to send it out.  It does not
have to be in the mint condition, but at least descent.  Manuals must be 
complete.  And if you still have your registration card, that will be perfect 
(although not necessary).  Just remember, IT MUST BE 6.0a, NOT 6.0.  Please 
reply by e-mail.  Thanx in advance. (One more: 3.5" is preferred,
although 5.25" is OK.)

Willie

"UNIX(tm), X & LAN --- The Promise of the Future!!"
"And OS/2 V2.0!!"

+=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=+
| Internet e-mail:                       Mom Bell:                        |
| unixlan@unix.cis.pitt.edu                 H: (614)267-2674  (after 9pm) |
| wmlin@speedy.cs.pitt.edu                  O: (614)888-3833              |
| Compu$erve: 71650,1444                                                  |
+=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=!=+
From: curt@vtucs.cc.vt.edu (Curt Tilmes)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Turbo Vision Help?
Date: 16 Oct 92 19:35:11 GMT
Organization: Virginia Tech, Blacksburg, VA
In-reply-to: gabriel@netcom.com's message of 15 Oct 92 20:40:20 GMT


Is there enough interest in Turbo Vision for a mailing list, maybe 
eventually 'comp.os.msdos.programmer.turbo-vision'?

It would be nice to meet with other TV programmers and share 
experiences/ new TV classes, etc..  With a mailing list, and
maybe an ftp site for sample code and libraries, we all might
spend a little less time re-inventing the same wheels.

If someone else will run the mailing list, I will manage an
ftp directory for any code/archives/whatever.

Curt
Newsgroups: comp.os.msdos.programmer
From: eda735a@monu6.cc.monash.edu.au (P.E. Mazur)
Subject: ASSEMBLERS/DEMOS/INFO EXCHANGE
Keywords: looking...
Organization: Monash University, Melb., Australia.
Date: Wed, 14 Oct 1992 05:45:22 GMT

Hello guyz.  Im going to ask a simple question:
What is the best assembler to use for 80386?  Im looking for something with
its own debugger, editor... the works... a coplete package that doesnt
require exiting to DOS to assemble (this is not the stone age!).
Does Borland do a modern package like this??

Next topic:  Anyone intrested in coding demos on the PC if welcome to get
in touch with me.  Im thinking of seriously getting into it this summer after
I finish my exams (thats summer Australian time!).  If anyone wants to share
info and source about this... Id love to hear from you.    


			- Shem

PS: If youre reading this Steve... keep in touch!!!  Same to all the other
ppl who have kept in touch but who I havent heard from in a while... :*)
Newsgroups: comp.os.msdos.programmer
From: jt@fuw.edu.pl (Jerzy Tarasiuk)
Subject: Re: Floppy Disk 1:1 interleave ?
Organization: Warsaw University Physics Dept.
Date: Fri, 9 Oct 1992 12:16:05 GMT

>>>>> On Tue, 6 Oct 1992 06:29:45 GMT, bmtong@cucs11.cs.cuhk.hk (Tong Bo-Ming) said:
Tong> 	It seems to me that DOS format disks with 1:1 interleave.  When I
Tong> call BIOS to read a chunk of disk sectors, it is so fast !  Is this
Tong> true ?

Yes. If you read disk using DOS, it is fast, too (if file is contiguous).
However, I found UNIX floppy disk driver cannot handle 1:1 at full speed
- before it is ready to read next sector, more than 4 sectors pass...
Therefore, UNIX works best if you use interleave 1:6, DOS is better :^).
(tested for Interactive UNIX System V, on 16/20 MHz 386 based machine).
Newsgroups: comp.os.msdos.programmer,comp.sys.ibm.pc.hardware,comp.os.msdos.apps
From: baileyc@ucsu.Colorado.EDU (Christopher R. Bailey)
Subject: Need Device Driver (printer/plotter) package for Dos
Summary: device drivers for printers, plotters, cgm needed
Keywords: cgm, plotter, printer, device, driver, dos
Organization: University of Colorado, Boulder
Distribution: usa
Date: Tue, 13 Oct 1992 23:18:31 GMT


We are developing a 2D and 3D plotting program under UNIX and DOS (X Windows
and MS Windows), and need to be able to send the plots ot several devices,
for example, laser printers, versatec plotters (electrostatic and pen), dot
matrix printers, etc.  We also need to be able to produce CGM format files.

On the UNIX side, we are using UNIRAS-FGL for our drivers, but on the PC,
we haven't found a set of drivers or whatever that will produce CGM files.  We
are currently considering a product called BabyDriver II, but it only seems
to support printers and plotters, no CGM.

So, we are in need of a package similar to UNIRAS, but for a PC, wether it
be commercial or publid comain.  Any info would be appreciated.  Thanks!

Newsgroups: comp.os.msdos.programmer,alt.msdos.programmer