Mega Top 1/os2_top1.zip/os2_top1/INFO/DIVSINFO/FORUM/OS2INST.INF

OS/2 Help File | 1994-05-10 | 427KB | 9,847 lines

ΓòÉΓòÉΓòÉ 1. About this forum ΓòÉΓòÉΓòÉ

     TALKLINK

     Welcome to the world of TalkLink, a unique, new conferencing
     service  offered  by  IBM. Using TalkLink, you can "talk" to
     customers, IBMers  and  personnel  of  our  many  affiliates
     around  the world - anywhere, anytime.  TalkLink is designed
     for people like yourself, who want to get the  most  out  of
     their  investment  in  computing  products  and  services.
     TalkLink "links" you directly into the development and  sup-
     port  communities of customers, IBM and affiliates. Our goal
     is to help you be as effective as you  can  with  access  to
     many conferences, vast databases and rich libraries.

     HIGHLIGHTS

     TalkLink  provides  the following capabilities for customers
     to review information electronically, submit questions  re-
     quests and receive answers  information.
     -  Conferences and forums -- question and  answer  bulletin
       boards  for  you to ask questions and help others with a
       wide variety of products and services.  Items posted  on
       this  bulletin  board  are shared between BBS users, IBM
       personnel and affiliates worldwide.
     -  Customer-to-customer messaging  --  customers  can  send
       private messages to each other.
     -  Support   --  customers  can submit or view problem re-
       ports.  These entries  will  be  responded  to  by  the
       conference/forum  owner,  normally within a certain time
       period. Users can also place orders for product  related
       materials.
     -  Software  library  -- downloads application programs and
       uploads contributions.
     -  News and announcements --  contains  recent  information
       regarding products and services.
     -  Modes of operation:
       -  Interactive  -- Users  are  connected  online  to
         TalkLink while using its facilities.
       -  Batch  -- Users can download  the  forums  to  their
         personal  computer  and  read the entries  offline.
         Users can also respond offline and the entries  will
         be saved and sent to the host the next time the user
         is  connected in batch mode.  Initially, this facil-
         ity is available for  OS/2  (R)  users only.
     -  Access:
                                   1
       -  Advantis -- local call from most cities  within  the
         US.
       -  Internet -- telnet avaialable now, full ftp soon.

     SEARCH SERVICE

     -  Search IBM databases via interactive mode -- This search
       facility  includes  a large question and answer database
       of items, IBM System  Center  Flashes,  and IBM's  prob-
       lem  management libraries. This database contains infor-
       mation  about  problems  and  fixes.  Not  all  general
       discussion  forums have related information in these da-
       tabases.

     TALKLINK FEES  CHARGES

     -  $15.00  Registration  Fee (one-time charge for each user
       registration)
     -  $18.00 Monthly Availability Charge  (includes  unlimited
       hourly service)
     -  This can be charged to a credit card or invoiced (for an
       additional  administrative fee of $7.00 for each monthly
       invoice).

     HOW TO ORDER TALKLINK

     Call 1-800-547-1283 to sign up for TalkLink.
     Outside of the United States please contact your
     local IBM sales office for availability and access.
**********************************************************************


ΓòÉΓòÉΓòÉ 2. Introduction ΓòÉΓòÉΓòÉ

===== OS2INST CFORUM created at 01:47:09 on 92/04/08 GMT (by HOPKINS at AUSVM8)
              IBM UNCLASSIFIED
              ------------
The information in this forum is considered by IBM to be
   external and may be shared by everyone who is given access.
   This forum is shared with the internal IBM employee conferences.

Forum: OS2INST CFORUM

Forum subject: OS/2 Base Operating System Installation

This FORUM is provided as a conferencing tool to promote
      discussion of OS/2 Base Operating System Installation
      and Customization, and present any issues, questions or
      problems related to OS/2 Installation.

Contributions must not contain confidential or proprietary information.

Each contributor agrees, in placing material in this forum, that IBM and
other users are free to prepare derivative works based upon it, and to use,
reproduce, perform, display and distribute inside and outside their company
such material and such derivative works, without obligation or charge.

IBM is not responsible or liable for the use, copying, or distribution of
materials placed on this forum, and has therefore no obligation to control
such acts.

All subscribers are required to abide at all times by the conference
rules described in the Bulletin Board Rules under "News and Announcements".

All IBM personnel are required to abide at all times by the IBMPC RULES
and the IBM Business Conduct Guidelines. IBM personnel will read the
CUSTOMER FORUM RULES in IBMPC RULES before contributing.

Contributions violating these rules will be deleted by the CFORUM
Owner or their delegate, and in some cases by an IBM conference
Administrator.

The OS2BBS CFORUM is where anyone may raise concerns regarding rules
violations found in this and other CFORUMS.

The IBM Administrator of this forum is:
  Name:       Paul Cheatham
  Mailing Address: Boca Electronic Support Team ( BEST )
          1000 N.W. 51st Street
          Internal Zip 1426-012/W2030
          Boca Raton,  FL  33429
  IBM Node/Userid: BCRVM1/CHEATHAM
  TalkLink Userid: LNK9/LNK9030

See OS2INST  932CFORU on OS2BBS  for appends to 93/01/11 (4514 lines)
 See OS2INST  933CFORU on OS2BBS  for appends to 93/03/22 (4519 lines)
 See OS2INST  934CFORU on OS2BBS  for appends to 93/05/24 (4743 lines)
 See OS2INST  935CFORU on OS2BBS  for appends to 93/06/27 (4706 lines)
 See OS2INST  936CFORU on OS2BBS  for appends to 93/07/19 (4653 lines)
 See OS2INST  937CFORU on OS2BBS  for appends to 93/09/11 (4517 lines)
 See OS2INST  941CFORU on OS2BBS  for appends to 93/11/15 (4475 lines)
..... 4475 lines pruned at 15:22:15 on 93/11/15 GMT (by OS2 at YKTVMV) .....

**********************************************************************


ΓòÉΓòÉΓòÉ 3. How do I start a partial install? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

If your installation procedure stops before completion, you might be
able to complete the installation without reusing all the installation
diskettes.  You do no hve to use all diskettes again if the install
stopped after you were prompted to put the Installation Diskette in
the drive the second time ( after you are in the graphical installation)
For example , if you were copying files from Diskette 9 on a 3.5 inch
diskette system you could resume the installation at diskette 9 after
doing the following:

1) identify which diskette was being unpacked when the install stopped

2) subtract the number of that diskette from the number of installation
diskettes and add one to the number.

3) Start the computer with the Installation Diskette and then insert
Diskette 1 when prompted.

4) When you are asked to press Esc to cancel, press Esc. You will see
a command prompt.

5) Use a text editor to edit the Config.Sys file on the hard drive.

6) In the line that starts with FIRSTDISK, change the number to the
number of the diskette that was in the diskette drive when the
  installation procedure stopped.  In the example, this is 9

  FIRSTDISK = 9

7) In the line that starts with NUMDISKS, change the number to the
  number of disks that you computed as remaining.

8) Remove the diskette and press CAD. You will see the graphical
  install panel, Select OK, then Install, and select all defaults.

9) When you are prompted, insert the diskette named in the prompt.
  In the example, this would be 9 - the diskette being unpacked
  when the install stopped.

10) At the Selective Install choices that you selected when you first
  tried to install are preserved.

Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************


ΓòÉΓòÉΓòÉ 4. Invalid Windows Config File ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I've had the same problem with PC/DOS 5.0.  What can we change in win.ini file
to make it acceptable?

Victor M. Yellen,  University of Florida
**********************************************************************

A friend called me asking me why OS/2 2.1 (full version) is complaining
about his WIN.INI when it worked perfectly well with Windows 3.1.
What is the answer to the previous append? I don't see it anywhere
in this FORUM. Thanks!

Kirk Davis
**********************************************************************


ΓòÉΓòÉΓòÉ 5. Installation problems with OS/2 for Windows ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have a problem where I deleted my printers from desktop and then attempted to
 reunstall from CDROM.  The PPDS 4029 goes OK but on attempting to install
Postscript I get message..."The files associated with this printer could not be
 unpacked."  From a CDROM not diskettes.  Please Help.

Victor M. Yellen,  University of Florida
**********************************************************************

What directory are you in when attempting to unpack.  Find the directory
se21\pmdd_1  or 2  or 3  directory having the files you need and try
again.  You may try calling 800 992 4777 for more of a hand held
support if you still have problems.

Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************

[Reference to append at 18:40 on 93/11/15 by AAEP0WB at OS2CUST ]

I have seent this problem before and as I recall I had to use the
ALT+F1 (or CTRL+ALT+F1) during reboot (you hold these keys down during
the rebooting) to rebuild the desktop and stop it. I thought that was
the same as deleting the INI files and running MAKEINI.

Alan Arnett, Fina Oil & Chemical, Dallas, TX, [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 6. Missing \OS2LDR following disk failure ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

FYI, OS2LDR has no extended attributes.  It does have SHR.  Those can be
changed to fit the needs of whatever "copy" you choose to use.

Jim Stuyck - J.D. Stuyck & Associates - Member, I.V. League - [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 7. Installing OS/2 2.1 from CD. ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have a friend who has clone currently running MSdos 5.0 and Windows 3.1
and would like to install 2.1 (dual boot) from the CD he has. The set-up
is a 486dx 33Mhz 16Mb RAM, 450Mb, Sound Blaster Pro, Panasonic 562 CD-ROM
The problem is there isn't a driver for this CD/interface combination on
the CD. Where do I get the appropriate drivers to allow this guy to
create the two boot disks that are needed???

Regards Ralph Buckley          Operations Bridge Project Support

BUCKLR at CROVM4 / GBIBMZGZ at IBMMAIL      Systems Service Delivery
[e-mail]                PO BOX 41, North Harbour
                         PORTSMOUTH, Hampshire
Int:(7)255504 / Ext:[phone]         UK, PO6 3AU.
**********************************************************************

Sound Blaster released a driver for their Panasonic drives, so if the Panasonic
CD-ROM is connected to the Sound Blaster, then this driver may work for you.
It is on the Internet, at FTP site FTP.CDROM.COM.

Mike Long - ISU/CARD - [e-mail] - TEAMOS2 - OS/2 Accredited
**********************************************************************


ΓòÉΓòÉΓòÉ 8. OS/2 For Windows - Uninstall ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We're going to begin installing the OS/2 for Windows 3.1 Special Edition
on a few of our windows workstations.  Recently a PC Week article did a
review of the product and "mentioned" that it would be difficult to
de-install the product if we wanted to.

We were planning on using dual boot initially.  What considerations would
we have if we needed to remove OS/2 from the PC in that environment?

Thanks in advance
Roman

Roman Dumiak - Allstate Insurance
**********************************************************************


ΓòÉΓòÉΓòÉ 9. Diamond Speedstar Pro LBV Card ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I convinced a friend to install OS/2 at home on his 486 DX2 clone
and he really likes it other than the video speed.  Under windows he
feels the video response is faster.  He has installed OS/2 using
the out of the box SVGA drivers.  His card is (as the title says)
Diamond Speedstar Pro LBV with a Cirrus CL-GD5426 graphics Co-processor
(LBV=Local Bus Video).  The SVGA driver in 2.1 lists cirrus 5422 &5424,
saying that these can be run in 800x600x256 & 1024x768x256.  How is this
selected???  If I open System Setup => System there is no first page of
resolutions.  Could this be a problem with the monitor??

Is there a newer driver available for this card?  How does he change
resolutions if there isn't. He would like to run it in 800x600 but
I can't find what it is currently running at or how to change it.

If there is a new driver available where can I download it from
(Please POST BBS Number!), what it is called, how do you install etc.

Gareth "I have a convert!" Jones
ISM - Information Systems Management Regina Sk Can.
[phone] TeamOS/2, OS/2 Ambassador & Generally Nice Guy
**********************************************************************


ΓòÉΓòÉΓòÉ 10. OS/2 SYS 2025 and 2027 error immediately ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I was testing OS/2 installation on an evaluation system and got the same
errors when I tried to boot up my utility diskettes to check the
harddrive partitioning before starting the install.  The weird thing was
that these same diskettes boot fine on other systems.  The disk0 of my
CID diskettes worked fine so I was able to use it to get my utilities
diskettes booted.  IBMLINK shows these errors can occur on
some sensitive diskette drives. If the diskettes work on another system,
I would try a diskcopy to another diskette and see if the replacement
diskette works.

Alan Arnett, Fina Oil & Chemical, Dallas, TX, [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 11. WordPerfect and CID (and IBM4019) ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

WordPerfect for OS/2 requires a parm add to the OS2 ini files, so that the
MIRRORS.DLL ( Windows Micro Kern. emulator and translater) can run.  These
change may be pre-add if you image the desktop and then install that image on
all machine.  Ask IBM on hoe to install a standard Desktop on all machines.

John E Quigley II  Standard Register Corp  -- IS -- [phone]
**********************************************************************

Welcome to the real world of CID installing.  Not everything is
perfect but just about.  We've been CID'ing for about six months now.
 The way we handled WP5.2 was to install it on a clean OS/2 machine
and see what it did. It created two directories (WPOS2 and WPCOS2).
It copied two files to the \OS2\DLL directory.  One file can be
copied from WPOS2 and renamed from MIRRORS._LL to MIRRORS.DLL.  The
other file SYSFONT.DLL can be copied from the WPCOS2 directory.  It
added the WPCOS2 directory to the LIBPATH and added

WPOS2 to the PATH in the config.sys.  One other problem we found
while trying to install WPOS2 was that cid installed machines that
are XGA need to have *.XGA and *.BGA in the \OS2\DLL directory
renamed to *.FON .  It also does not run the 64K color palette very
well either.  If you use PKZIP to zip up the WP directories and UNZIP
them as an install command I think you will have good results.

As far as the 4019 goes, well we're all having problems CID
installing printers.  Especially if they are not on the printer
driver diskettes that ship with OS/2.  We tried using the RINSTPRN
utility from the red book GG24-3780 but could not get it to work and
have not been able to get any help for that is not a supported
program. We have it installing the drivers and creating the icons but
it does the same thing as yours.  If you open up the JOB PROPERTIES
in the icon's setting before you do anything else (dont do anything
just open and select ok) it works fine. We just added that step to
our sign-off testing of the PWS.  If you hear of a way to remote
install printers and drivers please let me know. I guess we're the
only ones trying to do this because I have put this same question up
a few times already on this forum and nobody has answered it yet.

Good Luck,

Chuck Thomas Sunburst Bank Grenada MS
**********************************************************************

[Reference to append at 18:57 on 93/11/16 by SREG007 at OS2CUST ]

Welcome to the real world of CID installing.  Not everything is
perfect but just about.  We've been CID'ing for about six months now.
 The way we handled WP5.2 was to install it on a clean OS/2 machine
and see what it did. It created two directories (WPOS2 and WPCOS2).
It copied two files to the \OS2\DLL directory.  One file can be
copied from WPOS2 and renamed from MIRRORS._LL to MIRRORS.DLL.  The
other file SYSFONT.DLL can be copied from the WPCOS2 directory.  It
added the WPCOS2 directory to the LIBPATH and added

WPOS2 to the PATH in the config.sys.  One other problem we found
while trying to install WPOS2 was that cid installed machines that
are XGA need to have *.XGA and *.BGA in the \OS2\DLL directory
renamed to *.FON .  It also does not run the 64K color palette very
well either.  If you use PKZIP to zip up the WP directories and UNZIP
them as an install command I think you will have good results.

As far as the 4019 goes, well we're all having problems CID
installing printers.  Especially if they are not on the printer
driver diskettes that ship with OS/2.  We tried using the RINSTPRN
utility from the red book GG24-3780 but could not get it to work and
have not been able to get any help for that is not a supported
program. We have it installing the drivers and creating the icons but
it does the same thing as yours.  If you open up the JOB PROPERTIES
in the icon's setting before you do anything else (dont do anything
just open and select ok) it works fine. We just added that step to
our sign-off testing of the PWS.  If you hear of a way to remote
install printers and drivers please let me know. I guess we're the
only ones trying to do this because I have put this same question up
a few times already on this forum and nobody has answered it yet.

Good Luck,

Chuck Thomas Sunburst Bank Grenada MS
**********************************************************************


ΓòÉΓòÉΓòÉ 12. How I can see in the OS2*.INI ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

It would be sometimens very usefull to see whwt is in the
OS2SYS.INI and OS2.ini - files.

Do you know any progran which can open these files so that you
read them as easily as WINDOWS INI-files ???

I have seen OS2.INI-file witch size was about 7 Mb.
It would be nice to know what it includes |

Timo Ketola
OY Tietokonepalvelu Ab
Finland

This append was created on the External IBMLink system by
Oy Tietokonepalvelu
**********************************************************************

Timo,

The 7MB .INI file you saw is a "problem" that is corrected by both OS/2 2.1
and the second ServicePak for OS/2 2.0.  I suggest you upgrade.

There are several programs that view OS2.INI and OS2SYS.INI -- and allow you
to edit them -- that you can get.  The one I use is "INIMAINT" from Carry
Associates, 990 Ironwood Court, Marco Island, Florida, 33937, USA.  Telephone
is (813)-642-9126.  I got it from the diskette that comes with "OS/2 2.1
Unleashed" by Moskowitz and Kerr.  It's unregistered.

Also, I "think" there is an "ini editor" available as "Employee Written
Software," but I'm not sure of that.  If it's the one I used before INIMAINT,
it was adequate but had much less function.

Jim Stuyck - J.D. Stuyck & Associates - Member, I.V. League - [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 13. OS/2 for Windows: Install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

This was posted on the PCCBBS over night and I was asked to repost to this
board,  I have posted it here and in OS2MISC.  It contains some very valid
points and concerns.
========================================
Jack,

Please post this to the OS/2 BBS quickly. Thanks.

I have a friend that just bought and installed OS/2 for Windows. It
has the shut down bug. It also has a major conceptual problem. He
wanted to use the HPFS, a reasonable thing to do, so, Gee Whiz, when
he was prompted to reformat his drive to install HPFS, he did! You
guessed it. That meant that when the install was done, all he had was
OS/2 and DOS support. Since Windows went down the bit drain with the
reformat, along with all of his programs and data, he was a wee bit
perturbed (an understatement). (He has a backup so is ONLY upset, not
irate).

THE INSTALL PROCEDURE FOR OS/2 FOR WINDOWS ONLY WORKS PROPERLY IF YOU
STAY WITH A FAT FILE SYSTEM!!!!!
DO NOT SELECT THE REFORMAT OPTION !!!!!

He had to reformat his drive back to FAT, reinstall DOS and WIndows
and then install OS/2-f/W (like my new acronym?) on top of that in
order to create a true complete OS/2 2.1 albiet on a FAT drive. He
then XCOPIED everything to a different drive followed by doing another
reformat and OS/2-f/W install for HPFS. After xcopying the previously
correctly installed OS/2 back to his HPFS drive he finally had
OS/2-f/W with Win-OS/2 support on an HPFS drive.

IBM could not help him with this. He said they tried real hard but
nobody knew what to tell him and could only read from a sheet of
(useless) suggestions. Aparantly none of the IBM help line people had
had any preparatory contact with this process AT ALL!

IBM needs to set up a PC lab with DOS/Windows installed and turn a
bunch of semi-literates as well as serious True Hackers, loose with
OS/2-f/W and document the results, NOW. If they don't have a good
answer for this quickly they are going to have big problems!

He also made one other good point. Since IBM is marketing this as
"OS/2 for Windows", it should install like a Windows program! That
means: put your disk in drive A:, double click on the File menu in
Program Manager and "RUN" the install. There is no reason why this
could not be made to work other than it is too late now! Who the _ell
is in charge in Boca? Don't they make any effort to know how "normal"
people operate. If I hadn't stepped in IBM would have gotten a CD
shoved up their ___  by a guy who has spent a bundle on PCs and
software for the past 10 years, is quite intelligent, and far from
semi-literate.

The good side of this is he loves how OS/2 runs his software now. He
says, "AMI-Pro runs a lot better seamless under OS/2 than it ever ran
on this same system with Windows!"  A place he nearly never got to
because of the install mess.

Tom Garson
Ashland, Or.

---
 ╨╖ KWQ/2 1.2d NR ╨╖ "640K ought to be enough for anybody." - Bill Gates
1

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

Jack Hiatt
Team OS/2
The International Phoenix Alliance
**********************************************************************

An excellent cross-post Jack...
tg>IBM needs to set up a PC lab with DOS/Windows installed and turn a
tg>bunch of semi-literates as well as serious True Hackers, loose with
tg>OS/2-f/W and document the results, NOW. If they don't have a good
tg>answer for this quickly they are going to have big problems!
 There is a tale that some of the original AS/400 releases were tested
by giving the install package to the secretary. And then taking notes
on what she had problems with. The VSE install process looks like it
could also have been tested out this way, I wouldn't know, but I
wouldn't be surprised.

tg>He also made one other good point. Since IBM is marketing this as
tg>"OS/2 for Windows", it should install like a Windows program! That
tg>means: put your disk in drive A:, double click on the File menu in
tg>Program Manager and "RUN" the install. There is no reason why this
 I don't see any reason why not either. Since all that is required is
to boot the first disk, they could just put a file called INSTALL.BAT on
the first disk which executed a boot utility.

->Rich Corbett; Mgr. Sys.; ABC Liquors, Inc., Orlando, FL   (NASPA:CORBRIC7)
**********************************************************************


ΓòÉΓòÉΓòÉ 14. CID install with 21WPSF fix ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We're using NDM/2 to CID install all our software.  The way we implemented the
21WPSF is by including an USEREXIT in the OS2v21 response file.  Assuming that
you have unzipped the 21WPSF.ZIP into a directory \cid\img\21wpsf, you can add
this line USEREXIT = w:\img\21wpsf\applyfix.cmd c: .  W: is the drive
assignment that NDM/2 uses for redirected install.

PS we've been CID'ing for about siz months now.  Fun ain't it.

Chuck Thomas Sunburst Bank Grenada MS
**********************************************************************


ΓòÉΓòÉΓòÉ 15. Installation Needs (personal opinions) ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

  The first two diskettes of the 2.0 and 2.1 GA installations just SIT
there, either with the ЫOS2| BorgBox, or with a "Loading.  Please wait..."
message.  Is it working?  What's it doing?  There should be some sort of
moving status indicator for this section.  If the install is figuring out what
hardware is installed, put up a window with "Determining video
configuration..." and "Determining hard drive types..." and whatever else is
being done.  Give the installer (first time, especially) feedback so s/he
knows it's not dead.
  More color!  More bitmaps!  Make the install a Fun Place To Be!  On this
note, once the first 6 disks are loaded and the PM comes up, install the games
first.  Make them usable (even from a little menu, since the WPS probably
isn't ready) between disk swaps.  It would be Really Impressive to be able to
play games when the OS is still installing.
  For dual-floppy configurations (any combination of diskette formats),
allow the installer to multithread as well as the copy/decompress.  Have the
installer insert disks 1 and 2 into A: and B:, and switch directly to B: when
A: is finished.  Prompt the user to put disk 3 into A: while reading off B:.
When B: is done, prompt the installer to insert disk 4 into that drive, and so
on.  Minimize the install program's wait time, as well as the installer's.
  When installing add-ons (3rd party vendors, as well), have the install
program use MMOS/2 to really ASK the user to insert another disk.  Play a .WAV
when the "We need another disk" dialog comes up.  That's easy 'nuff.  For CD
installation, the sounds could be kept on disc so the drive space impact is
minimized.  If MMOS/2 is installed along with the OS/2 GA, and not as a
separate entity, the install program could start playing WAV files between
diskettes.
  Now that MMOS/2 is part of the OS/2 GA package, install them both
together.  Make the "OS/2 Tutorial" a flashy multimedia application, at least
for the CD install.  The 2.1 GA CD-ROM, even with all the AVI files, still has
over 300 megs free; the tutorial could become a real multimedia extravaganza.
This would also be a good place to plug the Ultimedia tools: once the
tutorial's done wowing the users, tell them it was created with Ultimedia.

Rocco Caputo (Who cares if it can't be done?)
**********************************************************************


ΓòÉΓòÉΓòÉ 16. Announcing LAD/2 4.0 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

LAD/2 4.0 is now available and provides a very easy to use front end
to NetView DM/2 distributions.  LAD/2 and NetView DM/2 now work together
to take advantage of the unattended install capability and rich
distribution function of NvDM/2 and the user friendly LAD/2 interface
to completely automate the CID process when using NetView DM/2.

LAD/2 4.0 will also interface with NetView DM on the host to provide
a complete prep site function.

You can still use LAD/2 to install and distribute software if you are
using NTS/2!  We have packaged both flavors of LAD/2 into one version.

In both versions we have also included the ability for LAD/2 to support
additional network adapters that are not included with LAD/2.

If you have purchased LAD/2 3.1, you will receive the LAD/2 4.0 program
without charge.  Code will be shipped from the software manufacturing
center December 10, 1993.  If you have purchased LAD/2 3.1 and need to
receive the code sooner, please contact your local IBM representative
or you can call us at: 1-800-547-1283 or (817) 961-LAD2 in Canada.

If you have any questions about LAD/2 4.0, please append them to this
forum.
 __  __   _____   _____  ________
|  | |  |  |  __|  |  __| |__   __| Bryan P. Heft
|  |_|  |  |  |__  |  |__   |  |   LAD/2 Partner
|  _  |  |  __|  |  __|   |  |   Dallas, Texas
|  | |  |  |  |__  |  |   Sincerely, USIB5V38 @ IBMMAIL
|__| |__|  |_____|  |__|    |__|
**********************************************************************


ΓòÉΓòÉΓòÉ 17. S3 Graphics @ 1024x768 NI on IBM 14P monitor ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

One of our users just got a PS/2 Valuepoint (S3 graphics adapter with standard
1 meg of video memory) with an IBM 14P monitor.
The problem is that when the user installed the S3 driver and reboots to
a 1024x768 graphics mode it appears the display is interlaced. (Flickering)
We have played around with DSPINSTL and have gotten to the point where it
is asking us for the program that determines the monitor type... problem
is we don't know what the name of the program is.
Any suggestions are welcome.

Wayne "This sure is easier when using an XGA-II adapter" Holmes
IBMLink:PNWB016  IBMMail:USUSWBZW  Internet: [e-mail]
**********************************************************************

On the Valuepoints it is the REFRESH utility that is to be ran at this
time during the installation of DSPINSTL.

Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************

Richard: Thanks... now all I have to do is figure out what diskette
has the program on it. Any suggestions??? <g>

Wayne "Why can't this stuff be integrated the same way the XGA
 support is?" Holmes
IBMLink:PNWB016  IBMMail:USUSWBZW  Internet: [e-mail]
**********************************************************************


ΓòÉΓòÉΓòÉ 18. Incorporating OS/2 4 Windows in a CID Install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Is there a way to set things up to allow a CID server to do both Full OS/2
2.1 installs as well as OS/2 2.1 for Windows installs without setting up
a separate directory structure and wasting about 30 meg on my CID server?
Since the Borg and the Ferengi are essentially the same, can't I just
the Ferengi install against the Borg diskette images?

Also, the Ferengi install asks for Windows diskettes.  How does this
translate into installing from images via CID?

Thanks.

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************

Matt,

Two things to consider:

1)  You said it took 30megs for the full-blown diskette images.  I'm using
  the "salmon" images and it takes 24,343,486 bytes (plus extended
  attributes).  If you are using the original "blue" diskette images, you
  might consider switching.
2)  "Windows stuff" is spread all over the diskette images.  I haven't taken
  a close look at how the "OS/2 for Windows" ("green" diskettes) are
  packed, but I doubt if you'll find more than one or two diskettes
  identical between "green" and "salmon" diskettes.  What you'd like is
  similar to wanting both "blue" and "salmon" images, something overcome
  by having users settle on ONE flavor, then using "OS2CCP."

|  I started looking at the differences between "green" and "salmon"
|  packaging.  The first thing I noticed was that even the README has
|  been moved.  It's now in "BUNDLE" on DISK_2 -- was in "BUNDLE" on
|  DISK_1.  The README, by the way, has extensive changes.

Jim

Jim Stuyck - J.D. Stuyck & Associates - Member, I.V. League - [phone]
**********************************************************************

[Reference to append at 21:59 on 93/11/19 by TBHIC at OS2CUST ]

Matt,

The answer to the first is no.  You need to have separate tree
structures.  For the Windows disk, create directories called DISK_W1,
DISK_W2,... through DISK_W6.

Helen Philippides - BTIG
**********************************************************************

Helen,
   I'd like to understand just what OS2-4W is doing with the Windows
diskettes.  I wanted to install on a machine with DOS/Win, but the Windows
code was loaded from CDROM.  (Soundblaster MM pkg).  I went back with
a selective install once I located my Win 3.1 diskettes (3.5"HD format).
But the install process was all screwed-up !!  I spent probably 3 - 4 hours
fiddling with diskettes.  It would give an error that it couldn't load a
file on diskette number such and such.  I would shell out, find the file
was already in my Windows directory, copy the offending diskette,
make room for the needed file, copy file from hard disk to diskette,
and go back and tell the install to retry.  Not something I would ask
anyone else to do !!
   Are there any plans to address this problem.  I expect a lot of folks
have Windows code preloaded and received a bundled CDROM.

Leo Tornow - Northwest Pipeline Corp.
**********************************************************************


ΓòÉΓòÉΓòÉ 19. Upgrade to OS24W leaves workstation unusable ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Don't know if this is the right forum.  If not, somebody let me know
where to put it.

I recently installed DOD 6.1, LAN Supp, DLR, Win31, WinWord, Excel,
ExtraWin and others on a Mdl 90.  The entire system worked
correctly.

Now the surprise ?

Upgraded the system to OS/2 for Windows (aka. Special Edition for
use with Windows ver. 3.1). The install proceeded flawlessly.  OS/2
came up fine and some of the Windows software worked.  The problem
lies with those products that access the network.  In this case in
particular Extra for Windows.  Also docs/files on server(s) are not
accessable.

From a corporate user standpoint, the upgraded system is not usable.
We MUST maintain mainframe access.  I'm submitting this append for
several reasons:
1) To make everyone aware that networked products won't work with
the upgrade applied.
2) To tell IBM that a problem exists with upgrading networked
workstations.  This upgrade invalidates the DOS network access
facility and now my Windows programs will not work.  This will be
perceived as not running my Windows applications.  The migration has
"broken" my Windows software.
3)  How do I get Extra for Windows to work under the new
environment?
4)  How do I logon to a server?

Our network environment is both LS 3.0 and Novell.  Any help
appreciated.

TIA.

Al Babineaux
Ashland Oil, Inc.

PS.  I'm submitting this on a Friday before going on vacation for
Thanksgiving Week.  Won't be back till 11/29.  So please, don't wait
for me to return, but give the above some consideration and then
reply.  .........Al
**********************************************************************


ΓòÉΓòÉΓòÉ 20. Conversion DOS to OS/2 with 3COM TokenLink Board ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am trying to convert a PC from DOS to OS/2.

Everything went quite well until I installed LAPS and tried to configure
for the token ring.  The PC has a 3COM Tokenlink board in it.  I did not
see anything in the LAPS menus for token ring except the IBM Token Ring
driver.  I selected that for the adapter.

When I boot the machine, it says that the board "was not found or is not
responding".

What do I do?

Bryan Drake @ DIT (OS2 BIGOT)

Bryan Drake @ DIT (OS2 BIGOT)
**********************************************************************

Brian,
Are you using the IBMTOK.OS2 driver ?  If not, you can get it from the
BBS.  Also try changing the adapter in LAPS from Alternate to Primary.
I found a similar report in the database and that was a workaround.

Helen Philippides - BTIG
**********************************************************************


ΓòÉΓòÉΓòÉ 21. HPIIcx Driver Installation - DeskScan II ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Is there any information available to help with the installation of an HPIICx
scanner with the native HP distributed card under either OS/2 and or WINOS2.

Jan Julian, DP Consulting & Services, Fairbanks, AK
**********************************************************************


ΓòÉΓòÉΓòÉ 22. Another OS/2 for Windows Install Problem ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

A friend and I attempted to install OS/2 for Windows from a
CD-ROM on a clone system last night.  We were unable to get the
install program to access the CD-ROM.

The system has a Creative Labs (Panasonic?) CD-ROM attached to
a Sound Blaster-16 card.  We tried reseating the CD-ROM into the
caddy, and the drive lights would flash after doing this, but
the install program would not access the CD-ROM drive.  Is it a
device driver problem?  If so, can we obtain the appropriate
drivers via CompuServe?

Thanks for your help.

Brenda Swafford
**********************************************************************

Brenda,

I haven't tried installing OS24WIN from a CD, but earlier this year I was
able to successfully install the OS/2 2.1 GA package on a machine at a
local Egghead store which had the CL SB-16 & CDROM package installed.

If the drivers shipped with OS24WIN are the same ones shipped with 2.1 GA,
you'll need newer versions.  I'd assume they are available on CompuServe,
but I downloaded my drivers from Pete Norloff's OS/2 Shareware BBS in
northern Virginia (703-385-4325).  I'd post the names, but (a) I don't
remember them, and (b) I'm fairly certain that newer versions have been
posted since then.

It's too bad there isn't a mechanism for distributing OEM drivers through
the OS2BBS. Maybe as disk images available the way the PS/2 Reference
Diskettes are now provided?

Frank McKenney / McKenney Associates / Richmond, Va. / [phone]
**********************************************************************

[Reference to append at 15:53 on 93/11/24 by V$ISWAFF at BCRVMPC1 ]

  Hello, Brenda ЫSwafford|.  I recently saw Creative Labs CD-ROM drivers
for OS/2 on their BBS (408.742.6660).  These may or may not work for you; I
was just looking for audio drivers and haven't tried the CD ones.  Hope you
get this while the rates are still low...

Rocco Caputo (Ft. Lauderdale, FL)
**********************************************************************

[Reference to append at 15:53 on 93/11/24 by V$ISWAFF at BCRVMPC1 ]

I have the Panasonic Double Speed CDROM w/ Soundblaster interface, and
installed it fine.  You do need to get on the IBM/OS2users forum on
Compuserve, or a local BBS and download a file called SBCD2.zip.  It
includes two files you'll need to add to your backup copy of
installation diskett #1 as well as instructions for modifiying the
config.sys.  I'm sure creative's BBS has them as well, but you could
grow old waiting to connect to their BBS.

Dotty Coffey,003025 (xzy3025@rchland)
department 44d
IBM  Rochester, Minnesota
     [phone]
t/l    553-1468
**********************************************************************

Hi Dottie:

We've been looking for this driver on Compuserve but have had no
luck finding it.  Can you append more information about where it
it is located.

Thanks for your help.

Brenda Swafford
**********************************************************************

I think I saw my name, so I'll reply even though I'm not sure which
driver you're looking for.

Possibly the driver for the Panasonic Doublespeed CD-ROM w/ SoundBlaster
interface?

I can't remember exactly where, but if you're using Wincim, you can go
to the OS2Users forum, click on the library-with-magnifying-glass icon,
and do a search on the file SBCD2.*  Or if you're looking for something
else, search on key words like the manufacturer, product name, etc.
Sorry, I can't tell you how to do it if you're not using Wincim, but I
think the Compuserve terminal interface does give you a search option.

I'm a new OS2 user, so don't expect much out of me...it'd be a case of
the blind leading the blind! <grin>

Dotty Coffey,003025 (xzy3025@rchland)
department 44d
IBM  Rochester, Minnesota
     [phone]
t/l    553-1468
**********************************************************************

[Reference to append at 13:24 on 93/12/02 by V$ISWAFF at BCRVMPC1 ]

Brenda,
The Panasonic driver is available here _now_. I'd downloaded it
early this week, in <eager> anticipation that the model 563
I ordered last week will arrive before the weekend!
It is in OS/2 Software Library, Selective Fixes, SBCD2 entry.

Good luck,
Tim Wuthrich
**********************************************************************

Brenda, Tim, Dottie,

I downloaded the file Tim mentioned from this BBS. This driver works just fine.
I installed OS/2 for Windows yesterday on a machine with the Soundblaster 16
package installed and had no problems - except for having to figure out on my
own how to install a Bootmanager configuration instead of dual boot, but that's
another story.

Tim Fansler <TeamOS/2>
**********************************************************************

I'll second the "works just fine" - my drive arrived friday,
so I spent the weekend CD"ing it!  My only question is "why
didn't I get one of these _alot_ sooner???"  (Oh yeah, there
_ was_ the small matter of money and priorities <g>.)

Tim "A real CDdrive convert now" Wuthrich
**********************************************************************


ΓòÉΓòÉΓòÉ 23. Service Pack Installation Sequence for OS/2 Base and DB2/2 CM/2 LAN ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We've recently received all levels of code and service packs for OS/2 2.1,
DB2/2, CM/2, LAN Server.  There are various components such as UPM and FFST/2
that are used by all these OS/2 products.  Is there a recommended sequence for
installing service packs?

Is it safe to assume that OS/2, DB2/2, CM/2, LAN Server follow some conventions
when they release service packs so that they do not overlay each others'
updates?  For example, if I install CM/2's service pack and it updates FFST/2..
can I then install DB2/2's service pack over it?  DB2/2's service pack also
has updates to FFST/2... what will I end up with? Will I need to reinstall CM2?

Where should questions about service pack pre-requisites/co-requisites and
sequence be directed?  I had called the DB2/2 support group and they could only
answer questions for their product but they could not tell me what install
sequence I should use... they suggested I call each product group.  I am
guessing each product group will only know about their own installation...

Another installation issue after applying service packs.... we ended up with
TWO UPM icons... WHY?????

Thanks.

Joe Thurston
**********************************************************************


ΓòÉΓòÉΓòÉ 24. Need Help with install on P70 - blank screen ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I had OS/2 2.0 (no additional fixes) on my P70. This is a 386DX
machine with 8mb of memory. This is the machine that I think has
a gas plasma display but it is supposed to be VGA.

I tried installing OS/2 2.1. When I am finished with all 20+ diskettes
I get the cursor on the screen and it is a blank screen. If I press
ctrl-esc, I get the window list with nothing there.

Please help! I have a lot of programs installed and data on my
hard disk. I did not format the partition since I already had 2.0
installed.

HELP!
Thanks!
Ken Solkowitz
**********************************************************************

Ken,
THere is a file called 21WPSF.zip in the fixes area of the BBS that may
help you with your problem.  You appear to be an IBMer by the id so I
imagine that the same file is available on one of the internal disks.

Jack Hiatt
Team OS/2
The International Phoenix Alliance
**********************************************************************


ΓòÉΓòÉΓòÉ 25. The keyboard doesnΓò¬t work ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Hi Timo,
IΓò¬ve had nearly the same problem when I booted the 90 ALA in unattended
start mode (reference setting). In my case neither mouse nor key-
board did react. I changed the setting and everything worked well.
Hope itΓò¬ll help.
Regards,
J}rgen IBM Germany SMC NW
**********************************************************************


ΓòÉΓòÉΓòÉ 26. trap D during OS221 installation ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

After upgrade from 386Sx to 386Dx I try to reinstall OS2 21 on this
 configuration:
 * 386dx 33Mhz with 64K cache, 8 Meg on board, AMI bios 91
 * SCSI futur domain LCS 6822N controller
 * 80 Meg disk C and 330 Meg disk D
 * 1.44 Meg

and optain a Trap D on diskette 1 before FDISK selection panel

TRAP 002  ERRCD=0000ERACC=****ERLIM=********
EAX=0007bf70 EBX=7beaac04 ECX=00004e04 EDX=00000014
ESI=fff2f5a8 EDI=00000000 EBP=00004de8 FLG=00003283
CS:EIP=0160:fff6704e   CSACC=c09b  CSLIM=ffffffff
SS:ESP=0030:00004f9c   SSACC=1097  SSLIM=00003fff
DS=0158   DSACC=c0f3  DSLIM=ffffffff CR0=fffffffd
ES=0158   ESACC=c0f3  ESLIM=ffffffff CR2=7b8a3000
FS=03b8   FSACC=00f3  FSLIM=00000023
GS=0000   GSACC=****  GSLIM=********

The system detected an internal processing
error at location ΓòóΓòó0160:fff5fbd5-000d:9bd5.
60000 , 9084
0386 00d1
Internal revision 6.514, 93/04/12

Any Idea ?

Thanks
**********************************************************************

Although you state in the "subject" as well as the text of your append that
you got a trap "D," the snapshot you included was for a trap "2."

Trap 2 is associated with bad memory, OS/2 being a notoriously wonderful
checker of "weak" memory.

Jim Stuyck - J.D. Stuyck & Associates - Member, I.V. League - [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 27. OS/2 SYS 2025 and 2027 error - one (?) solution ! ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

   and others responding to this append

Having had difficulties installing OS/2 2.0 on a JDR MCT-M486-33 M.board
(AMI BIOS dated 121291) before, I tried installation again these past
days using OS/2 2.1.
(I never succeeded installing OS/2 2.0 using this M.board, therefore
 I resorted to loading OS/2 while the hard disk was installed in another
 system, then moved the hard disk to the JDR M.board and was then able
 to run OS/2 - what a time eater ...)

I got the SYS02025 and SYS02027 immediately after using the Install. disk.
Trying different remedies : none of them helped (setup : disable cache,
change boot-up sequence, change from 3 chip SIMMS to 9 pin SIMMS etc.)
Scanning the forums I found references to the errors, but the references
pointed to a defective boot drive or defective diskette (see also OS/2
'Installation Guide', below), none of which proved to be the problem
after verification.

Finally I succeeded installing OS/2 2.1 after putting the jumper on the
M.board to slow down the CPU !
After OS/2 installation the jumper could be taken out again, like the
external cache could also be enabled again. This fact was mentioned in
the earlier README file of the 2.1 Beta version(s) - but is not shown
in the GA version (or may I have missed this somewhere in a book ?) !

Also, pages 124/125 of the OS/2 'Installation guide' elaborate on the
SYS 02025 / 2027 errors, calling it a 'disk read error', but no mentioning
that this could be caused by installing OS/2 at the higher speed of the
motherboard.

=> Could someone make a note of this and correct the OS/2 documentation,
  Please ? (Boca ?)

I would like to get from a knowledgeable person some insight, why this
problem could not harm my later 'day to day' operation, running at the
full speed of the CPU - or :
If this should really be no problem later, why is it then a problem
during install - and why can it not be avoided ??

(I wonder whether the people experiencing this problem earlier got their
 problem fixed too, else please try and let the forum know what you find
 slowing down your machine.
 If there still is a collective place for problems with solutions, I fee
 the above should be included - please let me know.)

Hope the above helps !         Rolf Klenk, Team OS/2
**********************************************************************

Rolf,

This kond of behavior has been seen on a number of tuboed MBs, at least by
folks who have reported problems over on the PCCBBS.

Jack Hiatt
Team OS/2
The International Phoenix Alliance
**********************************************************************

'tuboed' - Jack, have you been serenading your machines again?  :-)
                                BT
**********************************************************************


ΓòÉΓòÉΓòÉ 28. How to change XGA resolution via CID and RSPDSPI? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have a question on how to make XGA default to 1024x768x256.  I have
an XGA card with 2meg and would like to CID install it with the above
resolution.  However, with 2 mg, the default is 1280x1024.  Therefore,
I am wondering if the /mc: parameter would help me out with RSPDSPI?
I guess the bottom line is, "Is there a way to specify the resolution
you want your adapter to install at with a parameter in RSPDSPI?"

Thanks for the help
Tim Burleson
**********************************************************************

For what it's worth, the default depends on the display, as well as on the
storage.

John W. Kennedy -- Hoechst Celanese -- The OS/2 Hobbit\Team-OS/2
**********************************************************************


ΓòÉΓòÉΓòÉ 29. Response file install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

How do you get the response file install to work with
the salmon colored disks?  I can follow the procedures
listed in the install booklet and it works with the blue
colored disks, but the salmon disks come up 100K short.

Bob Mahoney - [e-mail]
**********************************************************************

Bob,

Make the following changes to the instructions in the "Installation Guide,"
pages 87-88:

o  add a new step, following "delete the SYSINST2.EXE..." to also delete
  BUNDLE on diskette 1 (the NEW diskette 1).

o  when, during installation, "diskette 1" is asked for the SECOND time,
  insert the ORIGINAL diskette 1 (because it has the BUNDLE needed at the
  end of installation).

Jim Stuyck - J.D. Stuyck & Associates - Member, I.V. League - [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 30. Installation Problem ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I just completed an OS/2 EXPRESS installation.  The system is a PS/2
Mod 60 with a Kingston Technology SX/Now! 386SX upgrade installed.
I have 7 Meg of RAM installed.  The installation went fine then
when I booted OS/2 the first time I got the colored OS/2 logo
screens, lots of disk activity, and finally a blank screen with
c0000005 in the top left hand corner.  Any ideas?

Tom Nichols  Endicott  Tie 855-8006
**********************************************************************

Found the problem.  Stupid me.  The system has an 8514/A card in it
which I installed drivers for.  The problem was, I'm setting this
up for someone else and I just had an 8513 plugged into the VGA
connection.  Once I got an 8514 hooked to the 8514/A card, the
problem disappeared.  Sorry for the trouble.

Tom Nichols  Endicott  Tie 855-8006
**********************************************************************

I was wondering if any one has had any success installing the drivers
for the HT216 local bus video adapter for Packard Bell computers in OS2
for Windows.  The HT drivers come with instructions for installing with
OS2, but it hasn't worked for me yet.

IBM Tech Support told me they don't support HT216's and proceeded to
give me three numbers for Headland Technologies which were no longer in
service.

Thanks

Dotty Coffey,003025 (xzy3025@rchland)
department 44d
IBM  Rochester, Minnesota
     [phone]
t/l    553-1468
**********************************************************************


ΓòÉΓòÉΓòÉ 31. Who has migrated hundreds of users to OS/2 2.1 ? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I would like to talk to people, both IBM and Customer, who have done (or
are planning) an upgrade of a large number of OS/2 1.3, OS/2 2.0 and/or
DOS/Windows workstations to OS/2 2.1.

I am the Project Manager of a team that is planning an automated process
to move over 750 PS/2 workstations to OS/2 2.1.  We plan to migrate up
to 60 workstations in parallel, including full backup, re-partition,
install (OS/2 2.1, CM/2 1.1, LAN Req, DB2/2, AntiVirus/2, NetView DM/2),
restore user data, create folders with all user apps on the desktop.
(small partition sizes force a complete re-build).  We are also migrating
38 Servers to LAN Server 3.0.

We have a technical team designing the process, streamlining, automating
and testing, testing, testing.  We also have over 900 users and over 50
PC applications to move to 2.1, and will pre-test all environments and
products, and give every user a day of OS/2 2.1 workplace/PM training.

At the peak of the roll-out, we expect to be training 90 people per
week and migrating 60 workstations (plus 1-2 servers) per weekend.

I would really like to talk to others who have done similar work with
at least 100 workstations, and preferably several hundred.

We already have developed technical and roll-out plans, and have proposed
this to our client; we need a reference or two to compare approaches and
findings.

Thanks in advance...    Call me, send a note, or append here.

Allan Oas, Project Manager, IBM Canada, Vancouver  604-664-6912
**********************************************************************


ΓòÉΓòÉΓòÉ 32. OS/2 4 Win Lost Memory in Dual Boot ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I recently installed OS/2 for Windows over an IBM PS/2 Mod 70.  The user was
a bit hesitant to "fully commit" to OS/2 so we set it up as Dual Boot.  The
issue has come up that when using dual boot to get back to the DOS/Windows
setup, it appears we've lost approximately 100K  (some of the Windows Apps
now fail due to insufficiant memory).  We've followed the instructions from
the install exactly (ie: adding COMSPEC, SHELL commands to the DOS CONFIG.SYS
that weren't there before).

A quick look with an old shareware program shows 81K that went to COMMAND.COM
that I don't remember seeing before.

Any Ideas?

Thanks

Roman Dumiak - Allstate Insurance
**********************************************************************

  How about DOS=HIGH,UMB in your DOS CONFIG.SYS, along with some sort of UMB
driver (Is it EMM386, or is it the XMS driver?  I used 386^Max "way back when
we had DOS".)  Compare the new CONFIG.SYS with the old pre-OS24W one.
  What are the high-memory driver companies (Quarterdeck, Qualitas, et al)
going to do when DOS finally kicks the bit bucket?

Rocco Caputo (Ft. Lauderdale, FL)
**********************************************************************

Rocco

Thanks for your response. We're using QEMM386.  The CONFIG.SYS hasn't changed
(DOS Version):
 DEVICE=C:\QEMM\QEMM386.SYS RAM
 DOS=HIGH
 DEVICE=C:\DOS\ANSI.SYS
 STACKS=9,256
 FILES=70
 BUFFERS=15
 LASTDRIVE=G

The interesting thing is when I run a Memory Map I get the following:

BYTES   OWNER

 2368   066Ch COMMAND
28304   071Ch SMARTDRV
17280   0E0Dh MOUSE
     :   (Netware related stuff)
  81K  2116h WIN  c:\WIN30386\WIN.COM:\COMMAND.COM

 It's this 81K that I think is the problem (WIN.COM ???)

Any thoughts would be appreciated (I'm not a Windows expert so I'm
not sure what this is).

Roman Dumiak - Allstate Insurance
**********************************************************************

Roman,

This is a portion of an append I made about a month ago.

 From OS/2 they select dual boot and DOS boots ok BUT QEMM fails to
 load some device drivers high (no room).  If they then cntl-alt-del reboot
 QEMM loads the drivers just fine.

It looks to be a similar problem.  I never got a response back.  I hope
you have better luck.

Dave Ferrey - EDS - Bethlehem Steel
**********************************************************************

I had the same problem when I installed a token ring card in a DOS/WIN
machine.  Even though I was very careful with making sure the mappings
etc were "correct" it would only work after a warm boot.  Go figure.

Anyways, the solution was to buy the new version of QEMM.  I don't know
if it was this or just the reinstallation that fixed it, I just Know
it went away.  AND AT NO POINT WAS OS/2 INVOLVED!

Gareth "My experience, for what it's worth" Jones
ISM - Information Systems Management Regina Sk Can.
[phone] TeamOS/2, OS/2 Ambassador & Generally Nice Guy
**********************************************************************

 To those of you who replied and anyone else considering installing OS/2
 for Windows....  My original problem stated that after installing a Dual
 Boot environment for with Os/2 for Windows that we lost about 100K when
 going back to DOS/Windows.

 What we have uncovered to date is this:

 The WIN.COM which is used by both OS2-WIN and DOS WINDOWS is now 91K
 larger than it was originally.  In rummaging through the hard drive there
 are apparently three files:

  WIN.COM   new after installing OS/2 for Windows
  WINOS2.COM  same date/size as WIN.COM
  WINDOS.COM  the "original" WIN.COM (Smaller/older date)

 What we have done to correct the problem is rename WIN.COM to WIN.OLD and
 renamed WINDOS.COM to WIN.COM.  Things seem to be working and we have the
 91K back. The WINDOS.COM seems to be working in both DOS (as expected) and
 under OS/2 (so far).  We've opened a problem report on this but so far no
 one has responded. If they come back with any useful information I'll post
 it.

Roman Dumiak - Allstate Insurance
**********************************************************************


ΓòÉΓòÉΓòÉ 33. OS/2 CDROM installation on Phillips CD player ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Hello, I am hoping somebody can help me with my OS/2 2.1 installation, I
have a Phillips CDROM which came with my GateWay 2000 machine, when I try
to install OS/2 my CDROM won't even flinch.  I probably need a driver for
my Phillips but I haven't been able to find it anywhere!!
If somebody knows where I can get this driver, or maybe even send me the
driver I would appreciate it greatly.  Please help I am running out of
patience, since I have been trying to get this to work for over a month
now!
Please respond to my reader if you have any answers for me, thanks in
advance.

William Lazo De La Vega
**********************************************************************

If it's the CM205 CDROM drive from Phillips (LMS), there seems to
be some information on the OS2HW (hardware) CFORUM. You should be
able to locate the appends with a keyword search on PHILLIPS or
CM205.  Good Luck.

Lew Pitcher
System Programmer
Toronto Dominion Bank
**********************************************************************


ΓòÉΓòÉΓòÉ 34. Cirrus Logic video on Gateway 2000 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I found the below append ealier in this forum but didn't see any
response.

I am having the exact same problem on my machine, same configuration.

Can anyone help?

Doug B.
IBM Rochester

Subject: Running DSPINSTL to Install Cirrus SVGA Drivers Gets SYS3171 Error

OS/2 2.1 installed on a Gateway/2000 using CIRRUS SVGA driver. Installed O.K.
with the standard VGA drivers. Went to run DSPINSTL to install 1024x768 driver
for CrystalScan monitor and got system error SYS3171.

Occurred after selecting the PRIMARY DISPLAY ADAPTOR TYPE on window and clickin
g on OK.

Register display show exception c0000005 at 12705b1f occurred.

Any ideas or known problem ... I have not called support center yet.

Thanks.

Steve Story, Barrington
**********************************************************************


ΓòÉΓòÉΓòÉ 35. Running OS/2 for Windows with Win for Workgroups 3.11 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I'm about to order OS/2.  Will the OS/2 for Windows product work
with Windows for Workgroups 3.11 ?

Mike Valenti
ISM - Information Systems Management Corporation
North York, Ontario - [phone] - FAX [phone]
**********************************************************************

No.

   Mel Hallerman
**********************************************************************


ΓòÉΓòÉΓòÉ 36. Problem with EarlyUserExit in OS/2 Response File ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am trying to use the EarlyUserExit to do a CHKDSK on a drive before
migrating from OS/2 2.0 to 2.1. This would be to validate the state of
the drive. I put the command into the response file, but it doesn't seem
to be recognized. The UserExit keyword that I've put in are, so it doesn't
seem to be the response file. Are there a special location that this
keyword needs to be in the file or any other notes?

The response file command is:
EarlyUserExit=x:\cid\userexit\chkdsk\chkdskc.cmd

CHKDSKC.CMD contains:
pause   (put in to test if this command file was being executed)
x:
cd \userexit\chkdsk
chkdsk c: /f

Any experience people have would be appreciated.

Thanks in advance

Jim Sauber, MN Mutual
**********************************************************************


ΓòÉΓòÉΓòÉ 37. OS/2 for Windows with 2.1GA ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

A couple of my clients who have the Borg version of OS/2, want to
get rid of the WIN-OS/2 on their boxes and go with their native
Windows installation.  Could this be as easy as replacing the Borg's
selective install with the one from the Ferengi, then using that to
do a selective install of their native Windows? Will other files
need to be replaces?  Perhaps BOOT.COM?

Also, when the 2.1 CSD comes will it have the capabilities to use the
native MS Windows already there?  That is, assuming it comes out in a
manufacturing refresh format <G>?

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************

The 2.1 csd beta (which just came out) says that it does not apply to
the os2fw version.

Alan Arnett, Fina, Dallas, TX, [phone], IBMMAIL: BET3KKRK
**********************************************************************

>The 2.1 csd beta (which just came out) says that it does not apply to
>the os2fw version.

But the real CSD should.

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************

Matt,
  This CSD is a Manufacturer's Refress, not a conventional CSD.
When the beta is over, it should be 1 CSD (detecting the target during th
the service) and 3 manufacturing refress, : 2.1 Full, 2.1 for Win31 and
2.1 WithoutWindows.

Geza Szivos <TEAM-OS2> IBMMail(CANOVXVV) The Phoenix Alliance
NOVACOR Chemicals (403)-290-6583 Fax [phone]
NHO-32 801-7th Ave Calgary, Alberta, CANADA T2P 2N6
**********************************************************************


ΓòÉΓòÉΓòÉ 38. PROBLEMS WITH 8514/A AND 2.1 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We have a PS/2 8580-311 with 8514/A Display Adapter and 8514 Monitor.  When we
install 2.1 it does does not recognise the presence of the 8514/A and installs
VGA support.  I used selective install and specified the 8514/A.  When I
rebooted the desktop was almost unreadable.  I had to reinstall VGA support to
make things useable.  Can anyone tell me what I am doing wrong?

Thanks, Paul wylie.

PAUL WYLIE  M. BRYCE & ASSOC.
**********************************************************************


ΓòÉΓòÉΓòÉ 39. Uninstall SB 16 WinOS2 software ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Does anyone know of GOOD way to uninstall the Windows portion
of SoundBlaster 16 software?  Hopefully, maintaining the other
installed Windows applications.
Jan H. Julian, DP Cons & Svcs
**********************************************************************

I am trying to load OS2 2.1 on my clone machine. I have an Adaptec
SCSI card. I get the above error on the second disk. What are the pro-
ceedures to try in a situation like this? Thanks !!!!!!!!!!!!!!!!!!
**********************************************************************

  Is your Adaptec controller's BIOS enabled?  Have you made any changes to
the controller jumpers and/or switches?

Rocco Caputo (Ft. Lauderdale, FL)
**********************************************************************


ΓòÉΓòÉΓòÉ 40. Config.sys did not migrate ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Hello-
 I just installed OS/2 2.1 on top of OS/2 2.0. My Config.sys did not
migrate over.
 Here is my environment:
  DELL 433/L with 204 M Hard Drive
  Drive partioned into C, D and E
  D drive has OS/2 on it and is 90 M
  16/4 Token Ring Card
  16 Meg of Memory

The Config.sys file has alot of "stuff" in it for Comm Mgr, Netware, TCP/IP
and the such. Plus our path statements are rather involved with Applications
off the LAN.

I used a CD ROM (NEC Multispin) to load the software. So I added the SCSI
adapter card to my system and connected the CD. I then added the nessary
CD .add statements to the config.sys located on the Diskette 1. The install
went smoothly (I backed up the current config.sys preparing myself for
possible problems). The ONLY problem I could determine was that the config.sys
did not migrate. In fact the Config.sys that did end up on the DELL machine
was the one that came off of the Diskette 1 and of course that had calls
to sysinst1.exe and sysinst2.exe which are used during the install.

Does anyone know what I might have missed for this to happen? I also should
indicate that the original config.sys does not have any statements in it
for the CD rom since the CD rom was ONLY used for the install and is not
normally connected to this machine.

Thanks.

Hilary - Charles Schwab, [phone]
**********************************************************************

Hilary,
You might want to post this in the OS2Beta CForum as requested in the
package.
There have been a number of folks there reporting problems with config.sys
migration.  You might find some help there.

Jack Hiatt
Team OS/2
The International Phoenix Alliance
**********************************************************************


ΓòÉΓòÉΓòÉ 41. Response file install; FAILED. ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Before I spend a ton of time looking at this could someone take a crack
at a quick resolution?

I created a response file (OS/2 2.1), started the install and was just
past the Logo screens with "Loading files. Please wait..." on the screen.
The KA-BOOM!

 "SYSTEM INSTALLATION FAILED TO START THE SESSION."  That's it.

Do you need more info for this?  Should I post my resp' file?

Appreciate any help.  Thanks  Jim
**********************************************************************

Jim-
  When I get this error, it ususally means that I pointed to the wrong
place for my disk1 image or it cannot access this for some reason.

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 42. TRANTOR install problem ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am unable to add a TRANTOR 338 with a NEC 74-1 CDROM drive to a
720c with the following config.

12MB - 160MB(HD)  -  IBM High Speed FAX/MODEM. running 2.1GA

I have installed the trantor drivers and drive is initiated as OS/2
comes up. however if there is a CD in the drive I get a hard drive
icon in the drives folder and if there is NO CD I get a CDROM as the
icon (that is reversed of every other CDROM I've ever seen). In any
case the clicking on the icon show the appropriate choices for a
CDROM drive, and even eject works!

However OS/2 access to DATA give a SYS0026, and VDM access gives
either a SYS0026 or a SYS0002.

Under DOS the drive is fine.

My client is getting a _little_ concerned...

Kevin Danzig    D.F.M. Solutions Ltd.
**********************************************************************

Kevin, Please see my reply to your question about using the MiniSCSI with
the ThinkPad in the OS2HW CFORUM.

Thanks,

Brian Peterson  [e-mail]
**********************************************************************

Thanks and Thanks again...

I had my Hardware guy order either the 348 or the 358 today and get
an R/A for the 338. Now if I only knew how to bill for my 4 hours of
lost time (this time I only killed 4 hours, ThinkPads often remind me
of M$-DOS 6.x... but they are much more useful ;-)

Kevin Danzig    D.F.M. Solutions Ltd.
**********************************************************************


ΓòÉΓòÉΓòÉ 43. Constant rebooting at install; >16 MB. ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Scenario:
I have two EMO's without ROM in an 8580-081 with 4 MB on planar.  I
downloed the NEWEMO package, patched the IFDDF.ADF file's version
number, and ran autoconfig twice.  Memory counts to 4 MB as before and
pauses, then beeps, then counts up to 22 MB.  I know the patched .ADF
got on the hard disk because the "KB OK" is now appearing as "KB ok".

What I need to know and verify is whether OS/2 2.1 is really using the
memory or just as a large swapper file.  I tried loading tons of apps'
and it was a while before my swapper got bigger, but as I removed stuff
from memory the swapper did not shrink.  Is this normal?

Any programs or tests I could do against this memory?  Appreciate any
tips or suggestions.  Thanks.

James Docherty
**********************************************************************


ΓòÉΓòÉΓòÉ 44. 2.1 dual boot install on Compaq Deskpro 66M ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

   On two different 66Ms, with 240M IDE harddrive and Qvision 1024/e graphics
controller card, single partition C:, with DOS 5.0, already installed, I tried
to install OS/2 2.1 GA.  The install seems to go OK, but once initialization
has completed and try to reboot, various system files disappear.  During
initialization, get messages about extended attribute errors on some files (not
the same ones in each case).  Some applications work, but for others some of
files have disappeared.  Each time I reboot it seems to go from bad to worse,
with more and more files disappearing .
   When I dual boot to DOS, most applications work OK.  However, trying to
read any files with SPF2 (Command Technology), errors occur.  I don't recall
other anomalies.
   Also CHKDSK under OS/2 always seems to uncover problems each time I boot.
   It seems that the FAT has been corrupted.  Eventually I split the hard
drive into two partitions, C and D, installed the Boot Manager partition,
put DOS onto C and OS/2 onto D.  That works OK.
   However I have about 5 other 66Ms that have a single partition with
dual boot DOS 5.0 and OS/2 2.0.  I want to install 2.1 over 2.0, but am
concerned that the same thing is going to happen.  I have contacted OS/2
support.  Their suggestion was to use two partitions, but there is quite a
bit of time involved in rebuilding the partitions on all the machines.  Plus
space is a bit tight now, so I would prefer to keep the single partition.
I also called Compaq, but I wasted my 20 minutes waiting for a rep in this
case.  They seemed to feel that it was a configuration problem and for help
they charge.
   If anyone has had any experience with this or suggestions, I would
sure appreciate any replies.  Thanks.
 -  Dave Greene

Dave Greene.  (Kwasha Lipton).
**********************************************************************


ΓòÉΓòÉΓòÉ 45. MSSER01.SYS ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

The OS/2 on-line help mentions (in passing) a driver for the MS mouse:
"DEVICE=MSSER01.SYS".

Is MSSER01.SYS on the installation disks?
Or do I have to get MSSER01.SYS from Microsoft?
**********************************************************************


ΓòÉΓòÉΓòÉ 46. Monitor setup on IBM PS/2 9585 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We have an IBM PS/2 9585 with the "standard" SVGA adapter. (IMHO "standard"
and "SVGA" is an oxymoron, but that is reserved for another message. <g>)
The monitor we are attaching is a IBM 14P. Now come the questions...

- What is the maximum resolution for that combination?
- Can the setup for non-interlaced display at the maximum resolution?
- Finally... how in the world do you setup OS/2 so you can get that
 display? (I have the feeling that the infamous "REFRESH.EXE" is
 involved here.)

Wayne "Why can't this be as easy as XGA?" Holmes
IBMLink:PNWB016  IBMMail:USUSWBZW  Internet: [e-mail]
**********************************************************************

From: Mike Walsh
To:  PNWB016 at HONE81╨╢

We have the same problem. We bought the machine for a power user as
IBM had nothing similar that they didn't call a "server". We added
a 17 inch colour screen. We relied on the fact that there was an SVGA card in
the machine.
As you say it's a "standard" SVGA card i.e. it's got only 512KB of memory.
Mean b*****s IBM selling a machine at that price with that kind of memory
amount.
Anyway the "best" we can get on that 17 monitor is a wonderful
102x768x16(!) at 43 (no misprint) Hz and interlaced at that. Absolutely
terrible.
We also found it impossible to change that setting to VGA with 256 colours.
The tech. info in the IBM announcement by the way says it's actually a card
for "VGA use".
So marketing and the tech guys obviously don't speak to each other.
Mike

* EMEA OS/2 Developer Assistance Program BBS
* gHostNet(0057002C01000000 2d119150) reply to (0008037800580000 B4280F98)
**********************************************************************

Mike: In our case we bought the 9585 because we needed the extra slots
for a BUNCH of connection adapters. (It is a specialized application for
our mainframe operations group.) In theory, the 9585 is MEANT to be a
server machine, so it doesn't need to hi-rez graphics, but in our case
it is an END USER machine...

Do you know if the adapter can have more memory put in it, or do we need
to look at getting a new adapter?

Wayne "Inquiring minds want to know" Holmes
IBMLink:PNWB016  IBMMail:USUSWBZW  Internet: [e-mail]
**********************************************************************

From: Mike Walsh
To:  PNWB016 at HONE83╨╢

As far as I've been told, you can't add memory to the 9585 graphics card.
(That would be too easy now, wouldn't it). Instead they are saying to replace
it with an XGA which seems a bit stupid if IBM really have abandoned XGA. The
original graphics card ? You just throw it away like the garbage it is. Mike

* EMEA OS/2 Developer Assistance Program BBS
* gHostNet(0057002C01000000 2d16e53c) reply to (0008037800580000 B42BA78D)
**********************************************************************


ΓòÉΓòÉΓòÉ 47. OS/2 4 WIN and DELL mouse.drv ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

When OS/2 for Windows is installed on a DELL that came pre-loaded with
MS Windows, the mouse pointer will be off by about a half inch when in
seamless Windows.

The problem is that DELL has reworked the \windows\system\mouse.drv.
DELL admits this and suggests that the solution is to install mouse.drv
from the MICROSOFT diskettes of MS Windows.

Also note: In full-screen Windows, \mouse\mouse.drv is used.
In seamless Windows, \windows\system\mouse.drv is used.  This means that
in seamless Windows, you will not have the extended functions of the
MS Mouse ver 9.00.
**********************************************************************


ΓòÉΓòÉΓòÉ 48. OS/2 installation on Valuepoint 466DX2/D ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Just downloaded this forum in preparation for doing some more upgrades
to OS/2 2.1 on this very type of machine.

We have successfully installed 2.1 on several of these machines.  We
have up to now always reformatted the disk when doing, mainly to, as the
project lead stated, "reduce ambiguity".  AKA reduce Murphy.  In most
cases the programmers didn't have data files to be concerned about, so
wiping the disk made sense.

I did have disk problems on the latest install, but have not seen the
trap you mentioned.  I also hung the installation once by selecting SVGA
instead of VGA.  I think the display driver for the Value Point monitors
was not in the set of SVGA drivers, and this is what caused the hang-up.
Just a guess, but based on past experience - mine and others.  Also the
install should, but doesn't, tell you that it can't find the driver.  It
accepts SVGA at the time it's selected.  It hangs at the end of the
install, many disks later.

------

I'd like to know if anyone has installed 2.1 on this machine without
following the suggestion in the readme.ins file on disk #3 to change
setting so that:

   - turbo/system speed should be OFF/slow
   - chaching (external) should be OFF
   - ROM shadowing should be OFF

I can find access to only the second item (external caching).  I
disabled when I upgraded my Value Point, but another was recently done
without disabling.  The readme.ins file warns of >>>unexplainable random
traps<<<.  Perhaps this is what happened to you.

BTW, you get at the caching by hitting F1 during startup and the
Power On Self Test, while the VP is checking memory and there's a
rectangle in the upper right of the screen.  See pg 42 of the PS/Value
Point User's Handbook - the chapter on Configuration Utility.
**********************************************************************

Sounds like memory, check your simms.....
**********************************************************************


ΓòÉΓòÉΓòÉ 49. SYS02025 SYS02027 problems ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am also having the same problem installing OS/2 for Windows on
a PS/2 Model 60 with a 486 Kingston Card installed. Any suggestions
or is it back to DOS 6.1???????

Dave White
**********************************************************************

Check your diskettes, and floppy setup in that machine.  The 2025 and 2027
are usually seen when the system doesn't recognize the floppies a boot
diskettes.

Jack Hiatt
MARC-Life Atlanta Ga.
Team OS/2
The International Phoenix Alliance
**********************************************************************

I have also seen this with a DEC 486-66 where the floppy drive was
apparently more sensitive than all the other drives in our building.  A
utility diskette wouldn't boot. Diskette was okay on other PC's, just
not this evaluation machine. Othe boot diskette worked fine.

Alan Arnett, Fina, Dallas, TX, [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 50. SRVIFS CID Install on 750c/PCMCIA TR Card ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Has anyone gotten CID to work installing on a ThinkPad 750c with a PCMCIA
card?  As far as I know, we have the latest drivers available. But we
keep getting a sockets error in our LANTRAN.LOG, apparently from the
token ring driver.

Any help on this will be appreciated.  Thanks.

Matt Hickman  Internet: [e-mail]   [phone]

| Turns out that we were using the Microchannel driver and we needed
| to use the ISA driver.  The 720 machine is MCA, while the 750 is ISA.
|And here I thought they both were PCMCIA B-}  Sigh...
**********************************************************************


ΓòÉΓòÉΓòÉ 51. Emergency Question about OS/2 Diskspace. ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Ref:   None

From: Mario van GILS
To:  All

* Original Area: C.OS2REXX
* Original To  : All (87:44/256)

We wan't to know how is the limitation of OS/2 diskspace for one partition.
Did any body knows that ?
Thanks for your answers.
Ciao Mario...

* EMEA OS/2 Developer Assistance Program BBS
* gHostNet(0057002C01000000 2d186af4)
**********************************************************************


ΓòÉΓòÉΓòÉ 52. EA_DATA._SF ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I recently installed OS/2 for Windows over MS DOS 6.2 and MS Windows 3.1.
I am using the FAT file system in order to use the dual boot feature.

I noticed that EA_DATA._SF is nearly 7 meg in size.
(I have about 7000 files.)
Is this about the right size for EA_DATA._SF ???
(That would be about 1K per file.)
**********************************************************************

The space for EA DATA. SF is allocated in clusters-per-file, just as the
free space is allocated for the files themselves, so, yes, 7MB is not
unlikely.

Here's the best thing you can do.  Some time when you have a few hours free
<grin!>, back up everything and repartition your disk into four partitions:

Boot Manager
C for DOS only (FAT)
C for OS/2 only (HPFS)
D for both (FAT)

This will generally be a better approach than dual boot, and will save you a
lot of disk space if you find (as most do) that you don't really need to put
much stuff in the DOS C partition or the D partition.  (I believe I have 8MB
for the first and 32MB for the second, with everything else on the HPFS
partition.)

John W. Kennedy -- Hoechst Celanese -- The OS/2 Hobbit\Team-OS/2
**********************************************************************


ΓòÉΓòÉΓòÉ 53. "Unmoveable" files ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I recently installed OS/2 for Windows over MS DOS 6.2 and MS Windows 3.1.
I am using the FAT file system in order to use the dual boot feature.

The MS DOS 6.2 defragger now shows that several dozen (yes, I said several
dozen) files/clusters/blocks are "unmoveable".

Why is this?  What does this mean?
**********************************************************************

DEFRAG treats "System" and "Hidden" files are "unmovable".  With dual-boot,
you now have not only IO.SYS and DOS.SYS (or whatever their names are -- I'm
accustomed to PC-DOS, with IBMBIO.SYS and IBMDOS.SYS) in that category, but
OS2BOOT, OS2LDR, OS2KRNL, OS2DUMP, OS2LDR.MSG, OS2VER, EA DATA. SY and
WP ROOT. SY.

Some of those are safe to mark temporarily not-System and not-Hidden and then
defrag, but the last I looked (I use HPFS and Boot Manager, nowadays, so the
subject hasn't come up for me in a while), some of them are not safe.  I know
that EA DATA. SY and WP ROOT. SY are safe when using Norton SpeeDisk or IBM
PC-DOS 6.1 DEFRAG, but I don't know for sure about MS-DOS 6.2 DEFRAG.  (I also
know that the DOS files are _not_ safe to defrag.)  Authorities differ as to
whether it is _smart_ to defrag EA DATA. SY or not, anyway.

John W. Kennedy -- Hoechst Celanese -- The OS/2 Hobbit\Team-OS/2
**********************************************************************


ΓòÉΓòÉΓòÉ 54. OS/2 2.0 on a Thinkpad 750 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Ref:   None

From: A1aa2415
To:  All

I need to get OS/2 2.0 working on a Thinkpad 750 - I've noted other messages
concerning a 720 but these involve the use of replacing files on the OS/2
install diskettes with files form the 720 reference diskette - the 750
doesn't have a reference diskette. Can anyone help ????

* EMEA OS/2 Developer Assistance Program BBS
* gHostNet(0057002C01000000 2d19e7a2)
**********************************************************************

Ref:   None

From: A1aa2415
To:  All

Can anyone help.  I've jsut got a Thinkpad 750 and I need to run OS/2 2.0 on
it. I've found instructions for putting it onto a 720, but these use the 720
reference diskettes and I didn't get any reference diskettes with the 750.
Any ideas

* EMEA OS/2 Developer Assistance Program BBS
* gHostNet(0057002C01000000 2d29bd1c)
**********************************************************************

[Reference to append at 13:11 on 93/12/23 by EMEADAP at WINVMB ]

The 750 Documentation states explicitly must be 2.1 or higher...If
you MUST get 2.0 on, you might try the ABIOS workarounds used before.
**********************************************************************


ΓòÉΓòÉΓòÉ 55. Lost Mouse...any cheese? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Ref:   None

Just upgraded from 2.0 to 2.1GA.  Trackball was working fine before.
On bootup, error screen - SYS1201:the device driver "C:\OS2\MDOS\
VMOUSE.SYS specified in....was not installed. Line 70 is ignored.
Booted with DOS diskette...checked for vmouse.sys - it was there, checked
for mouse.sys in config.sys....device=C:\OS2\MOUSE.SYS SERIAL=COM1
and file was in right place, cable plugged into same COM1 port.

Tried to delete both line from config.sys....rebooted OS/2...installed
new mouse.....still no mouse cursor! checked config.sys.....new lines
were inserted.  Reset w/o shutdown.....35 files FILE00xx.CHK were loaded
onto C drive.  Is this the time to run CHKDSK ???

Thanks for any assistance

 Stew Corman from sunny Endicott
**********************************************************************

>>Is this the time to run CHKDSK

the Filexxxx.chk WAS created by ChkDsk.

When you boot OS/2 and if fouds out that you hard-drive is 'dirty'
(power off reboots, dual-boot) then OS/2 runs Chkdsk at boot up time.

Geza Szivos <TEAM-OS2> IBMMail(CANOVXVV) The Phoenix Alliance
(403)-290-6583 Fax [phone]
**********************************************************************

[Reference to append at 15:02 on 93/12/23 by SCORMAN at ENDVM1 ]

>Tried to delete both line from config.sys....rebooted OS/2...installed
>new mouse.....still no mouse cursor! checked config.sys.....new lines
>were inserted.  Reset w/o shutdown.....35 files FILE00xx.CHK were loaded
>onto C drive.  Is this the time to run CHKDSK ???

The only time I had problems with that many .CHK files was on the first
couple of installs--the ones that kept corrupting until I could no longer
boot.  I don't think that many .CHK files bodes well for a long life.

As to the mouse, I had similar problems and got around it by placing the
mouse driver before the COM.SYS driver.  That worked for me...  I too am
using a trackball sucessfully-little solace, I know...

Ken Prevo
**********************************************************************

[Reference to append at 15:02 on 93/12/23 by SCORMAN at ENDVM1 ]

  It is my opinion that upgrading to 2.1 over 2.0 is a Bad Idea.  This comes
from lots of problems I've had trying to do so.  One pretty successful way
I've found is to boot from floppy and delete the entire \OS2\* file tree,
only leaving customized files there (1).  Then install 2.1 into the cleaned
out file tree.  The absolute best way I've found to make sure nothing strange
is left behind from 2.0 after the upgrade?  Back up your user files, low-level
format, partition, and install 2.1 as if this were the first installation.
  Then again, I've been having problems with this one Frankenstein machine.
Enough of them to wonder if it's easier to just go and buy a new one to make
them stop.

(1) I've since put all my custom files into directores not in the \OS2\* file
tree, so I don't have to worry about losing them on an update.

Rocco Caputo ([e-mail]) (Connecting from Ft. Lauderdale, FL)
**********************************************************************

Rocco,
Think a highlevel format would be sufficient.

Jack Hiatt
MARC-Life Atlanta Ga.
Team OS/2
The International Phoenix Alliance
**********************************************************************

Thanks to Rocco and Jack for your appends.  I cannot say that I am
comforted by the previous appends of OS/2 FW having the SAME problem.
I am feeling like a leper......On my own, I backed up all my important
files, wiped the disk clean with a low level format, used FDISK to make
three partitions ( only had one before on the Seagate ST1239A/210meg ),
preformatted them using a DOS bootup, ran Norton 2.0 to verify good
tracks, and re-installed OS/2 2.1 twice more times (am getting good
at this <grin>). Does not load VMOUSE.....opens desktop....works for a
minute or two moving icons around or droping/opening a few.  All of a
sudden, either a window will blank w/ system hang, or the mouse buttons
don't respond, or an error screen pops up claiming a file can't be found.
Thought that it might be a trackball hardware problem, so I BRS, plug
in a M*crosoft mouse (real one) and same thing happens.  Tried to switch
ports from COM1 to COM2...power down, retry....SOL....same response.
Thought I was going to have to change board jumpers and install an
additional I/O driver card.....BUT everything worked with OS/2 2.0 !!
If others have seen the same type of performance, I'll wait for a
more learned sagelike answer.  In the mean time, I'll look up the
keyboard stroke to use my Lot*s spreadsheet.  I was planning to
install a new Multi-media kit with PAS 16 card, since only 2.1 has
the MM support......Windoze had better not be the solution !!!

Let's keep the ball rolling on this one and thanks to all the kind
contributors.

Stew Corman from sunny Endicott ( w/ 1 foot snow on the ground)
**********************************************************************

Stew,
Don't recall for sure, but I _seem_ to remember something about
VMOUSE.sys needing to come before MOUSE.sys (I could be totally
"mis-remembering" this, but you might check that...)

Tim "Only 8 inches of snow here" Wuthrich,
The Upjohn Company
**********************************************************************

[Reference to append at 23:28 on 93/12/27 by SCORMAN at ENDVM1 ]

Stew,

If you still have your 2.0 disks around, try copying the MOUSE.SYS file
from disk one to the OS2 directory on the partition that has OS2
installed.

Caveat:  You lose Hot plug, Pen, and APM support.

If this works, I would suggest calling support with a detailed hardware
description.

Good luck,
Gordon Webster  IBM OS/2 Change Team
**********************************************************************

I have spent toooooo many hours on this installation so far.  The
MOUSE.SYS installed from diskette is dated 4-26-93 with a size of
15053.  The error SYS1201 has disappeared but the trackball is stone
dead......no movement, no action from either button.  I rebooted to
DOS and ran the Mouse Systems install diskette and it has no problem
finding the hardware on COM 1 and all the buttons work as well as
moving the cursor.  Sure sounds like a software bug to me <not grinning>.
Just got my Compuserve package in the mail, so it looks like I will
be reloading Windoze to see how it works.  I am not a happy camper.

Any new recommendations are welcome.

Stew Corman from sunny Endicott
**********************************************************************

I must be pigheaded or love to torture myself, but I did some more
experimenting:  turns out that the MSCMOUSE.COM that comes with the
trackball logs in where it finds the trackball.  When booted from
DOS diskette, the trackball is found properly on COM1, which is good
because the modem is on COM2.  However, when OS/2 loads a DOS window,
the mscmouse command in the autoexec.bat causes it to be found on
COM2.....WRONG!  If I attempt to force it to COM1, I get a "port not
available" or such.  Now some other observations: when the third light
of the modem "DTR" is on (modem not being used at this time) the
trackball will work for a few drag/drops.....then system crashes with
the DTR lamp going out. Most of the time on OS/2 bootup...the trackball
is totally dead....no buttons, no cursor move.....the arrow sits in the
middle of the screen.  Pulling off the modem cable did not improve.
Bootup from DOS works fine and so does Windoze.

Stew Corman from sunny (but cold) Endicott
**********************************************************************

[Reference to append at 22:08 on 93/12/28 by SCORMAN at ENDVM1 ]

I have spent toooooo many hours on this installation so far.  The
MOUSE.SYS installed from diskette is dated 4-26-93 with a size of
15053.  The error SYS1201 has disappeared but the trackball is stone
dead......no movement, no action from either button.  I rebooted to

I just checked and mine is the same date and size.  I'm running a Logitech
trackball and am in love with it.  Couldn't return me to a rodent with a
gun.  I am using SIO for my Com support.

I just looked through my CONFIG and the only part that seemed strange is
that VMOUSE.SYS (required for DOS/Win) is earlier in the list than the
MOUSE.SYS driver.  Not sure why that is but it works....

BTW...
C:\OS2\MDOS\VMOUSE.SYS                 14688  05-04-93  13:15:02

Ken Prevo
**********************************************************************

[Reference to append at 16:45 on 93/12/29 by SCORMAN at ENDVM1 ]

>because the modem is on COM2.  However, when OS/2 loads a DOS window,
>the mscmouse command in the autoexec.bat causes it to be found on
>COM2.....WRONG!  If I attempt to force it to COM1, I get a "port not
>available" or such.  Now some other observations: when the third light
>of the modem "DTR" is on (modem not being used at this time) the
>trackball will work for a few drag/drops.....then system crashes with
>the DTR lamp going out. Most of the time on OS/2 bootup...the trackball
>is totally dead....no buttons, no cursor move.....the arrow sits in the
>middle of the screen.  Pulling off the modem cable did not improve.
>Bootup from DOS works fine and so does Windoze.

Ahhh Ha! You don't use the DOS mouse driver with OS/2!!!!!  Remove it from
your autoexec.bat and I bet the mousestarts to work.  You have dueling
drivers!  VMOUSE.SYS provides DOS with mouse services automatically--just
as the gods intended but MS couldn't figure out how to do without a
separate driver.  OS/2 ain't that dumb...

Ken Prevo
**********************************************************************

[Reference to append at 16:45 on 93/12/29 by SCORMAN at ENDVM1 ]

Stew,
  I had a similar problem with OS/2 2.0.  When I moved the mouse, my
modem started dialing.  I found that my COM1 and COM2 were sharing
interupts.  I found the manuals (very difficult) and moved some jumpers
and all worked well.

Eric Brunsen
Armadillo Software Ц DEV4793

Internet:  [e-mail]

International Phoenix Alliance
OS2BBS:  TPA0001 - Eric Brunsen
**********************************************************************

[Reference to append at 16:27 on 93/12/29 by WZ01343 at HONE83 ]

>I just checked and mine is the same date and size.  I'm running a Logitech
>trackball and am in love with it.  Couldn't return me to a rodent with a
>gun.

Ken,
Partly as the result of your append, I'm trying out a Key Tronic board with
a trackball.  It is working just fine,  and it has several nice features
as well as good ballistics, but it sure will take some getting used to!
How long before you were as quick with the T-ball as with the old rodent?

Tim Wuthrich
**********************************************************************

>Partly as the result of your append, I'm trying out a Key Tronic board with
>a trackball.  It is working just fine,  and it has several nice features
>as well as good ballistics, but it sure will take some getting used to!
>How long before you were as quick with the T-ball as with the old rodent?

I wasn't much of a mouser so my transition to it was almost instantaneous.
I'm glad you are sharing my enthusiasm (at least partially) for it.  I've
found that mice and their alternatives can spark religious wars.  I have
hopes that one of these days Logitech will implement their enhancements as
an OS/2 available service.  They have a nice Win pop-up that lets you
decide what the middle button does.  I got used to it and miss it's
features.  I understand there's a shareware product called Rodent that can
provide somewhat similar services but haven't done much/anything with it.

One of our User Group Gurus is from Amoco and John says that the only
decent trackball is another brand.  Can't recall the make at the moment
but it a big brown beast with each side being one of the buttons.  It has
a very large ball in the center.  I used one at a fellows house and found
it rough and awkward compared to the Logitech--but, the encounter was
brief.

Ken Prevo
**********************************************************************

Thanks Ken, Gordon, and all who contributed to my effort.  After
numerous BRS reboots, CHKDSK must have put something in the right
place.  I belive that all the setting in config.sys and all hardware
is identical to when I first loaded ver 2.1.  The trackball started
working as it should, and hasn't quit yet.  It still bothers me that
if I didn't "fix it", that sometime it will return to haunt me.  The
total time spent formatting and installing THREE times was probably
about 15 hours.  This does not include the time on this forum, reading
and writing.

Stew Corman from sunny ( +18 inches snow ) Endicott
**********************************************************************


ΓòÉΓòÉΓòÉ 56. Internal Cache Problem ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 I've installed OS/2 2.1 on AMI-BIOS mainboard. I can run OS/2 fine
 when I turn internal cache to be off. But when I turn internal cache
 on I can boot OS/2 and it'll hang in later. I found that when cache on
 OS/2 can run faster than cache off.
  How can I run OS/2 when cache turn on?

 Koson Thambundit
 Bangkok, Thailand.
**********************************************************************

>  when I turn internal cache to be off. But when I turn internal cache
>  on I can boot OS/2 and it'll hang in later. I found that when cache on

While you may have a badly implemented cache on the motherboard, often
failures with the cache enabled actually point to something else that's
doing the failing.  I had this happen to me when I first installed OS/2
and it ended up being slow memory on a card on the ISA Buss.  It had
worked fine under DOS but OS/2 is a lot more efficient and caused it to
fail.  If you have the ability to change the speed of the BUSS in your
hardware, you might try setting that to it's lowest setting.  If not, then
pull all the cards you can from the system and see if the cache works
then.  If not, next step would be to swap memory--OS/2 is very memory
sensitive and "ok" memory under DOS can fail under OS/2.  Different memory
speeds has again become a no-no and can cause the problem you described.

You might also see if there is a write-thru / write-back cache jumper on
your computer and experiment with that.  Write-thru is slower but less
demanding from what I've been told.

Hopefully someone can provide better advise but this should at least
provide you with a starting point for resolving your problem.

Good luck!

Ken Prevo
**********************************************************************

In addition to things Ken mentioned, we had one AMI Bios
machine that required "adjustment" to the SRAM and/or
DRAM wait states (in Bios setup.)  I Don't remember exactly what
was needed, but this was a new machine (WIN clone), so it
_should_ have had the AMI defaults.  If you have no luck, let me
know and I can look at this machine on Monday (USA Monday that is...)

Tim Wuthrich,
The Upjohn Company
**********************************************************************

[Reference to append at 03:02 on 93/12/24 by KOSON at BKKVMCC1 ]

>  I've installed OS/2 2.1 on AMI-BIOS mainboard. I can run OS/2 fine
>  when I turn internal cache to be off. But when I turn internal cache
>  on I can boot OS/2 and it'll hang in later. I found that when cache on
>  OS/2 can run faster than cache off.
>  How can I run OS/2 when cache turn on?
>
>  Koson Thambundit
>  Bangkok, Thailand.
 On my AMI BIOS there is a selection for number of wait-states for the
cache. Have you experimented with WS-1 and WS-2? It also is possible to
specify different cache chips in the setup than are actually installed.
 It also gives address ranges that cache can be disable for. This is
intended for things like memory mapped I/O, e.g. token-ring cards.
If any such cards are present then their range should be mapped out.
The range values could also be used in a trial-and-error search for
bad chips.
(Isn't modern hardware wonderful?)

->Rich Corbett; Mgr. Sys.; ABC Liquors, Inc., Orlando, FL   (NASPA:CORBRIC7)
**********************************************************************

The wait states are for external cache, But verify that there are shadowram is
disable, that is the shadowing of ram, and the you use 3-2-2-2 wait state for t
he cache settings.  If this workes, change it it 3-1-1-1, or 2-1-1-1, or 1 over
all, depending upon the AMI Bios configuration.

John E Quigley II  Standard Register Corp  -- IS -- [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 57. Install with 5.25 diskette in B: ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

SInce the days of the 2.0 beta we have had the people who bought 3.5
diskettes when that was there B: drive and the INS21 setups were created
to allow them to install without changing drive cables.  Recently I have
see several people on other boards who have 5.25 diskettes and that is
there B: drive, does anyone know how to install with 5.25 diskettes when
the 5.25 drive is B: not A:?

Jack Hiatt
MARC-Life Atlanta Ga.
Team OS/2
The International Phoenix Alliance
**********************************************************************


ΓòÉΓòÉΓòÉ 58. OS/2 2.1 Install Hangs on Disk 1 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Hello all!  Hope everyone had a nice holiday.  Before embarking on
mine, I was attempting to install OS/2 2.1 on an EduQuest Model 50.
The install process locked on disk 1, after receiving the OS/2
graphic logo and switching back to text mode.  The drive lights
illuminate briefly, then go out and the system locks.  The system
unit has 8 megs of RAM and an ATI video board (standard in that model).
I've tried:
 1) Three different copies of OS/2 2.1, two of which were the GA code,
  one was OS/2 for Windows.  All three came up with the same result.
 2) The APAR that suggests moving the OS/2 files around on disk 1
  (sorry, the number escapes me).
 3) Moving around the SIMMs on the motherboard, on the odd chance that
  one would not be seated properly.
None of these seem to affect the problem in the slightest way.  I
suspect a hardware problem of some sort, but the CE's won't take any
action until I can come up with something more concrete.  Has this
sort of thing happened to anyone else?  How can I track down the problem?
Any help *at all* would be appreciated.  Thanks!
| Bad system board - it was replaced and all is well.  Thanks to
| those who responded!

Jerry Steinhauer - EduQuest SE, Madison WI - 608/273-5269 or t/l 744-5269
      X$1JAST at CHGVMIC1 or [e-mail]
**********************************************************************


ΓòÉΓòÉΓòÉ 59. SYS1201 error in CONFIG.SYS. Problem loading VMOUSE.SYS. No ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

mouse support in WPS.
  This is verrrrry agrevating... I am installing OS24W and the above
occurs. I get all the way through the installation using the mouse.
I click OK for the final time to reboot and access the newly
installed system. After the OS/2 logo appears, I get the error message
SYS1201 device driver did not install. The error points to a line in
my CONFIG.SYS for VMOUSE.SYS. My debug path.......

1. The directory pointed to contains VMOUSE.SYS.
2. The mouse is indeed plugged into the correct COM port.
3. The mouse is a noname MS compatible mouse, worked with Windows.
4. I tried installing the Logitech, PCMouse, and the generic serial
  pointing device mouse drivers from the selective install. No good.
5. I moved the VMOUSE device statement to the first one in my
  CONFIG.SYS. No good.
6. I opened a DOS window and started a DOS mouse driver successfully.

I noticed that other people have reported the same problem... I wonder
if they just gave-up, or got a resolution. I'll try OS/2 support
tomorrow... 1-800-992-4777. I hope they have the answer, but I would
appreciate any thoughts and replies here.

Mark
**********************************************************************

This may be the same problem as with 2.1. If it is, it really means
the new MOUSE.SYS (not VMOUSE) was not picked up correctly.
Look at the MOUSE.SYS that is pointed at by CONFIG.SYS and compare
it with the one on the install diskettes (it is on the Install
diskette or #1, I believe). If they are different, copy the one from
diskette on top of the one on the hard disk. rebbot and see if that
helps.
               Mel Hallerman
**********************************************************************

[Reference to append at 01:42 on 93/12/27 by MICKEY at RALYDPD ]

Yes, we do have a 1201.fax in OS/2 Support for this problem.....
**********************************************************************


ΓòÉΓòÉΓòÉ 60. Max. Files Open using CID ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Ref: Append at01:47:09 on 92/04/08 GMT (by HOPKINS at AUSVM8)


To:   Anyone
From:  Len Kutz

 I have got a CID Server up and working just fine, except for
the max. files open.  According to the CIDSETUP documentation
only 100 files can be open at a time.  Each CID install is opening
20 to 30 files, and this only allows 3 users to connect at a
time.  I have the max. users set at 10, but max. files can only
be 100.  Are my users using to many files?  Can I set a max.
of more than 100 files?  en at a time.  Each CID install is opening
20 to 30 files, and this only allows 3 users to connect at a
tim
    Len Kutz - American General
**********************************************************************

The maximum number of clients that can be connected concurrently
is 100 and the maximum number of files that can be open at
one time via the SRVIFS redirector is 9999. Change the
MAXFILES= parameter to 1000 in the .INI file, restart the
SERVICE.EXE, and give it a whirl.

Steve W. Davis  IBM Southwestern Area Applied Technolgy Ctr Dallas
**********************************************************************

Steve,

 After writting the append I found my problem and got it working
just fine.  The CIDINSTALL program I got from IBMLINK would
only allow Max. files of 100.  Maybe I have an older version
of the CIDINSTALL or just misunderstood the help files that
came with it.

 Also, now that I have the CID working, is there a way to have
peer-to-peer services and CID running at the same time?  I would
like this so I can update the CID machine without actually having
sit in front of it.  I have LAN Requester 3.0 installed, but
when I start the requester the CID can no longer be accessed.

Len Kutz - American General
**********************************************************************

Len, there shoudl be no problem runnign LR30 on your CID machine.  We
run our CID service on our least used LS30 Server.  It is likely that
you do not have enough resources defined in LAPS for both product to
run together.  Have a look at what you have set up and what you need.

Julian Swales
ISM - Information Systems Management Corp. CAWSTSDT @ IBMMAIL
Regina, SK, Canada, S4S 7H1, Phone #:[phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 61. SYS1201 error. Problem loading VMOUSE.SYS. No Mouse. ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

  RELIEF!!!!!!!! The suggestion to copy the MOUSE.SYS from the install
disks to the C:\OS2 directory worked! I also deleted the old MOUSE.SYS
from C:\ . A side note... I replaced my noname mouse with a Logitech
type-M mouse, and had the same failure as before.

Thanks Mel ! Good Job !

Mark

PS.. Some 'cookies' back to your reader....
**********************************************************************


ΓòÉΓòÉΓòÉ 62. Internal Processing Error on Installtion ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am getting the same exact error after installing OS/2 2.1 for Windows
on my 486sx25 w/ 8mb RAM, std VGA, Maxtor 345mb IDE drive, Adaptec
1542cf scsi controller w/ bios disabled, and a PIONEER DRM-600 CDROM
changer.  As soon as I change the basedev=AHA154x.add by adding the /ET
paramter as stated on page 365 of Using the Operating System, when I
reboot to make the change take affect I get:

TRAP-D
Internal Processing Error at ##0160:FFF5FBD5-000D:9BD5
60000,9084
48600b4
Internal revision 6.514  93/04/12

Any suggestions as to what's causing the problem and how to fix it?

Thinking it may be caused by relative statement loading in config.sys
(how's that for a fancy way of saying I didn't have a clue so I fiddled with
 the one thing I knew how to touch.  -- I did save backups as I made changes)
but half a dozen attempts all gave me the same error.  And without that parm
I get a drive not ready error whenever I try to access the DRM-600, making
it unusable.  (I am only trying to access data files.  This is a BBS.)

Leo Tornow - Northwest Pipeline Corp.
**********************************************************************

>but half a dozen attempts all gave me the same error.  And without that parm
>I get a drive not ready error whenever I try to access the DRM-600, making
>it unusable.  (I am only trying to access data files.  This is a BBS.)

I understand the ROMs on the 600 have been through several updates to make
them more standard (ie usable with OS/2)  so you might want to check with
them on your revision level...

Ken Prevo
**********************************************************************

[Reference to append at 15:10 on 93/12/28 by IL04688 at HONE82 ]

IBM told me that this TRAP-D indicates a hardware error.  Funny, I
had never encountered this trap on boot before, and if I took of the /ET
parm from the BASEDEV=AHA154X.ADD /ET statement in config.sys
I could boot with no problems.

But I stumbled into a fix for this problem with my Adaptec 1542cf scsi
controller and my Pioneer DRM-600 CDROM changer.

IBM level-2 support gave me specific settings for the Adaptec controller,
which you have to enable the BIOS and then press Ctrl-A when prompted
in order to use the Adaptec Select-SCSI utility.  IBM also suggested I
call the Adaptec BBS at 408.945.7727 and download their latest driver.

I downloaded AHA154X.exe dated 7-29-93, but when it un-archives itself
the driver is identical to the AHA154X.ADD that OS/2 2.1 for Windows
installed.  I ran COMP on them and sure enough, the files are identical.

The only IBM suggestion that was not already a default on my adapter was
to DISABLE PARITY CHECKING.  Now I could use the required /ET parm
with the BASEDEV=AHA154X.ADD /ET  without the "hardware" Trap-D
error.

But I was still getting icons for all the CDROM disks in the drives folder
and a "Drive x: not ready" error if I tried to access any of the CDROM
disks.

So I called the vendor back that had sold me the drive and controller,
thinking I would buy the 8-bit Future Domain kit.  (Especially since the
Adaptec utility showed the adapter at SCSI address 7, and the Pioneer
DRM-600 grabbing all of the SCSI addresses from 0 thru 6.  -- I thought
I would pre-position this system for a future fast SCSI-2 hardfile by
putting the bucks into a first-rate SCSI adapter up front.)

But the vendor had seen this problem many times before.  This PIONEER
design requires that you load all of the CDROM disks in the magazine
upside down.  When I turned them over so that the data side is up and
the label side is down, IT WORKS !!

Hope this append helps the next guy down this twisted path.

One last thing,  the PC hangs if I select DOS from the Boot Manager
menu with the Adaptec BIOS enabled.  I set the card switches to disable
the BIOS after making that one change regarding parity, and it boots
fine with OS/2 or DOS.

Leo Tornow - Northwest Pipeline Corp.
**********************************************************************


ΓòÉΓòÉΓòÉ 63. how do i erase EA DATA. SF? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have tried to install OS/2 and it failed, and now I am trying to clean
up its tracks. Can someone tell me how to delete the extended attributes
file, EA DATA.  SF?  The blanks in the filename are giving me fits.

(FWIW, I checked OS2BEGIN ANSWERS for an answer, found the question, but
the answer was "it is strongly suggested you leave this file alone".
Please just answer the question!)

Scott Symes
**********************************************************************

1/. ATTRIB EA?DATA.?SF -R -S -H
2/. ERASE EA?DATA.?SF

Don Hills  IBM New Zealand
**********************************************************************

Thank you very much, Don!  I finally did a ATTRIB EA*.* -S -H -R, and
DEL EA*.* since I didn't have any other filenames that matched that
pattern, but I forgot all about "?" to match single chars.  Thanks again.

Scott Symes
**********************************************************************

[Reference to append at 21:50 on 93/12/29 by SYMES at MANVM1 ]

>I have tried to install OS/2 and it failed, and now I am trying to clean
>up its tracks. Can someone tell me how to delete the extended attributes
>file, EA DATA.  SF?  The blanks in the filename are giving me fits.

EA*.* works for me...

Ken Prevo
**********************************************************************

I too am trying to obliterate OS/2 from my machine....after removing
the EA DATA file, I cleaned out everything I associate with OS/2,
tried to reboot, but the machine comes up with two lines after the
AMI BIOS screen:
OS/2 !! SYS01475
OS/2 !! SYS02027
the system is DEAD.....what have I missed?  thanks in advance

Stew Corman from sunny Endicott
**********************************************************************

[Reference to append at 21:17 on 93/12/29 by DONHILLS at SYDVM1 ]

and boot from an OS/2 disk and run the Chkdsk /f on that drive. (twice)

Geza Szivos <TEAM-OS2> IBMMail(CANOVXVV) The Phoenix Alliance
(403)-290-6583 Fax [phone]
**********************************************************************

[Reference to append at 14:46 on 93/12/30 by SCORMAN at ENDVM1 ]

This is from the Boot sector.
To go back to DOS , boot from DOS and do 'SYS a: c:' to make
it DOS bootable.
To fix it under OS2, use the SysinstX firom your install disk.

Geza Szivos <TEAM-OS2> IBMMail(CANOVXVV) The Phoenix Alliance
(403)-290-6583 Fax [phone]
**********************************************************************

Thanks, Geza
I hadn't even had time to have lunch, before your response and fix
worked!  Will try to load OS/2 2.1 when I get the latest disks....
I think mine may have gotten corrupted and are giving me bad installs.

Stew Corman from sunny <brrrr> Endicott
**********************************************************************

[Reference to append at 14:46 on 93/12/30 by SCORMAN at ENDVM1 ]

Try booting a DOS diskette and doing a SYS C:, or using the "make a disk
bootable" option on Norton.  (The problem is that the boot code on your disk
is now looking for OS/2, not DOS.)

John W. Kennedy -- Hoechst Celanese -- The OS/2 Hobbit\Team-OS/2
**********************************************************************

[Reference to append at 14:46 on 93/12/30 by SCORMAN at ENDVM1 ]

>the EA DATA file, I cleaned out everything I associate with OS/2,
>tried to reboot, but the machine comes up with two lines after the
>AMI BIOS screen:
>OS/2 !! SYS01475
>OS/2 !! SYS02027
The info for these can be found in the Appendix of the OS/2 Installation
Guide, if you want to see the full description.

The modified boot can't find OS/2.  You need to SYS C: from a floppy or
copy the stored boot record to track zero--but, you probably already
deleted it...If you have a Norton Recover Disk or such, they should also
be able to replace the boot record from their menu.

Ken Prevo
**********************************************************************

[Reference to append at 21:50 on 93/12/29 by SYMES at MANVM1 ]

Scott,
How are you deleteing the tracks?  If using DOS and you plan to reinstall
make sure you run an OS/2 CHKDSK against the drives involved before
starting. Failing to do so can cause major problems on the reinstall

Jack Hiatt
MARC-Life Atlanta Ga.
Team OS/2
The International Phoenix Alliance
**********************************************************************


ΓòÉΓòÉΓòÉ 64. OS/2 2.1 upgrade with boot mgr already installed and more ?s ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I already have boot manager installed on a 1 meg partition with OS/2
2.0 on a 99 meg partition and DOS 5 on a 50 meg partition. I think I
would like to upgrade the OS/2 2.0 to 2.1. How do I accomplish this
upgrade? I also have Extended Services and Netware for OS/2 2.0. Will
I need to upgrade these pieces too? I'm not finding documentation to
answer these questions.

George
**********************************************************************

It's been a while since I did an install but I believe the readme
has info regarding ES and I would suggest that you upgrade the Netware
requester to V2.01 + R201FX (available on OS2BBS) ...

Keith A. Blake  (The OS/2 Mole) V: [phone] (USPGC9GC/IBMMAIL)
**********************************************************************

I went ahead and upgraded the 2.0 partition that contained Extended Services(co
mmunications Mgr & Database Mgr) and also Netware requestor for OS/2 that came
with Netware 3.1.1. I had to modify config.sys to get the requestor to function
 again after the install but I had to fully reinstall Extended Services (ESINST
) to get CommMgr to work.

Thanks, George
**********************************************************************


ΓòÉΓòÉΓòÉ 65. Creating desktop objects during CID install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Is there a simple way during a CID install to add objects to a user's desktop?
Do the .INI files get created during the installation of OS/2 or during
the first boot? If during the first boot, could items be added to the INI.RC
file or does an .RC need to be created and then use MAKEINI to update the
new OS2.INI file?

Jim Sauber, MN Mutual
**********************************************************************


ΓòÉΓòÉΓòÉ 66. OS/2 2.1 Shutdown Problem (NLS German) ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

How does one get these fixes?

I will also call our SE, which is probably the way; but since
I'm here, I thought I'd ask. _ф8Л╥
I have certainly had this problem with ShutDown.

TschueB.
**********************************************************************


ΓòÉΓòÉΓòÉ 67. OS/2 1.3 program work under OS/2 2.1? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I  have a Zeos 486DX-66 with 16 MB RAM and a large HD.  If I install
OS/2 2.1, will I be able to run OS/2 1.3 programs?

Gerald K. McAuliffe
**********************************************************************

The OS/2 1.3 programs should run just fine unless they rely upon
some 1.3 internals. There are a number of older 16 bit PM apps I
have used under OS/2 2.x.  OS/2's game is _compatability_ <g>.

Tim Wuthrich, The Upjohn Company
**********************************************************************

[Reference to append at 19:17 on 94/01/01 by WZ01218 at OS2CUST ]

IBM states we support the 1.3 PM apps, if it does not work call
Support. All my 1.3 apps seem to work fine....
**********************************************************************


ΓòÉΓòÉΓòÉ 68. Install Problem ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I attempted to upgrade a system with a Maxtor 540meg Scsi drive and Future
Domain 1670 adapter.  A Toshiba 3301 was also on the 1670.  Also in the
system were 2 Seagate 210meg IDE drives.  The installation progresses to
the point of the reboot after all the files are transfered from the CD
several screens of file not found flash by and the system is stopped.
Rebooting from the install diskette shows the install partition looks good
but the files listed in the last screen of error msgs are not present.

Hardware
386/25 noname clone
1990 AMI Bios
Irwin 250 Tape on FC10 controller
3.5 diskette
5.25 diskette
2 Seagate 210meg IDE drives
16meg Memory

The above with Adaptec1510 and Toshiba 3301 works fine.

Replaced 1510 with the FD 1670 and added Maxtor Scsi drive.  Attempted to
reinstall as drive letters had changed and end up with completely unusable
system.

Thoughts & Ideas??????

Jack Hiatt
MARC-Life
<Team OS/2>
T.I.P.A.

Jack Hiatt
MARC-Life
<Team OS/2>
T.I.P.A.
**********************************************************************

Jack:
 Is this a pop quiz to see how many of us think we know as much as you?
OK, I'll byte (and cringe waiting for the replies.)
1) The 1991 AMI BIOS is recomended (but that's probably why you mention 1990).
2) There was that bug when memory hovered right around 16M, and the cure was
to take some out (or put a lot more in.)

->Rich Corbett; Mgr. Sys.; ABC Liquors, Inc., Orlando, FL   (NASPA:CORBRIC7)
**********************************************************************

Rich,
Wish it was a pop quiz.  Will have to double check the bios. Guess I will
contact Washburn tomorrow.  Had forgotten just what date was recommended,
I've run all the 2.0 betas on this old hunk of junk.

Will have to play with it some more later this week.  Can't afford to
trash my system again right now.

Jack Hiatt
MARC-Life
<Team OS/2>
T.I.P.A.
**********************************************************************


ΓòÉΓòÉΓòÉ 69. Reboot occurs during install from CD-ROM ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am having trouble installing OS/2 from CD-ROM.  I am using the Sound
Blaster Multi-CD and the Mitsumi FX001D CD-ROM.  I have installed the MITFIX
to the diskette one, but it does not help.  After booting and going to the
second diskette, the machine reboots.  I do not believe it is even getting
to the point of loading the device driver for the CD-ROM because I added the
/V to the BASEDEV statement and never see anything.  I use this card and drive
in DOS all the time and do not have a problem with either.  Can anyone help?
By the way, the OS/2 is OS/2 2.1 on CD-ROM (upgrade).

Craig
**********************************************************************

I have found the problem that was causing my reboot from CD-ROM installation.
Apparently, the diskette 1 was bad.  After making another copy of it, the
installation proceeded just fine.  I decided to try this after I heard some
strange noises preceeding the reboot.  Strange that this would cause a
cold boot, but it was.

Craig
**********************************************************************


ΓòÉΓòÉΓòÉ 70. OS2 INSTALLATION into GATEWAY NoteBook PC ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

To; Anyone

KOJI KITAMURA  Y13867 at YSUVM1  (IBM-Japan, YASU)

 Does someone knows how to install OS2 ver 2.1 into Gateway
Notebbok PC?  I can see from Forun that IBM Thinkpad 700 series
has been installed OS2 with changing BIOS, but I am not sure
other companies notebook PC is also applicable.
Most of the problem is memory address conflict and I want to know
the pre-conditioning before installation, like power management
switch as off, and other necessary conditions.
 My system has 8Mbyte memory with 486-33 CPU with 170Mbyte hard
disk with VGA 256 color support by Cirrus Logic controller.
Core logic is PT86C268 Pico Power and BIOS 128K.
**********************************************************************


ΓòÉΓòÉΓòÉ 71. EARLYUSEREXIT problems ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I'm doing some CID installs and trying to use the EARLYUSEREXIT
keyword. It doesn't seem to be working. The USEREXIT works fine. It should
be running a simple .cmd file that has one line in it (a PAUSE command).
This same function works fine with USEREXIT.

Has anyone had trouble with this or is it working fine for others?

Thank you in advance

Jim Sauber, MN Mutual
**********************************************************************


ΓòÉΓòÉΓòÉ 72. OS2 and boot manager installation on second hard drive ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have a multimedia value-point that I added a second hard drive to
install OS/2.  The first hard drive exists as configured from IBM
Direct - a single 340 MB startable FAT partition with dos/windows
installed.  I want to install boot manager and os/2 on the second
drive and set the bios to boot from the second drive.

I don't seem to be able to do this.  I'm installing OS/2 from CDROM.
The floppies boot okay and both hard disks and the existing partitions
can be seen.  However, all I can do in FDISK is create a partition and
delete a partition.  All other options are in 'blue' and unselectable.
This is true even after I create partitions and reboot.  I have never
seen the Install Boot Manager selectable.  Nor can I make a partition
on the second drive installable. Is there a restriction that boot
manager has to be installed on the first drive ?  Any suggestions ?

imaging away / M. Flick Flickner, IBM Almaden Research Center, San Jose, CA
VNET/BITNET: FLICK at ALMADEN  Internet: [e-mail]
**********************************************************************

Boot manager must be installed on the PRIMARY drive.  If there is no free
space on that drive you will not see the option to install BootManager.

Jack Hiatt
Marc-Life
Atlanta Ga
<Team OS/2>
The International Phoenix Alliance
**********************************************************************

I am going to offer a completely untested (to my knowledge) and non
warranted idea.  During my playing around with a second drive, I kept
getting undesirable drive mappings when I moved the new drive from
primary to secondary.  The first partition (primary) on the second drive
would end up as drive 'D:' instead of the second (extended) partition on
the primary drive.  I finally discovered that if I made all the
partitions on the second drive extended partitions, my second partition
on the primary drive would remain drive D:. Since then I have seen the
documentation that explains how this mapping is done and I understand
what was happening.  Later when I moved the second drive to a new PC, I
was real suprised when I was able the use the drive WITHOUT any
'primary' partitions.  I had left some unused space for booting OS/2 as
a utility (faster than diskettes) so I was able to repartition this area
to add boot manager.

Anyway, what might work is to put your new drive in the primary position
but only define extended partitions on it.  Then your primary partition
on the second hard drive, should come up as drive C:.  This way you can
put boot manager on the new drive and not have to partition the older
drive.  I know from experience, moving/reallocatin partitions is a
PAINFUL process.  This is a little unorthdox, but it might just work.

Let me know if you try this and whether or not it works.  It is a truely
a broadside into the dark.

Alan Arnett, Fina, Dallas, TX, [phone]
**********************************************************************

[Reference to append at 12:52 on 94/01/07 by TPA0003 at HONE81 ]

Can someone explain why boot manager needs to be on the jumpered
primary DRIVE ?  The valuepoint BIOS allows the user to select the
order of drives to boot from ( ie floppy A, drive 1, drive 2,
network...).  Is there anyway that I could use the bios to allow me to
install boot manager on the second drive without rejumpering ?  When I
set the bios to boot from drive 2 before drive 1 boot manager still
wasn't enabled.

I don't look forward to tearing the valuepoint apart if I have to
change the drive jumpers. Thing are very tight in the bays with 2 hard
drive, 2 floppies and a cd-rom...

imaging away / M. Flick Flickner, IBM Almaden Research Center, San Jose, CA
VNET/BITNET: FLICK at ALMADEN  Internet: [e-mail]
**********************************************************************

Are you installing OS/2 MR1 Beta?

If you are, use FDISK.EXE to install Boot Manager on physical disk two.

Gordon Webster
**********************************************************************

You didn't say how big your new drive is but you could do the following
to set up boot manager.
1) boot from diskette and backup your first drive to your second drive.
2) fdisk r
3) recreate your dos FAT partition on the first drive.  It will be 1Mb
  smaller than original due to the boot manager partition.
4) restore your first drive from your second.
You will now have your original system plus boot manager and you can
now add your second drive's partitions to boot manager. This is just
a fairly high level overview.  If I have missed any steps I am sure
someone will correct me...

Julian Swales
ISM - Information Systems Management Corp. CAWSTSDT @ IBMMAIL
Regina, SK, Canada, S4S 7H1, Phone #:[phone]
**********************************************************************

[Reference to append at 22:22 on 94/01/07 by GWEBSTER at BCRVMPC1 ]

Thanks for all the ideas...  I will look into using the MR1 beta
version if FDISK supports putting boot manager on the second drive.
Is there a CDROM for MR1 beta ?  If so how does one get it ?  Could I
just put FDISK ( and maybe boot manager ) from the beta on the
standard install floppies ?

Alternatively, I may backup C: to the D drive then repartition C:
(both drives are 340Mb).  A tool that could repartition a disk by
moving blocks/files would be handy.  I would also help if PC-direct
would leave 1 MB unused space when they install dos/windows.

I find it interesting that can't install OS/2 2.1 either.  As stated
in the earlier appends all I can do is create and delete partitions.
I am unable to make the partitions or logical drive installable.
Without an installable partition installing OS/2 is impossible.

imaging away / M. Flick Flickner, IBM Almaden Research Center, San Jose, CA
VNET/BITNET: FLICK at ALMADEN  Internet: [e-mail]
**********************************************************************


ΓòÉΓòÉΓòÉ 73. CID and DOS ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 Is it possible to connect to the CID servers while booted up
under DOS?  Since CID is taking care of our OS/2 installs so
nicely I was wondering about the chances of CID doing the DOS
machines also.  All I would like CID to allow is a connection
from a DOS machine, I can write the rest of the programs for the actual
installs.  Is there a SRVATTCH version for DOS? nstalls so
nicely I was wondering about the chances of CID doing the DOS
machines also.  All I would like CID to allow is a connection
from a D
**********************************************************************


ΓòÉΓòÉΓòÉ 74. Usual installation abuse ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Ref:

Tried to install OS/2 2.1 for Windows CD-ROM over a mostly deleted
OS/2 2.0.  Had the following problems.
 1 - during my attempt to purge 2.0 I couldn't delete os2krnl, os2boot
   etc.  Attempts at changing the attribute got something like
   "Not reset" (sorry, not the exact text)
 2 - get 3 repeats of the message "SYS0318 OSO001.MSG cannot be found"
   on (I think) Diskette 1 (ie: the 2nd diskette).
 3 - after installation, during regular OS/2 boot get the old
   "vmouse.sys on line xx was not installed" message and my mouse is
   dead.
 4 - about a couple hundred EAxxxx.CHK files on my root.

Anybody know what my problems are?  Particularly for items 1 and 2.
I see from reading the forum that others have had the vmouse problem
and that various approaches were used to fix it.  I haven't seen the
definitive problem/solution stated yet, is it known?  For the EAxx.CHK
problem, I saw something similar but with FILExxx.CHK (sp?) files being
generated.  I really don't think I had anything wrong with the disk
before I started installation (I did chkdsk on the drive before and
there was nothing wrong with it: I know someones going to say you didn't
use the /f option but I thought that was only to fix the chains, you
would still see that you had bad chains without the /f).  Thanks.

Dick Van Hall in Owego NY
**********************************************************************

SOunds like you tried to delete OS/2 from DOS, this usually causes the kind
of problems you are describing.  If this is the case, boot from the OS/2
Install Disk, Disk#1, ESC out should go to CD in subdir DISK_1, change
dir ..\DISK_2  run CHKDSK there useing the /F parm.  Delete the files
created and repeat again until the drive is clean.  The file you couldn't
reset attributes on should be able to be changed if you change all
attributes in ONE PASS.

Jack Hiatt
Marc-Life
Atlanta Ga
<Team OS/2>
The International Phoenix Alliance
**********************************************************************


ΓòÉΓòÉΓòÉ 75. CID RebootRequired ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

To:  Anyone
From: Len Kutz

 I'm installing PS/2 Models 70's and DELL 466/ME's using CID.
 After the install completes I get either a blank screen or
a trap error on both types of machines.  From what I've seen
on other appends I have the following setting in the response
file: (Х    ExitOnError = 1
    RebootRequired=0.
Since both types of machines are having the same problem I'm
sure I have done something wrong, but just can't figure out
what. p error on both types of machines.  From what I've seen
on other appends I have the following setting in the response
file: (Х
 After rebooting everything works fine, CID just doesn't end
very gracefully.  Any ideas would be a big help. figure out
what. p error on both types of machines.  From what I've seen
on other appends I have the following setting in the response
file: (Х
    Len Kutz - American General
**********************************************************************


ΓòÉΓòÉΓòÉ 76. CID install using diskettes ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We have used CID to upgrade our office of 150 machines and
found that it worked well over our Token Ring LAN
for OS/2 2.1, LAPS, Lan Server, and DB2/2.  Besides being
much quicker, the other great advantage was that we were
guaranteed of constistent installs over all the stations.
We do have a need to install some remote machines where I
want to take advantage of the response file concept.
Therefore, I am attempting to put the response files and
any necessary system files onto the local machine and define
the source of the images as being the a drive.  I have
removed the SRVIFS from config.sys as the machine will not
have to connect to a code server.  I then modified the
client command file to remove references to the code server.
When SEINST runs, I receive an error indicating the system
could not open a file and it lets me look at the INSTALL.LOG.
It appears from the log that it cannot open the DISK.NUM file
which of course it doesn't have.  I can also tell from the
log that DisketteSource is FALSE, which is probably the root
of my problem.  Does anyone know how to change this as maybe
a parameter to SEINST or RSPINST?

Thanks in advance
Jeff Durnwald
**********************************************************************


ΓòÉΓòÉΓòÉ 77. Return code 906 from RSPINST ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am using LAD/2 to do CID installs. Most have worked fine. On one particular
machine, we are receiving a return code 906 from RSPINST.EXE. This is after
SEINST begins, but before it copies files.

The messages are as follows:
CID0032: X:\EXE\OS2V21\SEINST - Return code from X:\EXE\OS2V21\RSPINST.EXE
was 906
CID00-5: X:\EXE\OS2V21\SEINST - REMOTE_INSTALL_STATE='0',
X:\EXE\OS2V21\SEINST completed with return code 0x1604

Can anyone provide information on what these error codes mean?

Jim Sauber, MN Mutual
**********************************************************************


ΓòÉΓòÉΓòÉ 78. OS/2 SPECIAL EDITION ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Can I install OS/2 Special Edition for Windows on a partition that already has
DOS and Windows installed on it without upsetting Windows?

Dave Harding - State of Oregon
**********************************************************************

This is EXACTLY what the OS/2 for Windows is for.
Go ahead. If anything is NOT working you can go back to REAL DOS/Win31
by selecting the Dual-Boot Icon.

Geza Szivos <TEAM-OS2> IBMMail(CANOVXVV) The Phoenix Alliance
(403)-290-6583 Fax [phone]
**********************************************************************

[Reference to append at 18:32 on 94/01/12 by ORMV003 at OS2CUST ]

Yes.....
**********************************************************************


ΓòÉΓòÉΓòÉ 79. Anybody here?? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Do you get your answer? If not feel free to call me direct 8-443-9677.
**********************************************************************


ΓòÉΓòÉΓòÉ 80. OS/2 install fails on IDE drive ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I just got a new IDE harddisk (Western Digital Caviar IDE 405 meg) and
finally have enough space to install OS/2.  I partitioned my disk up
using the OS/2 install program as:

 1 meg boot manager
 120 meg Primary DOS
 120 meg Logical FAT
 164 meg Logical HPFS

However, when I try to format the HPFS partition from OS/2 install I get
an error.  It asks me to check the log file and when I look there it has
two lines at the end that basically say, "Format failed, fix whatever's
wrong and try again."

So, what do I do?  What is wrong?  I put PC DOS 6.1 on one of the other
partitions and using it I can format the same partition OS/2 won't.  DOS
works great on the new drive...

I have a 486/50 machine with 8 meg memory, AMI BIOS, and an UltraStor
IDE controller.  I completely removed my original drive after I copied
it to the new one and I have all the jumpers and cables hooked up
properly for the new drive.  I set the correct parameters in the BIOS
and ran the IDE controller's configuration program via debug.

- Bill Seurer   Language and Compiler Development    IBM Rochester, MN
 Internet: [e-mail]   America On-Line: [e-mail]
**********************************************************************

I experimented some more with the formatting problem.  After the failure
the "drive in use" light stays on and a CAD reboot hangs (the light
stays on too).  A hard reboot (the button on the front) clears this up.

- Bill Seurer   Language and Compiler Development    IBM Rochester, MN
 Internet: [e-mail]   America On-Line: [e-mail]
**********************************************************************


ΓòÉΓòÉΓòÉ 81. CID Client Prompt ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I should know this but....  How do you supply the Client name to the
CID process and avoid the prompt?  We are finalizing an unattended
Cid process from a seed partition and this is one of the last
hurdles? That and coming up with a process to reboot from the maint
partition connect to the code server and execute some "copies" to the
new C: drive automaticly after the last pass?  Any comments or suggestions
accepted.

Brian K. Spears Konica Business Machines U.S.A., INC
**********************************************************************

If you're using THINIFS to add the SRVIFS stuff to your
requester, try specifying the '/REQ:*' parameter.  This will
generate a client name without prompting.  In your CID process
you could use DEFAULT.CMD instead of clientname.CMD for the
LCU command file.  If you do this and are using CASINSTL, be
sure to specify '/D' on the CASINSTL command so that it will
use DEFAULT.CMD if the clientname.CMD file is not found.

Hope this helps...

Bill Parrill
**********************************************************************


ΓòÉΓòÉΓòÉ 82. 8514/a Install Problems.... ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

OK, whats the secret handshake??  Someone at work has a model 80 with a 8514/A
adapter and it was only running in VGA Resolution.  He complained about it and
(being a nice guy) I offered to install the high resolution drivers for it. No
big deal right?  Run DSPINSTL and select 8514?  NOT!  Ok, run selective install
and select 8514! NOT!  Ok, OK, run a minimal install and install 8514.  NOT!
OK,OK,OK, Run a FULL install and Install 8514. NOT!  Alright, Run a full instal
 and don't migrate ANYTHING!  NOT!  Ok, it's corrupted INI files, run Makeini
for system and user files. NOT!

So I've come to the conclusion there is more to this than I realize.  The
screen I end up looking at is in high resolution but the "interlace" is wrong -
 It looks like only every second scan line is there and the colours are all
wrong.  Seeing as I have hopelessly broken his system (yeah, I made backups)
can someone PLEASE let me know the secret handshake QUICKLY!

Gareth "Its too late to think any more toonight" Jones
ISM - Information Systems Management Regina Sk Can.
[phone] TeamOS/2, OS/2 Ambassador & Generally Nice Guy
**********************************************************************

>So I've come to the conclusion there is more to this than I realize.  The

No S--- Shurlock...yeah, we all been there...<g>

>screen I end up looking at is in high resolution but the "interlace"
is wrong - > It looks like only every second scan line is there and the colours are all
>wrong.  Seeing as I have hopelessly broken his system (yeah, I made backups)

Are you sure he has an SVGA capable monitor?  Sounds like its a fixed
scan,  VGA only beastie...

Ken Prevo
**********************************************************************

[Reference to append at 04:11 on 94/01/20 by XXWCBS03 at TORVMCOP ]

Does the 8514/A have the extra 512KB of RAM, for a total of 1MB?

John W. Kennedy -- Hoechst Celanese -- The OS/2 Hobbit\Team-OS/2
**********************************************************************

The symptoms as described fit exactly what I saw when I attempted to
use an 8514/A with only 512K (actually, the expansion memory was
installed but was defective and the memory size jumper had been moved
to the 512K position).

John, you must have a "brain the size of a planet" to remember all these
things... (grin)

Don Hills  IBM New Zealand
**********************************************************************

The card has 1 MB of memory and worked under 2.0 (or so says the user)
The monitor is a 8514 which should (I believe) work in the higher resolutions

I will check this all out though.  Any other Ideas??  I'm about to give up

Gareth "Appending from home due to the flu" Jones
ISM - Information Systems Management Regina Sk Can.
[phone] TeamOS/2, OS/2 Ambassador & Generally Nice Guy
**********************************************************************

Granted, the user may not have had a problem at 2.0, but was he using
640x480 or 1024x768?
I've been back to your original append for another look, and you say that
"every second scan line appears to be missing". I assume by this you
mean the horizontal lines. The effect of having only 512K is that every
second *vertical* line appears to be missing, and the colours look odd.
So, if your problem is the *horizontal* lines, you have some other
problem (it could still be a defective 8514/A adapter). Try running the
8514/A tests off the reference diskette (use Ctrl-A to get into the
advanced diagnostics after booting the reference diskette to its main
menu). If it runs OK in 1024x768x256 then maybe it is an OS/2 problem.
Let us know what you find.

Don Hills   IBM New Zealand
**********************************************************************

OK, here's the latest scoop(?) The user insists the card has 1 MB but on
running the diagnostics I only get 1024x768 NOT 1024x768x256.  I assume I'm
supposed to if this card really had 1MB.  By looking at the card it has OPEN
DIP Sockets (10 of em) that look like they would take RAM so I am assuming
this is where the missing ram would go.

Is there any way of getting this card to display in 1024x768x16?  I think
this what what he was running it in under 2.0.  I can't find anything to
change!

Sorry for the delay in replying(not as sorry as my user) but I got knocked
out by some flu bug and took an unexpected 4 day holiday.

Gareth "Maxin and relaxin with a fab fever" Jones
ISM - Information Systems Management Regina Sk Can.
[phone] TeamOS/2, OS/2 Ambassador & Generally Nice Guy
**********************************************************************

Yeah, if those sockets are empty, the thing doesn't have the full 1MB.

To the best of my knowlege, OS/2 does not include support of a 512KB 8514/A
in 1024*768*16 mode.  (It is my understanding that the nature of the board is
such that it would require an entirely separate driver.)  To get 1024*768, you
must install the missing 512KB, and that's going to be difficult now, because
the upgrade package has been discontinued.  (The good news is that the street
price was down to petty-cash levels.)

John W. Kennedy -- Hoechst Celanese -- The OS/2 Hobbit\Team-OS/2
**********************************************************************

Thanks to everyone for your help!  I'll pass on the news to the User and
let him decide what he wants to do.

Gareth "I Love this place!" Jones
ISM - Information Systems Management Regina Sk Can.
[phone] TeamOS/2, OS/2 Ambassador & Generally Nice Guy
**********************************************************************


ΓòÉΓòÉΓòÉ 83. FDISK and One Large OS/2 Partition (4GB) ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Customer has a brand new 9595A that I really need to get up and
running fast, so your help is needed!

They have four 1GB drives that they want to run as one large primary boot
partition under OS/2 2.1, configured as RAID 0 in the RAID utility.
We got a workaround that allowed FDISK to see the 4GB partion but
unfortunately that partition cannot be marked as "installable" by OS/2.

The customer is not willing to split the partition in one small
partition for OS/2 and one large partition for apps and data.
We need a very quick answer for this problem.

Please append here or directly at WID at CHVM1.

Many thanks in advance.

Andre Widmer  IBM Switzerland
**********************************************************************

Andre,
The thing to do here is to really point out that it can a whole lot more
convient in a number of ways to keep the OS separated from the data if
at all possible.  You might even want to try to sell them on creating
two <100 meg partitions for the OS for safeties sake.  This would allow
them as later releases are made available to look at the upgrades in far
easier and safer manner, with a built it fall back using BootManager.
We configure all our servers and machines with large disks with at least
two partitions for OS usage.

Jack Hiatt
Marc-Life
Atlanta Ga
<Team OS/2>
The International Phoenix Alliance
**********************************************************************

[Reference to append at 06:30 on 94/01/20 by 84894838 at EHONE ]

As far as I can remember, the LS 3.0 Advanced has this feature.
Select the first HD, install OS/2 + LS 3.0 Adv. and THEN you can manipula
te with the partitions. One of the new feature was in the LS 2.0 --> LS 3
upgrade, that the boot (only in this case) partition can be mirrored.

By the way, Jack is right, get a (small 120-240) HD WITH boot manager
as your first HD. fixes, repairs are MUCH easier.

(I have 2 identical primary partition (C:) just in case it get corrupted.
)

Geza Szivos <TEAM-OS2> IBMMail(CANOVXVV) The Phoenix Alliance
(403)-290-6583 Fax [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 84. THINKPAD 750 AND EXTERNAL MOUSE ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have Thinkpad 750 with  OS/2 2.1. If I like use it with IBM PS/2
mouse I have problem with the mouse buttons.  If I try use them
they works only sometimes.  I can use the Trackpoint buttons when
the mouse is connected to the computer.

How I can use the mouse buttons ?

Timo

This append was created on the External IBMLink system by
Oy Tietokonepalvelu
**********************************************************************


ΓòÉΓòÉΓòÉ 85. How to change Display XGA -> VGA on OS/2 2.1 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I asked:
>partition!).  I will post the procedure later.  We can set the ThinkPad's
>built-in display to 16 color VGA with the above statement, but would like
>to set it to 256 color VGA instead.  What should we use in place of
>"/pk:VGA" to set up the ThinkPad 700C/720C display for 256 colors?

Debra responded:
>   Instead of passing in VGA as the primary display value, pass in
>SVGA.  Plus, there is an additional paramater you will need to send
>in, "mc:0"
>For example:
>
>c:\os2\install\rspdspi /pk:svga /sk:none /mc:0 /s:a:\ /t:c:

Debra,

Sorry for not responding earlier, but the person with the ThinkPad
didn't feed back the results of your suggestion until I asked
today.  The '/pk:svga' and '/mc:0' doesn't seem to change the
ThinkPad 700C to 256 colors (still only 16).  Is there something
else we need to supply?

Thanks.

Ken Singer, Shell Oil, Houston
**********************************************************************

I think I have cracked the secret code used for display installation (it
must be secret, because no one from IBM has responded to my referenced
append :-(( ).  Here is what I have decoded:

There are two main pieces to the puzzle:  (1) the *.DSC files in
\OS2\INSTALL; and (2) the *.DSP files on the DISP 1 and DISP 2 installation
diskettes.  Additionally, the DSPINSTL.LOG file in \OS2\INSTALL is the
Rosetta Stone (magic decoder ring).  All the files are editable ASCII
text files.

Apparently DSPINSTL builds its Display/Adapter selection list (box) from
the .DSC files; each list box line represents a DSC file.  The SVGA DSC
files are documented with in-line comments -- following is the PSSPDW.DSC
file (used for the ThinkPad 700C/720C):

---------------------------------cut here-------------------------------
* Title
"IBM VGA 256c "

* Action routine DLL
"SVGAINST.DLL"

* Type key
"SVGA"

* # additional parameters specific to SVGA
"1"

* Additional parameter (Chipset manufacturer = 6 for IBM speedway )
"6"

* # of chain elements
"3"

* chain element = key, general prompt, diskette prompt, vol label, resolution

* Configuration chain element - key set set by SVGA.DLL (eg, CXXXxYYYxCCC)
""
* General prompt
"IBM VGA 256c "
* diskette prompt
"Display Driver Diskette 1"
* volume label
"DISP 1"
* no resolution for configuration
""

* 1 more resolution chain elements follow

"SP640x480x256"
""
"Display Driver Diskette 2"
"DISP 2"
"640x480x256 512K"

"SP640x480x256A"
""
"Display Driver Diskette 2"
"DISP 2"
"640x480x256 1.0mb"
---------------------------------cut here-------------------------------

There appear to be three important elements in the .DSC files: (1) the
"Type Key"; (2) the "Chipset manufacturer additional key"; and (3) the
"Configuration Chain element keys".

The RSPDSPI diplay installation program searches through the .DSC files
looking for a "Type Key" specified in the /pk: or /sk: parameter of the
command line.  As there are several ( 8 to be exact) .DSC files with the
Type Key "SVGA", it uses the /mc: parameter to get a secondary match on the
"additional parameter", i.e.  the Chipset manufacturer or "manufacturer
code".  Once RSPDSPI finds a match on the Type Key and manufacturer code,
it then installs the proper files and adds/deletes .INI file and
CONFIG.SYS lines according to "instructions" in the .DSP files on DISP 1
and DISP 2. Again, it determines which .DSP file(s) to use by searching the
.DSP files for a matching configuration chain element key.

I sucessfully installed 256 colors on the ThinkPad using the IBM VGA 256c
selection manually using DSPINSTL.  I then looked at the DSPINSTL.LOG to
see what got installed, and by looking at various .DSP files deduced that
it used the SP480BC.DSP and SP480B.DSP files (after finding that the VGA
and WINVGA entries in the SP480BC.DSP file actually referred to packed
files (bundles) containing several files).  For example, the SP480B.DSP
contains the following:

---------------------------------cut here-------------------------------
:TITLE
640x480x256
:KEY
SP640X480X256

:FILES :MODE=PRIMARY
SV480256.DL_  %BOOTDRIVE%:\OS2\DLL

:FILES :MODE=PRIMARY :MODE=WINDOWS
WSPDSF.DR_  %WINPATH%\SYSTEM
WSPDSSF.DR_  %WINPATH%\SYSTEM
---------------------------------cut here-------------------------------

But the packed SV480256.DL_ file actually contains IBMVGA32.DLL (for
displaying 256 colors in VGA mode).

So, I reasoned that the RSPDSPI command line to install 256 colors for
the ThinkPad should be:

RSPDSPI /pk:SVGA /sk:none /mc:6 /s:c:\ /t:c:

(the DISP_1 and DISP_2 images had been copied to C:)
but, alas, RSPDSPI started and promptly displayed a series of "Message
file not found" messages.  An examination of RSPDSPI.EXE indicated that it
needed the DDE4 (C Set/2) message files, and indeed, when those files were
put in the \OS2\INSTALL directory, dreaded Trap messages were displayed
when the above command line was rerun.

It didn't take too long to see the problem: the null string in the first
Configuration Chain element key was causing the Trap.  After all, without
the string, how was it going to find the SP480BC.DSP file.  So, I replaced
the "" with "CSP640X480X256" (the key in SP480BC.DSP), and VOILA -- RSPDSPI
ran fine and 265 colors were displayed on my ThinkPad after rebooting.

Ken Singer, Shell Oil, Houston
**********************************************************************


ΓòÉΓòÉΓòÉ 86. Missing Fonts with 9517 Monitor ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

During a CID install we choose to let the system set the default display mode
in our response file.  We also choose to have all of the fonts installed. If we
install with a 9517 Monitor we get the driver setup for a 9517 display as
non-interlaced as we want.  However, we only get the System Fonts.
 Other fonts  are not available

Using a Value Point monitor with the same response files gives us 8514
interlaced mode but we do get all of the fonts we want.  Is
there any way to do a CID install and have the 9517 monitor set as the default device in
non-interlaced mode and still get all of the fonts?

Rob Talley - Burlington Northern Railroad - Ft Worth, Texas
**********************************************************************


ΓòÉΓòÉΓòÉ 87. OS/2 and the case of the strangely named diskette ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 I install OS/2 2.1 on a compaq 433i and get through the whole of the
installation process up to the first display diskette. I am them asked
for diskette 'Ы' (that should have been the carot sign - it seems to be
missing from my keyboard). I don't have a diskette with this label, and
if I try and boot at this stage I get to a command prompt but don't have
a desktop. If I try and reboot using ctrl-alt-f1 I am told something
terrible about country.sys.  What can I do??

Regards Jonathan
**********************************************************************


ΓòÉΓòÉΓòÉ 88. Need help using DEC Ln03R Scriptprinter. ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Can anybody help with the correct settings to use a DEC LN03R Scriptprinter?
We need to know the correct switchpack and COM1 settings.  This question got
no response in the printing forum.

PAUL WYLIE  M. BRYCE & ASSOC.
**********************************************************************


ΓòÉΓòÉΓòÉ 89. CID installation of XGA-2 and its resolution ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Hello Esperanza,

We have the same problem, we would like to change the resolution while
doing a CID install. Did you ever find a solution?

Dave Hancock, Advisory Systems Engineer, Publix Super Markets, Inc.
**********************************************************************


ΓòÉΓòÉΓòÉ 90. Getting Lots of 'System cannot find the file "xxx.xxx"' Msgs ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am attempting to install the OS/2 2.1 Upgrade (CD ROM) over my
existing 2.0 system.  The install went okay (except that I noticed a
whole bunch of EAxxxxx.CHK and FILExxxx.CHK files in my root directory
after the intall).

Anyway, I shutdown OS/2 and re-booted.  Shortly after the logos appeared
on the screen, I got a bunch of the following messages:

  The system cannot find the file "xxxxxxxx.xxx".  This...file is not
  located in the default path or path specified in CONFIG.SYS.

I could only see the filename on the last message, because the rest had
scrolled off the screen. The last one was "sonycds1.flt".

The very last message displayed before lock-up was:

  The system cannot find the dynamic link library DOSCALL1 which is
  needed to start the system.  Install it in the root, or in the
  directory specified on the LIBPATH statement.

This file IS present on the disk, in the \OS2\DLL directory. The path
statements from my CONFIG.SYS are:

  SET LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;\;
  SET   PATH=.;C:\OS2;C:\OS2\DLL;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2; ...
      C:\OS2\INSTALL;C:\;C:\OS2\MDOS;C:\OS2\APPS;\;
  SET  DPATH=.;C:\OS2;C:\OS2\DLL;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2; ...
      C:\OS2\INSTALL;C:\;C:\OS2\MDOS;C:\OS2\APPS;\;C:\OS2\BITMAP;

Anyone have any idea what is wrong?  Thanks!

Rich Molnar, VM Networking, ISSC Lexington
**********************************************************************

>I am attempting to install the OS/2 2.1 Upgrade (CD ROM) over my
>existing 2.0 system.  The install went okay (except that I noticed a
>whole bunch of EAxxxxx.CHK and FILExxxx.CHK files in my root directory
>after the intall).

The only time I've seen this kind of error was with hardware conflict that
mung memory/the FAT/HD.  One of them is, I'd bet causing your problem.
The only thing that I could then do to fix it was to reinstall.

BTW, one of the temporary fixs that for some reason worked was to install
the HPFS file system--even though I had no HPFS vols.  That kept me
running until I could track down the real culprit--an old WD Ethernet
board.

Ken Prevo
**********************************************************************


ΓòÉΓòÉΓòÉ 91. OS2 2.0 INSTALLS BUT WILL NOT BOOT ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I put the same append in NEW2OS2 FORUM but I think it belongs here.

I just bought a new clone and I cant get OS2 2.0 to boot.
At first I had a CIRRUS LOGIC video card and after going thru 5
install diskettes and selecting the basic configuration to install the
DUAL BOOT OS2 the system would abend with message
    INTERNAL SYSTEM ERROR FOUND AT LOCATION .....
I switched to TRIDENT local bus video card and the whole installation
went thru without any problems. But when the system boots up all I
get on my screen are colored vertical bars.
Using a mouse or a keyboard results in some screen disturbance with
no effect. Ctl+Alt+Del Changes screen to pure blue without rebooting,
I have to use a reset button.
I also tried installing with OS/2 2.0 formatting the C: drive
with FAT and installing the default basic configuration with identical
results. I do not know what else to try. Is it a hardware problem?

My system : 486 DX2/66MGz, AMI BIOS w/ 256K cache
       RAM 16M
       Trident local bus video w/ 1m DRAM
       Samsung 356 Hard drive
       MAG MX15F monitor.

Any suggestions would be greatly appreciated.

Ed Faynin.
**********************************************************************


ΓòÉΓòÉΓòÉ 92. boot manager corruption. ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 (no text entered)

Eric Decker
**********************************************************************


ΓòÉΓòÉΓòÉ 93. ATM information ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We are installing OS24WIN and formatting the OS2 drive as HPFS.  What
happens is that when the install "migrates" the windows over to be used
under OS2, it creates an ATM.INI file that points to the OS2 drive.
This is fine until you boot into DOS, start WINDOWS and try to install
an app that uses ATM (in this case MICROGRAFX).  It says that the drive
the ATM.INI file points to can't be used or is full.  Understandable
since the drive pointed to in the file is an HPFS partition.  To solve
the problem, we rename the .ini file, restart the app installation
progress and works fine.  Anybody have any thoughts on how to fix the
problem and if this is going to cause problems when we go back into OS2?

Thanks.

John McMullen, TEAMOS2 and TIPA, MCI, Atlanta
**********************************************************************

I ran into something similar geting ready for the SP. I reinstalled everything
this time making my OS/2 partitions HPFS, looking forward to finally being able
to use DCF/2. When installing WIN-OS2 support, I checked the little box that
indicates changes to the WIN-OS2 desktop should be reflected in the DOS-WIN
desktop. Bad move... after accessing Quicken (CD-Rom deluxe) in Win-OS2, I lost
several icons (they became little empty TV screens), and of course this showed
up in DOS-WIN as well. After thinking about it, I selectively reinstalled
WIN-OS2 support, again copying my existing windows desktop, but this time I
did NOT check the box for modifying DOS-WIN when Win-OS2 is modified. I don't
know if this will work, but my idea was to copy *.GRP, *.INI over to the
WINOS2 directory so that both windows flavors use their own initialization
files, which I can edit to suit myself. Don't know if this will work, because
I haven't finished experimenting with it yet. Does anybody know if this
approach will work?

Tim Fansler <TeamOS/2>
**********************************************************************


ΓòÉΓòÉΓòÉ 94. Intstall Problems on Gateway 2000 w/ UltraStor SCSI Controller ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I ran into several problems installing OS2-4-Windows on a Gateway 2000
machine, spent three hours on the phone w/ OS/2 support, but was
unable to successfully install.  Finally, support team helped me
restore my (broken) machine to its original state.

Before I attempt to install again (with knowledge I gleaned from
first attempt, plus a tip from UltraStor tech support), I'd appreciate
any tips you might have...  Here's my configuration, and what I've
learned so far:

My system:
 Gateway 200 486 DX2 66
 Mitsumi CD ROM
 ATI Ultra XLR 2MB Video
 UltraStor 34 SCSI Controller
 Seagate 1.05GB HD

Steps I Learned are Required To Install:

1. Disable Phoenix BIOS settings as described in README.INS
  (namely Turbo mode, External Cache, and both Shadow RAMs)
2. Get device driver for Mitsumi CDROM, make copy of OS2 Install
  Disk #1, and copy the device driver file to that diskette.
  Also add statement to CONFIG.SYS for the device driver.
3. For the ATI Ultra 2MB Video, change the PowerUp Settings to
  use "VGA PS2" mode.

These are all things I learned from OS/2 support.  I have since
called the UltraStor tech support line, and they say that, contrary
to what OS/2 support told me, I also need an UltraStor device driver
(ULTRA14.ADD) for installing OS/2 from CDROM.  The diskette install
does not require it, but from CDROM I need to add the device
driver to Diskette #1 and add a line to the CONFIG.SYS file.  They
sounded pretty confident about this.

Before I go off and try this again, does anybody have any
warnings/experience/advice on the subject?

Thanks!  I hope this helps some other poor Gateway 2000 owner!

K.E. Fichthorn
**********************************************************************

K.E.

  Make sure that it is WIN 3.1 and not W4Workgroups 3.11.

E Ilsley
**********************************************************************

[Reference to append at 19:16 on 94/01/27 by KENF at BLDVMA ]

 > >Steps I Learned are Required To Install:
> >1. Disable Phoenix BIOS settings as described in README.INS > >
(namely Turbo mode, External Cache, and both Shadow RAMs) > >2. Get
device driver for Mitsumi CDROM, make copy of OS2 Install > >  Disk #1,
and copy the device driver file to that diskette. > >  Also add
statement to CONFIG.SYS for the device driver. > >3. For the ATI Ultra
2MB Video, change the PowerUp Settings to > >  use "VGA PS2" mode.
I too am about to install the OS/2 Special Edition for Windows 3.1 and I
had a few questions about the steps you listed in your append in
addition to some more questions of my own.
Before I go any further, I'll throw out this disclaimer:  I am the type
of user who really doesn't twiddle much with his machine.  If it works
when I turn it on and I am able to do the things I like to do with
relative speed, I am happy.  With that said:
1) In your step 1 above, When I run the set-up I see a designation that
reads, "CPU SPEED = FAST."  Is this what you refer to as "TURBO MODE"?
2) Both Shadow RAMs?  I only see one choice for BIOS Shadow (Enabled or
Disabled) when I run the set-up.
3) Where in README.INS did you find this information?  The only Phoenix
info I found was on page 167 of the Installation guide and all it said
there was to call the manufacturer.
4) (Here is where my real ignorance shows) For both the Phoenix BIOS and
the ATI card, are these step necessary only during the installation or
do I need to leave this stuff permanently disabled?  If the answer is
"only during the install process," when can I enable them again?
5) The Installation Guide talks about problems with Micronics system
board revision E.  How can I tell which revision of the system board I
have?
I truly appreciate any and all help!

              Scott J. Heimer
               HEIMER@RCHLAND
SHEIMER@RCHVMX2                Department 4A6
         030-2  F212                 553-5372
**********************************************************************

Subject: Cant get rid of 1MB partition
 I just installed a SCSI drive in addition to the ESDI on my old PS/2
mod 80.  Running FDISK, I delete all partitions and then try to create
a single Extended partiton. But the pgm always creates a 1MB freespace
at the start of the drive, followed by the Extended I asked for.
 I can't create 2 Extended. If I make the 1MB into a primary, it changes
the drive lettering. If I leave it as freespace, I waste 1MB.
 FDISK will let me create Primary with >1MB.  Is there some rule
that a disk must have at least one Primary partition ?
Ron Winn
**********************************************************************

[Reference to append at 19:16 on 94/01/27 by KENF at BLDVMA ]

Here's an informational update, along with some critical commentary
on installing OS/2 2.1 on a Gateway 2000 machine.  Since my original
append, I have run into several new problems.

1. If you have an Ultrastor 34 SCSI Controller, and you are installing
  from CDROM, you must copy ULTRA14.ADD (device driver from Ultrastor)
  onto the OS/2 Install Disk #1, and add a "basedev" statement to the
  config.sys file.  The OS/2 support people had said this was not
  necessary.

2. Even though I had Windows 3.1 pre-installed on my system, OS/2
  prompted me to insert the Windows diskettes during installation.

3. It got worse.  When I provided the Windows 3.1 disks, OS/2 took
  them, but prompted me to enter diskette #7.  There is no such
  diskette. The installation stops at that point, and there is no
  way out but to power off or reboot.
  The solution to this problem, offered by the OS/2 support team,
  is to fake out the OS/2 install program by creating a phony
  Disk #7.  This involves formatting a blank diskette, giving it a
  volume label that matches conforms to the volume label pattern
  of Disks 1-6 (WINDSK7, I believe), and then copying to it the
  contents of Disk #6.

4. Finally, I made it to the point where "OS/2 install completed
  successfully".  But when I rebooted, the machine hung at the
  OS/2 Logo.  I discovered the problem -- there were four or five
  copies of the "basedev" statements that I'd added for my CD ROM
  and my SCSI Controller.

  Apparently, each time I attempted to install, it added new copies
  of those statements(?).  In any case, once I removed the extra
  "basedev" statements, OS/2 came up fine.

After going through all this, I wonder, "Why would a customer put up
with this?"  I only did it because I currently make a living writing
code in OS/2.  If I were looking for an operating system to run
applications, I would have given up trying to install OS/2 after the
first three or four hours.

Mine is not an isolated situation.  It can't possibly be.  I don't
know numbers, but Gateway 2000 certainly owns a good share of PC
sales, and many or most Gateway customers will run into the same
problems that I did.

Specific problems that I think need to be addressed are:

1. Requiring a user to switch his BIOS settings (Turbo, Shadow,
  External Cache) off for installation.
2. Requiring a user with pre-installed Windows 3.1 to provide
  diskettes.  I thought OS24Windows didn't need to install Windows!
3. Asking for a Disk #7 when there are only six Windows disks.#$???
4. The hardest problem of all...providing some graceful handling of
  various unsupported hardware devices.  Or better yet, support them!

K.E. Fichthorn
**********************************************************************

The company I worked for before MCI had a number of GW2000 and I agree
that installing 2.1 on these machines is a hassell.  As to your
statement about OS24Win, even though you have windows already installed,
if you choose to keep it, it will prompt for the original Windows
diskettes.  Here at MCI, we use DELL systems and they come with DOS 6.2
and Windows 3.1 preinstalled.  We have 7 window disks plus 1 enhancement
disks.  I don't know why GW only shipped 6 disks, very interesting.

John McMullen, TEAMOS2 and TIPA, MCI, Atlanta
**********************************************************************

Actually, I didn't get any Windows diskettes from Gateway.  Windows
is loaded on my GateWay System CD.  The OS/2 install program did let
me specify my CDROM drive for loading the Windows files off of CD,
but it got stuck when asking for Diskette #7.  That's when I went out
and got a shrink-wrap version of Windows.  But again, OS/2 Install
prompted me for diskette 7, even though there are only 6 diskettes
in the shrink-wrap version that I have.

But the real issue is, why does OS/2 request ANY diskettes for
Windows???  I've already installed it on my hard disk once!

K.E. Fichthorn
**********************************************************************

Ken, I can't answer your question on why it asks for window's disk
anyway. I too thought it was strange since WINDOWS was already
installed.  Maybe someone from IBM can give an answer (hint, hint)?.
Also, I don't know why DELL gave us 7 disk in their copy of WINDOWS that
was shipped with our machines while the shrink-wrapped copy of it only
has 6.

John McMullen, TEAMOS2 and TIPA, MCI, Atlanta
**********************************************************************

John,
   A lot of us would be interested in an answer from someone in IBM
on what OS/2 for Windows needs with the Windows diskettes during
install and how it comes up with the numbers it is looking for.  (See
my Dec 01, 1992 append asking this question of Helen in BTIG.)
Hopefully this append will put it back on the list so someone in BTIG
can get back to us here.

Leo Tornow - Northwest Pipeline Corp.
**********************************************************************


ΓòÉΓòÉΓòÉ 95. OS2 hangs on boot ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I've just installed OS2 2.1 on my PS/2 mod 80. The install process worked
fine, until I reached the stage where you are supposed to re-boot for the
configuration process. Then it hung, with the following error message:

TRAP 000d  ERRCD=0000 ERACC=**** ERLIM=********
EAX=000000d1 EBX=fca60730 ECX=fca60002 EDX=fca60550
ESI=0000082e EDI=fca6001b EBP=00004e9c FLG=00013202
CS:EIP=0568:00001dd0   CSACC=009f  CSLIM=000023e1
DS=0570   DSACC=00f3  DSLIM=0000092f CR0=fffffff3
ES=0570   ESACC=00f3  ESLIM=0000092f CR2=ffe4e000
FS=0000   FSACC=****  FSLIM=********
GS=0000   GSACC=****  GSLIM=********

The system detected an internal processing
error at location ##0160:fff5fbd5-000d:9bd5.
60000, 9084
0386 00b1
Internal revision 6.514, 93/04/12

I saw an earlier append, related to APAR PJ08730, which describes a way
to create a new diskette #1. However, it's not clear to me that this APAR
applies to my situation. Can anyone clarify whether the hang this APAR
addresses is a hang when booting from the diskette, or when re-booting
OS2 after an apparently successful install process?

Chuck Poland (POLAND at WTSCPOK)
**********************************************************************


ΓòÉΓòÉΓòÉ 96. CIRRUS LOGIC SVGA installation fails ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am trying to install the drivers for the CIRRUS LOGIC 5428 using
DSPINSTL but get "Hardware configuration does not support SVGA".
W31 and WinOs2 drivers install without any problems and I can go
with 1024x768x256 with both.  So it looks like only os2 has a
problem.  Can anyone help me out with what I am doing wrong?

Thanks in advance,
  Dave Hollar
**********************************************************************

Dave,

Rather than use DSPINSTL, try the "Selective Install" ICON in System Setup.

I'm not sure why, but recently a selective install worked for me with a
similar card where DSPINSTL did not.

Jim Stuyck - J.D. Stuyck & Associates - Member, I.V. League - [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 97. Converting 1.3 EE to LS 3.0 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We have a large number of servers that are currently running OS/2 1.3 with
Extended Edition's LAN Server v1.30.1. As we will have a considerable
chore in upgrading the all of the NET.ACC's and DCDB's for these machines
is there a conversion tool we could use in our upgrade procedures?
**********************************************************************

We have a large number of servers that are currently running OS/2 1.3 with
Extended Edition's LAN Server v1.30.1. As we will have a considerable
chore in upgrading the all of the NET.ACC's and DCDB's for these machines
is there a conversion tool we could use in our upgrade procedures?
**********************************************************************

Have you read through the LAN Server V3.0 Planning and Installation
Guide (IBM Document # S96F-8428)?  The BACKACC and RESTACC
utilities are talked about in detail. I assume you will
want to migrate from 1.3 to LAN Server V3.0 Advanced, and there
are several C/I/D scenarios in this document that describe how to
upgrade your 1.3 servers in a lightly attended manner (chapter 4 and
Apeendix E and G).

Steve W. Davis  IBM  Dallas, Tx
**********************************************************************


ΓòÉΓòÉΓòÉ 98. Boot mgr corruption ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 I have a user with 2 dell 466 l pc's with 16 meg of ram 340 hard disk partitia
 ed as follows. 1 st part. boot mgr 2nd part dos/windoze 3rd part. os/2 2.1.
 What seems to happen is the machines may work fine and then are shutdown and
 ebooted. Thw units count ram and then stop there. I must reboot with the os/2
 isks and fdisk the hard disks. Once that is done the units work fine until the
 next time. Any ideas ?????

Eric Decker
**********************************************************************


ΓòÉΓòÉΓòÉ 99. Mouse problems ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have been trying to get my Logitech mouse to work with OS/2 2.1 (for
Windows) but have had no success.  I am using the Boot Manager and have
DOS 6.1 and Windows 3.1 on a FAT partition and OS/2 2.1 on a HPFS
partition.  My mouse is an older Logitech serial mouse (C series)
connected to COM1 at the default IRQ and address.

I have no problems under DOS or Windows if started from DOS.  Nothing
works mice-wise under OS/2 (OS/2, Win, or DOS) whether I start it
straight from power-on or reboot from DOS.  I tried all the serial mouse
settings (Serial Mouse, Logitech C, Logitech M) and none work.  I get a
mouse pointer but it doesn't move nor do the buttons do anything.

Any ideas what might be wrong?

Just recently I got some new (dated in November) DOS and Windows mouse
drivers from Logitech.  There were instructions on how to set up under
OS/2 2.0 with them but not 2.1.  Can these drivers be the cause of the
problem (or perhaps the solution)?  When I do a selective install under
OS/2 I have to stick my Windows isntall diskettes in and some files are
copied from them including MOUSE.DRV which looks suspicious.

- Bill Seurer   Language and Compiler Development    IBM Rochester, MN
 Internet: [e-mail]   America On-Line: [e-mail]
**********************************************************************


ΓòÉΓòÉΓòÉ 100. Mouse problems ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Subj   Mouse problems
Ref:   Append at 20:51:31 on 94/01/31 GMT (by SEURER at RCHLAND)

Bill,

First compare the OS2\MOUSE.SYS file against the file on Install disk 2.
They should be the same size and date.

If this is an AT class machine, verify there are no IRQ conflicts.

CONFIG.SYS for older 'C' series Logitech:
 .
REM  COMx refers to either COM port 1 or 2 ONLY
REM  COM.SYS MUST be below the MOUSE.SYS statment
REM  All references to C: assume OS/2 is installed on the 'C' drive
C:\OS2\PCLOGIC.SYS SERIAL=COMx
C:\OS2\MOUSE.SYS TYPE=PCLOGIC$
C:\OS2\COM.SYS

CONFIG.SYS for 'M' series Logitech:

C:\OS2\MOUSE.SYS
C:\OS2\COM.SYS

Good Luck,
Gordon
**********************************************************************

I got my mouse to work last night.  Yay!
However, all I did was to move the DOS VMOUSE.SYS and DOS com driver
lines from just before the OS/2 ones to just after.  The original way is
how install put them in.  Why would the ordering make a difference?  I
didn't try any DOS stuff.  Might the mouse now not work in DOS?
                                 - Bill
Seurer   Language and Compiler Development    IBM Rochester, MN
Internet: [e-mail]   America On-Line: [e-mail]
**********************************************************************

I think all dos V* drivers need the OS/2 drivers to be loaded first because
they "hook" into interfaces provided by the OS/2 drivers to work.

Keith A. Blake  (The OS/2 Mole) V: [phone] (USPGC9GC/IBMMAIL)
**********************************************************************


ΓòÉΓòÉΓòÉ 101. OS/2 for Windows install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I'm trying to install OS/2 for Windows on an Ambra 466BL. I want the
plain vanilla configuration, with a single partition on the hard disk
formatted for HPFS. My first installation attempt (over MS-DOS 6.0 and
Windows 3.1) was successful except I never received the prompt to load
the Windows 3.1 diskettes, so I could not get WIN-OS/2 support. In the
System Setup / Selective Install / Software Configuration window
(installation guide p.26) I should have the option to checkmark the
line: WIN-OS/2 Support {7.8MB}. On my screen the line is completely
absent. Besides this problem, after the installation I remembered that I
should have set the cpu speed to SLOW, caching to OFF, etc., before the
installation (oops!).
The IBM helpline said to uninstall OS/2 and try it again. I uninstalled
OS/2, set the system parameters (e.g. cpu speed) to their correct
values, and tried to install OS/2 again using the single partition. The
result was the same, only this time I received a message: Windows 3.1
not detected. I got the same Software Configuration screen as the first
attempt, no option to add Windows.
Has anyone else experienced this problem?
Thanks.
Jim Donohoe
**********************************************************************


ΓòÉΓòÉΓòÉ 102. Funny startup.cmd ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 I have just 1 client with this funny problem, what is so strange about
it is that it happens to him on different machines, but just to him.

 Anyway, when the machine reboots after disk 5, a startup.cmd window
opens and never closes.  He can reboot using DOS or OS/2's first 2 disks
and delete the startup.cmd and then begin where he had left.

 Is he doing something wrong that I didn't detected? It seems Ok to me.

 Muchas gracias por su ayuda.

Carlos Mendoza (BE98006 at MEXVM2) Mexico.
**********************************************************************


ΓòÉΓòÉΓòÉ 103. Primary and Secondary Displays ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

     Could someone tell me what means option of primary and secondary
displays that OS/2 gives me when I'm installing it ? It needs a special
hardware ? What criterion that OS/2 will use to redirect the output to
a monitor or the other ? Any ideas ? Thanks in advance.

                           My best regards

                           Marcio D'Amico
                          IBM PSP Team - DAP
**********************************************************************

You need two display adapters or in the case of machines 85XXs that come
with vga port you need an extra adapter (one display port/adapter per
monitor).  OS/2 multiple display support isn't spectacular (like macs)
and IBM didn't indicate that they plan to do much to improve the current
situation when I asked, so I wouldn't rush out to get two displays unless
you really need them.  A few months ago probably in the HW Cforum someone
mentioned IBM was working on a addon (HW/SW) to OS/2 to do multiple displays...

Keith A. Blake  (The OS/2 Mole) V: [phone] (USPGC9GC/IBMMAIL)
**********************************************************************


ΓòÉΓòÉΓòÉ 104. Mouse "Strange happenings" returns ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Ref:   None

My random problems of VMOUSE.SYS not being loaded,etc from the holiday
timeframe disappeared.  The more recent "happening" is a lot more
reproducible.  After running WINCIM from Compuserve, returning to
OS/2 desktop, the mouse ( MSFT compatible trackball) works fine.  Shut
down system as supposed to.  Next time I hardboot or hit "RESET" button,
the mini clock/arrow appears but cannot be moved, buttons are dead.  Do
another hard boot after shutdown, and everything is fine as though
nothing were wrong.  If people complain about OS/2 taking toooooo long
to boot, then doing it twice each time is @#$#Ы%&* awful.

The system is a Northgate 386/40, AMI BIOS, 8 meg, w/OS2_2.1 GA + fix
What's this about loading OS/2 2.1 with turbo OFF? Could this be a
symtom??

Stew Corman from sunny Endicott
**********************************************************************


ΓòÉΓòÉΓòÉ 105. Is the INSTALL subdirectory necessary after install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Customer is trying to trim down the size of their client machines and
was wondering what in the INSTALL directory is needed for a production
system ? OR another way what can they delete. Thanks.
**********************************************************************


ΓòÉΓòÉΓòÉ 106. Replacing the primary drive ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have a good OS2 ver 2.1 installation with Boot Manager and
C: (DOS), E:(data) and F:(OS2) on the 1st physical drive.  3
data partitions are on the 2nd physical.  All the partitions
are FAT.  (No HPFS on the machine now.)

I intend to replace the 1st physical with a bigger faster
drive.  I intend to stick with Boot Manager, C: (FAT DOS),
E:(data, HPFS) and F:(OS2, HPFS).

Anyone see anything wrong with (or a better way)
    move all possible to 2nd physical
    replace the first drive
    Do an entire new OS2 installation
      (FDISK thru Install) on Drive #1
    Leave the EA's on drive 2 until I get enough
      free space to change one of its partitions
      to HPFS.

I don't think I can get away with anything so simple as to
backup my F:(OS2) partition and restore it back onto the new
drive after it is formatted.  (Can I?)

Ken Hammer, St.J., VT
**********************************************************************

Ken,
I have made a similar change out on one of our servers, but doing an
XCOPY with the parms /h/o/t/s/e/r/v, of the boot partition to a subdir
on my second drive while booted from floppy.  Remove primary drive,
install new drive, boot from floppy, install BootManager, partition new
drive, and format boot partition, and XCOPY boot partition back from 2nd
drive.  Making sure that the drive letters remained the same.

Jack Hiatt
The International Phoenix Alliance
<Team OS/2>
**********************************************************************

[Reference to append at 04:53 on 94/02/09 by WZ00887 at HONE82 ]

Ken,
the file system was changed to HPFS while doing the previous as well.
Just make sure that the config.sys is changed to reflect this before the
copy was done.

Of course if you have a backup program that will do a restore without
the OS then you could do it with the backup instead of xcopy.

Jack Hiatt
The International Phoenix Alliance
<Team OS/2>
**********************************************************************

WARNING!!! do NOT use the standard OS/2 backup program to backup and
restore an OS/2 partition. It doesn't backup all the files, even when
booted from diskette.  The program filters out several important files
like command.com and cmd.exe. There is a special pair of programs
(backup and restore) that are put on the utility disks that you can
create from a preinstalled 2.00.1 system, but I don't know if the 2.1
preinstalls have the same capability.

I too have successfully used the XCOPY shuffle to the second drive, but
remember to use ATTRIB to remove the attributes for the OS2*.* files and
any others that may lurk around.  Use chkdsk to see if any hidden files
remain.

Alan Arnett, Fina, Dallas, TX, [phone]
**********************************************************************

The OS/2 2.1 XCOPY command will move all the files ( except ones open
with write ability) by using the /H /T /R (and optionally the /O)
options. In many cases you can even run XCOPY against the drive you
booted from- provided the XCOPY is the only thing running, the only
files that don't get moved are SWAPPER.DAT and the occasional log file
such as those used by Comms Manager or FFST/2. I have yet to find a case
where a file that matters hasn't been copied- the swapper and log files
are automatically recreated next time the using program starts. If it
worries you, just boot from diskette and they'll *all* be copied.

Don Hills  IBM New Zealand
**********************************************************************

[Reference to append at 00:13 on 94/02/17 by ABAXX at HONE82 ]

But you can use the backup from the 'preinstalled with OS2' machines.
I used it on our 9577, when I backed up everything and repartitioned
the drive to one partition and restored.

Geza Szivos <TEAM-OS2> IBMMail(CANOVXVV) The Phoenix Alliance
(403)-290-6583 Fax [phone]
**********************************************************************

[Reference to append at 10:58 on 94/02/17 by DONHILLS at SYDVM1 ]

Don, thanks. I now remember there where some flags for XCOPY that I
wasn't familiar with. Guess RTFM even applies to experienced people.
Just don't use the regular backup/restore. That one bit me. There's an
open apar to drop some of the filtering, but I don't imagine it's high
on their priority list.

Alan Arnett, Fina, Dallas, TX, [phone]
**********************************************************************

Actually, I use the OS/2 BACKUP command because it makes a "package"
that can be handled by DOS. It also allows backing up an HPFS partition
with long file names to a FAT disk drive. I use XCOPY to move the root
directory and the files \OS2\CMD.EXE and \OS2\MDOS\COMMAND.COM, and
BACKUP to do the rest. All I lose is the EAs for the two command files,
and they aren't any great loss- that is, I've never had a problem after
deleting the EAs from those two files.

Don Hills   IBM New Zealand
**********************************************************************

Good idea. I was always nervous about what else might be filtered, and
haven't had the need so far to actually test it.  I'll keep this
technique in mind.

Alan Arnett, Fina, Dallas, TX, [phone]
**********************************************************************

[Reference to append at 05:17 on 94/02/09 by TPA0003 at HONE83 ]

Thanks Jack,

I should have waited and followed your advice.  I didn't have
enough space left to do as you suggest, so I did it all over
again clean.  Had I remembered how much work it is to reset
all the settings for the DOS sessions, I'd have removed some
date from my existing 2nd drive to make room for the OS2
partition as you suggested.

Your approach is one of those "forever and often used" tips
which IBM should capture in a findable location.

Ken Hammer, St. Johnsbury, VT
**********************************************************************


ΓòÉΓòÉΓòÉ 107. Install Problems on 9557-2BA Preinstalled with 2.0 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I just received a 9557-2BA Ultimedia SLC2 machine which unfortunately
came preloaded with OS/2 2.0 (GA) instead of 2.1 GA.  So I downloaded
the OS/2 2.1 package from OS2PROD2 (20 diskette version) ant tried to
install right over 2.0.  I got as far as the "Migrate Applications"
window where the PC hung.  That is, the mouse would move but nothing
could be selected.  I have been reading in this forum that I might have
to replace the ABIOS on the 2.1 install diskette with that on my
backup reference.  So I copied the 9557 backup reference's ABIOS.SYS
to the 2.1 install diskette.  Now the install dies at diskette 2 with
a message about FDISK failing even though I didn't ask to run FDISK.
The install log has an interesting comment: Non-ABIOS machine.

What steps, specifically as possible, do I need to take to install
2.1 on this machine?

John Ferrell
JFERRELL at MANVM1 - TL 8-725-3483
FSC System Services and Planning, 120/024, Manassas, VA
**********************************************************************

You shouldn't modify the 2.1 GA install diskettes, they already contain
support for the 9556/9557. Note that the preload was not a standard
2.0 GA- it had the necessary changes made to recognise the 9557.
Did you have any applications already on the system that needed
migrating? I assume not, because you had just received it. The safest
method is to reformat the disk and start again. Boot from the install
diskettes, and take the option to repartition/reformat. If you don't,
the install should still work, but you end up with some directories and
files left over on your disk from the preload that aren't any use to
you at 2.1.  If you need a more detailed answer than this, and don't get
it here, you could try asking in the SYS2-M57 FORUM.

Don Hills  IBM New Zealand
**********************************************************************


ΓòÉΓòÉΓòÉ 108. CidSetup Problem ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am in the process of setting up a CID Server using SRVIFS.  I have
everything set up, and have created Disk images for LAPS and OS/2 2.1
on the Code server, and created the Boot Disketts.  Question is, how
do I start/activate the Code Server.  I thought it was started by entering
SERVICE ... Any help would be greatly appreciated

Tom Razor
**********************************************************************

In order to start the SRVIFS server, you must go to the \SERVER directory
and execute SERVICE /INI=SERVICE.

Tom Lambert
P.S.  Sorry it took so long to answer question.
**********************************************************************


ΓòÉΓòÉΓòÉ 109. Installing OS/2 2.1 on ValuePoint 433DX/D ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

From the prior appends on this subject it appears that I am in for
a fun time!

I have just installed disks 1-5 and I'm looking at the System Configuration
dialog box.  These are the problems......

1. The autodetect display type is VGA, but I have an SVGA.  Should I
  select SVGA?  Rumor has it that OS/2 2.1 is not shipped with
  ValuePoint SVGA drivers (see above).  How does one aquire this
  driver?  Can some kind soul send it to me?  Please?
2. No CD-ROM device is detected, but I have a CD-ROM.  Should I select
  IBM CD ROM I ???
3. No SCSI support is detected, but I have a SoundBlaster 16 (which
  controls the CD-ROM).  What SCSI support should I select?
4. No default printer is selected.  I have an "IBM Personal Computer
  Graphics Printer" model 5152, what driver should I select??

Any help would be greatly appreciated.

John Henckel
**********************************************************************

>1. The autodetect display type is VGA, but I have an SVGA.  Should I
>  select SVGA?  Rumor has it that OS/2 2.1 is not shipped with
>  ValuePoint SVGA drivers (see above).  How does one aquire this
>  driver?  Can some kind soul send it to me?  Please?
 Always select VGA first and then go back to selectively install SVGA. In
this case (assuming that valuepoint line hasn't become a component-du-jour
situation) you need to install the S3 drivers available here.
They come with pretty complete instructions.

->Rich Corbett; Mgr. Sys.; ABC Liquors, Inc., Orlando, FL   (NASPA:CORBRIC7)
**********************************************************************

[Reference to append at 15:43 on 94/02/10 by HENCK at RCHVMV ]

I STILL do not have the CD ROM working with OS/2.  Please help!

I cannot get OS/2 to recognize the CD ROM drive.  I selected the
Adaptec 1740 SCSI and IBM CD ROM II from the install menu.
When I boot I just see:

SYS1201: The device driver "C:\OS2\OS2CDROM.DMD" specified in ...
CONFIG.SYS file was not installed.

If ANYONE has a Sound Blaster 16 with SCSI used to control a CD-ROM
working with OS/2 2.1, then PLEASE CALL ME.

John Henckel        507-286-4151  or tie.8-456-4151
**********************************************************************

> I cannot get OS/2 to recognize the CD ROM drive.  I selected the
> Adaptec 1740 SCSI and IBM CD ROM II from the install menu.
> When I boot I just see:
>
> SYS1201: The device driver "C:\OS2\OS2CDROM.DMD" specified in ...
> CONFIG.SYS file was not installed.

JOHN,

I had the same problem with the Adaptec 1542 and Toshiba 3401-B.
Pin 1 was not labeled on the 3401 so my first guess was wrong.
Turning the cable over worked. Pin 1 must match between the controler
and the drive. Good luck.

Don Callaway, Power Computing  [phone]
**********************************************************************

Don, I found the problem.  What I really have is a SB16 with an onboard
Adaptec SCSI adapter connected to a Panasonic CR-563 CD-ROM.

All I was missing was the SBCD2 package from OS2CSD.

John Henckel
**********************************************************************


ΓòÉΓòÉΓòÉ 110. Gateway 2000 and UltraStor ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Have several Gateway 2000 machines with UltraStor SCSI cards.  I loaded OS/2 2.
1 without a problem but we are having times when the machines hangs.  I think i
t has something to do with the hard drive.  When you look at OS/2 2.1 selective
 install section, the machine does not think that it has a SCSI card in it.  Th
e config.sys does not have the SCSI device driver loaded(of course), but it did
put in ibmint13.i13, that it may be using for the SCSI devices.  Anyone that c
an tell me what I need in the config.sys and if I need to load a special (unlis
ted) scsi device driver via the selective install, I would be grateful..  Thank
s in advance.

Gary Zimmerman   Southwestern Bell [phone]
**********************************************************************

Gary,
Ultra-Stor wrote thier own OS/2 drivers, they do not come with OS/2.  I would
contact Ultra-Stor or Gateway or a BBS/FTP site will have them also.
You install them manually, capy the ADD files into C:\OS2 and edit
config.sys.  You will have to know which Ultra-Stor model of controler you have
in order to get the correct driver loaded in CONFIG.SYS.

Mike Long - ISU/CARD - [e-mail] - TEAMOS2 - OS/2 Accredited
**********************************************************************


ΓòÉΓòÉΓòÉ 111. repeating os2 parameter settings on multiple os2 installs ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I need to install OS2 on multiple machines so that after installation
all look and operate identically. Numerous adjustments are made to the
desktop, config.sys, startup folder etc. after the default install
and with the number of machines that need to be installed with these
parameters the time to adjust each is significant. There must be a
"cookie cutter" approach I can use where I can setup one machine and
apply the settings to the other machines by copying specific files. I
am not sure which ones within OS2 contain any of my user defined
definitions. I am sure this is not a unique request and has been done
at other locations. Could anybody offer some guidance?  Your assistance
would be appreciated.
**********************************************************************

Check out Devtech Cforum.

Jack Hiatt
The International Phoenix Alliance
<Team OS/2>
**********************************************************************

[Reference to append at 01:32 on 94/02/14 by ACEN001 at OS2CUST ]

If you want a 'cookie cutter' approach, you might look at using a backup
program.  For example, we have cloned an OS/2 setup with Arcserve's OS/2 agent.
A number of OS/2 based backup programs should have this capability.
Look for the ability to run the restore program from an OS/2 Boot diskette set,
which essentially means that it has the ability to run as a character mode
app.  Most OS/2 based backup programs should do a good job with extended
attributes also.

One headache that Arcserve gave us was that it did not backup/restore the
boot track on the hard disk.  We restored to a pc that had DOS installed
by booting up on modified CID-style diskettes that gave us the ability to
run the text based OS/2 agent and talk over our LAN.  Because the boot
track did not get changed, it tried to come up as a DOS machine.  But by
using Boot.com we were able to get it to boot OS/2.  So, you might also
look to see if the backup program will backup and restore the boot track.

One warning.  These "cookie cutter" workstations should also be identical
as far as hardware and bios goes.  A lot of what the install program configures
is based on what it detects for hardware and bios.  Also, IBM might not
give you technical support for problems unless you duplicate them on a pc that
has been installed the old fashioned way.

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 112. Problems with Update to OS/2 2.1 UK (CID) ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We have a Problem with CID and Update from OS/2 2.0 UK to OS/2 2.1 UK.
Our Envirement is a NetWare Server 3.11 with the OS/2 2.1 Images and
Clients with OS/2 2.0 UK and the NetWare-Requester (NSD202A).
During the Update (CID), the Client hangs on the File WIN_30.RC.
By rebooting and restarting the Installation, the System stopped
on the second Diskette with a Fault in the FDISK.

Can someone help us?

Kind regards

U. Schneider

This append was created on the External IBMLink system by
DETTWILER INFO. AG
**********************************************************************


ΓòÉΓòÉΓòÉ 113. Mitsumi CDrom w/ Media Vision ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I helped get someone installed with OS/2 for Windows on a brand new
Gateway 2000 486dx2-66 but couldn't get OS/2 talking to the Mitsumi
double-speed CDrom drive.  It works under DOS so I looked in config.sys
for parameter values.  It is at address 340 and IRQ 10.  Anyone been
able to get this combination of card and CDROM to work ?  If so please
post the four or five lines from your config.sys.  If I need to call a BBS
to get drivers from Media Vision could someone post the number.  Thanks.

Leo Tornow - Northwest Pipeline Corp.
**********************************************************************

Leo,
Did you get the drivers for the Mitsumi drive?  I believe they are
available here, if not check out the PCCBBS the file is MITFIX.ZIP.

Jack Hiatt
The International Phoenix Alliance
<Team OS/2>
**********************************************************************

[Reference to append at 18:54 on 94/02/14 by IL04688 at HONE82 ]

I am the same but different<g>...mine goes:
BASEDEV=MITFX001.ADD /P:320 /I:11 /V

The /V is handy to validate that the driver is doing things the way
expected.

Ken Prevo
**********************************************************************

Jack and Ken,
   Yes, the driver I was trying to use was MITFX100.add.  I'll follow
Ken's pattern for parameters.  Thanks for the help.

Leo Tornow - Northwest Pipeline Corp.
**********************************************************************


ΓòÉΓòÉΓòÉ 114. 2.1 Boot Mgr on 1.3 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have a version of 2.1 installed on an external hard disk. My C: drive has
Boot Mgr.  While my machine is being repaired I want to use 2.1 on a replacemen
t machine which has 1.3 on C: and trash on the D: partition.
If I drop the D: partition (in order to install Boot Mgr), can I begin the
2.1 install process from CD-ROM, then abort the install without affecting the
1.3 version on C: ?  Then I could use 2.1 and return the replacement machine to
its owner pretty much in the same shape as I got it (even better shape with Boo
t Mgr.)!

Thanks for any info.

Joel Poole  Corte Madera, CA
**********************************************************************


ΓòÉΓòÉΓòÉ 115. OS/2 2.1 CDROM Install Disks ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have misplaced the two 3.5" installation disks from my CDROM version of
OS/2 2.1.  I still have the 5 1/4" copies.

Can anyone suggest the fastest method of "getting" 3.5" copies, either by
somehow coping the 5 1/4" or some other means.

Thanks.

Dave Ferrey - EDS - Bethlehem Steel
**********************************************************************

Dave-
 There are diskette images for all the diskettes in the \diskimgs\os2\35
directory on the CD-ROM.  Use the \diskimgs\loaddskf executable to create
a new diskette 0 and diskette 1.

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 116. System hangs during OS2 2.1 install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am trying to install OS2 2.1 in a MOD 80 which was running OS2 2.0.
It loads diskettes 1-5 and then it requests that you put back the
installation diskette.  At this point it goes into the "Transferring
Files..." screen and it hangs when the current file is VIOTBL.DCP.
Using DOS, I can read all the files in the installation diskette, so
I doubt it is a diskette problem.  Is this a known problem?
Thanks,
    Bill Melkesetian
**********************************************************************

I hit the same problem when I got my OS/2 V2.1 at the FTN.  The question is ?
is your diskettes blue label or red/pink label.  I have had many problems with
bad diskettes on OS/2 V2.1 with Blue Labels.  The problem only seamed to
act up on install, or OS/2 access but showed no problems with dos.

John E Quigley II  Standard Register Corp  -- IS -- [phone]
**********************************************************************

[Reference to append at 17:24 on 94/02/15 by MELKE at KGNVMF ]

I had a similar problemon a 9556-DBA except it wouldn't hang in the same
place or even on the same diskette consistently.  I finally gave up and
convinced an SE to come out for a look-see.  He scratched his head and decided
to have the motherboard replaced.  That solved the install problem, but there
is still a family of gremlins living inside it I think.  I've got an identical
workstation and have no problems, but even with the CSD that one doesn't
shutdown well.

Chuck Simonds, Goodyear Tire & Rubber Co.  (TEAM OS/2)
**********************************************************************


ΓòÉΓòÉΓòÉ 117. Backup the desktop ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am going to be installing OS/2 2.1 on two machines. One is already
at 2.1 but I am going to format the partition and then reload it (we
are having some strange problems with it). The other machine is
currently running 2.0 so it is just a migrate.

My question is if there is any good way to backup the desktop settings
for these two machines. The current 2.1 machine has two hardfiles and
four partitions and is set up as LAN server for a laser printer so I
would like to save as much as I can about the desktop.

Thanks.

John Brunsgaard
**********************************************************************

Probably the best method I've used is to use the Deskman/2 program.  You
can find more info about it in the DEVTECH CFORUM.  Development
Technologies is the company that produces Deskman/2 and they monitor that
forum.

As a no cost alternative, you might want to try the RoboSave package
from the Employee Written Software program.  For IBM internals like
yourself, get the ROBOSV package from the OS2EWS tools disk or ROBOSAVE on
OS2TOOLS.

Brent Allen - IBM Personal Systems Competency Center   Southlake, TX
**********************************************************************


ΓòÉΓòÉΓòÉ 118. 16 MB on ISA/PCI ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Can anybody explain what OS/2 does during install?
How does it recognize a system that can swap from/to memory from/to
disk directly above 16M?
On a normal ISA system swapping from above 16M is impossible (24bit bus).
On a PCI system this should be different (32bit local bus connected
to memory AND SCSI or IDE disk).
Thanks for any explanations|

This append was created on the External IBMLink system by
Willem van der Mark
Swissair CAA
8058 Zurich Airport
Switzerland
**********************************************************************

>How does it recognize a system that can swap from/to memory from/to
>disk directly above 16M?
>On a normal ISA system swapping from above 16M is impossible (24bit bus).

I'd guess that they have a ROM checksum or pattern match to identify
different HD controllers and whether or not they use DMA.

ISA machines can access above 16-meg.  There are port operated controllers
that can be used instead of DMA using controllers.  I think the PS2Assist
documents them--could be Sipple's FAQ though.  Not the best solution,
maybe, but it is possible to have an ISA machine and 32-meg of memory
using all of it for OS/2 programs.

Ken Prevo
**********************************************************************


ΓòÉΓòÉΓòÉ 119. SYS1217 message, OS/2 levels ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

After installing an 8514 adapter card on a customers machine,
I was using selective install to install 8514/A support.  At
diskette 8 I received SYS1217 Message that the "file cannot be
decompressed with this version of OS/2 unpack command."  Since
the version and CSD level of his OS/2 matched my diskettes, I don't
know what to correct.  The UNPACK.EXE on my OS/2 diskette is April 93.
but I have no way of knowing the date of the PACK.EXE.  Or is
this a CD ROM vs diskette installation problem?  I don't know how
his OS/2 was installed.
Suggestions?

Jerome Higgins
**********************************************************************

Sounds as if you could be using the display drivers from the 'salmon' colored
diskette onto a machine that was installed with the 'blue' diskettes.  See if
you can find a set of blue diskettes and everything should be ok.  There is a
utility to update your install directory to use the salmon colored diskettes
on a blue machine available on the IBM Nation BBS.

Chuck Thomas Sunburst Bank Grenada MS
**********************************************************************


ΓòÉΓòÉΓòÉ 120. Slowww Mouse! ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I've recently upgraded my system and now have installed OS2 for
Windows. All is going fairly well, but I have a 'problem' with
the mouse speed. I can't get it to move fast enough. I've got
the Settings for the mouse as fast as it will go, but moving
from one side of the screen to the other is a painful process.

Under Native DOS/Windows, no problem since it's using the
supplied mouse drivers. This is an OEM clone serial mouse with
no markings as to who made it. The only ID in the mouse driver
is MOUSE DRIVER 8.20a

I've tried installing it as a plain Serial pointing device and
as a Logitech type M. Both work identically (poorly).

I won't swear to this as fact, but after my initial install I
THINK the mouse was operating properly. I've done very little
since then other than installing Windows versions of 123 and
WP. The rest of my customization has been in setting up folders
etc. on the desktop and stuffing in some old DOS apps.

Do the OS2 drivers perhaps expect a hi-res mouse while my cheapie
probably is a lo-res? Just a thought.

Any ideas would be really helpful; my right hand is getting tired
from all this mouse movement.

George Deluca
ISM Information Systems Management Corp.
North York, Ontario M2J 4R3 416-351-6056
**********************************************************************


ΓòÉΓòÉΓòÉ 121. Install hangs before Display Driver Diskette ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

When installing OS/2 V2.1 on a machine the install appears to "hang"
after the required printer driver (the null driver only in this case
since there is not a printer on the machine) has been loaded.  After
the printer driver is loaded from diskette the window disappears and
the message box displaying the "Configuring OS/2" message reappears.
The system begins beeping and the hard disk light flashes in an
approximately regular pattern.  This continues until we reboot the
machine (waited about over 30 minutes once).

What I would have expected at this point in the install was for the
prompt to load the Display Drivers diskette to appear as was the
case when the same set of diskettes has been used to install other
machines.

I suspect that the system is having trouble deciding what display
driver option should be selected.

When the machine is rebooted it hangs at the OS/2 Logo (expected since
no display drivers appear to be available).

If I use SETVGA to install the display drivers I get a "SYS0002 File
not found" message but I can then get the system to boot past the
OS/2 Logo to a white screen where I get the message that the desktop
cannot be found or is corrupted and can go no farther (expected since
the INI files have not bee updated and the system install did not
complete.  Using MAKEINI does nothing to help the situation.)

Anyone have an Idea as to why the install would stop before the Display
Drivers are loaded and then have the system beep at me with the hard
disk still being accessed?

Bob Wardle - IBM Australia
**********************************************************************


ΓòÉΓòÉΓòÉ 122. DOS install with CID ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

While I understand PC-DOS 6.0 offers CID installation support, we still
use 5.0 and I would like to be able to automate the installation of our
OS/2 machines where DOS/Windows will be on drive C: and OS/2 for Windows
will be installed on drive D:.  It looks like I can simply setup a lab
machine with the configuration I want on drive C:, save its image and
XCOPY it to each machine as one of the steps in the CID install.  The
obvious concern that comes to mind (offer others if you think of them)
is that SYS C: will need to be run to set up the drive C: boot record.
I don't think I will get away with just dumping DOS onto drive C: and
expect boot manager to 'discover' it.  I might try that, but I'll bet it
doesn't work.

Has anyone set up the execution of DOS programs such as SYS within the
CID process. I see various EWS and other utilities that might help such
as STARTD and TSHELL, but I don't know if they would even work during
CID. Any suggestions would be appreciated.

Alan Arnett, Fina, Dallas, TX, [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 123. Install options ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

  What are the ramifications of not turning off turbo, level 2
caching during the OS/2 2.1 install ? I understand that random traps
could occur during the install process but once the install process
is finished will all be OK ?

Craig Brown ( IBM Gaithersburg )
**********************************************************************

(Modified for clarity, I apologize for poor initial proofreading)

Dire warnings aside, I have never turned them off on my home units (the
only non MCA machines I work with) and I haven't seen any problems that
I thought I could attribute to that, but the warning leaves itself a
mile of wiggle room, with it's 'after several months'.  I'm not saying
to ignore the warning, but it looks like 'it depends'.

Alan Arnett, Fina, Dallas, TX, [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 124. Transferring OS/2 between hard disks ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I need to transfer an entire OS/2 environment from one harddisk to
another.  Drive types are different, but capacities are equivalent
and the letter assignments will remain the same.  The target disk
currently has no system on it, and I will be using the same type of
file system on it (FAT).  What would be the fastest and easiest method
to achieve this?        Thanks, hank
**********************************************************************


ΓòÉΓòÉΓòÉ 125. Installations completes... and hangs ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I installed OS/2 2.1 (Brazilian version) and, after disk #4, the
installation was completed, and I should remove the diskette from
the drive and press ENTER to start configuration.

So, I removed the disk, pressed ENTER and OS/2 beeped. Just it.

After several tries, reformats, and hours, I reinstalled OS/2 2.0
which, after disk #4, reboots and starts configuration properly.

My system is a 386DX40, 4MB, VTC SVGA monitor with Realtek 1Mb card.
(Although I heard Realtek SVGA is not supported, it should work under
VGA mode, as OS/2 2.0 does).

TIA. Best regards,

Eduardo Gorges Rocha
**********************************************************************


ΓòÉΓòÉΓòÉ 126. Backup Command ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

So the question remains.  Does the OS/2 2.1 backup command behave like
the original OS/2 2.0 backup command or like the OS/2 2.0 preinstalled
backup command?  I have used that 2.0 preinstalled version and it worked
very well.  What version do we have now????

Julian Swales
ISM - Information Systems Management Corp. CAWSTSDT @ IBMMAIL
Regina, SK, Canada, S4S 7H1, Phone #:[phone]
**********************************************************************

The "shrink wrap" 2.1 BACKUP behaves the same as the 2.0 "shrink wrap".
It's only the preload versions that backup everything.

Don Hills   IBM New Zealand
**********************************************************************

I think that should be qualified. The backup command that backs up
everything, is the one that is put on the 'utility' diskettes that can
be created from the preinstalled system.  The backup command in the OS2
directory should have the same limits as the shrink wrapped versions.

Alan Arnett, Fina, Dallas, TX, [phone]
**********************************************************************

Quite right. Thanks, Alan.

Don Hills
**********************************************************************


ΓòÉΓòÉΓòÉ 127. Loosing CD-ROM during install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

In attempting to install os/2 using the cd twice I have lost the Toshiba 3401
CD-ROM.  Both time had different machines with different motherboards but
both time after the attempt the system did not reconginze the CD-ROM.  Prior
to the attempting to install the system recongized the CD-ROM.  The first
time it was attempting to install OS/2 over a DOS/Window system while the
second attempt was over a miminal OS/2 system.  Both times the install from
the CD-ROM fail but I could load OS/2 with diskettes but still did not have
access to the CD-ROM anymore.  Would like to know what can be done so next
time I could use the CD-ROM after the install and during the install.

Kevin Mooren
**********************************************************************

  Kevin:

  I just purchased OS/2 on CD but have yet to install it. I did download
 off the Media Vision BBS a file (Base---.ADD) that has to be copied to
 disk 1 before installation. The install manual has a blirb about this.
  As I said I just got OS/2 so I maybe way out in left field on this.

  D. Flatley at BTVMANVM
**********************************************************************


ΓòÉΓòÉΓòÉ 128. Installing OS/2 on second physical drive. ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I got a question from an OS/2 user.
He has a self-built clone and is trying to install OS/2 on the
second harddisk. With Boot Mgr on the first hd.
I thought this was possible, but he seems to be unsuccessful
sofar. Has anyone done such an installation?

Anton Versteeg - IBM Uithoorn
**********************************************************************

I have several bootable partitions on my secomd hard disk.  So it is possible.
Is he having problems:
 1. seeing and/or partitioning the 2nd hard disk?
2. setting a partition on the second hard disk installable?
 3. Getting the non-graphical install to go on the second hard disk?
 4. getting the graphical halve to run installing the second hard disk?
 5. booting to the second hard disk after the completion of the install?

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************

[Reference to append at 15:43 on 94/02/21 by 78887803 at EHONE ]

Yes, I have a couple of systems setup this way.

What problem is he having?

Aud :)
**********************************************************************

[Reference to append at 15:43 on 94/02/21 by 78887803 at EHONE ]

Anton,
I running off of such an install now, and have it on about 50-60 system
s at work.  How about some more specific information about his system
and the types of problems he is having.

Jack Hiatt
The International Phoenix Alliance
<Team OS/2>
**********************************************************************

[Reference to append at 02:12 on 94/02/22 by TBHIC at OS2CUST ]

I'll call him to find out.
Will let y'all know when I have more details.
Thanks so far.

Anton Versteeg - IBM Uithoorn, Netherlands  - TEAMOS2 NL - [e-mail]
**********************************************************************


ΓòÉΓòÉΓòÉ 129. video driver ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 I have a question from a customer: Does OS/2 2.1 have a video driver
 for a ZNON S3 accelerator card?
**********************************************************************


ΓòÉΓòÉΓòÉ 130. Slowww Mouse ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Just in case anyone else runs into the slow mouse problem I appended
earlier ...

It did turn out to be the cheapie clone mouse that came with my system.
I plugged in a friends standard Microsoft mouse and the mouse cursor
took off like it had jet assist.

Soooo... watch out that you don't get supplied with a lo-res mouse.

It appears the OS/2 mouse drivers don't have a large enough speed
setting range to support anything other than a hi-res mouse. I'm off
to my local mouse supermarket for a speedier rodent.

George Deluca
ISM Information Systems Management Corp.
North York, Ontario M2J 4R3 416-351-6056
**********************************************************************


ΓòÉΓòÉΓòÉ 131. System installation failed to start the session ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I'm attempting to do a "simple" LCU, OS/2 2.1 install to a P70, from
a PS/2 70, running 2.1.  I've tried to carefully follow the "OS/2
Configuration/Installation/Distribution CID Fastart Guide for LCU and
NVDM/2..Level 2.00" manual.  I've installed and utilized the latest
version of LAPS, but I am running into the above error.

The LT diskette runs and the P70 plasma monitor displays the
drivers that are being loaded.  AFter token ring V2.02 loads,
the system inevitably exits to a screen with only the above message
on it.  The error seems to be a "INS0916" from looking at the books,
but that error # does not appear.

I booted the P70 off OS/2 boot disks to have a look around, and
there are no files on the hard drive.  I did format the drive
before beginning this process, and I am able to use 'copycon' to
successfully copy a file to the disk of the P70.

I also used the utility, TRVIEW, from the LCU code server to
see that in fact the P70 adapter does come active on the ring
(not long before the failure occurs.  This is a test environment
with just the two machines connected on a single 8228.
Any insight appreciated! Thanks, Greg McCarthy IBM Chicago.
**********************************************************************


ΓòÉΓòÉΓòÉ 132. OS/2 2.1 install hangs ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Does anyone with a 9557-2BA have OS/2 2.1 installed?  Every time I
try to install it from diskettes (Both blue and salmon) it hangs
after the printer driver diskettes are installed with the message
"OS/2 is configuring the PC...please wait."  If so, did you have to
do anything special?  If not, what is the bios date/level of the
9557-2BA?

John Ferrell
JFERRELL at MANVM1 - TL 8-725-3483
FSC System Services and Planning, 120/024, Manassas, VA
**********************************************************************


ΓòÉΓòÉΓòÉ 133. Chapt 9 Still valid? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Is Chapter Nine of the "Remote Installation and Maintenance" Redbook
(GG24-3780-01) still valid for the OS/2 2.1 Service Pack just released?

Is there any other resources that go into a little bit more detail with
examples etc?

Thanks

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************

Matt,
The basic procedure for CID-installind the new ServicePak is pretty much
the same as documented in the RedBook.  There are two changes though.
There's a new parameter required for both the FSERVICE and SEMAINT
commands.  FSERVICE now has a /CID parm, and SEMAINT has a /S2 parm.
Refer to the README.INS file that came with the SP for more information.

Brent Allen - IBM Personal Systems Competency Center   Southlake, TX
**********************************************************************

Brent-
  Thanks for the response.  I'm thinking of being adventurous and using
semaint to build a bootable maintenance directory from which to apply
the service packs in a lightly attended manner.  But I have a couple
of questions:
  1. Do I need to wait for the 2.11 refresh to get the disk images
    from which semaint builds the bootable maintnence directory?
  2. Do I xcopy the display diskettes into CID service pak
    directory? Or put them in disk image subdirectories?
  3. There is no mention of multi-media in the red book (2.0 didn't
    have it) What do I do about multi-media service? Do I copy those
    diskettes into the CID service pak directory and include \mmos2
    in the response.fil's dirlist?
  4. I tried the /SP: on the new SEMAINT command and didn't notice
    any differences in the generated config.sys.  What does this
    parameter do?  Same ? for the /CID parameter with FSERVICE.
  5. I tried semaint in a DOS session and it seemed to work.  Is this
    a family app now?  Can I set up lightly attended installs of
    OS/2 this way?
6. If applying the SP fails on user exit, what do I need to do to
    cleanup and remove the stuff semaint put in?

Again, thanks for your response and thanks for any help you can give on
these questions.

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************

I'll answer what I can here....

1) No, you don't need to wait for the 2.11 refresh to run SEMAINT.  Just
make sure you use the /S2 parm.  Also, the README.INS says to use the
SEMAINT that came with the SP, not the one from the GA disks so update the
copy in your \CID\EXE directory.

2) XCOPY the display drivers into the CSD directory, not IMG.

3) I've never tried a CID MM installation so I'm not sure about it.  Just
looking at the diskettes however, it would appear that the two diskettes
that shipped with the 2.1 SP are a total refresh of the MMPM code.  As just
an educated guess, I would not copy the MM disks into the CSD directory.
What you'll probably need to do is put them in the IMG directory and just
rerun the standard installation process.  Again, I really don't know
because I haven't tried it and, as you've discovered, it's not documented
anywhere that I can find.

4) In case type wasn't just a typo in your append, the new parameter is /S2
not /SP.  I believe that it means "source number 2".  What I think it does
is points to the latest level of code so that SEMAINT can build the right
level of kernel and such when creating a maintenance partition.  I think
this is designed to address the problems we had building a maintenance
partition after 2.0+SP was installed on a machine.  In that scenario,
SEMAINT would build the maintenance partition from straight 2.0 and
wouldn't pull in the new kernel and stuff from the service pak 6055. With
/S2, it appears that it will copy the GA level code then go to the second
source and pull in any updates.  That should keep the maint. partition at
the correct/current level.

For the /CID parm on FService, I'm not sure what it does.  In some of the
testing of the SP, some IBMers including myself ran into some problems
during CID installations when diskette installs would work OK.  /CID must
tell FService to take actions unique to the CID environment to avoid those
problems.

In both cases, it's hard to say exactly what the new parms do.  They got
added rather late in the process and the only documentation I ever saw is
exactly what you see in the README.INS.

5) I don't know.  How adventurous do you feel? <g>  It might work....

6) Again, I don't really know.  To the best of my knowledge, there isn't a
back-out procedure if the SP install fails.  Removing the maintenance
partition created by SEMAINT wouldn't be too difficult, but it probably
wouldn't do any good.  The machine may be hosed-up since you might have a
mix of GA and GA+SP code so the odds of the machine actually being usable
are not too good.  I was running a test, and after using some incorrect
parms in the SP response file, I ended up with a Trap E when FSERVICE
completed.  My only recourse was to reformat and start over.....

Brent Allen - IBM Personal Systems Competency Center   Southlake, TX
**********************************************************************

[Reference to append at 21:05 on 94/02/25 by BRENT at DALVM41B ]

Brent-
  I did find a new feature for fservice not in the 3780.01Redbook nor in the
SP readme.  It is the /T parameter.  Turns out I needed this.  It was
documented in the 3783 Redbook.

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************

I almost always use the 3783 book so I never realized /T was missing in
3780. I have the newer -2 version and it's still not in there.  Sure does
make life hard when all the info's not available.  Glad to hear you got it
working.....

Brent Allen - IBM Personal Systems Competency Center   Southlake, TX
**********************************************************************

Brent-
 Actually, it was Sean at level 2 CID who pointed out the errors of my ways.
He deserves a big ATTABOY.  And so do you, Brent.  Thanks for your help.

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 134. SVGA on GW2K w/ATI ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Before I begin, just let me say that I am the type user that just likes
to have my system work when I turn it on.  I don't really enjoy dinking
around with the system settings and having to do a lot tweaking.  Having
said that, please excuse my ignorance.

I just recently installed OS/2 for Windows on a Gateway 66V with the ATI
Ultra Pro graphics card (1M) and the installation went fairly well.  Now
I want to be able to run at 1024x768x256, but I wanted to gather a
little information before attempting it.

A little background information:

1) Before I began the install, I changed the powerup configuration on my
graphics card to be VGA/PS2 mode 640x480 60MHz.
2) During the installation, I selected 8514/A as the adapter type.

Everything went fine during the installation and I have been running
without error for about a month now.  The system automatically came up
with 800x600 resolution for both OS/2 and Windows applications without
doing anything special or installing any additional drivers (which kind
of surprised me).  However, I think at that resolution the video is
running interlaced because I'm getting a lot more 'screen flicker' than
I was before I installed OS/2.

The current ATI drivers that I downloaded from Gateway (2.21 or
something like that) has PM drivers that I was going to try installing.
The steps that I know I have to perform include:

1) Run the mach32 install program from a full screen DOS session under
OS/2 and select to install the PM drivers.
2) Then run DSPINSTL.

Finally, I get to the point of the entire post.

Q1) First, for as long as I am running OS/2 on my system, do I have to
leave the powerup setting on my video card at VGA/PS2 mode 640x480 60MHz
or was it just for during the installation that I needed to do that?  In
other words, can I set it back to the Gateway Crystal scan 1572FS (which
has a refresh rate of 72MHz)?

Q2) How can I tell if the video is running interlaced or non-interlaced?
 If I am running interlaced, will changing the powerup configuration
help solve that problem?

Any and all help is greatly appreciated.

              Scott J. Heimer

               HEIMER@RCHLAND
              SHEIMER@RCHVMX2
               Department 4A6
               030-2  F212
                553-5372
**********************************************************************

1) Setting the power-up default to VGA is for the install.  You can change it
  after the install is complete.

2) I don't know of a way to positively determine interlaced/non-interlaced,
  but the flickering is an indication of interlaced.  Once you set your
  power-up configuration to a non-interlaced monitor, the flickering should
  go away.

Mark Thompson - Coal Services Corp., St. Louis MO
**********************************************************************


ΓòÉΓòÉΓòÉ 135. OS/2 Selective Uninstall? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We just received and installed a new PS/2 Server 195 (it's greaat!).  There's
just one problem.

OS/2 2.1 was preinstalled on this machine.  And whoever installed it
installed EVERYTHING including all of the productivity tools and GAMES!
But this thing is a SERVER and we'd like to reclaim the disk space these
components are using.  (Why would they install games on a machine intended
to be a file server?)

Anyway, is there a tool or at least a document we can use to safely
uninstall the unwanted components?  Note that OS/2 was PREINSTALLED, not
PRELOADED.  So the selective uninstall tool one finds on preload systems
is not present.

And would someone at IBM please pass this on to the PS/2 195/295 people:
How about just installing "bare minimum" OS/2 and letting the customer
decide how much of the accessories to install?

Thanks in advance..

Dave Gannon, Lead Programmer, Iowa DES
**********************************************************************

This isn't elegant, but you've gone too long with no response.

First, get the underlying files out of your directory structure.
    Go into <drive>:\OS2\APPS
              \BITMAPS
              \DLL
              \HELP
    and DEL from each, all the files you recognize as games.

Then, go to your GAMES folder.  Right mouse click on every icon
    you recognize as belonging to a game whose files you
    have removed.  Left click on the DELETE command in the
    menu and you are pretty well cleaned out.

Its may not be total, but neither should it be destructive
if you are very sure to use the OS2 tools and not DOS.  It's
safest (though slow) to use the drive icons, rather than the
command line which I'm always inclined to do.  When I do,
something bad usually happens to those little EA critters.

Good luck.

Ken Hammer, St. Johnsbury, VT
**********************************************************************

[Reference to append at 04:41 on 94/02/26 by IADES15 at OS2CUST ]

I missed this until I just saw the response by Ken.  There is a section
in the back of the Using Guide that will identify what modules belong to
games, and other subsets, since there is no selective uninstall I have
used this in the past to build a set of deletes to do this on several
machines.  If you have the CD of unline documentation you can cut & paste
from that to help with building such a file.

Jack Hiatt
The International Phoenix Alliance
<Team OS/2>
**********************************************************************


ΓòÉΓòÉΓòÉ 136. SEMAINT & FSERVICE ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Theoretically, if you apply a service pack from a maintainence OS/2 partition
then fservice is suppose to clean things up and allow you to reboot to your
upgraded OS/2.  But I can't seem to get this to work with the XR06200
service pack.  Perhaps someone could point out where I am going wrong.

Here is the sedisk command:
  semaint /S:j:\os2se21 /S2:j:\spse211 /T:c:\maint /b:c: /L1:c:\maint.log

Here is the config.sys line for fservice:
  set os2_shell=j:\spse211\fservice.exe /S:J:\spse211 /CID /R:c:\maint\rsp.fil

Here is my response file:
  **** Created Response File for XR06200****
  *
  :SERVICE
  :DIRLIST c:\os2\install\syslevel.os2
  c:\
  c:\*
  :ENDDIRLIST
  :FLAGS REPLACE_PROTECTED

Thanks for any help on this.  When I reboot after installing the service pack
it boots-up the maintanence OS/2 and restart fservice.  I have to boot up off
diskette and manually do cleanup now.

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 137. Second hard drive fdisk problem ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have a Compaq Deskpro 486/386m system. My primary drive is a 322 meg conner.
Added a second 504 meg Seagate. My current setup on the master drive is:
DOS 5.0 Bootable c:primary fat 60 <= used to have DOS 5.0 installed.
OS2 2.1 Bootable d:logical hpfs 258 meg
startable : primary Bootmanager 1
    none    : primary type 12   3

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Fdisk in OS 2.1 can see the 2nd drive.
Bios also sees it.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

(1). Under Fdisk said that all 504 meg on the second drive was a logical
   partition and saved/exit. Received message that an e partition was
  created and that I should now reboot.
When OS 2.1 came backup up it did not recognize my new e partition.
   Going back into FDISK I could see that the 2nd drive was all free space.
   Repeated procedure, making sure that I saved the new configuration.
(2)  Attempted to install the new drive as a primary partion.
(3)  reinstalled OS/2 making the 1st drive a C primary partition leaving
   the boot manager and bios partitons in place. Made the d partiton
  on the second drive primary and reinstalled OS 2.1. The results
were the same.

I called the vendor and was assured that since the drive is recognizable
in both OS/2 and the bios that the problem was with OS/2.

Does anyone have an explanation as to what the problem is?

Ron Bourassa 203-840-6437
**********************************************************************

Ron Bourassa,

> When OS 2.1 came backup up it did not recognize my new e partition.

I'm not certain this your problem, but did you format the newly
created partion after rebooting, _before_ trying the install?
I've been through an installation of a second disk, much as
what you are attempting and had no difficulty -  but I _did_
format newly created partitions...

Tim Wuthrich, The Upjohn Company
**********************************************************************

Tim, The problem is that the FDISK changes do not actually occur despite the
message  I get from OS/2 saying that it was successful. When I reboot and
get into FDISK it is just as if I hadn't saved the prior FDISK and I have
no way to refer to the drive. I.e. the drives icon doesn't show it and
E: receives a Sys015 when typed on the command line.

Ron Bourassa 203-840-6437
**********************************************************************

Ron,
I now understand what you meant -- unfortunately,  I don't
have any good ideas to try (other than to make sure the bios
definition agrees with the drive specs). Sorry.
Anyone else???????
Tim Wuthrich, The Upjohn Company
**********************************************************************

[Reference to append at 22:49 on 94/02/28 by CLDR015 at OS2CUST ]

We had problems with a ThinkPad docking station with a SCSI drive that was reco
gnized by OS/2 2.1 install, DOS booted from diskette, and exiting from the 2.1
install.  It was not recognized by OS/2 booted from the internal ThinkPad drive
.  The problem was the lack of SCSI support in CONFIG.SYS.  You didn't specify
how the Seagate drive is connected.  Maybe this will spark some idea.

Don Harmon, Red Kap Industries
**********************************************************************

[Reference to append at 14:55 on 94/03/02 by CLDR015 at OS2CUST ]

Ron,
I had a similar problem when trying to install a SCSI drive in my home
machine and it turned out to be a bad cable.  Don't remember what pin was
missing, but at least one was, and it would respond to FDISK, but when I
booted it was as if I had never touched the drive.

Jack Hiatt
The International Phoenix Alliance
<Team OS/2>
**********************************************************************

My drives are IDE, but it is worth checking out especailly since nothing
else I've tried woeked. Thanks for the info.

Ron Bourassa 203-840-6437
**********************************************************************

[Reference to append at 23:09 on 94/03/02 by TPA0003 at HONE81 ]

Ron,
 Don't know if this will help but I've seF know if this will help but Ive seen

 FDISK act strange
if the ABIOS.SYS does not contain (if needed) *.BIO files for your system.
This file is on the install diskette.  My example was on a PS/2 9585-ONG
and FDISK would not only fail to work but trash my reference partition also.
These files are extensions to the OROM bios and are e machine specifi
Contact your manufacturer.

Chuck Thomas Sunburst Bank Grenada MS
**********************************************************************


ΓòÉΓòÉΓòÉ 138. OS/2 2.1 Base install with a real WINDOWS migration ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Is it possible to do a OS/2 2.1 base install using RSPINST and a response
file and to request a real WINDOWS migration, when the real WINDOWS envi-
ronment is not on the station to generate but on a LAN attached applica-
tions server.
In other words could we specify for the  path of the real WINDOWS to be
migrated (in the response file)  a redirected drive?
To achieve this, the system to be generated will be 'SRVIFS attached' to
both the code server and  the application server
Thanks for your tips
Jacky GOLAY GEBEVA/SWITZERLAND
**********************************************************************

Have you tried the ExistingWindowsPath= keyword in your response file?

Brent Allen - IBM Personal Systems Competency Center   Southlake, TX
**********************************************************************

I am a Microsoft Beta Tester, and also do some alpha testing, and there is
nothing new about 3.11 upgrade not working under OS/2 for Windows.
None of the beta work, and to make it even clearer, I have Win 3.11 update
Alpha R3, that changes win 3.1 to win 3.1 32bit with several 32-bit applets
and api and updated dll's.  Microsoft is holding this back for Chicago Now.

John E Quigley II  Standard Register Corp  -- IS -- [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 139. 2/28 'A' version of 3.5 disk img 2.1 CSD  ??? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We downloaded the 3.5 Disk images of the OS/2 2.1 CSD on
Friday, 2/25.  Now today there is an 'A' version of these same
images.
Is there a difference?
Do we re-install the CSD?  Can we???

Any input appreciated.

Bill Pier  &:-{> of Hughes Aircraft Co. (714/732-8753 | [e-mail])
**********************************************************************

The only changes were to the disk labels- in the original ship,
the labels for the printer and display driver diskettes were transposed.
Also, references to an IBM Internal Use Only label printing utility were
(were going to be) removed. See the discussion in the OS2BETA CFORUM.

Don Hills   IBM New Zealand
**********************************************************************


ΓòÉΓòÉΓòÉ 140. Casey addresses windows 3.11 problem in PCWeek ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

PCWeek readers now know that OS/2 for Windows is incompatible with 3.11 (Feb.
28 issue, page 16.) Their labs tested it apparently before Boca, and they
also quoted a couple of sources:
---
 The next release of OS/2 for Windows, which IBM plans to ship this spring,
will address Windows 3.11 incompatibilities, said Wally Casey, director of
marketing with IBM's Personal Software Products division in Austin, Texas.
IBM "retained all the rights to clone all the APIs for all of the products
that Microsoft ships," Casey said.
 Microsoft officials denied changing code in Windows 3.11 expressly to
break IBM's OS/2 for Windows.
 "We had to develop Windows 3.11 before we ever saw OS/2 for Windows,"
said Paul Maritz, senior vice president for Microsoft's systems division
in Redmond, Wash.
---

->Rich Corbett; Mgr. Sys.; ABC Liquors, Inc., Orlando, FL   (NASPA:CORBRIC7)
**********************************************************************


ΓòÉΓòÉΓòÉ 141. SP install - new colors? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Did I do something wrong?  The README.INS(?) for the SP indicates that
the default WPS colors are different.  After installing the SP I don't see
any color changes.

Mark Thompson - Coal Services Corp., St. Louis MO
**********************************************************************

Mark,
   My belief is that the readme files are meant to apply to the
manufacturing refresh as well as the service pack.  In which case
I would expect different default colors if you install with a format
using the refresh, but that the service pack would respect and retain
your personal customization.  Could be wrong, but that thinking
explained it for me.

Leo Tornow - Northwest Pipeline Corp.
**********************************************************************


ΓòÉΓòÉΓòÉ 142. Drive Geometry over 1024 cyls ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I encountered some strange behavior trying to install OS/2 2.1 on
a Western Digital Caviar WD2540 IDE drive.  I tried both 2.1 GA and
2.1 for Windows.  Fdisk would not install Boot Manager at the end
of freespace, but would put it at the beginning of whatever freespace
was present.  With C: and D: partitions defined for example boot manager
would install in about the middle of this 540 meg hard file.  I also tried
putting this drive as a slave to a 340 meg master IDE drive.  Then I
could install OS/2, and partition physical drive 2, but OS/2 refused to
format the last partition.  Then it occured to me that perhaps the
problem is in the way Western Digital has defined this drive (we all
know these one inch drives only have one or two platters).  The WD2540
has 1048 cylinders, 16 heads, and 63 sectors per track.

My rusty memory would tell me that this is basically a fundamental DOS
limitation.  (And there are likely several DOS workarounds.)  And I can
see a couple of OS/2 possibilities:
  1.  Is the correct workaround to change the CMOS setup to only
     define 1024 cylinders  ?  (giving up about 12 meg of the 515 meg
     fdisk reports. -- strangely DOS says 507 meg)
 or 2.  Could HPFS be used for the partition that goes past 1024 cyls ?
     ( I doubt this because I tried leaving freespace undefined at
      the end of the drive and still could not format the last
      partition inside OS/2.)

TIA

Leo Tornow - Northwest Pipeline Corp.
**********************************************************************

>2.1 for Windows.  Fdisk would not install Boot Manager at the end
>of freespace, but would put it at the beginning of whatever freespace
>was present.  With C: and D: partitions defined for example boot manager
know these one inch drives only have one or two platters).  The WD2540
>has 1048 cylinders, 16 heads, and 63 sectors per track.

>My rusty memory would tell me that this is basically a fundamental DOS

Actually it is an INT13 limitation, which as we know is what DOS uses,
as well as OS2 under some conditions, and of course what the boot
process uses. Thus FDISK requires that bootable partitions, including
boot manager to be entirely in the first 1023 cylinders.
(See QA item CGXDF.) The OS/2 FDISK supposedly supports more than 1023
cylinders as long as no partition is more than 1023 cylinders.
I don't know about the DOS FDISK, but there was a definite bug in the
DOS4 FDISK which cause compatibility problems with DOS5...so always
use OS2 FDISK.
 Some controllers allow "sector translation" to be modified. You can
go on up to about 256 heads which will reduce the number of cylinders,
if your controller lets you change it at all. There is also some
"disk manager" driver software from places like maxtor which alter
what the addresses look like, but I've never used one.
 See also OS2 apar II060708 and DOS apars IR95257 and IR94445.

->Rich Corbett; Mgr. Sys.; ABC Liquors, Inc., Orlando, FL   (NASPA:CORBRIC7)
**********************************************************************

Thanks for the information, Rich.  That explains why boot manager
wouldn't go to the end of the drive.  (A habit I have picked up of
leaving 1-meg free even on DOS machines to make the OS/2 conversion
as pain free as possible.  It's sure easy for DOS users to decide they
need OS/2 if their neighbor has it. <g>)

When I try to format the last partition on this drive using the WPS
drives object I get a little popup saying something like the drive is
greater than 4096 megabytes.  From what I've heard so far I still
cannot understand why I can't format it as an Extended Logical drive.

Leo Tornow - Northwest Pipeline Corp.
**********************************************************************

[Reference to append at 15:16 on 94/03/02 by IL04688 at HONE82 ]

The problem (>1023 cyl) relates to booting only--as I understand it.  PC
when they boot use the ROM--which was configured to count to 1024 and not
beyond.  Once things are "up", you should be able to define the extra
space for an OS/2 partition but not access that area from DOS--which
retains the limit throughout.

Ken Prevo
**********************************************************************

>The problem (>1023 cyl) relates to booting only--as I understand it.  PC

I'm also working on the same problem on a Gateway Pentium.  The problem is not
only relating to booting.  In fact, we aren't trying to boot from the
partition at all...it's just going to be a data partition.  The OS/2 format
command returns an error as previously pointed out by Leo.

My quick solution was to make the 516MB partition a bit smaller (13MB in my
case), and it formatted just fine.  Losing 13MB doesn't really bother me, only
the fact that I burned some time trying to figure out what was wrong and how
it can be fixed.  Thanks for starting this thread...it came at the right time!

Brian Surdahl, Phillips Petroleum Co.
**********************************************************************

[Reference to append at 18:44 on 94/03/02 by IL04688 at HONE82 ]

The end of the drive is a problem that I have run into before also.
On our Server85 we had a problem which pointed at disk errors, so I
ran DISKTEST (note not Norton diskdoctor, it failed) letting it flag
bad sectors...it flagged the entire last cylinder! After that everything
ran fine, including sensitive things like diskdoctor, speeddisk, etc.
 APAR PJ09189 points at what the problem may be. Apparently OS/2 is also
trying to do a sector translation into it's own terms and may peek behind
the scenes to see what the real geometry is. Unfortunately it (FDISK) may
calculate what the last "real" cylinder is incorrectly and thus try
to use sectors which aren't there. They weren't real clear in the APAR,
but just knowing that the last cylinder may need to be flagged is enough.
I will always run DISKTEST on all newly FDISK/FORMATed drives from now on.

->Rich Corbett; Mgr. Sys.; ABC Liquors, Inc., Orlando, FL   (NASPA:CORBRIC7)
**********************************************************************


ΓòÉΓòÉΓòÉ 143. OS/2 2.1 for Windows installation ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

My customer has tried to installed OS/2 for Windows on a PS/VP 466
machines and experienced the following problem:

Everything goes fine until the system prompt for printer drivers.
When the printer driver diskette is inserted, a message box saying
that the DSC files could not be found.  Is this a known problem?
I've searched for the .DSC files on my own system and found that
those are related to display rather than printer.  The customer
also mentioned that the message box have the title from Display
Drivers.  Thanks.

Jackson Hui
**********************************************************************


ΓòÉΓòÉΓòÉ 144. LABELGEN program for labeling OS/2 2.1 CSDs ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I would like to print out the labels for the new OS/2 2.1 CSDs XR06200A.LBL).
It states within this file that you must use a label print function from a
program named LABELGEN. Where can I find this program?

Dale Radspinner, Simco Electronics @ NASA/JSC [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 145. Problems installing OS/2 2.1 on clone 486 from CD ROM ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Ref:

Have been attempting to help a friend install OS/2 2.1 from CD-ROM
on his home machine.  The CD-ROM is a Toshiba connect through a Media
Vision PA Studio 16 sound card...  I had to go out and find drivers
to place on install disk one to make the CD-ROM drive work, and
now the install process seems to go fine, but the system locks-up
when rebooting to configure (after OS/2 logo and Loading..., we see
a gray screen with clock mouse pointer, then mouse pointer goes away
and system is hung). Turbo mode, caching, and shadowing are disabled
per the read-me file.  The system is a 486/33, with the PA Studio 16,
20MB of RAM, a Diamond Speedstar 24x video adapter, I am not sure about
the hard drive, and also a 3.5 inch floptical drive....  Any suggestions
on what is wrong with my procedure/configuration....

Thanks,

Monty A. Queener
**********************************************************************


ΓòÉΓòÉΓòÉ 146. SYS1201 after installing MMPM/2 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I installed MMPM/2 on my OS/2 for windows system. When I boot I get:
SYS1201: The device driver "C:\MMOS2\SBPD2.SYS" specified in the DEVICE
command on the line 79 of the CONFIG.SYS file was not installed. Line 79
ignored.

Press Enter to continue.
SYS1201: The device driver "C:\MMOS2\AUDIOVDD.SYS SDAud1$" specified in the DEV
ICE command on line 86 of the CONFIG.SYS file was not installed. Line 86
ignored.

Press Enter to continue.

Both files are in the path indicated.

Dave Harding - State of Oregon
**********************************************************************


ΓòÉΓòÉΓòÉ 147. CID Redirected Install of XR06200 2.11 Service Pack ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I've been struggling the past week with getting a process to apply the 2.11
Service Pack (XR06200) via a redirected connection.  We currently have
the SRVIFS "thin client" setup to install 2.1 (via RSPINST.EXE) and other
products.  Unfortunately doing this with the CSD this isn't well documented.
I've tried to put together the various pieces of info and get it to work
to a point.  Basically it goes through and updates all of the files (status
bar), then starts updating printer/display drivers, then kicks up a big red
screen with the message "An error occurred while completing user exit:
X:\CSD\OS2SE21\XR06200\FIX\OS2\PRODUCT.EXE".  PRODUCT.EXE exists, I didn't
specify a user exit in the response file, and I have no other option at that
point than to reboot.  I recopied all of the CSD diskettes again.  Any
ideas?

Here's what I've done:
XCOPY A:\*.* X:\CSD\OS2SE21\XR06200\*.* /S/E  (for each CSD diskette)
Modified SRVIFS client #1 diskette with the following:
 PROTSHELL=X:\CSD\OS2SE21\XR06200\FS1.EXE
 SET OS2_SHELL=X:\CSD\OS2SE21\XR06200\FSERVICE.EXE /CID /R:X:\RSP\OS2SE21\XR06
200\CSDONC.RSP /S:X:\CSD\OS2SE21\XR06200
My CSDONC.RSP file looks like:
 :SERVICE
 :DIRLIST
 <default>
 :ENDDIRLIST
 :FLAGS REPLACE_PROTECTED

Thank You,
Scott Atwell - Analyst/Programmer - Farmland Industries, Kansas City, MO
**********************************************************************

I've been trying to do exactly the same thing and I've received exactly the
same errors.  Except that I can't get the CID process to update any of the
files on the workstation.  The log file says that the service process has
selected the correct subdirectories for service, then it unpacks RT_PATCH.EXE,
tells me it's updating the video drivers, then fails with the PRODUCT.EXE
error you have described.  Let me ask you a question: was your original OS/2
install executed with the "blue" disks or the "salmon" disks?  We installed
using the original blue disks and I think that's part of the problem.  If you
look in the DSPINSTL.LOG in your OS2 INSTALL subdirectory, you might find
that the error is explained here.  Fiddle with the version of the UNPACK2.EXE
file in the OS2 subdirectory and you might get somewhere.  It seems to use
the wrong UNPACK program when it tries to complete the video driver install.

How did you get it to update all the files?  That's where I'm stuck.  It tells
me that the service has been applied successfully, but nothing has changed
except the video drivers.  I agree that the documentation is poor.

Michael Laughlin  AlliedSignal Controls & Accessories [phone]
**********************************************************************

[Reference to append at 16:24 on 94/03/08 by FRMLSPA at OS2CUST ]

i had that same failure as well until I placed the DISPLAY Driver
diskettes in the same CSD subdir structure with XCOPY.  I cannot
find this step documented anywhere, except the mention that 'you
may be prompted to insert the display driver diskettes' during
normal installation.  good luck.              bt
**********************************************************************

Xcopying the display diskettes into the service directory was the key for
us fixing this problem also.  This problem has also shown up on pcs that
had the S316m drivers and some other hi-res video drivers.

Matt Hickman  Internet: [e-mail]   [phone]
**********************************************************************

I XCOPY'd the Display Drivers and Printer Driver Diskettes directly
into the X:\CSD\OS2SE21\XR06200 directory.  The first 13 diskettes
have a subdir structure of \FIX\OS2 and they're in
X:\CSD\OS2SE21\XR06200\FIX\OS2 directory.  Where did you copy your
Display and Printer driver disks???

To answer the "how did you get it to copy disks":  I had to make
two adjustments to my first attempt.  1) I tried (and would prefer)
to invoke FSERVICE directly from an OS/2 prompt (SHELL=CMD.EXE), but
could only get it to run if I set the SHELL=FS1.EXE (which means I
have to have a special Disk #1 to apply the CSD.  Normally disk #1
boots to a menu written in REXX to select what to install).  2) I originally
copied \FIX\OS2 for disk #1 to ...\XR06200\DISK_1, and #2 to _2, etc. like
you do with 2.1 Base.  It wouldn't copy files until I shoved everything
into the FIX\OS2 subdir structure.
- My UNPACK2.EXE is dated 1-29-94.
- Original 2.1 GA install was done via response file unattended via CID
 using SRVIFS.  The code put out in the \IMG\OS2SE21 subdir was the
 first released GA code (like 5 days after GA date).  DISK_4, DISK_5, etc.
 only have a file called BUNDLE which would indicate to me that it was
 the compressed version which I think is the "salmon"???

Scott Atwell - Analyst Programmer - Farmland Industries, Kansas City, MO
**********************************************************************

>I XCOPY'd the Display Drivers and Printer Driver Diskettes directly
>into the X:\CSD\OS2SE21\XR06200 directory.  The first 13 diskettes
>have a subdir structure of \FIX\OS2 and they're in
>X:\CSD\OS2SE21\XR06200\FIX\OS2 directory.  Where did you copy your
>Display and Printer driver disks???

Just Xcopy them into the same directory (XR06200).  Not exactly obvious,
but it works.

Brent Allen - IBM Personal Systems Competency Center   Southlake, TX
**********************************************************************


ΓòÉΓòÉΓòÉ 148. Re-install of 2.1 fails at desktop create ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I was running os/2 2.1 when my hard drive developed errors in the WINOS2
directory. Things got real bad so I re-installed changing the drive from
FAT to HPFS. The install from CD-ROM works up to the end where it says to
press enter for re-boot. The system hangs forcing a CTRL-ALT-DEL and re-boot.
Then I get a white screen with clock. Some times I get the Tutorial then
a trap E CS:EIP=0160:ff8d2a2. I have tried the makeini process, but that
fails to.Since this is a home PC IBM support is kinda short.

Can anyone help?

Don Callaway, Power Computing  [phone]
**********************************************************************

I GOT IT TO INSTALL! DON'T KNOW WHY, BUT A REFORMAT TO FAT AND MINIMUM
INSTALL WORKED. I STILL WOULD LIKE TO KNOW WHY HPFS ANF FULL INSTALL FAILS?

Don Callaway, Power Computing  [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 149. OS/2 4 Windows install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have a coworker who just installed OS/2 4 Windows on his home system.
After he installed OS/2 to his D: partition (without any real problems
that I'm aware of), he decided he wanted to reformat his C: partition
(with DOS/Windows) and add a Boot Manager partition.  He backed up the
partition, repartitioned and reformatted (FAT), and re-installed DOS &
Windows.  DOS & Windows still boot OK, but now Win-OS2 (or Windows under
OS/2, I guess it's not really Win-OS2, is it?) will not start.  It says
it cannot find FDISPLAY.DRV, which indeed does not exist on any accessed
drive.

Has anyone seen this before?  Does anyone know what FDISPLAY.DRV does and
where it should be or where it can be found?

Also, he is not happy with the OS/2 display driver that got installed.  (We
both use OS/2 at work, so he knows what it should look like.)  He says the
colors are all off.  He has a Gateway 2000 system with the SVGA display
circuitry on the motherboard, so he's not sure exactly what kind of display
driver should have been installed.

Is anyone familiar with this type of system and the display driver which
should be used?

Thanks for your help.

Steve Bassler, Allegheny Power
**********************************************************************


ΓòÉΓòÉΓòÉ 150. install disks after CSD ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I've got a strange sort of question. After I installed the CSD for OS/2 2.1
on my notebook computer, I decided that I should see if the APM stuff
would work any better. I went to do a partial install when I got to
thinking: What disks should I use to install from? The original 2.1 disks
or should I feed it the CSD disks? Well I tried the latter with no joy. I
would guess that means use the originals. But if I do that do I then re-
apply the CSD? (Since I know that the APM stuff was updated on CSD.)

Kevin Slater - USAir
**********************************************************************

Yes, any installs now begin with the original disks, then re-apply
the Service Pak.  I guess the only joy is that the Service Pak
now (it didn't in the olden days) checks file dates/times and
only updates the correct ones, thus saving you some time...     bt
**********************************************************************


ΓòÉΓòÉΓòÉ 151. SYS1217 UNPACK error with selctive install after SERVICE PACK ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We have just installed the 2.1 Service Pack XR06200.  Now, when we try to do
a selective install we get a SYS1217 error - The file cannot be unpacked with
this version of the OS/2 UNPACK command.  Where do we go from here?

PAUL WYLIE  M. BRYCE & ASSOC.
**********************************************************************

Much discussion of this is on the OS2BETA.CFORUM

Al Siegel gave this solution:

The solution is to have the SP version of UNPACK2.EXE in your OS2
directory, but named UNPACK2.SP, as well as a copy of UNPACK.EXE from
the GA, but named UNPACK2.GA. Then, depending on what you
trying to accomplish, copy one or the other of those to UNPACK2.EXE.

Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************

after having mulled this over, just keep UNPACK.OLD about.  When
you re-install the service pack, it will re-install the new one
for you... shame the new UNPACK didn't recognize BOTH formats...bt
**********************************************************************

These are the versions of UNPACK*.* that get refreshed by the ServicePak when
installed on top of a 2.1 "salmon" (later version) system:

 {C:\}dir unpack*.* /s

  The volume label in drive C is OS2 21+SP.
  The Volume Serial Number is 2626:6414

  Directory of C:\OS2

  1-29-94  1:36a   71680      0  UNPACK.EXE
  1-29-94  1:42a   77136      0  UNPACK2.EXE
      2 file(s)   148816 bytes used

 Total files listed:
      2 file(s)   148816 bytes used

Perhaps SERVICE, when examining a "blue" (earlier version) system, could have
done a different job? Better job?  Put both on?  Put only one on?  I don't have
a "ServicePak on top of blue" setup available to see what it would have done.

Jim Stuyck - J.D. Stuyck & Associates - Member, I.V. League - [phone]
**********************************************************************

I don't have a 'blue' system about either, but I suspect that since
replace is by name (and date/time delta), that the 'sp-updated-salmon'
UNPACK.EXE has replaced the 'blue' UNPACK.EXE, thus creating problems
when one goes to do selective install later from one's 'blue'
diskettes...and we haven't even gotten to OS2 for Windows yet...bt
**********************************************************************


ΓòÉΓòÉΓòÉ 152. Installing OS/2 2.1 SERPAK with stacker ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have the disks for the OS/2 2.1 SERPAK and have successfully installed
on a non-compress drive.  But I also have a machine with the operating
system residing on a stacked volume.  Stacker provides special instructions
for doing a base install which requires replacing disk two with one which
has minimally a different config.sys file.  Since the service pak install
grabs your current config file and then does not change it (I think this is
true, please confirm), can I just run the install on the compressed system
as I did on the other??  If not what do I need to do differently?
Thanks.

PS - using Stacker for OS/2 and DOS

Mike Held - WI DNR
**********************************************************************


ΓòÉΓòÉΓòÉ 153. Install OS/2 on PS1 - SVGA doesn't work ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I installed OS/2 2.1 upgrade on a 486/66 PS1 for a permanent OS/2 demo
machine at CompUSA in Sacramento.  OS/2 said it would install SVGA, and the
datasheet for the system said 1024x768.  When install complete (w/o errors)
video was at VGA.  I tried selective install, and it rapidly brought up a
(dos?) window, and returned error that SVGA not supported by hardware.

Similar msg on PS1 forum went un-answered.  This is a great system, but VGA
sure makes a crappy demo of the greatest software on earth!

Help - PS1 forum indicates video may have Cirrus h/w, which may need an OS/2
patch.  How do I get it?  Thanks

Charlie Kotan, TeamOS2
**********************************************************************

Charlie,
If that machine has a CL chipset in it there should be a program
available CLMODE that has to be run to set up the chipset before trying
to install highres drivers.  If you don't have it, it's available on the
Cirrus Logic BBS 510-440-9080.

Jack Hiatt
MARC-Life
Atlanta Ga.
**********************************************************************


ΓòÉΓòÉΓòÉ 154. OS24WIN and Gatway 4DX2/66V ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I'm trying to install OS/2 for Windows on a Gateway 4DX2/66V system.  I get to
the point where you pull the diskettes and reboot to OS/2 to complete the
install (starting with Disk5).  The system hangs on the reboot.  I have
all shadowing, external cache and turbo.  The system still will not boot.

Has anyone else had a problem with this box?

Chuck Heltzel, Tritec Info Svcs  (Team OS/2)
**********************************************************************

Chuck, its been a long time since I dealt with GW2K machines but from what
I can remember, you had to boot the machine with a DOS disk, run the setup
program for the monitor and change the refreash rate.  After doing this, OS2
should install and then you can redo the above and set it back to the default
rate.

I'm sorry but I can't remember more but rest assured, there will be other
appends regarding your message that will give more specifix info! :-D

John McMullen, TEAMOS2 and TIPA, MCI, Atlanta
**********************************************************************

[Reference to append at 20:56 on 94/03/10 by WZ00989 at OS2CUST ]

I installed OS/2 2.1 for Windows on my Gateway 4DX2/66V last December
from CD-ROM without any problems.

Scott Atwell - Analyst Programmer - Farmland Industries, Kansas City, MO
**********************************************************************

[Reference to append at 20:56 on 94/03/10 by WZ00989 at OS2CUST ]

It's probably not the Gateway itself but the ATI video adapter.  You have to
run the ATI INSTALL program from DOS and set the Power-Up Monitor Type to
"VGA".  Once the install is complete you can set the Monitor Type back to
whatever is appropriate.

Mark Thompson - Coal Services Corp., St. Louis MO
**********************************************************************


ΓòÉΓòÉΓòÉ 155. (no subject) ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

aSubject: OS24WIN and Gatway 4DX2/66V
Ref: Append at 20:35:56 on 94/03/10 GMT (by WZ00989 at OS2CUST)
>I'm trying to install OS/2 for Windows on a Gateway 4DX2/66V system.  I get to
>the point where you pull the diskettes and reboot to OS/2 to complete the
>install (starting with Disk5).  The system hangs on the reboot.  I have

My best advice would be to call the Gateway BBS and leave a private
message to the sysop asking him to post a message to you with the install
procedures.  Several people have done this and gotten good results.  My
understanding is GW won't post it in a public area on that board--for PR
reasons or whatever--and that you must request a copy.

Ken Prevo
**********************************************************************


ΓòÉΓòÉΓòÉ 156. Problem with CID Install of Service Pak ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have a CID install of the Service Pak running just fine except for one
thing. After the SP has installed, it displays the grey screen telling the
user to CTRL-ALT-DEL to restart the system. I assume that this should not
be showing up on a CID install, but rather it should go back to the batch
file controlling the process. Can someone help me with my problem?

Following is the batch file used to invoke FSERVICE:
x:
x:\fservice /t:c:\service /cid /s:x:\ /l1:c:\xr06200.log /r:x:\os2svc.rsp
c:
copy c:\service\config.s13 \config.sys
del c:\startup.cmd
copy c:\service\startup.s13 \startup.cmd
c:\os2\setboot /ibd:c:

Following are the contents of the OS2SVC.RSP file:
**** Default Response File
*
:SERVICE
:DIRLIST
<default>
:ENDDIRLIST

I understand that I don't have the directory structure exacts as stated in
the guideline. This is setup on a temporary basis until it works, then it
will be migrated to our normal CID system.

One other problem I found was that if the /s on the FSERVICE line came
before the /t, FSERVICE could not find the source files.

Jim Sauber, MN Mutual
**********************************************************************


ΓòÉΓòÉΓòÉ 157. Safe SP install ??? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I would like to get the SP installation right since there seems
to be lots to gain and the hazards lie in installing it wrong.

I've read  OS2MISC append by RRKurtz dtd 94/03/08
      Readme.txt from directory with the SP disk images
      Readme.ins from SP disk 1
      Readme   from SP disk 1 (no Readme.sp1 exists on mine)
      XR06200.XRF

That's enough reading;  time to take the plunge after satisfying
three questions:

1.  With lots of room on HPFS drive G:, what special do I have to
  do to XCOPY /s all of HPFS drive F: (home of OS2) so I can
  XCOPY /s it back to F: if the need arises?

2.  What is the README from SPDisk1 talking about when it says:
  "Added support for Boot Manager exists on a disk other than
   Disk 1.  The ability to delete and re-install the Boot
   Manager requires that you exit FDISK after you delete the
   Boot Manager and re-start FDISK to install Boot Manager again.
   This is true even if you are going to place it in the same
   partition.  This means you would have to re-enter the partition
   names."
  I have boot manager on Drive 1 of 2 physicals. ver2.1 works well
   #1: DOS is on FAT C:, data on FAT E:, and OS2 on HPFS F:
   #2: data is on FAT D:, data on HPFS G:, and data on HPFS H:
   When things settle down, H: will be the home for SWAPR.
  Will the SP installation require that I redo the Boot Manager?

3.  README.TXT (from the board with the disk images) refers to
  procedures 1 & 2 for all or selected partition installations.
  I have all of OS2 ver 2.1 on F:, but EA's etc. on the others.
  Doesn't that mean I can use Procedure 2 for drive F: and
  forget all the other complications?

Thanks for the ongoing help on this board, though I'm concerned
that it is becoming a venue for ghosts, goblins and naysayers.
Take a look at the fixes to 2.1 in XR06200.XRF and realize we
thought 2.1 was great;  and it was.

Ken Hammer, St. Johnsbury, VT
**********************************************************************


ΓòÉΓòÉΓòÉ 158. OS/2 errors 2025 and 2027 encountered when booting install disk ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Ref:

I apologize if this has been mentioned before...

In trying to install OS/2 for Windows, I get errors 2025 and 2027 as soon as
I try and boot from the installation floppy (drive A:). The only documentation
that I have seen for this refers to the BIOS I have on my machine, (which I'd
rather not have to replace if at all possible!!!). I have the 12/12/91 edition
of the AMI BIOS, version F, which I believe should be OK.

My machine is a 486/50 clone with 2 hard drives, the CD-ROM drive which comes
with the Soundblaster Pro package, Soundblaster and Videoblaster cards. I have
tried booting with/without the turbo setting with the same results. Also, I
have tried removing the 2nd hard drive from the hard disk controller card, stil
l
with no success!

Previously, I had tested the OS/2 Beta code, and I still have the Boot Manager
partition on my first drive from that time -- nothing else! Why would I have
been able to boot the beta code, and not the production version?

Any ideas would be gratefully appreciated -- I've been struggling with this
for a couple of months now!

Stephen Lane
**********************************************************************

I had these errors when trying to install OS/2 V2.1 on my machine at
home and it turned out to be a bad diskette drive.  Once I replaced
the drive everything was OK.  I had previously installed OS/2 V2.0 on
the same machine without problem so the drive must have "gone bad"
sometime in the next year.  This was a 135mm (5.25") drive.

Bob Wardle - Commonwealth Bank - IBM Australia
**********************************************************************

[Reference to append at 21:39 on 94/03/14 by STEPHENL at TOROLAB6 ]

SYS2025: A disk read error occurred.

SYS2027: Insert a system diskette and restart
the system.

Most times this ends up being a bad install disk.  Try to copy the
diskette under DOS and see if it copies ok.  Then, try booting from the
copied diskette.

If your OS/2 is the CD diskette version you can use LOADDSKF
to create another copy of Disk 0 under DOS.

Ken Prevo
**********************************************************************

[Reference to append at 21:20 on 94/03/14 by SHABOBW at SYDVM1 ]

I have both a 3.5" and 5.25" drive, and got the same problem with BOTH!
I can use both drives under DOS/Windows. Could both drives be bad,
or should I check the floppy controller?

Stephen Lane
**********************************************************************

[Reference to append at 00:26 on 94/03/15 by WZ01343 at HONE82 ]

I tried creating disk0 from the OS/2 for Windows CD using LOADDSKF, and
using that, but the 2025 and 2027 errors persisted, both on the 3.5" and
5.25" drives.

Stephen Lane
**********************************************************************


ΓòÉΓòÉΓòÉ 159. TZ environment variable ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 I have the problem to set-up the Date and Time in a PS/2 under OS2 V2.1
using C++, and having received a string from a Master Clock like:
"1961/12/12-00:03:15.8+10:15"
"YYYY/MM/DD-HH:MM:SS.T+HH:MM"  T being 1/10 secs (to ignore,
                +-HH:MM being the time shift from GMT

 I'll decode the above string and use the DosSetDateTime.  But
what about the TZ environment variable ?

On my PS2, TZ=NFT-1GMT  I could not find any info on NFS,ADT.. etc..
I learnt that these codes were not normalized anyway.

To day in France local time is +1GMT and also +1 for winter that makes
+2GMT.  The questions are:

1- What does mean TZ=NFT-1GMT ?
2- Is the winter time linked to TZ ?
3- Are the C functions localtime() and gmtime() related to TZ ?

 Thanks in advance for any hint       BDI
**********************************************************************

pPDATETIME points to a DateTime data structure. Structure is:
Hours (UCHAR) current hour (0-23)/ Minutes (UCHAR) current minute (0-59)
Seconds (UCHAR) current second (0-59)/ Hundredths current hdrths of sec
(0-99) / Day (UCHAR) current day of month (1-31) / Month (UCHAR) current
month of year ( 1-12) / Year (USHORT) current year / TimeZone (SHORT)
the difference in minutes between the current time zone and GMT. Positive
for TZ west of Greenwich, and negative for TZ east of Greenwich. A value
of -1 indicates that the TZ is undefined / DayofWeek (UCHAR) current day
of the week ( 0-6; 0=Sunday )
Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************


ΓòÉΓòÉΓòÉ 160. Append at 14:44:48 on 93/11/29 GMT Weak Memory ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have also experienced many of these trap 2 explosions on several
attempts to get os2.1 on my clone. Is there any way to try and weed
out this weak memory before os2 finds it, since it checks out o.k.
with the boot diagnostics and windows does not complain ?
**********************************************************************

There is a REXX program around that exercises all memory.  But, you'll
still need to decode the memory address in the Trap to determine the
failing part.  Pick up a copy of that program and let it run overnight or
until it breaks.  Copy the memory address and figure out which bank.
Often, the easiest way to determine a failing chip is with an extra SIMM
or swapping the current one around.  A really good OS/2 memory exerciser
would be great, wouldn't it.

Is all you memory in the clone the same?  Different speeds and even mixing
3-chip and 8-chip SIMMs can cause problems.  Thats timing related more
than acutal chip failure.

Ken Prevo
**********************************************************************


ΓòÉΓòÉΓòÉ 161. Matsushita CD-ROM drivers ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have just bought a Multimedia PS/1 with a Matsushita CD-ROM.
It is presently installed with DOS-Windoze, does anybody have heard
of OS/2 device drivers for OS/2.

DG - OS/2 fan.
**********************************************************************

Matshushita Electric Industrials owns Panasonic.  Follow the readme
for Panasonic install. I think you will find to use the statement
BASEDEV=SBCD2.ADD in the instructions.

Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************


ΓòÉΓòÉΓòÉ 162. Difficulty using "SVGA" command after applying ServicePak ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Maybe someone can help me... I have just applied the OS/2 2.11 Service Pak
and (following the instructions) wanted to execute the "SVGA ON" command
to set up a SVGADATA.PMI file.  According to readme.ins, this command is
to be executed within a FULL-SCREEN DOS session.  I attempt to do just that
-- i.e., I enter a FULL-SCREEN DOS session and type SVGA ON
I get back the error message that this command can only be executed within
a FULL-SCREEN DOS session.  Needless to say, I find this most puzzling
and perplexing...  Can anyone help out?
THANKS in ADVANCE.

Zvi Weiss
**********************************************************************

Zvi,
Have you attempted 'SVGA ON' in a FS DOS SESSION found in the Command
prompt folder?
What computer hardware do you have?
What do the lines in the config.sys file concerning Video say?

Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************

Ye, I made sure that I was in a Full-Screen DOS session before I tried to
use the SVGADATA ON command... And, no there were *no* special changes made
to the CONFIG.SYS file.  I did get in touch with IBM support and the fellow
explained to me that the documentation was mis-leading.  The command was
**only** meant to be used for SVGA monitors.  As I have an XGA, the
entire section did *NOT* apply to me.  I thanked him ......
Note: it WOULD have helped to have been clearer in the Doc's for the
ServicePak about this point, to begin with....

Zvi Weiss, Automatic Data Processing, Inc. -- Jersey City, NJ
**********************************************************************


ΓòÉΓòÉΓòÉ 163. 540 IDE's ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I attempted to install OS/2 2.1 for the past three weekends.
My new machine came with MS DOS6.2 + Window 3.1 and all  drivers
installed.  I tested some software and a couple of CDROM appl.
to  make sure everything worked before  I started to installed
OS/2.  I have since burned one hard drive(a MAXTOR 540A) and replaced
it with the one I have now(a Western Digital).  My OS/2 installation
consistently failed at the end of phase 1, after rebooting, and two
OS/2 logo screens(with loading...msg, the whole machine just stop
cold.
I have tried almost everything timing setting mentioned in this
forum, i.e. reset wait states, disable external cache, slow the
machine down to 33Mhz...etc to no avail. I tried dual boot, then
repartition to go with Boot mgr  and HPFS for the OS2 partition only.
The same thing happened each time, failed at the phase 1 rebooting.

Could anyone help explain what the OS/2 installation pgm is trying
to do after 'loading...' at that point?  I want to use OS/2 but
am extremely frustrated to find out intolerant the OS/2 install
is toward non-IBM machine.
Please help....
My hardware configuration:
============================
ALARIS 486SLC 2-66 VLB w/128K cache
540 Western Digital IDE
VLB IDE CONTROLLER
16mb  Memory(4MB * 60NS SIMM)
1992 AMI Bios
Toshiba CDROM
Spider Black Widow 2mb VLB VGA
Diamond Sonic Sound card
3.5" 1.44MB drive
**********************************************************************

Paul Golden or Jack Hyatt can probably give a better response.  They were
just through the hassle of a Maxtor 540 and OS/2.  I believe part of the
problem was that IDE wasn't built to handle that large a drive.  Your
switch may have continued that problem.  There are DOS drivers for these
internally divided drives but I don't know of an OS/2 driver that supports this
scheme.

How is your drive configured?  If it is one large drive, that may be the
problem.  If you go over 128meg on a FAT partition you start paying a
cluster tax, anyway.  The part after the loading is, to my understanding,
the point where the loader is shifting from using DOS I/O services to OS/2
drivers.  I can only guess that your controller/drive combo may be
confusing things to the point of crashing.  You may want to edit the
CONFIG.SYS for OS/2 from DOS to use the INT 13 driver.  This driver often
can provide a "work around".  But, try to post your FDISK setup and it may
get someone on the right path to resolve your problem.

If you need that much space on a single drive, I guess there's
limited choice in  ╡╙p╥Йр╥Ё ╕в┌СЦthe matter.  But, a two drive solution does has some advantages at a
similar cost.  A pair of 300-400 drives isn't far in cost from the 540's and
two drives can be a big advantage with OS/2.  If you want what you have,
maybe a swap to SCSI would be your best solution.

I hope/expect you'll get a much better answer.  But, this may get you going
along the right path for getting OS/2 up.

Ken Prevo
**********************************************************************

[Reference to append at 01:36 on 94/03/16 by MLIU at BLDVMA ]

Thank you, Ken.

When I tried the Dual Boot install, I had 120 MB C Drive(primary),
384 D drive(logical ext.).   When I switched to Boot Mgr install,
I had the following FDISK config:

   Boot Mgr              1mg
   Bootable   C:  Primary,  DOS_6, 50mg FAT
   Installable C:  Primary,  OS/2, 70mg HPFS
         D:  logical     382mg FAT

The last try we did ( I got a colleague to help who has bought a
similar machine, different IDE controller and Video card, but uses
DOS/Window only) was to blindly hitting the ENTER key at the
black screen which finally made the A drive status light blinking,
we then feeding it the rest of the installation diskettes(it was wild...)
just to see how far we could go.  Well, we got through the first 13
diskette and started feeding the A drive with a device driver
diskette and it failed to continue.  We verified all jumpers on the
Spider Video card are set as default.  No OS/2 driver has been
installed yet. We've tried both 8518 and 8512 displays.

If all else failed, I would probably go DOS/WINDOW instead of
swapping another yet another hard drive.
The vendor has verified that the machine worked
perfectly with all components when it left the shop...

Any suggestion is appreciated.
Moonli Liu, ISSC
**********************************************************************

[Reference to append at 01:36 on 94/03/16 by MLIU at BLDVMA ]

Have you tried disconnecting the sound card?
Is there IRQ contention problems?
What chipset is the video using?
Is the video set for VGA?
What are the config.sys statements concerning video?
Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************

[Reference to append at 17:14 on 94/03/16 by MLIU at BLDVMA ]

Unless some else jumps in with a better answer, I'd say that you decision
to run DOS/Win on the 540 is a smart decision until the new IDE2
controllers come out that handle the larger drives without any "cheating".

I remember a thread between Jack and Paul on the 540's and they tried
about everything and failed to make it work with OS/2 and finally
exchanged it for a different drive.  From the prices I see around, it
looks like the 540's are being dumped.  Probably  that is because of their
compatibility problems.  I hope it works out for you over time.
"Semi-compatible" situation can often drive one to the bottle...<g>

Ken Prevo
**********************************************************************

>I remember a thread between Jack and Paul on the 540's and they tried
>about everything and failed to make it work with OS/2 and finally
>exchanged it for a different drive.  From the prices I see around, it
>looks like the 540's are being dumped.  Probably  that is because of their
>compatibility problems.  I hope it works out for you over time.
>"Semi-compatible" situation can often drive one to the bottle...<g>
>
>Ken Prevo
Ken,
  I just installed a 545 MB Conner on my system with a promise DC420
Controller, and have no problems.  The drive is set up as follows.
Boot Manager 1 Meg
Dos      5 Meg Bootable  C:
Data Drive 499 Meg       E:
Swapper   40 Meg       F:

Cesar Ventura
TIPA
**********************************************************************

That certainly sounds like a nice setup.  The Maxtor was/is most of the
problem, I think.  Paul Golden would know more about it.  He and Jack
struggled to try to get one going.

Ken Prevo
**********************************************************************

[Reference to append at 21:47 on 94/03/16 by WZ01343 at HONE81 ]

Ken,
The problem that Paul and I experienced was on a Maxtor 540 SCSI that
turned out to have a major manufacturing problem.  It would only work on
1 particular Adaptec adapter, and that ain't the one I had.

Jack Hiatt
MARC-Life
Atlanta Ga.
**********************************************************************

>The problem that Paul and I experienced was on a Maxtor 540 SCSI that

Nothing like almost getting it right, is there...<seg>

Ken Prevo
**********************************************************************

[Reference to append at 23:32 on 94/03/16 by NANR6GN at HONE82 ]

Cesar

I have the same problem that
many do: install OS/2 in a 540MB drive (more than 1024 cylinders).

You seem to have done it. Is any of your configuration non-standard? In
other words, do you have any SMART IDE controller for your Hard Drive?

I've been trying to install OS/2 for a week without success. The FDISK
part of the installation doesn't let me choose the partition I'd like.

Do you have any comments of your installation (what you did, the set up,
etc)?

Thank you in advance for any hint.

Regards

Luis Fernando Soeiro
**********************************************************************

Luis,

1. Consult the documentation that came with the harddrive and find out
how many Mb are within the first 1024 cylinders.

2. Ensure that any bootable partitions  primary or OS/2 extended are
created at the beginning of free space and within the above limit.

3. The space beyond can be logical partions used for data.

Ray Latulippe (Boca Electronics Support Team)
**********************************************************************

[Reference to append at 19:44 on 94/03/25 by E00834 at RIOVM1 ]

>Subject: IDE 540
>Ref:   Append at 23:55:32 on 94/03/16 GMT (by NANR6GN at HONE82)
>Cesar
>
>I have the same problem that
>many do: install OS/2 in a 540MB drive (more than 1024 cylinders).
>
>You seem to have done it. Is any of your configuration non-standard? In
>other words, do you have any SMART IDE controller for your Hard Drive?
>
>I've been trying to install OS/2 for a week without success. The FDISK
>part of the installation doesn't let me choose the partition I'd like.
>
>Do you have any comments of your installation (what you did, the set up,
>etc)?
>
>Thank you in advance for any hint.
>
>Regards
>
>Luis Fernando Soeiro
Luis,
 I didn't do any thing special.  What I did is use DOS FDISK,
and told it to use the whole  DРdrive for the partition.  I then Booted OS/2 and redid the Fdisk.
 It still would not let me DРput the Boot manager at the end of the disk where I prefer to
have it.  The CMOS was set up  DРas per the Manufacturer's instructions.
 Sorry It took so long to answer, but I had a Heart attack on
3/23, and haven't been on line till this Monday.  Just catching up on the messages.

Cesar Ventura
TIPA
**********************************************************************

Cesar,
Hope the attack wasn't too serious, and that you are recovering well
from it.  Take care.

 Jack Hiatt
MARC-Life
Atlanta Ga.
Team OS/2    T.I.P.A.
**********************************************************************


ΓòÉΓòÉΓòÉ 164. How I can delete LPT1-file ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 I have HPFS-filesystem in the server. Now there is about 10 files
which name is LPT1 or LPT3.

How I can delete them and find people who has done them ??

Timo Ketola
Oy Tietokonepalvelu Ab

This append was created on the External IBMLink system by
Oy Tietokonepalvelu
**********************************************************************

Timo,
We endedup with a file called NUL on one of our HPFS servers.  I ended up
having to FORMAT the partition to get rid of it!  I tried DEL, MOVE, MOVE
to DEV\NUL, Drives, MRFILEPM, WINOS2 File Manager, PC Tools, GAMMA Tech
DELTREE, etc.  I was afraid to do too much with GAMMA Tech Sector editor.
I could not get rid of it.  Support replied that I might be able to get rid
of it by writing my own C program to delete it.  I formatted the partition.

Mike Long - ISU/CARD - [e-mail] - TEAMOS2 - OS/2 Accredited
**********************************************************************

We have had files called COM1, LPT1 and NUL on servers in the past. The
only way we have found to get rid of them is using the DOS version of
Sterling Software's Intelligent Backup. Intelligent Backup has file
manipulation utilities in it.

Jim Sauber, MN Mutual
**********************************************************************


ΓòÉΓòÉΓòÉ 165. Install OS2.2.1 on Getway2000 4DX-33V ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

  I am trying to install OS2.2.1 on a Gateway 2000.
I have partitioned my 250 meg hard disk in the following configuration

Name    Status      ACCESS       fs TYPE      MBYTES
      STARTABLE    :PRIMARY      BOOT MANAGER    1
DOS 6.0   BOOTABLE    C:PRIMARY      UNFORMATTED    19
OS2.2.1   INSTALLABLE   D:LOGICAL      UNFORMATTED    60
      NONE      E:LOGICAL      UNFORMATTED    163

When trying to format the disk during the INSTALL of OS2.2.1, there is
a system error and the log contains the following message
     Greater than 20 MEG partition exists
After restarting the installation program, I go back into FDISK and
the OS2.2.1 is no longer set to INSTALLAbLE it is set to BOOTABLE

Any ideas on how to fix my problem and install OS2.2.1
Ken Crane
**********************************************************************

Ken,
As you install do not go into FDISK.
During disk 1 it will tell what drive OS/2 will install on in a panel,
the drive letter  will be in a shaded box. If it is other than where
you want - change it. Then later on - in disk 2 it will ask if you want
to format the drive - at that time say yes and continue install.
Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************

[Reference to append at 03:05 on 94/03/18 by CRANE at POKVMCR3 ]

Ken,

Have you tried making the OS/2 partition a primary partition as well?
Then you would set that Bootable and installable and format it.
What happens is Drive C: letter will be assigned to either the DOS
partition or the OS2 partiton depending on which is booted. This way
one OS can not see the others drive.

Ray Latulippe (IBM)
**********************************************************************


ΓòÉΓòÉΓòÉ 166. Trap error messages on OS2 2.1 install. ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have tried several times to install os2/2.1, and everytime it fails
to complete with trap errors. The latest was a trap 000e at location
##0160:fff5fbd5-000d:9bd5. 60000,9084.
I have yet to be successful in installing this product on my clone.
I guess it was meant to be only installed on IBM products. The
rather frustraing thing about the aborted installs, is that os2
assumes that it is going to complete, because the first thing the
install does is set up the system to boot os2, so when the install
dies you can not boot anything. Fortunately I have gotten very good
at recovering from these disasters. Any ideas on what I can do ?
I have followed all of the install instructions.
I guess I can wait for the next version of windows to come out.
**********************************************************************

Well I guess you could wait for the next version of Windows to come out,
or you could possibly post detailed information about the hardware you
are trying to install on and maybe someone can give you a hand.  The trap
you are seeing is almost always a hardware conflict somewhere.  I've
successfully installed 2.1 on about 125 homemade clones with very little
problem, once we knew what hardware conflicts we might face on various
units.

Jack Hiatt
MARC-Life
Atlanta Ga.
**********************************************************************

[Reference to append at 01:33 on 94/03/20 by PRHERB at KGNVMC ]

>I have tried several times to install os2/2.1, and everytime it fails
>to complete with trap errors. The latest was a trap 000e at location
>##0160:fff5fbd5-000d:9bd5. 60000,9084.
>I have yet to be successful in installing this product on my clone.
>I guess it was meant to be only installed on IBM products. The

I think I'll see that address in my dreams.  I believe the IBM Q&A files
all reference it to a hardware problem.  In my instance is was a WD
Ethernet card that had memory that was to slow to survive under OS/2.

I think your reference to it working on IBM products isn't correct.  One,
there are IBM products that do have OS/2 problems as much as any clone.
Two, many clones are junk--plain and simple.  If they run DOS, their
designers quit--that doesn't mean they created an industrial-grade
product along the way.

Best advice I can give is simplify and then try again:
 -remove all cards from the system not required to boot
 -follow the admonitions in the read me about speed, cache etc.
That should make the install happen.  Trap-E (Page Fault) doesn't always
seem to end up being what it appears--at least from my limited experience.
If the install still fails with the system stripped, you might give the
INT-13 HD drivers a try; as a flyer-- it couldn't hurt.

But, my best advice is to call the 800 number.  I sure had good
experiences from that when I was first installing OS/2.  And, if you find
someone who's helpful make a note of his name and try to get back to
him/her,if you have to call again on the same problem.

OS/2 installs sure can be frustrating.  But, stick with it and I'm sure
you have it up and running and find it to be superior.  The first day I
ran OS/2 was an amazing joy that I'll long remember as one of the most
exciting times I ever spent with a computer!

Ken Prevo
**********************************************************************

[Reference to append at 01:33 on 94/03/20 by PRHERB at KGNVMC ]

First check out what BIOS you are using via page 167 "Installation Guide"
you must have the correct level (including Keyboard Controller) for your
BIOS. ALso if you have a Micronics mother board refer to page 169.
Next prior to install you must do the following.
1. Go into the BIOS and disable disk cache, shadow ram, Turbo mode.
2. Set the system to VGA 640 x 480.
3. If installing from CDROM refer to page XVII-XVIII "Installation Guide"
4. You will need the drivers for your sound card as well as for the CDROM
5. The above settings can be changed back after installation is complete.

Ray Latulippe (IBM)
**********************************************************************


ΓòÉΓòÉΓòÉ 167. OS2 trap e and append by gmt ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

The hardware I am using is a Austin computer 486/dx250 with the following
installed options:
1.) STB Horizon VLB graphics card
2.) Pro Audio 16 Sound Card
3.) Texel CD rom drive (the one supported by os2) this is how I tried
installing os2. It is hooked to the scsi port on my sound card with
the correct .add file on the installation disks.
4.) 8mb 70 ns ram.
5.) 256 kb cache
6.) Two hard drives, western digital 250mb and 340mb.
7.) Colorado external tape backup unit.

I once painstakingly wrote down all of the info on the screen for the
trap message and read it back to the os2 support. They told me that it
could be a hardware conflict, so I made disks from my cd rom(this kind of
defeats the nice features of the cd rom), then I removed all of the
hardware I could and have my computer still function. I still could not
install os2.
Any advice would be greatly appreciated. Thanks for your help.
**********************************************************************

>2.) Pro Audio 16 Sound Card
>3.) Texel CD rom drive (the one supported by os2) this is how I tried
>installing os2. It is hooked to the scsi port on my sound card with
>the correct .add file on the installation disks.

The Texel has long been a "good" CD for OS/2.  It was one of the first and
best early choices.  So, the problems must be related to your PAS16 and
it's driver.  I assume that you have a current or current enough driver.
If not, the latest should be available from their BBS or on the PCCBBS.

The only thing left is addressing.  Is the driver configured for the right
port and IRQ?  Is that configuration conflicting with existing IRQ's or
ports?  I imagine that's your problem area.

There are a number of programs around for DOS that do a system analysis
and report active interrupts.  These sometimes miss something that doesn't
yet have it's driver installed.  But, if you boot under DOS and load all
drivers, it should be accurate.  I'd guess you may be using the
printer interrupt.
Ken Prevo
Every morning for breakfast, eat a live frog!  Then the worst
that can happen to . you that day is behind you. -- MARK TWAIN
**********************************************************************

    Also keep in mind that the audio driver can cause a Trap 00E if
not the original MMOS/2 driver.  I have run the Media Vision driver with a
PRO AUDIO 16 and a NEC single speed external CD Drive.  I had no problems
with them.

    I believe that if you looked you would find out that the PS/1 and I
think Valuepoint lines are basically clones.  That's why my PS/1 is using a
CLARIS Chipset for SVGA, My CDROM is a PANASONIC CD-563, etc..  I could be
wrong but I also believe the Motherboard was manufactured overseas.  I
purchased it because I know IBM will fix it where ever I drag it on
contract, and it really is a nice piece of engineering.

Paul E. Sobanski  "Team OS/2"
**********************************************************************


ΓòÉΓòÉΓòÉ 168. How to change to VGA display option ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Last year (8/27) I got an answer to this question.  Could someone
please explain how I (internal user) can get to the archived forum
OS2INST 937CFORU.  Or even better could someone explain how to change
from SVGA to VGA, from command line, because my machine won't boot up
after I changed the video to SVGA.   THANKS!!

John Henckel
**********************************************************************

John,

You can recover to VGA by doing the following!!!

1. Insert the OS/2 Installation diskette into drive A:
2. Restart the computer
3. When prompted, remove the Installation Diskette, and insert Disk 1
then press enter.
4. When the first blue screen appears, press ESC.
5. Change to the C:\os2 directory on your hard drive.
6. Type SETVGA C: (If OS/2 is installed on a different drive, substitute
that drive letter for C).
7. Follow the instructions on the screen.
8. When the installation program is complete, remove the diskette from
the diskette drive.
9. Press Ctrl-Alt-Del. Your system will restart in VGA mode. You can now
reunstall an SVGA driver per page 337 "Using the Operating System".

Ray Latulippe (IBM).
**********************************************************************

Thanks,

John Henckel
**********************************************************************


ΓòÉΓòÉΓòÉ 169. Response-File Install Problem ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Help ||
I try to make a response-file-installation from a OS/2 2.1 CD-ROM.
I've created and modified tha samlpe "sample.rsp" and done the described
changes on DISK 1.
The Problem is :
After inserting DISK 1 and the display of the sign "Please wait.."
the installation procedure stops without any error message.
The prompt after stop is :  ЫD:\os21_049\DISK_1\!_

This append was created on the External IBMLink system by
Thanks for your help |||
T.Tschopp / M.Hug
Interact Consulting AG
**********************************************************************

T. Tschoop,
Where were the directions located that you were following?
Do you have the Automated Installation for CID enabled manual
              GG24-3783-01?
What changes did you make to the response file?

Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************


ΓòÉΓòÉΓòÉ 170. CDROM Installation ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Is there something I am missing when I try to install OS/2 2.1
from CD onto a Model 95?  I get to the point that I take the diskette
out and hit enter.  It comes up at the OS/2 ring screen and hangs.
This is the salmon version.

Alan T. Wiley
**********************************************************************

Alan,

Have you edited the copy of disk one per instructions on page XVII-
XVIII of the "Installation Guide" Also if you have XGA please reset
the system to VGA 640 x 480. Try this and see if it works. It might be
that you have a downlevel BIOS and you might need to make some changes
to disk one!

Ray Latulippe (Boca Electronics Support Team)
**********************************************************************

I tried it again selecting VGA resolution and still hangs at the same
place.  I know it is detecting the CDROM because the program asks me to
insert the CD into the drive.  I also see it copying files.  Where it
hangs is after selecting the system configuration.  It leaves the
message  "OS/2 Setup and Installation is updating the system
configuration.  Please Wait."

|PROBLEM FIXED:
|the problem turned out to be an 8mm tape drive that was hooked up
|at the same time.  OS/2 wants to know about everything that is
|attached to your computer...even though the tape drive reported
|in to the system configuration, it still needed a device driver
|in the OS/2 config.sys file.

Alan Wiley
**********************************************************************


ΓòÉΓòÉΓòÉ 171. CID Redirected Installs ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Hi,

I am trying to learn how to do CID redirected installs
and I am having a problem. I pretty much followed the
examples in the manual, execpt some name were changed
for OS/2 2.1.

I have two things which concerns me at the moment.

1. I get a message that OS/2 install ok, but
when I look a the C drive it leaves a bunch
of *.ADD files in the root.
Is this normal? It does not happen on a
diskette install.

2. When going to the second step, LAPS with
/e:maint. The whole process fails with
incorrect program invocation.

Does anybody have any suggestions on what I may be doing worng?

Bradley S. Gibson
**********************************************************************

Bradley,
Are the .ADD files for a SCSI or CD-ROM?

From the automated installation for CID enabled OS/2 V2.X March 1993
PG. 22 states: Laps /E: - executing environment for LAPS
   Maint - Executing environment was a CID hard disk initiated OS/2
       V2.X system. LAPS uses a special OS/2 V2.X Dll to build
       the IBMLVL.INI file.  This DLL will not run in a regular
       OS/2 V2.x system.

Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************

[Reference to append at 13:22 on 94/03/25 by IL70332 at OS2CUST ]

Bradley, What does the command that is invoking the LAPS install look
like?  Could you post it here?

Julian Swales
ISM - Information Systems Management Corp. CAWSTSDT@IBMMAIL
Regina, SK, Canada, S4S 7H1 PH#:[phone] Fax#:[phone]
**********************************************************************

[Reference to append at 13:22 on 94/03/25 by IL70332 at OS2CUST ]

>1. I get a message that OS/2 install ok, but
>when I look a the C drive it leaves a bunch
>of *.ADD files in the root.
>Is this normal? It does not happen on a
>diskette install.

Yes, this is normal in after a response file install.  One recommendation
is to add "UserExit=ERASE \*.ADD" to your response file to have it
automatically erase those files for you.

Brent Allen - IBM Personal Systems Competency Center   Southlake, TX
**********************************************************************

[Reference to append at 13:22 on 94/03/25 by IL70332 at OS2CUST ]

>1. I get a message that OS/2 install ok, but
>when I look a the C drive it leaves a bunch
>of *.ADD files in the root.
>Is this normal? It does not happen on a
>diskette install.

It happens to me, too.  I just live with it.

>2. When going to the second step, LAPS with
>/e:maint. The whole process fails with
>incorrect program invocation.

Known problem.  Get IC06187.

John W. Kennedy - Hoechst Celanese - TIPA - Team OS/2 - The OS/2 Hobbit
**********************************************************************


ΓòÉΓòÉΓòÉ 172. CD-ROM Selective Install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have OS/2 v2.11, and I just got a NEC 3Xi CD-ROM drive.  I used Selective
Install, it worked fine, about 4 files were copied from the GA disks, and my
config.sys was modified.  No problems.  I reboot OS/2 comes up fine, my
CD-ROM drivers load fine.  If I go back into Seleect Install, it says that
I don't have any CD-ROM support loaded.  But the drivers are loaded.

Something is wrong. I can't use CDExplorer...I get the following error:

"Error in MCI_OPEN(CD drive or MMPM/2 CD driver error) = 5045.
CD Explorer is closing."

Brian Surdahl
Phillips Petroleum Co., Bartlesville, OK  74004
[e-mail]
**********************************************************************


ΓòÉΓòÉΓòÉ 173. OS/2 errors 2025 and 2027 encountered ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We had same error with AMI BIOS and a Multi-IO card that controlled
our disk drives.  Succeeded in install by disableing ROM BIOS ADDRESS
SELECT on the Multi-IO card (change the jumper).

Mike Hanrahan, Kingsbury Corp.
**********************************************************************


ΓòÉΓòÉΓòÉ 174. SYS02025 SYS02027 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

CPU=IBMSLC2 in an AT bus clone (66mhz)
Same thing happened to me. Fortunately it has a TURBO button
to slow it down.
 1. Pushed TURBO to slower speed
 2. Pushed RESET to start IPL again
  SAME ERROR
 3. Power OFF/ON
 4. IPLd thru DISK 1 with no errors!
Something funny going on tho'... subsequent IPLs had the error...
Just kept RESETing/CADing until error went away! I don't understand why.
Fairly new 3.5" drive, keyboard cable connected soundly...
Got big red screened FDISK UNSUCCESSFUL message.
**********************************************************************


ΓòÉΓòÉΓòÉ 175. CID Installs on a 750C (PCMCIA) ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I've had an equal question open for the past month and no one seems to be
able to answer me so I hope I have better luck here.  I am trying to figure
out how to load a thinkpad 750C PCMCIA using CID.  I can't find the .bio
or Abios file for the 750c and the PCMCIA Token ring card drivers that
would need to be on the diskette as well as in the NTS load.  Any advise
you can give would be appreciated.  I've been using CID for quite a while but
this one has me a bit confused.

John Zawistowski
**********************************************************************

John,
In the March 1993 (GG24-3783-01) Automated Installation for CID enabled
OS/2 V2.x pg 221 - The ThinkPad 700 series is the only machine type
where the administrator should specify the DDIDDP, DDIDest, and DDIScr
keywords in the OS/2 V2.1 response file in order to install the loadable
ABIOS files.
Systems having a System Partition will load the loadable ABIOS file from
the System Partition during OS/2 V2.1 installation.
Systems without a System Partition wil load the loadable ABIOS file from
their Ref Diskette during standard diskette installation or load the
loadable ABIOS files from the code server according to the DDIDDP,
DDIDest, and DDISrc keyword in the response file.  OS/2 2.1 will prompt
the user for the Ref Diskette during normal OS/2 v2.1 diskette install.
From pg 184-185:

DDIDest - the OS/2 Device driver installation destination. Determines
     the target directory for the device driver.
  Keyvalue = Directory where to copy the device driver files
DDISrc  - the OS/2 Device driver installation source. Determines the
     source directory for the .DDP files
  Keyvalue = Directory where the .DDP files are
DDIDDP  - Use OS/2 device driver installation to install external
     loadable device drivers. A device driver profile ( a text
     file with a .DDP fiel name extension) must be provided by
     the device driver author to control the installation of the
     device driver.
  Keyvalue = List of .DDP files to install.
     example: DDIDDP=file1.DDP, file2.DDP
ACTIONS:
o Activate the system partiition by pressing Alt+Ctrl+Ins, when the
  cursor is located in the upper-right corner of the display.
o Select Backup/Restore of system programs from the first menu.
o Select Backup ref diskette and follow the displayed instructions.
o Reject the creation of the Diagnostic diskette ( hit Esc key)
o Create a new subdirectory in \IMG\OS2V21 directory of the code server.
o Copy from the backup Ref diskette ABIOS.SYS, .BIO, and .DPP files into
 the directory.
o Reference this directory by the DDISrc keyword.
----------------------------------------

Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************

[Reference to append at 14:06 on 94/03/28 by CHVY002 at OS2CUST ]

John,
IN addition the keyword PCMCIA specifies whether or not to install
PCMCIA.  1=install / 0= do not install
Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************

[Reference to append at 14:06 on 94/03/28 by CHVY002 at OS2CUST ]

I understand your confusion, it took me over two solid days to get it to
work. It is a bit tricky, but the 750C can be CID installed.  I placeda
lengthy append in the LAD2 CForum giving the steps necessary to CID install
PCMCIA machines using LAD/2.  The append is dated 01/12/94.  Althought some
steps I describe are strictly LAD/2, there are many other details that are
"generic CID" that you'll need to put into your CID process.  Take a look at
that append to get a feel for what has to happen and then maybe I can help
fill in the blanks.

Two answers for you from your original append:

1) There aren't any .BIO or ABIOS files required for the 750.  It's an
ISA-bus machine with no system partition and has no special BIOS stuff.
The DDI response file statements discussed by Richard in another reply to
your append are NOT applicable to the 750.  (ThinkPad 720s are MicroChannel,
750s are ISA.  Go figure....)

2) The T/R drivers are on the IBM PCMCIA Token Ring 16/4: Installation,
Drivers, and Diagnostics Diskette  (currently version 1.22).  Unfortunately,
the disk that actually ships with the adapter is version 1.10 which doesn't
even mention OS/2, much less have the drivers.  You'll need to get an updated
diskette.

Brent Allen - IBM Personal Systems Competency Center   Southlake, TX
**********************************************************************


ΓòÉΓòÉΓòÉ 176. Printing from OS2 2.1 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Ref:   None

I am trying to print from a model 85 which is a server machine.
Since no one could print from the LAN.  I tried printing directly
from the server using both drag and drop and printing from the command
line.  The job goes on the queue and is shown printing however
nothing arrives at the printer.  After a few seconds I get the
OS2 message that the printer is off or offline.
If I boot from a DOS disk, I can print fine from the command line.

I have swapped out the 4029 printer for a proprinter and after
adding the printer to the desktop with either IBMNULL or IBM42xx
drivers, same results.  So it seems like OS/2 configuration or ??
What have I missed?  I set up machines all the time and
have not experienced problems in this area.

I was certain of a hardware problem until I printed from DOS disk.

Jerome Higgins
**********************************************************************


ΓòÉΓòÉΓòÉ 177. Error on CID install MSGCID0002 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 (no text entered)
**********************************************************************


ΓòÉΓòÉΓòÉ 178. Error on OS/2 CID install MSGCID0002 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am experiencing an error using with CID installation.  The CID server comes
active fine.  I boot the client, insert the second disk, get a message that
the install is starting, then message CID0002 x:\EXE\OS2V21\seinst - was passed
an invalid parameter = /l1:Y:\OS2V21\P0010285.log.
The re-directed drive is there (I can see X: and Y: fine), and I can fine no
fault with the syntax of this command.  Please help!  Regards,

Steve Kiernan, Bank of Boston
**********************************************************************

Steve,
Did you try an uppercase /L1: instead of the lowercase?

Richard Decker PSPC-Boca Tech Interface Group
**********************************************************************


ΓòÉΓòÉΓòÉ 179. Can an install image of OS/2 2.1 XR06200 be built from service pack? ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I'd like to be able to CID install OS/2 2.1 with the service pack without
having to install OS/2 2.1 then install the service pack.  Is there a way
to create a OS/2 install image that would allow this?

If not, can I get order a version of OS/2 2.1 that includes the service pack?

Tom Ritter  -  Owens-Corning Fiberglas
**********************************************************************

You'll want to get the OS/2 2.11 refresh which is 2.1+SP.  Seems like I read
elsewhere on the BBS that it is being sent to the channels, so it's just a
matter of when it makes it out to the dealers.  Or, I believe you can get it
immediately by calling the 1-800-3IBMOS2 number.

Brent Allen - IBM Personal Systems Competency Center   Southlake, TX
**********************************************************************

[Reference to append at 14:27 on 94/03/30 by OCFC002 at SHOPER3 ]

The 2.11 refresh is available just received a copy yesterday.

Jack Hiatt
MARC-Life
Atlanta Ga.
**********************************************************************

[Reference to append at 14:27 on 94/03/30 by OCFC002 at SHOPER3 ]

I'm not sure how you could do this quickly/reliably/free/within license
terms (but IMHO it SHOULD be so (NOT AN OFFICIAL OPINION)), but...

there is a manufacturing release that is just what you want.  it will be
the only thing available after the channels clear, but what you want
is to get your hands on this and use it to build the image on your
CID server.  There is no way to combine the OS/2 2.1 code (especially
if it were built from blue label diskettes) and the SP on your CID
server...                              bt

Look for a PSP Marketing Specialist in your Area, fsiling that, post
me a reply and let's see how we can Do The Right Thing...
**********************************************************************


ΓòÉΓòÉΓòÉ 180. The operating system is missing from the startup drive... ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Ref:   None

I am getting the above message when rebooting after the first
5 diskettes have been loaded...

My configuration when starting install is:

Name    Status      ACCESS       fs TYPE      MBYTES
      STARTABLE    :PRIMARY      BOOT MANAGER    1
OS2 2.11   INSTALLABLE   C:PRIMARY      UNFORMATTED    120
TEST OS2   BOOTABLE     :PRIMARY      UNFORMATTED    120
      NONE      D:LOGICAL      UNFORMATTED    759

Anybody have any ideas???  If I take a look after this failure, C: is
marked BOOTABLE and the drive has been formatted HPFS.  I seem to be
missing something... but I am sure I followed the same steps on another
install!

Victor R Kruger, Jr
**********************************************************************

Victor,

I am not clear what you are trying to accomplish! Deactivate the boot
manager for now! Set C: startable and installable! Boot OS/2 2.1 and
install C: (format the disk when asked)!

Ray Latulippe (Boca Electronics Support Team)
**********************************************************************

Well, trying to install OS/2 :-)  I have done a hundred installs with
previous versions, and I was sure I used the 2.11 refresh a couple days
ago, but now I am not sure...

When I initially boot OS/2 from A:, and come up to question on accepting
drive/partition or specify, I specify... partition the disk with BOOT
MANAGER, two other primaries and a logical.  At this point there is NO
WAY to deactivate BOOT MANAGER... it maintains STARTABLE status!  Anyway,
specify C: as installable, save and exit.

After installing first 5 diskettes, pull out diskette and reboot...
error and machine is locked:

The operating system is missing from the startup drive.

Boot first 2 diskettes, and escape to command line... run FDISK and
BOOT MANAGER is STARTABLE and C: is BOOTABLE... so I go ahead and set
C: as STARTABLE (this will automatically deactivate BOOT MANAGER),
save and exit.  Reboot machine and same error... has anybody else
installed the 2.11 refresh???  I am using a 9595-1NT...

Victor R Kruger, Jr
**********************************************************************

Victor,
Is there an operating system on the drive?  Has the base portion been
loaded?

 Jack Hiatt
MARC-Life
Atlanta Ga.
**********************************************************************

[Reference to append at 22:29 on 94/03/30 by KRUGER at RALVM6 ]

Victor,

There is a commnad in OS/2 simular to DOS SYS command it is called
SYSINSTX.

Boot the install disk, then disk one! At disk one hit escape! re-insert
the install disk and type SYSINSTX C:
This should trnasfer the operating system to C:

Ray Latulippe (Boca Electronics Support Team)
**********************************************************************

Ray... ummmm nope :-(  this is getting frustrating!  I get the error
when type SYSINSTX C:

The type of the file system is HPFS.
An internal error occurred.

Thanks for your help so far... any more ideas (please, please :-).  I
am afraid I don't even have a clue at this point!

Victor R Kruger, Jr
**********************************************************************

Victor,

This should work if you have the compleate set of 2.11 diskettes (not
the 2.1 SP). Have you disabled the disk cache, turbo mode, shadow ram
and set the system to VGA 640 x 480 prior to attempted install?  Do all
of this then delete all the partitons and just recreate the BM and one
for this first initial installation (you can create the other partiotns
later!

Ray Latulippe (Boca Electronics Support Team)
**********************************************************************

Ray, thanks for your help... something was really messed up.  I knew
I was doing the right things, so I pulled an identical machine from
our testbed and with much success installed OS/2.  I went back and did
a low-level format on the hard drive and was able to install OS/2...
I do not know what was lingering on the disk (or how), but OS/2 must
of had something dangling on the drive...

Victor R Kruger, Jr
**********************************************************************

[Reference to append at 19:10 on 94/03/30 by KRUGER at RALVM6 ]

Like Victor, I have installed OS/2 on quite a few systems, but the
subject message he got, I also never encountered before.

> After installing first 5 diskettes, pull out diskette and reboot...
> error and machine is locked:

> The operating system is missing from the startup drive.

I did get this message using the 2.11 level - and see no way out.
The reason that I got this is possibly because I tried to 'clone' a
1 GB hard disk for a backup system by attaching the second disk drive
(as extended partition - to avoid the drive letters to shift - which
 makes OS/2 unusable in the 'higher than' C partitions).
I partitioned the 2nd dr. exactly like the source drive and then copying
data from the source drive to the second drive in the respective partitions.

The plan was to remove the source drive, install OS/2 and using
FDISK to make make the C partition active (=DOS, selectable from the BM)
but I get the above message and there seems to be no way out - at least
I have not yet found it, after multiple tries; even DOS can not be
installed anymore, even after I delete the the 'Bootmanager' and
'Primary' partition and subsequently recreate then.
(leaving the other partitions intact - so far, to keep the data).
I am not about to do a 'low level format' like Victor did, I hope there
is a another way, as I do not want to go through the recreation of all
that data again :

Any other suggestions (and explanations of the behavior) are welcome !

     Rolf Klenk              Team OS/2
**********************************************************************

Download the INSINF file (I think that's what they call it) and look at
the info about install problems.  There is a whole section about lockups
at DISK 5.

Ken Prevo
**********************************************************************

[Reference to append at 16:28 on 94/04/05 by KLENK at SJEVM5 ]

 + in OS221 : App. 13:40:34 on 94/04/05 GMT (by PELOQUIN at BCRVM1)
        &  18:40:31 on 94/04/05 GMT (by PELOQUIN at BCRVM1)

Mark Peloquins notes helped me fix my problem :
He pointed out, that the Subject message occurs, when the Master Boot
Record gets corrupted (however this may happen, I do not know details)

To fix the problem, I booted with a DOS 6.1 diskette and typed
 'FDISK /MBR'  (as Mark had mentioned)

and - Voila ! I was able to install OS/2 and DOS like in the old days !
Better yet, all my data in those prepared partitons was still there !

Thank you, Mark !

     Rolf Klenk              Team OS/2
**********************************************************************


ΓòÉΓòÉΓòÉ 181. S3 video chip and mouse pointer size ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I just installed OS/2 2.1 GA on a machine with a Diamond
Stealth (something or other) with an S3 chip (don't know the
chip version for certain).  I installed the S3 driver and
it works _very_ well - the performance at 800x600x256 seems
as good as standard 640x480x16 VGA.  I have gotten used to the
Large Mouse pointer I was using on an "SVGA" adapter;
However, that the Rexx exec which does:
 call SysIni "USER", "PM_IBMVGA", "CURSOR_SIZE", "1"
doesn't change the mouse pointer size.  Is the "key_name"
different for the S3? (just happened to think about this, but
I'm at home now & that machine is at work - I'll poke about
the ini file tomorrow) Does anyone know if this is the case,
or if it is just not supported on S3?

Thanks,
Tim Wuthrich, The Upjohn Company
**********************************************************************

Tim,

The difference probably lies in the reference to PM_IBMVGA. Since you
installed the S3 drivers you now have SVGA. Check out the ini for the
name difference.

Ray Latulippe (Boca Electronics Support Team)
**********************************************************************

[Reference to append at 23:57 on 94/03/30 by UPJA012 at HONE82 ]

>However, that the Rexx exec which does:
>  call SysIni "USER", "PM_IBMVGA", "CURSOR_SIZE", "1"

I recall seeing that the REXX program to change the cursor size has always
had a bug in it that kept it from working.  Evidently, that's still
uncorrected in the CSD.

Hopefully, someone will be able to post the right one for you...

Ken Prevo
**********************************************************************

[Reference to append at 13:25 on 94/03/31 by V$IRLATU at BCRVM1 ]

Ray, I did look at the ini today.  I now see an PM_IBMXGA entry
and tried :

  call SysIni "USER", "PM_IBMXGA", "CURSOR_SIZE", "1"

Upon reboot, there was no change in pointer size.  Editini did
show a cursor_size entry for the PM_IBMXGA key.

I guess this is not a real big deal, but the "larger pointer
<fix>" has gotten some exposure so we should understand the
configurations to which it applies.

Thanks,
Tim Wuthrich, The Upjohn Company
**********************************************************************


ΓòÉΓòÉΓòÉ 182. OS/2 for Windows installation problems with AMI BIOS rev.F ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Weeks ago, I wrote an append that referred to OS/2 errors 2025 and 2027 on
an attempt to boot the OS/2 for Windows installation disk. It is still a
problem! (No, there is no problem with my diskette or floppy drive. Turning
off the turbo mode doesn't help either!)

In a last ditch effort, I asked about changing my BIOS from the 12/12/91
AMI BIOS revision F to the latest version. I found out yesterday that this
would necessitate changing my mother board! (I currently have a 486 GMB-UN,
I believe, with a 50 MHZ DX2).

This is not a viable solution! Do I have to resort to Chicago when it comes
out or is there a feasible IBM solution?!

--
----------------------------------------
Stephen P. Lane      Internet: [e-mail]
1150 Eglinton Ave E,   Phone:   [phone]
North York, Ontario
M3C 1V7
**********************************************************************

Stephen,

If you refer to page 168 "OS/2 Installation Guide" you will see that
rev F of AMI BIOS is an acceptable level!
Who suggested going above rev F?  You will need to check the Keyboard
controller level though as per page 167!

Ray Latulippe (Boca Electronics Support Team)
**********************************************************************

[Reference to append at 16:59 on 94/03/31 by STEPHENL at TOROLAB ]

Stephen,
Double check the documentation, the F bios should be alright, I ran for a
long time on that one.  The problem wasn't really in the bios anyway but
the keyboard controller set.

Jack Hiatt
MARC-Life
Atlanta Ga.
Team OS/2    T.I.P.A.
**********************************************************************

[Reference to append at 16:59 on 94/03/31 by STEPHENL at TOROLAB ]

v$irlatu@bcrvm1 wrote:
: Stephen,

: If you refer to page 168 "OS/2 Installation Guide" you will see that
: rev F of AMI BIOS is an acceptable level!
: Who suggested going above rev F?  You will need to check the Keyboard
: controller level though as per page 167!

: Ray Latulippe (Boca Electronics Support Team)

I apologize for "flying off the handle". I attempted another OS/2 for Windows
install after my machine returned from the dealer, after noticing that my
keyboard controller was also valid. Although the dealer said that he hadn't
made any changes, (only investigated whether I could upgrade the BIOS),
the install worked!

All I can assume is that one or other boards and/or cables were reseated
properly. Thanks for your suggestions and those of everyone else who responded.

Steve.
--
----------------------------------------
Stephen P. Lane      Internet: [e-mail]
1150 Eglinton Ave E,   Phone:   [phone]
North York, Ontario
M3C 1V7
**********************************************************************


ΓòÉΓòÉΓòÉ 183. OS/2 Hdwe Experience ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Can anyone help Russ?
His Internet address is [e-mail]
Or you can talk to me at [e-mail]

Thanks.
Ron Palmer
________________________________________
 From: YOO096  --YJ0030            Date and time
 04/04/94 10:32:42   To: $WW090  --YJ0030

           FROM: Russ Peters
           SUBJECT: OS/2 Hdwe Experience

           You may recall, that I mentioned I was in the process of buying
an OS/2 machine  for home use and was having some installation problems;  the
configuration now   accepts the CD ROM software for installation but the screen
freezes and the    machine locks up near the end, after the "Migration" screen.
 IBM thinks      the video statements were missed in the config.sys file and
has FAX'ed a work   around for this; but we no longer have the use of the test machine.
 Although   I would like to buy a machine identical to the test machine,
it is appropriate   to get some more info first.  Could you post a notice on one
of the technical   boards to see if we can locate someone who has set up a multimedia
OS/2.1     machine with the following hardware?  Thanks.

           Mother Board:  ALARIS LEOPARD Rev.C 486 SLC2/66, VESA Local
Bus, 8 MB 70ns,            AMI Bios, 128 cache(Designed by Alaris, made
by IBM NC)       Display:    DIAMOND SPEEDSTAR PRO VLB (Cirrus Logic chip
set), SVGA              Monitor
           CD ROM:     Soundblaster Pro card, Panasonic 562, 2 speed
CD ROM drive     Hard Disk:   VESA Local Bus IDE controller, 420 Mb Western
Digital Drive
**********************************************************************

Ron,

This machine should work! You will need to check the AMI BIOS level per
page 167 and the keyboard controler level per page 168 "OS/2 2.1
Installation Guide"! Also prior to install you must go into the BIOS and
disable disk cache, shadow ram, turbo mode, and set the video to VGA 640
x 480! You must have all of your drivers available and if installing
from CDROM you need to change disk one as per page XVII-XVIII
"Installation Guide". You should download the MMPM2 CSD (MMPMCS.DSK) as
well as the latest SB drivers! After install is when you attempt to
change the video resolution!

Ray Latulippe (Boca Technical Interface Group)
**********************************************************************


ΓòÉΓòÉΓòÉ 184. OS/2 2.11 from CDROM with SB14 Card ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

In installing OS/2 2.11 on a Dell with a Sound Blaster 16 card, I found
that the config.sys on disk 1 was improperly set up for my machine.
In the config.sys the Sound Blaster driver line was:
   basedev=sbcd2.add /p:300
by adding a second SB driver line, I was able to complete the install
   basedev=sbcd2.add /p:300
   basedev=sbcd2.add

Could it be that if the config.sys on the disk 1 of the cdrom install
had basedev commands for all possible valid Sound Blaster configurations,
all bases would be covered?  Could something like this be done for the
next manufacturing refresh/version of OS/2?  It has the potential to
prevent a lot of customer frustration.

This idea could be applied to other device drivers as necessary.

Matt Hickman     Chevron Information Technologies Co.
voice [phone]    Internet:  [e-mail]
fax [phone]
**********************************************************************

Matt,

It would be impossible to cover all combinations of different drivers!
The only thing that looked wrong was the address! All you needed to do
was provide the corect one which should be documented with the driver
(readme file)! If you attempt to load device drivers for
everycombination then you would have to have those files availble one
the same disk containing config.sys! Perhaps what is more resonable is a
scrollong menu that allows the user to make a seletion of installed
hardware which then edits disk one's config.sys and unpacks the drivers
from yet a third disk and then reboots the system!

Ray Latulippe (Boca Electronic Support Team)
**********************************************************************

Well, Plug 'n Play should solve all our problems <BG>.  But it is still
a good idea to remove all possible road hazards in the install process.
It would take a pretty sophisticated user to be able to debug install
problems, and a fairly committed one to put up with the hassles.
And anything that reduces support calls will also be a blessing.

Matt Hickman     Chevron Information Technologies Co.
voice [phone]    Internet:  [e-mail]
fax [phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 185. CID0002 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Ref:   Append

Yes, I tried changing the case on the switches and parms to
no avail.....  Any other ideas?

Steve Kiernan, Bank of Boston
**********************************************************************


ΓòÉΓòÉΓòÉ 186. Install problems with OS4WIN ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I tried to install OS/2 for Windows (CDROM version) and ran into a wall
with an FDISK Unsuccessful error - big red box, check INSTALL LOG, etc.
According the the book, this error relates to in incompatible hard drive
controller and says that I should get the OS/2 drivers for my drive and
put them in the config file (like I had to for my CDROM support). Given
that I'm not using any unusual HD (it's a WD2540 IDE), I can't see why
OS/2 should be having a problem with it. What I'm wondering is if it
has something to do with the way the drive may be partitioned. The drive
is brand new and I formated it as one big partition. Here's my system
info:

GW2000 486SX/25
WD2540 IDE drive - 540MB
Creative Labs/Panasonic CDROM (interfaced through the SB16, SBCD2.ADD
  driver used)

HELP!

Keith Garvens
**********************************************************************

Keith,

This is exactly the problem you are haveing! WD 540 HD's have more than
1024 cylinders on them! The boot sector must be in a partition that is
within the first 1023 cylinders! What I recomend is that you create a
primary partition that will contain only the OS itself! This partiton
must be within the first 1023 cylinders! Then I would create another
partion for applications and yet another for DATA! thus if the OS messes
up you only have to format the small OS partition and reinstall! As for
backup you only have to backup the DATA patition! So in a nutshell all
primary partitions that you may wish to make must be within the first
1023 cylinders! Any partition after that should be extended logical!

               11 Apr 1994 14:13:13

Ray LaTulippe (Boca Electronic Support Team)
**********************************************************************

Thanks for the information. I don't entirely understand what you are
suggesting, so here's a few more questions:

1. How do I know how big to make my partitions?
2. My system currently is running with one big partition (DOS/WIN). To
  do what you're suggesting, does that mean that I have to start over
  and reformat (and partition) my entire disk?
3. When I make a partition (I'm not real FDISK-savvy), how do I know
  where it is 'made' (what range of cylinders are sued)?

Thanks for your help.
Keith Garvens
**********************************************************************

[Reference to append at 14:10 on 94/04/11 by KRG at RCHVMP3 ]

Keith,

Couple of things come to mind:
 You aren't using a WD IDE controller are you?
  (WD controller cards suck!)
 Are you trying to format it as one drive?
  (You can't format beyond Track 1023 in the primary partition.)

For FDisk and format to succeed you will have to create the primary
partition in the lower space and create a second partion that consist of
one or more logical drives in the rest.  You can use the 128-meg for the
OS and Swap and Spooler and not worry about running out of space.

My choice would be to make the first parttion about 128-meg and HPFS.
Then, you can decide if you want the rest to be one or several extended
partion logical drives.  If you plan to use a tape backup system, I
wouldn't make them any larger than a tape.

Ken Prevo
**********************************************************************


ΓòÉΓòÉΓòÉ 187. COUNTRY.SYS not found during boot ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I re-installed OS/2 2.1 after installing a second scsi hard drive
and rearranging everything. All was fine. I installed Extended services
and re-booted the system again all was fine. The only thing not working
at this point was I had no CD-ROM access, so I powered the machine off
and called it quits for the night. The next day I powered on the machine
but the OS/2 initialization quits after telling me it can not find
country.sys on line 34 if config.sys. I can boot from install disks
and see the file is where it belongs but OS/2 will not boot.
Anyone with any ideas on how to get out of this situation?
Thanks
Ken Prince E.I. DuPont
[e-mail](Internet)
IBMMAIL(USDUPGVW)
**********************************************************************

Ken,

This message is not what it appears (are they ever)! This is the first
attempt by OS/2 to talk to the drive! Check out the config.sys and
ensure that it is an OS/2 one! Also did you install dual boot!  Try
booting OS/2 from the drive! When this fails boot the install disk in
drive A: then insert disk one! Hit escape at disk one and insert the
install disk again! At the OS2 command prompt in the A drive type:
SYSINSTX C:

Let me know weather this is a dual boot setup or a boot manager setup!
For your info there is a copy of config.sys stored in the C:\OS2\INSTALL
directory! as well as backups for the os2*.ini files! Once you get all
setup copy the three files to this directory as backup!

               12 Apr 1994 10:32:15

Ray LaTulippe (Boca Electronic Support Team)
**********************************************************************

Thanks Ray for the tip I will use that to try and get things back working
I would appreciate it if you could read the CFORUM on OS2BBS OS2HW where
I posted a fairly complete description of what I am attempting to do.
In summary - I have a PS/2 model 90 w 320MB internal drive with a toshiba
3401 external cdrom cabled to the IBM SCSCI adapter w OS/2 2.1 installed
and working fine. I wan toexpand my hard drive capacity so I ordered a
Seagate ST31200N(1 GB) set up as an external drive. I naively thought
I could just cable this in with the CD-ROM and all would work fine.

If i boot from OS/2 2.1 CD-ROM version install disks and escape the
installation I can access all the devices just fine - in fact I
partitioned the new hard drive and copied the contents of the old
drive to the new for backup; repartitioned old drive(yes I am using
bootmanger) and re-instaled OS/2 2.1(from CD-ROM) and DOS/WIN.
I can boot DOS/WIN fine(but no access to CD-ROM; do have access to FAT
partitions on both hard drives. More often than not when I select OS/2
from boot manager I get the country.sys error - I have concluded that
somehow the new hard drive is interfering with the boot process - I don't
know how to get the set-up working except return the hard drive and
forget about upgrading capacity.

Thanks for listening and if you have any other comments they are welcome;
I really do need the capacity and adding SCSI devices external seem
so simple - but maybe my model 90 and its components(ie. adpter, bios,
eprom whatever) just won't support what I want to do.
To re-iterate if I boot from the install disks I have complete
and total access to all devices!!! I can't believe that the cabling,the
devices or the termination of the SCSI chain is at fault. The problem
appears to be with the interaction of the internals of the Model 90
and the OS/2 2.1 boot process.
Ken Prince E.I. DuPont

[e-mail](Internet)
IBMMAIL(USDUPGVW)
**********************************************************************


ΓòÉΓòÉΓòÉ 188. Suggested disk configuration for OS/2 for Windows ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

As I have mentioned before, I have a 540MB drive formatted as one big
partition (out of ignorance) with MS-DOS 6.2 and Windows and assorted
programs all loaded in. I'm trying to install OS/2 f/win. The questions
are:
1. Should I repartition first, then try to do OS/2 f/win? I do have a
  tape backup that I could save my current stuff, repartition, then
  restore and try OS/2
2. Install OS/2 and have everything on one big FAT partition?
3. Any thoughts on what partitioning scheme I should use?
4. Should I consider HPFS for any/all of the partitions?

I only want to do this once. I am aware of the formatting woes of the
540MB drive, although it isn't clear to me if I can or cannot use the
ENTIRE disk space in some form of partitioned FAT configuration. Please,
only respond if you actually have been through this. I've had too many
'well, this should work' type of comments already.

Keith Garvens
**********************************************************************

>I only want to do this once. I am aware of the formatting woes of the
>540MB drive, although it isn't clear to me if I can or cannot use the
>ENTIRE disk space in some form of partitioned FAT configuration. Please,
>only respond if you actually have been through this. I've had too many
>'well, this should work' type of comments already.

I have a drive about the same size--actually a bit bigger.  It even remaps
on its own and get around the > 1024 cyl in that manner.  DOS will not
handle a drive of that size.  It also croaks at about 625-meg of total
capacity.  (Don't shoot me for not remembering the exact value) To just
get access to all the drive's capacity I had to install an additional disk
manager product.  So, installing your drive as a single partition probably
doesn't make sense as a FAT setup either--you'd end up with unused
capacity.

One thing to consider is that if you do suffer a lockup that even C-A-D
doesn't cure, you will reboot with the "dirty flag" set.  This runs CHKDSK
on the boot partition.  On big drives people report it sometimes runs for
hours.  Even on your smaller drive, would you want to wait for 15-20
minutes for checkdisk to process the whole drive when it is setup as a
single partition.

Good drive managment seems to transcend a lot about OS's.  While the
result might not be as efficient as a single partition, it is a lot more
user friendly.  I prefer to have primary and logical drives that are
slightly less than the size of my tape backup--one tape equals one drive.
If I need to restore I don't have to sit there and swap in 3 tapes to get
to the file I need to restore.

The caveat on this is that HPFS comes into its own when the partitions are
128-meg or more.  So, a really small tape backup would make me think about
FAT partitions more than HPFS.  Or maybe a nice size HPFS with the FAT one
on the rest.

In the final analysis, you have to have a minimum of two partitions to use
all of the drive.  Folks who told you that OS/2 won't boot on a partition
that has part of itself about the magic 1023rd cylinder.  Just how you
split it up is up to you, though.  For every reason I give why I'd do it
one way another person will have a reason to do it his way.  You'll have
to figure it out on your own, I fear.  Don't make everything in the first
partition that you can or the remaining secondary partion will be so small
it'll be pretty useless.  Don't make partitions so large backing up and
restoring is a pain.  Don't make to many different sizes for the different
partitions.  Those aren't hard and fast rules they are just ones that seem
to work out fairly well for most folks.

How did I set my 300+ and 650+ drives up?  Well, I do have an old 60-meg
Maynstream Tape unit; so, I have LOTS of virtual drives.

Ken Prevo
**********************************************************************

Thanks for the insight. However, one part of my question still remains
either unanwered or answered by conflicting information, and that is
can I or can I not partition my 540MB drive so that I have access to the
whole 540MB without resorting to HPFS? If it is possible to use FAT all
around, great. If not, it would make sense to (multi-)partition the most
of the disk as FAT, so that DOS and Windows can be installed, then have a
partition at the end of the disk big enough to hold OS/2 and straddling
the 1023 cyl boundary, format it as HPFS and then install OS/2 f/Win
there. Will this work? I assume that it is a limitation of OS/2 f/Win
that since DOS and Windows must already be on the disk before OS/2 can
install, one cannot format the entire disk a HPFS like you could with
the regular OS.2 2.1, correct? Also if some combination of FAT and HPFS
is used, are there some components of OS/2 (particularly the swap file)
that must remain in HPFS, or can they be located anywhere?

Keith Garvens
**********************************************************************

[Reference to append at 21:06 on 94/04/12 by KRG at RCHVMP3 ]

Keith,

 SOLUTION or SUGGESTION:

        FDISK ERROR OR FAILURE TO BOOT FROM INSTALLATION
        DISKETTES ON SYSTEMS WITH HARDDRIVES THAT HAVE THE
        BOOTABLE PARTITION SET LARGER THAN 1024 CYLINDERS

 DESCRIPTION OF SYMPTOMS:

   On systems with large harddrives (greater than 1 Gb) the
   installation process reports FDISK errors or is unable to boot.

 SUMMARY OF RESOLUTION:

   While OS/2 is capable of supporting partitions
   greater than 1024 cylinders, they can not be bootable
   partitions.  This is a hardware related limitation and is
   true of DOS and OS/2, HPFS and FAT.
   Define the partition size for the boot partition to be within the
   first 1024 cylinders.

 DETAILS OF RESOLUTION:
   1.  Consult the documentation that came with the harddrive and
     find out how many Mb are within the first 1024 cylinders.
   2.  Ensure that any bootable partitions are created at the
     beginning of free space and within the above limit.
   3.  this also known as sector translation.. You need to
     have the drives under the 1024 clyinder limitations..

               13 Apr 1994 08:12:17

Ray LaTulippe (Boca Electronic Support Team)
**********************************************************************

[Reference to append at 12:34 on 94/04/13 by KRG at RCHVMP3 ]

Keith,

My understanding is that OS/2 FDISK will allow you to use the whole
disk! The restiction is that ALL primary partitions must be within the
first 1023 cylinders! Therefore have BM, DOS/Win, OS/2 within the first
1023! If you have all of these as primary then the system will assign
the drive letter C: between the DOS/Win partition and the OS/2 partition
offering greater isolation of the two Operating Systems! DOS/Win
partition should be just large enough to hold those two together (with
some room for the Win swapper! The OS/2 partition should be just enough
to hold OS/2! On my system this is less than 80 meg for the both! You
can point the OS/2 swapper to yet another HPFS partiton setup just for
it to increase disk access time! The rest of the disk can be formmated
as FAT (partiton for apps and partitions for data)! Then the only thing
you have to back up is the DATA, and of course the INI files and
config.sys of each respective operating system! Then if you need to
install OS/2 or your Win again you can reformat that particular
partition and do a clean install!

               13 Apr 1994 08:45:11

Ray LaTulippe (Boca Electronic Support Team)
**********************************************************************

[Reference to append at 12:34 on 94/04/13 by KRG at RCHVMP3 ]

OS/2 is the only one that can use the area above cylinder 1023.  This is a
DOS limitation.  Also, OS/2 cannot have a primary partition that straddles
or uses the >1023 cylinders.  OS/2 only supports secondary partitions with
high cylinders included.

DOS users typically get around the 1024 conundrum by using HD controllers
that remap the drive.  For example my old ESDI drive, looks like it is
600+ cyl to DOS with many more sector per track than the actual count.  It
then translates the access to access the "real" sector/cyl.  If your
controller can't do this then there are DOS extenders that allow that.
These are drivers that must be installed and obviously take up disk space.
They also aren't going to be seen/usable when you boot OS/2.

Getting clearer or cloudier?

Ken Prevo
**********************************************************************

[Reference to append at 12:19 on 94/04/13 by V$IRLATU at BCRVM1 ]

This sounds like just what I'm looking for. Now, I haven't read through
the procedure for setting up Boot Manager, which I think is the route I
want to go, but you mention (or imply) that both the DOS/WIN and OS/2
partitions are set up as Primary. True? What is the definition and purpose
of the Primary designation? Is it the same as bootable? It seems that I
certainly would need to have the 'last' partition (the one that straddles
the 1023 point) be HPFS, and I'd probably make it the one that holds the
OS/2 swapper. True? The rest I'd format as FAT. Now should the OS/2
partition also be formatted as HPFS? Thanks for all the helpful info!

Keith Garvens
**********************************************************************

[Reference to append at 15:45 on 94/04/13 by WZ01343 at HONE82 ]

How would one know if one's controller supported the remapping? By
controller, I take it you mean the card part of the drive and not the
IDE interface adaptor on the bus.
My machine's BIOS setup had an auto-config option for defining the drive
and it came up with a 'remap' of 524 cyl and 32 hds. I seemed to have
trouble formating and installing with that setup. Does that imply that
the controller can't handle it or is that a BIOS 'problem'?
If the controller did handle it or you had one of these DOS extenders,
THEN would you be able to use the entire 540MB?

Keith Garvens
**********************************************************************

[Reference to append at 16:51 on 94/04/13 by KRG at RCHVMP3 ]

Keith, may I jump in?  I setup OS2 for Windows using the following
setup on DELL 466/ME with a 500Mb drive:

BOOT MANAGER - 1Mb
PRIMARY C: - DOS/WINDOWS - 150Mb - FORMATTED FAT
LOGICAL D: -  OS2 4 WINDOWS - 320Mb - FORMATTED HPFS
LOGICAL E: - REST OF DRIVE - FORMATTED HPFS

I installed DOS/WINDOWS first and then installed all applications
to be used.  I then installed OS24WIN and since it could see the C:,
I told the install part this is where the window's code was to use.
Everything came up fine.  Was able to take advantage of the HPFS
and still run windows.  Give it a shot.

John McMullen, TEAM OS2 and TIPA, MCI, Atlanta GA
**********************************************************************

[Reference to append at 16:51 on 94/04/13 by KRG at RCHVMP3 ]

Keith,

With both the DOS/Winand OS/2 partition as primary partitions then the
Boot Manager would assign which ever you chose from the BM menu the
Drive letter C: the other primary partition (the one not selected off of
the MENU) would not be seen while the chosen OS was loaded! This works
in both directions OS/2 would never see the Dos/Win partition and
DOS/Win would never see the OS/2 partition! You can make the OS/2
partition HPFS if you so wish! As for straddling the 1023 cylinders run
Fdisk and see what its says!

               13 Apr 1994 16:24:57

Ray LaTulippe (Boca Electronic Support Team)
**********************************************************************

To do as you suggest, wouldn't that defeat any attempt to run Windows
stuff from OS/2?
**********************************************************************

[Reference to append at 21:06 on 94/04/12 by KRG at RCHVMP3 ]

Keith,
The week before last I migrated my system at work to a 486DX2
with a single Conner 540MB (520 "usable") drive.  I booted from
the 2.1 GA (blue) install diskettes and got through the fdisk
re-partitioning when I got a red error msg about fdisk failing (I
had installed Boot Manager at the _end_ of free space after
deleting the only partion).  Yup, thinks I, 1024 problem, so
tried placing BM at _start_ next time around, same thing!
Scratching my head, me thinks "Oh my", then, "You dummy, disable
external cache." Did that and it worked fine, just as expected,
with BM at the start.

Not quite the end of the story however, since in addition to
OS/2, I use another 32bit, non-Dos opsys.  The "other" system and
boot manager didn't like sharing the MBR when BM was on cyl zero,
so I re-located BM to an area as described in my partion
arrangement:

  C: "other" opsys  100MB Primary Fat
  D: Application1  100MB Logical Fat
  E: Application2  120MB Logical Hpfs
  -  Boot Manager  1 MB  "Primary"
  F: mini-OS/2    30MB  Logical  Fat
  G: OS/2 2.1 GA   80MB  Logical  Hpfs
  H: swap-files/   90MB  Logical  Hpfs (this falls off the 1023
   work space....................."end of the world")

I now use BM to to get to any of the three "bootable" partitions.
FAT versus HPFS is not really relevent here, w/r/t "usable"
space, just file system/opsys compatability.
BTW, a LAN install facility was a _big_ "productivity"
aid in this venture...

Tim Wuthrich, The Upjohn Company
**********************************************************************

[Reference to append at 22:08 on 94/04/13 by KRG at RCHVMP3 ]

Keith,

If you are using OS/2 for Windows then you would have to have DOS/Win on
the Second partition first, if you have OS/2 2.1 GA then this is not the
case! Either way you can have a pure DOS/Win 3.1 partition and a pure
OS/2 partition that runs DOS emulation and WinOS2! You caould still set
it up as I described even using OS/2 for Win!

               14 Apr 1994 08:23:20

Ray LaTulippe (Boca Electronic Support Team)
**********************************************************************

[Reference to append at 20:03 on 94/04/13 by V$IRLATU at BCRVM1 ]

> Originally appended at OS2INST CFORUM at 21:25:18 on 94/04/13 GMT
|
| This append is being resent as it appears to only be available on
| the Canadian shadow.
|
Ray,

 He can't make both the DOS/WIN and OS/2 partitions primary
because he is installing OS/2 for WINDOWS.  When OS/2 is booted
if the DOS/WIN partition is not accessable he won't have
Windows.

Lon Leader
ISM - Information Systems Management Corporation
North York, Ontario - [phone] - fax[phone]
**********************************************************************

Lon,

If you followed the thread I pointed out that to have the two primary
partitions and install OS/2 for Windows he would have to install DOS/Win
twice! So it is indeed possible!!! You just have an extra step to do!

Raymond LaTulippe (Boca Electronic Support Team)
**********************************************************************


ΓòÉΓòÉΓòÉ 189. Disk Configurations ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

This is a variation of the "suggested disk configuration for OS/2 for
WIndows thread.

M76, 245 MB HD, 8 MB RAM. I am setting up this machine for someone
who wanted an all IBM machine with store bought OS/2 2.1. IBM
CD-ROM II enhanced and the MCA Windsurfer. The problem is that
the Windsurfer is supported only under real WIndows 3.1 and not
WIN-OS2. OS/2-(WIN OS/2) support has been forthcoming for some time
but I am running out of time to set up the machine; thus, my question.

Being forced to incorporate real WIN 3.1 on the machine, I thought
I might set the disk up as follows:
  BM (end of free space)
  C: Primary DOS 6.1 (5 MB) FAT
  C: Primary OS/2 V2.1 (60 MB) HPFS
  D: Logical for APPS and WINDOWS 3.1 (70 MB) FAT
  E: Logical for APPS (100 MB) HPFS

When OS/2, WIN-OS/2 support is available, then I would like to get rid of
real Windows and DOS and make it a straight OS/2 machine. The problem
is that the owner does not live in my area and is only somewhat
knowledgeable about the software. I would not like to have him
re-install OS/2 with the CSDs and desktop and so on nor have to
re-install his applications on the D and E partitions.

My thought would be to take him through the process of deleting
the BM and removing the real Windows files on D (to give him more
space) and just write off the DOS space.

If I could delete the BM and reassign the DOS C: partition to a
logical drive then I would increase the C: (DOS) primary to effectively
be the D: disk at a later time. I think this is impossible however,
without reformatting the C: OS/2 primary and the other logical disks.

Any comments or other alternatives to solve this problem and how does
the allocation of 5MB for DOS and 60 MB for OS/2 look for this loaded
system? Thanks for your help

J. Cummings
**********************************************************************


ΓòÉΓòÉΓòÉ 190. CID Installation of OS/2 2.11 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We are successfully installing OS/2 2.11 using the CID process, however,
when selecting "format" in the OS/2 response file, the installation
fails with a 1604 "unexpected condition".  Any Ideas?

Loran Cavano
Ralston Purina Company
**********************************************************************


ΓòÉΓòÉΓòÉ 191. OS24WIN install from CD ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have been told the OS2 for Windows CD installation cannot be done
from an IDE CD ROM. Is this true? Is there a workaround other than
creating all the diskettes from the CD, possible involving changes
to the install diskettes?

Steve D. - Security Life
**********************************************************************

Steve,

It would definitly require a driver and modifications to the install
disk! The modifications to be made are detailed on pages XVII-XVIII of
the "OS/2 Installation Guide"! The question is is there a driver!

Raymond LaTulippe (Boca Electronic Support Team)
**********************************************************************


ΓòÉΓòÉΓòÉ 192. Device Driver on Disk1 During Install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am attempting to install 2.1 on a removable media wkstn without
a cdrom. Need to make space for the adaptec2740 .add (40k) on disk1,
but no room.  There are several drivers I don't need, but they are
packaged in a bundle.

How do I make room for the drivers I need????
I attempted to remove HPFS.IFS, but I need to format with it.  Also tried
to remove fdisk.com, but it needs that too.
Using 90meg bernoullis as removable media.  I already know about
loading lockdrive.  aha154xx ... drivers won't do it.

Gary Worrell  JHU/APL  Software Engineer
**********************************************************************

Gary,

You could remove any readme files or DOC files from the diskette (just
copy them to another disk!

Raymond LaTulippe (Boca Electronic Support Team)
**********************************************************************


ΓòÉΓòÉΓòÉ 193. Nightmare Re-Installation ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

My usual practice when an OS gets flaky for no apparent reason is to back up an
d re-install.  Well here is a horror story others my benefit from.

Attempt 1)  Full re-install of 2.1...accepted all defaults.  After printer
driver installation, got a message that the parameters in .DSC file were
incorrect..."ok button"...click...it checked drives & came back to same
message.

Attempt 2)  Full re-install of 2.1 plus re-format of boot partition...changed
video to "other"... got to same place as attempt 1...message SVGA (Trident)
initialization failed...ok button...click...message that installation was
complete...NOT!...wouldn't get past large OS/2 logo box.

Attempt 3)  Same as 2, but selected VGA...finally...success!!!! SP also
installed OK.

This installation used the same diskettes as the original install
which produced no problems.  To anyone from IBM, common sense
dictates leaving the driver used during the installation process
and displaying an error message which can be dealt wit later,
NOT requiring them to go thru umpteen disk repeatedly.
Furthermore, getting different results on the same machine
force me to conclude that the installation process has
as many bugs as an ant farm.

Robin Frank "The OS/2 Witch"
The Greyrock Group, Incorporated
CIS: 76470,1343  AOL: Greyrockgr  Prodigy: JVGS22A
**********************************************************************


ΓòÉΓòÉΓòÉ 194. ThinkPad 750-CS CID OS/2 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We'd like to request that whoever is going to be fielding OS/2
installation questions at the Technical Update next week in San
Francisco be prepared to with handouts on loading OS/2 2.1 GA
on a ThinkPad 750-cs using CID.

The PC-Company was gracious enough to help us develop a method
to get it working using diskettes.  ( No easy feat we might add. )  But
so far going thru Socrates we have not been able to get one of these
to CONNECT using CID, let alone go to the next step of INSTALLING with
CID.  ( We have invested 7 days full-time on this endeavor.  And we
have also begun looking at competing products.  So far none of them
are working with CID.  Consequently we are forced to distribute these
Laptops with DOS/Windows.  Which, of course, works fine.  But is not
the direction we had hoped to go. )

Leo Tornow - Northwest Pipeline Corp.
**********************************************************************

Maybe our expectations that IBM products would work together are just
not realistic.  The April 18th issue of PC Week on page 121 gives an
example of a firm that no longer has IBM SE support and just "took
five weeks to resolve a compatibility problem between an IBM ThinkPad
and an all-IBM network."

Perhaps IBM expects us to just stay dedicated to this one problem for
another three and a half weeks <g>.  Unfortunately we have lots of IBM
products and enough users that we have many problem situations to
resolve.  Ideally without having to call IBM support !

IBM should start by looking at the manufacturing process.  Why are
they still including version 1.10 of the PCMCIA drivers when they know
that they don't work ????  We'd love to hear that it is no longer true
since we plan to buy more of these IBM cards.  ( And will be forced to
use them with DOS until IBM can get the OS/2 part working AND DISTRIBUTED
to customers.)

Leo Tornow - Northwest Pipeline Corp.
**********************************************************************

[Reference to append at 15:54 on 94/04/19 by IL04688 at HONE83 ]

This IS a BEAR!!! In the LAD2 forum are instructions on setting up a
ThinkPad to do a CID installation. I found it VERY helpful.

Jim Sauber, MN Mutual
**********************************************************************


ΓòÉΓòÉΓòÉ 195. How do I get VGA 256C 640x480 in WINOS/2 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have a particular application that wants me to be in VGA 256 color
640x480.  How can I change winos/2 to look like that?  Under Windows,
I simply go to Windows Setup and Change Display type.  The setup under
winos/2 only has network options as an option.  Do I have to change
my OS/2 desktop to be VGA and then get into winos/2?

Thanks for the help.

Steve
**********************************************************************

Steve,

You can install the driver for that under WinOS2, also if you look in
system.ini you will see Fdisplay an dSdisply, these are for WinOS2
fullscreen and Seamless mode display and resolution setup!

Raymond LaTulippe (Boca Electronic Support Team)
**********************************************************************


ΓòÉΓòÉΓòÉ 196. How to get NonInterlaced Video ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

All,

OS/2 keeps giving me interlaced video.  Does anyone know how to get
non-interlaced mode?  I have a PS/VP with S3 and a 15V monitor.  I've
used the REFRESH program with SVGA ON.  No matter how hard I try,
SVGADATA.PMI always comes up with InterlaceMode=1.

Larry "IiNnTtEeRrLlAaCcEeD" Flynt
The Rosewood Corporation - Dallas, TX  Internet:[e-mail]
**********************************************************************

Larry,

 Please do the following:
    -boot system with real DOS
    -cd to the OS/2 sub-directory and delete the SVGADATA.PMI file
    -run STLMODE and under the CONFIGURE opition disable
     the following:
        -fast write buffer
        -enchanced fast write buffer
        -zero wait state
        -I/O address translate
     -under the MONITOR option set up the re-fresh rates
     -exit STLMODE and save changes to the EPROM
     -cd to the OS/2 sub-directory and run SVGAON DOS
     -then re-name SVGADATA.DOS to SVGADATA.PMI
     -re-boot system

Raymond LaTulippe (Boca Electronic Support Team)
**********************************************************************

[Reference to append at 16:04 on 94/04/20 by IL11737 at HONE82 ]

I need some help. I'm installing OS2 2.1 from CD on a P75 with a STB
ERGO-MC video board. I chose VGA on the install and when I finished the
install I would hang at the OS2 logo screen. I attempted to run SETVGA
(TYPED STEVGA at the C:\OS2 prompt) and got a "INSERT DISPLAY DRIVER
DISK 1" message. ????? I then typed SETVGA C: /P and got a bunch of
missing font messages. I even tried manually editing the config.sys file
with now avail.It appeares that OS2 tried installing XGA stuff because of
my XGA on-board video cotroller, I guess. BTW, the STB uses a ET4000 chip
**********************************************************************

[Reference to append at 17:41 on 94/04/20 by V$IRLATU at BCRVM1 ]

Raymond,

> run STLMODE and under the CONFIGURE opition disable...

Thanks for the quick response.  That's excellent!

I can't locate STLMODE, though.  Where do I find it?  I wonder what
STL stands for?

Larry "It's a Secret Tool, Larry" Flynt
The Rosewood Corporation - Dallas, TX  Internet:[e-mail]
**********************************************************************

Larry,

Check the S3 drivers disks!

Raymond LaTulippe (Boca Electronic Support Team)
**********************************************************************

[Reference to append at 17:51 on 94/04/20 by HEHUGGI at NYCVMIC1 ]

I have a ET4000 based SVGA card (STB ERGO-MC) and I can't get OS/2 to
recognize it. When I run DSPINSTL and select the ET4000 driver, OS/2
claims my adpater can't support it. I run DOS and WINDOWS with no prob-
lems. All my SVGA programs get along fine with the adapter and Windows is
running 1024x768, non-interlaced. My system is a P75 with XGA . It looks
as though OS/2 sees the XGA, it but won't acknowledge the STB card. I
called STB when I had the problem of installing the ET4000 driver (I
tried ignoring the "Adapter doesn't support message.) and getting an
obviously out of sync monitor. STB suggested eXcluding an area of memory
in my DEVICE=VEMM line in my config.sys. I took their recommendation, but
now realize my problem may be in this ADAPTER DOES NOT SUPPORT...message.
By the way, when I tried installing the ET4000 driver (ignoring message)
and got the out of phased monitor, typing SGVA ON at DOS didn't help.
**********************************************************************

[Reference to append at 12:11 on 94/04/22 by V$IRLATU at BCRVM1 ]

Raymond,

>Check the S3 drivers disks!

I did!  (It's not there...)

I've checked the S3 diskettes that came with my system (PS/ValuePoint
DOS/Windows.)  I've checked the S3 256 & 16M diskettes.  I've checked the
OS/2 2.1 GA CD.  I've checked the OS/2 2.11 SP.  I've checked the PS/VP
Diagnostics diskette.  I've checked several PS/2 options and reference
diskettes.

Please be more specific about where I can find this STLMODE thing.
I'm still wondering what STL means and how long I must wait for it?

Larry "Shouldn't Take Long?" Flynt
The Rosewood Corporation - Dallas, TX  Internet:[e-mail]
**********************************************************************

[Reference to append at 20:02 on 94/04/24 by HEHUGGI at NYCVMIC1 ]

Try running selective install and selecting the resolution that you wish
to use instead of using DSPINSTL!

Raymond LaTulippe (Boca Electronic Support Team)
**********************************************************************

[Reference to append at 01:58 on 94/04/25 by IL11737 at HONE82 ]

Larry,

My fault, that comes with the video card! Did you get a disk for your
video support! If not try using the SVGA command in DOS and rename per
page 339 "Using the Operating System" If you tell me which chipset your
system is using I can give you the number of the BBS and is you download
the DOS/Win drivers that file should be there if it is TSENG or Cirrus!

Raymond LaTulippe (Boca Electronic Support Team)
**********************************************************************

[Reference to append at 13:42 on 94/04/25 by V$IRLATU at BCRVM1 ]

Thanks for the reply, but selective install fails also. I was given one
suggestion to address the "out of phase" monitor symptom (run a ET4000
utility called VMODE before SVGA ON), but I'm not hopeful. First of all
I can't see this suggestion helping me with "Your adapter doesn't support
this driver" message and secondly, I don't remember VMODE being included
with my STB video board (early ET4000 chip). I'll look tonite. I can't
seem to understand why OS/2 would respond the way it does when I select
ET4000 driver.Last night I tried selecting VGA and got the same complaint
The only driver that doesn't ellict a "nag" is the XGA driver. ???????
Given my limited experience with OS/2 problems , I'd say if I could
remove XGA from my system board (P75), I'd force OS/2 to look for another
video board and hopefully 'address' my STB correctly.
**********************************************************************

[Reference to append at 13:09 on 94/04/25 by V$IRLATU at BCRVM1 ]

Raymond,

Okay, let's try this again. <sigh>

>Did you get a disk for your video support? If not try using the SVGA
>command in DOS and rename per page 339 "Using the Operating System."

Yes, I've got a 486DX-33 PS/Valuepoint that came with DOS, Windoze and
OS/2 drivers.  The DOS diskette has a REFRESH.EXE that one can use to
set the refresh rate.

I've booted real DOS, set rates with REFRESH, run SVGA ON DOS, renamed
SVGADATA.DOS to SVGADATA.PMI and (drum roll!) rebooted:

"Blech," I say.  It's still interlaced in all resolutions.

Larry "Blech: Sound heard around monitors laced with inters" Flynt
The Rosewood Corporation - Dallas, TX  Internet:[e-mail]
**********************************************************************

This seems to work:
 Run REFRESH this comes on the ValuePoint DOS and Drivers diskette.
 Set for best refresh rate.
 Then run SVGA ON  INIT this will create a svgadata.pmi file to keep the
 non-interlaced setting.

Works for us.

Dave Makoski
**********************************************************************

Dave,

The INIT parameter is only for the original PS/VP, I think.  The "Using
the Operating System" manual says this is for TSENG and Cirrus adapters.
My system has S3 built in the system board and SVGA ON INIT does nothing
at all on my system.

If you do have the type 2 VP (the ones with the vents on the side,) do a
FIND "Interlace" SVGADATA.PMI and tell me if it says Interlace = 0 or
Interlace = 1.

Larry "Maybe this would be easier on a non-IBM system" Flynt
The Rosewood Corporation - Dallas, TX  Internet:[e-mail]
**********************************************************************

[Reference to append at 13:09 on 94/04/25 by V$IRLATU at BCRVM1 ]

Raymond,

Have you forgotten me or just given up?  I'm the one with the IBM PS/VP
with S3 video on the system board and an IBM 15V monitor.  I can't get
noninterlaced video and surely you or someone you know can help me.

Larry "Maybe if I stop calling him 'Shirley'..." Flynt
The Rosewood Corporation - Dallas, TX  Internet:[e-mail]
**********************************************************************

Larry,

The following is the fax for changing refresh rates, I received this
from the OS/2 display group. If this does not work then you will need to
contact [phone].

    File:S3VP.fax  4/15/94

    S3 Based Value Point Systems

    Value Point systems running the S3 drivers flickers and has a
    black border around the desktop.

    DESCRIPTION OF SYMPTOMS:
    After installing SVGA support on Value Point systems monitor
    flickers and resolutions greater than 640x480x256 colors
    have a 1/2 inch black border around the
    desktop.

    SUMMARY OF RESOLUTIONS:

    Run REFRESH.EXE and set up the system to run in the highest
    re-fresh rate that the monitor can handle.

    The REFRESH program is located on the DOS CAD disk  shipped with
    Value Point systems.

    DETAILS OF RESOLUTIONS:

    1. Run DSPINSTL and set system up for SVGA mode , DO NOT RE-BOOT
    2. Open a DOS full screen session
    3.  Obtain the DOS CAD diskette that was shipped with the Value
      Point System
    4.  Switch  to the A: drive
       c:> A: <enter>
    5.  CD to the sub-directory named UTIL
       a:> CD UTIL <enter>
    6.  Run REFRESH.EXE
       a:\util:>REFRESH <enter>
    7.  Select the highest re-fresh rates that the monitor is
       capable of (WARNING)
    8.  Save changes and exit the utility
    9.  St the c:> run SVGA ON
    10.  Shut down and re-boot system

Raymond LaTulippe (Boca Electronic Support Team)
**********************************************************************


ΓòÉΓòÉΓòÉ 197. Installation Problem on PCI/ISA bus machine ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

> Originally appended to OS2INST CFORUM at 23:53:29 on 94/04/10 GMT
|
| This append is being resent as it appears to only be available on
| the Canadian shadow.
|
I am testing out a PCI/ISA bus machine with a PCI-IDE adapter.
The installation process stops at the second OS/2 logo with
the 'Loading...' message.  The floppy disk light stayed on,
while the hard drive light is off.  Suggestions ?

Kwok Fung
City of Calgary, DPSD, 403-268-1854
**********************************************************************


ΓòÉΓòÉΓòÉ 198. cid install getting msg xid10059 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

> Originally appended to OS2INST CFORUM at 01:29:36 on 94/04/15 GMT
|
| This append is being resent as it appears to only be available on
| the Canadian shadow.
|
I use cid to install cm1.1 and LS3.0 on preloaded OS/2 2.1 Valuepoint
machines. Most of the install worked OK but once in a while I ran into
this problem :
When booting from the CID diskette, SRVATTCH worked fine and attached
to the drives on the code server. When the PC was booted from the hard
drive, sometimes the SRVATTCH to the code server failed with message
xid10059 : the specified redirected drive cannot be detached. There is
no RC code associated with the message.
The NTS/2 message manual says that the message means the specified drive
has been redirected, use another drive! But the drive in question X
has never been attached to begin with. In fact that's what the SRVATTCH
is trying to do.
Anyone out there that ran into the same situation?
Thanh Nguyen - ISM
**********************************************************************


ΓòÉΓòÉΓòÉ 199. CID MMPM ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

> Originally appended to OS2INST CFORUM at 19:08:58 on 94/04/19 GMT
|
| This append is being resent as it appears to only be available on
| the Canadian shadow.
|
Is there any way to CID the MMPM installation with 2.1 GA ?

Geza Szivos <TEAM-OS2> IBMMail(CANOVXVV) The Phoenix Alliance
******  NOTE NEW PHONE NUMBERS  ******
(403)-750-3673   Fax:[phone]
**********************************************************************

Refer to Chapter 6, "Installing Multimedia on Multiple Workstations" in the
OS/2 2.1 Installation Guide.  It gives instructions on how to load the
diskettes to your hard drive, how to build a response file, and the
command to use to install from response file.  Can't say I've actually
tried it, but it does look like there's enough info there for you to
put it into your CID process.

Brent Allen - IBM Personal Systems Competency Center   Southlake, TX
**********************************************************************

Shame on me . :-)

It looks like, I have to read the manuals.<G>

Geza Szivos <TEAM-OS2> IBMMail(CANOVXVV) The Phoenix Alliance
******  NOTE NEW PHONE NUMBERS  ******
(403)-750-3673   Fax:[phone]
**********************************************************************


ΓòÉΓòÉΓòÉ 200. NETVIEW DM/2 AND DCAF ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have a NVDM/2 Server running in the same server with LAN Server 3.0
and DB2/2. All these work together fine when NVDM/2 is given the alter-
nate adapter solely for it to use and DB2/2 and LS3.0 use the primary
TR -adapter. The problem is that I would like to use DCAF to control
the NVDM/2 and LS3.0, and when I install and start DCAF Netbios target
the NVDM/2 gets very slow. Actually when I give a CDM INSTALL -command
from the NVDM/2 server when DCAF target is running it takes from 1 hour
to 2 hours before the NVDM/2 -client machine will run the install.
If DCAF is not started on the NVDM/2 server then the install starts
immediately in the NVDM/2 client machines.
Syslevels on the NVDM/2 server are :
 LAPS : WRU6000, LS3.0 : IPU7001, OS/2 2.1 : XRU2010, DCAF 1.1 : UB00000,
 NVDM2 : XR20302, DB2/2 : WRU7000

Markku Vieri, Oy Tietokonepalvelu Ab, Finland

This append was created on the External IBMLink system by
Oy Tietokonepalvelu
**********************************************************************

Oy,
You're getting contention on the single adapter.  Try increasing your
Netbios resources.

Ken Hygh      Rome Networking Systems Lab   kenhygh-vnet.ibm.com
NetView Distribution Manager Planning & Design
39.06.5966.2762
**********************************************************************


ΓòÉΓòÉΓòÉ 201. KBD01.SYS not found during install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Has anyone seen this one?

   I installed 2.11 the release with all the CSDs from OS2PROD2
last night. after making it through 4 disks without error, install
told me to remove the diskette and press enter. When install started the
IPL it got an error saying that KBD01.SYS could not be found, or the
CONFIG.SYS pointed to the wrong place for it. I found no reference
to KBD01.SYS in the CONFIG.SYS file. So I tried copying KBD01.SYS
to all the subdirectories and tried a reboot. The system still will not
IPL saying KBD01.SYS is not found or config.sys is not pointing the the
right place. So I tried putting DEVICE=C:\OS2\KBD01.SYS in the config.sys
still gives the same error.

Does anyone have any ideas?

I have a 486/66mhz/16meg, 1 gig SCSI Hd, Matrox(2m), Zenon system.

                   Thanks for any help, Jim
**********************************************************************


ΓòÉΓòÉΓòÉ 202. HP install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I am trying to install OS/2 2.1 GA on a Hewlett-Packard Vectra XP/60 Pentium.  This has an S3 928 video chipset.
This is a remote install from a Novell LAN.  When prompted to reboot after the initial files are copied I reboot and the
system hangs on the bubble screen the upper half of which is very distorted.

Also, several files, including OS2KRNL, are not copied to the target drive during the first part of installation.
The first part of remote installation corresponds to the first five diskettes of a manual installation.

Thanks,

  Craig Bugg

   Roadnet Technologies, Inc.
**********************************************************************

Craig,

What was the video set for prior to installation? For installation to go
more smoothly it should be set to VGA 640 x 480! After the OS is
completely installed then you set the higher resolutions!

Raymond LaTulippe (Boca Electronic Support Team)
**********************************************************************


ΓòÉΓòÉΓòÉ 203. 640x480x256C on 8514/a Adapter ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Can I get this resolution on my 8514/a adapter?  It tells me when I
try to use selective install or DSPINSTL that my installed adapter
is not compatible with the desired screen mode.  Is that really true?
I do believe that I have the expanded memory on the 8514 card.

I want to run a windows application either on my desktop or in a win-os2
full screen session.  This app needs 640x480x256c to run properly.

I saw an append about tweaking my system.ini but the example was
changing from an XGA to SVGA.  Is there a procedure for changing
8514 to SVGA by tweaking the system.ini?  I suppose I may have to
copy drivers from the OS/2 original disks..

Kahn, S.R.
**********************************************************************


ΓòÉΓòÉΓòÉ 204. Disk space needed for OS/2 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

In the install instructions for OS/2, it states that 20-40 MB of space
is needed (+5MB for MMPM). How much of that install space comprises
room set aside for the swap file, or is that separate (additional space
needed)? I don't want to make my OS/2 partition any bigger than needed.

Keith Garvens
**********************************************************************

Kevin,
I don't believe that any of the space listed is reserved for swap file.
You can put the swap file on any disk that you desire, during installation
or later by editing CONFIG.SYS, and changing the SWAPPATH.

Jack Hiatt
MARC-Life         404-394-5665 ext.355
Atlanta Ga.        T.I.P.A       Team OS/2
**********************************************************************

Actually, I believe the 20-40 meg figure includes a 4 meg swap file.
I was reading through some class material from Skills Dynamics and it
said that 2.1 uses 16-36 meg, plus the 4 meg swap file to get the
20-40 figure.

Brent Allen - IBM Personal Systems Competency Center   Southlake, TX
**********************************************************************

Brent,
I stand corrected.  I also came across the same statement in something else
that I was reading this afternoon and was going to modify my original
append.

Jack Hiatt
MARC-Life         404-394-5665 ext.355
Atlanta Ga.        T.I.P.A       Team OS/2
**********************************************************************


ΓòÉΓòÉΓòÉ 205. Setup for PS/2 w/ 9525 Monitor ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Question - Under OS/2 setup, SYSTEM option, when selecting video mode should
there be a unique selection to identify an IBM 9525 monitor?  If not, what
is the recommended setting.  I run a PS/2 77 with a 9517 and there is a
unique selection for the 9517.  My boss has a new system, PS/2 77 with a
9525 monitor.  I don't see a selection for the 9525.  The insultants that
set up her machine selected 8514 mode, which of course gave it a horrible
interlaced flicker.  I have temporarily changed the mode to the selection
identified as 15" VESA; this has improved the display but I am wondering
if there is something better.  Since the monitor is sold as one of the
"premium" monitors, I'm hoping there is something out there.  Ideas?

Karl S. Huf  The Northern Trust / Chicago
**********************************************************************

 I have a faint recollection that when IBM came out with the 952x
monitors they changed the pins so that they would identify themselves
to adapters as 8514s ... something to do with being best solution
to allow their new and improved monitors to run with anyone's
adapter (i.e. market competition) I think the suggested solution at
the time was with XGA-2 adapters is to chose the 951x monitor and
everything would be OK ...

Keith Blake (The OS/2 Mole) V: [phone] (IBMMAIL/USPGC9GC)
**********************************************************************

[Reference to append at 13:15 on 94/04/27 by TNT1106 at SHOPER3 ]

I am in the unique position of being able to answer my own question
I contacted the Personal Systems HelpCenter @ 1-800-PS2-2227 and asked
the same question - how should I setup OS/2 for the 9525 monitor?
I was told that there is a new level of the XGA support files that I
could get off the support BBS.  I got XGA211.DSK and, after running the
program to convert that file to an install disk, installed the XGA
support files onto the PS/2.  This updated the selection list available
under SETUP, SYSTEM, to include a 9525 option.  The display is MUCH
better now.  A previous post indicated that 8514 was a viable option;
I must disagree.  If you do not have the XGA211 files, get them.  In the
meantime, the best compromise is the VESA 15" option.  The 8514 interlaces
badly; don't use it.

Karl S. Huf  The Northern Trust / Chicago
**********************************************************************


ΓòÉΓòÉΓòÉ 206. OS/2 2.1 install dies during reboot after disk5 ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I have a friend installing OS/2 2.1 on a PS/2 Model 95.
After disk 5 when the system is supposed to re-boot; black screen
and lockup results.

Any ideas?

Couild it be related to the fact that he formatted his hard drive
from his OS/2 1.3 disks?

Thanks
Ken Prince E.I. DuPont
[e-mail](Internet)
IBMMAIL(USDUPGVW)
**********************************************************************

Ken,

This is a video problem, format the disk and install DOS and set the
system to VGA 640 x 480 mode. After OS/2 is installed he can then change
to a higher resolution.

Raymond LaTulippe (Boca Electronic Support Team)
**********************************************************************


ΓòÉΓòÉΓòÉ 207. Video setup and strange display problems ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

I just installed OS/2 for Windows. I was wondering if it was normal that
to change video modes, you must go through Selective Install each time?
The machine originally came up 640x480 (VGA - whatever the numbers are).
I wanted to change to 800x600 and was lead through the Selective Install
process, which then called for stuff of my Windows diskettes. Fine. All
looks good. Then to see happens, I tried changing to the next highest
resolution (10xx x 7xx - don't remember the values). Again, the same
procedure of asking for Windows diskettes. The thing is, it seemed to be
loading the same files that it did for the 800x600 change. Changing back
to 800x600 - same thing. And yes, I rebooted in between each change. Why
such a convoluted path to change video modes? Also, sometimes the machine
starts to boot and the initial OS/2 logo screen is 'squished', looking
like it was compressed from the top and bottom. WS comes up OK, though.

Keith Garvens
**********************************************************************

Because of contractual agreements, the Selective Install process must be
used to update the Microsoft code for Windows 3.1.  If you were
modifying the video resolution running OS/2 2.1 Standard Edition you
could use DSPINSTL.

Tom Haug  Boca Electronic Support Team
**********************************************************************


ΓòÉΓòÉΓòÉ 208. Installing OS/2 for Windows ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Does Windows have to be in any particular setup state in order for OS/2
for Windows to install correctly? In particular, the video resolutions?
My video has been screwed up ever since I installed OS/2 last Friday and
I've been told that if OS/2 and Windows were set up with different video
resolutions that strange things may happen. I started with a clean slate
and installed MS DOS 6.2 and Windows 3.1. Windows, by default, was VGA,
which I believe is 640x480x16. I then installed OS/2 and took it's
defaults of VGA for the primary monitor. After that and in no particular
order, I changed both to 800x600x256. Both seem to display correctly in
their respective environments.
What I am seeing is:

1. AT TIMES, during bootup, the OS/2 logos are squished top and bottom -
  egg-shaped instead of circles. WPS comes up looking OK
2. AT TIMES, during bootup, the OS/2 logos are scrambled, like the video
  is out of sync. WPS comes up looking OK.
3. Every DOS session requiring graphics is either producing a double
  image (the screen image is split top and bottom, with the same graphic
  displayed in each half) or is scrambled, as in #2.

Now I have an ET4000-based video card tha comes with the VMODE.COM setup
program. When should this be run - before OS/2 is installed, during
install when it is asked for at the video setup screen, or when? And
might this be the problem?

Keith Garvens
**********************************************************************


ΓòÉΓòÉΓòÉ 209. Disabling Turbo Mode before install ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Could some knowledgable person address why it is suggested that Turbo
mode be turned off on non-IBM machines before OS/2 install? Now the
READNE explicitly mentions 'turn it off in the CMOS settings'. On my
GW2000 machine, I have a CMOS setting for it, but also have a front
panel button. When CMOS is set to Turbo Fast, the button is overridden.
Then CMOS is set to Turbo Slow, the button is supposed to control whether
the machine runs fast or slow. Does the processor actually need to be
running slow (Turbo mode REALLY off) or does just the CMOS setting need
to be set to Slow? More importantly, what are the consequences for not
doing this?

Keith Garvens
**********************************************************************

There is no easy answer.  What it comes down to is that various turbo modes on
some machines confuse the install code -- make OS/2 think you've got a 486
when you've really got a 386, or other mistakes of that kind, and you'll end
up with an installed OS/2 that won't work.  IBM does its best, but there is no
standard way for OS/2 to ask the system for hardware details, and many users
don't even know the answers to many of the questions, so the install program
has to do ugly tricks like spinning on a useless loop, seeing how long it
takes, and making deductions about the hardware from that.  On _most_
machines, OS/2 will run fine in turbo mode once it is installed.

Some turbo "switches" (especially ones that work off funky keystrokes) only
work because they trigger some code in a DOS device driver; these won't work
under OS/2 -- at least on the install code -- so you should take the most
certain and positive way that your particular machine has of ensuring that
turbo is off

John W. Kennedy - Hoechst Celanese - TIPA - Team OS/2 - The OS/2 Hobbit
**********************************************************************

[Reference to append at 16:32 on 94/05/03 by KRG at RCHVMP3 ]

The main reason that "Turbo" mode is recommended to be turned off during
installation is that the installation process involves processing the
disk reads/writes in an overlapping IO mode in an attempt to speed up the
install process.  Since the bus speed in most systems is still about 8 to
10 mhz, which is much slower than the cpu speed, it is possible to get
files incompletely written or written incorrectly if the processor fails
to stay in sync with the disk processing, this may not show up during the
install, but may cause a failure later during operation when the bad
files are called.  This recommendation was made to try and head off user
problems that "could occur."  Many systems will install properly with
turbo on, but it is impossible for the install program to tell if the
one you are using will be ok.  It should make no difference whether you
use the cmos setting or disable it with the "turbo" button.

Alan Newman IBM / Boca Electronic Support Team
**********************************************************************


ΓòÉΓòÉΓòÉ 210. DOS CANNOT BE STARTED ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

We use the CID method to install OS/2 2.10 on various PCS.  Sometimes
when it boots for the 2nd time.. (the first time it boots on it's own)
it says 'DOS CANNOT BE STARTED' as one of the error messages.  Even with
the CID response file indicating install dos and format... it doesn't
seem to get installed.. hence this message.
The PC is a DELL NETPLEX 433/p.  I also got this once on a thinkpad, but
i seem to get it on several of these dells.
Any ideas?

Maria Miano - UPS
**********************************************************************


ΓòÉΓòÉΓòÉ 211. OS/2 Driver for COMPAQ QVision 1024/E Video Card ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Does anybody know of an OS/2 driver for the above card, fully
exploiting its huigh resolution capabilities?

Gerhard Heger
**********************************************************************


ΓòÉΓòÉΓòÉ 212. HPFS with a disk controller with HW Cache ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

If I have a dsik controller with a hardware cache, is there a chance
to turn off the HPFS software cache? Do I need a specific driver
for the disk?

Gerhard Heger
**********************************************************************

Gerhard,

The HPFS parameter should take into consideration the caching
capabilities of your controller card when OS/2 is installed.
This should reduce the amount of RAM set aside in the PC system.

The harddrive controller card must be listed in either the OS/2 Using
manual or in the README for the Operating system in order to use the OS/2
supplied drivers.

Most IDE controller cards are supported.  There are a limited number of
SCSI cards supported.

If the card is not listed in either the OS/2 Using manual or the README
files found on the OS/2 diskettes, please contact the controller card
manufacturer for OS/2 drivers.

Tom Haug  Boca Electronic Support Team

**********************************************************************


ΓòÉΓòÉΓòÉ 213. SYSTEM SETUP ΓòÉΓòÉΓòÉ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

On my model 95 I have a SCREEN tab on my system setting.
I have just installed OS/2 2.1 GA on a 9556 with a 6327 display.
I opened the system setting and there is NO SCREEN tab.  How did
it appear on my 95 and not on the 56?

THANKS in advanced.

Victor M. Yellen
Provost Office University of Florida
Internet= Victor.nw.mail.ufl.edu