HDTenEightyP/NetNews huggingface dataset:
From: dabl2@nlm.nih.gov (Don A.B. Lindbergh)
Subject: Re: OS/2 and SCSI
Organization: National Library of Medicine
Date: Fri, 31 Jul 92 14:43:38 GMT

>The following is from memory.  It may be incorrect in detail, but I
>believe that it is essential correct in broad.
>
>I believe the problem is with how the 1542 is set up.  'Out of the
>box' behaviour has the timing between the hard and floppy disks set in
>such a way that the OS/2 installation fails.  This leads to all the
>disk thrashing, etc.  I think you can change the timing on the 1542 by
>changing some jumpers on the controller, but I can't state that with
>certainty because I don't have this kind of card.
>

I have a 1542B and my understanding is that the initial problems most people
were having (including me) with the first release aha154x.add driver was
floppy access WHILE the hardisk was doing stuff caused errors.  It was 
apparently because the bus on/off time needed to be re-programmed in this 
situation and that code needed to be put in the driver, hence the updated
aha154x.add driver.  Since then there have been at least one more I think,
addressing different issues like > 1 Gig support.  The bus on/off time
parameters are software only adjustable, so it's unlikely that hardware
switches would accomplish what you suggest, but I am no 1542B 'expert'.
The simple way to get a successful installation is to let the hardisk
continue 'doing it's thing' around disk 9 (3.5") until it's finished
THEN insert the next disk.  After the installation is all over, replace
the aha54x.add driver with the new one.  I don't think you can easily
aha154x.add driver on the original diskettes because it seems to be 'packed'
with other stuff.  If you want to get tricky, at the step between disks 5 and
6 (I think) there is a 'break" in the installation, where you reboot and things
go 'graphical'  at this step, you could boot from an OS/2 floppy (or really
even DOS if you're doing FAT) and put the 'good' aha154x.add driver in place
in the /OS2 directory. (I think it shouldn't have put the 'bad' one there
at this point.)  Then reboot from the hardisk and continue with the
installation.  This worked for me, I'm guessing that the install sees that
the aha154x.add is already there and doesn't add it, maybe I was just lucky.
Actually now that I think about it, the way I understand the config.sys to work
is that it is parsed in it's entirety and only relevent stuff is used, which is
why it really doesn't matter if the INT13 driver is in the config.sys.  As long
as the DEVICE=aha154x.add is ALSO in there, THAT is the one that's used.
Therefore, it might be wise to make sure that line is in the config.sys during
the 'break'.  But this is really for thrill seekers, the easiest way is to just
let the drive settle down before continuing at disk 9.  Whew, sorry for the
lengthy explanation.

--Don
dabl2@lhc.nlm.nih.gov
From: mmtl@hobson.cc.flinders.edu.au (T.Lampre)
Newsgroups: comp.os.os2.misc
Subject: Re: The Ultimate OS/2 FTP Source
Date: 24 Jul 92 00:59:14 GMT
Organization: Flinders University

In article <64117@hydra.gatech.EDU> ccusekh@prism.gatech.EDU (Kevin Hodge) writes:
>In article <1992Jul22.151625.28860@watson.ibm.com> nrt@watson.ibm.com (Nicholas R. Trio) writes:
>NK: I think that it's valid to say software.watson.ibm.com will have the
>NK: latest patches for OS/2.  As far as public-domain software, I am really 
>NK: not set up for it (and haven't done any of the paperwork to allow it
>NK: to happen here).
>
>Gee Nick, what are you waiting for?  :-)
>
>   

Probably waiting for advice from the legal department. 

Were IBM to start providing access to Freeware, Shareware and
copylefted software they would have to make all sorts of disclaimers
about not endorsing or warranting the software stored there.

IBM seems to need to be more careful than most other companies in not
seeming to favour any other party at the possible expense of others.

In this age of litigation the last thing I would want to see is a case
of 'I lost income on my Widget Management program because you guys
didn't put it up on your server'. Stupid yes, but just look at the
suits that get filed and it's not improbable.

I would prefer to see the site used for patches, CSD's, drivers and
annoucements. We are already well served by ftp-os2 & other
'non-interested' parties for other wares.

