HDTenEightyP/NetNews huggingface dataset:
From: db3l@ans.net (David Bolen)
Subject: Re: OS/2 help needed!  comm and speed problems, etc.
Date: Fri, 11 Sep 1992 11:06:04 GMT
	<1992Sep11.070336.1@ducvax.auburn.edu>
Organization: Advanced Network & Services, Inc. - Elmsford, NY

In article <1992Sep11.070336.1@ducvax.auburn.edu> hank@ducvax.auburn.edu writes:

>In article <1992Sep11.052720.21425@ans.net>, db3l@ans.net (David Bolen) writes:
>> It's dependent on the filesystem you are using.  For any of your FAT
>> partitions (and the floppy), the DISKCACHE line controls things. (...)
>> Check out the command reference (look in the Information folder) for more
>> details.
>>
>>If you have an HPFS drive, then the size of the cache is set in the /C: 
>>option on the IFS= line that loads HPFS.IFS.  (...)
>
>The on-line ref says that DISKCACHE applies to HPFS drives also (search
>on "performance", then do "improving system performance", then check the
>HPFS entry).  From what I've seen on this group, the information in the
>on-line ref is incorrect.

Hmm - this (mis)information isn't in the command reference itself, but only
available through the master help index.  In any event, I think you're right
and that it's a pretty safe bet that it's a typo.  Even without the
information from the newsgroup, if you just try to match up the information
for "Improving I/O performance - HPFS" vs "... FAT", you'll see they can't
both use DISKCACHE:

   * One shows the threshold value as sectors, and the other as KB.  In the
     online command reference, the DISKCACHE description uses sectors for
     the threshold, while the HPFS.IFS argument /CRECL sets the threshold
     as KB.

   * The "..performance - HPFS" description says the maximum cache is 2MB,
     while the FAT description puts no absolute maximum on the cache size.
     Again, the FAT description agrees with the description of DISKCACHE in
     the command reference (well, actually the DISKCACHE entry does specify
     a 14MB maximum), while the HPFS entry agrees with the description of
     HPFS.IFS.

It's a good point though - it could cause confusion.

--
-- David
--
/-----------------------------------------------------------------------\
 \              David Bolen             \  Internet: db3l@ans.net      /
  |   Advanced Network & Services, Inc.   \   Phone: (914) 789-5327   |
 / 100 Clearbrook Road, Elmsford, NY 10523  \   Fax: (914) 789-5310    \
\-----------------------------------------------------------------------/
From: eaj@acpub.duke.edu (Edward A. Johnson)
Newsgroups: comp.os.os2.misc
Subject: zoo archiver
Date: 14 Sep 92 22:16:33 GMT
Organization: Duke University; Durham, N.C.

I have down-loaded a bunch of .zoo files from hobbes together with
zoo210.exe and zoo210e.exe. I presumed that one un-zooed the .zoo files
by entering at the os/2 command prompt:

zoo210 zoofile 

Nothing happens, i.e., no new files appear in the directory

If I type:

zoo210e zoofile

The window gives a SYS3176 error message. 
C
Moreover, if I try to unzip hpljw.zip that I downloaded from CompuServe
IBMOS2, using pkunzip I get a "Error in zip file, use PKZipFix" Where do
find such a utility?

Help!

-Ted-

Department of Cell Biology
Duke University Medical Center
Durham, NC 27710
C
C
C
C
C
B
C
C
C
C
C
B
B
B
B
B
B
A
A
A
A
A
A
A
A
A
A
A
A
The window gives a
Xref: sparky comp.os.os2.misc:29597 comp.periphs.scsi:4402
From: ts@cup.portal.com (Tim W Smith)
Newsgroups: comp.os.os2.misc,comp.periphs.scsi
Subject: Re: CDROM drives and OS2ASPI.DMD
Date: Tue,  8 Sep 92 20:54:04 PDT
Organization: The Portal System (TM)

