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 - Lars

Pages: 1 [2] 3 4 ... 85
16
Hardware / Re: The last nail in OS/2's coffin
« on: January 23, 2024, 05:18:53 pm »
If you want to delve into the details:

https://www.intel.com/content/www/us/en/developer/articles/technical/envisioning-future-simplified-architecture.html

Currently, this is only a proposal. But it gives a very good idea of what Intel thinks is no longer needed.

Its expected this will indeed be long term thing to happen. I understand the legacy bit takes up 12% of the space in CPU.
I read an article (I do not the have link handy) of one of the main AMD tech engineers and he said the proposal was every interesting.
However the engineer indicated the changes proposed are "very, very, very, very complex to make".

The other thing that this would imply is (the way I understand it) is that NO current VM would work anymore
to run legacy OS. Its the CPU that provides the virtualization support to hypervisor.

Roderick

Correct. Virtualization of OS/2 (and likewise: DOS and Windows 16-bit) will not be possible once x86-S is introduced. Only emulation will be possible (with a huge performance impact, of course).

17
Hardware / Re: The last nail in OS/2's coffin
« on: January 22, 2024, 05:24:55 pm »
Intel proposed Itanium 64 bit in 1989. It takes some time for these plans to come about. Even articles about the new 64 bit architecture from Intel mention cores that still provide X86 mixed with 64-bit only cores.

https://en.wikipedia.org/wiki/Itanium

Even if nothing happens for a while, it's worth thinking about how OS/2 runs on CPU features that matter very little to the CPU market.

The other thing that threatens OS/2 is the aging of its users. I predict that will be the actual cause of death.

With Itanium 64 bit, while moving to 64-bit, Intel wanted to push through a completely new CPU architecture with a completely different instruction set. That failed because nobody wanted to immediately rebuy all their software.

But with x86-S, Intel wants to make room on their die, kicking out all the stuff nobody needs any more (freeing space for valuable things like for example an increased cache size) and also, because the twisted x86 architecture seems to introduce more security issues then would be necessary because the x86 architecture has become too complex.
That is a completely different motivation. It is in Intel's best interest to push this through as fast as possible. And it has become fairly easy because all major OSes and their applications are 64-bit already and also already fullfil all prerequisites to make them run on x86-S.

18
Hardware / Re: The last nail in OS/2's coffin
« on: January 22, 2024, 02:28:43 pm »
If you want to delve into the details:

https://www.intel.com/content/www/us/en/developer/articles/technical/envisioning-future-simplified-architecture.html

Currently, this is only a proposal. But it gives a very good idea of what Intel thinks is no longer needed.

19
Hardware / Re: The last nail in OS/2's coffin
« on: January 22, 2024, 11:39:32 am »
Taken the fact that AMD was the driving force to intoduce 64-bit mode and Intel just following, I very much doubt that AMD would put the burden onto itself to support legacy HW concepts that no current OS needs. That would throw them behind Intel with no benefit at all. You need the die for modern stuff (AI in HW or some such, larger on-chip cache, larger SIMD registers etc.) and not for stuff that is not needed at all any more.

Intel taking that step is effectively Intel's confession that 16-bit and segmentation have no future at all.
As to the ring protection, it turned out that differentiating between "user" (Ring 3) and "system" (Ring 0) is already sufficient. For paging, these are already the only 2 "Ring Protection" levels (and they are consequently called "user" and "system").

Unfortunately, OS/2 offers use of Ring 2 (in conjunction with the IOPL flag in the EFLAGS register) to simplify I/O port access and therefore there are some applications that make use of that and would need to be rewritten to use a device driver instead. But see my statement about OS/2 device drivers ...


20
Hardware / The last nail in OS/2's coffin
« on: January 22, 2024, 12:05:09 am »
Sorry, it's in German (unfortunately it's also not free):
https://www.heise.de/select/ct/2023/26/2317912025061981023

