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] 5 6 ... 322
46
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.

47
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.

48
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.

49
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.

50
Programming / Re: new gcc toolchain
« on: March 15, 2024, 02:20:56 am »
Can you zip or 7z pdos.vhd and post it here? Seems an empty vhd should compress very well.

51
Programming / Re: fatal error: sys/cdefs.h: No such file or directory
« on: March 12, 2024, 02:10:30 am »
Do you know which package is needed to add the missing header files? This is the gcc from netlabs-rel (9.2.0-4.oc00)
Thank you!

libc-devel has most of the headers, libcx-devel also has a few.
There really should be a meta package, easy to forget things like the linker (watcom-wlink-hll)
Edit: You should use ash rather then bash as well. The bash port is incomplete.

52
Programming / Re: DosDevIOCtl disabling keyboard in VIO mode
« on: March 10, 2024, 07:43:17 am »
Good point about NE vs LX. Wonder when LX was first used on OS/2. Actually I think it was LE before LX.

53
Programming / Re: DosDevIOCtl disabling keyboard in VIO mode
« on: March 10, 2024, 04:15:27 am »
Running lxlite on the exe gives,
Code: [Select]
H:\tmp>lxlite uemacs.exe
┌[ lxLite ]───────────────────────────────────┬[ Version 1.3.9 ]┐
├ Copyright 1996,97 by FRIENDS software       ├    All rights   ┤
├ Copyright 2001,03 by Max Alekseyev          ├     reserved    ┤
├ Copyright 2008-10 by OS/4 team              ├                 ┤
├ Copyright 2011    by Steven H. Levine       ├                 ┤
├ Copyright 2017-23 by bww bitwise works GmbH └─────────────────┘
├ The file uemacs.exe contains 1 bytes out of module structure
├                  uemacs.exe initial: 72863 final: 42821 gain: 41.3%
├┤Total gain: 30042 bytes
Am I interpreting that correctly that there is 1 rogue byte somewhere?

That's my interpretation.

Quote

Quote
Hmm, your exe won't run after lxliting,
Maybe it doesn't like the non-standard virtual addresses. I am attaching one with the normal 0x10000 - can you see if that is ok?

Yes, this one worked after lxliting.

Quote
Quote
If you can find an old enough exehdr, perhaps the OS/2 v1.3 toolkit, it should run under Win2k as Win2k does support 16 bit OS/2 code
That would only operate on 16-bit NE executables, not 32-bit LX executables introduced with OS/2 2.0, right?

Yes, OS/2 1.x text code runs out of the box. Used to be a Presentation Manager kit to run 1.x graphics as well.

54
Programming / Re: DosDevIOCtl disabling keyboard in VIO mode
« on: March 10, 2024, 01:02:15 am »
Running lxlite on the exe gives,
Code: [Select]
H:\tmp>lxlite uemacs.exe
┌[ lxLite ]───────────────────────────────────┬[ Version 1.3.9 ]┐
├ Copyright 1996,97 by FRIENDS software       ├    All rights   ┤
├ Copyright 2001,03 by Max Alekseyev          ├     reserved    ┤
├ Copyright 2008-10 by OS/4 team              ├                 ┤
├ Copyright 2011    by Steven H. Levine       ├                 ┤
├ Copyright 2017-23 by bww bitwise works GmbH └─────────────────┘
├ The file uemacs.exe contains 1 bytes out of module structure
├                  uemacs.exe initial: 72863 final: 42821 gain: 41.3%
├┤Total gain: 30042 bytes

After lxliting with the defaults, the exe will only run on Warp v3 or later. The IBM linkers can also pack the data, code etc.
Hmm, your exe won't run after lxliting,
Code: [Select]
03-09-2024  15:59:13  SYS3175  PID 0085  TID 0001  Slot 00b7
H:\TMP\UEMACS.EXE
c0000005
0001d6a1
P1=00000001  P2=0040fd6c  P3=XXXXXXXX  P4=XXXXXXXX
EAX=00000000  EBX=00000000  ECX=00000000  EDX=00000000
ESI=00000000  EDI=00000000
DS=0053  DSACC=d0f3  DSLIM=bfffffff
ES=0053  ESACC=d0f3  ESLIM=bfffffff
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:0001d6a1  CSACC=d0df  CSLIM=bfffffff
SS:ESP=0053:00047f58  SSACC=d0f3  SSLIM=bfffffff
EBP=00047fd0  FLG=00010212

UEMACS.EXE 0001:0000d6a1

If you can find an old enough exehdr, perhaps the OS/2 v1.3 toolkit, it should run under Win2k as Win2k does support 16 bit OS/2 code

55
Programming / Re: DosDevIOCtl disabling keyboard in VIO mode
« on: March 09, 2024, 04:07:35 pm »
For now perhaps best to use exehdr to mark it to force full screen mode, especially if it still breaks the keyboard if run in a window.
Code: [Select]
exehdr /PMTYPE:NOTWINDOWCOMPAT uemacs.exeSeems to run fine here, though I don't know emacs enough to really test. Good work.

56
Programming / Re: DosDevIOCtl disabling keyboard in VIO mode
« on: March 08, 2024, 10:50:19 pm »
Try help 188,
Code: [Select]
[H:\tmp]pdptest
SYS0188: The operating system cannot run H:\TMP\PDPTEST.EXE.

[H:\tmp]help 188

SYS0188: The operating system cannot run ***.

EXPLANATION: The application program does not have a correct
END <label> directive.

ACTION: Contact the supplier of the application.

Not sure what an END directive is.

57
Programming / Re: DosDevIOCtl disabling keyboard in VIO mode
« on: March 07, 2024, 01:03:16 am »
Tried lxlite, a program originally for compressing lx files, extended quite a bit. It reports error reading executable.
yum install lxlite
lxlite /?

58
Programming / Re: DosDevIOCtl disabling keyboard in VIO mode
« on: March 07, 2024, 01:01:33 am »
In a DOS window,
Code: [Select]
H:\TMP>pdptest
SYS3011: The .EXE file that starts the program you specified contains
an error.

59
General Discussion / Article on the MS OS/2 2.0 preview at OS2Museum
« on: March 06, 2024, 05:11:35 am »
Michal got hold of the preview edition of MS OS/2 2.0 plus SDK and wrote an interesting article,
http://www.os2museum.com/wp/the-future-that-never-was/

60
Storage / Re: How to properly setup a working FAT32 USB stick?
« on: March 06, 2024, 02:48:10 am »
You can use LVM or miniLVM to give a preferred drive letter or *. The * means first available drive letter and I think is the default with removable drives. The preferred letter only gets assigned if nothing else hasn't already grabbed the letter.

Pages: 1 2 3 [4] 5 6 ... 322