OS/2 Warp 4 problem with compilation. lazarus / 68-Other OS ---------------------------------------------------------------------- mika · 2025-12-11 11:06 OS/2 Warp 4 with FixPack 15 have problem with compilation while assembling.  Assembler return code is -1, but running same assembler on same *.s file from command line it works just fine. Any ideas how to solve issue? I use official release instantiation of fpc 3.2.2 for OS/2. Wanted to have some fun with retro computing got stuck. ---------------------------------------------------------------------- Thaddy · 2025-12-11 12:35 Well, - and I know that might not be very helpful - the compiler has an option to just generate the .s files and no binaries. As you wrote that the .s files compile, you just found your workaround.  It may be just a case of adapting a linker script. At least you should be able to prevent generation of binaries and then compile the .s files. I am not familiar with the default warp linker, but it can also be a case of the proper -k option to pass to the linker. ---------------------------------------------------------------------- PascalDragon · 2025-12-12 19:30 Quote from: mika on December 11, 2025, 12:06:05 pmOS/2 Warp 4 with FixPack 15 have problem with compilation while assembling.  Assembler return code is -1, but running same assembler on same *.s file from command line it works just fine. Any ideas how to solve issue? I use official release instantiation of fpc 3.2.2 for OS/2. Wanted to have some fun with retro computing got stuck. If you compile with -sh and execute the resulting ppas.bat does that work? If not, can you fiddle around with the script to find out what the difference might be? ---------------------------------------------------------------------- mika · 2026-01-03 19:54 Quote from: PascalDragon on December 12, 2025, 08:30:23 pmIf you compile with -sh and execute the resulting ppas.bat does that work? If not, can you fiddle around with the script to find out what the difference might be? ppas.bat does work without changes. There is this OS/2 console in full screen and OS/2 console in window.  Oddly, but fpc in console in window works, but in full screen does not. As I found that dos.Exec function is failing with Dos error 206 within full screen mode. ---------------------------------------------------------------------- d2010 · 2026-01-04 23:16 Quote from: mika on December 11, 2025, 12:06:05 pmOS/2 Warp 4 with FixPack 15 have problem with compilation while assembling.  Wanted to have some fun with retro computing got stuck. Please, please how to downloading Os/2 live Os ?. I need operating system Os/2 running into my win8 x32.,, I do not have Os/2 or Deskview Os/2,, ---------------------------------------------------------------------- mika · 2026-01-06 09:59 Quote from: d2010 on January 05, 2026, 12:16:33 amPlease, please how to downloading Os/2 live Os ?. I need operating system Os/2 running into my win8 x32.,, I do not have Os/2 or Deskview Os/2,, Search "OS/2 Warp download". Maybe? There is no "live" iso or something like that. OS/2 is a legacy. Installation is a handful thou. If you gonna install on real hardware you will need working floppy disks (three of them). ---------------------------------------------------------------------- finchley · 2026-01-06 11:00 For what it's worth:  https://winworldpc.com/product/os-2-warp-4/os-2-warp-452 No idea if it works. Just searching the web... ---------------------------------------------------------------------- Thaddy · 2026-01-06 13:31 Yes, that will work. If it is legal is a different matter. BTW: Under windows 10/11, you can mount the "floppies" binaries by just right clicking from the explorer and choose mount. It will show up as a mounted floppy. Change to it and run. (mount all 3 floppies)