HDTenEightyP/NetNews huggingface dataset:
From: rocks@dante.nmsu.edu (Dave Rocks)
Subject: ftp-os2(hobbes) downtime
Organization: New Mexico State University, Las Cruces, NM
Date: Fri, 16 Oct 1992 21:10:44 GMT

nternet FTP site, ftp-os2.nmsu.edu(hobbes.nmsu.edu), will be down from
7am to 2pm, MDT, on Sunday, 10/18/92, due to a scheduled campus wide
power outage. We don't expect any other problems.

	The ftp site has been unreliable the last week or so because of our
	ongoing space problems. I am happy to announce that we just added a
	new .5gb drive to ftp-os2 which should hold us for a while. During
	the install process we managed to screw up a few times but I hope
	everything is straight by this PM.
From: dic5340@hertz.njit.edu (David Charlap)
Newsgroups: comp.os.os2.misc
Subject: Re: Out of memory on 16mb system?!
Keywords: memory
Date: 9 Oct 92 16:05:16 GMT
Organization: New Jersey Institute of Technology, Newark, N.J.

In article <burleigh.718325721@ogre> burleigh@ogre.cica.indiana.edu (Frank Burleigh) writes:
>I've just installed os2 ga on my new 486/50dx with 16mb.  I have
>applied many of the fixes found on software.watson (including
>the kernal, gt16mb, etc.).  Just after booting my friend started
>the WIN-OS2 clock, then started the 'cat and mouse' game.  The
>game never really started: there were several beeps with
>a message box warning that there "is insufficient memory" and
>advising that other tasks be shut down.

This error appears to be more of an "out of system resources" than
"out of memory".  It should be fixed with the 32-bit GRE, which will
have much larger pools of resources available.

It happens most often when lots of objects (windows, icons, bitmaps,
etc) are on screen at once.
-- 
David Charlap         |"there aren't 50,000 things for which it's worth writing
dic5340@hertz.njit.edu| software; and the computer industry doesn't have enough
----------------------+ programmers to create that much good software.
Therefore, most of it must be worthless" -- Boris Beizer "The Frozen Keyboard"
From: ASI509@DJUKFA11.BITNET
Newsgroups: comp.os.os2.misc
Subject: Re: Don't put program shadows on Desktop!
Date: 12 Oct 92 08:30:10 GMT
 <1992Oct8.170936.13611@magnus.acs.ohio-state.edu>
 <1992Oct8.181330.12816@cbnews.cb.att.com>
 <1992Oct8.205804.18871@magnus.acs.ohio-state.edu>
 <92283.134520ASI509@DJUKFA11.BITNET>
 <1992Oct9.174307.8240@muddcs.claremont.
Organization: Forschungszentrum Juelich

In article <1992Oct9.174307.8240@muddcs.claremont.edu>,
jokim@jarthur.claremont.edu (John H. Kim) says:
>
>ASI509@DJUKFA11.BITNET writes:
>>drives object.
>
>
>>A program object is a totally different thing. If you like you can think of
>>it as the WPS equivalent of a short batch file that calls your application.
>
>Here's where the problem is.  I have no problem with the concept of program
>objects (although I think they're clumsy).  The current problem in WPS is
>that they look EXACTLY like the original file in the drives object.

Yeah, but only in the beginning. What I do most of the time is give them a new
icon (these default DOS or OS/2 icons are rather dull) and a new name. I can`t
stand the .EXE extensions.

If you want to standardize a different look for your program objects, why don`t
you simply change the icon of the template?

Michael Bode.
From: dic5340@hertz.njit.edu (David Charlap)
Newsgroups: comp.os.os2.misc
Subject: Re: Why does OS/2 not support non-SCSI CD-ROMS ?
Date: 16 Oct 92 01:35:19 GMT
Distribution: usa
Organization: New Jersey Institute of Technology, Newark, N.J.

In article <1992Oct15.220629.5856@msuinfo.cl.msu.edu> sundaram@eecae.msu.edu writes:
>Hi all,
>
>I have been wondering why IBM has not decided to put out drivers for non SCSI
>CD_ROM setups yet. It seems that they decided that it was not worth it to 
>support "lesser" (i.e. cheaper) CD ROM drives. Is there a reson for this?

Two ideas:

1) When IBM released GA, only Toshiba had submitted specs for their
   drive.

