OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Setup & Installation => Topic started by: Charles Hudson on May 11, 2021, 12:54:50 pm

Title: How to reverse a failed driver installation
Post by: Charles Hudson on May 11, 2021, 12:54:50 pm
I need to reverse a failed video driver installation which has resulted in a general protection fault (trap: 000d, errc: 0000, exception SINGLEQ$) that prevents the machine from booting.  I am completely inexperienced ("noob") with OS/2 but I installed V3 on a '586 VLB machine and had a running system until I tried to install a video driver for the Genoa Windows VGA 24 VLB video card.  I found the driver on the Hobie(?) site and got halfway through the install before it failed.  The install mentioned saving the original files but didn't say what they were named or where they were saved.

I have a boxed set of OS/2 2.1 with disks and a manual.  With the help of these materials I am able to at least get the machine to a command prompt and access the C: drive, but from there I am unsure how to proceed, not knowing enough about the file structure or command syntax to search for most recently modified files.

Suggestions welcome, thanks.
-CH-
Title: Re: How to reverse a failed driver installation
Post by: Dariusz Piatkowski on May 11, 2021, 02:55:41 pm
Hey Charles,

Probably the quickest way to get back to a working system is by forcing the VGA mode at boot-up.

Here is what you need to do:

1) Re-boot the machine
2) when the white rectangle pops-up in the top LEFT corner of the screen (during early boot stage) you hit ALT+F1
3) you now should be looking at a menu that has several choices, select option 'V' I think (if I remember correctly), this will force the box to book in VGA mode

Try it and let us know what happens.
Title: Re: How to reverse a failed driver installation
Post by: Charles Hudson on May 11, 2021, 05:47:26 pm
As you described:  When the white rectangle appeared in the upper left corner of the screen, pressing ALT-F1 brought up a menu of options; one of which, "V" forced the machine to reinstall VGA.  The machine has done so successfully and I now have a desktop on the display.

Thank you indeed for your assistance.

The Genoa card uses the Cirrus Logic CL-GD5426 chipset, according to the information I found, but apparently there is another software tool to identify the monitor that is on a utility disk.  As the monitor I have attached to the machine is a Viewsonic LCD I don't think I would have found it anyway.  I do have other CRTs, however.

Eventually I would like to upgrade to Warp 4.52 but I think I'll get a little more familiar with the OS first.  Thanks again for your help.

-CH-
Title: Re: How to reverse a failed driver installation
Post by: Dariusz Piatkowski on May 11, 2021, 06:48:06 pm
Here is something else you could try: head on back to Hobbes and d/l the SNAP video drivers. Here is the direct link to the ZIP file => https://hobbes.nmsu.edu/download/pub/os2/system/drivers/video/snap-os2-3.1.8.zip (https://hobbes.nmsu.edu/download/pub/os2/system/drivers/video/snap-os2-3.1.8.zip)

Given that your video chipset is an older one I'm not sure if that last public version of SNAP supports it, but the README will most likely point it out.

The benefit with these drivers is that they simply have additional capabilities to help you deal with different monitor formats, resolutions, etc.

Worst case if SNAP does not work, is that you repeat the same VGA Recovery process that you had just gone through.
Title: Re: How to reverse a failed driver installation
Post by: Lars on May 11, 2021, 09:26:27 pm
I am not sure if OS/2 2.1 supports GRADD video drivers.
I remember that OS/2 2.0 initially only supported 16-bit video drivers ! Boy, that is such a long time ago..
Title: Re: How to reverse a failed driver installation
Post by: Andreas Schnellbacher on May 11, 2021, 09:53:56 pm
| SciTech SNAP Graphics for OS/2 requires a version of OS/2 Warp 3 or
| later in order to run. More importantly, it requires at least Warp 3
| with FixPak 35, or Warp 4 with FixPak 5 installed.
Title: Re: How to reverse a failed driver installation
Post by: Martin Iturbide on May 11, 2021, 10:28:42 pm
Hi Charles. Welcome to the forum.

Can you give us a little description of the machine where OS/2 is running?
- Which version of OS/2 are you running 2.0 or Warp 3 (You can execute a "ver /r" on the command line).
- What software is the one that is critical on that OS/2 system?
- Does the computer has some special hardware that needs to be supported?

Maybe with that we can give you a better idea which driver to use and if it is possible to easily go the Warp 4.52 or even ArcaOS if you want to acquire it.

Regards

Title: Re: How to reverse a failed driver installation
Post by: Dariusz Piatkowski on May 11, 2021, 10:42:31 pm
| SciTech SNAP Graphics for OS/2 requires a version of OS/2 Warp 3 or
| later in order to run. More importantly, it requires at least Warp 3
| with FixPak 35, or Warp 4 with FixPak 5 installed.