> I've tried a few combinations of switches on AHA154X.ADD to prevent the
> ASPI driver from allocating the CDROM per the instructions in the aspibeta.zoo
> kit (OS2_20.TXT):
> 
>    BASEDEV=AHA154X.ADD /A:0 /!DM:3 /SM:3
> and
>    BASEDEV=AHA154X.ADD /A:0 /!DM:3
>
> This technique seems a little strange to me since it's not clear how the /!
> switches communicate to the a specific driver so it's possible I have this
> part wrong.

Is there any evidence that these switches actually do anything?  I work for
a company that writes SCSI software, and I put a breakpoint at our ADD's
entry point and poked around with the OS/2 debugger.  OS/2 does *NOT*
appear to actually pass in the BASEDEV line to the ADD, even though the
PDD and ADD specs claim it does.  Either I made a dumb mistake, or this
part of BASDEV handing is not yet present, which would explain why these
switches didn't help you!

(As to how these switches communicate with other drivers, that is via
flags in the device table built by the ADD and examined by DMDs.  There
are flags in that table that the DM and SM arguments control.)

--Tim Smith
Newsgroups: comp.os.os2.misc
From: gwebster@ugly.UVic.CA (This space for rent)
Subject: Re: TE2 and <--
Organization: University of Victoria, Victoria, BC, Canada
Date: Sun, 13 Sep 92 00:44:16 GMT

In article <BuHn97.8tr@undergrad.math.waterloo.edu> gtaylor@undergrad.math.waterloo.edu (Gord Taylor) writes:
>In article <1992Aug31.094702.13681@actrix.gen.nz> Steve.Withers@bbs.actrix.gen.nz writes:
>>In article <klliou.715197673@milton> klliou@milton.u.washington.edu (Kan-Lee Liou) writes:
>>> I am using TE2 to emulate VT100 to connect to both UNIX and VMS machines 
>>> through my .32 bis modem.
>>> I keep getting problems in using editors (vi for UNIX or ed for VMS).
>>> The problems are parts of the text I am editing may become invisible (actually,
>>> it is happening now).  No text is lost, but I just cannot see it.
>>> One example is if I use the <-- (move left) key, all the characters it goes 
>>> through will disappear.  I can use the --> (move right) key to let them show up
>>> again, but it's really a pain..
>>> How can  I modify the setup and solve these problems?
>>> Thank you.
>
>Actually, I get much the same problem...it isn't (as far as I can tell) a VT-100 emulation problem at your end as it is at the UNIX end...Whenever I connect to U of Waterloo (the U I attend), I get the same thing when I'm in OS/2, when I used to use Windows 3.1...everywhere except when I used DOS (probably my term program compensated for it at that point because the programmers were aware of the error ie. Telix)

I used to have the same problem using Procomm Plus in DOS, then under OS/2,
until a friend messed around with the settings. He changed the backspace
translation to non-destructive, and it cured the problem. TE/2 has an 
entry in the TE2.ini file to change that too. If you are using the default
TE2.INI file, go to line 63 (in my file, anyway) which says: 

;VT100Backspace FALSE         ; Set true if you need a destructive backspace

Remove the ";" (this will un-comment the line). That should do it. Worked for
me anyway.






-- 
________________________________________________________________________
| Gord Webster           | Be cool or be cast out - Rush               |
| University of Victoria | OS/2, it's curtains for Windows             |
| Victoria, B.C., Canada | Oxygen is for losers - Red Dwarf            |
From: tom@longs.lance.colostate.edu (Tom Aurand)
Newsgroups: comp.os.os2.misc
Subject: Re: New COMMPAK2.DLL for TE/2
Date: 15 Sep 92 22:26:09 GMT
Organization: Colorado State U. Engineering College, Ft. Collins, CO 80523

In article <18136.117.uupcb@cutting.hou.tx.us>, matt.johnson@cutting.hou.tx.us (Matt Johnson) writes:
|> ST>I've been playing with the new COMMPAK2.DLL contained in cpk2_102.zoo and it
|> ST>seems to be faster than the old one.....
|> ST>Any comments?
|> 
|> I haven't noticed much improvement when TE/2 is the only session running, but
|> CPK_102 seems to make great improvements when other CPU intensive tasks are
|> running at the same time that a download is in progress...which is most of
|> the time for me. <g>
|> 

