When you install the Steath 64 drivers you will get a    ".dsc error."

The offending .dsc files are the wd*.dsc files in the ins.  Rename them
to wd*.dsb or whatever ...the Warp drivers will then install correctly.

BTW, if your drivers don't work well, Try the ST64Video(968) drivers ver
1.00 from the Diamond lib (even though they are not supposed to work
with the non-accelerated 964 chip).

>>>>>I tried to install the newest diamond video drivers fro OS2 warp
last night.  Now, when I try and run the DSPINSTL program I get:
"Display driver installation detected an invalid argument count in a
configuration file .dsc.  Check the file."

I tried to reinstal, same thing. What happenned and how do I fix it?<<<<<

You will want to restore the DSPINSTL.EXE that shipped with Warp, into
the \OS2\INSTALL directory on your OS/2 drive.  There should be a file
by the name of DSPINSTL.SAV.  If this file is dated 1995, you should be
able to copy DSPINSTL.SAV to DSPINSTL.EXE, to correct the problem.
Otherwise, you will need to have it reinstalled from OS/2.

>>>>> They work, but fine wouldn't be my description of it!  I can't get
1024 X 768 out of your OS/2 drivers, but can in Windows??  I have a 2meg
Diamond stealth Vram which can't make up it's mind if it's a VLB or
PCI!!  (referring to the bar at the top of the screen on boot up)<<<<<

What version of the BIOS does your Stealth card have? 

You should have at least version 1.05.

Which monitor did you select under S64MODE for the driver installation?
The custom monitor option is not supported under OS/2 so if you use a
customer configuration you will need to open a full screen DOS session.
Run s64mode and choose a pre defined monitor.  Then go to your os2
directory, without closing the DOS session and run SVGA ON.

Our card and driver will support 1024x768 under OS/2 2.1 and Warp.

>>>>>Help!  Having problems getting Warp drivers installed.

 I have downloaded the drivers and faithfully (I think) followed the
instructions.  As soon as I get into the "Primary Display Driver List"
and choose "32 Bit S3 Display Drivers V2.4" and click "OK" I get a
dialog box telling me "The installed adapter does not support the
selected display driver.  Do you wish to continue?".  I'm not brave
enough to tell it "OK".

 Questions: the downloaded drivers are identified as being for OS/2 2.1.
They *are* okay for Warp, aren't they?<<<<<

Yes, those drivers work fine with Warp, I use them myself.

>>>>> FYI: The MSD routine identifies my video card as Diamond, BIOS
Version Stealth 64 DRAM Vers.  2.01, Video BIOS Date 10/26/94.  VESA
Version 1.02, VESA OEM Name: S3 Incorporated.  Vision864.<<<<<

You will need to check for two files in your OS/2 directory,
SCREEN01.SYS, and SCREEN02.SYS, make sure that they are not read only.
You will want to reinstall the VGA driver using Selective Install.  Then
you will want to reboot, OS/2, and run S3INST from the floppy drive.
Once it has completed execution, you will want to reboot OS/2.  Then you
will want to run the DIsplay Driver Install, and select the 32-bit S3
Display Driver.  It should then install with no problems.


>>>>>Seamless Windows, apparently, simply aborts in loading.  The OS2
clock appears and persists for about 45 seconds, and then the mouse
pointer returns to the desktop without any indication of what caused the
loading to abort.  I had thought I might diagnose the problem by
attempting to load windows in a DOS window using WINOS2.COM to create a
log file, but that proved very scary.  The attempt resulted in a black
screen which wouldn't respond to anything.  To make a long story short,
I spent a couple of hours attempting to restore OS2 without success and
ended up 'booting' to DOS.  I then discovered that all SVGA modes were
completely inoperative and any attempt to activate SVGA in any program
resulted in a black screen and system lock-up.  All my boots during this
period were warm.  Fortunately, when the computer had been powered off
for a period, when it was turned on again, everything was restored to
normal.  It appeares that my attempt to load WINOS2.COM had rendered all
SVGA modes completely inoperative as long as the system remained
powered-on)!  Unfortunately, I got no log file out of the exercise (and
don't intend to repeat it out of fear of screwing-up the card
permanently).  To get a life back, I'll have to ignore seamless Windows
until you recognize that some of us have a real problem and decide to
help us with a fix, or I repace the card (please don't suggest another
Diamond product - at this point the volume and character of messages to
your forum are not very reassuring.  Any new ideas?<<<<<

I have had a number of reports of this problem.  This should not occur,
provided that you used the OS/2 for Windows Installation Text for the
Stealth VRAM, and had the VGA, not SVGA, driver installed into OS/2 when
installing the driver.

>>>>>This is the error explanation and register information:
sys3175
An access violation exception occurred and was generated when an attempt
was made either to load or store data in an inaccessible location or to
execute an inaccessible instruction.  This exception corresponds to both
the Intel 80386 processor general protection fault (#13),caused by an
invalid access attempt, and the page fault (#14), caused by an attempt
to access an uncomitted page or page with incorrect attributes for the
desired operation.

A program generated an access violation at 00016a8c
UNPACK2.exe 0001:00006a8c<<<<<

The following is a resolution from IBM regarding this type of error
during installation of Warp.  This may apply to the problem you are
experiencing with installing the driver.

=====================================
RESOLUTION

    Remark out the basedev=xxxxxxx.add from config.sys on the harddrive
    except ibmint13.i13 and ibm%flpy.add and the cdrom
    controller device driver (Where xxxxxx can be any character and % is
    replaced by 2 for microchannel system and a 1 if any other system).
    Also refer customer for possible 174 in Users Guide to OS/2 book
    additional explanation and actions.
    If customer has Ethernet Card (NE2000 Compatible), ask to
    customer to remove it (PJ15955).
=====================================

