I use warp 3 without built-in win-os/2, which of course is rather different, as I believe warp 4 always has it built in. Maybe the answer to your problem though is that, at least in warp 3, win-os/2 support is installed not through system in the main configuration folder, but rather with selective installation. It should bring up a first screen with basic hardware settings, click ok and another screen should appear with options for win-os/2 and other things. Incidentally, I`ve found that trying to start a win-os/2 session (albeit with real win-311) can crash os/2 if win-os/2 is installed after the latest (warp 3) fixpak is applied. If win-os/2 is installed beforehand, or the fixpak temporarily backed out of, and the fixpak then (re)applied, it works fine, dont ask me why. Hope that helps.
|