Right...and per Charles' original post (although the BOLD is my add), where he stated:

Quote
...I am completely inexperienced ("noob") with OS/2 but I installed V3 on a '586 VLB machine and had a running system until I tried to install a video driver for the Genoa Windows VGA 24 VLB video card...

the suggestion to deploy SNAP should provide a viable and hopefully better result.
Title: Re: How to reverse a failed driver installation
Post by: Dave Yeo on May 12, 2021, 02:32:15 am
The question is whether he has applied any fixpaks, which from the sound of it, he likely hasn't.
The other question is which driver he tried to install. This seems like the best bet, https://hobbes.nmsu.edu/download/pub/os2/system/drivers/video/CL_54xx_041.zip (https://hobbes.nmsu.edu/download/pub/os2/system/drivers/video/CL_54xx_041.zip).
Getting it to work with a wide screen monitor is questionable too, so perhaps best would be to apply the fixpak then SNAP.
Actually, reading the SNAP readme, it doesn't seem to support the  Cirrus Logic CL-GD5426 chipset, can't find it in the driver either, the oldest is the CL-GD5430. Need the PCI number to be sure.
Title: Re: How to reverse a failed driver installation
Post by: Charles Hudson on May 12, 2021, 11:26:02 am
Thank you all for your responses.

The machine is running OS/2 Warp 3 on a VESA local bus motherboard.  No fixpacks have been applied.

The video card is a Genoa Windows VGA 24 (model 8500 VL) which features a Cirrus Logic CL-GD5426 chipset.  I downloaded the driver file for this chipset from Hobbes, read the README files and tried to install the driver.  Installation of the files went well until I was asked to specify the monitor; I couldn't, and the install left me with an unstable system.

The Genoa card probably came with a supplemental or "utility" disk when packaged by the manufacturer, but if I recall correctly this card was purchased second-hand from eBay and no disk was supplied.  Furthermore, the Viewsonic display didn't exist when the card was produced, so I would have to find an analogue.

The default display parameters for the OS are VGA 640x480 256 colors.  I know the Genoa card can do better and was trying to find a better resolution and bit depth.  But, as I say, I am not very experienced with the OS and don't really know what's possible or how to achieve it.  I thank you all for your help.

-CH-
Title: Re: How to reverse a failed driver installation
Post by: Dave Yeo on May 12, 2021, 04:28:40 pm
Sounds like this card, https://stason.org/TULARC/pc/graphics-cards/E-H/GENOA-SYSTEMS-CORPORATION-XVGA-WINDOWSVGA-24-MODEL-90.html (https://stason.org/TULARC/pc/graphics-cards/E-H/GENOA-SYSTEMS-CORPORATION-XVGA-WINDOWSVGA-24-MODEL-90.html)
The problem with old video drivers is you had to specify the refresh rates, clock rates etc of your monitor, which varied, especially with older monitors which had fixed settings. Likely the documentation had a list of monitors or there is a way to create a monitor setting. Had to do similar with old XServer, where if you could find the frequencies of your monitor, you'd enter into the config file.
Without documentation, it may be hard to get the card working. One option is to find a newer card, perhaps an ATI or such, most were supported back then.
Title: Re: How to reverse a failed driver installation
Post by: Dariusz Piatkowski on May 12, 2021, 04:49:37 pm
...The default display parameters for the OS are VGA 640x480 256 colors.  I know the Genoa card can do better and was trying to find a better resolution and bit depth.  But, as I say, I am not very experienced with the OS and don't really know what's possible or how to achieve it.  I thank you all for your help.

-CH-

So I'm curious, when the WPS (Work Place Shell) comes up and you see your OS/2 Desktop, are you able to select the "OS/2 System => System Setup => Screen" object?

I have had SNAP deployed here for some years now so I am not 100% sure, but I am nearly certain that this is the standard OS/2 "screen-setup" object. If that objects exists on your machine, you should be able to open it up and select a higher resolution and colour depth. Of course these will be driven by the system's ability to recognize the display montior hardware, but it's worth a try in order to avoid getting stuck with the ancient VGA resolution.
Title: Re: How to reverse a failed driver installation
Post by: Dave Yeo on May 12, 2021, 05:02:05 pm
Hi Dariusz, before monitors supported EDID, you really did have to set things up manually for your monitor, and depending on the monitor specs you entered, the screen object would have shown the possibilities I assume. I only had a VGA monitor back in the Warp v3 days and don't remember the screen object.
Needed a Win3.1 video driver too before GRADD.
From XF86Config for example,
Code: [Select]
# Any number of monitor sections may be present

Section "Monitor"

#    Identifier  "AST svga-lr"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

#    HorizSync   30-70

#    HorizSync  30-64         # multisync
#    HorizSync  31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync  15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

#    VertRefresh 50-130

EndSection

