HDTenEightyP/NetNews huggingface dataset:
From: jedwards@ms.uky.edu (Jonathan Edwards)
Subject: Re: L40SX Power Management driver problem
    <1992Sep30.91927.10502@ms.uky.edu> 
    <1992Sep30.152032.12209@jarvis.csri.toronto.edu>
Date: Wed, 30 Sep 1992 21:39:18 GMT
Organization: University Of Kentucky, Dept. of Math Sciences

byu@white.toronto.edu (Benjamin Yu) writes:

>Is this power management driver specifically for the L40SX?  Can it be
>used on another laptop?  My Samsung NoteMaster will not go into suspend
>mode under OS/2 2.0.

I expect it's specifically for the L40SX (since it comes on the L40SX
reference diskette).  What kind of processor does your NoteMaster have?
Does is suspend under DOS?
From: jreynold@nmt.edu (John Reynolds)
Newsgroups: comp.os.os2.misc
Subject: Re: Beta GRE/WinOS2 3.1 (hpfs)
Date: 25 Sep 92 16:57:42 GMT
Article-I.D.: nmt.1992Sep25.165742.8267
Organization: New Mexico Tech

Is this beta releasing coming with 32-bit hpfs drivers? If not, when
will they be ready? Is it one of the things slated for "this fall?"

-Jr



-- 
Windows...It's like a stale cookie.
OS/2..."It's like butter" (SNL quote)
Newsgroups: comp.os.os2.misc,rec.games.misc
From: db3l@ans.net (David Bolen)
Subject: Re: Attention potential Beta Testers
Date: Wed, 30 Sep 1992 14:21:44 GMT
Organization: Advanced Network & Services, Inc. - Elmsford, NY

In article <2AC9ACD5.4323@tct.com> jim@tct.com (Jim Kunzman) writes:

>Well I just spent five hours backing up my drives, doing a low-level
>format, attempting to install the beta, discovering that disk 4 of the
>distribution media is defective (apparently nothing on tracks 75-79),
>and of course restoring my original OS/2 to once again have a working
>system.  You might say I was slightly chagrined.

Hey - that's the same disk that was bad in my set.... perhaps it went
through a particular duplicator that was bad.

Things turned out ok for me though - I called IBM and although they said
it might take a week due to a backlog in the production cycle, they agreed
to send me a new disk 4.  It showed up the next day!  Way to go...

Actually - if anyone else has encountered (is encountering) this problem,
perhaps someone from IBM could check to see if putting the BUNDLE file from
disk 4 up on a server would be ok?

--
-- 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    \
\-----------------------------------------------------------------------/
Newsgroups: comp.os.os2.misc
From: masaki@leland.Stanford.EDU (Pixel)
Subject: Weird OS/2 Installation Errors...
Summary: Help!
Organization: DSG, Stanford University, CA 94305, USA
Distribution: usa 
Date: Sat, 3 Oct 92 19:44:07 GMT

  I am having difficulty installing OS/2 on my 386SX.  Booting from the
installation diskette produces the following two error messages:

OS2 !! SYS02025
OS2 !! SYS02027
  I realize that the second message means that I need to reboot the
computer, but the first message is not documented anywhere.  Any guesses
on what it means?
  Thanks in advance for any help on this matter.

Albert Huntington
masaki@leland.Stanford.edu
From: root@bhole.UUCP
Newsgroups: comp.os.os2.misc
Subject: Re: OS/2 CSD   e-mail disribution
Date: Sat, 03 Oct 92 10:17:42 EDT

Re: Re: OS/2 CSD   e-mail disribution
By: slumos #0 @unlv.edu (Steve Lumos) USEnet      
 
> Actually, the SPP ships on 10 disks. That is HARDLY the entire system
> (grin!) 
> I don't think IBM is too concerned with pirating. There was a post
> recently from somebody who had the beta release but NOT the GA
> release. It seems that they are not checking out people who call and
> order the beta. The beta version IS the full OS. 29 disks total.
> TTYL - Steve

I *have* the GA release. How do I get the new BETA?
Please respond in email & here. 

Mark
dvss!bhole!root@udel.edu

Newsgroups: comp.os.os2.misc
From: kendall@iat.holonet.net (Kendall Willets)
Subject: Re: Drive Icon View
Organization: HoloNet (BBS: 510-704-1058)
Date: Tue, 29 Sep 1992 07:23:13 GMT

imj1@cunixa.cc.columbia.edu (Imad M Jureidini) writes:
: Hi!
: 
: 	I was wondering if it was possible to get the Icon view as the default
: when I open the Drive view.  I just can't stand the Tree view.
: 
If this isn't in the FAQ, it should be:

