HDTenEightyP/NetNews huggingface dataset:
From: colovas@ohstpy.mps.ohio-state.edu
Newsgroups: comp.os.msdos.misc
Subject: exceptions, processors & motherboards
Date: 8 Oct 92 13:50:42 GMT


Help!
 I have been running up against a bunch of general protection faults while
trying to use the Borland C++ 3.0 compiler. after trying a number of things to
correct this problem, all suddested by borland in the CIS forum, I have decided
to come here. The latest one looks like this:
Exception 13: general protection fault at 024f:0A81 error code 01DC
ax=0032,bx=7020,cx=0000,dx=0D1F,di=0000,si=0002
ds=05BF limit=FFFF segment# 004C c:\borlandc\bin\bc.exe
es=0CD7 limit=07FF segment#
cs=024F limit=0B60 segment# 0015 c:\...\bc.exe
ss=05BF limit=FFFF segment# 004C c:\...\bc.exe
Error Code 01DC limit= 092F segment# 
strike any key to continue....

Unhandled Exception 000D at 029F 0A81 ErrCode 01DC
Memory allocation error
cannot load command system halted
--------------------------------------------
This is not the first one. The thing is, it runs perfectly fine on my 386 w/387
system at home, so what gives with this? (This is a 486. Both are 33Mhz
machines, too) borland is the only thing that gives me headaches. Can anybody
help me out here? any tidbits would be greatly appreciated.

Also, does anyone know if there is some software I can run to either make 
sure my CPU/motherboard is running properly or check the compatibility of 
the motherboard with the 100% clone standard? TIA 
-Pete
________________________________________________
___________________________________________
___________________________________

Peter W. Colovas  			"This time around the revolution will
Department of Physics 			 *NOT* be televised!"
Ohio State University
colovas@ohstpy.mps.ohio-state.edu
Newsgroups: comp.os.msdos.misc
From: scdorcy@lims01.lerc.nasa.gov (JAMES DORCEY)
Subject: Re: exceptions, processors & motherboards
News-Software: VAX/VMS VNEWS 1.41    
Organization: NASA Lewis Research Center
Date:  8 Oct 1992 16:42 EST  

In article <1992Oct8.183317.29074@ncsu.edu>, dspascha@eos.ncsu.edu (DAVID 
SCOTT PASCHAL) writes...
> 
>In article <14148.2ad40473@ohstpy.mps.ohio-state.edu>, 
>colovas@ohstpy.mps.ohio-state.edu writes:
>>Help!
>|> I have been running up against a bunch of general protection faults while
>|>trying to use the Borland C++ 3.0 compiler. after trying a number of things to
>|>correct this problem, all suddested by borland in the CIS forum, I have decided
>|>to come here.
> 
>|>This is not the first one. The thing is, it runs perfectly fine on my 386 w/387
>|>system at home, so what gives with this? (This is a 486. Both are 33Mhz
>|>machines, too) borland is the only thing that gives me headaches. Can anybody
>|>help me out here? any tidbits would be greatly appreciated.
>|>
>|>Also, does anyone know if there is some software I can run to either make 
>|>sure my CPU/motherboard is running properly or check the compatibility of 
>|>the motherboard with the 100% clone standard? TIA 
>|>-Pete
> 
>Hi.  I too have had problems with GP faults in BC++ 3.0, but it seems to be
>connected with the editor.  Every now and then when I first load the program and
>try to insert or delete a line it dies with a GP fault.  If I close all my
>windows or all but one window and start over I don't have any more trouble
>for a while until it happens again.  Sometimes I can have 10 or more windows
>open without any problem.  I noticed that when BC++ gets GP-happy I can run it
>in a DOS box in Windows 386-Enhanced mode and not have any problems, so perhaps
>it's a problem with the DPMI server built into BC++.

