OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Setup & Installation => Topic started by: Mo on August 31, 2020, 09:44:05 pm

Title: ArcaOS 5.0.6 released
Post by: Mo on August 31, 2020, 09:44:05 pm
https://www.arcanoae.com/arcaos-5-0-6-now-available/ (https://www.arcanoae.com/arcaos-5-0-6-now-available/)

Unfortunately Changelog not Readme on the website reflect changes in 5.0.6 yet
Title: Re: ArcaOS 5.0.6 released
Post by: Martin Iturbide on September 01, 2020, 02:51:26 am
It is now available.
https://www.arcanoae.com/wp-content/uploads/wiki/ArcaOS-changes.txt

Summary of changes 5.0.6

- Updated JFS to 1.9.8.
- Updated brlaser CUPS print driver.
- Updated NetDrive Samba plugin to 3.7.1.
- Updated VirtualBox Additions to 6.1.12; improved packaging.
- Updated FAT32 to 5.0.3.
- Updated ACPI to 3.23.14.
- Updated eCo Runtime Base & Win to 20200525.
- Updated NAPS help (minor).
- Updated Panorama to 1.16.
- Updated TestLog to 3.32.
- Updated PRINTMAN to 0.8.6 (proper filtering of non-current-codepage PPD strings).
- Updated CUPSWIZ to 1.20 (proper filtering of non-current-codepage PPD strings).
- Fixed repeating "EPSON" string in generated printer driver list.
- (Installer) Various minor layout fixes.
- (Installer) Moved Media Folder creation to phase 2 to avoid potential hang in phase 3.
Title: Re: ArcaOS 5.0.6 released
Post by: Sean Casey on September 01, 2020, 05:08:44 pm
I just updated and now ANPM is broken.   When starting, ANPM prompts for my AN repository subscription IDs and PWs, and then throws a Python Error "The Python interpreter terminated with error code 123.   I also tried to rebuild the RPM database and received the popup error VX-REXX "DosConnectNPipe". 

Title: Re: ArcaOS 5.0.6 released
Post by: Eugene Tucker on September 01, 2020, 06:37:59 pm
I have had no issues with updating on my desktop. Next we will see how my laptop goes.
Title: Re: ArcaOS 5.0.6 released
Post by: Andreas Schnellbacher on September 01, 2020, 06:43:04 pm
I just updated and now ANPM is broken.
Scan the log files in %LOGFILES%\* (default is ?:\var\log\*) for entries with the word 'error'.
Title: Re: ArcaOS 5.0.6 released
Post by: Andreas Schnellbacher on September 01, 2020, 06:51:59 pm
The USB stick creation went without problems and the BIOS can boot from it.

I've tried to update one of my test/service partitions that had ArcaOS 5.0.1 with the USB stick. Phase 1 continued, but after reboot from harddisk for phase 2, it can't find the USB stick anymore. The USB drivers doesn't seem to work. I've tried to load USBD.SYS as first USB entry (it was appended before the new USBHID.SYS), but that didn't help. Even with disabling startup.cmd, the RediscoverRPM object in the drives folder won't add the drive R:

Will try to burn a DVD later.

Edit: Corrected ArcaOS version number.
Title: Re: ArcaOS 5.0.6 released
Post by: roberto on September 01, 2020, 07:58:02 pm
In my case after updating from DVD, everything is correct, in principle.
The problem was with the config.sys, The update modified this:
REM RUN = C: \ OS2 \ ACPIDAEMON.EXE
RUN = C: \ OS2 \ ACPIDAEMON.EXE

I changed it back to REM and the sound was perfect again, because it could be heard in sections.
Along with other improvements.
With the ANPM without problems.
The manjonng better.
saludos
Title: Re: ArcaOS 5.0.6 released
Post by: Sandra Asja Eickel on September 01, 2020, 08:47:45 pm
I've tried to update one of my test/service partitions that had ArcaOS 5.[0.]1 with the USB stick. Phase 1 continued, but after reboot from harddisk for phase 2, it can't find the USB stick anymore. The USB drivers doesn't seem to work.

