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 ... 34
1
Applications / Re: DMARC error
« on: August 17, 2022, 02:22:35 pm »
The domain name that is your email address is SPF and DMARC setup correctly ?

Goto https://mxtoolbox.com/ and put your domain name to check if stuff is setup correctly.
Is your SPF record also needs to have the correct entries.

Roderick Klein

2
Applications / Re: Test build of dooble with qt5
« on: June 18, 2022, 09:41:59 pm »
Dmitry is currently still traveling. He is now working to get settle within the EU. I visited him in Turkey about 1 month ago.
So for now the work on the browser is kind of on halt.

Roderick

3
Events / Re: User Meeting Cologne November, 5th 2022 confirmed
« on: June 17, 2022, 05:34:28 pm »
Hi Remy

we have not decided wether we will record the meeting on video or not. We will discuss a live stream as well, but Thomas and me are not experts in this case, we will have a look at this even though.

Please give us more information on the travel topic. I do not understand what you exactly mean, sorry for this, I have to apologize.
I guess you - if at all - would travel from France to Germany and I do not see any restrictions regarding this. Do you have a link for me where I can get further details? Thank you in Advance!!

When I organized WSE in Cologne, it turned out the internet connection in the youth hostel a few years ago was REALLY bad. They said they would get a fibre optic internet connection. So a video stream would be very difficult. At the time they had they had a few stacked DSL lines. When a busload of students arrived the video stream was dead. I streamed the video stream in the end via my mobile phone. I can help with that if I am present.

Roderick

4
General Discussion / Re: eCS 2.2 purchase
« on: June 16, 2022, 10:44:10 pm »
You will never know how much of system memory (RAM) is mapped below the 4 GB physical address line.

Newer systems tend to reserve a lot of the physical memory space below 4 GB presumably for the PCI(e) bus so that you can use older 32-bit PCI cards/devices, potentially requiring large amounts of physical address space (like, say a 32-bit PCI graphics card with 2 GB of video memory: it needs 2 GB of physical address space below the 4 GB address line). Newer 64-bit PCI cards are of course not suffering from this problem.

It's just a fact that every modern OS is 64-bit by now, which means, it has no problem accessing system memory if it is mapped to physical addresses beyond 4 GB and therefore it is not affected by this limit. And therefore manufacturers no longer care about this limit.

Testing ArcaOS 5.1. beta (I am on the tester team) I have seen systems where all PCI devices have 64 bit MMIO addresses (I had one of these laptops). The UEFI loader remaps these back to 32 bit MMIO address ranges. Now the video card could be an issue using a lot of memory below the 4 GB. However more and more video cards have something called PCI bar resizing. This *might* help de amount of reserved RAM be reduced. When I have such a laptop I will test again and see if that is indeed the case.

Roderick Klein

5
General Discussion / Re: eCS 2.2 purchase
« on: June 09, 2022, 02:05:59 pm »
I am testing a system here with UEFI firmware (1 year old) and I have 3.3 GB of RAM. It depends on the system.

Roderick

6
Applications / Re: Boycott Discussion
« on: June 01, 2022, 01:53:21 pm »
It is not to undermine the free will. Its rather to see how we can try and learn in this forum to see how we can possibly analyse WHY a program crashes.

Who ever made a memory dump or process dump  and loaded in PMDF ?

Roderick

7
Hardware / Re: ArcaOS 5.1 UEFI support - GOP?
« on: May 28, 2022, 06:07:07 pm »
With the phase out of the BIOS, the VGA BIOS and VGA hardware is also gone. That is pretty big step! VSVGA.SYS is basically a big wrapper around the video BIOS and VGA hardware. VEFI.SYS partly emulates the VGA hardware. So there is some slowdown, but on new UEFI only systems the system is that quick you should not notice it.  But it should be faster then DOSbox possibly, because the rest of the hardware is "real".

A lot of the stuff for me does not look totally unknown as I looked at in my Mensys days working on eCS... It just never got of the ground.

Roderick

8
Hardware / Re: ArcaOS 5.1 UEFI support - GOP?
« on: May 27, 2022, 07:20:45 pm »
All this info you can find in youtube presentations from alex taylor he did for warpstock europe.

