Thread View: comp.os.os2.setup.video
3 messages
3 total messages
Started by Robert Eddy
Tue, 08 Apr 1997 00:00
Setting up the ET6000 device drivers
Author: Robert Eddy
Date: Tue, 08 Apr 1997 00:00
Date: Tue, 08 Apr 1997 00:00
37 lines
2279 bytes
2279 bytes
I am running Warp V4 without any fixpacks and am trying to get a new ET6000 video card to behave. The card is installed in the machine (P120, 32M RAM and with Samsung 15GLe monitor) and operates correctly with Win95 and Win 3.1 which reside on other partitions. My problem has evolved this way: I installed the ET6000 and drivers for Win95 & Win3.1 on their respective partitions without problems using the drivers which came with the ET6000. I downloaded the latest drivers from IBM for Warp 4 & created the disk using the loaddskf, printed the instructions and installed the driver using the recreation of the SVGADATA.PMI procedure. The machine and the card then worked perfectly - I could change screen size, pallettes etc without problem. The only problem was that the machine would freeze (hard reset only to recover) when I entered any WinOS2 program. After some thought I decided to reinstall the drivers. The problem I now face is that I get to the part in the installation program where the "svga.exe on monitor" is run and everything stops. The screen goes blank and the DOS Full Screen window appears with the sign on message from svga.exe saying its version 2.51 and the program apparently hung. Recovery via ctrl-esc and then closing the program is the only way to recover. It appears to me that the problem may be that the svgadata.pmi file in the c:\os2 directory is missing. I have tried to run the svga.exe in a dos full screen with the same result as the previos paragraph. The command line options I have tried are on monitor, on init and on dos, all with the same result. The svga status produces a list of screen sizes and resolutions. Any help guidance would be much appreciated. Robert Eddy
Re: Setting up the ET6000 device drivers
Author: John Youells
Date: Thu, 10 Apr 1997 00:00
Date: Thu, 10 Apr 1997 00:00
53 lines
2852 bytes
2852 bytes
robeddy@dove.mtx.net.au (Robert Eddy) wrote: > >I am running Warp V4 without any fixpacks and am trying to get a new ET6000 >video card to behave. The card is installed in the machine (P120, 32M RAM and >with Samsung 15GLe monitor) and operates correctly with Win95 and Win 3.1 >which reside on other partitions. > >My problem has evolved this way: > >I installed the ET6000 and drivers for Win95 & Win3.1 on their respective >partitions without problems using the drivers which came with the ET6000. > <<SNIP>> >Any help guidance would be much appreciated. > > >Robert Eddy > > If you are running a 4mb ET6000 card the following may help: I have been struggling with the various releases of Tseng ET6000 drivers for quite awhile. Many folks have had problems with 'crash on first mouse move' and corrupted icons and fonts in seamless winos2. After a lot of testing, and looking through the binaries of the seamless driver, I originally found the setting in system.ini [Tseng] section of hardwarebitblt=0 to get rid of some of the black icons and changing the fonts in the boot section to 8514fon.fon got rid of the font corruption. But eventually I gave up and installled another card. Well the other day I picked up a 2 meg Jaton ET6000 card to test instead of my 4mb Dynamite 128/video. I installed the Jaton 2mb and the 12/19/96 Tseng drivers and they worked fine! No seamless winos2 problems. Hmmmm, installed the Hercules board without regenerating svgadata.pmi and it worked fine as well. Regenerated svgadata.pmi for 4 mb's and curruption all over again! Put the 2mb svgadata.pmi back and even the Hercules was fine in seamless (with the default of hardwarebitblt=1). Well after talking again to Hercules this afternoon it seems that Tseng just found the same thing. Seems that they must have tested mostly with 2mb boards!! Seems that even though the svgadata.pmi handles the 4mb info the seamless winos2 driver does not. In a previous post I enclosed a svgadata.pmi file that was generated for an Optiquest v775, for the benefit of those who don't have access to a 2mb et6000 board. I hope this helps. BTW, with Sysbench 0.91c I turn 78 graphics marks with a K5PR-166. John Youells LifeStream Computing
Re: Setting up the ET6000 device drivers
Author: Kevin Zimmerman
Date: Fri, 11 Apr 1997 00:00
Date: Fri, 11 Apr 1997 00:00
30 lines
1819 bytes
1819 bytes
Robert Eddy wrote: > The problem I now face is that I get to the part in the installation > > program where the "svga.exe on monitor" is run and everything stops. > The screen goes blank and the DOS Full Screen window appears with the > > sign on message from svga.exe saying its version 2.51 and the program > apparently hung. Recovery via ctrl-esc and then closing the program is > the only way to recover. > > It appears to me that the problem may be that the svgadata.pmi file in > the c:\os2 directory is missing. I have tried to run the svga.exe in a > dos full screen with the same result as the previos paragraph. The > command line options I have tried are on monitor, on init and on > dos, all with the same result. The svga status produces a list of > > screen sizes and resolutions. Make sure you type: C:\OS2\SVGA.EXE on monitor then type AUTO when the screen reappears. After that is all done open a DOS full screen and go to your OS2 directory and type SVGA on DOS. This creates a svgadata.dos. Delete the svgadata.pmi and rename it svgadata.pmi. Also make sure you use IBM's Warp 4 drivers from: http://service.software.ibm.com/os2ddpak/html/index.htm Kevin zoob@mwci.net
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads