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 - Dave Yeo

Pages: 1 [2] 3 4 ... 324
16
Applications / Re: AOS disk size limitation?
« on: June 04, 2024, 07:20:44 pm »
Doug Bisset came up with the format routine, I expanded it to keep the JFS volume there between warm reboots.
I often use the ramdisk as a scratch work area, so like it to be preserved for a warm reboot, which includes the system dump keys (CTRL-ALT-F10 twice) when the OS locks up, which does mean running chkdsk on the ram disk.
Eventually there's a cold reboot to clean the ram disk and even with only a 4GB ram disk, I haven't had it fill up.

17
Applications / Re: AOS RAM Disk
« on: June 04, 2024, 08:13:44 am »
I think you could remove the cache statement, or at worst shrink it to 64 if removing it seems to screw things up.
Personally, I reformat as JFS, see my other reply.

18
Applications / Re: AOS disk size limitation?
« on: June 04, 2024, 07:47:08 am »
The limit for OS/2 HPFS is 64GB, in practice somewhat less, perhaps 60GB for stability, so a 8GB ram disk is no problem. The 2GB limit is the file size limitation on HPFS.
If you want JFS, add this to startup.cmd (ram disk is H: here, adjust as needed)
Code: [Select]
if exist H:\jfs.part goto next
FORMAT.COM H: /FS:JFS <REPLY_Y.txt
sleep 1
touch h:\jfs.part
:next
And create reply_y.txt besides startup.cmd in the root of your boot volume containing Y
This will preserve the JFS volume across reboots if you've set the ram disk to preserve its contents and your hardware allows it.

19
Programming / Re: Qt6 Development
« on: June 04, 2024, 06:29:45 am »
OK, solved it. Removed the C_INCLUDE_PATH, LIBRARY_PATH and CPLUS_INCLUDE_PATH, leaving the PATH and BEGINLIBPATH statements and qmake ../dooble.pro works.
Guess I was getting too fancy with setting up the environment

20
Programming / Re: Qt6 Development
« on: June 04, 2024, 06:11:48 am »
No, Qt5 Dooble has always morphed here, unlike Qt6 Dooble.
After converting line endings (?) and changing the drive letter, here's the diff,
Code: [Select]
--- .qmake.stash-1.txt  2024-06-03 21:03:10.000000000 -0700
+++ .qmake.stash.txt    2024-06-02 19:20:38.000000000 -0700
@@ -8,6 +8,8 @@
     QMAKE_GCC_MINOR_VERSION \
     QMAKE_GCC_PATCH_VERSION
 QMAKE_CXX.INCDIRS = \
+    L:/qt6-6.2.x/include \
+    W:/usr/include \
     W:/usr/include/c++/9 \
     W:/usr/include/c++/9/i686-pc-os2-emx \
     W:/usr/include/c++/9/backward \
@@ -23,5 +25,6 @@
 QMAKE_CXX.LIBDIRS = \
     W:/usr/lib/gcc/i686-pc-os2-emx/9 \
     W:/usr/lib/gcc \
+    L:/qt6-6.2.x/lib \
     W:/usr/lib \
     /@unixroot/usr/lib

Which brings up the question of how your environment is finding the Qt6 stuff. My qt6dev.cmd,
Code: [Select]
set QT6_ROOT=L:
set C_INCLUDE_PATH=%QT6_ROOT%/qt6-6.2.x/include;%UNIXROOT%/usr/include;%UNIXROOT/usr/local/include;%C_INCLUDE_PATH%
set CPLUS_INCLUDE_PATH=%C_INCLUDE_PATH%
set LIBRARY_PATH=%QT6_ROOT%/qt6-6.2.x/lib;%UNIXROOT%/usr/lib;%UNIXROOT/usr/local/lib;%LIBRARY_PATH%
set PATH=%QT6_ROOT%\qt6-6.2.x\bin;%PATH%
set BEGINLIBPATH=%QT6_ROOT%\qt6-6.2.x\lib;%BEGINLIBPATH%

As you can see, @unixroot is W: here and I have qt6-6.2.x installed in the root of L:

Edit: Now I see typos, dropped %. I'll fix and retest.
Edit2: No change, nothing in usr/local that matters anyways

