July 24, 2008 01:27am pdt

1. fridom 2,000
1. kevo04 2,000
3. allyourb... 1,200
4. giltjr 1,000
4. Makaveli213 1,000
4. rpggamer... 1,000
4. flyingCo... 1,000
8. jdera 800
9. Greenclock 750
10. JoseParrot 150

1. dannykon 20,161
2. Otta 16,797
3. juxtapose 5,644
4. itsmeand... 5,100
5. b_vishwajit 4,300
6. dotENG 3,000
7. Stonewal 2,960
8. twh270 2,400
9. arjen 2,380
10. fridom 2,000
10. badbearo... 2,000
10. simpswr 2,000
10. kevo04 2,000
10. choekstr 2,000
10. jimmymcp02 2,000
10. viverss 2,000
10. strung 2,000

08.23.2000 at 08:29PM PDT, ID: 11090085

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

6.6

How to check display driver required thru command line?

Zone: OS / 2 Operating System

Tags: driver

I have a problem of installing SGVA driver to all my wkst remotely. As the wkst comes with different display driver chipset (eg Cirrus Logig, s3 etc...), is it possible to check the chipset required thru OS/2 without going to the bios or opening the casing. I hope this can be done thru some REXX function call.

Thanks.

Start your free trial to view this solution

Question Stats

Zone: OS

Question Asked By: joekwchen

Solution Provided By: Stanley_S

Participating Experts: 2

Solution Grade: A

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
Automotive
New Net Users
New Users

Software
Digital Music
Gaming World
Home Security

Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Displays / Monitors
Handhelds / PDAs
Components
Peripherals
Laptops/Notebooks

Servers
Misc
Apple
Embedded Hardware
Networking Hardware

Storage
Desktops
New Users

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMware
Misc
Web Development

OS
CYGWIN
Voice Recognition
Virtualization
Message Queue
Quality Assurance
Security
Firewalls

MultiMedia Applications
Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals
Devices

Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
Web Computing
WebApplications
IDS
Vulnerabilities
Email Clients
File Sharing

Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Consulting
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMware

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel
Automation

Algorithms
Game
Signal Processing
Project Management
Open Source
Database

Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Web Services

Images
Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration

WebApplications
Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Web Computing

Broadband
Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Lounge
Business Travel
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles
Automotive

Community Support

Suggestions
New to EE
New Topics
CleanUp

Announcements
General
Feedback

Input
EE Bugs

08.25.2000 at 12:47PM PDT, ID: 4074269

Stanley_S:

If you install OS/2 first and then upgrade the drivers, then this is valid. There is an OS/2 program similar to the old Norton System Info that detects most of the chipsets, but then OS/2 would have to be installed to run it. sysinfo015.zip on Hobbes http://hobbes.nmsu.edu/pub/os2/util/system/sysinfo015.zip

A simpler thing to do would be to use non-chip specific drivers. (simpler CID install script, etc.) IBM has two of them on the OS/2 device driver web pages, IBM's GRADD drivers or SciTech's display drivers. Both of these support most of the major chipsets without any intervention from you.

It has been indicated that SciTech has been chosen as the future direction for drivers. SciTech's has the simpler install, is CID capable and detects the chipset on its own.

The web site the official version can be obtained from is: http://service.software.ibm.com/os2ddpak/html/02C85B26B9A029488725689000530FE4.html

Beta versions are at: http://www.scitechsoft.com/down_sdd_os2.html this will support newer chips such as the Matrox G400, etc.

Here is a cut from the documents in the official release 7 version (the beta is version 13, I believe):

List of all supported chips (Updated 06/08/2000):

This is a complete list of the various graphics cards that this version of SciTech Display Doctor supports. Please note that this list refers to the actual chips being used, not a board level implementation. Thus you
will not see any products from Hercules or STB on the list, but their products are supported because they use S3, Cirrus, Tseng, etc. chips. Also, any card
with less than 512KB of memory cannot be supported by SciTech Display Doctor.

