search

malxau / os2api

MIT License
12 stars 0 forks source link

Greetings :) No issue, but a question. #2

Open Tron-05 opened 10 months ago

Tron-05 commented 10 months ago

I enjoy OS/2 as a hobby. I am not anti-Visual Studio 1.5. However, I was wondering why you chose VS 1.5 over Visual Age for your OS/2 and DOS projects.

malxau commented 10 months ago

(I’m not allowed to log in to Github, so responding via mail – apologies if the formatting is whack.)

As far as I know, VisualAge is a 32 bit compiler. So when building for DOS and OS/2, you have to make some choices:

· What I did – 16 bit OS/2 + 16 bit DOS

· 32 bit OS/2 + a 32 bit DOS extender

· 32 bit OS/2 and a (substantially different) 16 bit DOS

Most of my tools seem like they ought to be 16 bit on DOS, and DOS seems like a bigger target than OS/2. OS/2 is for fun J What I tried to say at the top of the blog post is if I’m making a 16 bit DOS port, can I get a 16 bit OS/2 binary “for free” or close to it.

If the goal was pragmatism, there’s some other options:

· Emulate enough Win32 on OS/2 to have a 32 bit NT and 32 bit OS/2 codebase, and a (substantially different) 16 bit DOS one. This is not different in the number of codebases between a 32 bit NT + 16 bit OS/2 and DOS. The version of VisualAge I have (3.0) doesn’t support 64 bit math, DAX/DAPIE/Open32, and OS/2 doesn’t have Unicode, so there are still a lot of differences to work through. But in general OS/2’s capabilities are closer to NT than DOS, so there’s a good argument that the end result is better.

· Use OpenWatcom and build a 16 bit binary without the heroics of hacking Visual C++. Really, I need to make more use of OpenWatcom since it’s a freely available compiler that targets DOS, OS/2 and old Win32, which is what I’m trying to target. Visual C++ 1.5 is a commercial product that’s theoretically unavailable. My loyalty to Visual C++ at this point is beyond irrational.

