Author Topic: Dooble releases-Qt6  (Read 101742 times)

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5417
  • Karma: +129/-1
    • View Profile
Re: Dooble releases-Qt6
« Reply #195 on: April 07, 2025, 11:17:03 pm »
Latest fixes from upstream, mostly NLS related, see release notes. ftp://dry@ftp.os2voice.org/tmp/dooble-2025-04-07-Qt6.zip

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5417
  • Karma: +129/-1
    • View Profile
Re: Dooble releases-Qt6
« Reply #196 on: June 06, 2025, 05:10:05 am »
ftp://dry@ftp.os2voice.org/tmp/dooble-2025-06-01-Qt6.zip
See release notes for latest fixes etc. All changes from upstream.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 5301
  • Karma: +44/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: Dooble releases-Qt6
« Reply #197 on: June 06, 2025, 04:56:04 pm »
Hello Dave

I get this message, but I have Qt 6.8.1.
Quote
------------------------------------------------------------

06-06-2025  09:54:00  SYS2070  PID 01b3  TID 0001  Slot 008e
C:\QT6\APPS\DOOBLE\DOOBLE.EXE
QT6GUI->GCC1.___truncsfhf2
127

Is something that I'm missing?

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5417
  • Karma: +129/-1
    • View Profile
Re: Dooble releases-Qt6
« Reply #198 on: June 06, 2025, 05:07:00 pm »
Looks like Paul used his latest GCC to build qtgui so you need gcc1.dll from that. Attached.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 5301
  • Karma: +44/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: Dooble releases-Qt6
« Reply #199 on: June 06, 2025, 06:21:08 pm »
Thanks Dave. I don't know why but it is had been hard to all the stuff for me lately.

I'm getting this error. I guess it is because Qt 6.8.1 does not has webengine, right?

Quote
------------------------------------------------------------

------------------------------------------------------------

06-06-2025  11:17:58  SYS2070  PID 0045  TID 0001  Slot 001d
C:\QT6\APPS\DOOBLE\DOOBLE.EXE
QT6WEBEN->QMLPLUGN.__ZN8QJSValueC1ERKS_
127

Do you I have to go back to a lower version of Qt6 with webengine?

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5417
  • Karma: +129/-1
    • View Profile
Re: Dooble releases-Qt6
« Reply #200 on: June 06, 2025, 06:31:29 pm »
Thanks Dave. I don't know why but it is had been hard to all the stuff for me lately.

I'm getting this error. I guess it is because Qt 6.8.1 does not has webengine, right?

Quote
------------------------------------------------------------

------------------------------------------------------------

06-06-2025  11:17:58  SYS2070  PID 0045  TID 0001  Slot 001d
C:\QT6\APPS\DOOBLE\DOOBLE.EXE
QT6WEBEN->QMLPLUGN.__ZN8QJSValueC1ERKS_
127

Do you I have to go back to a lower version of Qt6 with webengine?

Regards

It looks like it. I also have lost track of Qt6 versions. Dooble's About reports I'm using Qt6 6.2.12 which is what I linked it to. Not sure what the newest version that would work.

David McKenna

  • Hero Member
  • *****
  • Posts: 892
  • Karma: +32/-0
    • View Profile
Re: Dooble releases-Qt6
« Reply #201 on: June 06, 2025, 11:15:41 pm »
 I was never able to get the 6.2.6 webengine working with QT 6.8. QT 6.6 was the most recent one it worked on. Probably best to just stick to 6.2 for now...

Regards,

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2533
  • Karma: +195/-0
    • View Profile
Re: Dooble releases-Qt6
« Reply #202 on: June 06, 2025, 11:40:18 pm »
There was some upstream restructuring of DLL's in 6.8.x....

Neil Waldhauer

  • Hero Member
  • *****
  • Posts: 1126
  • Karma: +30/-0
    • View Profile
    • Blonde Guy
Re: Dooble releases-Qt6
« Reply #203 on: Today at 01:30:54 am »
I'm trying dooble-QT6 on a new computer.

Code: [Select]
SYS0008: There is not enough memory available to process this command.
All available memory is in use. "QT6WEBEN"

This is the output of mem /v

Code: [Select]
Total physical memory:     15,998 MB
Accessible to system:       1,670 MB
Additional (PAE) memory:   14,328 MB

Resident memory:              148 MB
Available virtual memory:   1,424 MB

Available process memory:
  Private low memory:         337 MB
  Private high memory:      1,344 MB
  Shared low memory:          258 MB
  Shared high memory:       1,267 MB

I'm using VIRTUALADDRESSLIMIT=2560
I marked every DLL to load code into high memory -- most were already so marked.

I think for some new machines, dooble-QT6 will be out of reach...
Expert consulting for ArcaOS, OS/2 and eComStation
http://www.blondeguy.com

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2533
  • Karma: +195/-0
    • View Profile
Re: Dooble releases-Qt6
« Reply #204 on: Today at 01:48:02 am »
I'm using VIRTUALADDRESSLIMIT=2560
I marked every DLL to load code into high memory -- most were already so marked.

I think for some new machines, dooble-QT6 will be out of reach...

Yeah quite possibly. Even with the full 4gb, it's a challenge - with less than this visible to OS/2 - we're pretty much screwed.

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5417
  • Karma: +129/-1
    • View Profile
Re: Dooble releases-Qt6
« Reply #205 on: Today at 03:08:55 am »
It's interesting. Here, before loading Dooble-Qt6,
Code: [Select]
Available process memory:
  Private low memory:         306 MB
  Private high memory:      2,128 MB
  Shared low memory:          223 MB
  Shared high memory:         343 MB
After loading it, nothing displayed except about:blank
Code: [Select]
Available process memory:
  Private low memory:         306 MB
  Private high memory:      1,956 MB
  Shared low memory:          220 MB
  Shared high memory:          99 MB

SeaMonkey is using most of my 3.5GB of visible ram and virtualaddresslimit is set to 2944. 3072 causes the system to get unstable.


Steven Levine

  • Jr. Member
  • **
  • Posts: 82
  • Karma: +12/-0
    • View Profile
Re: Dooble releases-Qt6
« Reply #206 on: Today at 09:35:53 am »
Neil,

I recommend you verify your VIRTUALADDRESSLIMIT setting.  Your mem /v output:

 Available virtual memory:   1,424 MB

looks to me like I would expect it to appear for VAL 1536.