1
Applications / Re: OO v3.18
« on: January 16, 2025, 06:32:44 pm »
Isn't there an ICU legacy package available too? yum list icu*
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.
> /Z is normally needed if you don't have RTS/CTS wired.
So I misunderstood the usbcom.txt - '/Z Forces CTS handshaking and forces DSR and CTS on.'. 'Forces handshaking' sounds to me like I need CTS active driven from the link partner. I would call left unconnected CTS/RTS/DSR/DTR as 'no hardware handshake' or 'ignoring hardware handshake lines'.
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM5 /Z
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM6 /Z
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM7 /Z
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM8 /Z
REM ! DEVICE=M:\OS2\BOOT\USBCOM.SYS
DEVICE=M:\OS2\BOOT\USBCOM.SYS /M:4 /N:COM6 /Z
apirc = DosQueryFSAttach(sTemp, 0, FSAIL_QUERYNAME, p2, &cbBuffer);
//TRACE1(" apirc=%4d ", apirc);
if ( apirc == NO_ERROR )
{
//TRACE1("%-8s ", p2->szName + p2->cbName + 1);
if ( p2->cbFSDName > sizeof(DriveInfo[uDrvNo].fsName)-1 ) p2->cbFSDName = sizeof(DriveInfo[uDrvNo].fsName)-1 ;
memcpy(DriveInfo[uDrvNo].fsName, p2->szName + p2->cbName + 1, p2->cbFSDName);
DriveInfo[uDrvNo].fsName[p2->cbFSDName] = '\0';
switch ( p2->iType )
{
case FSAT_CHARDEV: // Resident character device
DriveInfo[uDrvNo].type = DT_FLOPPY;
break;
case FSAT_PSEUDODEV: // Pusedu-character device
if ( IsMediaRemoveable(uDrvNo) )
DriveInfo[uDrvNo].type = DT_REMOVABLE;
else
DriveInfo[uDrvNo].type = DT_RAMDRIVE;
break;
case FSAT_LOCALDRV: // Local drive
if ( !strncmp (DriveInfo[uDrvNo].fsName, "CDFS", 4) )
DriveInfo[uDrvNo].type = DT_CDROM;
else
if ( IsMediaRemoveable(uDrvNo) )
DriveInfo[uDrvNo].type = DT_FLOPPY;
else
DriveInfo[uDrvNo].type = DT_HARDDISK;
break;
case FSAT_REMOTEDRV: // Remote drive attached to FSD
if ( !strncmp (DriveInfo[uDrvNo].fsName, "RAMFS", 5) )
DriveInfo[uDrvNo].type = DT_RAMDRIVE;
else if ( !strncmp (DriveInfo[uDrvNo].fsName, "CDWFS", 5) )
DriveInfo[uDrvNo].type = DT_RSJ;
else
DriveInfo[uDrvNo].type = DT_NETWORK;
break;
}
Is my printf use of '%lld' incorrect?
Which compiler? You don't get any warning when compiling with -Wall?
What other device drivers, especially the IFS stuff, are you loading? What size cache are you defining for these?I usually let the IFS stuff as it is defined by ArcaOS installer. For older systems I also don't have big JFS cache. HPFS386 is remed out since long as it produces similar problems.
The symptoms you describe all look & feel like the "out of memory" stuff I was seeing when testing the very large (>1G) JFS cache sizes here.
it again gives the "Couldn't load xul.dll". This is with VIRTUALADDRESSLIMT = 3072.
With VIRTUALADDRESSLIMIT=2560 it boots ok until it is about to start the desktop and then it goes black.
REM 20210711 VIRTUALADDRESSLIMIT=2560 to 3072 because of qt browser
REM 20210711 neither simplebrowser nor Seamonkey nor ndpiso plugin works with 3072 -> 2900
REM 20211023 changed to 0xXX00 as Dave suggested in AN Testers from 2850 to 2816
VIRTUALADDRESSLIMIT=2816
Max resolution offered by Panorama is 1280x1024.My tests with a new system tought me to -
Is there a "safe" way to get a higher resolution or do I simply have to experiment.
I find it strange that there is so much problems with OS/2 video. I have a dell 30inch 2560x1600 monitor that runs without any problem. No problem with video cards, I don't have one, it runs from the built in video of the Ryzen 3 processor.I observe different problems with OS/2 video output nowadays.
So if you want to dual boot to two operating systems, one using UEFI and one using Legacy or CSM, you would have to put those operating systems on separate drives and use the BIOS supplied F11 boot menu.On my new Asrock B550M Pro4 with Ryzen 7 I choice to UEFI boot from the first MBR NVMe which starts the AN Launcher there. From there I can choose to start an ArcaOS installation on the MBR drive (L:\) but also the ArcaOS installation on my second GPT NVMe (D:\). I also can start GRUB/Debian on the 1. NVMe and Win7 on the second GPT drive.
Does make sense now. But maybe you understand the confusion. Usually we used the standard tools (fdisk, lvmgui, MiniLVM) or DFSee to create all partitions and volumes. There is also the strong advise to only use ArcaOS tools to create volumes. I guess most of us know about these mentioned tools.v 2.52. Included with ArcaOS 5.1.0 EN. Built 2023-08-23. Maybe that's to old. But I really tried. Even looked into the help without any hint.
I even cleared start of the disk with DFSee and started again. But could not find how to select GPT when creating the first partition.
I think there's a basic misunderstanding here: neither MiniLVM nor PTE _create_ a GPT disk. They are partition editors that know how to manipulate an *existing* GPT disk. To create one, you must use 'InitDisk.exe' or DFSee.
After a reboot, MiniLVM will clearly identify which disks are GPT and which are MBR. 'PTE' will only display GPT and will ignore MBR (IIRC). The other partition editors ('lvm.exe' and that java thing) are useless for GPT because they can't see the actual GPT disk.
Too old of a minilvm? Note that the latest is called the "Installation Volume Manager" and seems to handle GPT fine.v 2.52. Included with ArcaOS 5.1.0 EN. Built 2023-08-23. Maybe that's to old. But I really tried. Even looked into the help without any hint.