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 ... 99
1
Networking / Re: Network setup for VirtualBox
« on: December 18, 2025, 04:22:50 pm »
Can you not use "Netbios via TCP/IP" instead of plain "Netbios" ?

2
Networking / Re: OS/2 IP Stack Hardening
« on: December 15, 2025, 09:29:55 am »
So, what machine gives you problems ?

It is obvious that "inet" is outdated and has no convenience package installed, in contrast to "main" which seems up-to-date.

And from Alex' website, I deduce that if you install convenience package 2 for WSeB, then that includes updates to the TCP/IP stack. Once you have done that, you can potentially install further updates as per Alex' website.

3
Storage / Re: Sharing drive between OS/2 and linux -JFS
« on: November 28, 2025, 12:17:32 pm »
I can't manage to mount a OS/2 created JFS partition on my Debian 12. No matter what I tried it does not work.
Code: [Select]
root@zazu:/dev# mount -t jfs /dev/sdc1 /media/500GB/
mount: /media/500GB: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.
In dmesg I see nothing what would help -
Code: [Select]
root@zazu:/srv# dmesg | grep -i sdc
[    3.817598] sd 3:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[    3.817600] sd 3:0:0:0: [sdc] 4096-byte physical blocks
[    3.817612] sd 3:0:0:0: [sdc] Write Protect is off
[    3.817615] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[    3.817632] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.817650] sd 3:0:0:0: [sdc] Preferred minimum I/O size 4096 bytes
[    3.840623]  sdc: sdc1
[    3.840683] sd 3:0:0:0: [sdc] Attached SCSI disk
[  361.915751]  sdc: sdc1
[  362.183053]  sdc: sdc1
[  686.496790]  sdc: sdc1
[12970.328576]  sdc: sdc1

Superblock seems to be okay -
Code: [Select]
root@zazu:/dev# jfs_tune -l /dev/sdc1
jfs_tune version 1.1.15, 04-Mar-2011

JFS filesystem superblock:

JFS magic number: 'JFS1'
JFS version: 1
JFS state: clean
JFS flags: JFS_OS2  JFS_COMMIT  JFS_GROUPCOMMIT  JFS_INLINELOG 
Aggregate block size: 4096 bytes
Aggregate size: 976672248 blocks
Physical block size: 512 bytes
Allocation group size: 1048576 aggregate blocks
Log device number: 0xb
Filesystem creation: Thu Nov 27 16:56:38 2025
Volume label: 'JFS_BACKUP'

I tried different disks. Numerous attempts to create a JFS partition with MiniLVM and try to mount it in Linux. But can't get it to work.

fdisk complains that it does not start on sector boundary. But how can that be? I think OS/2 - ArcaOS can create partitions on sector boundaries only.
Code: [Select]
root@zazu:/dev# fdisk -l
Disk /dev/sdc: 465,76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC WD5000AZLX-6
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xdf5ee166

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdc1  *       63 976768064 976768002 465,8G  7 HPFS/NTFS/exFAT

Partition 1 does not start on physical sector boundary.

Any attempts to create the partition on Linux an see it on ArcaOS fails also. Help appreciated.

Just a guess:
The error message says that the partition does not start on a physical sector boundary. Which is correct as the physical sector is 4096 bytes in size.
Given that the minimum I/O size is also 4096 bytes in size, I would think that your drive does not allow to be accessed by 512 byte sectors. Or you might need to jumper it (if possible) to allow addressing by 512 byte sectors.


4
Programming / Re: Software ports - the state of my art until now
« on: November 25, 2025, 07:32:01 am »
In case "nasm.exe" is used as the assembler:

why can you not use switch "-f obj" to produce an OMF object file right away ? That would be the equivalent to calling the C compiler with the "-Zomf" switch which will also produce an OMF object file.

That's at least the nasm switch I used to compile some SSE3 assembler code (unfortunately, alp.exe does not support SSE3) to link with a few other (OMF) object files with Watcom. And that worked without a problem.

5
Programming / Re: Software ports - the state of my art until now
« on: November 19, 2025, 01:52:56 pm »
Hello all, I have finally set up a convenient development environment for my ArcaOS 5.1 VM and I'm in the process of porting some other software, hoping it will be useful. I placed my hands on something interesting, I have to say - and many things just compile without problems, thanks to the huge work of people like Paul Smedley and the others. Thanks guys!