If that stick was connected to XHCI (USB 3.x) and your old installation had not upgraded the USB drivers to support XHCI before, then this result is (sadly) expected.

Quote
Due to the current installer design, it is necessary to install USB 12.06 and XHCI prior to the update for systems requiring XHCI.

This is not only an ugly documentation failure, but might have even worse consequences:
When this happened to me by upgrading from 5.0.1 to 5.0.5 from a stick, it killed FireFox & Co., so you can't then even download the missing drivers to continue installation ...

I'll have to invest a little more time into my ticket https://mantis.arcanoae.com/view.php?id=2914 (https://mantis.arcanoae.com/view.php?id=2914) ...

Greetings,
Sandra-Asja
Title: Re: ArcaOS 5.0.6 released
Post by: Andreas Schnellbacher on September 01, 2020, 11:18:28 pm
If that stick was connected to XHCI (USB 3.x)
Sure, but no, it wasn't. I've used the (black) USB 2 ports. And the XHCI driver was installed, what makes me wonder for an update, because it was communicated otherwise. After that, I tried a new installation on that partition. Same problem: USB stick can't be found in phase 2. Now I really have to burn a DVD.

BTW: That was my first installation from USB. I've already tried it when that feature was new, but copying the .iso file had failed. I was too busy with other stuff to try it again. Additionally, I had hardware problems with an almost new Kingston SSD.
Title: Re: ArcaOS 5.0.6 released
Post by: Pete on September 02, 2020, 12:07:26 am
Hi All

5.0.6 cannot be installed from USB here. Same problem as 5.0.5 - USB stick goes "missing" after the boot "Menu for own choices", not sure if this is what Andreas calls "phase 2" but I would say that it craps out before phase 1.

5.0.4 installed from USB without any problems so changes to either USB code or installer code have caused this backwards step.

Looking through the 5.0.6 changelog I see no reason to bother with installing 5.0.6 from dvd, I'll just update my 5.0.5 installation with the few odd drivers that have been updated.


Regards

Pete

Title: Re: ArcaOS 5.0.6 released
Post by: Doug Bissett on September 02, 2020, 01:52:16 am
Quote
I've tried to update one of my test/service partitions that had ArcaOS 5.1 with the USB stick. Phase 1 continued, but after reboot from harddisk for phase 2, it can't find the USB stick anymore.

