SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 09 | June | 2002 ]

<< Previous Message << >> Next Message >>


Date: Sun, 9 Jun 2002 16:17:33 PST7
From: Harry Chris Motin <hmotin@attglobal.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Re: IRQ Wars, the sequel

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Writing it down longhand has got to be a pain. I've never had a problem
getting print screen to work inside my BIOS setup utility. I also have
an Award BIOS (ID N=BA: 02/20/2001-693A-686-2A6LGP8NC-00 for an AZZA
motherboard).

For me it's as simple as turning on the printer and pressing the PRINT
SCREEN key. Usually, I can do it twice for each sheet of 8.5x11 paper
and thereby get 2 different BIOS setup windows on each sheet. You can
tell when the system sends the image to the printer. On my monitor a
small speck of a discontinuity moves back and forth all over my screen,
just after hitting the PRINT SCREEN key. Then, the printer light begins
to flash. And as I say, I can do this twice before the printer has
finished a complete image and is ready to eject the paper (I have to
press a button on the printer to manually eject it).

I am really surprised that you cannot get the PRINT SCREEN to work
inside your BIOS setup utility

HCM

_________________________________________________________________________=
______________________

"J. R. Fox" wrote:
> =

> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> If you are responding to someone asking for help who
> may not be a member of this list, be sure to use the
> REPLY TO ALL feature of your email program.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> =

> Harry wrote:
> =

> > I know this won't help you right now, but it might later, judging on =
my
> > reading of your email to Tony, below. When you get your system back u=
p
> > and working correctly, take a print screen of your various BIOS
> > settings. I've done that on my system and keep it handy. When I fool
> > around with my system, trying to track down a problem and/or get bett=
er
> > performance, I can always go back to what I originally had.
> >
> > HCM
> > ________________________________________________________
> =

> Thanx.
> =

> A very good idea. I always tried to have a record of this, but never g=
ot around
> to doing it with the new iteration of this box . . . partly because th=
ings were very
> much in a state of flux anyway. I always did this the most tedious way=
, scribbling
> it out screen by screen in longhand, because I could never get Print Sc=
reen to
> work inside the Award setup program. Maybe there's some trick to that.=
Print
> Screen does work as expected, once I have some version of OS/2, or W2K =
booted up.
> =

> Jordan
> =

> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> =

> To unsubscribe from this list, send an email message
> to "steward@scoug.com". In the body of the message,
> put the command "unsubscribe scoug-help".
> =

> For problems, contact the list owner at
> "rollin@scoug.com".
> =

> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 09 | June | 2002 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.