Just a WAG, but I'm not totally certain that BC++ 3.0 is compatible with 
Windows 3.1 --> maybe a solution is an upgrade to BC++ 3.1 (BC++ 3.1 would 
also give you the capability to write programs which support the Windows 
3.1 API calls).

Just a thought.

JD
Newsgroups: comp.os.msdos.misc
From: gill@eagle.sangamon.edu (Warren Gill)
Subject: Re: greater PATH length
X-Newsreader: TIN [version 1.1 PL6]
Organization: Sangamon State University
Date: Sat, 17 Oct 1992 02:57:22 GMT

  This *may* be a solution, or maybe not.   You could SUBST some of your
longer paths, and put the subst'ed drive in your PATH.

    SUBST E: c:\public\nw\hpnwdos\wp51

    PATH C:\DOS;E:;...

--
      ______                                                               
      )     (   Warren Gill, Microcomputer Software Specialist
     /       |  Sangamon State University, Springfield, IL                 
    (        |  Internet:        gill@eagle.sangamon.edu
     \_  *   |                                                             
       \     |  HSB-117          Monday-Friday 08:00-16:30 CDT
       /    /   217/786-7354
        \/\/    
          Life is at best only a child's game. Yet the game must be       
           played conscientiously. {Fukuzawa Yukichi}                     
Newsgroups: comp.os.msdos.misc
From: gilchr@ee.ualberta.ca (Andrew Gilchrist)
Subject: Hardware addresses for floppy drive
Summary: I need help.  Tell me the soft switches for the floppy drives.
Organization: University Of Alberta, Edmonton Canada
Date: Thu, 15 Oct 1992 11:07:14 GMT

Hi.  I recently decided that it would be very cool if I had a handy
reference which described the exact format of a 3.5 inch disk track.
You see, I am in need of what we used to call a "nibble editor."

This is essentially a program which allows you to modify the data stored
on the disk (i.e. address and data marks, etc.).  This allows you
to do all manner of neat things, like hiding sectors by giving them absurd
numbers, interleaving sectors on different tracks... the list goes on.

Anyway, no one I know has ever heard of such a utility for PC machines.
The only thing that comes close is Norton's Disk Editor, which is
useless in this repect.

It would appear that I may need to write such a program myself.

However, I can find no handy reference which describes the ACTUAL workings
of the floppy controller BIOS.  This frustrates me greatly. I do not
relish the task of reverse-engineering the floppy BIOS calls.

If someone could provide documentation for the floppy hardware addresses
(soft switches), or even point me to a useful reference on the topic,
I would be most pleased.


Andrew Gilchrist
gilchr@ee.ualberta.ca

Xref: sparky comp.os.msdos.misc:5616 rec.games.video:20182
Newsgroups: comp.os.msdos.misc,rec.games.video,alt.znet.pc
Subject: Z*NET PC Issue 34
From: znet@status.gen.nz
Date: Sun, 11 Oct 92 09:33:47 GMT
Organization: Z*NET Global News Gateway

  Greetings,
 
  Issue 34 of Z*NET PC may be read in alt.znet.pc  .  This issue is
  jammed packed with news / views / tips and hints on your computer.

  Happy reading.

  Title   : Z*Net PC Online Magazine - Issue #34 
  Keywords: ZNET NEWS PC WINDOWS IBM OS2 NEWTON STAC NEWSWIRE 34

  The latest edition of Z*Net PC Online Magazine, Issue #34 In this release:
  Disktop August News, Z*Net Newswire, Mike Mezaros Returns, IBM News Update,
  OS/2 Plans, Apple Announces Newton, and more news and reviews....  Zipped

                 ZPC34.ZIP/Bin   Bytes:  48640
       ZPC34.ASC  three messages 899 lines in alt.znet.pc

  If your site does not carry alt.znet.PC ask your administrator to carry it.


  regards

  
  - Z*NET On-line magazines
    Free ASCII magazines covering the lastest news and views.
Newsgroups: comp.os.msdos.misc
From: groenvel@brown.crayola.cs.psu.edu (John D Groenveld)
Subject: vpic for my xga s3
Organization: Penn State Computer Science
Distribution: usa
Date: Sat, 10 Oct 1992 22:24:26 GMT

Which version of vpic and which config do i need for my GA300 xga s3
card?
Thanks 
John
************************************************************************
|John D Groenveld                    |"Have you ever been experienced? |
|groenvel@crayola.cs.psu.edu         |   Not necessarily stoned, but   |
|groenvld@eclx.psu.edu               |           beautiful."           |
|jdg117@psuvm.psu.edu                |              The                |
|jdg@eclu.psu.edu                    |     Jimi Hendrix Experience     |
************************************************************************
Newsgroups: comp.os.msdos.misc
From: jenk@microsoft.com (Jen Kilmer)
Subject: Re: ONE gigabyte partition possible under MSDOS???
Date: 09 Oct 92 04:15:20 GMT
Organization: Microsoft Corporation

In article <bontchev.718549803@fbihh> bontchev@fbihh.informatik.uni-hamburg.de 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 primary
>> part. of 417mb via FDISK, and the rest (~5xx mb) is partitioned as an extended
>
>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. 
>
MS-DOS 4.0 and later supports volumes up to 2 gigabyte. You can have 
a primary partition up to 2 gigabyte in size.  (Compaq MS-DOS 3.31 could
only go up to 512M.)

However....MS-DOS uses interrupt 13 to access the hard disk via the
BIOS. Some drives are not fully accessible via the BIOS; sometimes
special controllers are required.  The Int 13 interface allows up
to 1024 cylinders / disk * 63 sectors / track * 256 heads * 512 bytes
per sector == 8 gig (I think). But many of the big disks have more
than 1024 cylinders. Usually this if fixed by having a controller
tell the BIOS that there are, say, half as many cylinders as there
really are and twice as many heads...then the controller does 
translation.

Another alternative is to use special partitioning software like
Disk Manager (from OnTrack) or SpeedStor (from Storage Dimensions)
that will replace the BIOS and the MS-DOS disk device driver for
that logical drive. Then the BIOS' limitation don't matter.

-jen
From: roy%cybrspc@cs.umn.edu (Roy M. Silvernail)
Newsgroups: comp.os.msdos.misc
Subject: Re: ansi.sys vs. nansi.sys vs nnansi.sys
Date: Sat, 10 Oct 92 19:01:13 CDT
Organization: Villa CyberSpace, Minneapolis, MN

jt@fuw.edu.pl (Jerzy Tarasiuk) writes:

> NANSI.SYS has few advantages compared to ANSI.SYS - quicker display due
> to writing directly to screen instead via BIOS, one (?) more escape
> sequence recognized. NNANSI emulates VT100 (?) - having it loaded I was
> able to connect to machine requiring at least VT100 using dumb terminal
> program and have good full-screen display (probably the machine doesn't
> use all VT100 capabilities, so I am not sure if NNANSI really emulates it).

Since the masochist in me recently researched writing a vt100/102
terminal program, I did quite a bit of study in that area.  NANSI and
vt100/102 are overlapping, but not identical, sets.  In particular, the
command to reset vt100 terminals to their default values is interpreted
by NANSI as 'set screen to 40 column mode'.  Since ELM initiates with
just such a command, I was less than amused. :-)

(I actually got the ANSI emulator done, but other priorities have kept
me from the vt100 part...)
--
Roy M. Silvernail --  roy%cybrspc@cs.umn.edu - OR-  cybrspc!roy@cs.umn.edu
  perl -e '$x = 1/20; print "Just my \$$x! (adjusted for inflation)\n"'
          "Does that not fit in with your plans?"
                      -- Mr Wiggen, of Ironside and Malone (Monty Python)
From: f_cnnghamjk@ccsvax.sfasu.edu
Newsgroups: comp.os.msdos.misc
Subject: Mathematica timing please...
Date: 16 Oct 92 02:25:45 GMT
Organization: Stephen F. Austin State University

Will someone e-mail the result of the Mathematica command
 
                              Timing[10000!]
 
to me? (Please suppress the output, the timing is all I want.)
 
Thanks.
 
 
Randomly, Kelly Cunningham
<deviate@lipschitz.sfasu.edu><f_cnnghamjk@ccsvax.sfasu.edu><jkellyc@tenet.edu>
"There is no reason for any individual to have a computer in their home."
                    Ken Olson, President and visionary, Digital Equipment,1977
Newsgroups: comp.os.msdos.misc
From: raistlin@wixer.cactus.org (Eli Boaz)
Subject: Re: upgrading from 3.3 to 5.0
Keywords: msdos 3.3 msdos 5.0 fdisk
Organization: Real/Time Communications
Date: Sat, 10 Oct 92 11:59:26 GMT

In article <edndowne.718676281@kraken> edndowne@kraken.itc.gu.edu.au (Barry Downes) writes:
>Hi,
>I am trying without success to upgrade my Samtron 286 laptop from MSDOS 3.3
>to MSDOS 5.0     The hard disk was partitioned under 3.3 as two 20mb drives
>C: and D:, but I would like to go to a single 40mb partition if possible.
>
>The problem is that after upgrading to 5.0 I can re-partition with FDISK,
>but the dos 5.0 format program won't work.  It hangs after confirming that
>the contents of the drive will be erased.
>
>I am unable to do a low-level format as the machine doesn't seem to have
>the ll format code at c800:whatever, and I don't have another low-level
>formatiting program.

Well, since it is a 286 you can't low-level format the disk with the
c800 method used in IBM PC's and IBM PC/XT's (8088's).  The reason is
that the hard drive BIOS is no longer in the hard drive controller,
like it was (is) in 8088's.  Your system BIOS should have a low-level
formatting section in the setup menu.  Just in case you don't know
how to enter your BIOS setup program, you should either A) be able
to press [Del] while it's checking memory -or- B) press [Alt] [Ctl] [S]
anytime you're at the DOS prompt... (Most system's I've seen use
the "Press [Del] to enter SETUP method...")