From: Tron @.*** Sent: Thursday, January 4, 2024 4:25 PM To: malxau/os2api Cc: Subscribed Subject: [malxau/os2api] Greetings :) No issue, but a question. (Issue #2)

I enjoy OS/2 as a hobby. I am not anti-Visual Studio 1.5. However, I was wondering why you chose VS 1.5 over Visual Age for your OS/2 and DOS projects.

— Reply to this email directly, view it on GitHub https://github.com/malxau/os2api/issues/2 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AECPGSNSLS2PMFFPE6DECKTYMZYORAVCNFSM6AAAAABBMUCK52VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DKMRZGUYDCNQ . You are receiving this because you are subscribed to this thread.Image removed by sender.Message ID: @.***>

malxau commented 10 months ago

Your message also reminded me to write up about C/C++ 7.0 add-on for OS/2, which might be interesting for people who want to compile OS/2 programs on OS/2.

http://www.malsmith.net/blog/c7-os2/

Tron-05 commented 10 months ago

Greetings Malcom 🙂

Thank you for your response. You are correct, VisualAge is an OS/2 and 32 bit compiler only. I have the big boxes for VisualAge 3.0 for OS/2, VisualAge 4.0 for OS/2, and VisualAge 3.5 for Windows. I actually had to check, I couldn't remember if Visual Age for OS/2 had a 32-bit option. I have a couple of big box C/set compilers for OS/2, which are older than VisualAge 3.0 for OS/2 I have not checked those yet.

I agree with you, I have a big box of Watcom C++ and it does everything 16/32 Bit, win, OS/2, DOS etc.

Visual Studio is a great choice too. Interesting stuff 🙂

Disclosure: AI may have written the above email or contributed to the content.

Tony Hinton Professor University of Advancing Technology 2625 West Baseline Road Tempe, Arizona 85283 @.**@.>| UAT.eduhttp://uat.edu/ 480-351-7887 (office) 480-228-1860 (mobile) Connect With Us: https://business.facebook.com/UATFacebookhttps://business.facebook.com/UATedu/| https://twitter.com/UATedu?lang=en Twitterhttps://twitter.com/uatedu | Instagramhttps://www.instagram.com/uatedu/?hl=en | LinkedInhttps://www.linkedin.com/school/university-of-advancing-technology/ | UATtech.comhttp://uattech.com/ Learn. Experience. Innovate.

techrespect

From: Malcolm Smith @.> Sent: Thursday, January 4, 2024 3:52 AM To: malxau/os2api @.> Cc: Tony Hinton @.>; Author @.> Subject: Re: [malxau/os2api] Greetings :) No issue, but a question. (Issue #2)

(I’m not allowed to log in to Github, so responding via mail – apologies if the formatting is whack.)

As far as I know, VisualAge is a 32 bit compiler. So when building for DOS and OS/2, you have to make some choices:

· What I did – 16 bit OS/2 + 16 bit DOS

· 32 bit OS/2 + a 32 bit DOS extender

· 32 bit OS/2 and a (substantially different) 16 bit DOS

Most of my tools seem like they ought to be 16 bit on DOS, and DOS seems like a bigger target than OS/2. OS/2 is for fun J What I tried to say at the top of the blog post is if I’m making a 16 bit DOS port, can I get a 16 bit OS/2 binary “for free” or close to it.

If the goal was pragmatism, there’s some other options:

· Emulate enough Win32 on OS/2 to have a 32 bit NT and 32 bit OS/2 codebase, and a (substantially different) 16 bit DOS one. This is not different in the number of codebases between a 32 bit NT + 16 bit OS/2 and DOS. The version of VisualAge I have (3.0) doesn’t support 64 bit math, DAX/DAPIE/Open32, and OS/2 doesn’t have Unicode, so there are still a lot of differences to work through. But in general OS/2’s capabilities are closer to NT than DOS, so there’s a good argument that the end result is better.

· Use OpenWatcom and build a 16 bit binary without the heroics of hacking Visual C++. Really, I need to make more use of OpenWatcom since it’s a freely available compiler that targets DOS, OS/2 and old Win32, which is what I’m trying to target. Visual C++ 1.5 is a commercial product that’s theoretically unavailable. My loyalty to Visual C++ at this point is beyond irrational.

From: Tron @.*** Sent: Thursday, January 4, 2024 4:25 PM To: malxau/os2api Cc: Subscribed Subject: [malxau/os2api] Greetings :) No issue, but a question. (Issue #2)

I enjoy OS/2 as a hobby. I am not anti-Visual Studio 1.5. However, I was wondering why you chose VS 1.5 over Visual Age for your OS/2 and DOS projects.

— Reply to this email directly, view it on GitHub https://github.com/malxau/os2api/issues/2 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AECPGSNSLS2PMFFPE6DECKTYMZYORAVCNFSM6AAAAABBMUCK52VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DKMRZGUYDCNQ . You are receiving this because you are subscribed to this thread.Image removed by sender.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/malxau/os2api/issues/2#issuecomment-1876893401, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGPKK4XLC4CL3PTV4D57KBLYM2CXFAVCNFSM6AAAAABBMUCK52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZWHA4TGNBQGE. You are receiving this because you authored the thread.Message ID: @.***>

Tron-05 commented 10 months ago

That would be an awesome read! I have been looking for a big box version of C/C++ 7.0 but have not found one yet. I may have it on some old and early MSDN disks. That would be a great version to mess around with!

Disclosure: AI may have written the above email or contributed to the content.

Tony Hinton Professor University of Advancing Technology 2625 West Baseline Road Tempe, Arizona 85283 @.**@.>| UAT.eduhttp://uat.edu/ 480-351-7887 (office) 480-228-1860 (mobile) Connect With Us: https://business.facebook.com/UATFacebookhttps://business.facebook.com/UATedu/| https://twitter.com/UATedu?lang=en Twitterhttps://twitter.com/uatedu | Instagramhttps://www.instagram.com/uatedu/?hl=en | LinkedInhttps://www.linkedin.com/school/university-of-advancing-technology/ | UATtech.comhttp://uattech.com/ Learn. Experience. Innovate.

techrespect

From: Malcolm Smith @.> Sent: Friday, January 5, 2024 10:02 PM To: malxau/os2api @.> Cc: Tony Hinton @.>; Author @.> Subject: Re: [malxau/os2api] Greetings :) No issue, but a question. (Issue #2)

Your message also reminded me to write up about C/C++ 7.0 add-on for OS/2, which might be interesting for people who want to compile OS/2 programs on OS/2.

http://www.malsmith.net/blog/c7-os2/

— Reply to this email directly, view it on GitHubhttps://github.com/malxau/os2api/issues/2#issuecomment-1879551724, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGPKK4UDED6CVDPL2J3C4ZLYNDLFZAVCNFSM6AAAAABBMUCK52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZGU2TCNZSGQ. You are receiving this because you authored the thread.Message ID: @.***>

Tron-05 commented 9 months ago

Greetings :)

New topic: working on an issue for no reason except it bugs my ADHD. OS/2 Warp 4.52 and ArcaOS 5.06 had the same result under the virtual box. The theme sounds when you open and close a window in OS/2 work, but they cut themselves short like 1/10th. Go into Win OS/2 and there is no problem there, the sounds are fine.

Lots of experimenting. Using SB16 default drivers and settings. The Midi OS/2 sounds do not work at all. However, if you try to play a Midi file in OS/2, the Midi is silent, but after that, the desktop theme sounds to play okay in OS/2 and does not cut itself off early.

Any advice? I am thinking drivers? Cheers mate!