3DLabs Permedia, Permedia 2, Permedia 2V, Permedia 3
3dfx Voodoo Banshee, Voodoo3
ARK 1000PV, 2000PV, 2000MT, 2000MI (Quadro64), 2000MI+ (Quadro64)
ATI Mach64 GX, Mach64 CX, Mach64 CT, Mach64 VT, 3D Rage, Mach64 VTB
ATI 3D Rage II, 3D Rage II+, Mach64 VT4, 3D Rage IIC, 3D Rage Pro
ATI 3D Rage LT Pro, Rage Mobility, Rage XL, Rage 128, Rage 128 Pro
Alliance ProMotion 6422, ProMotion AT24, ProMotion AT3D
Chips & Technologies 65550, 65554, 65555, 69000
Cirrus Logic CL-GD5434, CL-GD5440, CL-GD5436, CL-GD5446
Cirrus Logic CL-GD7555 LCD, Laguna 5462, Laguna 5464, Laguna 5465
Cyrix MediaGX
InteGraphics CyberPro 2000, CyberPro 2010
Intel i740, i740 PCI
Macronix 86250, 86251
Matrox MGA Millennium, MGA Millennium II, MGA Mystique
Matrox MGA Mystique 220, MGA-G100, MGA-G200, MGA-G400
NVIDIA RIVA-128, RIVA-128ZX, RIVA-TNT, RIVA-TNT2, RIVA-TNT2 M64
NVIDIA RIVA-TNT2 Vanta, RIVA-TNT2 Ultra, GeForce 256, GeForce DDR
NVIDIA Quadro
NeoMagic MagicGraph 128, MagicGraph 128XD, MagicGraph 256AV
Number Nine Imagine 128, Imagine 128 II, Imagine 128 II VRAM
Number Nine Imagine 128 II DRAM, Ticket 2 Ride WRAM
Number Nine Ticket 2 Ride SGRAM, Ticket 2 Ride IV
OAK Spitfire 64107, Spitfire 64111, Eon 64017, Eon 64217, Warp 5
Philips 9710
Rendition Verite V1000, Verite V2200
S3 Trio32, Trio64, Trio64V+, Trio64UV+, Trio64V2/DX, Vision 864
S3 Vision 964, Vision 868, Vision 968, Virge, Virge/DX/GX, Virge/VX
S3 Virge/GX2, Virge/MX, Trio3D, Trio3D/2X, Savage3D, Savage4
SiS 6202, 6205, 6215, 5597/5598, 6326, 5595/530, 5595/620
Sigma Designs RealMagic 64 GX
Trident TGUI9440, TGUI9440-R2, TGUI9680, ProVidia 9682
Trident Cyber9385 LCD, ProVidia 9685, 3DImage 975, Cyber9397 LCD
Trident 3DImage 985, Blade 3D
Tseng Labs ET4000/W32p, ET6000, ET6100
Weitek P9000, P9100
VESA VBE 1.2, VBE 2.0, VBE 3.0

The following is the list of all supported Mobile or Laptop chip sets.

The following is a complete list of the various laptop graphics chipsets this version of SciTech Display Doctor supports. Please note that this list refers to the actual chips being used, not the laptop brand or model itself. Thus you will not see any products from Gateway or Dell on the list, but their products are supported because they use NeoMagic, ATI, Cirrus etc. chips.

ATI 3D Rage LT Pro, Rage Mobility
Chips & Technologies 65550, 65554, 65555, 69000
Cirrus Logic CL-GD7555 LCD
NeoMagic MagicGraph 128, MagicGraph 128XD, MagicGraph 256AV
S3 Virge/MX
Trident Cyber9385 LCD, Cyber9397 LCD
VESA VBE 1.2, VBE 2.0, VBE 3.0

Supported Resolutions

Supported resolutions and color depths are adapter dependent and will vary depending on the amount of graphics memory and the adapter implementation.

Accepted Solution

08.27.2000 at 12:46AM PDT, ID: 4085468

Otta:

I agree!

Access:

http://service.software.ibm.com/os2ddpak/html/displayc/ibmcorpo/

and click on "IBM Special Edition SciTech suite of drivers".

That's what I use ("build 99") with my Matrox Millenium G200 video-card.

08.27.2000 at 05:57PM PDT, ID: 4090951

joekwchen:

First of all thanks to u guys.

I've actually tested installing the SciTech driver. After I installed it, I have the SYS3175 - DOSCALL1.DLL error when bootup. After checking thru, it seems that my Comms Manager/2 (CM/2) can't start properly. After I uninstall it, the problem goes away.

I've also tried reinstalling the fixpak after installing the display driver but it won't help either.

I'm running OS/2 v3 Fixpak 39. I've dismantled the PC and I've found a Intel 810 chipset there. I've tried download somthing call INTGRADD driver from intel web site but after installing it, the screen freeze after reboot.

Any more suggestions?

Thanks.

08.27.2000 at 09:47PM PDT, ID: 4092418

Otta:

Reboot, and press ALT+F1 when you see the "white-box" and the text 'OS/2' at top-left of the screen.

Select 'load VGA driver', and let it boot.