>(BTW: I CAN successfully do the dos 5.0 upgrade provided I stick with the
>original dos 3.3 partitioning, but I really don't want two logical hard
>drives.)

I don't see why two partitions is a problem, but okay. <shrug>

Hope this helps,

-- 
|ttyl,                     || Line noise provided by S. W. Bell Telephone!  |
|Eli Boaz                  |}-----------------------------------------------{
|raistlin@wixer.cactus.org || "Poker?!"  -- Lt. Cmdr Data, Time's Arrow I   |
\--------------------------/\-----------------------------------------------/
Newsgroups: comp.os.msdos.misc
From: edndowne@kraken.itc.gu.edu.au (Barry Downes)
Subject: upgrading from 3.3 to 5.0
Keywords: msdos 3.3 msdos 5.0 fdisk
Organization: ITC, Griffith University, Brisbane, Australia
Date: 10 Oct 92 00:18:01 GMT

Hi,
I am trying without success to upgrade my Samtron 286 laptop from MSDOS 3.3

to MSDOS 5.0     The hard disk was partitioned under 3.3 as two 20mb drives
C: and D:, but I would like to go to a single 40mb partition if possible.

The problem is that after upgrading to 5.0 I can re-partition with FDISK,
but the dos 5.0 format program won't work.  It hangs after confirming that
the contents of the drive will be erased.

I am unable to do a low-level format as the machine doesn't seem to have
the ll format code at c800:whatever, and I don't have another low-level
formatiting program.

Can anyone help?

(BTW: I CAN successfully do the dos 5.0 upgrade provided I stick with the
original dos 3.3 partitioning, but I really don't want two logical hard
drives.)

Thanks in Advance,

Barry        <B.Downes@edn.gu.edu.au>
.
From: stern@mble.philips.be
Newsgroups: comp.os.msdos.misc
Subject: Re: Expand DOS prompt?
Date: 7 Oct 92 09:59:12 MEWT
Organization: MBLE , Brussels, Belgium

In article <int704v.718177058@aurora.cc.monash.edu.au>, int704v@aurora.cc.monash.edu.au (Mark Cosham) writes:
> glowe@bonnie.ics.uci.edu (Glen H. Lowe) writes:
> 
>>In article <92276.140844ISSSEG@BYUVM.BITNET> <ISSSEG@BYUVM.BITNET> writes:
>>>Appearantly DOS prompt only allows 128K (characters).  I need to know
>>>how to expand DOS prompt beyond 128K using DOS and not some external
>>>utility or application like 4DOS.
>>>
>>>Please help me if you can...
>>>Thanks,
> 
>>128,000 characters is not enough for you prompt? =)  Seriously, I think
>>you really mean 128 bytes.  I don't think such a beast exists
> 
>>Glen Lowe
>>University of California, Irvine
> 
> THe 128 byte limit is built into COMMAND.COM and isn't easy to change
> without changing to another shell, such as 4DOS.  Even so, you would
> have to modify COMMAND.COM which will cause you the same problems as
> an external shell would.
> 
> Mark
> -- 
>  Practice random kindness and senseless acts of beauty.
> -----------> <-------> <-------> <-------> <-------> <-------> <-----------
>  Mark Cosham   Monash University, Melbourne, Victoria, Australia
>     int704v@aurora.cc.monash.edu.au       cosham@yoyo.cc.monash.edu.au

