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 ... 6 7 [8] 9 10 ... 85
106
Applications / Re: DOSBox Video Resolution Issue - SDL
« on: July 26, 2023, 10:38:28 am »
Usual questions: is there a file DIVE.DLL? Can it be found via LIBPATH? Does it have an entry point #19?

107
Networking / Re: [SOLVED] Release IP and Refresh IP from DHCP
« on: July 25, 2023, 12:42:49 pm »
I can say this about Virtualbox and WIFI: bridged networking can be a persistent problem. I worked around this by creating a NAT network that happens to have the same network address range as my routers local network. That did the trick. And I seem to remember that a NAT network also implements a DHCP server.

108
Programming / Re: Qt6 Development
« on: July 24, 2023, 03:08:57 pm »
I have the feeling that that additional socket option creates a local socket name that is not valid under OS/2.

109
Setup & Installation / Re: USB to Serial adapter setup
« on: July 21, 2023, 08:56:35 pm »
usbser.sys is contained in the DDK toolkit sources. The DDK sources can be found at multiple places in the internet.

110
Setup & Installation / Re: USB to Serial adapter setup
« on: July 20, 2023, 08:10:30 am »
Have to remember that Arca Noae did some major changes to the USB stack to support XHCI (USB3). Might want to test with Lars's stack, which I think is a lot closer to the stack that IBM released.

I seem to remember that someone said that my USBCOM.SYS hangs the system. I also seem to remember that the AN driver is "fitted" to the AN USB stack as that has turned the inter driver interface to 32-bit and therefore requires the USBCOM.SYS to also have a 32-bit inter driver interface (in other words: they gave up on compatibility and implemented their own proprietary interface).

I think, a ticket to AN is the best choice. If mode.com returns "drive not ready" that likely indicates USBCOM.SYS properly detects the device but fails on the OPEN call or some such. Should be debuggable though.

111
Applications / Re: Registry editor
« on: July 17, 2023, 11:59:00 am »
My inis are currently quite big -
Code: [Select]
15.07.23  13.13       3.500.039      0   R_SA_  OS2.INI
15.07.23  13.13         457.587      0   R_SA_  OS2SYS.INI

Just started checkini / cleanini but that didn't help much.

What potentially could help is to write a tool that reads these INIS, application per application and key per key and writes the application/key pairs back to a new INI file that needs to be swapped in/replaces the original on the next system restart.

I suspect that the Prf API is not really good at compressing the INI file, if keys are removed, truncated and/or subsequently enlarged. The only thing that will then (hopefully) help is to actually create a new INI file.

I do not know if checkini/cleanini work this way.

112
Applications / Re: Registry editor
« on: July 13, 2023, 03:47:18 pm »
I wonder if my ini files are a "normal" size.

Directory of  H:\os2\os2*.ini

7-13-23   6:18       2,123,544      0  OS2.INI
7-12-23   9:03         305,745      0  OS2SYS.INI

That's about the size that they have on my system. But I should mention that I still use eCS (with driver updates) and I have no clue what AN changed in addition. I doubt that it helps but you could also try to change the VIRTUALADDRESSLIMIT value (I still think your issue is shared memory related so that might have a bearing on the problem).

What is size/date/bldlevel string of your DOSCALL1.DLL ?

What is really odd is this combination:
Code: [Select]
P1=00000002  P2=001bfffc  P3=XXXXXXXX  P4=XXXXXXXX
SS:ESP=0053:001c0000  SSACC=d0f3  SSLIM=bfffffff
EBP=001c0044  FLG=00010202

That means the program failed when it tried to write (P1=2) 4 Bytes to address 1bfffc (P2) which is just 4 bytes below ESP (EBP pointing well above ESP which is what can be expected). That would mean, you have hit the bottom of the stack / hit guard page of the stack without the OS commiting a new memory page for the stack. Either regedit2 stack is too small (I doubt that) or some recursion happened that ate all of the stack. I think that would point to a problem with the INI file. Even if it does not give you a problem during operation, might want to try an ini file cleaner.

113
Programming / Re: Strange behaviour in SDL2
« on: July 13, 2023, 03:45:15 pm »
Great news, hoping some of the code can be used for https://github.com/psmedley/qt6-multimedia-os2/issues/1

I briefly looked at the Qt stuff but got carried away by the C++ stuff (Qt specifics ? "emit" ...). I do not get where the OS specific nifty details have to go.
SDL2 uses the MMPM API directly, Chromium uses libkai (which I guess is a good choice).

114
Programming / Re: Strange behaviour in SDL2
« on: July 13, 2023, 08:41:41 am »
short update: we have fixed an error in the SDL2 device detection, we have added detection of capture (recording) capable devices, we have implemented capturing/recording support. We still need to test this stuff.

115
Applications / Re: Registry editor
« on: July 13, 2023, 08:25:34 am »
I had opened both, OS2.INI and OS2SYS.INI (of the non-boot partition) via the profile loading function of regedit2 at the same time and that was not a problem. I even opened more profile files (in the end, it was about 5 different files) and that also was not a problem.

I think your assumption is correct that rwINI will not use the ordinary Prf... API functions but will read and parse the profile file contents directly. That will likely avoid some problems with shared mem etc.

Maybe, this problem is related to shared memory (if the Prf... API functions are used), in particular if your OS2.INI and OS2SYS.INI files are very big.

Side note: I can open OS2.INI from my boot partition by using the profile loading function of regedit2.

116
Applications / Re: Registry editor
« on: July 11, 2023, 10:27:14 pm »
I used regedit2 to access my OS2.INI on drive E: from my system on drive D: and had no problems.
1) check if your OS2.INI you are trying to access is corrupt
2) check for file attributes. For some reason my OS2.INI and OS2SYS.INI on drive E: only have the "A" attribute set while the ones on the D: drive have the "RSA" attributes set. But maybe the file attributes are changed when these files are opened during system start

117
Programming / Re: Qt6 Application Testing
« on: July 05, 2023, 07:34:13 pm »
and what happens if you adjust INSTALL_DESTINATION to strip to ${CMAKE_INSTALL_PREFIX}/shared only?

118
Programming / Re: Strange behaviour in SDL2
« on: July 01, 2023, 03:39:55 pm »
I was not aware that the details may be interesting to the end user. It was just to not clutter this forum with endless code exchange and to speed up work.

119
Programming / Re: Strange behaviour in SDL2
« on: June 30, 2023, 10:59:57 pm »
I will need to reread the docs. We'll continue on Slack.

120
Programming / Re: Strange behaviour in SDL2
« on: June 30, 2023, 03:21:59 pm »
Also, what you would need to do is build a list of devices in the SDL_DetectDevices function.
Then, the one-based device number can be the handle (again, one-based) that you use as the instance number in the MCI_OPEN call. That would allow to select between different devices.

Pages: 1 ... 6 7 [8] 9 10 ... 85