Compile Issues

[blantonl]

The common theme seems to be "floating-point support not loaded"

I get this after each complile of the etrunker/trunker applications using the Open Source Watcom compiler when running the resulting exe. sometimes the exe will load, but when it switches to "WantCTS" then is bombs out with the Floating Point Support not loaded error.

I've heard that this is because the PMODEW isn't loading, but I've been able to successfully link pmode into the compile (I see PMODE's message before loading etrunk), but, still no joy.

Has anyone out there successfully compiled the etrunk.exe source code and gotten the resulting exe's to run properly? How _exactly_ did you do it?

If we can get this working, I have some pretty good updates to release for etrunker.

Lindsay

 

[nrf]

Sir, please note that I was using an earlier version of watcom when I had it. if you want I could send it to you. it was donated so it would be appropriate.

let me know

nrf

 

[mr_hankey]

while not actually trying to _compile_ the thing myself, the more i read into this problem, the more it looks like a statement in the code that tries to read a floating point value from something that isn't a float, or that the libraries aren't being loaded due to the absence of a floating point expression in the code:


>>Hmm. Sounds like that could be my problem -- I read in the data, but
>>don't do any floating point computation at all. Straight conversion.
>
>
>> cin >> sample.number;
>
>
> That is text to floating-point conversion.
>
> Stephen Howe [TeamSybase]
> London, UK

That's true, but it doesn't seem to be enough to trigger the compiler to
load the floating point libraries.

I added a floating point expression (sample.number * 1.0) and everything
started behaving.

========================

> The docs say that the problem occurs because no fp value is being
> passed to a function. So adding "cout << sample.number;" will "fix"
> the problem.

Aha! That's better than adding in a gratuitous mathematical expression
that I didn't need. I can actually make a case for printing out the
original value in the context of the original program. (And it works!)

> It is also possible to force the fp support to be linked in
> this way:
>
> extern "C" char _ppfltused_;
> #pragma extref _ppfltused_;

====================

> For the first time since I used Watcom, I have an error message that read=
s
> "Floating-point support not loaded." That never happened to me. And I
> played around the switch and include files to no avail. Does anyone
> know how to deal with this?
> =

> Marc St-Jacques (stjacque@ere.umontreal.ca)
> Page d'accueil: http://mistral.ere.umontreal.ca/~stjacque

Well as stated in the documentation:

"Floating-point support not loaded

You have called one of the printf functions with a format of "%e", "%f", or "%g", but have not
passed a floating-point value. The compiler generates a reference to the variable "_fltused_" whenever you pass a floating-point value to a function. During the linking phase, the extra floating-point formatting routines will also be brought into your application when "_fltused_" is referenced. Otherwise, you only get the non floating-point formatting routines."

So look for printf():s and floating point format tokens and check that the argument

 

[SCPD]

Lindsay .. what you have described is exactly what I was finding on 16 bit OS's. I have been unable to get this resolved ...

If you do get this figured out I would be interested in hearing the solution.

 

[blantonl]

while not actually trying to _compile_ the thing myself, the more i read into this problem, the more it looks like a statement in the code that tries to read a floating point value from something that isn't a float, or that the libraries aren't being loaded due to the absence of a floating point expression in the code:

Hankey -->

I've been down this path already with the code, as this is a common issue. But, we don't think this is the actual issue.

We believe that we have narrowed it down to the following issues:

1. The DOS Extender isn't being linked properly.
2. The newest version of the Watcom Compiler is having an issue with the existing code and/or makefiles.

We're still working on it - hopefully someone out there with archaic dos build skill can help!

 

[blantonl]

Ok, I think I have this problem licked.

I've been using the OpenWatcom Compiler 1.1, but this version was just recently released. So, I went and downloaded the legacy compiler Watcom 11.c, added PMODE support for in the wlink.lnk file.

It looks like we are in business, although I have NOT tested to see if 16 bit support is enabled in my compiled version. But, I get a good compiled EXE that is running without errors (so far)

We are making progress.

Looks like it's just a compiler version issue.

More updates soon!

[Thanks to guidance from Rick Parrish and NRF]

 

[SCPD]

Lindsay can you give us the URL of where the 'good' compiler can be downloaded ?

 

[EricCottrell]

Hello,

Since I was using Watcom from the beginning all I had to do was to update for the new dos extender.

I submitted changes to the trunker/etrunker program that adds the VR5000 to the list of supported radios. I have been running it for months without any problem. I have a single radio setup where the main vfo is tuned to the control channel and trunker tunes the secondary vfo to the voice frequencies. The only problem is the VR5000 uses a noisy demodulator chip.

Are those changes in the program to be released?

73 Eric

 

[blantonl]

Lindsay can you give us the URL of where the 'good' compiler can be downloaded ?

http://openwatcom.mirrors.pair.com/watcom/11.0c/watcom-c-11.0c.exe

Are those changes in the program to be released?

Negative.

 

[SCPD]

Thanks Lindsay. I'd like to know why the newer compiler wasn't cooperating. It is very nearly the same code as the "classic" Watcom 11.0c.

Eric - the next version will very likely have your patches applied.

I'm not sure if the next Trunker for DOS will be a version 3.8X (small changes) or 4.0 (big change).

Also, for those messing around with Watcom compilers in general, there are two popular DOS extender programs - DOS4GW and PMODEW. The latter takes up less memory and has fewer licensing issues.

Finally, Lindsay - which set of makefiles did you use?

-rick

 

[blantonl]

Why Rick, I used yours of course... ;-)

 