I suppose that this has also been.picked up by other IT press articles about the new X86-S architecture.
What it basically states is that Intel will now finally remove all 16-bit support (true for real mode, protected mode and VM86 mode), all segmentation, Ring 1 and 2 of the protection rings.
That means: NO OS/2 device driver will work, NO  OS/2 1.x application will work, no application with an IOPL segment will work, no VDM will work, some parts of the kernel will cease to work.

OS/2 is going to be put to it's well deserved, permanent rest.
The current x86 will likely live on for a couple of years but there clearly is no future for OS/2, not even in a virtualization environment like Virtualbox.

21
General Discussion / Re: Hobbes Retirement
« on: January 10, 2024, 03:48:31 pm »
As a user, how do I upload files to OS2SITE ? As far as I understand I currently cannot.
If I knew, I could already start to upload my files to OS2SITE instead of still uploading them to Hobbes.

22
Programming / Re: Installing VisualAge 4 on ArcaOS 5.x
« on: January 10, 2024, 02:28:44 am »
Do the "mixed CID" installation:

1) create a file "parms.txt" with the following content assuming that:
    a) D: is your installation drive letter
    b) D: is your boot drive letter (see /B: parameter)
    c) V: is your CD-ROM drive letter
    d) adjust the main path (VACInstDir) to your liking
    e) adjust the samples path (VACSampDir) to your liking
    f) adjust the OS/2 toolkit path (VACToolDir) to your liking

/O:VAC
/SET:VACInstDrv=D:
/SET:VACSampDrv=D:
/SET:VACToolDrv=D:
/SET:VACInstDir=IBMCPP40
/SET:VACSampDir=IBMCPP40
/SET:VACToolDir=Toolkit
/SET:VACMediaPath=V:\VACPP
/R:V:\VACPP\VACPP.RSP
/S:V:\VACPP
/B:D:

Then run this from the directory where you created file "parms.txt":

clifi.exe /A:B /F:"<WP_DESKTOP>" /PARMS:parms.txt

You will get an installation object on your desktop where you can then select/deselect installation options.

Also find attached a text file that explains how to setup the help system. The help system still works with Firefox, there is no need to use Netscape. The file talks about VAC 3.6.5 but the help system is the very same for VAC 4.

23
Programming / Re: Installing VisualAge 4 on ArcaOS 5.x
« on: January 09, 2024, 03:06:27 pm »
Did you try the Netscape browser based installation ?

If yes: even if you do not want to change drive and directory information for the installation directories, you need to reenter/reselect the drive/directory information, otherwise the browser will crash.

If you go with Alex' Install object suggestion, you can at least avoid that problem altogether.

24
Applications / Re: ArcaOS 5.1 - First Impressions
« on: January 08, 2024, 01:14:11 am »
Thanks, I had also opened a ticket. Yes, it looks like the thread creation in "fdrForceRefresh" leads to the accumulation of started threads that perform the actual refresh.

The parent method of "wpRefresh" seemingly needs to have the REFRESHINPROGRESS flag not set on entry in order to actually do something so yes, you would need to "lock out" an additional refresh via another means.

25
I have never understood why Russia never managed to make more out of their abilities and possibilities.

