FPU26 on FreeBSD
Bill W Smith Jr
last few days, I work with Peter Elsner and this is a continuation of
our problems.
To sum up: We have FPU26 runnig on FreeBSD 4.0 using ibcs2 and the
fansi terminal emulation. Color, linedraw, positioning.. all work. We
now have only two problems preventing immediate implementation:
1) the fansi terminfo that we were given apparently did not include
support for civis, cnorm and cvvis. This means the cursor cannot be
changed between hidden, underline and block. All attempts to decompile
the fansi we were given has failed, and the person we got it from no
longer has the .src. This is NOT a show stopper, but is annoying.
2) FoxPro is apparently adding the timezone offset (CST6CDT, +0500) to
all time calls, causing FoxPro to incorrectly report time. Dennis
Allen has indicated this problem and does not have a fix. I suspect we
are looking at a difference in the shared time libraries between SCO
Unix and FreeBSD. Dennis has suggested physically setting the system
clock to GMT time so FoxPro will display the correct time but I am
concerned how this will affect time-critical operations and use of
sys(2) (seconds since midnight) which we use. Dennis also suggested
replacing ALL calls to date() and time() with fndate() and fntime()
which we could make OS-aware to handle the difference. I would prefer
a fix to the problem.
If anyone can help please contact me or Peter <pe...@servplex.com>
-----------------------------------------------------------------------
Bill W Smith Jr mailto:bi...@servplex.com
ServPlex, Inc. - Software for the Distribution Industry
Vice President, System Design & Development
http://www.servplex.com ICQ:425524
(281) 955-2800 voice (281) 955-7564 fax
JanS
IBM unix ?
As far as the date thing goes, with FPU & FPD you are better off
using a function call for all date stuff ( the y2k thing ).
Thanks in advance
Jan Siegrist / jsie...@home.com
-----------------------------------------------------------
Got questions? Get answers over the phone at Keen.com.
Up to 100 minutes free!
http://www.keen.com
peter...@my-deja.com
necessary civis command to it, (the other's were there, why this one
was skipped is beyond me). And the cursor problem is now solved.
All that is left is the date issue...
In article <396dd98a....@news-server.houston.rr.com>,
Sent via Deja.com http://www.deja.com/
Before you buy.
TOYlet
Bill W Smith Jr
AS400.
Y2k is not now and never has been an issue on FPD and FPU. The only
issue was perception as it would accept 02/29/00 as valid because it
THOUGHT you meant 2/29/1900. If you typed 2/29/2000 it would correctly
report that as an invalid date. Dates in ALL xBase variants have
always been y2k-compatible.
On Wed, 12 Jul 2000 20:20:03 -0700, JanS
<jsiegris...@home.com.invalid> wrote:
>This is an unrelated question, will FPU run on an AS400 running
>IBM unix ?
>As far as the date thing goes, with FPU & FPD you are better off
>using a function call for all date stuff ( the y2k thing ).
>Thanks in advance
>Jan Siegrist / jsie...@home.com
---
Donal mailto:do...@brewich.com http://www.brewich.com/users/donal
SysAdmin of The Brewers' Witch BBS http://www.brewich.com
Modkinus Primus of soc.religion.paganism http://www.brewich.com/org/srp
RingMaster of The WebCircle WebRing http://www.brewich.com/webcircle
BW Internet Services http://www.bwis.com Pagan-owned and operated ISP
Dennis
The date issue. The problem with FPU on Linux is that the date/time is always
4/5 hours ahead of the system clock. The exact offset of the GMT. A hardware
problem.
My web site, dennisallen.com, does have a terminfo file for Linux. In fact,
there's a FAQ sheet on how to create FPU 2.6 code compatible with Linux.
Des
Didn't LUPDATE() suffer from a y2k thing ?
Des
"Bill W Smith Jr" <bi...@servplex.com> wrote in message
news:396f508a....@news-server.houston.rr.com...
Rush Strong
news:396f508a....@news-server.houston.rr.com...
> To the best of my knowledge, noone has suceeded in running FPU26 on
> AS400.
>
> Y2k is not now and never has been an issue on FPD and FPU. The only
> issue was perception as it would accept 02/29/00 as valid because it
> THOUGHT you meant 2/29/1900. If you typed 2/29/2000 it would correctly
> report that as an invalid date.
Uh . . . I sure hope not!
- Rush
Gene Wirchenko
>To the best of my knowledge, noone has suceeded in running FPU26 on
>AS400.
>
>Y2k is not now and never has been an issue on FPD and FPU. The only
>issue was perception as it would accept 02/29/00 as valid because it
>THOUGHT you meant 2/29/1900. If you typed 2/29/2000 it would correctly
>report that as an invalid date. Dates in ALL xBase variants have
>always been y2k-compatible.
Um, you got that reversed. There was no 1900-02-29. There was a
2000-02-29.
[snipped previous]
Sincerely,
Gene Wirchenko
Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.
Bill W Smith Jr
wrote:
>bi...@servplex.com (Bill W Smith Jr) wrote:
>
>>To the best of my knowledge, noone has suceeded in running FPU26 on
>>AS400.
>>
>>Y2k is not now and never has been an issue on FPD and FPU. The only
>>issue was perception as it would accept 02/29/00 as valid because it
>>THOUGHT you meant 2/29/1900. If you typed 2/29/2000 it would correctly
>>report that as an invalid date. Dates in ALL xBase variants have
>>always been y2k-compatible.
>
> Um, you got that reversed. There was no 1900-02-29. There was a
>2000-02-29.
Whatever! :)
Gene Wirchenko
>On Sat, 15 Jul 2000 03:30:58 GMT, ge...@shuswap.net (Gene Wirchenko)
>wrote:
>
>>bi...@servplex.com (Bill W Smith Jr) wrote:
>>
>>>To the best of my knowledge, noone has suceeded in running FPU26 on
>>>AS400.
>>>
>>>Y2k is not now and never has been an issue on FPD and FPU. The only
>>>issue was perception as it would accept 02/29/00 as valid because it
>>>THOUGHT you meant 2/29/1900. If you typed 2/29/2000 it would correctly
>>>report that as an invalid date. Dates in ALL xBase variants have
>>>always been y2k-compatible.
>>
>> Um, you got that reversed. There was no 1900-02-29. There was a
>>2000-02-29.
>
>Whatever! :)
That's the wrong blasé remark. You should have used
Whenever!
but do you care?
Whatever. <g>