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 ... 320
1
Programming / Re: Xpdf v. 4.01
« on: March 28, 2024, 03:18:56 pm »
Tried building Dooble,
Code: [Select]
[K:\work\dooble-dry\build]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

2
Programming / Re: Xpdf v. 4.01
« on: March 28, 2024, 06:34:25 am »
Hey Dave,

At some point could you get a devel package of Qt6 together?

Not sure what's missing here - the current zips include all headers/libs. If you mean an RPM -  I have no time/inclination to put one together - I have little enough free time as it is.

I thought that some of the libs were missing. Perhaps it is plugins where the import libs are missing.

3
Programming / Re: Start program from VX-Rexx
« on: March 28, 2024, 03:46:49 am »
Thanks to Dave Yeo, who built version 4.01, the new pdftotext now works from VX-Rexx as well.

Actually 4.05, the latest. Good that it works for you.

4
Programming / Re: Xpdf v. 4.01
« on: March 27, 2024, 10:57:32 pm »
Here's the full release version including the crashing xpdf.exe. 7z sure compresses this better, almost 80% improvement. Built with no patches, just the cmake arguments I posted to Paul.

5
Programming / Re: Xpdf v. 4.01
« on: March 27, 2024, 10:00:19 pm »
Yes, as long as the correct qmake is in front of the PATH.
At some point could you get a devel package of Qt6 together?
Edit: My cmake line, run from build
Code: [Select]
cmake -DXPDFWIDGET_PRINTING=OFF -DCMAKE_BUILD_TYPE=Release ..

6
Programming / Re: Xpdf v. 4.01
« on: March 27, 2024, 09:23:12 pm »
Built xdpf.exe by disabling printing like Windows does. Unluckily it crashes with a sigsegv in qt5core.dll

7
Programming / Re: Xpdf v. 4.01
« on: March 27, 2024, 08:54:46 pm »
Tried building 4.05, seems we are missing some printer support. Linking xpdf.exe is missing,
Code: [Select]
W:\usr\local\src\xpdf-4.05\build> __Z8printPDFP6PDFDocP8QPrinteriiP10XpdfWidget
printPDF(PDFDoc*, QPrinter*, int, int, XpdfWidget*)

I'll examine more. Here's the command line tools that did build.
Edit, removed the command line tools in favour of the ones posted down the page.

8
Programming / Re: REXX IDE recommendations?
« on: March 25, 2024, 11:35:18 pm »
There's eFTE2, both PM and cmd line versions. Folding editor, does Rexx syntax highlighting, has menu for adding various Rexx commands, only when a Rexx file is loaded. No error highlighting while editing.
https://trac.netlabs.org/efte

9
Programming / Re: How does AVIO works?
« on: March 24, 2024, 08:46:01 pm »
You could try borrowing it from https://openlibrary.org/books/OL21931986M/Programming_the_OS_2_presentation_manager. I didn't feel like registering.

10
Programming / Re: How does AVIO works?
« on: March 24, 2024, 06:26:14 pm »
Was just reading an article of the new OS/2 v2, https://books.google.ca/books?id=cSMUxSP5pKgC&lpg=PP1&pg=PT433&redir_esc=y#v=onepage&q&f=false where Charles talks about the advanced VIO stuff not having 32 bit functions in the interest of future portability. He references stuff he has written to do what you are describing I think, in his book, https://ecsoft2.org/docs/os2-presentation-manager-programming-charles-petzold. Probably worth a look.
Edit: Archive.com doesn't allow downloading it, so another source would be needed.

12
General Discussion / Re: MS os/2 2.0 kernel
« on: March 22, 2024, 04:58:23 am »
My understanding is that it is the kernel that evolved into the current kernel. IBM likely modified it quite a bit and MS may have had functions in it that were removed. Trapping int0x21 calls is one possibility as MS was planning on supporting Win16 apps similar to NT's WOW, with WLO so they would have run more native then IBM's solution.
The compiler etc probably aren't very useful, LX binaries weren't even supported, and they were beta quality. Though IBM may have used the cl386 compiler for the kernel.
You could always ask on http://www.os2museum.com/wp/the-future-that-never-was/, Michal is pretty knowledgeable and usually answers comments. It is where much of my incomplete knowledge comes from.

13
Programming / Re: new gcc toolchain
« on: March 17, 2024, 08:47:25 am »
I switched from FAT32 to FAT16 in order to test that, and managed to crash ArcaOS 5.0.8 attempting to add the attached volume. I will report it via the official channels.

Did you change the partition type?
Edit: seems it is 06, so yes.
DFsee sees has this,
Code: [Select]
DFS partition  Id : 21  disk nr : 17  = FixedDisk Diskgeo = CHS:    957  16  63
 System Indicator : 0x06       = FAT16         UNIX devicename: /dev/Ida1     
 FileSyst. format : FAT16                     Windows BOOT.INI: Partition(1)   
 Partition   type : Primary    Visible        Bootrec-OEM-name: MSWIN4.1       
 Partition   size : 0x000E9091 =   466.1 MiB  =    946.938 cylinders           
FAT entry size of : 16  Bits   (FAT16   ) will be forced.                     
Size of FAT entry : 16  Bits    FAT label in Root : PDOS                       
FAT DIRTY status  : 0x00 = CLEAN                                               
FAT1 CRC-32 value : 0x861c6346  FAT2 CRC-32 value : 0x861c6346 = OK           
The FAT entry size seems weird.

14
Programming / Re: new gcc toolchain
« on: March 15, 2024, 11:25:00 pm »
Not much. Help lvm for the command line parameters, addendum.inf (toolkit) has the ioctl programming.
DFsee is available at https://dfsee.com, Jan the author, is pretty knowledgeable, I believe there is a mailing list.

15
Programming / Re: new gcc toolchain
« on: March 15, 2024, 03:43:15 am »
DFSee has this warning,
Code: [Select]
│Warning: The GEO Head/Sectors fields 16/63 in the bootsector         
│         do NOT match the current disk geometry values 14/63!       
│This may prevent using the partition from some operating systems like
│OS/2, eCS or windows that check this for consistency. The most likely
│cause for this is MOVING or CLONING the partition between different 
│primary locations, or between a primary and logical location. Use the
│FIXPBR command or 'Fix HiddenSectors/Geo value' menu to correct this.

I ran "Fix HiddenSectors/Geo value" on the vhd and attaching it.

Pages: [1] 2 3 ... 320