They have capable sports guys, they have capable and talented artists (some of the world best pianists among them), they have smart people (I have a big maths book written by a Russian mathematician in the 1950's or so), they have resources/raw materials and they have money.
But the result is just plain meagre.

26
Copy from the commandline. That works ok.
VBOXSF.IFS (from Virtualbox) seemingly does not properly handle the FS_COPY command for remote drives (because that's how shared folders are represented to the OS/2 guest).
It would be nice if you raised a bug with Virtualbox.

27
Applications / Re: ArcaOS 5.1 - First Impressions
« on: January 07, 2024, 01:09:30 pm »
Yes, you are right. I opened a ticket there. Maybe Rich will have a look. I would try my suggestion myself but I have never built XWorkplace myself.

28
Applications / Re: ArcaOS 5.1 - First Impressions
« on: January 07, 2024, 05:59:17 am »
It's a folder with 362 Icon files.

Thanks for sharing that little detail. I was able to duplicate this easily once I knew what you were talking about (though I suspect they were actually PNG icons, not "icons"). Blame the MM classes...

It's .ICO files of class WPIcon. That is not a subclass of any MM class. Also, I can open the /OS2 folder, hit F5 multiple times with the same effect.
The only thing that helps is to close the folder which will immediately terminate all those refresh threads.
Xworkplace's XFolder replaces the wpPopulate method. If at all, I would suspect this to be the culprit.

As a test, I have reduced to one core only. In that case, the second PMShell instance will not "accumulate" multiple threads. So, this is a serialization issue of the WPS.

I think, I have found the culprit, it is in XFolders "wpRefresh" override method (src\classes\xfldr.c).
That method needs to protect itself against being invoked when a Refresh is already ongoing.

Therefore, it should be extended like this:

SOM_Scope BOOL  SOMLINK xf_wpRefresh(XFolder *somSelf,
                                     ULONG ulView,
                                     PVOID pReserved)
{
    BOOL        rc;
    ULONG fFlags;

    // XFolderData *somThis = XFolderGetData(somSelf);
    XFolderMethodDebug("XFolder","xf_wpRefresh");

    fFlags = _wpQueryFldrFlags(somSelf);

    if (fFlags & (FOI_REFRESHINPROGRESS | FOI_POPULATEINPROGRESS))
    {
       return FALSE;
    }

   _wpModifyFldrFlags(somSelf, FOI_REFRESHINPROGRESS,FOI_REFRESHINPROGRESS);

    rc = XFolder_parent_WPFolder_wpRefresh(somSelf, ulView, pReserved);

    fdrForEachOpenInstanceView(somSelf,
                               stb_UpdateCallback,
                               2);           // update

    xthrPostWorkerMsg(WOM_REFRESHFOLDERVIEWS,
                      (MPARAM)somSelf,
                      (MPARAM)FDRUPDATE_TITLE);

   _wpModifyFldrFlags(somSelf, FOI_REFRESHINPROGRESS,0);

    return rc;
}

I think it would also be a good idea to remove the "xthrPostWorkerMsg" as there is no need to update the window title of a single refreshed folder and it also executes asynchronously (so, either reset the FOI_REFRESHINPROGRESS flag in the window function posted to from "xthrPostWorkerMsg" or better remove it completely from this spot).

Is there any proper place where I can raise a problem report ?

29
The Virtualbox provided additions have a fixed "VBoxSF.ifs" for quite some time now. It was fixed in >= 6.1.32 and is working just fine (with shared folders) with the provided "VBoxSF.ifs".
See: https://www.virtualbox.org/ticket/19453

For the same reason,whenever you update Virtualbox you should always also update the complete guest additions (available as a "virtual device" called "guest additions").

I have never found a need to update gengradd.dll but in case it matters for your sytem:
For your graphics problem, unlock \os2\dll\gengradd.dll and overwrite with the gengradd.dll that is part of the guest additions. However, do not copy the lib*.dll files from the guest additions as they are outdated/no longer needed.

30
Applications / Re: ArcaOS 5.1 - First Impressions
« on: January 06, 2024, 01:36:44 pm »
It's a folder with 362 Icon files.

Thanks for sharing that little detail. I was able to duplicate this easily once I knew what you were talking about (though I suspect they were actually PNG icons, not "icons"). Blame the MM classes...

It's .ICO files of class WPIcon. That is not a subclass of any MM class. Also, I can open the /OS2 folder, hit F5 multiple times with the same effect.
The only thing that helps is to close the folder which will immediately terminate all those refresh threads.
Xworkplace's XFolder replaces the wpPopulate method. If at all, I would suspect this to be the culprit.

As a test, I have reduced to one core only. In that case, the second PMShell instance will not "accumulate" multiple threads. So, this is a serialization issue of the WPS.

Pages: 1 [2] 3 4 ... 85