21
Programming / Re: Qt6 Development
« on: June 03, 2024, 05:02:59 am »
weird, working for me...
Code: [Select]
{0}[u:\dev\dooble] mkdir obj

{0}[u:\dev\dooble] cd obj

{0}[u:\dev\dooble\obj] qmake ..\dooble.pro
Project MESSAGE: The QtCharts module has been discovered.

{0}[u:\dev\dooble\obj] qmake --version
QMake version 3.1
Using Qt version 6.2.8 in U:/QT6-6.2.X/lib

One change here is that with fix, Dooble now acts as a PM app, VIO window disappears until Dooble exits, rather then morphing to PM, which left the VIO window outputting mostly stderr. You should check your Dooble's stderr. lots of messages.
attaching my .qmake.stash for comparing with yours. Mine created in my Qt6 dev environment, qmake-qt5 ../dooble.pro

22
Programming / Re: Qt6 Development
« on: June 01, 2024, 08:19:42 pm »
Still the same error,
Code: [Select]
[L:\work\dooble\obj]qmake ../dooble.pro
L:/QT6-6.2.X/mkspecs/features/toolchain.prf:76: Variable QMAKE_CXX.COMPILER_MACROS is not defined.
Project ERROR: failed to parse default search paths from compiler output

23
Programming / Re: Qt6 Development
« on: June 01, 2024, 07:52:46 am »
Sorry about that, I didn't copy the file from the OS/2 box to the server. I managed to VPN I to home and it should be in place now.

Got it, will test tomorrow, 'tis late here.
Thanks

24
Programming / Re: Qt6 Development
« on: June 01, 2024, 03:36:56 am »
Not found. Tried with more recent dates, 29 and 30, still not found

25
I'd guess that the tools are fairly mature, so a downgrade wouldn't matter, but it is only a guess. Could look at the changelog at wherever Tiff is maintained.

26
Yum install libtiff-legacy-tools looks like it would install tiff2pdf, version 3.9.5-2. Might have to install after upgrading
Seems that an issue should be raised at Bitwise about the missing tools.

27
Hardware / Re: Modern Motherboards - Whats working
« on: May 25, 2024, 02:19:53 am »
The biggest problem with new computers/MB's is how much memory OS/2 sees as they're designed with 64bit OS's in mind. Lots of reports where less then 2GB's is usable on the newest
Neil's advice about Lenovo M series is good, I picked up one, about 6 years old, for C$90 (US$65-70), works great, no PS2 ports on this one but they were an option. Most (all?) are Intel though.

28
Programming / Re: Qt6 Development
« on: May 24, 2024, 07:52:49 am »
Mount U: under Ubuntu and do it? Probably have to do it as root, or do a chown first.
Maximize memory under OS/2 and try again. Maximum VIRTUALADDRESSLIMIT and don't load the WPS and minimize what else is loaded, also a small JFS cache., no HPFS or FAT32. I started running OS/2 on a 386 with 4MB's of ram. I had it tuned to run pretty good, didn't run the WPS for a long time until I upgraded to 8 MB's of ram.

I managed to get the checkout to complete using ACPI /MAXCPU=1

Good, something to remember.

29
Programming / Re: Qt6 Development
« on: May 24, 2024, 06:26:39 am »
Thanks Dave, that will give some clues.... Are you able to raise an issue in the qt6-base-os2 repo?

Ok, I think the issue is that the files in https://github.com/bitwiseworks/qtbase-os2/tree/master/mkspecs/features/os2 are missing in Qt6

I tried adding features/os2, no change. Then I tried using the whole features/ from Qt5, still no change.

30
Programming / Re: Qt6 Development
« on: May 24, 2024, 06:25:18 am »
Mount U: under Ubuntu and do it? Probably have to do it as root, or do a chown first.
Maximize memory under OS/2 and try again. Maximum VIRTUALADDRESSLIMIT and don't load the WPS and minimize what else is loaded, also a small JFS cache., no HPFS or FAT32. I started running OS/2 on a 386 with 4MB's of ram. I had it tuned to run pretty good, didn't run the WPS for a long time until I upgraded to 8 MB's of ram.

Pages: 1 [2] 3 4 ... 324