It is very easy to break this limit!
You only have to use an external tool that handles environment variables
in a better way than COMMAN.COM.

Have a look at XSET (version 2.60), it is available
   at SIMTEL-20  pd1:<msdos.batutl>xset260.zip
or at garbo.uwasa.fi:/pc/envutil/xset260.zip


	XSET allows you to put EVERYTHING you want in a variable of
 the current environment and use it as if you gave it the value with
 the standard DOS command 'SET'. You will be able to write very efficient
 batch files including string manipulation, calculation,...
 and it is fully compatible with MS-DOS 5.0, DR-DOS 6.0, NDOS, 4DOS,...


--  Marc Stern  <stern@mble.philips.be>
Newsgroups: comp.os.msdos.misc
From: thyerj@uncg.edu (Jonathan Thyer)
Subject: CD-ROM
Organization: University of North Carolina at Greensboro
Date: Wed, 14 Oct 1992 12:46:37 GMT

Can someone please give me a general run down on how a CD-ROM system works 
on MS-DOS machines.  I need to know things like, device drivers needed, is 
the CDROM assigned a drive letter like an ordinarily disk device, any 
comparisons of products out there you may have..... Just some general 
thoughts please.  Could you please Email your responses, POST if you think 
it would benefit all.

--
Jonathan S. Thyer, Programmer/Consultant        EMAIL: thyerj@iris.uncg.edu
IRC Department                                  PHONE: (919) 334-5350
235Q Bryan Bldg, UNCG
Greensboro, NC 27412

