| Terence 2006-07-21, 9:58 pm |
| Bogus:adj: Counterfeit, spurious, fake.
Implicitly intentional. Never meaning "mistaken", "incorrect",
"debatable".
Kevin wrote, among other paragraphs, the following, to whic I have
added comments.
>YOU HAD A FILE HANDLE LIMITATION -- NOT AN FCB LIMITATION.
Kevin is correct in this observation ; my terminolgy DID treat FCB's
and DCB's as the same thing.
I plead this is because I always accessed the DCB created as part of
the FCB to get at and modify the control bits and disc unit. (This was
for general-purpose sorting of files). And I was using assembled
machine-code-called functions to do so, underlying the Fortran file
sorting algorithm code.
I didn't use file handles, but the addresses of the FCBS, which amounts
to the same thing. A handle is just a number that points to an array of
addresses of file control blocks, within predetermined available spaces
for addresses and blocks. Some of the lower handle numbers are
pre-assigned.
>And you could have solved it by creating a CONFIG.NT file in the appropriate
>place (usually SYSTEM32 under your windows directory) and putting FILES=32
>into it.
Now, this is the strange thing! It never worked with XP!
A lot of people in the Lahey Forum worked on this to try to resolve the
problem.
Playing with config.nt in an XP machine didn't change anything!
A special test program in Fortran was written and used to open and
close files and run on many XP computers, with the modified config.nt
file. The program found the defined requested new limit in MS 95, 98,
(using config.sys) 2000 and NT (using config.nt), and essentially
unlimited in native windows compilations, but stubbornly stopped at 20
units on XP systems. The conclusion was that XP was ignoring the
files=32 instruction in the config.nt file and had a fixed pre-assigned
value.
All this is covered in the Lahey Forum message file which still exists
>You mention CONFIG.SYS in the same sentence as CONFIG.NT,
Yes, but correctly; they were not equated to each other.
MS 2000, and NT uses the .nt suffix, the others earlier systems use
..sys.
But what XP systems use is a mystery.
>when it is clear the XP neither uses nor even parses CONFIG.SYS.
Which I did not claim. And of course I always knew this, since putting
in many, many MS NT and MS 2000 systems before ever seeing an XP
machine
>Then you claim that XP "disregards" the instruction to increase to 32.
> But did you tell it FCBS=32 or FILES=32?
How? nobody ever in the Forum ever found out how to do this in a way
that XP would use over 20 handles in a DOS emulation!.
> Did you relize that the DOS virtual machines opened
>prior to that will not automatically change? Did you realize that the
>CONFIG.NT must be in the SYSTEM32 directory (or wherever the NTVDM is
>being launched from, if the defaults have been over-ridden)?
Yes to all. These are basic requirements for using DOS on Windows
machines.
Whatever other faults I have, this was supposed to be my speciality.
(Know how to get RS232C ports to work in XP system DOS emulations?>
This was never solved either).
Actually we use both command.com and cmd.exe DOS emulator program calls
as appropriate, since the executions differ enormously.
Terence Wright
|