🚀 go-pugleaf

os2-l@mistik.express.net (Mustafa Soysal MS57) wrote:

>I think the win32s thing is the key, since that application
>(http://www.filmworks.com/) will also choke on the win32s.

>I am wondering if this can be solved by simply setting the path or dpath
>variables differently.  It seemed that win32s.386 could not be found.

>Seattle Filworks gave me a workaround since the windows installation
>program was refusing to set it up under WinOS2, but they didn't have
>anything further.  When I get to start the program by fiddling with
>default directories etc, I can still get the system to tell me that
>win32s was not installed properly.  Basically, the reboot part of the
>installation is missing, and it could be that the last step of the
>installation was not done.  Any hacks?

Please try to "hack" it.

I know that MS Office leaves a file called _MSSTART.BAT/EXE in the Windows
directory when it needs a "reboot" to complete.

The main problem with win32s 1.30 under OS/2 is that the memory scheme in 1.30
pushes memory past the DOS limit, breaking it under WinOS/2's virtual DOS
session.

Good luck.