Trevor Lampre
MIS Unit
Flinders University of South Australia
From: unixg.ubc.ca!ochealth@overmind.mind.org
Newsgroups: comp.os.os2.misc
Subject: Re: OO File system (was re: os/2's som)
Date: 22 Jul 92 21:44:00 GMT
Organization: University of British Columbia, Vancouver, B.C., Canada
X-mailer: Stadel 3.4a-227
X-Spam-content: irrelevant

In article <BrssDz.Dyw@apollo.hp.com> ced@APOLLO.HP.COM (Carl Davidson) 
writes:
>
>The best example of an object-oriented file system I know of is the 
>Apollo Domain file system. It does *precisely* what Pete describes, 
>i.e. the I/O system knows how to determine the type of object you are 
>

Hahahahhahha!

If NT has an operating system like Domain, it'll fall flat on it's
face! Domain's BSD type UNIX sucked rocks! Incompatible, unstable, 
unpredictable, etc.

Gimme Sun hardware/software any day over Apollo. Good thing HP bailed
Apollo out.

>-- 
>Carl Davidson  (508) 436-4361  |
>Chelmsford System Software Lab | Microkernels: Where less is more.
>The Hewlett-Packard Company    | 
>DOMAIN: ced@apollo.hp.com      |


-- 

_____________________________________________________________________________
_
jpm: ochealth@unixg.ubc.ca         
                           Happily using OS/2 2.0 because MS Windows isN'T 
___
                                                      Insert VapourFeature 
^^^
Newsgroups: comp.os.os2.misc
From: jar@inel.gov (Jeffry A Rich)
Subject: HPFS not finding bad blocks
Organization: Idaho National Engineering Laboratory, Idaho Falls, Idaho
Date: Tue, 28 Jul 92 16:55:53 GMT

I tried sending this "Cry for help" in the Advocacy group, but, apparently that was the wrong area. I'll try again.

I have a 130mb hard drive with two known media errors on the disk. I can bypass these errors in dos/windows by using pctools.

When using OS/2 and HPFS, these errors manifest themselves within applications that I've installed on the disk. I was under the impression that if you format the drive while installing OS/2, the file system automatically detects these media errors and works around them. This does not seem to be happening.

If anyone has any thoughts concerning this problem, I would be most appreciative in hearing them.

 Regards,
   JR Rich
========== long legal disclaimer follows, press n to skip ===========

Neither the United States Government or the Idaho National Engineering
Laboratory or any of their employees, makes any warranty, whatsoever,
implied, or assumes any legal liability or responsibility regarding any
information, disclosed, or represents that its use would not infringe
privately owned rights.  No specific reference constitutes or implies
endorsement, recommendation, or favoring by the United States
Government or the Idaho National Engineering Laboratory.  The views and
opinions expressed herein do not necessarily reflect those of the
United States Government or the Idaho National Engineering Laboratory,
and shall not be used for advertising or product endorsement purposes.
Newsgroups: comp.os.os2.misc
From: bash@tware.com (Paul Bash)
Subject: Re: Has Colorado created OS/2 drivers?
Organization: Techware Design, Boulder, Colorado.
Date: Wed, 22 Jul 1992 18:27:05 GMT

In article <protein.711773060@garfield.catt.ncsu.edu> protein@garfield.catt.ncsu.edu (Chris Blackmon) writes:
>Has Colorado MicroSystems created drivers for their DJ (Jumbo)
>series tape backups yet?  Are they due sometime?
>
>tnx.
>
>

Colorado _Memory_ Systems was advertising in the Denver employment adds a 
month or so ago for people with OS/2 device driver experience. This implies
to me that the drivers aren't going to be available any time soon now (my
guess is at least 6 months).
  
-- 
Paul Bash                                                   Techware Design 
bash@tware.com                                              Boulder, CO  U.S.A.
Organization: Queen's University at Kingston
Date: Friday, 24 Jul 1992 08:41:29 EDT
From: Jim Gerlach <GERLACHJ@QUCDN.QueensU.CA>
Newsgroups: comp.os.os2.misc
Subject: RAM disks in DOS sessions

I use a statistics package (Systat and Sygraph) that makes only limited use of
EMS memory (1.5 Mb) but will use a RAM disk if available. Is it possible to
setup a virtual RAM disk for the full screen DOS session I use to run this
app (I have 8 Mb of RAM)?

Thanx for any help. Jim