That can happen, IF you were using a pre=release version of the USB drivers (where did you get ArcaOS 5.1, it hasn't been released to the testers, yet). Due to the way the drivers are versioned, release 12.7 GA is a lower (or equal) level than USB 12.7 test versions. so they don't get updated.

I have done updates from all of the previous ArcaOS GA versions (with no updates to them), and every one of them added the new USB stuff, INCLUDING the XHCD driver. I could not install from USB3, because USB3 is on an add on card, that BIOS does not know about. Trying to update with the pre-release USB 12.7 driver failed to update the driver, and did not install the XHCD driver. FAT32, and ACPI may also fail, under the same conditions. Just install the updated versions from the DVD, and don't mess with test versions, if you don't want this type of problem.

Quote
The problem was with the config.sys, The update modified this:
REM RUN = C: \ OS2 \ ACPIDAEMON.EXE
RUN = C: \ OS2 \ ACPIDAEMON.EXE

That is NOT a problem, It is supposed to happen that way.  The end result is supposed to be a "new" install of ArcaOS, with most (if not all) of your software still installed.

If ACPI is causing trouble, and you can create a test case that demonstrates the problem, open an incident, and get it fixed. If this is a newer system, it probably doesn't run properly without ACPI. If it is an older system, it may have flaws in the ACPI support (well, new systems can also have flaws in ACPI support).

Quote
If that stick was connected to XHCI (USB 3.x) and your old installation had not upgraded the USB drivers to support XHCI before, then this result is (sadly) expected.

This was true for ArcaOS 5.0.5. It is not true fro ArcaOS 5.0.6. See above.

Quote
Sure, but no, it wasn't. I've used the (black) USB 2 ports. And the XHCI driver was installed, what makes me wonder for an update, because it was communicated otherwise. After that, I tried a new installation on that partition. Same problem: USB stick can't be found in phase 2. Now I really have to burn a DVD.

USB 2 ports are not always connected to an EHCD controller. They can be connected to an XHCD controller. If the USB stack didn't get updated, for some reason (see above), it is likely that the XHCD controller didn't have the driver.

Quote
Looking through the 5.0.6 changelog I see no reason to bother with installing 5.0.6 from dvd, I'll just update my 5.0.5 installation with the few odd drivers that have been updated.

That is probably the easy way. Hopefully, Arca Noae will get their versioning in order, so this doesn't happen again. You should be able to just re-run the update (start from the first boot), to be sure that you get all of it. If you have test versions installed, they may need to be updated manually.

Quote
5.0.6 cannot be installed from USB here. Same problem as 5.0.5 - USB stick goes "missing" after the boot "Menu for own choices", not sure if this is what Andreas calls "phase 2" but I would say that it craps out before phase 1.

That is the pre-boot phase. Phase 1 is after it starts to write to the disk drive. If phase 1 works, the USB drivers are working, and the problem is likely that you are using some USB drivers, that are, incorrectly, recognized as being current, when they are not.

If you don't get to the pre-boot menus, it is likely that the BIOS is not reading the USB stick properly. Do you see the dots, as it loads MEMDISK? That is all done by BIOS. Check for a setting that is called something like FAST START, in the USB section. If you read the details, that can either turn off all devices, or it can set it to use only mouse and keyboard. The USB stick will not work, although I would expect the initial menu to also go missing.

BIOS handling of USB boot is absolutely ridiculous. It seems that every machine (even the same brand) does it differently, and user settings (not necessarily made by the user) will affect what happens. I can't even begin to tell you what the settings should be, unless you have a machine identical to one of mine. Look carefully, and read what the settings do. Even then, it may not make any sense. You also cannot boot from an add on card, that the BIOS doesn't know about. If all of that doesn't help, open an incident.
Title: Re: ArcaOS 5.0.6 released
Post by: Pete on September 02, 2020, 03:08:09 am
Hi Doug

The problem with 5.0.5 and 5.0.6 USB installation here is that after completing the pre-boot phase "Menu for own choices" is that the USB eject and/or (re)attach fail.

This can be illustrated by simply attaching a usb flash drive to a booted ArcaOS system with USB 12.06 or 12.07 installed. With the flash drive still attached (do not eject) reboot the system. Is the flash drive accessible? - the answer here is that it is not in the drives folder and Refresh Removable Media does not cause the flash drive to be displayed.

If I then physically remove the flash drive then reinsert it the flash drive becomes accessible and is displayed in the Drives folder.

That suggests the problem is the result of usb coding changes after USB12.01 - supplied with 5.0.4 and worked fine for usb install, also passes the above reboot without ejecting test.


Regards

Pete
Title: Re: ArcaOS 5.0.6 released
Post by: Doug Bissett on September 02, 2020, 04:58:43 am
Quote
This can be illustrated by simply attaching a usb flash drive to a booted ArcaOS system with USB 12.06 or 12.07 installed. With the flash drive still attached (do not eject) reboot the system. Is the flash drive accessible? - the answer here is that it is not in the drives folder and Refresh Removable Media does not cause the flash drive to be displayed.

Interesting. That was supposed to be fixed (and, I know of a few cases where it was fixed). I guess you should report the problem (again), but be sure that you have the USB stack, from the ArcaOS 5.0.6 DVD installed. No point in wasting resources to find out that it didn't get updated. I know why it doesn't get updated, when you are using a test version before updating, but it should be okay otherwise. There MAY be a problem with the 12.7 version from the subscription (before the one that was just released). Be sure you aren't using that one.

You may find an option, in BIOS, something about "hand off" (from BIOS control, to driver control). If it exists, it might cause such a problem (I am guessing, because none of my machines have that, or I never noticed it).

If you haven't done it, install E:\CID\SERVER\ARCAPKG\USB.WPI (where E: is the DVD drive, or ISOFS drive), and see if it still has the problem. If it asks, replace everything, and, of course, re-boot before trying it.
Title: Re: ArcaOS 5.0.6 released
Post by: ivan on September 02, 2020, 10:19:35 am
On my ASUS Ryzen  test system the first reboot hangs on USBUHCD.SYS so it looks as if I will have to restore the boot partition from a disk image again.
Title: Re: ArcaOS 5.0.6 released
Post by: Andreas Schnellbacher on September 02, 2020, 12:54:55 pm
That can happen, IF you were using a pre=release version of the USB drivers (where did you get ArcaOS 5.1, it hasn't been released to the testers, yet).
OK, sorry for the confusion. It's 5.0.1 GA. (I had named it here 5.1 many years ago, because it followed 5.0.) I was wrong. I've fixed it in my text above.

But it happened also with a full reinstall. So, the USB drivers in the ISO (12.07) most likely doesn't work here.

USB 2 ports are not always connected to an EHCD controller. They can be connected to an XHCD controller.
Sure, but they worked already before the USB 3 drivers.
Title: Re: ArcaOS 5.0.6 released
Post by: ivan on September 02, 2020, 02:05:21 pm
OK, I got round the USBUHCI.SYS hang problem by telling the setup page just to install the XHCD driver and plugging the keyboard and trackball into the USB 3 sockets.

Now, apart from setting all the folders to 'as placed' and to 'not maintain sort order' I have to work out how to get back the standard OS/2 sloped icons - with all due respect to whoever designed the flat icons I don't like them, too much like the uninspired win 10 offering, sorry.
Title: Re: ArcaOS 5.0.6 released
Post by: Andreas Schnellbacher on September 02, 2020, 02:39:44 pm
Now, apart from setting all the folders to 'as placed' and to 'not maintain sort order' I have to work out how to get back the standard OS/2 sloped icons - with all due respect to whoever designed the flat icons I don't like them, too much like the uninspired win 10 offering, sorry.
Interesting. I feared that. Disabling always sort and changing the icon theme belong to the first things I configure. Unfortunately, there exists no way to get the icon positions back as before, IIRC. Maybe it helps to disable that before opening the first folder with the WPS. Instead of the blue folder icons, I use the standard eCS theme. It works for all, except for the Network folder. I remember that the ITheme format has changed and adapted it, but didn't try more.
Title: Re: ArcaOS 5.0.6 released
Post by: Sean Casey on September 02, 2020, 05:15:01 pm
I just updated and now ANPM is broken.   When starting, ANPM prompts for my AN repository subscription IDs and PWs, and then throws a Python Error "The Python interpreter terminated with error code 123.   I also tried to rebuild the RPM database and received the popup error VX-REXX "DosConnectNPipe".

This issue was due to the installation process adding the following to my config.sys:

    SET COMSPEC=C:\OS2\CMD.EXE /K C:\OS2\NUMON.EXE

This was derived from my existing entry:

    SET OS2_SHELL=C:\OS2\CMD.EXE /K C:\OS2\NUMON.EXE

Changing to the following resolved my error:

    SET COMSPEC=C:\OS2\CMD.EXE
Title: Re: ArcaOS 5.0.6 released
Post by: Doug Bissett on September 02, 2020, 05:43:39 pm
Quote
Sure, but they worked already before the USB 3 drivers.

The internal connections can change, when the X controller is added to the mix. Perhaps that is where the problem lies.

Quote
OK, I got round the USBUHCI.SYS hang problem by telling the setup page just to install the XHCD driver and plugging the keyboard and trackball into the USB 3 sockets.

This also points to a problem with the internal routing. Report the problem.

Quote
This issue was due to the installation process adding the following to my config.sys:

    SET COMSPEC=C:\OS2\CMD.EXE /K C:\OS2\NUMON.EXE

This was derived from my existing entry:

    SET OS2_SHELL=C:\OS2\CMD.EXE /K C:\OS2\NUMON.EXE

Changing to the following resolved my error:

    SET COMSPEC=C:\OS2\CMD.EXE

What is NUMON.EXE? There is no such thing in ArcaOS. Report the problem, but they can't support everything that a user adds to the mix. Was that line in your original CONFIG.SYS? Very few lines actually get changed, if the install completed successfully.
Title: Re: ArcaOS 5.0.6 released
Post by: Sean Casey on September 02, 2020, 06:58:21 pm
What is NUMON.EXE? There is no such thing in ArcaOS. Report the problem, but they can't support everything that a user adds to the mix. Was that line in your original CONFIG.SYS?

This was in my config.sys when I upgraded from 5.0.4 to 5.0.5, but it only became an issue upgrading from 5.0.5 to 5.0.6. Numlock2 is licensed by Mensys and is not distributed by Arca Noae; it turns on numlock.
Title: Re: ArcaOS 5.0.6 released
Post by: Pete on September 02, 2020, 07:16:28 pm
Hi Sean

Probably easier to use the Desktop -> Properties -> Startup page -> "Enable Numlock at Startup" option.


Regards

Pete


Title: Re: ArcaOS 5.0.6 released
Post by: Sean Casey on September 02, 2020, 08:00:21 pm
Hi Pete,

That looks like a winner, thank you!   Removing numlock2.
Title: Re: ArcaOS 5.0.6 released
Post by: Andreas Schnellbacher on September 02, 2020, 09:06:44 pm
Quote
Sure, but they worked already before the USB 3 drivers.

The internal connections can change, when the X controller is added to the mix. Perhaps that is where the problem lies.

Doug, interesting. It was already added for phase 1 by the CSM and didn't work with the config.sys on the boot drive for phase 2. BTW: I've tried 2 ports before writing. The second try was with a one beneath the PS/2 ports, which is usually connected to USB 2 chips, if any.

With Lars' Hardware Manager and then (gues it was Dmitry's) Hardware Explorer in tree view it shouldn't be a problem to confirm that. I wish I had found a way to make at least the XWP objects visible after the phase 1 of the update. Maybe I should better have used usbtree for that.
Title: Re: ArcaOS 5.0.6 released
Post by: Andreas Schnellbacher on September 02, 2020, 09:44:05 pm
Doug, do you know, if the order of the USB drivers still matters with 12.07? In the config.sys of my new-install try I have:

Code: [Select]
BASEDEV=USBD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBHID.SYS
BASEDEV=USBMSD.ADD /REMOVABLES:8 /FLOPPIES:0

In the config.sys of the update I had (before I moved USBD.SYS above):

Code: [Select]
BASEDEV=USBOHCD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBEHCD.SYS

...

BASEDEV=USBD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBXHCD.SYS

and probably below:

Code: [Select]
BASEDEV=USBHID.SYS
BASEDEV=USBMSD.ADD /REMOVABLES:8 /FLOPPIES:0

Again: Both don't recognize the USB stick in phase 2.

(I guess I have to report it to David. Before that, I have to try if it can be reproduced.)
Title: Re: ArcaOS 5.0.6 released
Post by: Doug Bissett on September 03, 2020, 05:47:29 am
Quote
With Lars' Hardware Manager and then (gues it was Dmitry's) Hardware Explorer in tree view it shouldn't be a problem to confirm that. I wish I had found a way to make at least the XWP objects visible after the phase 1 of the update. Maybe I should better have used usbtree for that.