Some video drivers such as the ATI Mach 64 would probe the monitor and try to figure it out. This blew up my original VGA monitor by over driving and breaking the fly cable, looked like a lightning storm in the back of the monitor.
Title: Re: How to reverse a failed driver installation
Post by: Charles Hudson on May 12, 2021, 05:19:23 pm
If I go to system setup the only option I have for screen resolution is 640x480x16.  If I go to selective install then for display I have several driver options including the "blitter" (recommended by the Hobbes driver) for Cirrus Logic 5426.  It may be these drivers were installed when I tried to update the display driver (and failed).  I may also have selected "generic VGA" when setting up the machine, thinking I could change it later.

If I invoke the system information tool I get an error screen.

Screen shots attached.

-CH-
Title: Re: How to reverse a failed driver installation
Post by: Dave Yeo on May 12, 2021, 05:46:34 pm
Reading the readme from the driver, I guess you could try to hunt down the DOS drivers which seem to include the monitor utility, it likely would run on OS/2's Dos session. Or there might be a generic monitor that is good enough like SuperVGA or IIRC, Warp came with a generic SuperVGA driver, which, while not accelerated, would at least give more colours and 800x600 resolution.
The driver also mentions the display.log and dspinstl.log if you want to look and perhaps remove any files that were added during the aborted driver install.
Title: Re: How to reverse a failed driver installation
Post by: Martin Iturbide on May 12, 2021, 07:11:49 pm
Hi Charles

Now I get you are using Warp 3 with no fixpacks.  Since you are back with VGA support and no trap error I guess you know need to get a decent resolution on your Warp 3 box.

I'm guessing yours is a hobbie machine and it is not an vital machine used on some industry. Otherwise it is very important to backup the full HDD image, just in case.

