🚀 go-pugleaf

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


I have managed to get PhotoWorks to run under Warp for Windows (3.0).
Here is the method I used.

Installation of PhotoWorks:

(1) Load Win-OS/2 as usual.
(2) Rename "winos2.com" to "winos2.tmp" while Win-OS/2 is running.  This
    file is in the \windows directory.
(3) Install the Photoworks software.
(4) Restore "winos2.com" by renaming "winos2.tmp" back to "winos2.com."

Running PhotoWorks:

Now, chances are, the program will not run correctly.  This is because
Win32s 1.25 (which is installed along with Photoworks during the 
Photoworks installation) won't run under OS/2 as is.  OS/2 uses the 
file "vw32s.sys" in the \os2\mdos directory to allow Win32s to run.  
But, the version with OS/2 doesn't work with Win32s 1.25.  I was able 
to find a new version of "vw32s.sys" at ftp-os2.nmsu.edu in the 
windows directory. I followed the installation instructions, learning 
that the actual version of Win32s is 1.25b.  This is important 
because the DEVICE= line in the OS/2 "config.sys" file needs this 
information.  This is explained in the documentation that comes 
with the new "vw32s.sys" file.

After doing the above and then installing the fix, I was able to get
Photoworks to run properly.  I hope this information is somewhat useful
to you.

-- 
Chris Lanciani
lanciani@ee.gatech.edu