I still can't start a winos2 app during a V.32bis V.42 Ymodem-G download.
I get a crc error in the download, TE/2 falls back to terminal mode,
and then the file goes beeping and puking across my screen
for the rest of its life.

This on an hpfs that is on a quick 4Mb ram buffered, EISA bus-mastering SCSI.
From: tmottone@klaava.Helsinki.FI (Teemu Mottonen)
Newsgroups: comp.os.os2.misc
Subject: Re: SYS2237 ? NPX ?
Date: 11 Sep 92 13:30:59 GMT
Organization: University of Helsinki

In article <19920911081059.h198@hosp.med.umich.edu> h198@hosp.med.umich.edu writes:
>> I was recently playing with WOWII (a modplayer for DOS). Suddenly
>> the program crashed and I got this error message: "SYS2237: DosKrnl:
>> A NPX instruction was attempted but no NPX is present."
>> What does this mean ? What's a NPX ?
<...>
>  There are other things that can cause this.   If the program really uses
>  a numeric coprocessor, OS/2 should emulate it.   There is a fix out for
>  this called VBIOS.SYS (replacement VDD).   Unfortunately, it doesn't fix
>  all of these NPX problems.   Try it, and if it doesn't work, report it
>  to IBM.   I am currently working with an IBM person on one of these.

I don't think the program uses the coprocessor, it just plays MOD sound
files through my Soundblaster. It does use a non-standard tweaked VGA
mode (360x240x256?) though, could that cause the NPX error ? I'll try
the VBIOS fix.

Teemu.
-- 
Teemu Mottonen
Dept. of Computer Science    tmottone@kruuna.helsinki.fi
Univ. of Helsinki, Finland   tmottone@klaava.helsinki.fi
From: "robert fielder" <robert.fielder@canrem.com>
Newsgroups: comp.os.os2.misc
Subject: un:csd dates
Date: 4 Sep 92 21:13:24 EST
Reply-To: "robert fielder" <robert.fielder@canrem.com>
Distribution: comp
Organization: Canada Remote Systems


BD>Sadly, no. They are IBM reps  for a major corporation. They seem  pretty
BD>frustrated to me, though.

Bill:

OS/2 is a super-complex piece of software.  That it takes time to get
it right it no surprise to anyone who understands this.  For my money,
I would wait an extra month or three to get a solid product, than
something sooner that takes more upgrades later.

How many of these frustrated individuals are salepeople, as opposed to
the techie sort?  Sales people have run places like IBM for far, far
too long; they have no idea of how to generate realistic completion
dates or schedules, and do more harm to any corporation's credibility
than all other factors taken together!

Robert

Entered on Fri  09-04-1992  18:15:51 from Brampton, Ontario, Canada
---
  DeLuxe 1.21 #502  I see the light with Windows - on the other side
--
Canada Remote Systems  - Toronto, Ontario/Detroit, MI
World's Largest PCBOARD System - 416-629-7000/629-7044
From: kslater@sps.pgh.pa.us (Kevin J. Slater)
Newsgroups: comp.os.os2.misc
Subject: Can I wax some OS/2 files..
Date: 5 Sep 92 12:11:32 GMT
Organization: SPS ACAD BBS, (412) 487-3637

I *need* space on my os/2 disk drives badly. Are there some files that 
are installed with os/2 that I can safely delete? Is there a listing 
anywhere of what files and .dll's are for what programs? How about a 
program to see what program(s) use a particular .dll?

Here are some files that I think maybe could go:

\os2\cdfs.ifs
\os2\cdrom.sys
\os2\ibmint13.i13
\os2\keyb.com
\os2\os2dasd.dmd
\os2\os2scsi.dmd
\os2\viewdoc.exe - What's this do anyway?
\os2\bitmap\os2logo.bmp
\os2\dll\ucdfs.dll
\os2\mdos\vcdrom.sys
\os2\mdos\winos2\fixwp.exe - I don't own WP
\os2\mdos\winos2\system\hercules.drv
\os2\system\ucdfs.msg