The USB drivers should detect whatever happens, but there are many possibilities, and the drivers are still quite new, so they may not detect everything that they should detect. I have looked at what Hardware Explorer tells me, but I am not sure that it really tells the whole story. Usbtree is useful too, but may not tell the whole story either.

Quote
Doug, do you know, if the order of the USB drivers still matters with 12.07? In the config.sys of my new-install try I have:

I know that USBD.SYS should (must) be first, followed by the X, E, O and U drivers (not necessarily in that order). Then USBHID.SYS. I don't think the rest matter, as long as they follow. Before v12.1, they need to be X, E, O, U, followed by USBD.SYS and USBHID.SYS, then the rest. I think Lars fixed his drivers so it doesn't matter what the load order is, but that is a different, unsupported (by Arca Noae), driver set. My Logical Config.Sys Sort program (LCSS) at HOBBES does it slightly different from what the "official" USB installer does, but it always works, for me (and others). Of course, if there is a problem in the driver, that isn't likely to help.

Quote
(I guess I have to report it to David. Before that, I have to try if it can be reproduced.)

Try what Pete suggested, a few posts back. That would seem to be pretty close to what happens with the installer. It may be that the driver is  looking, before the stick is attached by the hardware, and that could be caused if the drivers are at the end of CONFIG.SYS (although that is probably not the case). I believe the installer runs "LVM.EXE /RediscoverPRM" from STARTUP.CMD, which could be getting there too early, so it doesn't "see" the device.

