Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Andi B.

Pages: 1 2 [3] 4 5 ... 34
Just did a 
Code: [Select]
zip -rS9 m:\* -x delete\* 2>error.logfrom O:\... and backed up my running M: partition. As usual it works. error.log is empty. I've my swapper.dat on another partition. Have to try with symlinks (-y) sometimes.

Maybe you should remove q (-ryS) or add 2>error.log to see what's the problem.

Backing up running system - if you restore then the restored system will have not the latest os2.ini and os2sys.ini changes but the state when the systems was booted. Usually not a big deal. But that's the main reason why it's better to back up when running from a maintenance partition/ArcaOS stick/bootable CD/DVD.

Hardware / Re: Someone tried OS/2 with 3840x2160 Display?
« on: April 17, 2020, 01:35:31 pm »
All my ArcaOS subscriptions has expired since a while so I'm not on current level. I have Panorama 1.06 or 07 or something like that which worked well for systems which are not supported by SNAP until now. I've bought more than one ArcaOS license in case someone wonders.

I'm testing on my Asus H87-Pro which offers 3 digital monitor interfaces. These 3 digital interfaces where one of the main reasons I bought this board a few years ago. At that time I planned to use 2 or 3 1920x1200 monitors digitally connected to this board. Unfortunately SNAP still does not support the Haswell integrated Intel HD4600 graphic. So I've to use Panorama with this system.

Now other possibilities than MultiMonitor setups are came to mind. With a big monitor and 3840x2160 resolution (max. on this board with 60Hz) I could replace 2 of the 24" 1920x1200 monitors. Of course this only works with DisplayPort.

As the 27" Eizo runs fine with 2560x1440 resolution I was confident 3840x2160 would work to. But then I tested my sons Samsung with 3840x2160 and that did not work. I don't know if it's a problem with Panorama or maybe this is another Samsung model with crippled/wrong EDID information like one of Dariusz Samsung. Should have checked that while testing...

Hardware / Re: Someone tried OS/2 with 3840x2160 Display?
« on: April 15, 2020, 10:28:12 am »
Now I had a chance to test a ~32" 3840x2160 monitor. Unfortunately it did not work for me. No clue if it's cause of my old Panorama. I think I use something like 1.07. Every OS/2 installation I tried came up with standard VGA 640x480 resolution without any chance to change it to another setting. Tried PanUtil without success. Guess Panorama couldn't read or interpret EDID information correctly.

Of course the same setup worked with Win in 3840x2160.

A few days ago I though I give the newest SM version a try. But it behaves not very stable on my system. Every now and then it crashes without any .trp file or popuplog.os2 entry.

Before I heavy used SeaMonkey/2.42.9esr Build-Identifikator: 20190520220003 which is much more stable. But as I now do much wiki (confluence) editing it sooner or later eats up all higher shared memory. At that time it becomes very unresponsive. So I though I try the newest version.

First thing I noticed with the new version is, it uses more of the rpm dlls and does not provide the same in it's own directory. That's good IMO. But I had to update nss... packages from netlabs exp repository. Otherwise sites which needs TLS1.2 did not work. Okay I've no big problem using the exp repository. But I can't get this version as near as stable than the older one.

I tried a new profile without much success. Although startup is now way faster cause with my standard profile I usually automatically load email and calendar too. But the new profile without any extensions did not help either.

What makes me wonder is that SM does not create .trp files anymore. The older version did.  Anyone else seeing such problems? Dave here ;-)

Hardware / Re: Someone tried OS/2 with 3840x2160 Display?
« on: April 05, 2020, 11:48:06 am »
Okay seems the probability that it works for me is high. Now found the following types -
- Acer EB490QK, 48.5", 705€, 91 DPI, DP, VGA, 3xHDMI
- iiyama X4372UHSU-B1, 42.5", 524€, 103,7 DPI, 2xDPv1.2, 2xHDMI, matte/anti-glare
- HP Z43, 42.5", 767€, 103,7 DPI, DP, mDP, HDMI, anti-glare

Advantage of the Acer is it's size. With 91 DPI our usual fonts should be very good readable even a bit bigger than on the 24" 1920x1200 with 94 DPI. And VGA. But not sure if it's really anti-glare/matte.

iiyamas plus is the price.

Hardware / Re: Someone tried OS/2 with 3840x2160 Display?
« on: April 04, 2020, 06:01:00 pm »
I don't think SNAP supports more than 1920x1200 for 16x10 aspect ration and 2048x1536 for 4:3. Maybe in VESA mode but pretty sure not with dedicated drivers. For now I think we've to stick with Panorama.

