OS/2, eCS & ArcaOS - Technical > Applications

More WinOs/2 troubles

(1/2) > >>

Glenn:
Hello all.. among the few other Win 3.1 programs I tried installing yesterday, to evaluate how competitive OS/2 could have been in the early 1990s for productivity apps, Mathematica (v2 I think), Matlab 4.2c, Fortran Powerstation 1, PharLap 6 (as the Matlab wanted these libraries). WinOS/2 restarted after Mathematica and Matlab installs.
Problem is: WinOS/2 does not start anymore. I removed in win.ini / system.ini the lines referring to Fortran (nothing related to PharLap in those) but still does not start.
I guess that one of those replaced more recent system libraries, but which ones ??
Any idea ?

Roderick Klein:

--- Quote from: Glenn on August 05, 2024, 08:53:03 am ---Hello all.. among the few other Win 3.1 programs I tried installing yesterday, to evaluate how competitive OS/2 could have been in the early 1990s for productivity apps, Mathematica (v2 I think), Matlab 4.2c, Fortran Powerstation 1, PharLap 6 (as the Matlab wanted these libraries). WinOS/2 restarted after Mathematica and Matlab installs.
Problem is: WinOS/2 does not start anymore. I removed in win.ini / system.ini the lines referring to Fortran (nothing related to PharLap in those) but still does not start.
I guess that one of those replaced more recent system libraries, but which ones ??
Any idea ?

--- End quote ---

On an DOS command prompt type winos2 /b /? (I forgot) or win /b. Windows can be started to created a bootlog and give you a hint what went wrong.

Roderick

Glenn:

--- Quote from: Roderick Klein on August 05, 2024, 10:13:56 am ---
--- Quote from: Glenn on August 05, 2024, 08:53:03 am ---Hello all.. among the few other Win 3.1 programs I tried installing yesterday, to evaluate how competitive OS/2 could have been in the early 1990s for productivity apps, Mathematica (v2 I think), Matlab 4.2c, Fortran Powerstation 1, PharLap 6 (as the Matlab wanted these libraries). WinOS/2 restarted after Mathematica and Matlab installs.
Problem is: WinOS/2 does not start anymore. I removed in win.ini / system.ini the lines referring to Fortran (nothing related to PharLap in those) but still does not start.
I guess that one of those replaced more recent system libraries, but which ones ??
Any idea ?

--- End quote ---

On an DOS command prompt type winos2 /b /? (I forgot) or win /b. Windows can be started to created a bootlog and give you a hint what went wrong.

Roderick

--- End quote ---

I tried win /b. I think the attached bootlog.txt is what it produced. Apart from failure to load some fonts, I do not see any specific error message.

Dave Yeo:
I learned back in my Win 3.1 days to make backups of win.ini, system.ini, config.sys and autoexec.bat files as Windows breaks so easily. Have you checked autoexec.bat? Mine,

--- Code: ---@ECHO OFF
ECHO.
PROMPT $i$p$g
REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512;F:\DELETE,512;G:\DELETE
,512;H:\DELETE,512;K:\DELETE,512;M:\DELETE,512;N:\DELETE,512;O:\DELETE,512;P:\DE
LETE,512;Q:\DELETE,512;R:\DELETE,512;S:\DELETE,512;T:\DELETE,512;W:\DELETE,512;X
:\DELETE,512;Y:\DELETE,512;Z:\DELETE,512;
SET WIN3DIR=W:\OS2\MDOS\WINOS2
PATH=W:\OS2;W:\OS2\MDOS;W:\;W:\OS2\MDOS\WINOS2;W:\sys\MDOS\BIN;W:\TCPIP\DOS\BIN;
LOADHIGH APPEND W:\OS2;W:\OS2\SYSTEM
SET TMP=W:\var\temp
LOADHIGH W:\sys\MDOS\BIN\2GBFIX.COM >NUL
LOADHIGH DOSKEY FINDFILE=DIR /A /S /B $*
DOSKEY EDIT=QBASIC/EDITOR $*
SET DIRCMD=/A
SET TEMP=W:\OS2\MDOS\WINOS2\TEMP
SET ETC=W:\TCPIP\DOS\ETC

--- End code ---

Adjust boot drive letter.

Today I would back up\os2\mdos before doing any test installs. A simple zip works.

Glenn:

--- Quote from: Dave Yeo on August 05, 2024, 04:43:30 pm ---I learned back in my Win 3.1 days to make backups of win.ini, system.ini, config.sys and autoexec.bat files as Windows breaks so easily. Have you checked autoexec.bat? Mine,

--- Code: ---@ECHO OFF
ECHO.
PROMPT $i$p$g
REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512;F:\DELETE,512;G:\DELETE
,512;H:\DELETE,512;K:\DELETE,512;M:\DELETE,512;N:\DELETE,512;O:\DELETE,512;P:\DE
LETE,512;Q:\DELETE,512;R:\DELETE,512;S:\DELETE,512;T:\DELETE,512;W:\DELETE,512;X
:\DELETE,512;Y:\DELETE,512;Z:\DELETE,512;
SET WIN3DIR=W:\OS2\MDOS\WINOS2
PATH=W:\OS2;W:\OS2\MDOS;W:\;W:\OS2\MDOS\WINOS2;W:\sys\MDOS\BIN;W:\TCPIP\DOS\BIN;
LOADHIGH APPEND W:\OS2;W:\OS2\SYSTEM
SET TMP=W:\var\temp
LOADHIGH W:\sys\MDOS\BIN\2GBFIX.COM >NUL
LOADHIGH DOSKEY FINDFILE=DIR /A /S /B $*
DOSKEY EDIT=QBASIC/EDITOR $*
SET DIRCMD=/A
SET TEMP=W:\OS2\MDOS\WINOS2\TEMP
SET ETC=W:\TCPIP\DOS\ETC

--- End code ---

Adjust boot drive letter.

Today I would back up\os2\mdos before doing any test installs. A simple zip works.

--- End quote ---

And here is mine

--- Code: ---@ECHO OFF
ECHO.
PROMPT $i$p$g
REM SET DELDIR=C:\DELETE,512;S:\DELETE,512;T:\DELETE,512;Z:\DELETE,512;
SET WIN3DIR=C:\OS2\MDOS\WINOS2
PATH=C:\OS2;C:\OS2\MDOS;C:\;C:\OS2\MDOS\WINOS2;C:\sys\MDOS\BIN;C:\TCPIP\DOS\BIN;
REM PATH D:\PHARLAP\BIN;D:\PHARLAP\CV386;
PATH=D:\IBLOCAL\BIN;%PATH%
PATH=D:\IBLOCAL\BIN;D:\COREL\OFFICE\SHARED\IDAPI;%PATH%
PATH=D:\F32\BIN;D:\BC45\BIN;%PATH%
Set LIB=D:\F32\LIB
Set INCLUDE=D:\F32\INCLUDE
LOADHIGH APPEND C:\OS2;C:\OS2\SYSTEM
SET TMP=C:\var\temp
LOADHIGH C:\sys\MDOS\BIN\2GBFIX.COM >NUL
LOADHIGH DOSKEY FINDFILE=DIR /A /S /B $*
LOADHIGH MOUSE
DOSKEY EDIT=QBASIC/EDITOR $*
SET DIRCMD=/A
SET TEMP=C:\OS2\MDOS\WINOS2\TEMP
SET ETC=C:\TCPIP\DOS\ETC
REM PATH=D:\BC45\BIN;%PATH%

--- End code ---

Navigation

[0] Message Index

[#] Next page