HDTenEightyP/NetNews huggingface dataset:
From: danodom@matt.ksu.ksu.edu (Dan Odom)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Poll : Microsoft support on the Internet
Date: 21 Nov 1992 13:46:09 -0600
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

tfj@apusapus.demon.co.uk (Trevor Jenkins) writes:

>So that they can see the groundswell of opinion against them. I for one
>will NOT pay the exorbitant rates for CI$ access as well as paying for
>internet access.

BINGO!  That's my objection, too.  What I see in Microsofts replies is that
they don't care about the student population of the world AT ALL.
They won't even give us tech support (except through CI$).  The main
reason that I have Microsoft C++ is for compatibility with other people
(I can compile their code).  Watcom claims to have a Microsoft compatible
library; maybe I should switch to them.  Or find/write a MS-Compatible
library for Borland C++ (STILL my favoite MS-DOS compiler).


-- 
Dan Odom
Kansas State University
danodom@matt.ksu.ksu.edu
Member of the League for Programming Freedom; mail lpf@uunet.uu.net
Newsgroups: comp.os.msdos.programmer,comp.sources.wanted
From: paul@tct.com (Paul Levin)
Subject: Wanted: how to format a floppy from a program
Organization: TC Telemanagement, Clearwater, FL
Distribution: usa
Date: Mon, 23 Nov 1992 20:57:22 GMT


Is there a simple way to do a high level format to a floppy disk, from
a program (such as a C program) ?  I was hoping for a DOS or BIOS call,
but I can't find an obvious one.

Please reply via email to  --  paul@count.tct.com

Please do not post a follow-up, as I do not read this news group.  I already
spend too much time reading other news groups in my "work" day.
-- 
From:  Paul Levin   paul@count.tct.com   813-532-2239 (work, 9-5 EST)
    --> Jesus loves you, and died for you; thank Him today. <--
From: mchst12@pitt.edu (Mark Hahn)
Newsgroups: comp.os.msdos.programmer
Subject: Re:  MS-DOS in 386 protected mode
Date: 23 Nov 92 02:19:55 GMT
Reply-To: mchst12@pitt.edu

It's absolutely impossible to run unmodified msdos in protect mode.
Why?  Because Intel chose to place tag bits in the low-order positions of 
a selector (the protect-mode equivalent of a segment number).  The low
two indicate privilege level (ring 0-3) and 0x04 indicates LDT/GDT.
This means that if you want a series of consecutive selector values,
they will be scattered across rings and between LDT and GDT.  Not only
that, but the different rings are just aliases for the same descriptor.
V86 mode is Intel's response to this, of course.

Incidentally, it's amusing that you CAN run real-mode programs in
protect mode: as long as they don't make assumptions about seg
registers.  I have some Turbo C++ code that switches itself into PM,
but it doesn't really do anything past there.

regards, Mark.
Newsgroups: comp.os.msdos.programmer
From: s1110238@giaeb.cc.monash.edu.au (Lee Hollingworth)
Subject: Re: Mouse Cursor Drawing .
Organization: Monash University, Melb., Australia.
Date: Wed, 18 Nov 1992 07:23:16 GMT

buxduac@dct.ac.uk writes:

>How does a mouse driver draw it cursor on the screen ?  Does it use a
>nice safe DOS function or does it have to do the bit manipulation itself ?
>  I know int 33H function 09 sets the cursor shape but the drawing I
>can not find !.

Int 33h 09h does indeed set the cursor shape and it uses ES:DX for pointer
to screen and cursor.  (ES segment, DX offset).

You will need a function which defines segment:offset such as MSC && TC++
FP_OFF() and FP_SEG().

/***
 * file:    mouse.h
 * purpose: mouse defines
 ***/

#ifndef MOUSE

#define LBUTTON             0
#define RBUTTON             1

#define SOFT_TEXT_CURSOR    0
#define HARD_TEXT_CURSOR    1

#define MOUSE_BUS           1
#define MOUSE_SERIAL        2
#define MOUSE_INPORT        3
#define MOUSE_PS2           4
#define MOUSE_MP            5

