* Jerry_McBride,MoDem_Corner,New_Jersey,USA,1:266/28.0@fidonet.org * First off, I love "doing" what people tell me is "impossible". Getting winos2 to run in Warp III is one of those "impossible" things that turns out to be do-able and downright enjoyable! There are basically two methods, that I have used, to get the os2 2.1ga winos2 to run with Warp release 1, 2 or 3(GA). Also, I have been able to get the winos2 notebook settings to function correctly with this install procedure. However, I have not be able to get the Win-Os/2 Setup object in the System Setup folder operational. **** Before I begin, I will assume that you have some idea how to unpack files from your os2 install disks/cdrom and that your system is setup reasonably close to what I run. I boot os2 from my c: drive, which is formatted as one hpfs partition and run in vga video mode. If your system is radically different from mine, then it will be on you to "build" on what I provide for you here. I will also assume that you have not installed windows 3.1, if you have, you are again in a position of having to "build" on what I provide you here. We begin... **** Step:1 ----- Backup your hard drive(s). Step:2 ----- The second step to install winos2 onto your Warp III system is to actually get the winos2 files onto your hard drive. Procedure #1 and #2, described below, are the only two ways that I have experimented with. Read over both procedures and choose one. Proc #1: The easiest way is to put the winos2 files into an archive and move it from an os2 2.1 machine to the Warp III machine. I have used infozip to create the archive: "zip -r9 winos2 \os2\mdos\winos2". Once I copied the winos2.zip to the Warp III machine I used: "unzip winos2" to install the files. The winos2 archive will be somewhere around 3.8meg. It's possible to transfer it via floppies or by "wire". Use what you are familiar with. Proc #2: The second way of getting winos2 onto your Warp III machine, requires access to the os2 2.1 install diskettes. This procedure will install the winos2 files and setup for xga winos2 sessions (default install). By using this method, you will not overwirte any of your exisiting warp files or corrupt any of your other system settings. On your Warp III machine, first, create this path: c:\os2\mdos\winos2\system Now, from an os2 prompt, insert the following numbered os2 2.1 install diskettes and execute the command to the right of the diskette number. Diskette #6 -------- unpack a:winenv Diskette #7 -------- unpack a:winini Diskette #8 -------- unpack a:winreadm Diskette #9 -------- unpack a:winaccess Diskette #9 -------- unpack a:winenv Diskette #9 -------- unpack a:wintouch Diskette #10 ------- unpack a:winver Diskette #11 ------- unpack a:winscrsv Diskette #12 ------- unpack a:winenv Diskette #16 ------- unpack a:winenv Diskette #16 ------- unpack a:winsound Display Diskette #1 unpack a:winxga If you chose procedure #1, your winos2 is setup for whatever video/mouse mode that your 2.1 system was running. If you chose procedure #2, your winos2 is setup for default xga video and a serial mouse on port 1. If you would rather vga, then do the following: move to the winos2 directory and edit program.ini and change all occurances of xga to vga. Edit system.ini and perform the same change from xga to vga. Also, while you're in the winos2 directory, check mouse.ini and see if it's setup right. I had to change serial1 to serial2. Now, go back to the root, insert Display Diskette #1 and unpack a:winvga. Your winos2 is now setup for vga video. I have not tried any other video mode or mouse setup and I leave it up to you to figure out other modes of operation. Step:3 ----- Move to the root directory and edit config.sys and add the following path statements: Add c:\os2\mdos\winos2\system; to the LIBPATH line Add c:\os2\mdos\winos2; to the PATH line Add c:\os2\mdos\winos2\system; to the DPATH line At the end of your config.sys add this line: DEVICE=C:\OS2\MDOS\VWIN.SYS Exit your editor. Edit autoexec.bat and add "c:\os2\mdos\winos2;" to the PATH line. Exit your editor. Step:4 ----- To complete the install of winso2 on your Warp III system, you will now have to unpack the Warp III winbase bundle on diskette #9 or in the cd-rom directory \os2image\disk_9 Do either of the follwing at the os2 prompt: diskette #9 - unpack a:winbase unpack drive_spec:\os2image\disk_9\winbase Step:5 ----- Go over all that you have done and perform a shutdown, restart and open an os2 session. From the prompt enter the command: win. Dos should load, followed by winos2. Enter the printmanager and install whatever printer you desire. When you are prompted for a disk during the printer selection, the system is expecting OS/2 2.1 driver diskettes. I would recommed installing the same printer type that you set warp for. Winos2 is now installed. You can create windows objects on your os2 desktop, as you desire. Step:6 ---- The information detailed below was the result of the efforts of Nicolas Lindstrom at comp.os.os2.misc. I will forever be in his debit! To allow winos2 notebook settings: Find a good ini-editor, such as INIMAINT by CARRY ASSOCIATES. Learn how to use it and peform the following addtions to the named ini files. - Add to OS2.INI the application WINOS2 with the keyword PM_GlobalWindows31Settings with data PROGTYPE=PROG_31_STD. - Add to INSTALL.INI the application WINOS2 with the keyword PM_GlobalWindows31Settings with data PROGTYPE=PROG_31_STD. - Add to REINSTALL.INI the application WINOS2 with the keyword WIN31INSTALLED with data C:\OS2\MDOS\WINOS2 and keyword WINDOWSSUPPORT with data YES note: this last edit to REINSTALL.INI only required me to alter what was already there! So look over the applications/keywords that are in this ini file, before you procede. note: OS2.INI is locate in the \os2 directory, while INSTALL.INI and REINSTALL.INI are located in the \os2\install directory. Check over your editing, exit the inieditor and perform a shutdown and reboot. You will now be allowed access to the winos2 setting in the dos notebook settings. This worked for me, so give it a try... INIMT32.ZIP - inimaint 3.2 is available for freq/download from 1:266/28. note:I have had MANY requests from people wanting to install real WINDOWS on their HPFS systems. For those that "really" want to do this, here's how... Step:1 ----- Read the "winos2 install" procedures described above. Even though you will be installing real windows on your HPFS system, the information offered above is a great learning experience and I will assume that you have at-the-least looked it over and understand most of it. I will also assume that you are running WARP 3.0, as this is the current GA version of OS/2. Step:2 ----- You will have to have access to a system that is currently running windows, preferably 3.1. Strip the windows desktop to the bare minimum. This is only necessary to make the transfer of the windows files easier to accomplish. The "bare bones" install of windows, once zipped up is almost 5 megs in size. So any apps that you drag along, just makes this chore more difficult. Using PKZIP, or similar, archive the windows directory and all sub-directories, keeping the directory structure intact. Move the archive from the windows system to your HPFS system. You can transfer the archive by floppy, wire, whatever you have access to. Step:3 ----- Uncompress the archive. You will now have all the necessary windows files on your system. Almost ready to use... Step:4 ---- Perform a shutdown and reboot. This is a necessary step, as it allows Warp III to detect your newly installed windows directory. Step:4 ----- To complete the install of windows on your Warp III system, I will refer you to the Warp User's Guide, page 19. Enjoy. note: As I collect information concerning this "project" I will add it to this document. To be sure that you get the most current information, I recommend that you make an effort to freq/download this file on a timely basis. Currently, the only thing I have yet to figure out is HOW to enable the WIN-OS/2 Setup object in the System Setup folder. If someone has this information, please share it with me and everyone else. Thank you, Jerry McBride.