Jim Gerlach - Cancer Research Laboratories
James.H.Gerlach@QueensU.CA                    Queen's University
GERLACHJ@QUCDN.QueensU.CA (NetNorth/BITNET)   Room A309A, Botterell Hall
tel (613) 545-6446                            Kingston, Ontario
fax (613) 545-6830                            CANADA  K7L 3N6
Newsgroups: comp.os.os2.misc
From: Bill.Hirt@mtask.omahug.org (Bill Hirt)
Newsgroups: comp.os.os2.misc
Subject: OS/2 
Date: 25 Jul 92 10:55:24 CST
Reply-To: bill.hirt@mtask.omahug.org
Organization: Multitasking Systems, Kansas City
Followup-To: comp.os.os2.misc


 RJ> Now, the BBS I am trying to run is a Searchlight BBS, 
 RJ> on a machine with 4 Megs
 RJ> of ram (soon being upgraded to 16) on a 486/33. If 
 RJ> anyone has any suggestions
 RJ> on how to get the board to run, I would be most greatful.

I have several friends who have tried running DOS-based BBS systems under OS/2
and it is difficult to get much performance on inbound transfers. They were
trying 9600+ transfers. Since you are only at 2400, you might get by. You try
using Searchlight with a FOSSIL and see if that helps. There a special FOSSIL
driver for OS/2 DOS windows (x00v149a.zip). It should be available from most
Fido-based BBS systems or you can call my system at (816) 587-5360 and download
it. It is also available on the hobbes.nm archive.

 RJ> And, if anyone has suggestions on either shareware or 
 RJ> commercial OS/2 BBS's 
 RJ> that I should look at, drop me a line...

I used to run Searchlight and made the move to Maximus/2 earlier this year. I
haven't been sorry. Maximus is free, unless you run a commercial system, and
extremely configurable. It also runs great under OS/2 and is very stingy in the
amount of CPU time it uses. I run on a 386-40 with 16 meg and unless the user
on the line is doing some really intensive disk access, I don't even know they
are there.

There are also several others like Simplex, but Max so far is the predominant
OS/2 BBS package. Several other packages apparently are being ported, so there
should be even a wider selection this fall.

Newsgroups: comp.os.os2.misc
From: nrt@watson.ibm.com (Nicholas R. Trio)
Subject: Re: The Ultimate OS/2 FTP Source
Date: Fri, 24 Jul 1992 16:46:34 GMT
Disclaimer: This posting represents the poster's views, not necessarily those of IBM
Organization: IBM T.J. Watson Research Center
Keywords: FTP, OS/2

The IP address for software.watson.ibm.com is:

            129.34.139.5

It's really not that random. :-)

Nick Trio (nrt@watson.ibm.com)
IBM T.J. Watson Research Center

Newsgroups: comp.os.os2.misc
From: mike@mustang.uucp (Mike Hoffos)
Subject: Re: Does 800x600x256 on the VGA part of a Graphics Ultra work under OS/2?
Organization: None; it is a private machine
Date: Tue, 21 Jul 1992 15:09:20 GMT