Thanks, Roderick, I'll check it out. Sadly, if there were captions (auto-generated or otherwise) on the video, a Google search didn't pop it up when I was searching :(.

Try this

https://www.youtube.com/watch?v=onY3uZw7m3Y

Roderick

9
How big is DUX, can you ZIP up the program and send it to roderickklein@xs4all.nl I will try and debug it here and see if I can find the reason for the crash.

Roderick

10
Applications / Re: Boycott Discussion
« on: May 27, 2022, 11:45:03 am »
Its not any statements against anybody or OS/4. You should not recommend to swap key system files to get an application to work. I think we should rather start to learn how to analyze the issue at hand and see if we can fix possibly. If you put an old version of PMMERGE.DLL, what can then be broken ?

That's my fault and I apologize. I saw mention that the trap was happening in PMMERGE.DLL and I remembered that the OS/4 team had squashed some bugs in that, so I figured it was worth a shot to try.

Nobody is to blame at all. All suggestions are well intended. I just do not see you should swap a key system file.  OS/4 has fixed some bugs in PMMERGE.DLL. But I did not know what exactly fixed and that is why I asked what bugs where fixed. I suggested asking for the information so we could possibly find out what was causing it. But sadly PMMERGE.DLL is a big DLL and a lot ways this DLL can crash. Its one of the core PMSHELL DLL's.
The crash could be caused by an installed font. Does the DUX program install any extra fonts for example ?

I thought it would have been a great learning project to debug the issue on the forum. The stuff how to read popuplog.os2 is document by IBM in PDF's, Martin has these. And Martin I think knows what PMDF.EXE is for ?, which I also suggested we could use to load a procesdump.
We could have use Steve Levine his script for this http://www.warpcave.com/os2diags/index.html  to create a procdump.
How many people use this to debug crashes they can not figure out ?

Roderick

11
Applications / Re: Boycott Discussion
« on: May 27, 2022, 11:36:33 am »
Hi Roderick
From my perspective this way of fixing stuff is the same as throwing mutt at the wall and see if it sticks.
I think everybody is putting Glenn on the wrong foot to make him replace pmmerge.dll. It might fix the crash the but nobody even knows why the crash occurs in the first place. So if you backlevel the last version of pmmerge.dll with an older one. The program might start to work, but then what is broken ?
I mean its all well intended but what is causing the crash in the first place ? PMMERGE.DLL is pretty important system dll and not something that should just be swapped out like spare tire from the trunk of your car.

I took these words as your opinion and FUD against the OS4 development..

Regards

I told you that already 3 times Martin its not, not not. End of story.  I thought we would try as community project see how we could analyze the issue and learn how to trace the issue in the way you can trace it with tools from IBM. 

Why do you think I asked in the second posting for the popuplog.os2 entry to see what is going on ?
https://www.os2world.com/forum/index.php/topic,3063.msg34814.html#msg34814

Why do you think I asked for this ? If the version of PMMERGE.DLL matches with the PMMERGE.DLL you MIGHT be able to trace the crash.
The crash could be caused by an font installed. I have seen that happen as well.

Why do you think I suggested using PMDF and making a procdump of the process crashing ?
I will not try and get engaged anymore to try and help debug a problem anymore.
Good luck swapping files around.

Roderick

12
Hardware / Re: ArcaOS 5.1 UEFI support - GOP?
« on: May 27, 2022, 01:07:55 am »
Rich explained it better. Anyway in Arcaos 5.1 beta the bass video handler dll bvhsvga.dll has been replaced by bvhefi.dll for uefi boit. The uefi loader provides an extremely minimal video bios. And vsvga.sys for dos sessiobs is replaced by vefi.sys.

All this info you can find in youtube presentations from alex taylor he did for warpstock europe.


Roderick

13
Hardware / Re: ArcaOS 5.1 UEFI support - GOP?
« on: May 27, 2022, 01:03:58 am »
Its already workung with go suppirt. Arcaos ships with something called an launcher.

Roderick

14
Applications / Re: Boycott Discussion
« on: May 27, 2022, 12:17:15 am »
Its not any statements against anybody or OS/4. You should not recommend to swap key system files to get an application to work. I think we should rather start to learn how to analyze the issue at hand and see if we can fix possibly. If you put an old version of PMMERGE.DLL, what can then be broken ?

What can we do with popuplog.os2 Entry ? How can we analyse a crash and see if we can fix it actually. Sometimes the exceptq.log provides SOME information so you can see what goes wrong. But since popuplog.os2 has registers. How can you analyse this ? If we could learn that togheter we can help possibly BETTER analyse crashes for people as team. BTW That is not always easy, but if we can learn it to an extend...

15
I tried to load this version on ArcaOS 5.0.7.
https://hobbes.nmsu.edu/download/pub/os2/apps/misc/AHD_Patch_2-02.zip
It opens but no crash occurs. Anyway I would need your popuplog.os2 entry. And if that does not work maybe procdump can help to figure out WHY its crashing. You could load that up in PMDF and with the PMMERGE.SYM file give a hint why its crashing.
Its not easy but it could give a hint.

Pages: [1] 2 3 ... 34