🚀 go-pugleaf

Da habe ich auch was!!!!

Article: 20378 of bit.listserv.os2-l
Path: rz.uni-karlsruhe.de!news.uni-ulm.de!news.belwue.de!news.dfn.de!Germany.EU.net!EU.net!howland.reston.ans.net!cs.utexas.edu!natinst.com!news.dell.com!paladin.american.edu!auvm!ACS.RYERSON.CA!j2ngo
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.os2-l
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-ID: <Pine.3.89.9410310157.B37764-0100000@turing.acs.ryerson.ca>
Date: Mon, 31 Oct 1994 01:18:06 -0500
Sender: IBM OS/2 Unedited Discussion List <OS2-L@HEARN.BITNET>
From: Jonathan Vincent Ng <j2ngo@ACS.RYERSON.CA>
Subject: Running WinOS2 in WARP
Lines: 118

    Since the announcement of OS/2 Warp 3 (and before that) people have
been asking about running their WinOS2 old in the new WARP 3 (without
WinOS2) either because they do not wish to pay MS (yet again) for another
Windows license, or they can't wait for Warp w/WinOS2 to come out, or
basically can't use Warp 3 because they have all HPFS and do not wish to
reformat (no available FAT partition to install Windows and
backup/restore to HPFS).

People often ask why can't I just use my WinOS2 code from OS/2 v2.1?
Well, as you may or may not know, there are quite a few people who have
attempted this with varying degrees of success.  The posting below is a
method that works, and it seems to be the most complete and to the point
that I've seen.  You understand that the following setup is not
officially supported by IBM (nor will IBM stop you from doing this).
If you are interested you might want to give the following a try, at your
own risk of course.

^L

=========================================================================
   Date: 10-21-94  17:03                Message #: 1979            Sol3
   From: Jerry McBride                  Status: PUBLIC
     To: All                            Ref #: 0
Subject: WINOS2 in WARPII               Conf: Os2 (6)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Hello All!

I'll make this short and followup if anyone needs the extra "meat"...

For starts, I am a registered user of both OS2 2.1 and the
Warp II beta. Yes, Warp II beta is expired, but I continue
to run it until I get my copy of 3.0... anyday now :')

Anyway, as an experiment, I installed WINOS2 from Os/2 2.1 onto my WARP
II
system. It appears to work, just fine. I haven't the time,
at this moment, to run enough windows software or to polish
off my winos2 install, but I don't see any problems to stop
others from doing the same.

My system is a vga equiped, 386 with Warp installed on
drive C: and here's how I did it.

Create the following directory path on your os2 partition
if it does not already exist: os2/mdos/winos2/system

From a Warp II os2 prompt, insert the following disks from
your 2.1 package and execute the unpack commands.

#6  - unpack a:winenv
#7  - unpack a:winini
#8  - unpack a:winreadm
#9  - unpack a:winaccess
    - unpack a:winenv
    - unpack a:wintouch
#10 - unpack a:winver
#11 - unpack a:winscrsv
#12 - unpack a:winenv
#16 - unpack a:winenv
    - unpack a:winsound

From display disk #1, unpack a:winvga

This will uncompress the winos2 files into the correct
directories. Now, move to your winos2 dir and edit the
program.ini and system.ini to change all occurances of xga
(the default winos2 video format) to vga. Also edit
mouse.ini to see if it is setup correctly.

Now go to your root directory and edit your config.sys and
add c:\os2\mdos\winos2\system; to the LIBPATH line,
c:\os2\mdos\winos2; to the PATH line and
c:\os2\mdos\winos2\system; to the DPATH line. At the end of
the config.sys add these two device lines:

DEVICE=C:\OS2\MDOS\VWIN.SYS
DEVICE=C:\OS2\MDOS\VW32S.SYS

Exit your editor.

Now, check and be sure that vwin.sys and vw32s.sys is in
your os2\mdos directory. If not, get them from your warp
install disks/rom.

Boot your computer. From an os2 prompt you should be able
to enter: win and have the winos2 desktop come up, ready to
run windows software. If there is a problem, it should
display the error and enough information to figure out what
to do. You guys/gals with "nice" hardware, are "by
yourselves" with this... sorry...

Now, don't flame me if you run into trouble or if you can
get certain windows functions to work. This is as far as I
have gotten in this expirement. The few windows apps that I
had time to play with, seem to work just fine. including
amipro 3.0.

A warning for the curious. On disk #14 of the OS/2 2.1 package is a
compressed file named: winbase. Do not unpack this file as
it WILL overwrite a few of your Warp .dlls. You don't need
any of these anyway as they already exist in Warp. For the
real curious, the files in the winbase bundle are:
pmdde.dll, winprf.dll, pmclip.dll, vwin.sys, wincfg.dll,
pmcontrol.inf and wcfg.dll.

Let me know how you all make out. If you reconfig your
winos2 for different video, mouse or sound, let me know how
well it works and if you had any special problems.

Thanks,
    Jerry
--- timEd/2 1.00+
 * Origin: MoDem_Corner_609-877-0836_EdgeWater_Park_NJ_USA_V.fc (1:266/28)


/*** Jonathan Vincent Ng **** Toronto Ontario Canada ***\  \\\\\\\\\\\
*    j2ngo@acs.ryerson.ca   *       jvng@io.org         *  // Team  //
*  jvng@m-net.arbornet.org  *      XplorR on IRC        *  \\  OS/2 \\
\***** God is real...,unless casted to an integer. *****/   \//////////