After the good news, here are two interesting (?) problems I'm encountering on two ports:

1 - I'm working on porting Hatari (Atari emulator on SDL, https://www.hatari-emu.org/) and it mostly compiles, but then emxomf fails with two errors:

emxomf: Index too large
emxomfld: a.out to omf conversion failed for 'cpu/UaeCpu.a'.
make[2]: *** [src/CMakeFiles/hatari.dir/build.make:1287: src/hatari.exe] Error 1
make[1]: *** [CMakeFiles/Makefile2:460: src/CMakeFiles/hatari.dir/all] Error 2
make: *** [Makefile:146: all] Error 2


I think they may be related to cmake, but can't find the culprit. Some of my current flags are these (attaching the CMD file I'm using to set up my dev environment):

EMXOMFLD_LINKER=wl.exe
EMXOMFLD_TYPE=wlink
CFLAGS=-O2 -DOS2
CXXFLAGS=-O2 -DOS2
ASLAGS=-Zomf
LDFLAGS=-Zomf -Zhigh-mem
LIB=-lcx


2 - eigen3 (math library) and octave workshop, both requiring Qt4:
I've tried to install all Qt4 software from RPM repositories but I still seem unable to find the development libraries. I'm about to look at them again but currently I seem unable to compile Qt4 software.

I'll gladly accept any advice on these two problems I'm encountering - in the meantime I'll try on something more and maybe start publishing my works on hobbes.

Mentore

ASLAGS ? I suppose that should be ASFLAGS ?
I think -Zomf should go into CFLAGS and CXXFLAGS and not ASFLAGS (assuming ASFLAGS are for the assembler)