Surely there must be plenty more hidden amongst those 32M of files that 
OS/2 default installs?! I'll still be using Windows (some stuff) and I 
use plenty of old DOS stuff. But I don't have a CDROM (and probably won't 
anytime soon) and even if I need some of the files back, I can just 
uncompress them from floppies, right?

....Kevin

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Kevin J. Slater (kslater@sps.pgh.pa.us)       | Believe in the Lord Jesus
Slater Programming Services  | CI$ 73077,2427 | and you will be saved - you &
Glenshaw, PA 15116-0027      | bix kslater    | your household. - Acts 16:31
- - - - - - - - - - - - WESPAC BBS (412) 487-3637 - - - - - - - - - - - - - -
From: bert.tyler@satalink.com (Bert Tyler)
Newsgroups: comp.os.os2.misc
Subject: Video modes not supported
Date: 6 Sep 92 09:14:00 GMT
Reply-To: bert.tyler@satalink.com (Bert Tyler)
Organization: Datamax/Satalink Connection * Ivyland, PA (215) 443-9434

NA>I have a Genoa 6400 video card.  I'm running OS/2 2.0 on a 486-33
NA>The question:  Why can't I access some of my video modes when OS/2
NA>is running?  (I tried in a full-screen DOS session, and it merely
NA>locked up the system when I went for my 800x600x256 mode.  It also
NA>get screwed when I switch to 640x480x256 and many other modes.)
NA>Is there any way to get past this problem?

Neal, blame your OS/2 video driver (and this is *not* an OS/2-specific
problem: many Windows video drivers cause similar problems when you
attempt to run chip-specific high-rez graphics in a full-screen DOS
window).

The problem is that your OS/2 (or Windows) video driver is not
correctly virtualizing the chip-specific I/O ports that have to
be accessed to throw your video adapter into its high-rez modes.
This can crash the DOS session and/or can crash the OS/2 (or Windows)
screen when you return to the OS/2 (or Windows) desktop afterwards.

Another frequent symptom is that you *can* throw your adapter into
a high-rez mode in a DOS session, but then switching back to the
OS/2 (or Windows) desktop while that DOS session is in a high-rez mode
yields a trashed image on either the OS/2 (or Windows) desktop or - when
you switch back to the DOS session - the DOS image.  That's because
many video drivers only save the portions of the adapter's memory used
by a "normal" VGA adapter (part of the first 256K), and not all of the
video memory used in a SuperVGA mode (1 MB or more).

