OS/2, eCS & ArcaOS - Technical > Applications

More WinOs/2 troubles

<< < (2/2)

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

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:

--- Quote from: Glenn on August 05, 2024, 06:29:54 pm ---
--- 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 ---

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...

--- End quote ---

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:

--- Quote from: Lars on August 07, 2024, 06:41:10 am ---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.

--- End quote ---
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.

Navigation

[0] Message Index

[*] Previous page