[Cambion]

Could someone possibly tell me how to get trunker.exe to compile? I'd appreciate it a lot. To save space, it can be to my e-mail address, or for the benefit of the group, to this thread.

So far, I have downloaded

watcom-c-11.0c.exe
pmw116.zip

I installed Watcom to c:watcom and added a few of the variables to my WinXP Pro "Variables" in the advanced tab of "My computer". But I cannot get an EXE from the source codes of trunker. I put pmw into the watcominnt directory.

Again, any assistance would be greatly appreciated in this matter.

Regards
Scott

ps I am wanting to make personal mods to the source, and respect the official releases that I'd never release my changes to anyone, period. Just in case you're wondering =)

 

[SCPD]

Scott;

Have you been able to successfully compile and run a simple "hello world" program like this ?

#include <stdio.h>

int main(int argc, char *argv[])
{
  puts("hello world!");
  return 0;
}

The above when saved as "hello.c" should be able to compile like so ...

wcl386 hello.c

The result should be a hello.exe file that you can run.

-rick

 

[Cambion]

Rick,

When I run wcl386 from the binnt I get an array of errors. The one from binw creates a dos/4g executable that's completely screwed.

But... I run IDE.exe from the Binnt directory, create a new project file, for a DOS 16 bit executable (.exe) and add the hello.c to my project and it compiles without errors, and actually runs.

I have some experience with MS Visual C++ and Dev-C++ (both are actually installed on my system). This compiler is just giving me grief. I have the Trunker source codes downloaded from this web site, and it should compile. I have an O.E. somewhere... just can't find it.

Thanks for your assistance. If you have any ideas what I'm doing wrong, I'd appreciate an eye-opener =)

Scott

 

[SCPD]

Scott;

So you can create 16 bit LE executable DOS programs ... that's a good sign. You never mentioned the specific error messages so I don't have a clue as to what is wrong.

Here's what I have done to successfully get Watcom running.

1. create a pair of batch files, called "wcvars32.bat" and "wcvars16.bat". Each batch file sets the appropriate environment variables and path strings for the command line tools. I run "wcvars32" just before building any protected mode programs and I run "wcvars16" just before building any ordinary DOS programs. I can post the batch files here.

2. there are several ".lnk" file in the binnt directory. I modified one so that invoking the linker with "pm" caused the pmodew DOS extender to be linked directly to the program. I can post my modified LNK file here.

3. I placed the PMODEW files in the BINNT directory so the linker would find them.

Keep in mind that Watcom can create at least three types of programs - "LE" executables as used in DOS, OS/2 executables which is the format for programs running under a DOS protected mode 32 bit extender, and "PE" executables which run under Windows. If you mix and match any of the libraries for these three environments, you will get grief.

-rick

 

[Cambion]

Rick,

Thanks, I would appreciate it if you would include the batch files to the forum so I (and others) can download them. I am running VMware with Windows XP as the OS so I can run Watcom in an environment that will allow me to super-tweak until I get things right. I had installed the newer version of Watcom and got the same floating point error discussed earlier in this thread. So I know I was on the right track. With my main computer, running the 11.0c and kept getting "Unable to open ide.cfg". I try to run my own batch files to set the variables, and I get the same thing.

I'll post the errors in compiling once I get everything set up. Again, I appreciate the assistance.

Scott

 

[SCPD]

watcom batch files

WCVARS32.BAT

set WATCOM=winbookwatcom
set STLPORT_DIR=%WATCOM%STLPort-4.5.3stlport
set PATH=%WATCOM%innt;%WATCOM%inw;%PATH%
set INCLUDE=%STLPORT_DIR%;%WATCOM%h
set LIB=%WATCOM%lib386;%WATCOM%lib386dos
set EDPATH=%WATCOM%eddat

WCVARS16.BAT

set WATCOM=winbookwatcom
set PATH=%WATCOM%innt;%WATCOM%inw;%PATH%
set INCLUDE=%WATCOM%h
set LIB=%WATCOM%lib286;%WATCOM%lib286dos
set EDPATH=%WATCOM%eddat

 

[SCPD]

watcom lnk

WLINK.LNK

# example linker initialization file.
# remember, don't put carets (^) in these!
system begin 286
    option osname='Windows 16-bit'
    libpath %WATCOM%lib286
    libpath %WATCOM%lib286win
    library windows
    option stack=8k, heapsize=1k
    format windows
end
system begin 386
    option osname='Windows NT character-mode'
    libpath %WATCOM%lib386
    libpath %WATCOM%lib386
t
    format windows nt
    runtime console
end
@%watcom%inwwlsystem.lnk
system begin pmodew
    option osname='PMODE/W'
    libpath %WATCOM%lib386
    libpath %WATCOM%lib386dos
    op stub=pmodew.exe
    format os2 le
end

 

[acarsnut]

HELLO CODE GUYS
Is there anyone working on or can it be done.to change the detail log so the colors match what you have the talk group and radio id set for.on my trunk setup I have the fire in red all the way across when it comes up police in blue.makes it easier to seperate the depts.would be nice if you could do that in the detail log also.that way your af and unaf would be color coded per talk group all the way across the screen.

THANKS FOR THE TIME
LOVE MTRUNK
David
GROVER NC

 

[troymail]

I see it's been awhile but was anyone able to resolve the
Floating point issue ?

I recently downloaded Watcom 1.2 and trunker compiles
via the IDE just fine but when I move the executable to
my DOS machine and run it, it crashes with the Floating
Point error....

Thanks