TIP: Click on subject to list as thread! ANSI
echo: os2prog
to: Jason Hendriks
from: David Noon
date: 1997-01-14 21:57:20
subject: Watcom C++ 10.6

On Sunday, 97/01/12, Jason Hendriks wrote to David Noon about "Watcom
C++ 10.6" as follows:

JH>  DN> Ditch the path and .DLL suffix. Just call it EPMLINK, check the button
JH>  DN> for DLL activation and let the LIBPATH take care of loading.
JH> 
JH> That's the default.  But both Watcom 10.5 and 10.6 give me 
JH> the error "unable to start editor" (NOT "editor not 
JH> available" - file not found).

Hi Jason,

Do you have an older EPMLINK.DLL earlier in your LIBPATH that could be
incompatible with the current Watcom IDE? Or one from another product?

My directory for *.DLL for Watcom 10.6 looks like:

The Volume Serial Number is A6BD:8814.
Directory of G:\WATCOM\BINP\dll

 2-29-96   4:06p     54914           0  codeview.dll
 2-29-96   4:06p     87320           0  dwarf.dll
 2-29-96   4:06p     15823           0  epmlink.dll
 2-29-96   4:06p      9398           0  export.dll
 2-29-96   4:06p      2398           0  net.dll
 2-29-96   4:06p      3338           0  nmp.dll
 2-29-96   4:06p      4550           0  nov.dll
 2-29-96   4:06p     10114           0  os2edit.dll
 2-29-96   4:06p      7318           0  par.dll
 2-29-96   4:06p     48042           0  rcsdll.dll
 2-29-96   4:06p      7448           0  ser.dll
 2-29-96   4:06p     18764           0  std16.dll
 2-29-96   4:06p     28678           0  std32.dll
 2-29-96   4:06p      2614           0  tcp.dll
 2-29-96   4:06p      2730           0  vdm.dll
 2-29-96   4:06p     59726           0  watcom.dll
 2-29-96   4:06p       644           0  wdpmhook.dll
       17 file(s)     363819 bytes used
                     9445888 bytes free

Does yours match the size and date/time?

Note also the os2edit.dll. That might also be required. Do you have
all the above DLL's?

JH> D:\WATCOM\BINP\DLL is in my libpath and even moving EPMLINK to
JH> \OS2\DLL did  not help.

This should not be necessary.

JH> Any other ideas?  Is there a way to start
JH> the  dll right from the command line?  I would sure like to get  this
JH> working because EPM is sloooow.

There is no way to start a .DLL directly, since it isn't a main
program, it's a subroutine library.

It's only speed advantage over EPM is getting started, and that's
marginal. Once it starts it's just EPM.

Regards

Dave


 * KWQ/2 1.2i * "Dyslexic Christian sells soul to Santa."  ... News at 11
--- Maximus/2 3.01
* Origin: DoNoR/2,Woking UK (44-1483-725167) (2:440/4)
SEEN-BY: 50/99 54/99 270/101 620/243 625/0 160 711/401 409 410 413 430 808
SEEN-BY: 711/809 934 955 712/311 407 505 506 517 623 624 704 713/317 800/1
@PATH: 440/4 141/209 270/101 712/624 711/808 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™.