#define IRQ_PS2             0

struct graph_cur {
    int screen_mask[16];
    int cursor_mask[16];
    int spotx;
    int spoty;
};

/* graphics mode cursor, hour glass */
static struct graph_cur far gcursor_hour = {
    /* screen mask */
    0x0000,
    0x0000,
    0x0000,
    0x8001,
    0xC003,
    0xE007,
    0xF00F,
    0xE007,
    0xC003,
    0x8001,
    0x0000,
    0x0000,
    0x0000,
    0x0000,
    0x0000,
    0x0000,

    /* cursor mask */
    0x0000,
    0x7FFE,
    0x6006,
    0x300C,
    0x1818,
    0x0C30,
    0x0660,
    0x03C0,
    0x0660,
    0x0C30,
    0x1998,
    0x33CC,
    0x67E6,
    0x7FFE,
    0x0000,
    0x0000,

    /* hot spot x, y */
    07, 07
};

#define MOUSE
#endif


void m_cursor(struct graph_cur far *cursor)
{
    unsigned seg = FP_SEG(cursor);
    unsigned off = FP_OFF(cursor);
    int spotx = cursor->spotx;
    int spoty = cursor->spoty;

    _asm {
        mov     ax, 9
        mov     bx, spotx
        mov     cx, spoty
        mov     es, seg
        mov     dx, off
        int     33h
    }
}

Lee Hollingworth
s1110238@giaeb.cc.monash.edu.au
Newsgroups: comp.os.msdos.programmer
From: mcastle@mcs213f.cs.umr.edu (Michael R Castle)
Subject: Re: ***4DOS vs DRDOS 6.0***
Date: Mon, 23 Nov 1992 16:13:33 GMT
Organization: University of Missouri - Rolla

In article <1992Nov22.140508.12220@bsu-ucs> 00clcoffing@leo.bsuvc.bsu.edu writes:
>I figure I should put on my $.02 about DRDOS 6.0....
> [stuff deleted]
>     My friend down the hall also used (note past tense) DRDOS and SSTOR.
>Somehow part of SSTOR's data file became corrupt.  When SSTOR loaded, it
>displayed a message to the effect of "...file corrupt, mounting device as
>read only."  The DRDOS manual advised us to run CHKDSK to correct the problem
>then reboot.  How is it possible to correct the problem when SSTOR has the
>drive write protected?  We backed up all data which wasn't corrupted, and
>removed DRDOS for good!

