Recent Posts

Pages: [1] 2 3 ... 10
Applications / Re: Desktop Enhancement for WPS
« Last post by Remy on Today at 11:39:15 am »
I tried to download the given file but my anti viral tool detected a virus inside.
You never got a false alarm before?

It should be save to run the executable (and the resource DLLs) on OS/2.

I'll check again using online virustotal
Programming / Re: Alternatives to compiling Rust in Firefox port OS/2
« Last post by OS4User on Today at 11:21:27 am »
@os4user I'm not disagreeing with you, but if we don't convert to omf, how do we debug on OS/2?

I am not familiar with this matter and have no idea why object files are needed for debugging.
Hi All,

I still think that emxomfld could be stripped down by not converting and bypassing the weak linker to call wl.exe. This may also result in needing the minimum changes to GCC.

I'm still thinking about how best to handle it. We may still WANT to convert to OMF in some cases in order to use the 'classic' debuggers.

Of course, switching to ELF may make gdb easier to compile/work.

Just thinking out load, I was considering introducing -Zelf to tell GCC to invoke as_elf.exe rather than as.exe - that also opens up the use of -Zelf -Zomf to use ELF initially, but convert to OMF at link time (if we have a suitable ELF -> OMF converter that makes the exercise worthwhile).

I'll probably hack something together short term and make sure that 'stuff' works, then think about how best to support a.out, elf & OMF object formats in a more flexible manner...

Thinking some more.... I think I'll fork emxomfld.c and create an emxelfld.c which will do the following:
- use wlink by default
- use noautocnv by default to ensure we don't try and convert elf to OMF

This should make it easy to add -Zelf to gcc which would use emxelfld.exe as the linker

The bit I haven't worked out yet is how to tell gcc to use as_elf.exe not as.exe

It may be that the gcc elf needs to be a completely separate install to gcc aout/omf
Applications / Re: Desktop Enhancement for WPS
« Last post by Andreas Schnellbacher on Today at 01:55:07 am »
I tried to download the given file but my anti viral tool detected a virus inside.
You never got a false alarm before?

It should be save to run the executable (and the resource DLLs) on OS/2.
Setup & Installation / Re: How to reverse a failed driver installation
« Last post by Dave Yeo on Today at 01:23:31 am »
I would also vote to get "" (Latest freeware) - (or even - 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

Setup & Installation / Re: How to reverse a failed driver installation
« Last post by Dave Yeo on Today at 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.
@Ibrahim, the VT isn't necessary, just nice to have. As for 3D graphics, I wonder if it needs host video driver support or can be brute forced.

@Martin, yes, I don't really see much issue with using the OS4 kernel, but Lewis seems fairly worried about upsetting IBM so I'll err on the cautious side. As Ibrahim sayss, things should work on the stock kernel, even ones not distributed by Arca Noae, though reboots will be needed more often to recover memory.
With low-end Windows 9x 3d gaming being a goal wouldn't it be feasible, easier even, to just bypass VT all together? Without VT, I find that I can properly use Linux, Windows XP and to a limited "down-tuned" extent even 7 with no major performance losses on Virtualbox with the stock kernel. Keep in mind, it's not like this is going to be the next VBox so I doubt that degree of performance is even necessary.

Besides (putting technical legality aside as a whole can of worms), as good a platform as the OS4 Kernel can be, I personally feel it would be better to have it running on our stock kernel for the sake of stability and to an extent, ease-of-use.
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... 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.

Dave's suggestion is probably the best-fitting driver package you're going to find. I'd give that a shot...
Setup & Installation / Re: How to reverse a failed driver installation
« Last 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?


** 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.
Pages: [1] 2 3 ... 10