2) IBM was only supporting their drive, but TOSHIBA was compatible.

Perhaps IBM doesn't know of everybody's proprietary interfaces and
doesn't have the time to be bothered writing drivers for them all.
SCSI is (more or less) a standard, so one driver can be made to work
for everybody.

As always, it's up to the manufacturer to support custom hardware.
-- 
David Charlap         |"there aren't 50,000 things for which it's worth writing
dic5340@hertz.njit.edu| software; and the computer industry doesn't have enough
----------------------+ programmers to create that much good software.
Therefore, most of it must be worthless" -- Boris Beizer "The Frozen Keyboard"
Newsgroups: comp.os.os2.misc,rec.games.misc
From: jeffc@netcom.com (Jeff Cohen)
Subject: Re: Gunship, Autoexec, Ram Disk, PC-NFS
Keywords: lockups, autoexec, ramdrive, nfs
Organization: Hacker's Anonymous
Date: Sat, 10 Oct 1992 19:27:46 GMT

In article <1992Oct7.041302.8086@trl.oz.au> peter@tardis.trl.OZ.AU (Peter K. Campbell) writes:
>_______________________________
>
>Number 4 - Sun PC-NFS, version 4.  We have it installed on a lot of
>machines at work, and it is pretty vital being able to access the
>network with it.  I can install the drivers in OS/2, but as soon as
>anything tries accessing them I get memory errors, of course.
>
>Now, I believe that if we bought IBM's tcp/ip + networking stuff et. al.
>that we could set up the machines to access our Unix boxes via this.
>However, there is a fair bit of money tied up in PCNFS, and so
>because of this plus a few other problems it looks like OS/2 will not
>be used on our machines (the other main problem is the lack of 256+
>colour driver support, which should be fixed with the shrinkwrap
>release).
>
>Does anyone know if their is some fix that allows PC-NFS to work under
>OS/2, or if Sun are working on an OS/2 Upgrade?
>
>Thanks in advance.
>
>Peter K. Campbell
>p.campbell@trl.oz.au
>#include <std.disclaimer>

No fix is required to run PC-NFS under OS/2 2.0.  I've successfully
done it.  The trick is, you must use a specific DOS version.  It won't
run in a simulated DOS session.  Simulated DOS sessions do not support
block device drivers.

Of course, you can only run PC-NFS in a SINGLE DOS box, and the mounted
file systems will be invisible to OS/2.
-- 

==============================================================================
Jeff Cohen         | #include <standard.disclaimer>
jeffc@netcom.com   |                       
==============================================================================
Newsgroups: comp.os.os2.misc
From: bangell@cs.utah.edu (bob angell)
Subject: Re: Dual Monitors (Mono/Trident 8900 VGA) Problem
Date: 11 Oct 92 09:44:14 MDT

In article <1b86qhINNon0@darkstar.UCSC.EDU> kristine@cats.ucsc.edu (chfn) writes:
>
>What is 'echomon'?
>

something said usually in the Bahamas/Caymans or in the general viscinity
relating to the computer phrase 'echo' ... :-)

Sorry couldnt resist.

-Bob-

>Thanks.
From: dic5340@hertz.njit.edu (David Charlap)
Newsgroups: comp.os.os2.misc
Subject: Re: 3.5" beta disks-what if A: = 5.25"?
Date: 9 Oct 92 18:17:52 GMT
Organization: New Jersey Institute of Technology, Newark, N.J.

In article <1992Oct9.173716.27919@usl.edu> das9674@usl.edu (Stephenson Daniel A) writes:

>Wouldn't it be nice to have a little switch, maybe even OUTSIDE
>the computer to switch the drive designations at will?

An old model Tandy-1000 had a feature like this.  If you held down the
F1 key while powering on (not while booting), the A: and B: drives
would swap.  Of course, it was useless on that machine, since both
drives were 5.25" 360K disks.

