| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Watcom C/C++ (was: Os/2 C++) |
Hello Mike! 01 May 95 08:39, Mike Bilow wrote to James Mckenzie: MB> My objection is that, at the time I paid about $200 for the MB> product, there was free technical support available via e-mail. MB> Several months afterward, Watcom announced that they were MB> eliminating free technical support. I felt burned. That happens in this world. I am going to write Watcom at their internet address asking if they ever thought of starting a WATCOM fidonet echo. It will be extremely hard to start one from over here (considering that I leave in less than 5 months.) MB> In addition, my entire usage of technical support had consisted MB> of reporting bugs. Very good use. But if you don't mind, would you post an example of what kind of bug you found. Maybe if they receive multiple postings, then they will think twice of killing off the internet address. In my case, I have not joined Compuserve for one very important reason, finances. The second reason, time, is not a major factor. MB> Admittedly, I was using the 16-bit OS/2 MB> compiler, and that is something that is not a very popular MB> component. Nevertheless, Watcom's new policy on bug reporting, MB> as it was explained to me by customer service, is that you call MB> Watcom, provide a credit card number, and they refund your charge MB> if they later decide that what was being reported actually was a MB> bug. And not very good business sense. You would loose more customers this way (re: Microsoft Access.) Look at their recent policy change. Call technical support with a valid bug report, receive report number. Several days later, receive call from Microsoft with either a workaround or thanks. They are working with the customer, not against them. MB> You are confusing E, which comes with OS/2, with EPM, which is MB> written by IBM but included with Watcom. To change the editor, MB> modify \watcom\binp\idex.cfg by changing the line: MB> Editor "epmlink" DLL MB> to read: MB> Editor "c:\\watcom\\binp\\vi.exe" But how do yoou build vi for OS/2? James --- GoldED/2 2.50.B1016+* Origin: OS/2 Support * Your place for OS/2 information and Files (6:760/13) SEEN-BY: 105/42 620/243 711/401 409 410 413 430 807 808 809 934 955 712/407 SEEN-BY: 712/515 628 704 713/888 800/1 7877/2809 @PATH: 760/13 5 6 270/101 105/103 42 712/515 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.