| Author |
Open Error on Windows 2000
|
|
| Stephen Quinn 2006-06-17, 7:55 am |
| Drop this a bit
FILES=255
to around
FILES=127
unless your app actually needs 200+ files open
IIRC I've read here that S'87 doesn't support a lot of open files (ie > 15
CMIIW<g> )
> I used TLINK instead of PLINK86 to compile the source to produce the
> executable. I don't know if this helps.
Try it with Blinker
HTH
Steve
| |
| darkhrse@gmail.com 2006-06-17, 7:55 am |
| I'm trying to run a Clipper Summer '87 program on a Windows 2000 Server
(SP4) machine but as soon as it attempts to open the 8th table and 10th
index file, I get the open error (0) error. This happens immediately
after the USE statement before the NETERR check.
I've already modified CONFIG.NT to contain the FILES=255 line and the
CLIPPER environment variable is already set to F150;V28;R32;E460;I100.
I used TLINK instead of PLINK86 to compile the source to produce the
executable. I don't know if this helps.
Anyway, hope you guys can help me. Greatly appreciate it!
| |
| darkhrse@gmail.com 2006-06-17, 7:55 am |
| Thanks for replying.
I did your suggestion to change 255 to 127 but I still get the same
error.
I unfortunately don't have a copy of Blinker but since your reply
suggested that perhaps the linker may have something to do with it, I
tried re-linking the object files using PLINK86 this time but I still
get the same error.
I'm in the process of considering to get Blinker. Is this compatible
with S'87 though?
Stephen Quinn wrote:
> Drop this a bit
> FILES=255
>
> to around
> FILES=127
>
> unless your app actually needs 200+ files open
>
> IIRC I've read here that S'87 doesn't support a lot of open files (ie > 15
> CMIIW<g> )
>
> Try it with Blinker
>
> HTH
> Steve
| |
| Stephen Quinn 2006-06-17, 7:55 am |
|
You could go to www.blinkinc.com and read what compilers it supports
(IIRC V5.1 does but I can't get to my machine with it on at the moment)
and/or
d/l thedemo version and try it to see if it fixes your problem.
HTH
Steve
| |
| E. Fridman 2006-06-17, 7:55 am |
| > Could it be that when I run CMD in Windows 2000, it doesn't actually
> read CONFIG.NT? If this is the case, it doesn't initialize the
> environment to allow 127 file handles. How do I test this?
Where is your CONFIG.NT located? What directory?
It should be in %SystemRoot%\SYSTEM32\
| |
| darkhrse@gmail.com 2006-06-17, 7:55 am |
| Here's a PRG I created to test the problem outside the system, just to
try to isolate the problem:
----------------------------
01 Ans = "Y"
02
03 Clear
04 @ 10, 10 say "Continue? (Y/N) " Get Ans
05 Read
06
07 If Upper(Ans) = "N"
08 quit
09 EndIf
10
11 Select 12
12 Use sysuser Index sysx
13
14 Select 1
15 Use members Index memx
16
17 Select 2
18 Use loans Index loansx
19
20 Select 3
21 Use gl_mastr Index glmx
22
23 Select 4
24 Use gl_tran1 Index gl1x
25
26 Select 5
27 Use gl_tran2 Index gl2x, gl2y
28
29 Select 6
30 Use tran_fl Index tranx, trany
31
32 Select 7
33 Use numbers
34
35 @ 11, 10 say "Complete!"
----------------------------
The original error replicated here occurs at line 30. The actual error
is "open error tranx.NTX (0)".
To isolate the problem, I changed line 27 to Use gl_tran2, removing the
indexes, to see if line 30 will still cause a problem. When I ran the
program, it completed without any problems. This proves that the table
tran_fl and the indexes tranx and trany are valid and uncorrupted.
When I restored line 27 to its original statement, the error
reappeared.
To reiterate, I have FILES=127 in my CONFIG.NT and the CLIPPER
environment variable is set to F150;V28;R32;E460;I100.
I've tried linking the OBJ files using TLINK, PLINK86 and the demo
version of BLINKER with all of them producing the same results.
Could it be that when I run CMD in Windows 2000, it doesn't actually
read CONFIG.NT? If this is the case, it doesn't initialize the
environment to allow 127 file handles. How do I test this?
Many thanks to all who reply!
Stephen Quinn wrote:
>
> Does the path where your files reside have a space it in??
> Eg
> C:\Program Files\MyApp
>
> If so move it to a path where there are no spaces in it.
> Eg
> C:\MyApp
>
> The only other thing I can think is that the file is corrupt.
>
> You've said that you recreate it to make sure it exists but are you sure the
> DATA in the DBF isn't corrupt which might be causing your index to be corrupt.
>
> HTH
> Steve
| |
| Stephen Quinn 2006-06-17, 7:55 am |
|
> I don't understand why a simple USE file8 INDEX ntx10, ntx11 will cause
> an "open error ntx10.NTX (0)" error. And the program doesn't even allow
> NETERR to catch the problem.
Does the path where your files reside have a space it in??
Eg
C:\Program Files\MyApp
If so move it to a path where there are no spaces in it.
Eg
C:\MyApp
The only other thing I can think is that the file is corrupt.
You've said that you recreate it to make sure it exists but are you sure the
DATA in the DBF isn't corrupt which might be causing your index to be corrupt.
HTH
Steve
| |
| Ross McKenzie 2006-06-17, 7:55 am |
| On 14 Jun 2006 23:32:48 -0700, darkhrse@gmail.com wrote:
>Thanks again for replying.
>
>Sorry for being a pest but I downloaded the Blinker demo and it did
>support S'87. However the problem persists.
>
>I don't understand why a simple USE file8 INDEX ntx10, ntx11 will cause
>an "open error ntx10.NTX (0)" error.
Hi.
Is the file "NTX10.NTX" actually present?
Regards,
Ross McKenzie
ValuSoft
Melbourne Australia
valusoft AT optusnet DOT com DOT au
| |
| darkhrse@gmail.com 2006-06-17, 7:55 am |
| Hi,
Yes, NTX10.NTX does exist. Just for the heck of it, I've rebuilt this
index over and over again just to make sure it's there, it's not in
read-only, and it's a valid index file. Besides, I would have gotten a
different open error code number if the file didn't exist, I think.
Ross McKenzie wrote:
> On 14 Jun 2006 23:32:48 -0700, darkhrse@gmail.com wrote:
>
>
> Hi.
>
> Is the file "NTX10.NTX" actually present?
>
>
> Regards,
>
> Ross McKenzie
> ValuSoft
> Melbourne Australia
>
> valusoft AT optusnet DOT com DOT au
| |
| darkhrse@gmail.com 2006-06-17, 7:55 am |
| Thanks again for replying.
Sorry for being a pest but I downloaded the Blinker demo and it did
support S'87. However the problem persists.
I don't understand why a simple USE file8 INDEX ntx10, ntx11 will cause
an "open error ntx10.NTX (0)" error. And the program doesn't even allow
NETERR to catch the problem.
I'll have to look at this problem in another light...
Stephen Quinn wrote:
> You could go to www.blinkinc.com and read what compilers it supports
> (IIRC V5.1 does but I can't get to my machine with it on at the moment)
> and/or
> d/l thedemo version and try it to see if it fixes your problem.
>
> HTH
> Steve
| |
| darkhrse@gmail.com 2006-06-17, 7:55 am |
| E. Fridman wrote:
>
> Where is your CONFIG.NT located? What directory?
>
> It should be in %SystemRoot%\SYSTEM32\
Yes, my CONFIG.NT is right at that path.
| |
| Stephen Quinn 2006-06-17, 7:55 am |
| > Could it be that when I run CMD in Windows 2000, it doesn't actually
> read CONFIG.NT? If this is the case, it doesn't initialize the
> environment to allow 127 file handles. How do I test this?
Nope - the OS reconises it's a 16 bit .exe and runs it in a command.com shell
which gets it's defaults from the <app>.pif file which reads the config.nt file
(although you might check this in the 'Properties' of the icon on your desktop).
HTH
Steve
| |
| E. Fridman 2006-06-17, 7:55 am |
| <<< One of the advantages with Blinker is that you can burn the Clipper
environment into the exe. Then you no longer need to be concerned with
Config files or Autoexc files..>>>
Not true. You still need CONFIG.{SYS|NT} setting "FILES=..."
| |
| Fred Zuckerman 2006-06-17, 7:55 am |
| I use S'87 with Blinker 5.0 on WXP and W2k systems.
Many times I have 10 dbf's & 20 ntx's open at the same time.
One of the advantages with Blinker is that you can burn the Clipper
enviroment into the exe. Then you no longer need to be concerned with Config
files or Autoexc files. I always set the enviro to: F150;E0;R20.
Fred
"E. Fridman" <pm771.am@gmail.com> wrote in message
news:1150381902.285922.257430@h76g2000cwa.googlegroups.com...
>
> Where is your CONFIG.NT located? What directory?
>
> It should be in %SystemRoot%\SYSTEM32\
>
| |
| E. Fridman 2006-06-17, 7:55 am |
| You may want to post your _exact_ CONFIG.NT and AUTOXEC.NT files here.
May be there is an extra space somewhere. Other than that - I'm out of
ideas.
---------------------------------------------------------------------------------
darkhrse@gmail.com wrote:
> E. Fridman wrote:
>
> Yes, my CONFIG.NT is right at that path.
| |
| Speedy 2006-06-18, 6:55 pm |
| Try FILES=131 in config.nt
255 I belive is to high value.
If I remember correctly it is 250 max.
And there was some DOS bug in the old days, so 131 was a good number, and it
never failed me ;-)
I am convinced this is a CONFIG.NT and not application problem.
gl hf
Speedy
<darkhrse@gmail.com> wrote in message
news:1150278856.014410.78870@p79g2000cwp.googlegroups.com...
> I'm trying to run a Clipper Summer '87 program on a Windows 2000 Server
> (SP4) machine but as soon as it attempts to open the 8th table and 10th
> index file, I get the open error (0) error. This happens immediately
> after the USE statement before the NETERR check.
>
> I've already modified CONFIG.NT to contain the FILES=255 line and the
> CLIPPER environment variable is already set to F150;V28;R32;E460;I100.
>
> I used TLINK instead of PLINK86 to compile the source to produce the
> executable. I don't know if this helps.
>
> Anyway, hope you guys can help me. Greatly appreciate it!
>
| |
| Bambang P 2006-06-19, 7:55 am |
| On 15 Jun 2006 01:40:37 -0700, darkhrse@gmail.com wrote:
>26 Select 5
>27 Use gl_tran2 Index gl2x, gl2y
>28
> .....
>To isolate the problem, I changed line 27 to Use gl_tran2, removing the
>indexes, to see if line 30 will still cause a problem. When I ran the
>program, it completed without any problems. This proves that the table
>tran_fl and the indexes tranx and trany are valid and uncorrupted.
>
>When I restored line 27 to its original statement, the error
>reappeared.
>
you can try to separate the index opening statement with the dbf
opening statement
Use gl_tran2
if neterr()
? "Failed open gl_tran2.dbf"
endif
set Index to gl2x, gl2y
Actually, I don't think it helps but it is a good practice (mainly for
multi user environment) to open the index file(s) after the dbf file.
--
Bambang P
http://bpranoto.tripod.com
--
Posted via a free Usenet account from http://www.teranews.com
| |
| LHSoft@gmail.com 2006-06-24, 7:55 am |
| Hi,
Sorry to jump in this late.
To me it seems that you are trying to use 17 filehandles, the dbf:s and
the ntx:s
With Summer 87 there is a limit of 20 handles if I remeber correctly,
and the exe itself uses 1 or more if it's overlayed, the operating
system uses a minimum of 4, so you are running out of handles. I had
the same problem in the past, but found a solution, now I can't
remember if it was the Funcky lib or someother obj or lib that I used
with Blinker that made it possible to increese the handles, the
function that I had to call in the beginning of the program was
SetHandles(number_of_handles).
I might have those needed obj's or lib's somewhere on 5.25 inch
floppys, the problem is that I don't have any PC with floppy ability
anymore. Maybe somebody else can remember this problem and supply you
with the needed pieces.
Lasse Holm
Bambang P wrote:
> On 15 Jun 2006 01:40:37 -0700, darkhrse@gmail.com wrote:
>
>
> you can try to separate the index opening statement with the dbf
> opening statement
>
> Use gl_tran2
> if neterr()
> ? "Failed open gl_tran2.dbf"
> endif
> set Index to gl2x, gl2y
>
> Actually, I don't think it helps but it is a good practice (mainly for
> multi user environment) to open the index file(s) after the dbf file.
>
> --
> Bambang P
> http://bpranoto.tripod.com
>
> --
> Posted via a free Usenet account from http://www.teranews.com
| |
| E. Fridman 2006-06-24, 7:55 am |
| <<< With Summer 87 there is a limit of 20 handles if I remeber
correctly ... >>>
>From Summer'87 NG (http://www.ousob.com/ng/sum87/ng7b162.php):
A Clipper compiled program can open a maximum of 15 files (255 with
DOS 3.3.)
| |
| Nick Ramsay 2006-06-24, 7:55 am |
| On 21 Jun 2006 13:25:44 -0700, "E. Fridman" <pm771.am@gmail.com>
wrote:
><<< With Summer 87 there is a limit of 20 handles if I remeber
>correctly ... >>>
>
>
> A Clipper compiled program can open a maximum of 15 files (255 with
>DOS 3.3.)
While that is true in a strict sense, you still need to inform the OS
via CONFIG.SYS / CONFIG.NT that you want to open more than the
default number of handles (20 & 40 respectively).
There's also the small but vital matter of the clipper environment
variable being set to reflect the increased requirements.
SET CLIPPER=Fnnn
| |
| Karel Zámečník 2006-06-24, 7:55 am |
| set
FILES=240
in CONFIG.NT.
Run command line with
COMMAND.COM
(Start - Run).
Run application with command line switch
MYAPPLICATION.EXE //F:200
"Speedy" <speedy@nowhere.fbi> píše v diskusním příspěvku
news:4495ce01$1@proxy.mimer.no...
> Try FILES=131 in config.nt
> 255 I belive is to high value.
> If I remember correctly it is 250 max.
> And there was some DOS bug in the old days, so 131 was a good number, and
> it never failed me ;-)
>
> I am convinced this is a CONFIG.NT and not application problem.
>
> gl hf
> Speedy
>
>
> <darkhrse@gmail.com> wrote in message
> news:1150278856.014410.78870@p79g2000cwp.googlegroups.com...
>
>
|
|
|
|