Open the drive->settings->menu, click on ~Open, and push the Settings...
button.  Pull down the "Default Action" list and click on "Icon View". 
Push OK.  Close the settings and it should work.  If it doesn't, make sure
to explicitly choose the "Icon View" even if it appears to be there
already.  Apparently the action of choosing it ensures that it will be
recorded in the object's attributes.
From: joe2@vnet.ibm.com
Date: Tue, 6 Oct 92 14:34:34 FWT
Newsgroups: comp.os.os2.misc
Subject: Re: SVGA ON - doesn't function, beta or GA
Reply-To: <joe2@vnet.ibm.com>
Disclaimer: This posting represents the poster's views, not those of IBM
News-Software: UReply 3.0
            <unruh.718054377@physics.ubc.ca>

In <unruh.718054377@physics.ubc.ca> William Unruh writes:
>mlord@bmers63.bnr.ca (Mark Lord) writes:
>>I believe that your problem may be that the SVGA support under OS/2 2.0 does
>>*not* include support for the Trident 8800 chipset.  It does, however, include
>>support for the 8900/9000 chipsets.  A new Trident 9000 card with 512KB runs
>>for about C$60 these days, and is *fully* supported under OS/2 using the
>>drivers from Hobbes.
>
>What OS2 needs is to allow users to install a SVGADATA.PMI file  and
>then BVHSVGA believes and uses that file. As it is it checks to see if
>it recognises the video card, and uses the .PMI data ONLY if that agrees
>with what BVHSVGA  thinks the video card is. This means that if in the
>future someone comes out with a new chip not currently recognised by
>OS2, you're out of luck, without IBM releasing a version of OS2 which
>specifically recognises that card. That's stupid, unmodular design.
>There should be a defined interface with OS2 (BVHSVGA) which any card
>manufacturer can hook to by obeying those interface restrictions and
>writing and appropriate driver. If I misunderstand the OS2 SVGA design,
>please correct me.
>Bill Urnuh
>unruh@physics.ubc.ca
>
>
   This is not quite correct Bill... :-) They have tried to achieve
some kind of device-independance with the .PMI file. But this is not
always possible. Video registers  are such a mess... I'm afraid
that BVHSVGA will always have to know about your video chip
(for instance the .PMI file does not specify how to switch between
video banks, which is vendor-specific).
   What is wrong with the current BVHSVGA design, is that it is
asking OEMHLP$ for the video adapter type and chip version,
instead of just using the .PMI file. And sometimes SVGA.EXE
and OEMHLP$ do not agree about the adapter type!!! (OEMHLP$ is
buggy).
    I am trying to get this bug fixed, but this is a tough job,
