#Calmira update
Copyright (C) 1997-1998 Li-Hsin Huang.Ĭalmira II 3.02 update is a runner-up to the upcoming 3.1 release of Calmira (interim release). It's a fully integrated environment for managing your files and programs, and is designed to run smoothly on 386 and 486 computers. Calmira is a Windows 95 user interface for Windows 3.1. Copyright (C) 1997-1998 Li-Hsin Huang.Ĭalmira shell for Microsoft® Windows(TM) 3.1, Source Release 2.2. LinkĬalmira shell for Microsoft® Windows(TM) 3.1, Source Release 2.0. Unzip this file with "Use folder names" option enabled.
#Calmira zip file
LinkĬalmira II v3.3 as ZIP file in case you don't like installers. Copy the downloaded files to your Win-OS/2 directory and change the shell= statement in system.ini to calmira.exe. Win9x look and feel shell for Win 3.1 works well with Win-OS/2 Full Screen sessions. LinkĬalmira v3.0 - free Win'95-style shell for Win-OS2Ĭalmira II 3.2 Release. See the Source page for details about the source code. Licensed under the GNU Public License (GPL). Source code for Calmira II v3.3, requires Delphi 1.0 (16-bit). Calmira 3.3 must be installed before installing this update. See the Bugs page for details on fixed bugs. This is a bugfix release to address the most nagging bugs in earlier releases. This source is licensed under the GNU Public License (GPL).
You must have Delphi 1.0 (16-bit) to compile this source. You must have Calmira II 3.2 installed before installing this update. This is an interim update for Calmira II 3.2.
#Calmira install
Otherwise, the installer will install the default INI files. To preserve your old settings, answer No.
When upgrading from an older version of Calmira, you will be asked if you want to overwrite CALMIRA.INI and START.INI. Built using a customized version of Jordan Russell's Inno Setup. Install Calmira II v3.3 from scratch, or to update any older version of Calmira. Full Calmira II v3.3 release as a fully automated installer. LinkĬalmira II v3.3 with NEW installer. The simple way to kill this session (if it hangs or crashes) is to make an object for KILLPID.EXE (from FM/2 Utilities - below) with the name of All3d in the parameter box and Windows support is killed.
Haven't you ever had Win-OS/2 hang a zombie thread when you exit a seamless Windows program? This way whatever was hanging is irrelavant since the Windows support is still running. I figured since I already had All3D running I'd go ahead and have some Windows toolbar running to avoid PROGMAN. Root | Home Hobbes | UnixOS2 | OS2Ports | VOICE | OS/2 World | News and RumorsĬan correct low memory warnings in Windows and Dosĭialog Enhancer '99, Updates all the old WIN-OS/2ĪPISPY v1.1 - A tool for searching some functions which are used in a WIN-OS/2 session.ĪTM v3 fix for multiple WIN-OS/2 sessionsīuttonGo - This is what I have running in my desktop capture with the title bar description Windows - Programs. OS/2 Site - OS/2 software and information.
0 kommentar(er)
