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 - Roderick Klein

Pages: [1] 2 3 ... 31
Hardware / Re: Hardware Compatibility Wishlist for 2022
« on: January 22, 2022, 04:27:14 pm »
I have another one: Support up to 4 GB RAM for the system with addition of Physical Address Extension.

Maybe the os/4 team can comment.
My technicall estimate to get this in current os/2 kernel.
Well not going happen...


OS/4 uses PSE-36 for quite a long. But for ram drive only.
To use PSE-36 or PAE for general propose memory   requires   totally  rewrite kernel component "Pager" and all PDD at least.  So "Well not going happen... (ะก)".

Thanks for the technical clarification.


Hardware / Re: Hardware Compatibility Wishlist for 2022
« on: January 22, 2022, 03:22:54 pm »
I have another one: Support up to 4 GB RAM for the system with addition of Physical Address Extension.

Discussed in this forum before plenty of times. Maybe the os/4 team can comment.
My technicall estimate to get this in current os/2 kernel.
Well not going happen...

Putting in this support will require big big changes.


Hardware / Re: Hardware Compatibility Wishlist for 2022
« on: January 21, 2022, 06:50:17 pm »
- 2.5 Gigabit Ethernet PCI Express.

Best I can tell this requires no special support. If somebody has such a chipset is not supported open a ticket at Arca Noae if you have such a chipset,

"These drivers exist and are included in the MultiMac distribution because someone needed them and requested a driver.  MultiMac drivers are typically very easy to create. If you have a specific network adapter that is not supported by an existing MultiMac driver and you need a driver for it, please open a ticket and request a new driver. Make sure you attach a TestLog log file to your ticket."


Hardware / Re: Hardware Compatibility Wishlist for 2022
« on: January 21, 2022, 06:46:47 pm »

Just trying to organize the ideas without any order or weights we have:

- Audio and Camera support for a Videoconference tool.
- Bluetooth support for Keyboard and Mouse.
- GPT support for large disks.
- 2.5 Gigabit Ethernet PCI Express.
- Intel Wifi support.
- Dual Screen Support
   - Intel HD dual screen support. (To mirror screen or extend screen)
   - Easier Hot plug to projectors. (To mirror screen or extend screen)

I think I would like to add to the list:
- Hibernate support for PCs  / Laptops.


That large hard disc support with GPT is already working. See the readme file of the AHCI driver of Arca Noae.
Added support for 48/64 bit LBA operations.

But it seems you need the GPT filter driver for this to work which is included in ArcaOS 5.1.0. beta.


Hardware / Re: Hardware Compatibility Wishlist for 2022
« on: January 21, 2022, 03:50:37 pm »
Browser development is going to pickup again. We have collect SOME funding, but we need more.

Roderick Klein

Hardware / Re: Hardware Compatibility Wishlist for 2022
« on: January 21, 2022, 01:15:10 am »
I also think WiFi would be a high priority. Both WiFi and dual screen have been mentioned by Arca Noae on their roadmap.

To this would add GPT support for large disks.


ArcaOS 5.1.0. already has large GPT disc support in conjunction UEFI support.
But this is of course not yet released.  See the Warpstock Europe video's for more information.


Internet / Re: The new browser / QT5
« on: January 20, 2022, 10:08:55 pm »
Hi Rene

I also have no information or plans about the release of the new Qt5 Browser. I know that Bitwise works keeps updating libraries and news on his website, but I don't know any timeline.


Things have grinded to halt duo to difference circumstances.  I am working on an update to be published in the month January to tell everybody what the status is.


Setup & Installation / Re: OS2DASD hangs after 1st stage installation
« on: January 14, 2022, 08:54:27 pm »
Taje out the ACPI.PSD from yoru config.sys or add /VW switch and see if this fixes hanhg.
The hang is most likely occuring with the witch over from the MINIFSD code to the IFS code.


Hardware / Re: New ArcaOS USB driver and Floppy drive
« on: January 10, 2022, 10:17:44 pm »
I ran into a problem. USB drive of floppy disks does not reread the floppy disk when accessing the disk. In the 16-bit version, everything works successfully.
What can be done to solve the problem?

Are you using the AN USB drivers or the Lars his USB drivers ?


Storage / Re: JFS - Trap 0003 - anyone?
« on: January 09, 2022, 12:28:29 am »

I figured I would inquire here first before logging a ticket for the AN folks on this JFS issue.

So the other day I had a weird situation: my nightly RSYNC job LOG needed to be "rotated" having grown to some 32M in size over the past couple of years. I decided to manually split it up into calendar year LOGs. I most likely had the file open in my editor while at the same time attempted to execute a CLI copy of that big file.


JFS died with TRAP 0003...meltdown!

Following a power re-boot JFS did a check disk and uber quickly flashed some messages up on the screen about lost directories. The chkdsk forced an automated re-boot and a 2nd chkdsk run. At the end of what felt like the longest 5 mins ever I got back to my MAINT partition to discover that my 'lost+found' directory now had some 17k files. Clearly chkdsk found some directory problems and moved a boat-load of files into the 'lost+found' directory. Yikes!

Anywyas, I was aware that this is probably the worst JFS situation when directories are mangled. Now luckily for me I had a nightly backup (RSYNC...LOL), so I was able to recover just fine. The mangled directories turned out to be my Firefox and Thunderbird cache, thus the massive listing of files.

Now that I'm up and running again and spending a little time researching this I discovered the following description of a TRAP 0003:

TRAP 0003 - BREAKPOINT. This is a special instruction (INT 3) used in "debugging" software, which was left in the code either accidentally or by design. Contact software support.

Further on, the following is also available:

[G:\]help 1933