especially from France :-(

-Joel Armengaud
Newsgroups: comp.os.os2.misc
Subject: help! I have a G-HOSTS3 video card, what to do!
From: jammin@hogbbs.scol.pa.us (Ben Barrett)
Date: Mon, 28 Sep 92 21:24:47 EDT
Organization: The Heart of Gold BBS, Lemont PA

I have a 486-33 8 ram 200 hd, etc, with sb pro
ok so all that is irrelevant.
anyway, i have this G-HOSTS3 S3 acc. video card, capable of 1024x768x256.
will someone please explain this 32-bit GRE thingy.
will i be able to have 1024x768x256???
it would love it.
although no one has heard of my video card.
there's gotta be someone somewhere who can help me
so PLEASE do.
soon!
i'm anxious, and wanna know what i'll be able to gain from upgrades, etc.
                                        jammin@hogbbs.scol.pa.us
                                                Ben Barrett
lookin forward to your replies.
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Newsgroups: comp.os.os2.misc
Subject: Re: New Trident 800x600x256 seamless drivers released ??
Date: 30 Sep 92 00:34:22 GMT
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago

In article <1992Sep28.073852.12768@news.tu-graz.ac.at> tom@piassun1.joanneum.ac.at (Tom Leitner) writes:
>I have heard that Trident has released a new set of their OS/2 2.0 drivers
>for their 8900C,9000 card series. Especially a 800x600x256 seamless driver
>is said to be released lately. Can anyone confirm this ? Being in Europe
>I just can't  affort to check the Trident BBS myself. Could someone check
>that on the Trident BBS and (if positive) possibly upload the drivers
>to ftp-os2.nmsu.edu?
>I'd appreciate that very much. Thanks in advance and regards from Austria.

No such new drivers on the Trident BBS -- sorry.

Perhaps the forthcoming Service Pak contains those drivers.  We'll
see.

-- 
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
Newsgroups: comp.os.os2.misc
From: unruh@physics.ubc.ca (William Unruh)
Subject: Re: SVGA ON - doesn't function, beta or GA
Keywords: SVGA, beta
Organization: University of British Columbia, Vancouver, B.C., Canada
Date: Fri, 2 Oct 1992 00:49:48 GMT

dd435157@longs.LANCE.ColoState.Edu (Dan Doner) writes:

>The problem:  SVGA ON does nothing (from full screen dos window, of course)

>Sometimes SVGA ON generates a .pmi file from a dos window, but we all know this file will contain
>garbage (it says I have a Tseng 4000 - I dont).

As I understand it, SVGA has software to try to figure out what kind of
card
is attached to the system. If there are (slight) differences in your
card, it may not recognise that card. To make it worse, after SVGA has
generated the .pmi file, bvhsvga partially(?) ignores it and goes to
another internal program OEMHLP and tries to determine the card again.
It uses both this new information and the stuff in .pmi to do it's
stuff. The detection software in SVGA and in OEMHLP is different so
cards one will recognise may not be recognised at all, or as a different
type by the other. In that case BVHSVGA refuses to do its job and/or
crashes if asked to switch modes. To make things worse, bvhvga, the
straight VGA driver also has bugs, and sometimes doesn't switch back to
VGA properly. Will the CSD fix these things? I guess hope is a virtue
and I will try to be virtuous.
Bill Unruh
unruh@physics.ubc.ca
{If any more knowledgeable people see errors in the above please correct
me]
Newsgroups: comp.os.os2.misc
From: reimert@mamacass.etdesg.trw.com (Scott P. Reimert)
Subject: Re: OS2 HPFS
Organization: TRW Inc., Redondo Beach, CA
Date: Sat, 3 Oct 92 01:26:39 GMT

In article <1992Oct1.043722.3393@nmt.edu> mystical@nmt.edu (Gurupartap Davis) writes:
>
>
>I just got a new 486sx system and I've installed OS/2 in dual boot mode.
>I was wondering about the possible benefits of using the hpfs mode, though.
>Maybe I could partition the disk (eg. 80 megs DOS FAT, 120 Megs HPFS) or

	You're mixing apples and oranges here. HPFS isn't a mode like that
	of Dual Boot. It's an installable file system, used instead of the
	FAT style. For loading modes, you have Boot Manager, Dual Boot or
	just starting OS/2 as the solitary OS for the system. 

>even just format the entire disk.  would I still be able to boot from a 
>floppy if my system hangs?

    Yes, since the above is true, you can still boot from a floppy.

>If anybody has any experience using the hpfs
>or knows anything about it, I would appreciate some information.
>Are the two systems compatible at all?  If I had the disk partitioned would
>either system be able to access the other?  Maybe just OS/2 could access
>the DOS partition?  *MAYBE* the dos partition could read text files created
>on the OS/2 partition (eg. to fix a crappy OS/2 config.sys file that keeps
>it crashing before I can get to the desktop to fix whatever was wrong in the
>first place????)
>Hmmm.  Maybe I actually stayed on the subject after that ramble...wow.
>Anyway, I'd like some help and guidence from anybody...please?
>
>btw, please email responses, I tend to forget to read news :)
>Partap
>mystical@jupiter.nmt.edu
>
>
The two systems are compatable, but you can only have a single drive C
active at any time. DOS files on any drives other that drive C will be
"seen" and accessable by OS/2. 


-- 
-------------------------------------------------------------------------------
  Scott Reimert  \    reimert@mamacass.etdesg.trw.com     /Standard disclaimer:
Redondo Beach, CA \______________________________________/"Blah blah blah ... "
__________________|Always store beer in a cool dark place|_____________________
Newsgroups: comp.os.os2.misc
From: sam@ms.uky.edu (Mike Mills)
Subject: Sony CDU541
Date: Mon, 5 Oct 1992 17:25:46 GMT
Organization: University Of Kentucky, Dept. of Math Sciences