-- 
David Charlap         |"there aren't 50,000 things for which it's worth writing
dic5340@hertz.njit.edu| software; and the computer industry doesn't have enough
----------------------+ programmers to create that much good software.
Therefore, most of it must be worthless" -- Boris Beizer "The Frozen Keyboard"
Newsgroups: comp.os.os2.misc
From: rdippold@qualcom.qualcomm.com (Ron Dippold)
Subject: Re: Os/2 and second drives
Organization: Qualcomm, Inc., San Diego, CA
Distribution: na
Date: Fri, 9 Oct 1992 22:41:54 GMT

shane@cs.UAlberta.CA (Ruman Shane James) writes:
>      I'm considering buying another hard drive to satiate software's space 
>apetite and remember reading that Os/2 didn't pacticularily like second drives

Not that I know of.  Especially if you're using IDE drives.  There
might be some problem with SCSI or ESDI I'm not aware of.

>, has there been any problems with using Os/2 on a system with two drives.  

Works bootiful for me.


>Also if two drives works fine, is it possible to format the second one totally
>as HPFS while Os/2 continues to reside on my FAT drive 1(unfortunately still
>gotta use dos occaisonally).  Illumination would be appreciated as always!

It's possible, but I wouldn't recommend that.  What I'd recommend is
formatting the smaller one as FAT, then formatting the larger one as
HPFS and putting OS/2 on the HPFS drive.  It will run much faster that
way, and then you can always boot just the FAT drive to run DOS.
Don't use a dual boot system, use the Boot Manager option.


-- 
Be careful when playing under an anvil tree
From: gumby@cs.mcgill.ca (Phil PRANNO)
Newsgroups: comp.os.os2.misc
Subject: Re: Windows NT for about $500...
Date: 8 Oct 92 15:55:46 GMT
Organization: SOCS - Mcgill University, Montreal, Canada

In article <1992Oct8.052508.23316@news.Hawaii.Edu> lkan@uhunix.uhcc.Hawaii.Edu (Linus Kan) writes:
>I don't think so--it's just a gimmick!  That was the estimated price
>range so that tempted users like me would eventually buy OS/2.
>Microsoft says that--do you think they'll actually sell NT for
>that price?  Think about it--if you were a sales strategist at 
>Microsoft, how much would you suggest NT sell for so as to 
>maintain total monopoly on Intel based systems?  $500 for NT is
>quite ridiculous--it's all just a (brillant) gimmick and a false
>'add'.
>

Actually, NT started off as a server platform and after MS saw that
OS/2 2.x would be more popular than they thought they changed their
minds.  They now claim it will run on a fast 386 with 8 meg, where as
before they said it would require a fast 486 and 16 megs...

>I'm sure Microsoft is reading the OS/2 newsgroups and get user
>evaluations and problems plus tips and ideas so that they could
>improve their NT code.  And since NT and OS/2 are similar in code,
>Microsoft is learning its mistakes from the release of OS/2 2.0
>--us OS/2 users did all the test Microsoft needed for the NT kernel.

Excuse me, but these kernals are not the same AT ALL.  NT uses
a micro kernal ala MACH and OS/2 uses an INTEL specific one.

[stuff deleted]

>Well, when NT is ready for release, Microsoft would come out hard
>with a powerful campign against OS/2.  The final analysis--OS/2 2.x
>would NOT survive in the long run--unless die-hard OS/2 users
>want to be unique and sway away from the mainstream, ie. Windows.

Maybe you should learn some facts.   Every major software vendor
is or is about to release and OS/2 2.0 specific version of their
popular programs (WordPerfect, LOTUS, Borland, ...).  Sales (or
shipments) of OS/2 will reach 2-3 million by year end.  NT isn't
even out of the starting blocks yet (and won't be before next summer by
most accounts).

Swallow hard and learn to use that 2nd mouse button!
 
>
>Hey--I have OS/2 2.0 on my system...won't be there long though.0

We don't want you anyways :)

>
>:) lkan


-- 
 Phil Pranno        *  The implosion of all matter in the universe into an
 gumby@cs.mcgill.ca *  infinitely small and dense point may lead to a NEW "BIG
 McGill University  *  BANG".  Should a new universe emerge, the validity of 
   -> GO OS/2 <-    *  these statements cannot be assured.
