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" ?
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
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.
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/In dmesg I see nothing what would help -
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.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.
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
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.
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.