Hi Bart,
Yes, that has been in the kernel since the initial implementation by
Ron Cemer. It used to work on fnodes but now updates the SFTs.
These routines (mainly merge_file_changes() in fatfs.c) could be moved
to share.c if the hooks from RBIL table 01636 were implemented.
Given the
Hi Christian,
I know about the OEM ID and the DOS-C release string which can be
retrieved by Int21.33FF. I don't see how SHARE could use that...
I suppose there's no way to get the kernel's build number for SHARE then?
The revision number (eg 38 for 2038) is returned in BL
if you call int
Given the number of hooks, some of which are not even documented,
I would say that the current implementation of SHARE is smoother.
I agree.
This format of share exe hooks table about MS SHARE lists:
- a routine of unknown purpose, probably not called
Since SHARE of MS-DOS 3.3+ is
Am 06.07.2009, 10:00 Uhr, schrieb Eric Auer e.a...@jpberlin.de:
Hi Christian,
I know about the OEM ID and the DOS-C release string which can be
retrieved by Int21.33FF. I don't see how SHARE could use that...
I suppose there's no way to get the kernel's build number for SHARE
then?
Please explain in what way Win 3 uses virtual(?) machine numbers
and why supporting them is needed to get a Win compatible SHARE.
MS-DOS usually sets the net machine number (offset 1Eh of SDA, table at
Int21.5D0B) to zero (indicating local) inside its Int21 dispatcher,
unless the server
Over the weekend, the ISP that handles our DNS did an upgrade and
unfortunately it didn't happen smoothly, so they are effectively down right
now. Based on what we know, this may take some time before they can correct
it.
Until this is fixed, www.freedos.org will not be resolvable in DNS, so it
Hello all,
It is true that no DOS provides pipes. HX makes up for this by creating a
new file and opening 2 instances (1 read only)--per the HX docs that I
looked at on Sunday. If SHARE is not loaded, this ostensibly may not
work as expected.
Christian:
Is your file sharer ready yet (able to