--
Jonathan S. Thyer
InterNet: thyerj@iris.uncg.edu
From: mccall@mksol.dseg.ti.com (fred j mccall 575-3539)
Newsgroups: comp.os.msdos.misc
Subject: Re: IRQ questions.
Date: 8 Oct 92 16:08:44 GMT
Article-I.D.: mksol.1992Oct8.160844.12912
Organization: Texas Instruments Inc

In <ardtlong.718439433@adam.adelaide.edu.au> ardtlong@adam.adelaide.edu.au (Dale T. Long) writes:


>On examining my system (a HT12A (286) based machine) I was given the following
>results. I used two programs; QA Plus and MSD (Microsoft's, of course).

>IRQ     QA Plus                 MSD
>-----------------------------------------------------
>0       Timer                   Timer
>1       Keyboard                Keyboard
>2       [Cascade]               Second 8259A  (through the BIOS)
>3       COM2                    COM2
>4       COM1                    COM1
>5       available               LPT2  (not installed)
>6       Floppy Disk             Floppy Disk
>7       LPT1                    LPT1
>8       Clock/Calendar          Clock/Calendar
>9       available               Redirected IRQ 2
>10      available               reserved
>11      available               reserved
>12      available               reserved
>13      reserved                reserved  (for co-processor)
>14      Fixed Disk              Fixed Disk
>15      available               reserved

>I would like to know what the [cascade] of IRQ2 means and why MSD shows it as
>a 'second 8259A'. As well as why MSD shows IRQ9 as being a redirected IRQ2.
>What does this all mean? Why is it redirected? Is this something all 286
>achines have or is it something particular to my machine (HT12A)?
>What tricks does an 8259A do?

The original PC only had 8 interrupts.  Wnen they went to the 16-bit
bus on the AT, they added 8 more.  However, in order to get to them it
was necessary to put another interrupt controller in, 'cascaded' off
of the first one.  This is accessed via IRQ2, which is remapped to
IRQ9 on all ATs so as to allow compatibility with the old 8-bit
machines and to have a complete set of IRQs.

[In other words, MSD is correct and your machine is normal.]

-- 
"Insisting on perfect safety is for people who don't have the balls to live
 in the real world."   -- Mary Shafer, NASA Ames Dryden
------------------------------------------------------------------------------
Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.
From: franks@hpuamsa.neth.hp.com (Frank Slootweg CRC)
Date: Fri, 9 Oct 1992 15:49:47 GMT
Subject: MS-DOS 5.0 COPY bug?
Organization: Hewlett-Packard, The Netherlands
Newsgroups: comp.os.msdos.misc

  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).