I've no clue which monitor would be a good choice. But for me it has to be one in the range of 95 - 110 DPI (24" 1920x1200 = 94 DPI, 27" 2560x1440 = 109 DPI). Standard fonts are big enough and readable in this DPI range for me. So the biggest display which may work for me is 42.5/43" with 3840x2160 (104 DPI). A quick search for a cheap one gave me the DELL I mentioned. I usually do not buy DELL. If I would know for sure this resolution works, I would look for Eizo, Samsung or HP and maybe Lenovo models. Usually the Eizos are to expensive for me. Number and type of interfaces are important for me too. 2 DP, 1 DVI and VGA would be nice too. The mentioned DELL does have even VGA. I don't care about HDMI or speakers or USB hubs build in or other gimmicks. But these are my preferences. I really want to know if 3840x2160 works for someone with Panorama before I buy such thing. Of course you need DisplayPort connection for that.

Hardware / Someone tried OS/2 with 3840x2160 Display?
« on: April 03, 2020, 08:25:04 pm »
Until a few months ago I though my two 24" 1920x1200 monitors give me the maximum display size I can use with OS/2. And this only when I can use a graphic card which SNAP can drive in multi-head mode. Then I bought a used Thinkpad T540p with a 2880x1620 panel. Surprisingly this resolution works with panorama. But of course the display is much to small. Notebooks are only toys for me. For real work I need more than 24".

Now I've the opportunity to lend a 27" Eizo with 2560x1440 resolution. As the motherboard on one of my systems does have a DisplayPort I tested this monitor with OS/2 and it works. Now as I know that Intel processor integrated graphic chip can drive more than 1920x1200 via DP I wonder if it would be possible to drive even bigger displays. The motherboard specification says max. resolution 4096 x 2160 @ 24 Hz / 3840 x 2160 @ 60 Hz. Now I wonder if something like the DELL P4317Q Ultra HD IPS 42,5" which can do 3840x2160 will work with this board. Anyone tested such high resolutions with any motherboard?

Networking / Re: Test build wpa_supplicant v2.7 - v2.10-devel
« on: April 03, 2020, 12:51:51 pm »
Thanks for testing and reporting. I don't see any problem here too with the new build. But I didn't test all the improvements and extensions which are made upstreams. This build does have a few more compile options enabled. But I guess these are only relevant for people who have newer drivers with more features then we do.

Games / Re: Quarantine Gaming !! - Dev/Port Help
« on: March 31, 2020, 06:54:05 pm »
Code: [Select]
No, I don't even have a GCC environment running.yum install gcc*   :-)

Networking / Re: Test build wpa_supplicant v2.7
« on: March 29, 2020, 07:35:28 pm »
If updated wpa_supplicant to the current code base in the official repository. This is not a release version but the current development state for the next official 2.10 build (v2.10-devel). I've tested this version with the latest XWLAN and also with the included QT gui frontend.

Please don't share direct links to the full filename but to the directory above.

Code: [Select]
So, I thought if we can't at this moment make the OS fit the hardware, why not make the hardware fit the OS?  Anyone tried running it on the 486FPGA?Running an OS needs more than a CPU. If the 486FPGA emulates a real 486 CPU well enough then it probably will run. But I see no benefit in using a FPGA instead the real chip. What Southbridge do you want to wire to such FPGA? Another FPGA? And which Northbridge? And which .... Do you know all the components which makes up a standard PC and will you pack all of them into one or more FPGAs? If yes, the first question would be, which 'standard' PC. The 486 systems from IBM, with our without Microchannel? Or the ones from Compaq, or?

If you want to put something into an FPGA why not emulate an ATI X300 but with two working DVI outputs as we have a multihead driver for this chip.

Programming / Re: Observing if a program uses vio calls
« on: March 07, 2020, 07:49:57 pm »
LarsonCommander does fire up a new cmd window in case | more is used with dir.

Internet / Re: Any updates on the Falcon QT browser?
« on: March 07, 2020, 07:38:17 pm »
...and it's what I'm currently hardly working on.
I think you meant "...and that's what I'm currently working on (very) hard." ;-)

Storage / Re: JFS file corruption
« on: February 21, 2020, 04:17:49 pm »
In the last 1-2 years I've bought 2 WD SSDs too. Think these are Sandisk internally as IIRC WD bought Sandisk. These WD drives are slower than my Samsung EVO 8xx drives. Unfortunately the price for Samsung SSDs is a bit high compared to WD. For my main machines where I use the SSDs a lot I still prefer Samsung EVO.

Storage / Re: JFS file corruption
« on: February 21, 2020, 12:37:22 pm »
I'm using SSDs for my systems since many years. I've even \TEMP and \TMP on SSDs and these dirs are used a lot especially when building software. But especially my older SSDs are all from Samsung which were tested at that times as being very robust. Usually I've some spare space on SSDs which is not partitioned too. So far no single failure or problem like Ian reported.

Pages: 1 2 [3] 4 5 ... 34