I'm considering purchasing a Sony CDU541 for use under both OS/2 and windows.
Does anyone have any opinions of this drive?  I THINK (but I'm not sure) that
it comes with a scsi controller that is supported by OS/2...can anyone
confirm this?

Also, if anyone has any alternate suggestions, please let me know.  I'm 
looking for a drive that meets MPC standards, and will work under OS/2 and
Windows.  I would really like to have the double-speed NEC CDR 84, but I
can't really afford both it AND the Adaptec SCSI controller to go with it.
I'm looking to get away with about $400 including controller.

Thanks.


-- 
--Mike Mills              E-Mail:  sam@ms.uky.edu, {rutgers, uunet}!ukma!sam
--UK Math Sciences Dept.                  mike@ukpr.uky.edu    
--(606) 257-1429 (work) 263-0721 (home)
Newsgroups: comp.os.os2.misc
From: hoppie@kub.nl (Jeroen Hoppenbrouwers)
Subject: Re: Turn Help Off?
Date: Tue, 29 Sep 92 14:25:50 GMT
Organization: Tilburg University, Tilburg, The Netherlands

In article <1992Sep29.120934.18742@ra.msstate.edu> wjw1@me1.MsState.Edu (Bill Wilson) writes:
>In article <1992Sep29.041820.7181@cybernet.cse.fau.edu> azzarito@cse.fau.edu (Doug Azzarito) writes:
>>In article <1992Sep28.135943.6934@persoft.com> johnf@persoft.com (John Freeborg) writes:
>>>
>>>(1) How do you turn off BY DEFAULT the annoying little help line at
>>>    the top of the screen of OS/2 or DOS sessions when you are sitting
>>>    at the prompt?
>>
>>For OS/2 screens, edit CONFIG.SYS, and change your PROMPT.  The $i adds the
>>help line.  For DOS screens, edit your AUTOEXEC.BAT and take out the HELP ON.
>>
>>>(2) Some of the icons on my desktop have title text in light grey.
>>
>>Yep, they're shadows, and you can't change the icon text color.  Sorry!
>
>Ummmm.... not quite right on answer (2) here. You can define the icon text
>colors (for shadows and regular objects) in the scheme palette. The scheme
>palette lets you control the colors and fonts for just about everything.
>
>__
>Bill Wilson : MSU Nuclear Engineering
>"My brain is full now... may I be excused?"
>

I tried this and was unsuccessful. But the SYSCOLS program did it
without
hassle. Highly recommended!


Jeroen


-- 
Jeroen Hoppenbrouwers, research engineer at     |  Stop connecting computers;
Tilburg University, The Netherlands             |  start connecting people!
Newsgroups: comp.os.os2.misc
From: peter@tardis.trl.OZ.AU (Peter K. Campbell)
Subject: Re: SVGA ON - doesn't function, beta or GA
Keywords: SVGA, beta
Organization: Telecom Research Labs, Melbourne, Australia
Date: Wed, 7 Oct 1992 03:24:59 GMT

dd435157@longs.LANCE.ColoState.Edu (Dan Doner) writes:

>I have tried just about every suggestion I have been able to find in hints/tips, the FAQ and 
>various other info docs from hobbes (ftp-os2) relating to this problem, so I have done my homework.

>The problem:  SVGA ON does nothing (from full screen dos window, of course)

>Sometimes SVGA ON generates a .pmi file from a dos window, but we all know this file will contain
>garbage (it says I have a Tseng 4000 - I dont).

>Hardware:  Logix SVGA w/ 512k RAM (trident 8800 I believe), 25DX, 8 meg RAM and so on.

I had exactly the same problem, and I even managed to stump the OZ OS/2
support guy (although he tried hard).  However, after various delving and
a few helpful people I found out that the problem is the 8800 chip set.

For no apparent reason the trident drivers and SVGA program only support
the 8900 and newer trident chipsets, and refuse to have anything to do
with the 8800s at all.

In fact, when I tried "svga on" or "svga status" with the trident it just
came back with the useless usage message, which is what really p-ed me
off - it is very annoying to type "svga on" and basically be told to
type "svga on" as an error message.

If it had of come back and said something like "sorry, unsupported chip
set", then I wouldn't have wasted several days trying every trident
driver and graphic fix that I could find.

So, I found that you cannot install any SVGA drivers in OS/2 for the
8800 cards - not in the desktop, and not in WINOS2 either.  From my
questioning there appears that there never will be drivers written
either, at least not by Trident or IBM.

Unfortunately the only suggestion I have is to flog off your card to
a non-OS/2 user, and to buy a new card, like I did.  Plus seeing as
none of the fancy stuff for decent cards has any real support in OS/2
yet (e.g. no 24 bit, fast S3 cards don't work), I suggest buying a
cheap good quality card like the Tseng 4000 or the newer Tridents
until IBM and the board manufacturers get their act together.

BTW, has anyone 256 colour drivers for Tseng cards yet?  I can only
find 16-colour about the place.

Peter K. Campbell
p.campbell@trl.oz.au
#include std.disclaimer
Newsgroups: comp.os.os2.misc
From: jwh@citi.umich.edu (Jim Howe)
Subject: Re: L40SX Power Management driver problem
Date: Wed, 30 Sep 92 11:05:00 EDT
Organization: IFS Project, University of Michigan
Reply-To: jwh@citi.umich.edu

In article <1992Sep30.91927.10502@ms.uky.edu>, jedwards@ms.uky.edu (Jonathan Edwards) writes:
|> This probably won't help, but it couldn't hurt (I've posted your problem
|> to the internal IBM conferencing facility.  With any luck someone who
|> knows more about the situation will be able to help...).
|> 
|> I haven't sprung for the additional memory needed to run OS/2 2.0 yet,
|> but someone who has wrote the following:
|> 
|>  To get Suspend/Resume to work while running OS/2 2.0 I did the
|> following:
|>  
|> Note: I have OS/2 2.0 installed on the D: partition of my hard disk.
|>  
|> 1. Copied the file PWRMGMT.SYS from the 1.03 reference diskette to the
|>    D:\ root directory.
|> 2. Edited CONFIG.SYS and added the line "DEVICE=D:\PWRMGMT.SYS"'.
|> 3. Copied the file IDLE.EXE from the 1.03 reference diskette to the
|>    D:\ root directory.
|> 4. Created a STARTUP.CMD in the D:\ root directory with the following:
|>  
|>     Detach D:\IDLE.EXE
|>     Exit
|>  
|> 5. Reboot OS/2 2.0
|>  

This doesn't pertain to OS/2 so much as it does the L40, but can
someone tell me if it is possible to get information about how
to interface to the L40 power management system?  We're working
with some software that needs to be able to communicate
with the L40 power manager.  Thanks.


James W. Howe                  internet: jwh@citi.umich.edu
University of Michigan             uucp: uunet!mailrus!citi.umich.edu!jwh
Ann Arbor, MI   48103-4943         

Newsgroups: comp.os.os2.misc,comp.os.os2.advocacy
From: jedwards@ms.uky.edu (Jonathan Edwards)
Subject: Re: What is thunking?
Keywords: thunking
Organization: University Of Kentucky, Dept. of Math Sciences
Date: Sat, 26 Sep 1992 12:58:32 GMT

gonzaled@ucsu.Colorado.EDU (LGV/MC) writes:

>I've heard this term, "thunking," used at least a couple of times in the
>OS/2 newsgroups and would like to see a detailed explanation of what exactly
>thunking is/does.
>Plus, I'm curious if it's a bad or smart way to do whatever it does.

>So, essentially, what is thunking and does it have merits?

OS/2 2.0 supports both 16-bit and 32-bit code.  The problem that thunking
solves is allowing 32-bit programs to invoke 16-bit routines.

The Intel x86 architecture is segmented.  A segment is referenced via a 
selector.  In the 16-bit universe, a segment can be no larger than 64K.
That limit was increased to 4G when the 386 came along.

OS/2 2.0 uses a single selector to map the flat address space a 32-bit
module sees.  (This is an oversimplification but the things it ignores
are not important from the thunking point of view.)  OS/2 2.0 also maps
the segmented address space a 16-bit module sees on top of the flat
address by breaking the flat addess space into distinct 64K blocks and
assigning a single selector to each block.  (There are 8K selectors
available for this purpose, which is why the application address space
under OS/2 2.0 is limited to 512M rather than 4G...)

Since the 16-bit and 32-bit address spaces map the same set of virtual
(linear) addresses, 16-bit code and 32-bit code can share information.
To do so, however, something must ensure that any 32-bit pointers the
32-bit code passes to a 16-bit routine are translated to the equivalent
16-bit segmented pointers along the way.  The code that takes care of
this is called a thunk.  (The thunk must also handle a number of other
related tasks made necessary by the x86 architecture, such as changing
all the segment registers to hold 16-bit selectors rather than 32-bit
selectors.)  

This scheme imposes additional constraints that a thunk cannot solve.
For instance, 32-bit code must ensure that any variable it passes to
16-bit code does not cross a 64K boundary.  (The 16-bit code is  
probably not expecting to receive an argument that spans segments.)

Thunking is not pretty and it's unfortunate that it's required.  The
alternative would have been to disallow most 32-bit-to-16-bit interaction.
This might have been reasonable had 32-bit versions of everything been
available immediately.  Given that that's not the case (and probably
couldn't have been), thunking is a reasonable burden (especially since
most of the work can be done by the compiler if you tell it what
you're going to do).