Solved

Matrox Impressions and Fullscreen Win-OS/2

Posted on 1997-04-30
10
350 Views
Last Modified: 2013-12-27
I just got Warp 4 after running the beta since it came out
and also purchased a Matrox Impressions VLB/2mb.

The problem is, is that I can't load a fullscreen Win-OS/2
session because it can't load matrox's 'smga16.drv'.

I've checked through my win.ini and system.ini files
everything looks okay.  The only thing may be is that it
doesn't list the resolution the screen should be at;
1024x768.

Any suggestions?
0
Comment
Question by:jonpaul
  • 5
  • 4
10 Comments
 

Expert Comment

by:john_n
Comment Utility
What are your symptoms?

When you try to start the full screen session . . .

Does the screen go black or do you get a corrupted screen?

Does the machine lock up?

Do you get any error messages?

Do you get returned to the OS/2 desktop?

One of my clients has a video card that uses mga drivers.  I'll try to find out more.
0
 

Author Comment

by:jonpaul
Comment Utility
Basically what happens is that the windows sessions is starting
to load, ie; c:\Loading...Please wait.

then get a short flash (error message; ERROR LOADING SMGA16.DRV)

and then I'm wisked back to the OS/2 desktop...

I get no lock up whatsoever.  Just unable to load a fullscreen

windows session...

thanks
jon-paul leclair
jon_paul_leclair@bigfoot.com
0
 

Expert Comment

by:john_n
Comment Utility
Sorry I didn't think of this question before, but . . .
Did you get the Matrox card before or after Warp 4?
If before, was it working with Warp 3?
If after, did you load the latest driver from OS/2 or from Matrox?  I think you'll have to get the OS/2 drivers for this to work.
They are located at http://www.matrox.com/mgaweb/drivers/ftp_other.htm, just click on the OS2 link.

Good Luck
0
 

Author Comment

by:jonpaul
Comment Utility
I have all the current drivers from Matrox.

I basically installed as I installed v4...

I've emailed Matrox on this but I haven't heard anything yet on
this...


0
 

Expert Comment

by:john_n
Comment Utility
I hope you don't mind my shots in the dark, but after looking at your original message again, it appears as if the 'ERROR LOADING SMGA16.DRV' statement might be in the AUTOEXEC.BAT file.  The machine I have with MGA (smga8.drv) drivers has a set statement in the autoexec.bat with the following:
SET MGA=C:\CPQ\OS2
Check to see if this may be required and set it to the path where the drivers exist.
Again, it's a shot in the dark, but probably can't hurt.
Good luck.
0
Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

 

Author Comment

by:jonpaul
Comment Utility
Okay...I have that setting: SET MGA=C:\MGA\OS2

Still nothing...I mean it's not a huge deal since the windows

programs I need run fine in there own sessions but sometime you

just want to load a fullcreen session to run your Windows stuff.

I've tried contacting Matrox twice now but no reply!

I'm wondering if the error is happening because of no resolution

settings in the SYSTEM.INI. eg; WIDTHxHIGHT=1024x768

here is the contents of my system.ini:
--------------------------------------
[boot]
useos2shield=1
os2shield=winsheld.exe
shell=progman.exe
mouse.drv=mouse.drv
network.drv=
language.dll=langeng.dll
comm.drv=comm.drv
keyboard.drv=keyboard.drv
system.drv=atmsys.drv
;386grabber=vga.3gr
;286grabber=vgacolor.2gr
drivers=mmsystem.dll
WAVDMAPPS=
atm.system.drv=system.drv
display.drv=MATROX SMGA16
sdisplay.drv=smga16.drv
fonts.fon=vgasys.fon
fixedfon.fon=vgafix.fon
oemfonts.fon=vgaoem.fon
os2gdi.exe=GDI.EXE
os2user.exe=user.exe

[keyboard]
subtype=
type=4
keyboard.dll=kbdus.dll
oemansi.bin=

[boot.description]
keyboard.typ=Enhanced 101 or 102 key US and Non US keyboards
mouse.drv=Microsoft, or IBM PS/2
network.drv=No Network Installed
language.dll=English (American)
system.drv=MS-DOS System
codepage=437
woafont.fon=English (437)
aspect=100,96,96
fdisplay.drv=Matrox SMGA16
sdisplay.drv=smga16.drv

