Документ взят из кэша поисковой машины. Адрес оригинального документа : http://crydee.sai.msu.ru/ftproot/pub/misc/doc/os2.hints/diamond-warp Дата изменения: Sun Aug 20 21:14:52 1995 Дата индексирования: Sun Apr 10 19:47:52 2016 Кодировка: Поисковые слова: vallis

From ns.itep.ru!CERN.ch!EU.net!newsfeed.internetmci.com!news.mathworks.com!zombie.ncsc.mil!simtel!harbinger.cc.monash.edu.au!yarrina.connect.com.au!news.starway.net.au!news.internex.net.au!usenet Sun Aug 20 21:14:53 1995
Path: ns.itep.ru!CERN.ch!EU.net!newsfeed.internetmci.com!news.mathworks.com!zombie.ncsc.mil!simtel!harbinger.cc.monash.edu.au!yarrina.connect.com.au!news.starway.net.au!news.internex.net.au!usenet
From: jplrepo@connexus.apana.org.au
Newsgroups: comp.os.os2.setup.video
Subject: How I got my Stealth 64 VRAM 2meg to work with OS/2
Date: 17 Aug 1995 10:03:00 GMT
Organization: Connexus Internet
Lines: 45
Message-ID: <40v44k$4qc@preeda.internex.net.au>
Reply-To: jplrepo@connexus.apana.org.au
X-Newsreader: IBM NewsReader/2 v1.2

For anyone who is interested this may help...
After months of frustration I finally got my Stealth VRAM drivers to work with OS/2
As with everyone previously you have to make the necessary changes to
S3INST.CMD to change all references from \OS\ to \OS2\BOOT....
Run the S3INST.CMD file, it's a good idea to keep another copy of your
SCREEN0?.SYS files from the \OS2\ directory just in case the REXX command file
doesn't do it's job.
The main things that this REXX file does is extract the new SCREEN0?.SYS files and
a new SVGA.EXE file, changes PSS3.DSC in \OS2\INSTALL and adds a display driver
icon to your OS\2 System System Setup Folder.
I found that when you get to the reboot stage after running S3INST.CMD that I
needed to copy SCREEN0?.SYS to both \OS2\ and \OS2\BOOT directories.
Reboot, now you will be started with the new drivers but it aint over yet...
Run SVGA.EXE from a DOS Full screen window. this will create your SVGADATA.PMI
file in the \OS2\ directory. Without this your monitor won't synch. And if you run
the SVGA.EXE that is installed by S3INST.CMD after rebooting it should recognise
your card. If anything has gone wrong to now SVGA.EXE won't know what kind
of card you have.
You now have to copy back the old SCREEN0?.SYS files to the \OS2\ directory and
reboot.. Now the system is in standard VGA mode again.
Now run the Display Driver install Icon from your Os\2 System System Setup folder.
This will extract files from S3VIDEO and S3WIN from the driver disks and change
your OS2.INI and CONFIG.SYS files. It should also copy SCREEN0?.SYS from your
\OS2\BOOT directory to your \OS2\ directory.
Ok, almost there, I had a great deal of trouble running this part of the install,
It seems that UNPACK2.EXE caused several access violations. I eventually got around
it by REM'ing out BASEDEV commands from my CONFIG.SYS except for the Hard
Disk and Floppy drivers. I still had problems, so i found copying the floppies to my hard
disk and running the driver install icon, point to your hard disk instead of drive A:
Eventually I got everything to run through ok from the display driver install icon.
If you get a message saying your graphics card is not known or something like that
ignore it. When it asks you to select your monitor configuration utility
select Install using Display Adapter Utility Program.
Then specify the path to your S64MODE.EXE program. For me it went like this:
C:\S64\UTIL\S64MODE.EXE MONITOR
You have to preconfigure S64MODE.EXE to your monitor type, and as the instructions
say you can't use the User Defined monitor. Try to find one that has the same
synch rates as your monitor.
After running all of this through the display driver install icon and rebooting...
Hopefully your system settings will then show all the different resolutions supported
by your new drivers.
Hope this helps some of the people who have been posting here....
Or you could try the Disgruntled Diamond WWW page:
http://www.gladstone.uoregon.edu/~trenton/diamond