Xref: sparky comp.os.os2.misc:32712 comp.os.linux:13260
From: easyrob@cs.utexas.edu (Robert Depew Reynolds)
Newsgroups: comp.os.os2.misc,comp.os.linux
Subject: Re: Running Linux in a VDM. Can I do it?
Date: 12 Oct 1992 23:18:41 -0500
Organization: CS Dept, University of Texas at Austin
NNTP-Posting-Host: coltexo.cs.utexas.edu

Doesn't Linux require a 32-bit machine?  At best, the VDM emulates a '286
machine.  Linux is a REAL 32bit operating system that requires full access to
a 32bit machine.  OS/2 is also a REAL operating system that requires complete
control of its hardware.  You can not run 32-bit specific code in a VDM.  This
would destroy system integrity.  There are however ways to have both operating
systems on your machine.  You can use BootManager to switch back and forth.
The procedure needed to do this can be found in one of the FAQs associated with
these to fine operating systems.
 
/===========================================================================\
|  Robert D. Reynolds               |      You may choose      GOOD         |
|  easyrob@cs.utexas.edu <INTERNET  |      any TWO you         /  \         |
|  (512) 345-8509        <TELEPHONE |      wish!              /    \        |
|====================================================\       /      \       |
|  I have been known to work, but I have never been  |      /        \      |
|  known to speak for an employer or even like 'em   |    FAST ---- CHEAP   |
|  most of the time.  Well there is PAYDAY!  :-)     |                      |
\===========================================================================/
                              GO TEAM OS/2 !!!
Newsgroups: comp.os.os2.misc
From: linstee@dutecaj.et.tudelft.nl (Erik van Linstee)
Subject: Wildcard problem
Organization: Delft University of Technology, Dept. of Electrical Engineering
Date: Wed, 14 Oct 1992 19:34:45 GMT

Tell me if this is wrong or not; I have a bunch of files in a
dir name *.2.man, now I want to rename them all to *.man so
I enter ren *.2.man *.man and expect to get a bunch of *.man
files. Too bad, the files still have the same name. So I
try a similar thing under dos (or 4dos actually) and it works
fine. So what's up, why doesn't the wildcard expansion function
as I expect it to?

Erik



-- 
Erik van Linstee   |   Delft University of Technology   |   I'll be back ... 
----
   We are god, 'cause only we can create the idea of his existence
   in our holy brains...  (Yello)
Newsgroups: comp.os.os2.misc,comp.os.ms-windows.misc
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Subject: Re: SHELL.DLL and Microsoft Mail
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago
Date: Wed, 14 Oct 1992 16:09:32 GMT

In article <1992Oct11.124414.9063@iccgcc.decnet.ab.com> halco@iccgcc.decnet.ab.com (ext. 3540) writes:
>I recently ordered the Windows Mail Working Model to try out.  When I load
>it under WinOS2, I get an error message stating that the file SHELL.DLL
>could not be located (a correct conclusion by the software-there is no
>SHELL.DLL anywhere on the disk).
>Has Microsoft written OS/2-proof mail software, or is there some workaround?

Microsoft forgot to include the OLE DLLs (which do not ship with
Windows 3.0 but do ship with most OLE-aware apps and Windows 3.1).
You can lift the DLLs from any Windows 3.1 installation or any
OLE-aware application (like Ami Pro or Word for Windows).

-- 
Timothy F. Sipples      | The OS/2 FREQ. ASKED QUESTIONS LIST 2.0f is avail.
sip1@ellis.uchicago.edu | from 128.123.35.151, anonymous ftp, in /pub/os2/all
Dept. of Econ., Univ.   | /faq, or from LISTSERV@BLEKUL11.BITNET (send "HELP")
of Chicago, 60637       | [For the Internet, vote Clinton-GORE this year.]
Newsgroups: comp.os.os2.misc
From: kitchin@avo.hp.com (Bruce Kitchin)
Subject: Re: Can't install OS/2 Ver 1.3
Organization: Hewlett-Packard, Santa Clara Division
X-Newsreader: TIN [version 1.1.3 PL6]
Distribution: usa
Date: Tue, 13 Oct 1992 15:17:45 GMT

