file handles and pdisk (AREV Specific)
At 11 MAR 1998 11:07:01PM John Davy wrote:
Pdisk appears to use a file handle and not release it.
Is there a way to close such handles, Flush has no effect
Thanks
John D
At 12 MAR 1998 12:33PM Aaron Kaplan wrote:
Are you PDISKing back to LPTx?
What version of ARev?
How are you determining this?
At 12 MAR 1998 08:58PM Matt - MGA wrote:
I know in our applications when we do a PDISK out to a DOS file, after the output is finished, we have to do a PERFORM "PDISK PRN" in order to close the file handel. Also, after we have done this, we usually do a PERFORM "SUSPEND EXIT DIR *.BAT" just to make sure the file handle is closed. We use DIR *.BAT because there are about 10 .BAT files in our revboot directory, so it's a real quick command to ensure that the file has closed properly.
Hope that helps.
Matt Sorrell
MGA, Inc.
At 13 MAR 1998 01:05PM Victor Engel wrote:
To get even faster, create an empty bat file called NULL.BAT and call it.
At 15 MAR 1998 10:24PM John Davy wrote:
I'm Pdisk 'ing back to prn
I have dtermined that file handles are not being released by creating a loop and pdisking to prn about 200 times
The max number of times pdisk can be executed is determined by the number of file handles set in config.sys
After this the program crashes and has to be killed off
At 16 MAR 1998 11:06AM Aaron Kaplan wrote:
People have reported similar things before, and while I don't dispute them in general, I have some troubles with your description of this problem.
When ARev prints, it prints using the INT21 write to file handle. (This is part of the reason there are some issues printing in 95 and NT). PRN is a reserved DOS handle and is not consistantly re-opened or reallocated. If I were to PDISK PRN, I'm trying to open the PRN handle and DOS will either allow or disallow me access to this handle. It will not attempt to create hundreds of them.
I also wrote a small program the looped 1000 times, PDISK PRN inside and did nothing.
I can't think of any way to PDISK a few hundred times on the same handle without closing it first. A real file will be open, so it will use the same handle. PRN is always open so the system forces an overwrite.
PDISK is just a shell around the SETPTR program anyway.
SetPtr( FileName, Action)FileName is the file name
Action=1 means overwrite file unconditionally
Action 1 means return back in status if file exists.
Action returns back error codes
Action Sprezzatura, Inc.[/url]
At 16 MAR 1998 06:51PM John Davy wrote:
Hi Aaron,
Following is a little routine that will crash my system everytime
sometimes dropping me straight out of arev, sometimes scrolling the message
QUICKDEX MFS
running up the screen. I have been unable to reach 200, and when I reduce the number of files handles in the config.sys this number decreases
for i=1 to 1000
PERFORM "pdisk prn (s)"print @(1,1):i:next
I guess I should say that I am using Arev 2.11 on a windows95 box
Many Thanks for taking the time to look at this problem
John Davy
At 16 MAR 1998 10:50PM Victor Engel wrote:
My system crashes as well. Actually, it doesn't crash but puts up an out of file handles message. Then I can't even do something simple like PC to get a DOS prompt. Furthermore, adding the (O) option netted the same result.
At 17 MAR 1998 10:33AM Aaron Kaplan wrote:
I ran the same program when I posted and it zipped right up to 1000, pretty quick. I decided to try varying versions of ARev and noticed that 2.01 was almost a second between tries while 2.10 was blindingly fast. $SETPTR was different, and there were some changes related to file handles in 2.12, which I could have copied down.
You might want to try this. Get the ARev 2.12 Maitenance Release and apply it to a back-up of your system. Copy in the $SETPTR from the 2.12 into the 2.11 and see if that changes anything.
At 17 MAR 1998 12:08PM Victor Engel wrote:
The version I tried it on was HR-1 5.5, which, theoretically is Arev 3.02. I wouldn't say PDISK PRN went blazingly fast. However, it did execute several per second. The code at the end of $SETPTR is ASM_SETPTR.ASM_10:50:46 06 AUG 1991_AREV*2.11.46
At 18 MAR 1998 04:42AM John Davy wrote:
Hi,
Thanks for your patience with this, I really appreciate the help.
I have a copy of ver 2.12 that I will try this on and get back to you in a day or so
Thanks again,
John
At 19 MAR 1998 02:31AM John Davy wrote:
Hi,
Sorry but this didn't seem to help
I did notice that the $setptr prog in verbs was not updated by the
2.12 maintenance update.
Is there some other component that it may interact with?
My system is running stand alone (on my c: drive) under win 95
The system was previously bumped for a number of users but is now only used by me.
The network driver is set to non networking
My Pc is attached to a netware 3.12 network
Most of the above is probably not related since I have a number of clients reporting this problem.
Our application performs a pdisk at the beginning and end of each report.
Any other Ideas?
Thanks for your help so far
John
At 09 SEP 1998 10:48PM H. Alex Cravero wrote:
I have tryed all the hints in this pages and nothing will clear the file handles.
I used 255 files in the config.sys, then PERFORM "SUSPEND EXIT CLS" this with PDISK and also SETPRINTER etc.. The message "Out of file handles" will show after the 255 files have been used.
I am trying something else and if successful will let you know.