I would also vote to get "snap-os2-3.1.8.zip (https://hobbes.nmsu.edu/download/pub/os2/system/drivers/video/snap-os2-3.1.8.zip)" (Latest freeware) - (or even sdd7_b38.zip (https://hobbes.nmsu.edu/?detail=%2Fpub%2Fos2%2Fsystem%2Fdrivers%2Fvideo%2Fsdd7_b38.zip) - older) installed there but the "no fixpacks" in Warp 3 may be an issue.

If I don't recall it wrong the latest US Warp 3 fixpacks is Fixpack 40. ... I don't recall if FP43 was only for Warp 4 Server. I also have this quick article on how to install those IBM fixpacks from the HDD (https://www.os2world.com/wiki/index.php/Applying_Fixpaks_to_OS/2_Warp_from_a_Local_Hard_Drive_(Alternative)).

Regards



Title: Re: How to reverse a failed driver installation
Post by: Charles Hudson on May 12, 2021, 10:32:33 pm
Yes, the VLB machine is part of a collection of old iron.  The reason for using the Genoa card is because it is designed for a VESA system (has an extended slot on the motherboard) as is the DTC SCSI controller**.  I brought it out because I needed to use the PC to format a disk for use in another machine.  The OS install was performed in 2019 and the BIOS backup battery had gone flat from disuse.  Once I got the geometry set and booted to the OS I found the display "wavy".  It turned out to be a blown capacitor in the PSU; replaced PSU.

I have spent most of my working life using machines from the DR - CP/M and MS-DOS continuum.  I am fairly conversant with that topic but was curious to see what OS/2 could do.  I'm still making baby steps; I have found some resources, however, and I thank once again those who have responded.

May I ask, regarding fixpacks:  Must they be applied in order or is the latest an accumulation of all the previous issues?

-CH-

** Drive A: is 1.4MB 3.5 floppy, drive B: is 1.2 Mb 5.25 floppy, drive C: is 120 Mb Viking SCSI, drive D: is CDR.  Also on board,  ISA cards: Everex ser/par I/O, Intel 8/16 LAN card, SoundBlaster, SIIG I/O card.  VESA motherboards typically did not carry I/O ports or supporting hardware - you added your own.  As I can not invoke the system information utility, except for the drives  I have no idea whether these are recognized or configured by the OS.  Of particular interest are the serial ports.
Title: Re: How to reverse a failed driver installation
Post by: Dariusz Piatkowski on May 12, 2021, 10:45:53 pm
Hi Dariusz, before monitors supported EDID, you really did have to set things up manually for your monitor, and depending on the monitor specs you entered, the screen object would have shown the possibilities I assume. I only had a VGA monitor back in the Warp v3 days and don't remember the screen object...

Yikes...you are right...I do recall those days after all. My first OS/2 video card (which would have been OS/2 v3) was actually a Cirrus Logic shipset card...but heck, those drivers are long gone from my machine.

Charles,
Dave's suggestion is probably the best-fitting driver package you're going to find. I'd give that a shot...
Title: Re: How to reverse a failed driver installation
Post by: Dave Yeo on May 13, 2021, 01:17:44 am
Hi Charles, the fixpaks are cumulative, so just the latest is needed, though at one point IBM split the device drivers into their own fixpak and the 2nd device driver fixpak had the USB support removed, so if you want USB, you need to install the 1st and then the 2nd device driver fixpak.
You really need at least fixpak 17 for the SIQ fix and the device driver fixpak will give support for much newer hardware like Hard drives, though that is easy to add by itself
There are also fixes for other stuff such as the network stack, which can actually be used to getting networking (beyond the internet kit) working on plain OS/2 V3 or earlier.

As for your video card, you might be able to easily find a newer VLB card then you have. Even the next generation Cirrus Logic looks better.
Title: Re: How to reverse a failed driver installation
Post by: Dave Yeo on May 13, 2021, 01:23:31 am
I would also vote to get "snap-os2-3.1.8.zip (https://hobbes.nmsu.edu/download/pub/os2/system/drivers/video/snap-os2-3.1.8.zip)" (Latest freeware) - (or even sdd7_b38.zip (https://hobbes.nmsu.edu/?detail=%2Fpub%2Fos2%2Fsystem%2Fdrivers%2Fvideo%2Fsdd7_b38.zip) - older) installed there but the "no fixpacks" in Warp 3 may be an issue.

As I said, SNAP doesn't support that old card, here's what is supported,
Code: [Select]
0 1013:00D0 cirr546x.drv.Jul.26.2000.20.24.21   ; Cirrus Logic Laguna 5462
0 1013:00D4 cirr546x.drv.Jul.26.2000.20.24.21   ; Cirrus Logic Laguna 5464
0 1013:00D6 cirr546x.drv.Jul.26.2000.20.24.21   ; Cirrus Logic Laguna 5465
0 1013:00A8 cirrus.drv.Jul.11.2003.18.37.08     ; Cirrus Logic CL-GD5434
0 1013:00AC cirrus.drv.Jul.11.2003.18.37.08     ; Cirrus Logic CL-GD5436
0 1013:00A0 cirrus.drv.Jul.11.2003.18.37.08     ; Cirrus Logic CL-GD5440
0 1013:00B8 cirrus.drv.Jul.11.2003.18.37.08     ; Cirrus Logic CL-GD5446
0 1013:FF0C cirrus.drv.Aug.07.2001.17.59.27     ; Cirrus Logic CL-GD7543 LCD
0 1013:0040 cirrus.drv.Mar.10.2000.13.04.48     ; Cirrus Logic CL-GD7555 LCD
Taken from x:\os2\drivers\snap\graphics.bpd

Title: Re: How to reverse a failed driver installation
Post by: Fahrvenugen on May 22, 2021, 04:31:14 am
For Warp 3 I definitely recommend installing Fixpak 40 - it is the last officially released Fixpak for Warp 3.

If you are running the blue-spine version of  Warp 3, or if you are running the red spine but don't have the WinOS/2 sub-system installed, then it is possible to install Fixpak 43 for Warp Server 4.  Warp Server 4 was based on the Blue Spine version of the  Warp 3 code base (in other words, it came with  the WinOS/2 stuff), and while the *client* version of Warp 3's last Fixpak was Fixpak 40, the Server version received a few more fixpaks, up to Fixpak 43.

In order to be able to able to install anything above Fixpak 40 on the client OS you'll need to grab a little utility from Hobbes which will tweak the syslevel files so that the fixpak installer thinks it is installing to a version of Warp Server.  Search hobbes for:

b120.zip

and that'll do the needful.  If you go above Fixpak 40 then you'll also need to install the device driver fixpak.  It is then that they separated the device driver updates from the main fixpak to make them a separate "device driver" fixpak.  I think the latest DD fixpak that'll install on Warp 3 is Device Driver fixpak 2.

As for the Cirrus Logic card, it appears there is a device driver for that video card on Hobbes.  If you search for:

CL_54xx_041.zip

I don't have such a card so I can't really try this, but a lot of those drivers had to actually be installed with a utility called ddinstall (or maybe it was ddinstal - I can't remember and I'm not sitting at my Warp machine right now, so I'm just going by memory).  There is probably a readme in the video card zip file.

Chances are the video driver won't work on a stock install of Warp 3 with no fixpak installed.  Many of those device drivers needed at least Fixpak 17, although admittedly 17 was a very buggy fixpak - I'd just go right for FP40 and skip all the others.  FP 40 was (is) extremely stable and adds a lot to Warp 3 (including the SIQ fix, the 32 bit chkdsk for HPFS, the ability to use Win32s Version 1.25, the ability to use GRADD and Scitech Display Doctor, an early version of Open32, and more).  I still have a few Warp 3 - FP 40 machines running that I maintain and they are rock solid stable.