Warp 4 + S3 Virge/DX with 2 MB RAM
Mike Lam
I couldn't make the S3 Virge/DX to function under Warp 4.
The screen simple corrupted after I installed S3 drivers.
- Warp 4 base
- Warp 4 with FixPack 4
- S375 card with S3 Virge/DX chip and Eagle BIOS
- S3 1.02.03 driver from S3 site
- S3 1.01.03 driver from S3 site
I have to fallback to vga using F3 key
L. Mark Bruffey
get matrox, get rid of virge, get rid of problems.
mark
Dan Casey
In article <346c190c$5$qnivqjrv$mr2...@news.mdi.ca>, nos...@mdi.ca wrote:
>In <346919...@voicenet.com>, on 11/12/97
> at 01:48 AM, "L. Mark Bruffey" <mbru...@voicenet.com> said:
>
>>get matrox, get rid of virge, get rid of problems.
>
I just bought an Elsa Winner 3000S and it works fine (for a $99.00
video card), but it DOES have an S3 Virge chip on it.
--
****************************************************
* Dan Casey Doesn't "Microsoft" *
* Team OS/2 Mean "Small & Limp"? *
* Abraxas on IRC *
* To Reply by E-Mail.....ROT13 my Address *
****************************************************
* PGP Public Key Available on my Web Page *
* Or E-Mail me with a subject of PGP Key *
****************************************************
* Visit my Web Site at: *
* http://www.geocities.com/SiliconValley/Bay/3031 *
****************************************************
L. Mark Bruffey
Dan, what model is your S3 chip? Mine was a 325. Perhaps the later
models have corrected the problem?
Mark Bruffey
Dan Casey
In article <346DCF...@voicenet.com>,
"L. Mark Bruffey" <mbru...@voicenet.com> wrote:
>Dan, what model is your S3 chip? Mine was a 325. Perhaps the later
>models have corrected the problem?
I'm not sure what it is, and I'd have to crack open the box to
look....rmview, hardware manager and the Elsa Utility don't show the
model number of the chip. Splash Screen (at system boot) shows version
4.05.0, but I can't see the screen long enough to see exactly WHAT
it's a version OF.
If you really need to kmow, let me know, and I'll open the box and
look at it.
Trevor Hemsley
On Sat, 15 Nov 1997 12:43:28 -0500, Dan Casey wrote:
->In article <346DCF...@voicenet.com>,
->"L. Mark Bruffey" <mbru...@voicenet.com> wrote:
->>Dan, what model is your S3 chip? Mine was a 325. Perhaps the later
->>models have corrected the problem?
->
->I'm not sure what it is, and I'd have to crack open the box to
->look....rmview, hardware manager and the Elsa Utility don't show the
->model number of the chip. Splash Screen (at system boot) shows version
->4.05.0, but I can't see the screen long enough to see exactly WHAT
->it's a version OF.
->
->If you really need to kmow, let me know, and I'll open the box and
->look at it.
SVGA STATUS from a fullscreen DOS prompt might tell you as might the
contents of SVGADATA.PMI. You'll probably have to pipe SVGA STATUS into
MORE to be able to see the relevant bit.
Trevor Hemsley, London, UK
(Trevor-...@dial.pipex.com or 75704...@compuserve.com)
L. Mark Bruffey
That's OK, Dan. Don't go to all that trouble. It's not worth it, I
think.
Thanks,
mark
Dan Casey wrote:
>
> In article <346DCF...@voicenet.com>,
> "L. Mark Bruffey" <mbru...@voicenet.com> wrote:
> >Dan, what model is your S3 chip? Mine was a 325. Perhaps the later
> >models have corrected the problem?
>
> I'm not sure what it is, and I'd have to crack open the box to
> look....rmview, hardware manager and the Elsa Utility don't show the
> model number of the chip. Splash Screen (at system boot) shows version
> 4.05.0, but I can't see the screen long enough to see exactly WHAT
> it's a version OF.
>
> If you really need to kmow, let me know, and I'll open the box and
> look at it.
>
> --
> ****************************************************
> * Dan Casey Doesn't "Microsoft" *
> * Team OS/2 Mean "Small & Limp"? *
> * Abraxas on IRC *
> * To Reply by E-Mail.....ROT13 my Address *
> ****************************************************
> * PGP Public Key Available on my Web Page *
> * Or E-Mail me with a subject of PGP Key *
> ****************************************************
> * Visit my Web Site at: *
> * http://www.geocities.com/SiliconValley/Bay/3031 *
> ****************************************************
Michael Peters
Dan,
I have a utility here..S3id.exe that runs in a dos window and
gives
the chip info without my having to take the lid off. Got it from
the
S3 web page I think.
Mike Peters
Replying to a message of Dan Casey to all:
DC> In article <346DCF...@voicenet.com>,
DC> "L. Mark Bruffey" <mbru...@voicenet.com> wrote:
>> Dan, what model is your S3 chip? Mine was a 325. Perhaps
the later
>> models have corrected the problem?
DC> I'm not sure what it is, and I'd have to crack open the box to
DC> look....rmview, hardware manager and the Elsa Utility don't
show the
DC> model number of the chip. Splash Screen (at system boot)
shows version
DC> 4.05.0, but I can't see the screen long enough to see
exactly WHAT it's
DC> a version OF.
DC> If you really need to kmow, let me know, and I'll open the
box and
DC> look at it.
DC> --
DC> ****************************************************
DC> * Dan Casey Doesn't "Microsoft" *
DC> * Team OS/2 Mean "Small & Limp"? *
DC> * Abraxas on IRC *
DC> * To Reply by E-Mail.....ROT13 my Address *
DC> ****************************************************
DC> * PGP Public Key Available on my Web Page *
DC> * Or E-Mail me with a subject of PGP Key *
DC> ****************************************************
DC> * Visit my Web Site at: *
DC> * http://www.geocities.com/SiliconValley/Bay/3031 *
DC> ****************************************************
DC> -!- YARN + VSOUP + YEP + TEDIT in Warp 4.0
DC> ! Origin: Team OS/2, Indianapolis, IN (0:0/0)
DC> =
Michael Peters
mpe...@netspace.net.au
NewsWave/FleetStreet [OS/2]
Dan Casey
In article <vweikcwuyvmqqoolrugpu.pminews@trevor>,
Thanks for the tip, Trevor, but it doesn't show the model number of
the chip.
From the SVGADATA.PMI file on that box:
[PMIVersion]
2.15
[AdapterType]
S3
[ChipSet]
S3VIRGE
#includecode "S3PMI.DLL";
[Hardware]
BusType = PCI
OEMString = "S3VIRGE PLANAR, S3 Incorporated"
Version = "ELSA WINNER 3000-S"
---------------------------------------------------
My curiosity got the better of me....
From the chip itself...
S3 ViRGE
N1C3BD
86C325
9633 C14333.00
BTW, my first response on this subject was in response to the poster
who recommended getting rid of the S3 Virge card to solve the problem.
He then went on to recommend a Matrox card or an Elsa card (to which I
responded that the Elsa cards use the S3 Virge chipset).
--
****************************************************
* Dan Casey Doesn't "Microsoft" *
* Team OS/2 Mean "Small & Limp"? *
* Abraxas on IRC *
* To Reply by E-Mail.....ROT13 my Address *
****************************************************
* PGP Public Key Available on my Web Page *
* Or E-Mail me with a subject of PGP Key *
****************************************************
* Visit my Web Site at: *
nos...@mdi.ca
DC> I'm not sure what it is, and I'd have to crack open the box to DC>
look....rmview, hardware manager and the Elsa Utility don't show the DC>
model number of the chip. Splash Screen (at system boot) shows version DC>
4.05.0, but I can't see the screen long enough to see exactly WHAT it's DC>
a version OF.
My guess is that is is ViRGE VX, model number 375... I think that's what
Elsa uses...
===Proud Member of Team OS/2, Team OS/2 at Taiwan, ICENews Beta Tester===
===================And Bovine Team Warped Key Crucher====================
NUTS' Home Base
US Mirror http://www.cybermail.net/~davidwei
Taiwanese Mirror http://www.taconet.com.tw/~davidwei
光碟月刊 OS/2 技術編輯 <<>> Hope_Net CD-ROM Monthly, OS/2 Editor
Mike Lam
To get chipset type, you can extract the S3CHIPID.EXE from the
driver disk, eg. from www.s3.com - s375 driver for os/2 has it.
1. From the driver files, extract the S3CHIPID.EXE
ie. unpack prereq.pk2 .\
(the exe is in prereq.pk2 and ".\" mean output to current directory)
2. Write a simple rexx cmd:
/* begin **/
's3chipid.exe'
say RC
/* end */
3. The command file will print out the ID number, which is:
1 = 801/805
2 = 928
3 = 911
4 = 864
5 = 964
6 = 868
7 = 968
8 = Trio32
9 = Trio64
10 = Trio64V+
11 = Aurora64V+
12 = ViRGE
13 = ViRGE/vX
14 = Trio64UV+
15 = Trio64V+Compatible
16 = Trio64V2
17 = Yosemite
18 = ViRGE/DX-GX <== I'm using this in VGA mode only :<
19 = ViRGE/GX2
20 = ViRGE+COMPATBLE
I guess my problem may be due to the video card's onboard RAM not fast
enought, it says 50ns? (corrupted display during booting if using high
resolution than VGA)
Good luck
arn...@ausnews.austin.ibm.com
Is this an increasing order of "betterness"? That is, is a Trio64V2
better than a ViRGE?
thanks,
arnold
Mike Lam (mik...@hkstar.com) wrote:
: 3. The command file will print out the ID number, which is:
Mark Klebanoff
arn...@ausnews.austin.ibm.com wrote:
>
> Is this an increasing order of "betterness"? That is, is a Trio64V2
> better than a ViRGE?
>
> thanks,
> arnold
I don't know, but I do know that I've managed to get my Diamond
Trio764V+ working pertty well under Warp 4 (knock on wood). Not too
many people can say the same about the Virge Chip. If you can't get it
working, then it really doesn't matter how good it is.
Trevor Hemsley
On 21 Nov 1997 03:57:51 GMT, arn...@ausnews.austin.ibm.com wrote:
->Is this an increasing order of "betterness"? That is, is a Trio64V2
->better than a ViRGE?
Just looks like chronological order of release date to me...