(Under OS/2 1.3, folks who used DOS programs which used my freeware
XGA drivers to throw their XGA adapter into a high-rez mode in a
DOS session told me that when they returned to their OS/2 session,
all of the OS/2 desktop's text was gone.  Windows folks had it worse
(or maybe better - matter of opinion, I supppose) - the Windows XGA
driver virtualized the XGA's registers completely away, so that my
XGA drivers would claim that you didn't have an XGA adapter at all.)

                   Bert Tyler   (bert.tyler@satalink.com)
---
 . DeLuxe./386 1.25 #343sa . Your mileage may vary.  Your car may not run.
From: Gary.Woodman@anu.edu.au (Gary Woodman)
Newsgroups: comp.os.os2.misc
Subject: Re: News flash :::: Plus Hardcard drivers are now available for OS/2
Date: 15 Sep 92 01:02:56 GMT
Organization: Computer Services Centre, Australian National University
NNTP-Posting-Host: gurrung.anu.edu.au

In article <f8vnnzr.msmith@netcom.com> msmith@netcom.com (Martin P. Smith) writes:

>I will most likely pick up the driver anyhow but I am curious what you mean.

Could you please upload this to ftp-os2.nmsu.edu for us here in the outback?

--
Gary.Woodman@anu.edu.au         This post made from 100% recycled electrons.
From: nina@panix.com (Nina Yuan)
Newsgroups: comp.os.os2.misc
Subject: Re: Need help selecting FAST VIDEO CARD!
Keywords: VIDEO, SPEED, FREAK!
Date: 13 Sep 92 15:03:27 GMT
Organization: PANIX Public Access Unix, NYC

In <1992Sep13.001702.24333@midway.uchicago.edu> sip1@ellis.uchicago.edu (Timothy F. Sipples) writes:

>Unless Diamond (makers of the Stealth) can guarantee OS/2 2.0 drivers
>(and it pays to ask them -- and have them put it in writing), I would
>stay away from their product for the time being.

But on the non-accelerated side, the Speedstar (ET4000) works fine, right?
I'm finally buying an OS/2-capable system (486/33) and selecting an 
appropriate video card has been a real headache.  I'm leaning towards getting
a simple ET4000 like the Speedstar (for the rumored support in the next
release) for the time being, and waiting for the ATI Ultra Pro (25 mil
WinMarks!) and its drivers to come out.  Anyone have better suggestions for
me?  (I'm just looking forward to junking my old AT and finally being able
to run OS/2!)

-nhy

-- 
-------------------------------------------------------------------------
Nina H. Yuan
Harvard College             Panix -- Public Access Unix & Internet of NYC
yuan1@husc.harvard.edu      nina@panix.com
Newsgroups: comp.os.os2.misc
From: affie@earley.sns.neuphilologie.uni-tuebingen.de (Ralf "Affie" Hauser)
Subject: Re: First time OS/2 weirdnes and questions...
Organization: sns
Date: Wed, 9 Sep 1992 15:12:57 GMT

In article <gjw900.13.716037791@anu.edu.au>, gjw900@anu.edu.au (Gary Woodman) writes:
|> In article <sNq0PB1w164w@dvss.UUCP> dvss!jtroy@udel.edu (Jay Troy) writes:
|> 
|> My home system freezes every 7-10 days, with the HD light hard on. It isn't 
|> doing anything that I can tell. Maybe it's a hardware problem; my HD didn't 
|> like being kicked around by the WPS in 4 meg.
|> 

I had the same problems in the earley days of computing...

I fixed the problem by changing the CMOS setup of my system (486/33, 16MB, AMI
BIOS dated June 91, ADAPTEC 1542B):

	There is a setting in the "Advanced BIOS setup" called: 
		BUS CLCK RATE or something like that
		I can't remember the name but I can look for it this evening...

	Anyway, it has four (or five) different possible values
		2,5   3   4   (5)  6   
	and it determines the clock divisor for the system's bus.

	Anyway, I increased the value from 2,5 (33Mhz/2,5: optimal)
	to 3 (33Mhz/3: not that optimal but far from being bad)
	and everything worked fine.
	It has to do with my ADAPTEC 1542B and my disk drives (HPFS & FAT)
	but don't ask me for a explanation of why and why not.

	Anyway, it works!!!

I hope this is of any help for you!

	affie

 ______________________________________________________________________________

 Ralf "Affie" Hauser                            Seminar fuer Sprachwissenschaft
 Kleine Wilhelmstrasse 113                         7400 Tuebingen - WestGermany
 e-mail: affie@frege.sns.neuphilologie.uni-tuebingen.de

	'The human mind ordinarily operates at only ten percent of its capacity
		- the rest is overhead for the operating system.'
 ______________________________________________________________________________
Newsgroups: comp.os.os2.misc
From: parry@yoyo.cc.monash.edu.au (Tom J Parry)
Subject: Read only files, HPFS, wrong, wrong, wrong
Originator: parry@yoyo.cc.monash.edu.au
Organization: Monash University, Melb., Australia.
Date: Thu, 10 Sep 1992 05:05:59 GMT

After playing with GNU RCS for a while I have come to the conclusion that
the DOS System/Hidden/Read Only attributes for files are a little stupid.

First of all, what is the difference  between these three attributes. In
the (almost) decade that I have been playing with PC's I am yet to work out
why all 3 of these exist, when the effect of all three seems to be the
same.

My first question is therefore, why did HPFS hang on to these? Read only
files should not be hidden, hidden should not be read only etc. Compared to
the UNIX method of file protection it is quite annoying.

The reason this has come up is, as I said above, RCS. Being a UNIX program,
RCS marks non-locked checked-out files as read only. It gives write access
to those you have locked. This means you won't end up modifying a file you
have not checked out of the RCS.  Under UNIX it works great, but under the
DOS style (and hence HPFS), you check out a file, but then can not compile
it because it is read only. This is especially painful when using GNUMAKE
(but I'll save that sob story for my next post...)

So, can anybody think of a solution to the RCS problem? 1) would be to get
the source and strip out all the read only stuff. 2) rewrite HPFS with some
better protection mechanisms for files [unfortunately, I'm a little busy
this week so I won't get around to the HPFS rewrite :-) ]

But, if we strip out this bit of code from RCS we are taking out a very
nice part of it. Maybe HPFS stands for High Performance FAT System.



-- 
Tom J Parry.
Your reality is a figment of my imagination.
Newsgroups: comp.os.os2.misc
From: kaz@iastate.edu (Jimmy Buffet)
Subject: Vmode and SVGA and OS/2
Summary: Speedstar VMode and SVGA
Keywords: Diamond Speedstar 24
Organization: Iowa State University, Ames IA
Date: Sat, 12 Sep 1992 21:06:54 GMT

After receiving help from this newsgroup (thanks!) about running vmode
in a dos box and then running svga on, I tried to do so and haven't tested
the SVGA drivers yet.  However, now when I run a full screen windows
session, the windows screen is WAY too tall.  All the tests in vmode for
custom monitor looked fine... any ideas?  Thanks...

Kaz (kaz@iastate.edu)
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Newsgroups: comp.os.os2.misc
Subject: Re: mouse probs with os2
Date: 15 Sep 92 15:48:06 GMT
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago

In article <1992Sep15.001509.19746@ccu1.aukuni.ac.nz> elejw@ccu1.aukuni.ac.nz (James Williams) writes:
>I've been running 0s2 v2 for a few weeks now, and I'm very impressed with it.
>One or 2 probs tho'. When I run the game RETALIATOR, the system doesn't 
>recognise the mouse. This may be because RETALIATOR has it's own mouse driver
>built in, and os2 can't handle this?

You might try running the stub mouse driver (\OS2\MDOS\MOUSE) before
running Retaliator.

>Um,,,Also the zx specrum emulator Z80 ( a beautiful piece of s/w, v1.41) 
>works on my friends  486 33 system, but not on my 386 20 system! to compound
>the problem, the spectrum emulator JPP works on my system, but not his!

Not sure on this one.  Have you tried a specific DOS session (per
Appendix E of your Installation Guide and/or the online Command
Reference under VMDISK)?

-- 
Timothy F. Sipples      | The OS/2 FREQ. ASKED QUESTIONS LIST is avail. from
sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/faq.
Dept. of Econ., Univ.   | Or from LISTSERV@BLEKUL11.BITNET (send "HELP").
of Chicago, 60637       | Family Values Means a Job
From: dic5340@hertz.njit.edu (David Charlap)
Newsgroups: comp.os.os2.misc
Subject: Re: zoo archiver
Date: 15 Sep 92 16:25:47 GMT
Organization: New Jersey Institute of Technology, Newark, N.J.

In article <5324@news.duke.edu> eaj@acpub.duke.edu (Edward A. Johnson) writes:
>I have down-loaded a bunch of .zoo files from hobbes together with
>zoo210.exe and zoo210e.exe. I presumed that one un-zooed the .zoo files
>by entering at the os/2 command prompt:
>
>zoo210 zoofile 
>
>Nothing happens, i.e., no new files appear in the directory
>
>If I type:
>
>zoo210e zoofile

Zoo210e.exe is a self-extracting archive.  It is not the zoo program.
To get the programs from it:

1) Move the file (zoo210e.exe) into an empty directory.
2) Go to that directory
3) Run zoo210e.exe with no parameters

The program will create many files in the directory, including:

zoo.exe - the zoo program
zoo.man - the manual pages

There are other files as well.

I believe zoo210.exe also contains source code.

Once you extract the zoo program, read the instructions.  The syntax
is fairly simple, but you should know some of the basic parameters.
Type "zoo h" for help.
-- 
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"