After backing up (you didn't before hand? tsk tsk), did you even TRY to 
run chkdsk?  

I assume SSTOR is similiar to STACKER in this aspect:

When a *possibly* corrupt compressed volume, it is mounted read only.  However,
the volume is represented on the host drive as a bid hidden file.  Normally
this file is set with the bits Hidden, Read-only, and System.  SSTOR/STACKER
aware programs (such as DRDOS chkdsk and STACKERS scheck) can play with those
bits and go in and muck around with the file.  Hmm... I would think that 
putting all the functionality of regular chkdsk and sstor-aware chkdsk would
bloat the binary a little bit.  (Or does DRDOS offer 2 version of those 
binaries which would need to be sstor-aware?). 

anyway, my observations,
mrc 

Xref: sparky comp.os.msdos.programmer:10814 comp.os.ms-windows.programmer.misc:3585
From: paul@sierra.com (Paul Stratton)
Newsgroups: comp.os.msdos.programmer,comp.os.ms-windows.programmer.misc
Subject: Re: Poll : Microsoft support on the Internet
Date: 19 Nov 92 19:52:57 GMT
Organization: Sierra Geophysics Inc.,  Kirkland, Wa

In article <1992Nov14.200035.28509@news.ysu.edu> doug@cc.ysu.edu (Doug Sewell) writes:
>to call long distance to access.  But they don't have any form of anony-
>mous FTP to get the same things as are on the board.
>
>That in itself would be nice, and probably not too painful to implement.

Take a look at ftp.uu.net in the vendor/microsoft directory.  A lot of
the stuff on their bbs is located there too.

There is a lot of stuff from other vendors here too.


-- 
Paul Stratton               -----   -----   -----    -----    -----    ------
Sierra Geophysics, Inc.    /          /    /        /    /   /    /   /     /
P.O. Box 3886              -----     /    /---     /-----   /-----   /-----/
Seattle, Wa.  98124            /    /    /        /   \    /  \     /     /
From: rol@grasp1.univ-lyon1.fr (Paul Rolland)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Dos taking over int 5.
Date: 18 Nov 92 13:19:45 GMT
Followup-To: comp.os.msdos.programmer
Organization: Apple Computer Europe

In article <1992Nov13.075323.454@ifi.uio.no>, runefr@ifi.uio.no (Rune
Fr|ysa) wrote:
> 
> 
> Yesterday, I experienced the following problem:
> I have an interrupt (print screen key) routine conntected to int 5.
> After booting, the interupt address is: FF000:FF54 which is owned by
> BIOS, next using Norton SI to set screen mode to 80x50 lines, results
> in a vector to 02D5:37E3 which is Dos system area, and my interrupt
> routine which was installed before DOS takes over, no longer get 
> called at the press of the print screen key.
> 
> Anyone who has any idea of how to solve this problem? 
> (I prefer not to take control over int 09)

I think BIOS routines works only in 80x25 mode. If you want to have it
working in a graphic mode, you have to load the program GRAPHICS (if I
remember well), which will setup a new routine for graphic printing (on an
IBM compatible printer :( ). I *guess* it is the same problem for 80x50
text mode, but I don't know if the answer is the same. Why about trying ? 

Paul Rolland, rol@grasp1.univ-lyon1.fr
---

A bug can be changed to a feature by documenting it. Developpers know !

--------------------- DISCLAIMER -------------------

All the opinions I express in this posting are mine, but I'm
ready to share them with anybody interested :-)
From: wdrdjh@thor.cf.ac.uk (Dr D J Harvey 92)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Borland C++ 4.0 - Who knows What?
Date: 18 Nov 92 13:23:16 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

In article <1992Nov17.184053.15765@borland.com> dave@borland.com (Dave Draper) writes:
|In article <4205.9211171028@thor.cf.ac.uk> wdrdjh@thor.cf.ac.uk (Dr D J Harvey 92) writes:
|>I've heard a rumour that Borland C++ 4.0 is due to ship at the end of this
|>year and will include a DOS extender.  How well founded is this this
|>info?  Also, does anyone knwo (or have any idea) what the compliance
|>modes (e.g. DPMI etc) of the extender will be and whether there are
|>likely to be any distribution royalties on programs that include it?
|>
|
|What you have heard is nothing but a rumor. It has no basis in fact.
|Borland C++ 4.0 is not even a product.
|

I realise you can't officially comment on unreleased products, but
there's nothing more likely to fuel suspicions than an overly defensive
denial (ask any politician<G>)

There aren't any worries about killing 3.1's sales are there ??

Dave Harvey
harveydj@cardiff.ac.uk
+44 222 552588
Dept Radiology
University Hospital of Wales
Heath Park
Cardiff CF4 4XW
UK
From: dpn2@po.CWRU.Edu (Damien P. Neil)
Newsgroups: comp.os.msdos.programmer
Subject: Re: BC++ 3.1 bug?
Date: Sat, 21 Nov 1992 06:31:16 GMT
Organization: Case Western Reserve University
NNTP-Posting-Host: b63519.student.cwru.edu

In article <1992Nov20.174122.2729@microware.com> adam@microware.com (Adam Goldberg) writes:
>The following produces an interesting error:
>
>#include <dos.h>
>#include <mem.h>
>
>void main(void)
>{
>   unsigned short far *ppm, *dest;
>
>   if(NULL == (ppm = (unsigned short far *)farmalloc(1024)))
>   {
>      error message...
>   }
>
>   if(NULL == (dest = (unsigned short far *)farmalloc(1024)))
>   {
>      error message...
>   }
> 
>
>This produces an error on the _second_ farmalloc(), "suspicious
>pointer conversion". (not on the first...)

Try:           unsigned short far *ppm, far *dest;

You need to specifically declare each pointer far.

BTW -- a minor nit: main() should be declared as returning an int...
Damien Neil   dpn2@po.cwru.edu      "Until somebody debugs reality, the best
CMPS/EEAP double majoring masochist  I can do is a quick patch here and there."
Case Western Reserve University                   - Erik Green
Newsgroups: comp.os.msdos.programmer,comp.os.ms-windows.programmer.misc
From: fr@compu.com (Fred Rump from home)
Subject: Re: Poll : Microsoft support on the Internet
Organization: CompuData Inc.
Date: Tue, 17 Nov 1992 17:47:56 GMT

ngorelic@speclab.cr.usgs.gov.cr.usgs.gov (Noel S. Gorelick) writes:

>Of course, I wish to add my YES vote here, but I did not see the original
>article.  Is this a poll by someone at Microsoft?  Or just another net.dude?
>(ie: is it an offical kind of thing, or just someone making noises?)

Nor did I. But obviously an MS presence here would be heaven sent.
fred
-- 
W. Fred Rump 	office:	   fred@COMPU.COM     'mans feet have grown/so big 
26 Warren St.   home: fred@icdi10.compu.com  that he/forgets his littleness'
Beverly, NJ. 08010                          		Don Marquis 
609-386-6846    bang:uunet!cdin-1!icdi10!fr
From: nllopis@ecs.umass.edu
Newsgroups: comp.os.msdos.programmer
Subject: Re: Direct video memory access
Date: 15 Nov 92 13:41:49 GMT

For any information on direct memory access, if you are half serious 
about it, I would strongly suggest that you get a copy of the
book "PC&PS/2 VIDEO SYSTEMS" by Richard Wilton, published by
Microsoft Press. 
I had it for a couple years and it has proven to be really 
usefull. It has all the information you need for direct 
graphics programming in all video cards CGA,EGA,VGA,MCGA,Hercules,
etc....
Definetely worth the $27 it costs!


	Noel Llopis
In article <2890.2B054487@catpe.alt.za>, JWF.Thirion@p2.f118.n7102.z5.fidonet.org (JWF Thirion) writes:
> Hello Andrew!
> 
>  AM> I would like information on accessing video memory directly on any PC.  I
>  AM> need information for any screen type, in particular, HERCULES, CGA, EGA
>  AM> and VGA, for text and graphic modes.
> 
> I don't know if the following is what you want, but here goes  (I don't know if Hercules is correct):
> 
> Display  | Video Segment | Type       | Bits per pixel
> 
> HERCULES : 0B000h        : Text       : ?
>            0B000h        : Graphics   : ?
> 
> CGA      : 0B000h        : Text       : ?
>            0B800h        : Graphics   : 4 bits per pixel
> 
> EGA      : 0B800h        : Text       : ?
>            0A000h        : Graphics   : 1 bit per pixel.  (16 Color Mode)
> 
> VGA      : 0B800h        : Text       : ?
>            0A000h        : Graphics   : 1 bit per pixel.  (16 Color Mode)
>                                         8 bits per pixel.  (256 Color Mode)
> 
> MCGA     : 0B800h        : Text       : ?
>            0A000h        : Graphics   : 8 bits per pixel.  (256 Color Mode)
> 
> To for instance plot a pixel at the first position on the screen in MCGA mode, use the following code:
> 
> MOV AX, 0A000h     ; Video Segment
> MOV ES, AX         ; Place it in Extra Segment.  (Used as destination)
> MOV AL, 01h        ; Color to use.  (Blue in this case)
> MOV CX, 0001h      ; Number of pixels to plot
> MOV DI, 0000h      ; Offset on the screen.  Calculated : DI = (320 * Y) + X.
> REP STOSB          ; Plot all pixels.  (Use STOSB if you just want to plot one)
> 
> I hope this could help.  Leave me a message if you are still having trouble with it and I will write a short example to show you how it is done.
> 
> CU,
> JWF Thirion (Derik)
> 
> 
> --  
> INTERNET: JWF.Thirion@p2.f118.n7102.z5.fidonet.org
> via:  THE CATALYST BBS in Port Elizabeth, South Africa.
>        (catpe.alt.za)   +27-41-34-1122 HST or +27-41-34-2859, V32bis & HST.
Newsgroups: comp.os.msdos.programmer
From: mokler@desert.in-berlin.de (Claudius Mokler)
Subject: Re: borlandc++ bcinst?
Organization: Private Site
Date: Fri, 20 Nov 1992 12:51:17 GMT

You simply have to set your settings using the IDE and then
save the settings via Options|Save ...
This isn't wonderful, but it works somehow.
Newsgroups: comp.os.msdos.programmer,comp.os.ms-windows.programmer.misc
From: joser@gfimda.uucp (Joe Rodriguez)
Subject: Re: Poll : Microsoft support on the Internet
Date: Mon, 23 Nov 1992 15:36:51 GMT
Organization: Kraft General Foods

YES

+--------------------------+------------------------------------+
| Joe Rodriguez            |    ||   //    /====\    +=======   |
+--------------------------+    || //     ||         ||         |
| Kraft General Foods      |    |</       ||  ====   ||====     |
| General Foods-USA, IMD   |    || \\     ||    ||   ||         |
| Mailcode:  T12-1         |    ||   \\    \====/    ||         |
| 555 South Broadway       |------------------------------------+ 
| Tarrytown, NY  10591     | joser@gfceb   - ICES INGRES Host   |
| (914) 335-6059           | joser@gfimda  - IMD System         |
|                          | INTERNET/UUCP:  gfimda!joser@uunet |
| Pager: (212) 356-5116    |                 uunet!gfimda!joser |
+--------------------------+------------------------------------+
-- 
+--------------------------+------------------------------------+
| Joe Rodriguez            |    ||   //    /====\    +=======   |
+--------------------------+    || //     ||         ||         |
| Kraft General Foods      |    |</       ||  ====   ||====     |
From: andyg@hpcvra.cv.hp.com (Andrew Gryc)
Date: Thu, 19 Nov 1992 18:43:41 GMT
Subject: Re: Floppy Drive Readiness
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Newsgroups: comp.os.msdos.programmer

Below is code I wrote to determine if a disk is in Drive A (the code can
be easily modified to check for B: too, if you load DL from a stack param;
0=A:, 1=B:).
It is in C inline assembly (best of both worlds, as far as I'm concerned).  
I've used it without problem, but please note that I was coding this for 
a specific BIOS platform (i.e. read the note about ES:BX!).  Have fun...
 

o
 \/___________________________________________________________________________
 /\
o

int DiskInDriveA(void)
{
  _asm {
    mov cx,4        ; Allow once + 3 retries before we give up 
                    ; (motor may not be on initially, and BIOS will err)

TryAgain:
    push cx
    mov ah,4        ; Verify sector (uses ES:BX as ptr to verify buffer)
                    ; Don't care where es:bx points to (NOTE: apparently, this
                    ;   can be a problem for some early versions of BIOS, 
                    ;   to be safe, point to a sector-sized "junk" area) 
    mov al,1        ; 1 sector long
    xor cx,cx       ; cylinder 0, sector 0
    xor dx,dx       ; head 0, drive 0
    int 13h         ; Who cares if it verifies, just want to see if disk present
    cmp ah,80h
    jne DiskThere   ; 80h is disk timeout--anything else is a real disk

    mov ah,00h      ; Reset diskette A:
    int 13h
    pop cx
    loop TryAgain   ; Oops, errored on verify...

    xor ax,ax
    jmp short ExitDisk
DiskThere:
    pop cx           ; Grab the loop off the stack
    mov ax,1
ExitDisk:
  }
}

----------------------------------------------------------------------
Andrew J. Gryc   |  #include <stddisclaimer.h>
Hewlett-Packard  |
Corvallis, OR    |
Newsgroups: comp.os.msdos.programmer
From: gilem@aix.rpi.edu (Michael R. Gile)
Subject: help with borland c++ templates
Organization: Rensselaer Polytechnic Institute, Troy, NY
Date: Fri, 20 Nov 1992 16:05:16 GMT

I wanted to use the borland c++ templates to create a 
bag of structures, and so I tried to use the 
BI_BagAsVector type.  The only problem is that you get
an error of an illegal operation on the structure.  I
figure that I have to make the structure a class which
is derived from Object.  Is this correct?  If so, could
someone point me in the right direction, because I don't
have a clue on which virtual functions must be declared
in the new child class for the == to work (this is the
operation that causes the problems.

Thanks
Mike
Newsgroups: comp.os.msdos.programmer
From: leonard@qiclab.scn.rain.com (Leonard Erickson)
Subject: Re: Undocumented commands for MSDOS
Reply-To: Leonard.Erickson@f51.n105.z1.fidonet.org
Organization: SCN Research/Qic Laboratories of Tigard, Oregon.
Date: Mon, 16 Nov 1992 08:24:29 GMT

bailey_j@kosmos.wcc.govt.nz writes:

>I have found two undocumented commands for MS-DOS: "truename" which seems
>to give the same output as "cd" on its own, and a /f switch for command.com
>which seems to do something unspecified. Can anyone tell me what these two 
>do ?

Oops! I almost forgot. The /f parameter is *normally* used in the SHELL
line of CONFIG.SYS. It tells COMMAND.COM to automatically do a "Fail" 
on any critical errors (and thus avoid the Abort, Retry, Fail prompt).
Mostly useful for unattended systems.

-- 
Leonard Erickson		      leonard@qiclab.scn.rain.com
CIS: [70465,203]			 70465.203@compuserve.com
FIDO:   1:105/51	 Leonard.Erickson@f51.n105.z1.fidonet.org
(The CIS & Fido addresses are preferred)
Newsgroups: comp.os.msdos.programmer
From: dmurdoch@mast.queensu.ca (Duncan Murdoch)
Subject: Re: Borland C++ 4.0 - Who knows What? (actually TP 7)
Organization: Queen's University
Date: Thu, 19 Nov 1992 03:53:22 GMT

In article <1992Nov18.222936.26394@kronos.arc.nasa.gov> raymond@kronos.arc.nasa.gov (Eric A. Raymond) writes:
>What sort of support does it have for interrupts?
>
>That is, if you do a setvect does does the handler perform in real or
>protected mode?  Is there any control over doing this (i.e., a real
>mode handler)?

From what I can spot on a quick read through the BP 7 manual, there's no 
special support for interrupts.  That is, you'll have to use the DPMI 
services directly.

Duncan Murdoch
From: lectro@stein.u.washington.edu (Jonathan Maier)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Very puzzling struct problem!
Date: 22 Nov 92 04:05:12 GMT
Article-I.D.: u.1992Nov22.040512.6906
Organization: University of Washington, Seattle

In article <1992Nov21.221745.23588@jarvis.csri.toronto.edu> ematias@csri.toronto.edu (Ummm... me!) writes:
>- having 16 integer variables in the struct would work.
>- having 32 integer variables in the struct would work.
>- having 48 integer variables in the struct would NOT work.
>- having 64 integer variables in the struct would work.
>- having 80 integer variables in the struct would NOT work.
>- having 96 integer variables in the struct would NOT work.
>- having greater than 96 ints in the struct would NOT work.

It looks like the number of variables should be 2 raised to some power
(ie- 16(=2^4), 32(=2^5), 64(=2^6), etc.).  You'll probably notice that
some things are more "efficient" if they map directly into the binary
(base 2) scheme that the computer is based on.

  Jonathan E. Maier             # ## #                lectro@u.washington.edu
 -----------------------------  # ## #  --------------------------------------
  Weekend Operator             ## ## ##              University of Washington
  UCS Operations              ##  ##  ##                  Seattle, Washington