6
Thank you very much for your offer but that won`t be necessary.
Glad you got it working. Which means I can now update the existing package with the updated .NIF file.
By the way, could you attach your protocol.ini, just out of curiosity ?

8
The best I can think of is to look into "Presentation Manager Driver" source code and see how it is being used. Other than that, I would not know.

9
What happens if you maximize and then restore a window while in seamless mode ?

Another idea: open Windows in full screen mode, go to ProgramManager->ControlPanel->Desktop and set "Border Width" to say 3. Maybe you need to change back and forth between two values. The default value seems to be 3. Note that this will not be possible if you are in seamless mode !

If that still does not help: there are entries in OS2.INI like "WIN_RES_x". In each of these there are 4 keys that reference what windows display driver is in use for fullscreen and seamless, respectively. Maybe you will have to manually update each of these to match your settings in system.ini.

10
I don't pretend to understand it but just a gut feeling: have you tried and toogle between different OS/2 Desktop schemes ? Maybe that helps.
If there is something like Window Desktop schemes (I cannot remember) you can try that, too.

Are you using the default drivers (that come with GRADD, I think) for fullscreen and seamless Windows or have you replaced these with the Windows drivers that Martin is advertising:
https://www.os2world.com/forum/index.php/topic,3836.msg49420/topicseen.html#new

?

11
How to use this .NIF file:

1) get the latest driver for your Xircom CE2 card: https://hobbesarchive.com/Home/Download?path=/Hobbes/pub/new/Xircom_CreditCardIIps_2-04.zip

2) unzip the file into a temporary directory

3) change to the "NDIS" subdirectory of that temporary directory and copy/overwrite the CE2OS2.NIF file to that directory

4) run the "Network Adapters and Protocols" tool to install the driver by browsing to the "NDIS" subdirectory

A word of wisdom: The CE2NDIS.OS2 driver seems to support quite a few settings that I now added to the CE2OS2.NIF file so that they can be set and written to PROTOCOL.INI. Amongst those settings there are a couple of boolean settings with "Yes"/"No" keyword values for true/false. I think the Xircom device driver writers took a shortcut for boolean values in that they are only looking for the keyword instead of the proper keyword value. That said, it means that if you want to delete a boolean setting you will actually need to wipe the keyword value to an empty string instead of setting it to "No" so that it will be completely removed from PROTOCOL.INI. Additionally, it might be possible that for boolean settings, the driver will only expect to see the keyword instead of the keyword = value line. It might therefore need some experimentation.
Most importantly, the CE2NDIS.OS2 driver also supports point enabled operation by setting CARDSERVICES and SOCKETSERVICES both to "No". So you can still install PCMCIA card and socket services support and then ignore the slot where you inserted the Xircom card as suggested by Steve.

Another word of warning: per default the driver operates in "memory" mode and not "io" mode where memory means the drivers registers are memory mapped (addressable by a normal memory address instead of an io port). The address range accepted by the driver/the default address (expressed as a real mode segment value) might not be available on your system. If you have odd system behaviour, you might then try other values for the [MEM] keyword. The ArcaOS memory utility (or the QSINIT loader) can help you with the display of reserved memory regions on your system. I can help if that should become relevant/necessary.

Once you find out that the .NIF file works for you, let me know and I will rebundle the driver zip with this updated .NIF file and reupload to Hobbes.

12
Sorry for the late reply, had some hardware issues on the Thinkpad. The original drive died so I replaced with a flash card. The Xircom dongle also seems to be defective. I installed on a Windows 98 laptop and got the drivers installed but was getting inconsistent pings at the slightest touch of the dongle.

@Martin - I downloaded the drivers you posted, need to get a dongle to test. Thank you.

In case you want to retry your CE2 card with the driver set that Martin provided (say "FIN-XIR2.ZIP"):
the .NIF installation file would need a "brush up" to actually install the proper entries into the PROTOCOL.INI file.
Gleaning at the driver binary (CE2NDIS.OS2) and other .NIF files from Xircom, I think I would be able to provide you with a fixed .NIF file.

I can also see that even with the CE2NDIS.OS2 driver (and a corrected .NIF file), you will be able to ignore socket services and run the driver in "point enabled" mode which would allow you to always have PCMCIA support installed. If set up correctly via PROTOCOL.INI, the driver will just ignore/bypass the card services.

@Martin: would you see any issues in uploading these drivers to Hobbesarchive ? I am not the legal expert ...

If you would be willing to cleanup the .NIF file for install I would be more than happy to test and buy a cup coffee or make a donation for the work put in. I have a dongle on the way and should be here next week.

13
Sorry for the late reply, had some hardware issues on the Thinkpad. The original drive died so I replaced with a flash card. The Xircom dongle also seems to be defective. I installed on a Windows 98 laptop and got the drivers installed but was getting inconsistent pings at the slightest touch of the dongle.

@Martin - I downloaded the drivers you posted, need to get a dongle to test. Thank you.

In case you want to retry your CE2 card with the driver set that Martin provided (say "FIN-XIR2.ZIP"):
the .NIF installation file would need a "brush up" to actually install the proper entries into the PROTOCOL.INI file.
Gleaning at the driver binary (CE2NDIS.OS2) and other .NIF files from Xircom, I think I would be able to provide you with a fixed .NIF file.

I can also see that even with the CE2NDIS.OS2 driver (and a corrected .NIF file), you will be able to ignore socket services and run the driver in "point enabled" mode which would allow you to always have PCMCIA support installed. If set up correctly via PROTOCOL.INI, the driver will just ignore/bypass the card services.

@Martin: would you see any issues in uploading these drivers to Hobbesarchive ? I am not the legal expert ...

14
Marc, you are saying that you are using XIRCOM card CE2 but you have installed driver CE3NDIS.OS2.

Are you sure that is the correct driver for your card ? On the other hand, I cannot find anywhere a driver CE2NDIS.OS2.

Anyway, the driver that Steve has suggested (the point enabled driver) is here:
https://archive.org/download/Xircom/Xircom.zip

15
Can you post your setup.cmd and also protocol.ini ?

The error does not sound as if this is HW or driver related. It rather sounds like TCP/IP not being set up correctly.

By the way: you might also consider applying the patch to the NDIS driver:
https://www.os2site.com/sw/drivers/network/3com/3c589patch.zip

That might not strictly be necessary on your system but it surely won't hurt either. In addition, it will make the "3net_log.exe" utility work.

Finally, look here, it is about Warp 4 but since you are using Warp 3, it might apply nonetheless:
https://www.os2world.com/olderforum/OS2World%20Ultraboard/www.os2world.com/cgi-bin/ultraboard/UltraBoardea6e.html?action=Print&BID=62&TID=1518&SID=

Pages: [1] 2 3 ... 99