| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | DOSFINDFIRST HELP |
DL> > What I am asking for is this: IS there anyone who knows of any system > bugs (under 2.1 with LS 3.0) with the DosFind??? functions? DL> JP> You need the latest CSDs for LAN Requester. One of the fixes listed JP> is that programs that attempted to have more than one JP> DosFindFirst/Next/Close handle open at once would hang the entire JP> machine. JP> This was a problem in the installable file system, as far as I can JP> gather. JP> I can vouch for this. I used to have dreadful trouble remembering not JP> to do DIR /S on a network drive. After installing the patch JP> everything worked fine. Thank you for you reply. I had a response from someone on CServe as well regarding this. I was about to abandon all hope. I was going mad trying to find a bug in my code. I knew it wasn't an access violation, wasn't the stack or anything like that because thos things get trapped. I was looking for subtle abuses of the API calls that I have found to corrupt the system before, but I find nothing here. I suppose those 100 lines of code were a desperate act. Have you ever noticed that iterated calls to DosCloseNPipe with an invalid handle will trap the whole system after about 70 iterations? That one was hard to catch too, but at least it didn't kill the debugger while I was trying to trace it. I discover it one day when a server was down and my client app was trying to open the pipe. DosCloseNPipe was being called even when DosConnectNPipe failed. I carelessly ignored the return code from the close and never noticed a problem figuring it would just return a harmless "ERROR_BAD_HANDLE" anyway... I learned a valuable lesson with that problem and was looking so hard for something similar in the code with the find first problem. I was looking so har I didn't even think of blaming the system . I am happy to report that since installing 7045 (& fix to NET.EXE) it is lookin stable now. The swapper never gets larger than 4MB on the 12MB machine. It used to get up to about 7-8MB before it hung. Seems clean now. ___ * MR/2 1.52 NR * MS Windows : XT power for your 386/486 machine! --- WILDMAIL!/WC v4.11* Origin: Freezing Point BBS - WDNet HQ - Mpls MN: (1:282/85.0) SEEN-BY: 12/2442 620/243 624/50 632/348 640/820 690/660 711/409 410 413 430 SEEN-BY: 711/807 808 809 934 942 949 712/353 515 713/888 800/1 @PATH: 282/85 1 270/101 396/1 3615/50 229/2 12/2442 711/409 808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.