SCOUG-HELP Mailing List Archives

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

Date:	Thu, 23 Aug 2001 20:47:05 PDT
From:	"mrakijas" <mrakijas@oco.net >
Reply-To:	scoug-help@scoug.com
To:	<scoug-help@scoug.com >
Subject:	SCOUG-Help: Video driver install problem

Content Type: text/plain

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

Okay, this is getting embarassing. I'm still

working on the same machine on which I performed the

motherboard upgrade. Everything was progressing

okay in that things are getting fixed up and I
managed to install the network drivers appropriate

for the new PCI network card. Now it's the video

card drivers that are giving me trouble. The card

itself is an 8 MB S3 Trio 3D/2X based card. I've

had good luck with S3 cards in the past, at least

when I wasn't choosing a Matrox card.

So, I found the latest, greatest video drivers

appropriate for the chip. The file was called

20001ENG.ZIP, specifically claims support for the

Trio 3D/2X, is version 2.00.01 and was released
22 Jun 1999. I ran the SETUP.CMD file (yes, I read

the readme first). It recognized the fact that the

Warp version reported is newer than 2.4 (i.e. Warp

4) since I have FixPak 14 in the machine and warned

that it may not be appropriate. Of course, this

should be no problem so I proceeded. Files get

copied but once it's actually trying to install the

video drivers to get used, it soon errors out. The

best I can tell, the command file can't run

DSPINSTL.EXE (mostly since DSPINSTL.EXE won't run

from the command line either) but I'm not sure why.

There might be a dependence on SVGA.EXE but SVGA.EXE

otherwise runs and generates an SVGADATA.PMI file as

you would expect. Below is the snippet of code from

the CMD file doing the install (for reference) that
sets up the parameters for DSPINSTL.EXE. I can read

enough of the command file that I verified that all

the previous stuff, mostly file copying type stuff,

executes as expected. I think the CMD file is

irrelevant - why won't DSPINSTL.EXE run from the
command line? Please don't suggest SDD, though.

I'm not ready to start futzing around with that yet

- that's a future experiment. As before, thanks

again in advance for any ideas you might have.

-Rocky

call unpack 'prereq.pk2' trg||'\os2\svga.exe'
call saylog "Starting OS/2's display install

program..."
say ''
/* set up parameters for dspinstl.exe */
call stream log, 'c', 'close'
dspinstl = trg||'\os2\install\dspinstl.exe'
dspsrc = right( src, 1 )
if (dspsrc <> '\') & (dspsrc <> '/') then
dspsrc = src
else
dspsrc = left(src, length(src)-1) /*

dspinstl: no trailing slash */
dspopt = '/pk:other /sk:none /s:'dspsrc' /t:'trg
if os2ver = 2.11 then do
dspdsc = '/pd:'src'S3MISC1.DSC'
dcmd = dspinstl dspopt dspdsc cid
rc = lineout(log, dcmd)
''dcmd
end
dspdsc = '/pd:'src'PVIRGE.DSC'
dcmd = dspinstl dspopt dspdsc cid

____________________________________________________
__
Sent via the oco.net WebMail Server

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

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

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

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

Return to [ 23 | August | 2001 ]

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