[386Enh]
mouse=*vmd
network=*dosnet,*vnetbios
ebios=*ebios
woafont=dosapp.fon
display=*vddvga
EGA80WOA.FON=EGA80WOA.FON
EGA40WOA.FON=EGA40WOA.FON
CGA80WOA.FON=CGA80WOA.FON
CGA40WOA.FON=CGA40WOA.FON
keyboard=*vkd
device=vtdapi.386
device=*vpicd
device=*vtd
device=*reboot
device=*vdmad
device=*vsd
device=*v86mmgr
device=*pageswap
device=*dosmgr
device=*vmpoll
device=*wshell
device=*BLOCKDEV
device=*PAGEFILE
device=*vfd
device=*parity
device=*biosxlat
device=*vcd
device=*vmcpd
device=*combuff
device=*cdpscsi
local=CON
FileSysChange=off
PagingFile=D:\WIN386.SWP
MaxPagingFileSize=20480

device=vsbpd.386
[standard]

[NonWindowsApp]
localtsrs=dosedit,ced

[mci]
WaveAudio=mciwave.drv 4
Sequencer=mciseq.drv
CDAudio=mcicda.drv

[drivers]
timer=timer.drv
midimapper=midimap.drv
MIDI=sbpfm.drv
AUX=sbpaux.drv
Wave=sbpsnd.drv
MIDI1=sbpsnd.drv

[timer.drv]
TIMERMax386Res=10
TIMERMax286Res=10

[MGA.DRV]
PixelTOUCH=OFF
Interlace=OFF
3D=OFF


[sndblst.drv]
port=220
Int=5
DmaChannel=1
HDmaChannel=1
MidiPort=388

----------------------------------------
thanks for your help...
Jon-Paul LeClair
jon_paul_leclair@bigfoot.com
0
 

Expert Comment

by:john_n
Comment Utility
According to my OS2 Warp Unleashed book, page 542 discussing the WIN-OS/2 Display Driver,
"WIN-OS/2 determines which display driver to use based on entries in the SYSTEM.INI file.  ... The entries that specify the driver names are:

Driver                                 Entry
_______________________________________________
Application                            [boot]
Full-screen WIN-OS/2 display driver    fdisplay=
WIN-OS/2 Window display driver         sdisplay=

Your system.ini file has the following:
fdisplay.drv=MATROX SMGA16
sdisplay.drv=smga16.drv

If what the book says is true, I think you may need to have a filename in place of the 'MATROX SMGA16'.

Further examples in the book indicate filenames with the following convention (this example is for xga drivers)
    XGA.DRV for full screen
    SXGA.DRV for seamless sessions

See if you have a MGA16.DRV file and try putting that filename
in place of the MATROX SMGA16 in your system.ini file.

You may also need to put the same .drv filename in the statement that starts
    display=MATROX SMGA16

Let me know how that works.  Be sure to backup your .ini files before any big changes.

Good Luck
John
0
 

Expert Comment

by:john_n
Comment Utility
My comment was reformatted, section that says

Driver                                  Entry
_______________________________________________
Application                             [boot]
Full-screen WIN-OS/2 display driver     fdisplay=
WIN-OS/2 Window display driver          sdisplay=

should have two columns of information, I've put in the table again with an underscore '_' to separate the information.

Driver__________________________________Entry
---------------------------------------------------
Application_____________________________[boot]
Full-screen WIN-OS/2 display driver_____fdisplay=
WIN-OS/2 Window display driver__________sdisplay=

Good luck.

0
 

Accepted Solution

by:
jlouvau earned 100 total points
Comment Utility
Two possibilites:

1) You said it was a VL card - If the card's RAM is mapped to AC000, that could easily be the root of your troubles. The Imression boards tend to do really flakey things to full-screen sessions when mapped there (ISA and VL only).

2) Is the card's RAM mapped to D8000-DBFFF? If so, the WIN driver won't load unless you change your Win-OS/2 settings/properties:

Set MEM_EXCLUDE_REGIONS to D8000-DBFFF to keep Win-OS/2 from stomping on the memory area the driver wants to use.

3) Just in case: You *DID* run MGAMON.EXE (it creates MGA.INF) didn't you?

0
 

Author Comment

by:jonpaul
Comment Utility
Good ideas...and i realize that those things are potential
problems...but i have NO documentation on the DIP switches for
this card!

This is not a huge thing since i can run all the windows
programs i need to in their own seamless sessions...

I do have another problem which I will post as new...
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Suggested Solutions

Many people tend to confuse the function of a virus with the one of adware, this misunderstanding of the basic of what each software is and how it operates causes users and organizations to take the wrong security measures that would protect them ag…
I use more than 1 computer in my office for various reasons. Multiple keyboards and mice take up more than just extra space, they make working a little more complicated. Using one mouse and keyboard for all of my computers makes life easier. This co…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
You have products, that come in variants and want to set different prices for them? Watch this micro tutorial that describes how to configure prices for Magento super attributes. Assigning simple products to configurable: We assigned simple products…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now