--------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: EFZ00000 Date: 11/25/97 From: JOHN T. HONG Time: 08:53am \/To: JONATHAN DE BOYNE POLLARD (Read 1 times) Subj: Re: Win32s? JD> BM> I'm using warp3 Blue Spine (with WinOs2) and have tried to install JD> BM> Win32s V1.25. JD> JD> OS/2 Warp version 3 does not support Win32s version 1.25. For support for JD> Win32s version 1.25, upgrade to OS/2 Warp version 4. Actually it does, only it is a bit tricky. --- GEcho 1.20/Pro * Origin: The Danger Zone, St.John's, NFLD (709)368-4709!! (1:258/300) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: EFZ00001 Date: 11/28/97 From: STEVE MCCRYSTAL Time: 06:32am \/To: RON MCDERMOTT (Read 1 times) Subj: Win32s? ; In a msg of , Ron McDermott writes to Steve Mccrystal: ; Ron, RM> The file he references is not the Win32S code, RM> but the driver for using the code under OS/2.. Now I'm confused! I have Win32s installed and working, to level 1.25b, using only the code in the 2 files I mentioned. What exactly is in the small file we're discussing here, please? Is it a later VW32S.SYS, or what? Thanks! -[Steve]- --- GoldED/2 3.00.Beta1+/#1057US3 * Origin: -[Steve's Place]- New Berlin, WI (FidoNet 1:154/731.2) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: EFZ00002 Date: 11/28/97 From: STEVE MCCRYSTAL Time: 06:01pm \/To: ANDY ROBERTS (Read 1 times) Subj: Win32s? ; In a msg of , Andy Roberts writes to Steve Mccrystal: ; Andy, AR> W32S125B.ZIP 16-Oct-95 18:52 13470 AR> Contains: AR> VW32S.SYS 16-Oct-95 18:52 15073 AR> WIN32S.LIC 16-Oct-95 18:49 3470 AR> WIN32S.PKG 16-Oct-95 18:47 1540 AR> WIN32S.TXT 16-Oct-95 18:50 5573 AR> I replaced C:\OS2\MDOS\VW32S.SYS to upgrade from version A to B. Aha! Thanks. This is an OS/w thing. I was thinking in terms of Windows code supporting Win32s. SM>> I ask because I downloaded the files to install Win32s level SM>> 1.25a for a friend of mine yesterday, and there were 2 files SM>> as below SM>> 11-23-97 9:19 2,287,698 w32s125.zip SM>> 11-23-97 9:34 1,284,585 w32s125a.exe SM>> The difference in size between these two and the file you SM>> have is quite dramatic! :^ AR> AFAIK the larger file contains the full library. Which may NOT AR> be necessary, depending on what app you are going to install. But one or more of them is needed to get support for Win32s in WinOS/2. The file you have will not, on it's own, provide such support. It merely allows WinOS/2 to hook Windows Win32s code. AR> As I mentioned in a previous msg, some Win95 apps will not run AR> under Win-OS2 if you have any version of MS Windows installed on AR> your HD. That's not an issue for me personally -- I have a Win95 partition that I rarely use. I had to do it to help my wife, who is forced to use Win95 a work. AR> Win95 apps that require Win32s v.1.30 may not run under OS/2 at AR> all. It's a rare app indeed that actually NEEDS v1.30 - at least in as much as it *uses* the capability of v1.30. What Microsoft has forced ISVs to do to their code is another matter! AR> Some of the MS written Install.Exe for 3rd-party apps have been AR> known to contain seek'n'destroy code aimed at any non-MS OS. So AR> be prepared to completely reinstall OS/2. Maybe dozens of times. One can only hope that a curent list of such apps would be compiled and updated as required! AR> But the best solution of all is to use native OS/2 apps. I agree, and as I said earlier, it isn't an issue for me. My interest is in order to help a friend who needs to run some rather specialized aviation software that is only written for Windows. He wants to run it in WinOS/2, tho, since he shares my disdain for things of Microsoft origin. -[Steve]- --- GoldED/2 3.00.Beta1+/#1057US3 * Origin: -[Steve's Place]- New Berlin, WI (FidoNet 1:154/731.2) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: EG100000 Date: 11/30/97 From: ANDY ROBERTS Time: 02:08am \/To: STEVE MCCRYSTAL (Read 1 times) Subj: Win32s? Steve Mccrystal, 28-Nov-97 18:01:33, Steve Mccrystal wrote to Andy Roberts SM> November 27 1997 Andy Roberts writes to Steve Mccrystal Subject: Win32s? AR>> AFAIK the larger file contains the full library. Which may NOT AR>> be necessary, depending on what app you are going to install. SM> But one or more of them is needed to get support for Win32s in SM> WinOS/2. Definitely. But it is included on many CDs with the Win95 app. SM> The file you have will not, on it's own, provide such support. SM> It merely allows WinOS/2 to hook Windows Win32s code Correct. The little file with vw32s.sys is special for OS/2 while the big file contains the common MS DLLs. AR>> As I mentioned in a previous msg, some Win95 apps will not run AR>> under Win-OS2 if you have any version of MS Windows installed on AR>> your HD. SM> That's not an issue for me personally -- I have a Win95 partition SM> that I rarely use. If you have 2 separate Primary partitions that can NOT see each other, then you are probably safe. But if you have Win95 on the only Primary partition and Warp on an Extended partition (the typical locations) then you are going to be in for a very unpleasant surprise sooner or later (depending on the app.) It is not a matter that Win95 is not loaded and running. The MS written Install.EXE searches your entire HD looking for specific files that are included in MS Win3.1 and Win95. If it finds 1 of those files then it will not run under Win-OS2. But if it does not find those files then it will run under Win-OS2. And nothing you change in your Config.Sys or Autoexec.Bat or any other setup will have any effect of that situation. It took me over 1 year to discover that. AR>> Win95 apps that require Win32s v.1.30 may not run under OS/2 at AR>> all. SM> It's a rare app indeed that actually NEEDS v1.30 - at least in as SM> much as it *uses* the capability of v1.30. What Microsoft has SM> forced ISVs to do to their code is another matter I'm inclined to think there is very little if any functional reason to all the Win32s upgrades. There is evidence that it is all just a MS marketing ploy to prevent apps from running on anything except the latest MS OS so that MS can sell more software. Just a gimmick. AR>> Some of the MS written Install.Exe for 3rd-party apps have been AR>> known to contain seek'n'destroy code aimed at any non-MS OS. So AR>> be prepared to completely reinstall OS/2. Maybe dozens of times. SM> One can only hope that a curent list of such apps would be SM> compiled and updated as required I have not seen an organized list. But I have seen msgs from many users. There must be at least 1/2 a dozen apps like that. In some cases it is just a matter of the app over-writing essential files. OS/2 is not the only victim. I've seen the same problem under DrDOS6 and NWDOS7. Thanks and Good Luck, Andy Roberts NetMail 1:109/921.1 AdeptNet 55:730/101 andy@shentel.net --- Terminate 5.00/Pro*at * Origin: OS/2: penthouse. DOS: poorhouse. Windows: outhouse. (1:109/921.1) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: EG100001 Date: 11/28/97 From: ANDY SMITH Time: 08:48am \/To: JOHN THOMPSON (Read 1 times) Subj: Os/2 and win95 -=> John Thompson recently spurted the following gem to Andy Smith <=- Hiya John, JT> It doesn't overwrite the Boot Manager; it simply removes its active" JT> flag from the partition table. To restore Boot Manager you simply run JT> fdisk and tell it to mark Boot Manager as "active" again. Ah right, with you...cheers Andy --- FMailX 1.20 * Origin: Zeons Lair Images BBS +44-1768-899420 (2:256/305) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: EG100002 Date: 11/30/97 From: VICTOR LOBERGER Time: 11:14am \/To: JONATHAN DE BOYNE POLLARD (Read 1 times) Subj: Win32s? Jonathan, JdBP> It's probably a lot easier to just install 1.25, and JdBP> edit Windows' INI files and the command line for JdBP> VW32.SYS in CONFIG.SYS to report the appropriate JdBP> version level. It sure does sound a lot easier. My questions are what .INI files if more than WIN32S.INI and what exactly would be the command line for the VW32.SYS? I just have a couple programs that think they need 1.30. FreeCell works fine with what I'm running, so I must be close. 8-) Thanks for any help! Victor --- Maximus/2 3.01 * Origin: Aarrgghh! BBS-Running Max/2, MainDoor/2 & Squish/2 (1:154/731) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: EG100003 Date: 11/30/97 From: RON MCDERMOTT Time: 03:58pm \/To: STEVE MCCRYSTAL (Read 1 times) Subj: Win32s? SM>; SM>In a msg of , Ron McDermott SM>writes to Steve Mccrystal: SM>; SM>Ron, RM> The file he references is not the Win32S code, RM> but the driver for using the code under OS/2.. SM>Now I'm confused! I have Win32s installed and working, to SM>level 1.25b, using only the code in the 2 files I mentioned. WARP 4? It may be that the Win32S code is automatically included in WARP 4, but if THAT were the case, why wouldn't the drivers be there automatically too? The code DEFINITELY wasn't in WARP 3, because I had to add it, ALONG with the drivers. The Win32S code itself is a couple of megs, and installs itself under WINOS2\SYSTEM... SM>What exactly is in the small file we're discussing here, please? SM>Is it a later VW32S.SYS, or what? The file size referenced HAS to be VW32S.SYS, it's FAR too small to include the Win32S code. ___ * MR/2 2.26 * DOS=HIGH? I knew it was on something... --- Maximus/2 3.01 * Origin: The Reading Room (1:272/160) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: EG100004 Date: 11/30/97 From: JIM BAXTER Time: 06:54pm \/To: ANDY SMITH (Read 1 times) Subj: os/2 and win95 on 11-26-97, Andy Smith said to Jim Baxter: JB> well, you have it wrong my friend :) ->I just seemed to remember reading that when you install Win95 it over ->writes the boot manager..still ta for the info, I shall give it a go. it didn't do anything on my system.. but anyways, good luck with your ventures :) --- MR/2 2.2 NR "Who is #1?" "You are, #6." --- Renegade v5-11 Exp * Origin: Electric Prayers - Everybody Knows This is Nowhere (1:221/802) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: EG300000 Date: 12/03/97 From: CHARLES JACKSON Time: 08:02pm \/To: ALL (Read 1 times) Subj: Printing / memory problem Hello, Recently my wife drew a map to our house using the Paint Brush program included in win-os2. She did a very nice job for our church members but thing won't print. Every time we try to print it, a dialogue box pops up and tells us that we don't have enough memory (I have 64meg installed) or the printer isn't installed correctly. I have changed all the settings possible to allow for use of the memory, I have changed from windowed to full screen, and every other possible thing I can think of to know avail. The printer is installed correctly and work perfect with other win-os2 programs. Can someone please tell me what I'm doing wrong? AMD K5 166 64MEG EDO MEM 1.02G WD HARD DRIVE SB16 12X CDROM PANASONIC KX-P2180 (With newest windows drivers) OS/2 Warp V.4 FP level 5 Thanks for your help, Charles Jackson crjackson@juno.com crjackson1@aol.com --- TAG 2.7c + FastEcho 1.45a * Origin: WoS BBS San Antonio, Tx. (210)655-6203 (1:387/770) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: EG300001 Date: 11/25/97 From: MARK TUCKER Time: 10:01pm \/To: JONATHAN DE BOYNE POLLARD (Read 1 times) Subj: Win32s? BM> I'm using warp3 Blue Spine (with WinOs2) and have tried to install BM> Win32s V1.25. JDB> OS/2 Warp version 3 does not support Win32s version 1.25. JDB> For support for Win32s version 1.25, upgrade to OS/2 Warp JDB> version 4. You can install support for Win32s version 1.25 on Warp 3.0 any flavor. It is built into Warp 4.0, that is all. --- cPoint [OS/2] v2.23/FreeWare * Origin: Center Of the Universe (1:325/812.1275)