An interesting test, would be to go to System Management, at the end of phase 1, and add "sleep 2" to the beginning of STARTUP.CMD, then continue to phase 2. The bottom line is, that if the drivers work in phase 1, they should work in phase 2. It is a totally different story, if you can't get to the pre-boot menus, before the initial OS/2 boot, that is all done by BIOS. Phase 1 happens after you start the boot from MEMDISK, and that loads the drivers from MEMDISK, in the order that the pre-boot menus set up. Phase 2 uses a slightly modified version of your own CONFIG.SYS, from the hard disk. If there is something odd in there, it may not work quite right. The installer manages the USB lines (and a few other things), but most of it is left as it was found.
Title: Re: ArcaOS 5.0.6 released
Post by: Andreas Schnellbacher on September 03, 2020, 10:07:13 am
I know that USBD.SYS should (must) be first,
That's also what I remembered. It was below the others and above the newly added X type. After moving USBD.SYS above, I had the same problem with phase 2.

Yes, Lars has fixed his drivers to accept any order.

I believe the installer runs "LVM.EXE /RediscoverPRM" from STARTUP.CMD,
Yes. I've used the program object in the drives folder, but that didn't help either.

add "sleep 2" to the beginning of STARTUP.CMD, then continue to phase 2.
No, that won't help. I had renamed STARTUP.CMD from another partition to avoid automatic execution. In phase 2 the desktop booted and I executed STARTUP.CMD manually, but with the same message.