In article <1992Jul20.174848.7662@njitgw.njit.edu> dic5340@hertz.njit.edu (David Charlap) writes:
>In article <1992Jul18.205156.4997@mustang.uucp> mike@mustang.uucp (Mike Hoffos) writes:
>>Under MS-DOS 5.0, I frequently used gif viewers that allowed me to use
>>the 800x600x256 mode that the VGA portion of the ATI Graphics Ultra offers.
>>
>>No matter what I do though, OS/2 just doesn't like to let the same
>>programs in a DOS full-screen session go into the mode. When they try
>>to enter 800x600x256, all that happens is that the screen stays in text
>>mode, but the colors get all funny.  When you give the keystroke that
>>would get you out of the picture viewing mode, the screen corrects itself.
>
>Did you install the VSVGA.SYS driver into CONFIG.SYS?  I thought svga
>on does that automatically, but it might not have.  Go into CONFIG.SYS
>and be sure that the reference to VVGA.SYS isn't there (or is
>commented off) and that VSVGA.SYS is there.
>
>-- 
>   |)  David Charlap           "I don't even represent myself
>  /|_  dic5340@hertz.njit.edu   sometimes so NJIT is right out!.
> ((|,)
>  ~|~  Hi! I am a .signature virus, copy me into your .signature file.

Yep, I did do svga on; it did nothing.  And my config.sys does have
the vsvga.sys there.  My question still stands; does anyone with an
Ultra get 800x600x256 in a DOS full-screen session if a program tries to
fiddle the VGA portion into the mode?

Mike Hoffos

-- 
mike@mustang.cuc.ab.ca                    | WANTED: A 360x360 dpi 24-pin DVI
mhoffos@cuug.ab.ca (not quite reliable)   | driver that compiles under UNIX.
THIS SPACE INTENTIONALLY BLANK            | Mail me if you have one!
	       Proudly on the bleeding edge with ESIX SVR4.0.3!
From: kskapin@csws8.ic.sunysb.edu (Keith T Skapinski)
Newsgroups: comp.os.os2.misc
Subject: Re: What does TRAP 000e mean?
Date: 24 Jul 92 17:13:43 GMT
Organization: State University of New York at Stony Brook

In article <1992Jul22.234448.6530@bronze.ucs.indiana.edu> tselling@peabody.iusb.indiana.edu (Teresa Selling) writes:
>I was happily typing along in TE/2 comm program when my system halted
>with a TRAP 0003.  What does that mean.  Perhaps I should mention
>that I've not been able to download with TE/2.  I wind up using a dos
>comm package for that.
>Thanks.
>--
>Teresa Selling, IUSB, Indiana.
>


Ah ha. I used to get that same trap every once in a while. It turned out to
be a bios problem. I updated my bios (regular bios and keyboard bios) and the
problem went away. I don't know if this is the same cause in your case. What
is your bios date and keyboard bios revision. (Keyboard revision should by F
or greater.)

By the way, why is everyone using TE/2. I tried it and went back to the
PMTerm that came with OS/2. I think its much better. More protocals, more
and better term emulation, etc. The only thing I didnt like about PMTerm
was that it was a pain to set up. Now that its set up, its great. I like
it better than any other term program for OS/2 that I've seen.

-- 
----------------------------------------------------------------
|  kskapin@ic.sunysb.edu  (Keith Skapinski)  |    place        |
|                                            |  witty quote    |
|  BEEPER / VOICE MAIL SYSTEM: 516-341-3641  |     here        |
----------------------------------------------------------------
From: hamzy@cse.fau.edu (Mark Hamzy)
Newsgroups: comp.os.os2.misc
Subject: Re: Couldn't stick it out...
Date: 28 Jul 92 23:43:49 GMT
Distribution: usa
Organization: Florida Atlantic University, Boca Raton, FL, USA

In article <mg.712256058@elan> mg@elan (Michael Golan) writes:
>roger@kean.ucs.mun.ca writes:
>
>>>       For all it's "32 bit advanced coding", just about everything I do is 
>>> slower than the equivalent operation in Windows.  
>
>I must say I tried WIN3.1 yesterday on my system, with ATI vantage, and it
>really is fast! why is os2  so slow (in comparision)?
>
>BTW, its a good idea to unfregment the OS2 partition (by booting dos).
>Pctools compress version 6.0 works, at least if you dont re-order directories
>(I didnt try it, I worry about it touching the ext.attr. bits)
>This does speed OS2 up (if you have FAT. if you have HPFS, good luck.
>it might be more freg. resistent, but it cant prevent it...) seems like
>the OS2SYS.INI file gets fregmented, and really slow things down. I had
>e.g. the 'OS2 system' folder take 8 seconds to open, compared to 2 when
>it was 'new'. Software that degrade with use, ha? :-)

UGHH ... that sends shivers down my spine.  I may be wrong but here is my
view:  On a FAT file system, the EAs are stored pretty much separately from
the file itself.  Those .EA files around your system have hard coded "pointers"
in them so moving them around is dangerous.

Correct??

BTW: I believe that the system ini files are cached.
From: olender@vivaldi.cs.colostate.edu (Kurt Olender)
Newsgroups: comp.os.os2.misc
Subject: Re: Why can't two full-screened DOS apps multitask???
Date: 30 Jul 92 18:50:59 GMT
	<1992Jul29.183031.24757@stiatl.salestech.com>
	<1992Jul30.162709.4439@midway.uchicago.edu>
Distribution: usa
Organization: Colorado State Univ. Computer Science Dept.


