1
Hardware / Re: USBCOM big problem
« on: January 10, 2025, 11:03:29 am »
For the "Future Technology" device you should try USBSER.SYS instead of USBCOM.SYS.
OS2 World Community Forum
OS/2, ArcaOS and eComStation - Warp Community
News:
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
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.
2
Programming / Re: DISKIO - storage device detection logic
« on: January 04, 2025, 02:32:16 pm »
I seem to remember that IOCTL_PHYSICALDISK was for accessing all sectors of a physical disk whereas IOCTL_DISK was for accessimg a drive / a volume (or partition) of a disk.
So that has nothing to do with device type.
So that has nothing to do with device type.
3
Programming / Re: DISKIO - preferred TIMER to use
« on: December 27, 2024, 12:21:32 pm »
You can also use the TIMER$ driver with all its known ill effects (high IRQ load, for example). Question is if that timer will too much interfere with the measurement itself ( decrease I/O performance due to the high IRQ rate of the timer).
4
Setup & Installation / Re: TCP/IP 4.3 patches
« on: November 25, 2024, 06:49:33 am »
I understood from Neils comment that the base device drivers in the patch package are not properly doing the job. An executable building upon these cannot fix that.
5
Setup & Installation / Re: TCP/IP 4.3 patches
« on: November 13, 2024, 04:28:28 pm »
Neil is trying to install and upgrade Warp4. His aim is not to cannibalize his ArcaOS installation, nor to invest hundreds of dollars to update to it (or eCS).
6
Setup & Installation / Re: TCP/IP 4.3 patches
« on: November 12, 2024, 11:37:41 pm »
I can find it in here:
https://public.dhe.ibm.com/ps/products/tcpip/fixes/v4.3os2/ic27649/ic27649.txt
but of course, that is just an addon patch to TCP 4.3.
The good thing is that it also contains all the relevant protocol and socket drivers and the other DLLs that work together with TCPIP32.DLL (for example TCPIPDLL.DLL that I seem to remember is the interfacing DLL for 16-bit apps using the older BSD Version 4.3 API and TCP32DLL.DLL is the interfacing DLL for 32-bit apps using the older BSD Version 4.3 API, see also the TCP/IP Version 4.21 Programming Reference that comes with the OS/2 toolkit: "Introduction to Networking Services).
https://public.dhe.ibm.com/ps/products/tcpip/fixes/v4.3os2/ic27649/ic27649.txt
but of course, that is just an addon patch to TCP 4.3.
The good thing is that it also contains all the relevant protocol and socket drivers and the other DLLs that work together with TCPIP32.DLL (for example TCPIPDLL.DLL that I seem to remember is the interfacing DLL for 16-bit apps using the older BSD Version 4.3 API and TCP32DLL.DLL is the interfacing DLL for 32-bit apps using the older BSD Version 4.3 API, see also the TCP/IP Version 4.21 Programming Reference that comes with the OS/2 toolkit: "Introduction to Networking Services).
7
Setup & Installation / Re: TCP/IP 4.3 patches
« on: November 12, 2024, 08:45:32 am »
You presumably need to update both, MPTS and also TCPIP:
https://altsan.org/os2/fixpaks/mpts.html
https://altsan.org/os2/fixpaks/tcpip.html
https://altsan.org/os2/fixpaks/mpts.html
https://altsan.org/os2/fixpaks/tcpip.html
8
Programming / Re: DOSBox-x - infinite loop in configure/make
« on: November 07, 2024, 01:59:58 pm »
So why not like this:
bool cdrom = drive->isRemovable() ? true : false;
Because that is a method that the "DOS_Drive" class offers (should offer, it's a virtual method that needs to be filled "with life").
Then, you do not need all that other test nonsense to test for CDROM yes/no.
In the end, all that #ifdef'ed code is nonsense as "labellocal" is not used anywhere.
I think all the (outer) //Get Volume label #ifdef block can therefore go away.
bool cdrom = drive->isRemovable() ? true : false;
Because that is a method that the "DOS_Drive" class offers (should offer, it's a virtual method that needs to be filled "with life").
Then, you do not need all that other test nonsense to test for CDROM yes/no.
In the end, all that #ifdef'ed code is nonsense as "labellocal" is not used anywhere.
I think all the (outer) //Get Volume label #ifdef block can therefore go away.
9
Hardware / Re: Mouse, Trackpoint, Trackpad, Touchpad - I2C Question
« on: November 04, 2024, 10:37:09 am »
Question is: how does the I2C controller interface to the PC system?
Does the I2C controller show up as a PCI device ? Is there a standardized set of (io mapped or memory mapped) registers or some such to talk to the I2C controller ?
I also cannot find any information on how to unambiguously identify a device on the I2C bus. You can scan the I2C bus and see what device addresses are in use but not exactly what device (like for USB, the vendor and product id ...).
That seems to be pretty proprietary, from what I can tell all scan code for I2C devices guesses the device by its typical address use.
Does the I2C controller show up as a PCI device ? Is there a standardized set of (io mapped or memory mapped) registers or some such to talk to the I2C controller ?
I also cannot find any information on how to unambiguously identify a device on the I2C bus. You can scan the I2C bus and see what device addresses are in use but not exactly what device (like for USB, the vendor and product id ...).
That seems to be pretty proprietary, from what I can tell all scan code for I2C devices guesses the device by its typical address use.
10
Programming / Re: [SDL2] SDL_ListModes and emulation
« on: November 01, 2024, 09:41:02 am »Hi Lars
I deleted the sdl2*.dll files that starfighter definitely uses and updated SDL2 to 2.28.1-1 then tried running Starfighter.
Result: Error window displayed stating Cannot start J:\Games.eCS\StarFighter\starfighter.exe ...
Dropped starfighter.exe onto the PMdll object which shows starfighter needs the following files to run
sdl2.dll
sdl2mix.dll
sdl2img.dll
The above are not included in SDL2 2.28.1-1
Maybe you already have those somewhere on the libpath? - Or am I missing some sort of "forwarder" dll file where calls to sdl2*.dll files get passed to sdl2200.dll?
Regards
Pete
Ah, ok. I was mislead by you stating that the SDL2 package installed by ANPM "does not work". I thought that that would trap your system or some such.
Now I see that the game uses a completely different SDL2 implementation (thanks OS/2 for being such a mess).
I found the mentioned SDL2 files in my \ecs\dll directory and they are from 2016. Likely the package that you also have installed. So no, you are not missing anything.
By the way, I find this newer package:
http://www.hobbesarchive.com/Home/Download?path=/Hobbes/pub/os2/dev/libraries/graphics/SDL2_2-0-4_2020-09-07.zip
Have you tried that or is it better to stick to the package from 2016 ?
11
Programming / Re: [SDL2] SDL_ListModes and emulation
« on: October 31, 2024, 07:28:27 pm »Hi Mentore
I have not played any ZX Spectrum games in many years, would not mind having another go at pacman as I think the Speccy version was the best.
Starfighter (downloaded from hobbes) is an SDL2 game that runs in a window so SDL2 for OS/2 should not be fullscreen only.
However, Starfighter does not work with SDL2 files installed by ANPM - currently at 2.0.18-3 - but requires an earlier package http://hobbes.nmsu.edu/download/pub/os2/dev/SDL2-2.0.4-20160225.zip in order to run.
So, I guess the question is: Are you using the right variant of SDL2?
Regards
Pete
Hi Pete,
1) I downloaded "Project_Starfigher_1-6.zip" from Hobbes
2) I have SDL2 version 2.28.1-1 installed, so that is newer than what you have. I got this either from Netlabs or Netlabs experimental as an RPM, you should be able to also install it.
That works just fine with USB audio as well as on board audio (UNIAUD). I can switch back and forth the default audio device and that also works just fine.
12
Programming / Re: VisualAge C++ 3.6.5 (+ Fix2) - WarpIn or RPM?
« on: October 31, 2024, 01:04:59 am »
See here:
http://www.hobbesarchive.com/Home/Download?path=/Hobbes/pub/incoming/VAC_3-6-5_InstallFix_2024-10-31.zip
Once you copied the CD-ROM to a temp dir and dropped the ZIP over it, you just need to get the two Fixpak 2 files and drop them into the FIXPAK2 folder.
The main folder contains the main install REXX script, the FIXPAK2 folder contains the two REXX install scripts to install the 2 fixpak files.
http://www.hobbesarchive.com/Home/Download?path=/Hobbes/pub/incoming/VAC_3-6-5_InstallFix_2024-10-31.zip
Once you copied the CD-ROM to a temp dir and dropped the ZIP over it, you just need to get the two Fixpak 2 files and drop them into the FIXPAK2 folder.
The main folder contains the main install REXX script, the FIXPAK2 folder contains the two REXX install scripts to install the 2 fixpak files.
13
Setup & Installation / Re: WSeB Server parts on ARcaOS 5.1 with installed Samba - what to deinstall?
« on: October 28, 2024, 12:33:55 pm »Sigurd,
This
SS:ESP=05c7:00003732 SSACC=00f3 SSLIM=00003fff
indicates we failed with stack overflow. Of course, this does not tell us why. We need to see to logs to get some idea of what the installer was doing at the time of the exception.
Hi Steve,
can you briefly explain why ? The segment is not an expand down segment so the offset (3732) should always be <= lim (3fff) which it is.
To me the error more looks like 5c7:4f34 (ES:"value of P2") has been attempted to access (DS is 0 which seems odd ...). And 4f34 certainly exceeds 3fff.
By the way: do you know what P1=00000008 (XCPT_SPACE_ACCESS) is supposed to mean ? I could not find any info about that.
14
Programming / Re: VisualAge C++ 3.6.5 (+ Fix2) - WarpIn or RPM?
« on: October 25, 2024, 02:07:51 pm »
The FI browser plugin largely cripples the capabilities of Feature Install.
For example, you are very limited in selecting/deselecting packages (for VAC 3.6.5 the only thing you can do is to install or not install the toolkit). Plus it is more of a hassle rather than help.
As Alex Taylor has presented, using FI via the command line (clifi.exe) is not too difficult and my REXX scripts make use of that. They even avoid the need for any manual interaction (apart from selecting/deselection of packages which I think is a fair enough reason for manual interaction).
The fixes also install via REXX scripts and FI is smart enough to find out what to update and where the original install is located.
For example, you are very limited in selecting/deselecting packages (for VAC 3.6.5 the only thing you can do is to install or not install the toolkit). Plus it is more of a hassle rather than help.
As Alex Taylor has presented, using FI via the command line (clifi.exe) is not too difficult and my REXX scripts make use of that. They even avoid the need for any manual interaction (apart from selecting/deselection of packages which I think is a fair enough reason for manual interaction).
The fixes also install via REXX scripts and FI is smart enough to find out what to update and where the original install is located.
15
Programming / Re: VisualAge C++ 3.6.5 (+ Fix2) - WarpIn or RPM?
« on: October 24, 2024, 07:13:27 am »
I have created a CD-ROM that contains a few Rexx scripts that build upon the Feature Installer. No need for Netscape. I can bundle the changes in a ZIP and then you need to do this:
1) copy your cd-rom to a tmp dir
2) drop the zip content on top of that. Due to licensing issues, you will also need to get the fixpak and put it in a subdir
3) burn a new cd-rom from that
You can then just invoke the rexxscript that allows you to select a target location. The rexx script for the fixpak needs no additional info as it can locate the install location via feature install.
1) copy your cd-rom to a tmp dir
2) drop the zip content on top of that. Due to licensing issues, you will also need to get the fixpak and put it in a subdir
3) burn a new cd-rom from that
You can then just invoke the rexxscript that allows you to select a target location. The rexx script for the fixpak needs no additional info as it can locate the install location via feature install.