Now, try CM/2. If it works, install the IBM/SciTech driver, and try CM/2 again.

08.27.2000 at 10:40PM PDT, ID: 4092642

joekwchen:

Otta,

tested the above, still fails! what should I do?

Thanks.

08.28.2000 at 12:14AM PDT, ID: 4093408

Stanley_S:

Which version of CM/2? 1.11? Or are you using the CM/2 that comes in the eNetwork package?

DOSCALL1.DLL in some of the fixpacks have been a problem, but I don't know the Warp 3 packages well enough to comment if the one in FP39 is a problem.

Warp 3 is totally unsuppported without a contract by IBM, I couldn't even give you a email of someone to ask if this is a known problem, but I would suggest contacting the SciTech people with the error information.

You didn't mention which version of the SciTech you loaded/tested.

08.28.2000 at 01:29AM PDT, ID: 4094049

joekwchen:

Stanley,

I've downloaded sddse702.exe. I've tried to install using the SDD option during setup.

The CM/2 version i use is 1.11 CSD 6150.

Meanwhile, I try to contact Scitech and see. The version I downloaded, is it an evaluation copy or free to OS/2 Warp 3 users.

08.28.2000 at 06:25AM PDT, ID: 4096490

Stanley_S:

Sddse702 is a 'old' version. Free to all OS/2 3 & 4 users with the minimum fixpack required.

Download the newer one at the SciTech website. It is hard to find on the page, so use the LINKS option in the browser to locate it. It is still free since it is a beta. You do have to register.

From the documents do you have any of these situations?

=========================================
FUNCTIONAL RESTRICTIONS
_______________________

Current known restrictions include the following:

1) SciTech Display Doctor/se** generally only supports PCI and AGP graphics
adapters, and does not support ISA, VLB and Microchannel. The only
exception is for laptop chipsets that are on a non-PCI local bus, or
early motherboard integrated chipsets such as the early MediaGX family.

2) The SciTech Display Doctor/se** GRADD drivers, do *NOT* require a
chipset specific SVGADATA.PMI file, but instead have a single PMI file
implemented via a DLL. Hence when running SDDGRADD do *NOT* use the
SVGA ON INIT command to create an SVGADATA.PMI file.

3) The IBM GENGRADD drivers, require VESA** compliant video BIOS (Version
1.2 or greater) or an appropriate SVGADATA.PMI file to provide generic
unaccelerated VESA support. For older non-VESA adapters with SVGA PM
driver support from IBM, GENGRADD may often be used as an alternative
SVGA driver set by following the GRADD Graphics BBS drivers SETUP
installation command with the command "SVGA ON INIT" from an OS/2 or
DOS Full Screen prompt to create an SVGADATA.PMI file, before rebooting
to use the GENGRADD drivers.

4) If you enable the HPFS386 Local Security feature, you must make sure that:
- The x:\os2\drivers\nucleus directory is always readable.
- The x:\os2\drivers\nucleus\config subtree has read/write/create
access for all users.
Where "x:" is your OS/2 boot drive. Failure to do this will cause your
system to not boot properly unless the administrator is logged on.

5) Any adapter with less than 512KB of memory cannot be supported by SciTech Display Doctor.

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

Also there are some useful utilities in the package listed in the very end of the README. TXT file. They include a program to determine the graphics chip type and if it is supported, and another tool to remove some of the default functions from the driver if they are incompatible. Again, I would download the newer version to make sure that any bugs are corrected.

08.28.2000 at 10:03PM PDT, ID: 4108413

joekwchen:

Hi Stanley,
Basically I've fulfilled all the requirement. From the newsgroup posted, it seems that my problem is due to CM/2 3270 emulator unable to start. They mentioned something called Advanced Video I/O (AVIO) that CM/2 use to display. What is the changes from the GRADD technology?

No answer was provided but however it says something about JR08266 which is not found at ibm web site.

08.29.2000 at 08:01AM PDT, ID: 4115915

Stanley_S:

It may be possible to upgrade to the eNetwork Communication package which can migrate your older CM/2 configuration to a newer release. eNetwork has an AS/400 and 3270 package and separate packages for both.

Have you tried the SciTech version of the Gradd drivers?

08.29.2000 at 05:48PM PDT, ID: 4122483

joekwchen:

Thanks Stanley, I have tried it. It's still the same. I think it is because CM/2 does not work well with this type of GRADD technology.

I think I shall open another question more specific to the CM/2 and GRADD problem.

08.29.2000 at 05:49PM PDT, ID: 4122488

joekwchen:

Comment accepted as answer

20080236-EE-VQP-29