Your basic problem is that OS/2 (whichever version) is an operating
system rather than an application.  Therefore it must be able to be
installed with no software on your disk (or over whatever software
is on your disk).

You do NOT run the installation program from DOS, but you boot from
the installation disk (put it in drive a and reboot the computer or
power cycle it).  It will then lead you through the installation
procedure.

Since you have DOS on your system, you will probably want to enable
dual boot so that you can choose to boot OS/2 or DOS alternatively.
This should be covered in the installation manual.  Most people who
are moving to OS/2 want the ability to go back to Dos when they have
a problem or a program which wont run (under OS/2 2.0 this is a much
rarer situation, but while 1.3 is far better than its predecessors,
there are still programs that it will not run and therefore
you may want to keep a copy of DOS installed).  Somewhere in the
installation procedure you will be either asked whether to install
dual boot or it might do it anyway.

Good luck.
From: kristine@cats.ucsc.edu (chfn)
Newsgroups: comp.os.os2.misc
Subject: Re: Dual Monitors (Mono/Trident 8900 VGA) Problem
Date: 11 Oct 1992 03:25:05 GMT
Organization: University of California, Santa Cruz
NNTP-Posting-Host: am.ucsc.edu


What is 'echomon'?

Thanks.
Newsgroups: comp.os.os2.misc
Subject: Re: Running BASICA crashes OS/2
From: cvafyaga@vmsb.is.csupomona.edu (Srikanth Viswanathan)
Date: 7 Oct 1992 14:44 -0800
 <2OCT199216224637@utarlg.uta.edu> <1992Oct5.175423.20844@midway.uchicago.edu> <1992Oct6.073055.26822@u.washington.edu>
Distribution: world
Organization: California Polytechnic University, Pomona
News-Software: VAX/VMS VNEWS 1.41    

> 
>Guess what folks...it's not fixed in the beta!  Don't try this at home!

It is going to be fixed in the CSD though.  It's one of the APARs listed.

> 
>And who is this PaulDev guy I just met, anyway?  :)

Yeah, I'd like to know too!  Probably some guy at Boca who got a little
bored.

Srikanth
From: jmaynard@oac.hsc.uth.tmc.edu (Jay Maynard)
Newsgroups: comp.os.os2.misc
Subject: Re: CYRIX 387-33: DOES IT WORK THE OS/2???
Date: 14 Oct 1992 17:44:43 GMT
Organization: UT Health Science Center Houston


I'm running a Cyrix 387-40 in my AMD/BIOTEQ 386-40; it runs fine, with no
reported errors. Have you tried the Cyrix diagnostic program that came with
the chip in a DOS window? I'd be suspicious about running a 387-33 in a 386-40
system; I'd suggest going back and springing for the extra speed.
-- 
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
jmaynard@oac.hsc.uth.tmc.edu      | adequately be explained by stupidity.
    Vote for a REAL change on 3 November: Throw out the check-bouncing,
  tax-and-spend Democrat Congress! (obviously, not an opinion of UTHSCH)
Newsgroups: comp.os.os2.misc
From: harris@garfield.catt.ncsu.edu (Michael Harris)
Subject: Re: Why XGA-2?
Organization: North Carolina State University
Date: Tue, 13 Oct 1992 13:35:55 GMT

Here's another...

If you are really picky, the pointer is now a hardware object.  (Sometimes
referred to as a "sprite" in other architectures)  Therefore, it doesn't blink
when you draw under it.  This frees up cpu cycles.  Each time you move the
mouse, several images must be drawn.  If you have a hardware overlay, you
can avoid much of that.

______________________________________________________________________________
     Michael Harris - harris@catt.ncsu.edu or harris@carvm3.vnet.ibm.com
 System Administrator, Computer & Technologies Theme Program, NC State Univ.
(My opinions are my own and do not represent those of NCSU or IBM Corporation)
From: shyguy@ocf.berkeley.edu (David S. Shy)
Newsgroups: comp.os.os2.misc
Subject: Re: Beta Trap
Date: 15 Oct 1992 21:46:24 GMT
Organization: U.C. Berkeley Open Computing Facility
NNTP-Posting-Host: tornado.berkeley.edu

