Help with Eznec on WinXP
 

I'm trying to get Eznec ver 2 to run on a WinXP machine, but I keep getting
an Error 137, insufficent memory. Does anyone have a suggestion on what I
need to set, or fix?

Any help would be appreciated. Please post to the news group, as this
address doesn't have a mailbox associated with it to avoid spam.

Robert
N3LGC

SignalFerret wrote:
I'm trying to get Eznec ver 2 to run on a WinXP machine, but I keep getting
an Error 137, insufficent memory. Does anyone have a suggestion on what I
need to set, or fix?

I vaguely remember the firewall/virus-protection needs to
be disabled during installation. I'm sure Roy will respond.
--
73, Cecil, W5DXP

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

I could be wrong, and Roy will correct me if I am, but EZNEC seems to be
written in Visual Basic, or similar... might you need the run-time libraries
for an older edition?
And, he (Roy) mentions "double percision"--a nasty reality of basic (and
some Fortran compilers also), which seems to confirm my suspicions...

Regards,
John

"SignalFerret" wrote in message
news:JoW9e.26259$jd6.8685@trnddc07...
I'm trying to get Eznec ver 2 to run on a WinXP machine, but I keep
getting an Error 137, insufficent memory. Does anyone have a suggestion
on what I need to set, or fix?

Any help would be appreciated. Please post to the news group, as this
address doesn't have a mailbox associated with it to avoid spam.

Robert
N3LGC

precision even!!! before all the spelling freaks fall on me!

John

"John Smith" wrote in message
...
I could be wrong, and Roy will correct me if I am, but EZNEC seems to be
written in Visual Basic, or similar... might you need the run-time
libraries for an older edition?
And, he (Roy) mentions "double percision"--a nasty reality of basic (and
some Fortran compilers also), which seems to confirm my suspicions...

Regards,
John

"SignalFerret" wrote in message
news:JoW9e.26259$jd6.8685@trnddc07...
I'm trying to get Eznec ver 2 to run on a WinXP machine, but I keep
getting an Error 137, insufficent memory. Does anyone have a suggestion
on what I need to set, or fix?

Any help would be appreciated. Please post to the news group, as this
address doesn't have a mailbox associated with it to avoid spam.

Robert
N3LGC

"SignalFerret" wrote in message
news:JoW9e.26259$jd6.8685@trnddc07...
I'm trying to get Eznec ver 2 to run on a WinXP machine, but I keep
getting an Error 137, insufficent memory. Does anyone have a suggestion
on what I need to set, or fix?

Any help would be appreciated. Please post to the news group, as this
address doesn't have a mailbox associated with it to avoid spam.

Robert
N3LGC


Is that a DOS program? I recall upgrading to a Windows version, and think
it was 3.x.

Tam

Yes, it's the DOS version, and up grading is not in the budget this month.
Hence, the need to get this version working.

Robert N3LGC

"Tam/WB2TT" wrote in message
...

"SignalFerret" wrote in message
news:JoW9e.26259$jd6.8685@trnddc07...
I'm trying to get Eznec ver 2 to run on a WinXP machine, but I keep
getting an Error 137, insufficent memory. Does anyone have a suggestion
on what I need to set, or fix?

Any help would be appreciated. Please post to the news group, as this
address doesn't have a mailbox associated with it to avoid spam.

Robert
N3LGC


Is that a DOS program? I recall upgrading to a Windows version, and think
it was 3.x.

Tam

No, I am wrong about that being a problem...
I should have looked first...
Here is another guy with a problem with EZNEC 2.0 on Windows XP--however,
not the same problem...
http://lists.contesting.com/pipermai...ry/043902.html
So, it does run--with more or less success, on XP...
However, does setting the "compatibility option in the dos emulator of
Windows XP help with this problem? -- simply drop a cmd icon on your
desktop, right click the icon, pick properties, and set the "compatabiliy"
tab to windows 95 and run the program though this icon... might help....

Regards,
John
"SignalFerret" wrote in message
news:JoW9e.26259$jd6.8685@trnddc07...
I'm trying to get Eznec ver 2 to run on a WinXP machine, but I keep
getting an Error 137, insufficent memory. Does anyone have a suggestion
on what I need to set, or fix?