Now I remember that there was a message that AiRBoot doesn't work anymore and that it needs to be manually reinstalled first. But AiRBoot had worked. At phase 2 it boots to the CSM to let it boot from harddisk, which boots the correct partition. After these tries, AiRBoot still works normally.

Phase 2 uses a slightly modified version of your own CONFIG.SYS, from the hard disk. If
there is something odd in there, it may not work quite right.
Yes, the order of USBD.SYS, as I wrote. It's all very similar to eCS, where I was more involved.
Title: Re: ArcaOS 5.0.6 released
Post by: Doug Bissett on September 03, 2020, 05:41:13 pm
Quote
Yes, the order of USBD.SYS, as I wrote. It's all very similar to eCS, where I was more involved.

Okay, it is probably a bug in the driver. That needs to be reported, with supporting documentation (see the "Best practices" wiki).

ArcaOS has very little in common with eCS. ArcaOS is a completely new implementation, from the ground up, and the USB 12.x drivers are completely new. Very few, if any, parts of eCS are included, and what looks to be the same thing, has been completely re-written.

The USB drivers have proven to be very problematic, because nobody follows the rules, and other operating systems have gone along with that, because the biggest of them all makes their drivers work with devices that are way out of spec. That means that OS/2 must follow suit, but there is very little, if any, documentation about what gets changed to make those devices work. Even different BIOS implementations work differently, with the same hardware, and BIOS settings can also change the way it works. David just hasn't found all of those possible differences, yet.
Title: Re: ArcaOS 5.0.6 released
Post by: Rick Smith on September 03, 2020, 10:37:04 pm
Greetings,

I am relatively new to Arca, I have downloaded the update iso do I have to reinstall or is there an upgrade path? If there are upgrade instructions could you point me that way?

Rick
Title: Re: ArcaOS 5.0.6 released
Post by: Andreas Schnellbacher on September 03, 2020, 11:18:45 pm
You can update all versions since ArcaOS 5.0 to 5.0.6. The updater is included since 5.0.4.

Upgrading between major version of ArcaOS is planned.

Migrating from eCS or OS/2 W4.x is planned.