In article <Bw5Avu.L4A@mentor.cc.purdue.edu> syserror@sage.cc.purdue.edu (Artificial Intelligence) writes:
>
>I am among the unfortunate ones which cannot even get the GRE Beta to install.
>The machine is a 486-33 with 4 megs of RAM and an AMI BIOS.  I have heard from
>a (somewhat unreliable) source that the beta requires at least 8 megs of memory
>rather than the 4 necessary for the GA.  I have also heard of possible 
>incompatibilities with the AMI BIOS.  

I don't know about the memory theory, but i don't believe
that the beta is having incompatiblities with
the AMI bios.  I am running the beta on a 486DX/33 w/
12 megs of ram and AMI bios (dating 1990).  Everything
has been running so well that I am considering deleting
the backup of my 2.0 GA (read my previous post about 
not needing to reformat when installing the beta for
more info...).  Before, there were more than frequent
crashes when moving windows around while Procomm+ was 
dialing.  Now I do this on purpose just to try to bring
up an error... haven't been successful yet... :)

Dave
shyguy@ocf.berkeley.edu
From: syserror@sage.cc.purdue.edu (Artificial Intelligence)
Newsgroups: comp.os.os2.misc
Subject: Beta Trap
Summary: Problems with trap 000D and reset on beta installation
Date: 15 Oct 92 04:23:53 GMT
Organization: Purdue University


I am among the unfortunate ones which cannot even get the GRE Beta to install.
After getting the boot section on, the installation continues in graphic mode.
However, from this time on, the machine halts at unpredictable times with
a TRAP 000D.  The farthest I have gotten in installation is disk 8, and, of 
course, a failed installation means starting over from disk 6.  By manipulating
various combinations of wait states, caching, and AT bus timings in the BIOS,
I have gotten it to hard reset at unpredictable times rather than trip a TRAP.
The machine is a 486-33 with 4 megs of RAM and an AMI BIOS.  I have heard from
a (somewhat unreliable) source that the beta requires at least 8 megs of memory
rather than the 4 necessary for the GA.  I have also heard of possible 
incompatibilities with the AMI BIOS.  

If anyone knows the cause of TRAP 000D, can affirm or refute the RAM or BIOS
theories, or has had similar problems or a potential solution, please let me
know.

Thanks in advance-


Aaron
-- 
Lifetimes come and go, memories pass and fade;
The frailties of carbon based life shall yield
To the superior permanence of silicon...
From: Andrew Tong
Newsgroups: comp.os.os2.misc
Subject: Changing Printing options...
Date: 10 Oct 1992 22:40:30 GMT
Organization: California Institute of Technology, Pasadena
NNTP-Posting-Host: scratchy.caltech.edu
Originator: werdna@scratchy

Is there any way to change the way OS/2 handles DOS and Windows print  
jobs?

Apparently, OS/2 tries to print the job as the job is being printed by the  
program.  I want OS/2 to hold the job until after the program has finished  
outputting the whole thing, then dump it all to the printer in one big  
lump.

(What's happening is this: Whenever I print from Coreldraw or Pagemaker,  
the printer will go for a couple of lines, and then wait for a long time.   
With a deskjet, this is not desirable, as the printer "resets" its  
printhead after moments of inactivity....)
Newsgroups: comp.os.os2.misc
Subject: Scanner driver's GP fault
From: ghdai@vax1.umkc.edu
Date: Tue, 13 Oct 1992 16:17:24 GMT
Organization: University of Missouri - Kansas City

Hi, there,

Just before my lab upgraded the OS for a 486 machine, my boss bought a
flatbed scanner (Envision ENV3000, Mustek 3000C-compatible).  I had objected
him in buying it because it came with Micrografx's Picture Publisher LE for
Windoze.  What we need is OS/2 version of the software.  But all is too late.
The PP could drive the scanner when windoze 3.1 was there, buy after
installing OS/2 2.0, it cannot be used any more since the MUSTEKA4 scanner
driver causes GP fault once you try to scan.  Anybody knows what can be done
to solve the problem, please give me a reply.  Thanks in advance.

Newsgroups: comp.os.os2.misc