More WinOs/2 troubles

[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]

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 ?

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]

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 ?

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

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: [Select]

@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

Adjust boot drive letter.

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

[Glenn]

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: [Select]

@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

Adjust boot drive letter.

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

And here is mine

Code: [Select]

@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%


[Glenn]

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: [Select]

@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

Adjust boot drive letter.

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

Dave, thank you, you pointed me into the right direction. After commenting out the extra PATH statements, WinOS/2 started again. If you look at my autoexec, the programs installed their addition to the path as being in front of the other ones. I put all the additional path statements after the other ones, and it started again. So, some executable sharing its name with a WinOS/2 one, I suppose.

The only remaining problem now is that message (from Borland C++, see screenshot) even though the said line is in my system.ini...

[Roderick Klein]

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: [Select]

@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

Adjust boot drive letter.

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

Dave, thank you, you pointed me into the right direction. After commenting out the extra PATH statements, WinOS/2 started again. If you look at my autoexec, the programs installed their addition to the path as being in front of the other ones. I put all the additional path statements after the other ones, and it started again. So, some executable sharing its name with a WinOS/2 one, I suppose.

The only remaining problem now is that message (from Borland C++, see screenshot) even though the said line is in my system.ini...

That is digging deep in memory. I seem to recall WIN/OS2 can not load a .386 driver.
But I might be wrong.

Best regards,

Roderick Klein

[Lars]

I think, .VXD drivers cannot be loaded but .386 should do (maybe that also depends how the driver mucks with the OS. I am fairly sure the BC debugger uses that .386 driver to hook into the Windows kernel). But you will need to start Windows in extended mode. I forgot how to do that in OS/2 but I think you can configure that via the DOS/WIN settings for your Win31 object.

[Glenn]

I think, .VXD drivers cannot be loaded but .386 should do (maybe that also depends how the driver mucks with the OS. I am fairly sure the BC debugger uses that .386 driver to hook into the Windows kernel). But you will need to start Windows in extended mode. I forgot how to do that in OS/2 but I think you can configure that via the DOS/WIN settings for your Win31 object.

What is "extended" mode? There is "enhanced" mode, but this is already the default..

[Lars]

I meant to say enhanced mode. If that does not work: too bad.