Timothy F. Sipples writes:

   (Ian Mercado) writes:
   >How come anytime I have a program running in a full screen window, it gets
   >suspended whenever I switch over to another full screened DOS window?
   >Windows doesn't do this, so why should OS/2??

   It should still run.  I have noticed, however, that certain
   applications won't run in the background if they use certain SuperVGA
   modes.  I'm not quite sure why this occurs -- you might want to report
   the specific circumstances to IBM using the os2prob.txt form,
   available via anonymous ftp from ftp-os2.nmsu.edu.

For once, the answer is in the documentation that comes with the OS/2 package.
Read the "Compatibility" booklet that comes in the package.  Page 7 starts the
discussion on video compatibility.  In there it explicitly states that DOS or
windows programs in the background that attempt to update the screen through a
driver that doesn't know how to virtualize the screen are suspended.  I
believe the standard VGA drivers that come with OS/2 will handle this, but
some hi-res Windows or other drivers may not.
From: bert.tyler@satalink.com (Bert Tyler)
Newsgroups: comp.os.os2.misc
Subject: Bad news for POV and OS/2
Date: 28 Jul 92 22:15:00 GMT
Reply-To: bert.tyler@satalink.com (Bert Tyler)
Organization: SataLink Info Systems - Huntingdon Valley, PA - 215-364-3324

JS>   Well, I got the final word from the POV-Team leader today.
JS>Here is what he said:

JS>  The beta test has to happen on Compuserve with CIS users. I hate to play
JS>the bad guy here, but I'm the one who gets the "Why doesn't this work?"
JS>mail. Your intentions are great, but every version that has been released
JS>outside of the CIS development circle has made its way all over the place.
JS>And it is impossible to coordinate new code changes easily unless all
JS>involved are on Compuserve.

JS>I don't know who he thinks I am, but I don't have the cash to spend on
JS>getting a compuserve account just so I can release a binary.
JS>I talked to Turgut, and I think that He'll be releasing his port anyway. :-)
JS>(his and mine are identical as it turns out, we both did the same thing)

[flame on]

Maybe he thinks he's the leader of a crew of dedicated raytracers
that have spent literally man-*years* building a freeware raytracing
package that they then give out >> with source code << for others to
enjoy.  I guess he just doesn't realize that he should also be spending
the money to give you a Compuserve account so that you're not
inconvenienced in any way by the fact that none of his team happens
to use your favorite operating system at the moment.  I guess he
doesn't realize how much he owes you for using his software.  Maybe
after you release an executable using his copyrighted source code
*after* he has expressly told you not to do so he'll realize what
fine folks you are.

Then again, maybe they'll just release later versions of POV without
source code if the first thing that happens is folks ignoring their
distribution restrictions.

[flame off]

I've seen posts from Turgut that indicate he's a reasonable person,
and wouldn't release software using someone else's copyrighted source
code after that person has expressly denied permission for him to do so.

Compuserve accounts aren't that expensive, folks.  Hopefully, they're
not as expensive as your reputation is.  The POV crew is developing
an outstanding piece of software over there, and they would love
to have an OS/2 member on their team.  I would hate to see version
1.5 of POV released without source code just because of nonsense like
the above.

                   Bert Tyler   (bert.tyler@satalink.com)
---
 . DeLuxe./386 1.25 #343sa . Your mileage may vary.  Your car may not run.
                                                  
Newsgroups: comp.os.os2.misc
From: David Boyer <boyer@soupfin.cs.indiana.edu>
Subject: Re: My theory on why OS/2 has problems...
Organization: Computer Science, Indiana University
Date: Fri, 31 Jul 1992 12:59:41 -0500

quan@Xenon.Stanford.EDU (Tony Quan) writes:

>I've been using OS/2 for almost 4 months now without a problem and
>am amazed by the variety of problems with OS/2 that people report here.
>My guess on what's going on:  a lot of the problems are caused by
>people running OS/2 on no-name clones that aren't 100% compatible.
>These machines run DOS and maybe even Windows fine, but the higher
>demands of OS/2 expose the incompatibilities.  Any comments?

I also tend to agree with you. I had a very hard time installing OS/2
(frequent crashes, slow hdisk performance fixed by os2v2oem.zip) and
experienced frequent crashes after installation. My problems did
not go away UNTIL I replaced my keyboard BIOS. Somebody on the net posted
a note from Washburn and Company about AMI BIOS problems (thank you!).

OS/2 now runs very nicely. I am starting to think that I may actually
like OS/2 better than DesqView386 :-)

Dave Boyer