Any help would be appreciated. Please post to the news group, as this
address doesn't have a mailbox associated with it to avoid spam.

Robert
N3LGC

That was a common problem with DOS EZNEC programs running on modern
machines and the fix is simple. Drop me an email and I'll be glad to
send you instructions.

Although I'm glad to answer questions here which are of general interest
about EZNEC and its use, it's more appropriate to answer specific
support questions directly.

Roy Lewallen, W7EL

SignalFerret wrote:
I'm trying to get Eznec ver 2 to run on a WinXP machine, but I keep getting
an Error 137, insufficent memory. Does anyone have a suggestion on what I
need to set, or fix?

Any help would be appreciated. Please post to the news group, as this
address doesn't have a mailbox associated with it to avoid spam.

Robert
N3LGC

John Smith wrote:
I could be wrong, and Roy will correct me if I am, but EZNEC seems to be
written in Visual Basic, or similar... might you need the run-time libraries
for an older edition?

No, that's not the problem -- it's due to DOS not being able to properly
determine the size of a large amount of RAM. And the DOS versions were
written with the MS BASIC Professional Development System, not Visual
Basic. Windows versions of EZNEC (v. 3.0 and 4.0) are written in Visual
Basic, except the calculating engines and a few speed-critical main
program routines which are written in Fortran.

And, he (Roy) mentions "double percision"--a nasty reality of basic (and
some Fortran compilers also), which seems to confirm my suspicions...

Double precision isn't a "nasty reality" -- it's simply a way of storing
floating point variables. Normal precision floating point variables are
stored in four byte words, and consequently have a resolution of about
seven significant decimal digits. Double precision variables require 8
bytes and have about 15 significant digits of resolution. Fortran
additionally has a complex data type which requires twice as much
storage space, since each variable of that type has two parts. Some
compilers have additional, higher precisions available. The program
author can choose which data type to use for each individual variable.

Roy Lewallen, W7EL

Yes, you are correct. In "C"/C++ conversion is automatic (or generates a
compiler error prompting you to "cast" to another type) if there is the
slightest chance you will unintentionally lose precision...
If I go to VB or Fortran I tend to get a lot of math errors (which are not
caught by the compiler, but in real world use!) until I remember to
compensate and control my code better... double precision is used by
"C"/C++ (the "double"(integer) and "float"(floating point) variables) also
(you are right, it is related to the size, in bytes(bits), of the math
variable(s) in question), no problem--it is just more transparent in C.
And, you are correct again, "precision" is only a matter of where you wish
to "quit", and "double-double-precsion" and greater are able to be done,
either as a function of the compiler, hard code a routine directy in
assembly language yourself, or the programmer can institute them in the high
level code...
Visual Basic, Fortan, COBOL (yuck!), Pascal, "C", etc, etc are usually only
a matter of syntax, style, speed and preference... "C" is just my personal
preference...

Years ago it was common for Basic/VB to constantly have issues with math
variables (actually, changes to the functions in the OS) in each new release
of windows, I live in the past... frown

Warmest regards,
John

"Roy Lewallen" wrote in message
...
John Smith wrote:
I could be wrong, and Roy will correct me if I am, but EZNEC seems to be
written in Visual Basic, or similar... might you need the run-time
libraries for an older edition?

No, that's not the problem -- it's due to DOS not being able to properly
determine the size of a large amount of RAM. And the DOS versions were
written with the MS BASIC Professional Development System, not Visual
Basic. Windows versions of EZNEC (v. 3.0 and 4.0) are written in Visual
Basic, except the calculating engines and a few speed-critical main
program routines which are written in Fortran.

And, he (Roy) mentions "double percision"--a nasty reality of basic (and
some Fortran compilers also), which seems to confirm my suspicions...

Double precision isn't a "nasty reality" -- it's simply a way of storing
floating point variables. Normal precision floating point variables are
stored in four byte words, and consequently have a resolution of about
seven significant decimal digits. Double precision variables require 8
bytes and have about 15 significant digits of resolution. Fortran
additionally has a complex data type which requires twice as much storage
space, since each variable of that type has two parts. Some compilers have
additional, higher precisions available. The program author can choose
which data type to use for each individual variable.

Roy Lewallen, W7EL