Notes:

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

- The problem also occurs if the source is "zombies.wp*" or "zombies.w*".

- The problem also occurs is the destination is "zombies.wp" (i.e. no
  renaming).

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

- The problem does not occur for XCOPY.

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

Frank Slootweg
Newsgroups: comp.os.msdos.misc
From: fox@rei.com (Fuzzy Fox)
Subject: Re: How can I use my High Memory ?
Date: Fri, 9 Oct 1992 23:22:41 GMT
Organization: Recognition Equipment, Inc.

mccall@mksol.dseg.ti.com (fred j mccall 575-3539) writes:

>>I have a no-name 286 with 4 Meg and MSDOS 5 loaded High.
>>but my Chipset (VLSI 82C100) is just too clunky to use them.  

Have you tried UMB_DRVR?  (UMBDR522.ZIP is the latest version I'm aware
of.)  According to my UMB_DRVR documentation, the 82C100 is a peripheral
chip and is not involved in selecting Shadow RAM.

Basically you are confusing HMA with UMB access.  HMA is just past 1 Meg,
whereas UMB is between 640K and 1 Meg.  TSR's and drivers cannot load
into the HMA (at least, most can't), but can nearly always load into UMB
space.

You need a UMB provider program.  Since you have a 286, the normal 386
programs won't work, but The Last Byte or UMB_DRVR might work for you,
if you can identify your chipset.  I found TLB to be very difficult to
install.  The hard part about installing UMB_DRVR was finding out my
chipset, but you seem to have located one of your chips...try locating
one that actually controls memory mapping, and you may find that
UMB_DRVR works well for you.

-- 
#ifdef TRUE        | Fuzzy Fox (a.k.a. David DeSimone)       fuzzy@netcom.com
#define  TRUE   0  |
#define  FALSE  1  |   "If you can't take the heat, you haven't learned
#endif             |      a damn thing from USENET!"  -- Rao V. Akella
Newsgroups: comp.os.msdos.misc