--------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E3400000 Date: 03/03/97 From: TAMMY KAM Time: 10:14pm \/To: JONATHAN DE BOYNE POLLARD (Read 2 times) Subj: Warp 4 -> Transferred from OS2PROG, where it wasn't on topic, to OS2DOS, where -> it is: I don't mean this as a complaint so I hope it won't be taken that way. With several os/2 echoes I sometimes get confused which question goes in which os/2 echo. I decided to post it and wait for help or moderator shame shames.. -> TK> 1. In Warp 3, I had to use Sharefix and Ostsr for sharing and -> TK> timeslicing on my Wildcat4/Intermail system. Do I still need -> He'd probably never heard of the programs. Which is to be expected, -> since they really address a very narrow and specialised user -> community, if we are being honest here. Yeah I learned that some of the tech staff is very uneducated on bbs questions but I must admit that other than the cost of the phone call I have had great service from ibm. -> The simplest answer is that WildCat and Intermail haven't changed. I know but I have hope. -> They still won't be DPMI multitasking friendly. So yes, you -> probably will have to continue to use OSTSR to convert DesqView What I decided to do was test it all out myself. I removed the ostsr and sharefix and called from another computer and it definitely is needed with the Warp 4 if a dos mailer and bbs are run. -> probably continue to need SHAREFIX until the progra (if they ever -> will be, which is doubtful having seen the way that Mu Software has -> worked for the past few years). I have only been a sysop a short time so I'll bear in mind what you have said and keep a watchful eye on Mustang and it software. So far, I like it and the support I have received. I must admit though I do wish they would come out with a version for os/2 without Win95. I am still a little hesitant on win95. Thanks for the help and information. Cyberly yours, Tammy Kam --- InterEcho 1.19 * Origin: CyberAsylum BBS 1-901-795-9144 tammykam@netten.net (1:123/424) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E3500000 Date: 02/28/97 From: STEPHANE BESSETTE Time: 02:15pm \/To: STEPHEN HAFFLY (Read 2 times) Subj: Win95 under os/2 ??? -=> Quoting Stephen Haffly to Stephane Bessette <=- SH> On (16 Feb 97) Stephane Bessette wrote to George White... GW> NO! Win 95 will _only_ install on a primary partition on the first GW> hard drive. SB> Not true. I once installed Win95 on drive D. Both drive C SB> and drive D were from the same physical hard disk. SH> Hi Stephane, SH> Please complete the hows. Were you using boot manager? If so, then SH> Boot Manager was on a primary partition that controlled the boot SH> process. I am sure that after Windows 95 tried to trash your C: setup SH> that you had to go back with OS/2's FDISK and set things back to SH> right. I did that last summer. My friend was very quemish about partitioning and formatting a hard drive, so I did most of the work. He wanted to be certain to be able to run his DOS and Windows software, and had also purchased Win95 (because that's what people on the Windows platform had to do), and he had also purchased OS/2 v3.0, because I kept telling him about it. So, to satisfy him, and give him the most freedom possible, I decided on the following partitions: C: DOS/Windows 3.1 D: Win95 E: OS/2 F: unused : boot manager I put boot manager at the end, because DOS/Windows 3.1 had already been installed, and I didn't want to go through that installation. I installed OS/2, showed him some of the basics, and he said that he liked it, that it wasn't difficult to use, contrary to what he had used. Then I exited OS/2, rebooted in Windows 3.1, installed Lotus SmartSuite, rebooted OS/2, and ran the 'add new program' utility. And he was impressed that OS/2 could find the SmartSuite applications that had been installed under native Windows 3.1 (although I must admit that this was the response I had aimed for). By that time it was getting a bit late, so I quickly installed Win95, and couldn't do it. There was a hardware conflict, and either the sound card or the mouse wouldn't work (I can't remember which). After an hour of fiddling around and not gettin anywhere, but getting a bit sleepy, I gave up and told him to seek help from someone who knew Win95 better than I did. Luckily, he had such a friend. Before he left, I reactivated the boot manager: Win95 simply deactivates it, it doesn't trash it. This way, his computer could run DOS/Windows 3.1 and OS/2. Or so I thought. For some reason, Lotus SmartSuite would no longer start under OS/2. I no longer had access to the computer, and couldn't figure out the problem over the phone. I asked him what he had done since I had last seen the computer, and he said nothing, except that now Win95 was working (probably his friend had fixed that problem). Anyways, he liked Win95 and decided to scrap OS/2. Humft #$%#$$#!!. So that was the end of it. I know that this may have been a long story, but you did ask that I 'complete the hows', and so I hope I did. If you were only wondering about how to reactivate boot manager, then you only need to use fdisk and activate the partition. You could do it from Win95, or use the two OS/2 installation floppies, and exit the installation. At the prompt, type fdisk. Also, I've since installed Win95 on my own computer; I'm tired of friends calling me about their Win95 problems and me having to learn Win95 'over the phone', by asking them questions. I've installed it, looked at it, and I must admit that I'm disappointed. I had heard a lot of hype, and a lot of comments about how user friendly it was, how you could do so many things with it. But my initial though on it was: "What, this is all that there is?" I couldn't believe it. I always believed that Win95 could compete against OS/2, and now I see for myself that it just isn't so. Here's one difference: folders. Under OS/2, a folder is an object that contains other objects: other folders, files, program objects, shadows, templates, ... Folders can present their information in three views: tree, icon, details. With each of these views, you can also specify other details, such as the size of the icons. You can also specify filters, so that certain objects are hidden and others visible: show me all files with extentions .CPP, .HPP, .EXE, .DLG, .RC and I'll be happy since these are the files I need when I program, and I have no use of .OBJ nor of .BAK. You can also specify how the objects are sorted. Then you can specify the background, whether it is a color or a bitmap. You can easily customise the system menu (the one in the upper left corner of every window). You can make it a work area, a really useful feature in some circumstances. You can add comments, make the folder a template, and change its icon. With Win95, you can specify some features, such as whether the extentions are displayed. There must be other things you can do, but I'm not quite certain. Nevertheless, it should be clear that you're quite limited, compared to OS/2. I've been using OS/2 for 2 years now, and I find it difficult to use an OS that works against me. I need templates. I need shadows. I need to be able to drag and drop objects. I need superior multitasking: I rarely have less than 4 programs running. I need OS/2. Stephane [TEAM OS/2] --- Blue Wave/OS2 v2.20 * Origin: Juxtaposition BBS. Montreal, Qc, Canada (1:167/133) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E3500001 Date: 03/02/97 From: GEORGE WHITE Time: 10:59am \/To: KEN SCHAFER (Read 2 times) Subj: Win95 under os/2 ??? Hi Ken You wrote to Brent KS>BS>So I was wondering if I could Install win95 on this drive, KS>BS>or will it give me problems when I am under os/2. KS> GW> NO! Win 95 will _only_ install on a primary partition on the first KS> GW> hard drive. KS>I have found this to be true but... KS> GW> If you have ony one physical hard drive and can add a second drive KS> GW> there is a way to install it relatively painlessly, otherwise it KS> GW> will involve a lot of work. KS>...this makes it sound like awfully difficult. It's actually rather easier than either of the two options in the messages you've repeated. It boils down to: 1) Install a second HD 2) Use Fdisk to create a primary partition on it (at least as big as the existing D partition as it will become D). Other partitions to personal choice. 3) Boot from floppys (using the install disks and escapeing via F3 is the easiest route) and copy (using XCOPY) the full drive D data from the existing drive D (it will be E now) to the new drive D. 4) Use FDISK to delete the existing D partition on the first drive, and then create a boot manager partition and a primary partition in the rest of the space. The existing data will all be unchanged, the remaining partitions on the primary will have the same drive letters as before the changes, so there is no need to re-install OS/2 (which he had installed on C), and Win 95 can be installed on the empty primary partition just created on the first hard drive. If the partition sizes on the first hard disk need changing PartitionMagic (commercial) will allow changing them. KS>I found these 2 very useful messages in these echoes... KS> RE> Is it possible ot have both of the above KS> RE> operating systems on the same KS> RE> hard drive but partitioned? I tried and I didn't have any luck. KS>These instructions assume that the hard drive is empty. But Brent has things installed, and didn't want to start over. If complete reinstall is acceptable, then they apply. KS>1) Boot from the OS/2 install floppies KS>2) Partition the disk as follows: KS> - a boot manager partition KS> - a primary partition for Windows KS> - enough unallocated space to add OS/2 later KS>3) Set the Win95 install partition active as C: KS>4) Boot from the Win95 install floppies KS>5) Install Win95 on the C: drive KS>6) After installing Win95, boot again from the OS/2 floppies KS>7) Create a partition for OS/2, and active boot manager as C: KS>8) Install OS/2 KS>This has worked for me so far. KS>----------Cut------------------- George * SLMR 2.1a * Desk: A very large wastebasket with drawers. --- Maximus/2 3.01 * Origin: DoNoR/2,Woking UK (44-1483-725167) (2:440/4) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E3500002 Date: 03/03/97 From: DAVID NOON Time: 08:40pm \/To: JAMES MCKENZIE (Read 2 times) Subj: Dpmi Limits In a message dated 02-28-97, James Mckenzie said to Jonathan de Boyne Pollard about Dpmi Limits Hi James, JM>However, make sure that you never provide a DOS/4GW program session more JM>than 32MB of DPMI memory or strange actions might result. Such as? I haven't had to push any of my DOS/4GW proggies beyond 32MB yet, so I'd like to know what might happen. Regards Dave ___ * MR/2 2.25 #353 * Pieces of nine! Pieces of nine! A parrotty error? --- Maximus/2 3.01 * Origin: DoNoR/2,Woking UK (44-1483-725167) (2:440/4) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E3A00000 Date: 03/02/97 From: JONATHAN DE BOYNE POLLARD Time: 12:03pm \/To: DAVID NOON (Read 2 times) Subj: Dpmi Parameters JP>> Unfortunately, some of the client-side code is in JP>> DOS4GW.EXE itself, I believe. DN> In the copy with Watcom C/C++ 10.6 this is hauled in automatically by DN> the stub module. You do need to have the DOS/4GW (i.e. Watcom) DN> directory along the path, but you don't need to use DOS4GW.EXE to DN> load the program. Yes, but all that that means is that the stub program was augmented so that it went searching for DOS4GW.EXE along the path if the executable was invoked directly. DOS4GW.EXE is still required. On a system with a DPMI host of its own (such as an OS/2 Virtual DOS Machine), the DPMI host built in to DOS4GW.EXE (i.e. "VMM") isn't required and won't be initialised by the DPMI client. But that doesn't mean that DOS4GW.EXE itself is superfluous, because I believe that not all of the client side code is in the application executable itself. At the very least, the loader for the LE format that brings the "real" program into memory seems to be in DOS4GW.EXE. I suspect that that is not the only "necessary" DPMI client code that resides in DOS4GW.EXE instead of the application executable itself. JdeBP --- FleetStreet 1.16 NR * Origin: JdeBP's point, using Squish (2:440/4.3) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E3A00001 Date: 03/04/97 From: TONY LANGDON Time: 08:27am \/To: ALEX BINNIE (Read 2 times) Subj: PPoint point system It's 26 Feb 97 05:43:44, We'll return to Alex Binnie and Tony Langdon's discussion of PPoint point system TL> (using DOS_DEVICE). This will use SIO's port configuration, so Binkley TL> will find the correct IRQ via the FOSSIL. AB> I am already doing exactly this now. AB> Thank you for the help Anyway. No probs. Been through the FOSSIL woes myself. :-) Nothing worked for me, except VX00.SYS. :-) ... !!!ereh fo tuo em teG !!!pleH --- FMail/386 1.02 * Origin: The Bridge - Remote Sysop. (3:635/728.18) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E3A00002 Date: 03/03/97 From: ALEX BINNIE Time: 08:08pm \/To: KEN SCHAFER (Read 2 times) Subj: PPoint point system On (18 Feb 97) Ken Schafer wrote to Alex Binnie... Hello Ken KS> In a message to all, you wrote: AB> I am trying to run ppoint with OS/2 Warp Version 4 and I am AB> having a little difficulty as my com port is on COM2 IRQ 5 and I AB> cannot get binkleyterm to dial out on this setting. KS> Your DOS software is possibly looking for IRQ3. SIO (which I use with KS> Frontdoor) has a line in my CONFIG.SYS as follows... KS> device=g:\sio\sio.sys (com2:115200,2f8,irq5:irq3,-) KS> ...which, in effect, tells the system to reroute IRQ3 instructions to KS> IRQ5. I ended up using SIO and VX00 as the fossil and it works perfectly but I must say that these bloody Plug and Pray motherboards are more trouble than they are worth :-( Regards Alex Email 100675.231@compuserve.com ... ... People who live in glass houses don't have much of a sex life. --- PPoint 1.92 * Origin: Alex's Travelling at Warp 4 (2:259/50.3) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E3C00000 Date: 03/06/97 From: JONATHAN DE BOYNE POLLARD Time: 04:25am \/To: TAMMY KAM (Read 2 times) Subj: Warp 4 TK> With several os/2 echoes I sometimes get confused which question goes TK> in which os/2 echo. I decided to post it and wait for help or TK> moderator shame shames.. I believe that Jim Gilliland in the OS2 echo posts a "Family Guide" on a regular basis. If he's stopped (and I haven't even checked that he still _is_ the moderator, to be honest), then I suppose that we (the other OS/2 echo moderators) ought to organise something. TK> Yeah I learned that some of the tech staff is very uneducated on bbs TK> questions [...] Probably because they've never run a BBS themselves. It's certainly not something that I can see support staff being trained in. (-: TK> I have only been a sysop a short time so I'll bear in mind what you TK> have said and keep a watchful eye on Mustang and it software. So far, TK> I like it and the support I have received. I must admit though I do TK> wish they would come out with a version for os/2 without Win95. I am TK> still a little hesitant on win95. Mustang Software has been leading users on with promises of "jam tomorrow" when it comes to an OS/2 version of WildCat and so forth for as long as I can remember. A year or so back I remember seeing a lot of people become disillusioned with waiting, and switching to one of the many native OS/2 BBS softwares instead, such as LoraBBS, AdeptXBBS, Maximus, and so forth. I'd be really surprised if there were many, if any, OS/2 users still sticking to Wildcat in the hope of an OS/2 version after all of these years. I certainly wouldn't have, had I been in their position. JdeBP --- FleetStreet 1.16 NR * Origin: JdeBP's point, using Squish (2:440/4.3) --------------- FIDO MESSAGE AREA==> TOPIC: 252 OS2 DOS Ref: E3C00001 Date: 03/05/97 From: TONY LEWIS Time: 06:20pm \/To: ALL (Read 2 times) Subj: Changing resolution OS2 Can some tell me how to get OS/2 to change the default 640x480x16 resolution to 800x600x256 or atleast a 256color mode. I've installed WinOS2 and windows and it's using 800x600x256. But the desktop wont change in fact it doesn't even display any additional screen res. I know it supports my video card in the higher modes as it's listed in the manual and the drivers are on the CD. I even followed the directions for SVGA install, which worked but still didn't add any other screen sizes. Is there a way to maybe set this in the config.sys file? Percision@juno.com ___ Blue Wave/QWK v2.20 [NR] --- PCBoard (R) v15.21/M 10 * Origin: GE999 BBS * The Anime Resource * 718-961-1764 (1:278/539)