See here (https://www.arcanoae.com/wiki/arcaos/updating-from-a-prior-release/).

Maybe also interesting: Changelog (https://www.arcanoae.com/wp-content/uploads/wiki/ArcaOS-changes.txt), ArcaOS (https://www.arcanoae.com/wiki/arcaos/), ArcaOS Roadmap (https://www.arcanoae.com/roadmaps/arcaos/)
Title: Re: ArcaOS 5.0.6 released
Post by: ivan on September 04, 2020, 01:05:11 am
OK, having got the base system up and running and most of the icons changed over to OS/2 ones I started loading my usual set of programs that I use.

First problem, when I went to compare how this version ran against my 5.0.2 version on my work computer - I tried to start BS_Info but it passed out with the opening screen just flashing on before vanishing although it did leave some information in popuplog.os2 saying that the problem was with doscall1.dll.

I'm now wondering if I should just download all the updates and revert to an older version 5.0.2 or 5.0.3 that I know works.

Title: Re: ArcaOS 5.0.6 released
Post by: Dave Yeo on September 04, 2020, 03:52:25 am
Seems to run fine here, though it took a while to look at all the syslevels. Doscall1.dll hasn't changed . What is the error?
Title: Re: ArcaOS 5.0.6 released
Post by: ivan on September 04, 2020, 10:36:43 am
Popuplog entry.

09-03-2020  17:34:30  SYS3171  PID 003e  TID 0001  Slot 0078
E:\BS-INFO-2.2\BS_INFO.EXE
c0000005
1ffe01f4
P1=00000008  P2=000001cc  P3=XXXXXXXX  P4=XXXXXXXX 
EAX=00000000  EBX=0000edec  ECX=00000006  EDX=00000020
ESI=0039ee30  EDI=0039eeea 
DS=0053  DSACC=d0f3  DSLIM=7fffffff 
ES=0053  ESACC=d0f3  ESLIM=7fffffff 
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=fff7:000001f4  CSACC=00df  CSLIM=0000e4ff
SS:ESP=01ce:0039ede0  SSACC=00d3  SSLIM=0000efff
EBP=0039ee18  FLG=00010282

DOSCALL1.DLL 0004:000001f4

It is the same for the other 3 entries.
Title: Re: ArcaOS 5.0.6 released
Post by: Rolf on September 04, 2020, 01:14:29 pm
Try it with v2.3 beta:

http://www.bausys.ch/files/bs_info_2_3_beta.wpi

You can start the program with the parameter -debug.
A file BS_info.err is then created.

You can send them to me:

roga23@bausys.ch

Rolf
Title: Re: ArcaOS 5.0.6 released
Post by: ivan on September 04, 2020, 02:47:27 pm
Hi Rolf,

Thanks for that, it works without problems except for those I cause by not having some programs where you expect them (example, most tools go in the 'tools' dir while a few go in the 'apps' dir on the boot partition home to emttools, pmdll, tcpconfig, usbcfg and a few others.

BTW, now we have a working USB 3 driver maybe you need to update the USB section to show the XHCD  info.

Do you still need the debug info now it works? 
Title: Re: ArcaOS 5.0.6 released
Post by: Rolf on September 04, 2020, 06:14:03 pm
Hi Ivan

Excellent !

Yes, please send me the debug information.

Thank you for your tips.
I always try to improve it.
Title: Re: ArcaOS 5.0.6 released
Post by: roberto on September 05, 2020, 04:42:34 pm
Hi Rolf
I have tried your new version of BS_info, and it fails me quite a bit,
 only the third or fourth attempt works well for me, and if I am executing the seamonkey is better.
 When it works it shows me information in all the sections, less in the VIDEO.
 I wanted to ask you, how do you calculate the percentage of virtual available memory, line 3 photo?

I see that a very similar result can be reached with very different settings.
I understand that 2907 = 160 + 268 + 2240 + 242 - 3 small differences?
In my case I cannot exceed 3054mb in the config.sys that tells me as accessible physical memory,
 the mem / v.
I understand that the system will be more stable the more it will be done at 100%? , it is right?
Saludos