SYS1933: A program caused a breakpoint error.  The program was ended.


EXPLANATION: A program started an INT 3 instruction when it was not
being run by a debugger.

ACTION: Correct the program and retry the command.

I found this extremely interesting given that in this latest version of JFS AN announced a successful quashing of a JFS bug when operations on a file LARGER than the JFS CACHE would potentially trap.

In my case I am running a large 1G cache, so I do not think this to be the issue...however as I experiment with various MIN and MAX buffer settings I may have potentially ran into a problem there. Hard to tell and NO I have not tried to replicate this issue!!! ha....

Take a look at the attached TRAP screen...what do you guys make of it?


Is this under ArcaOS ? I ask this as I am not familiar with older OS/2 versions. But if you are running ArcaOS are you also dealing
the latest ACPI, JFS and OS2KRNL from Arca Noae ? They contain different fixes that can resolve a TRAP 3.
But I am not certain.


Web applications / Re: The MicroWeb DOS web browser
« on: January 06, 2022, 11:27:31 pm »

I got this reply from Mike, the mTCP author.

I wrote mTCP to bring networking to my old computers.  Think about machines like the original IBM PC (1981), the PCjr (1983) and the PC AT.  mTCP works fine in an emulated machine, and possible even in a virtual DOS machine.  But it needs a packet driver which has direct and exclusive access to a network card.  And it provides its own TCP/IP implementation.

If you want to use the networking available in a DOS VDM the programs need to be rewritten to use those networking APIs directly.  I don't think that is a huge problem, but some quick Googling did not give me any information on what that network API even looks like.  Do you have any links on what the network API for DOS VDMs looks like?

Do you know by chance the API that the DOS VDM uses for networking?


Hmmm I do not know if this is even documented somewhere with some examples how to write code to acess this interface.
VDOSTCP.SYS is most likely the driver providing this interface...
IBM TCP/IP for DOS 2.1.1 Programmer's Toolkit

The very few times I used the WIN/OS2 TCP/IP stack it crashed my system most cases. So I am not 100% certain how stable it this VDM TCP/IP support.


Web applications / Re: The MicroWeb DOS web browser
« on: January 05, 2022, 01:16:12 am »

Today I read about this text web browser for DOS.

It works on DOS full screen on my ArcaOS 5.0.7 VM, but I have no network under DOS.

Can someone please give me some tip or pointer on how to set the network on VDM DOS?


As Ibrahim already explained TCP/IP support is working in the DOS VDM.
I think the issue is that the web browser is expecting a different interface then can be found in the DOS VDM.

Network setup
MicroWeb uses Michael Brutman's mTCP networking library for the network stack. You will need a DOS packet driver relevant to your network interface. You can read more about configuring DOS networking here.

I do not know how you can get the Brutman mTCP interface to work.
Very quickly reading I think its expects an Ethernet driver under DOS to talk to. But I only read this extremely quickly this link.


Web applications / Re: QT5 simplebrowser
« on: November 20, 2021, 07:36:56 pm »
Seems I did have one system where it did seem to make a difference, but maybe I'm misremembering. In this case it may well have been a coincidence where the reboot fixed things.
I'm not sure if IBM finished the high memory support and a theory is that too high a VAL value on some hardware might intrude into kernel memory space. This system for example has 3,241 MB's memory accessible to the system, which doesn't leave much room above 3072 VAL value for the JFS cache etc. I'd assume a video card could eat up more memory at the top end.

Few people know that this virtualaddresslimit was already build into Warpserver advanced. It was only later this code was moved into the _W4 kernel. In my book the code is finished. IBM introduced high memory for stuff such as DB2, which could use this high memory.
Now does the code contain bugs, possible. But we need to have proper debug data for that.


Web applications / Re: QT5 simplebrowser
« on: November 19, 2021, 08:22:44 pm »
Here, after the last big update to netlabs.rel, my system became very unstable.

Try to rollback nss* and nspr. I have installed almost all packs from  netlabs.rel  -  everything quite stable.

It's weird, I updated nss* and nspr4 quite a while back on my netlabs-exp partition. The browser started just vanishing, no trp, no popuplog entries and attempting to trace it down was futile. Now on that partition, after updating libc etc, the browser frequently crashes in various places, usually related to committing memory in various places.
This partition using netlabs-rel became very unstable after the big update, fixed partially by lowering my VIRTUALADDRESSLIMIT from 3072 to 2560 but still so frustrating that I formatted it and restored a backup, back to stability.
Seems that a combination of the libc and NSPR4 and NSS updates led to the extreme instability. Previously I had tried the newer NSPR4 and NSS on this partition and had the vanishing browser thing so rolled back.
I've also tested by rebuilding the browser with the updated NSPR4 and NSS and things were stable.
So now I'm testing rebuilding NSPR4 and NSS and just replaced the NSPR4 DLL's as a test. So far things seem stable.
I continue testing and updating the other files. Anyone who wants to play along, here's my newly built NSPR4 DLL's, they're Pentium 4 with -mtune=generic raw builds, so still have the debugging stuff included, could be lxlited, my build didn't create dbg files for these. Unlock and replace the ones in @unixroot/usr/lib and reboot to use them. Haven't tried marking them for high memory yet. If you want to revert, use ANPM or YUM to reinstall.
Be good if someone testing the Otter beta tests too.

I just have one question has there ever been any hard evidence for fiddeling with the virtual address limit really increases or decreases applications stability ? As in something of debug trace to point that this *actually* trace. To be honest I have a hard time feeling this contributes to making applications stable or more stable.

I can see where increasing the amount of virtual memory you can have an application leak memory longer. But reducing virtual address limit ?


Pages: [1] 2 3 ... 31