Return-Path: Received: from asio.cia dot com (asio.cia dot com [209.197.145.101]) by mail. (Weasel v1.20) for ; 09 June 2001 01:00:00 From: "Digest" To: "OS/2GenAu Digest" Date: Sat, 9 Jun 2001 01:00:00 +1000 (EDT) Reply-To: "OS2GenAu" Priority: Normal X-Mailer: CASMailer 1.0 for OS/2 Warp PPC 1.05/G4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: No. 83 Message-ID: <200106090100.000029G6atmail.> Date:- 9 June 2001 1================================================ From: "Gavin Miller" Date: Fri, 08 Jun 2001 17:09:04 -0400 (EDT) Subject: Re: [os2genau] Epston Stylus Installation Hi Alan, As your problem has spread to Windo$e, it might have something to do with the actual cartridge. I've had one fail on me before, and all the printer did was beep when a print job was sent. See what happens with the replacement printer. :-) Cheers, Gavin On Thu, 7 Jun 2001 23:18:24 +1000, Alan Duval wrote: >I spoke too soon. >This morning I tried printing from my various programs and was able to do >so from all except Lotus Smartsuite 123. when I tried to print a range of >cells it would only print the cell borders and the background colours but >not the figures in the cells. I tried many times and in the end decided to >remove the background colours and try to print. Well at this point the >printer head moved a few times and then stopped and the green light started >flashing and the second light went red. Nothing I did helped so I had to >turn off the printer. I tried again with the same result. Rebooted and >tried again several times with the same result. >I then went back to windows to check that the printer was still able to >print and to my horror found the same thing happened. Tried to print from a >command line but no result. Also the maintenance utility wouldn't function. >Then rang Epson and they told me to try various things but no result so >they are giving me another printer. >I'll pick it up on Saturday. Hope this works better. > >> >> I'm starting to suspect a corrupted os2sys.ini file. Do you know >> how to use iniedit or inimaint ? I'd be tempted to de-install all >> printers, go through the INI file and remove anything that refers >> to either your old Deskjet or this Epson, reboot and then >> re-install the drivers. > >You may have a point here as although I delete printer objects and their >drivers if I reinstall the driver it says that the files already exist??? >Also Warpguide is never able to fully install the driver and says that >install has failed as it has been unable to create a printer object.??? >why. > >I've got iniedit but don't know how to use it. Also got Unimaint but >haven't explored it's use with ini files. >How would I know whether the files referred to my old deskjet or this >Epson? I guess if they had HP or EP at the start they would be candidates >but they may not have such obvious letters. > >Regards > >Alan 2============================================= Date: Fri, 08 Jun 2001 23:28:57 +1000 From: Daryl Pilkington Subject: [os2genau] SOLVED: [OT] Internet Dial-Up Thanks for all the input folks, The internal hardware modem in question was a: Askey Diamond Voice 56i V1456VQH-R AST CONCLUSION: Solution was not strictly a Windoze problem. It did demonstrate though, that a good understanding of how modems work in practice was required to solve this problem. It also demonstrated how the automation in Windoze is a major handicap in problem determination for skilled professionals. FINDINGS: I installed the internal modem on my known-to-work OS/2 box, which does nothing "automatically". 1) Whilst I thought the modem was configured for com2, (2f8, IRQ3). I found it was configured for (2f8, IRQ4). Misconfigured, the modem simply didn't respond under OS/2. Under Windoze AT commands worked OK & the modem even dialed out! (Doesn't say much for the i/o routines of Windoze). In both cases hardware flow control had been selected. Once configured correctly, it worked just fine with 56Kflex protocol on my OS/2 box. 2) It was a Rockwell chipset 56Kflex modem & required a firmware upgrade to v90. Once this was achieved, it also worked fine under OS/2. 3) Reinstalled in Windoze box. I only had the original 56Kflex modem.inf file. which I used. FYI a Windoze modem.inf file defines what AT init strings are required for modem: compression error correction Maximum DTE speed This file is useful for finding out these strings for configuration of modems in non-Windoze environments. This time it passed the userid & password, but then it died. This was a new situation, so I figured I'd install the new v90 modem.inf file. 4) With the v90 modem.inf file it didn't even pass the userid & password. I've seen this problem before & is usually due to modem protocol misconfiguration rather than a PPP issue. 5) Based in this hunch, I installed a "standard modem" inf file. It then worked!!! This indicates the manufacture-supplied v90 modem.inf file was defective. -- Regards, Daryl Pilkington //// The PC-Therapist, Business Computing Integration O OS/2 Warp, Redhat Linux, DB2 IBM Certified Systems Expert email: darylpatpc-therapist dot com dot au ICQ: 91914134 Tel: +61-2-8902-1300 Mob: +61-425-251-300 Fax: +61-2-9411-3720 Mob SMS: 0425251300.0000atorangenet dot com dot au (120 characters max, send no carriage returns) END=============================================