Re: [OT] Did you try ReactOS?

Actually, I am the one, who was talking about those "strange" and "weird"
TDI simularities.

Aleksey, take a look at your version of Microsoft WinDDK TDI.H include file,
in my case the path is C:\WinDDK\6000\inc\api\tdi.h

Then, take a look at ReacOS version of include file:
ReactOS-0.3.3-REL-src\ReactOS-0.3.3\include\ddk\TDI.H

Browse over definitions. Look for several defines for tags,

{MICROSOFT
// These are tags that transports pass to ndis as a first param of
NdisAllocatePacketPoolEx
// api. Ndis uses this as pooltag for allocating packet pools for that
transport.
#define NDIS_PACKET_POOL_TAG_FOR_NWLNKIPX 'iPDN'
#define NDIS_PACKET_POOL_TAG_FOR_NWLNKSPX 'sPDN'
#define NDIS_PACKET_POOL_TAG_FOR_NWLNKNB 'nPDN'
#define NDIS_PACKET_POOL_TAG_FOR_TCPIP 'tPDN'
#define NDIS_PACKET_POOL_TAG_FOR_NBF 'bPDN'
#define NDIS_PACKET_POOL_TAG_FOR_APPLETALK 'aPDN'
}

{ReacOS
#define NDIS_PACKET_POOL_TAG_FOR_NWLNKIPX 'iPDN'
#define NDIS_PACKET_POOL_TAG_FOR_NWLNKSPX 'sPDN'
#define NDIS_PACKET_POOL_TAG_FOR_NWLNKNB 'nPDN'
#define NDIS_PACKET_POOL_TAG_FOR_TCPIP 'tPDN'
#define NDIS_PACKET_POOL_TAG_FOR_NBF 'bPDN'
#define NDIS_PACKET_POOL_TAG_FOR_APPLETALK 'aPDN'
}

Look at several structures,

{MICROSOFT
typedef UNALIGNED struct _TA_ADDRESS {
USHORT AddressLength; // length in bytes of Address[] in this
USHORT AddressType; // type of this address
UCHAR Address[1]; // actually AddressLength bytes long
} TA_ADDRESS, *PTA_ADDRESS;
}

{ReacOS
typedef struct _TA_ADDRESS {
USHORT AddressLength;
USHORT AddressType;
UCHAR Address[1];
} TA_ADDRESS, *PTA_ADDRESS;
}

Look at defines for strings,

{MICROSOFT
//
// define some names for the EAs so people don't have to make them up.
//
#define TdiTransportAddress "TransportAddress"
#define TdiConnectionContext "ConnectionContext"
#define TDI_TRANSPORT_ADDRESS_LENGTH (sizeof (TdiTransportAddress) - 1)
#define TDI_CONNECTION_CONTEXT_LENGTH (sizeof (TdiConnectionContext) - 1)
}

{ReacOS
#define TdiTransportAddress "TransportAddress"
#define TdiConnectionContext "ConnectionContext"
#define TDI_TRANSPORT_ADDRESS_LENGTH (sizeof(TdiTransportAddress) - 1)
#define TDI_CONNECTION_CONTEXT_LENGTH (sizeof(TdiConnectionContext) - 1)
}

Look at address types,

{MICROSOFT
//
// Known Address types
//
#define TDI_ADDRESS_TYPE_UNSPEC ((USHORT)0) // unspecified
#define TDI_ADDRESS_TYPE_UNIX ((USHORT)1) // local to host (pipes,
portals)
#define TDI_ADDRESS_TYPE_IP ((USHORT)2) // internetwork: UDP, TCP,
etc.
#define TDI_ADDRESS_TYPE_IMPLINK ((USHORT)3) // arpanet imp addresses
#define TDI_ADDRESS_TYPE_PUP ((USHORT)4) // pup protocols: e.g. BSP
#define TDI_ADDRESS_TYPE_CHAOS ((USHORT)5) // mit CHAOS protocols
#define TDI_ADDRESS_TYPE_NS ((USHORT)6) // XEROX NS protocols
#define TDI_ADDRESS_TYPE_IPX ((USHORT)6) // Netware IPX
#define TDI_ADDRESS_TYPE_NBS ((USHORT)7) // nbs protocols
#define TDI_ADDRESS_TYPE_ECMA ((USHORT)8) // european computer
manufacturers
#define TDI_ADDRESS_TYPE_DATAKIT ((USHORT)9) // datakit protocols
#define TDI_ADDRESS_TYPE_CCITT ((USHORT)10) // CCITT protocols, X.25 etc
#define TDI_ADDRESS_TYPE_SNA ((USHORT)11) // IBM SNA
#define TDI_ADDRESS_TYPE_DECnet ((USHORT)12) // DECnet
#define TDI_ADDRESS_TYPE_DLI ((USHORT)13) // Direct data link
interface
#define TDI_ADDRESS_TYPE_LAT ((USHORT)14) // LAT
#define TDI_ADDRESS_TYPE_HYLINK ((USHORT)15) // NSC Hyperchannel
#define TDI_ADDRESS_TYPE_APPLETALK ((USHORT)16) // AppleTalk
#define TDI_ADDRESS_TYPE_NETBIOS ((USHORT)17) // Netbios Addresses
#define TDI_ADDRESS_TYPE_8022 ((USHORT)18) //
#define TDI_ADDRESS_TYPE_OSI_TSAP ((USHORT)19) //
#define TDI_ADDRESS_TYPE_NETONE ((USHORT)20) // for WzMail
#define TDI_ADDRESS_TYPE_VNS ((USHORT)21) // Banyan VINES IP
#define TDI_ADDRESS_TYPE_NETBIOS_EX ((USHORT)22) // NETBIOS address
extensions
#define TDI_ADDRESS_TYPE_IP6 ((USHORT)23) // IP version 6
#define TDI_ADDRESS_TYPE_NETBIOS_UNICODE_EX ((USHORT)24) // WCHAR
Netbios address
}

{ReacOS
#define TDI_ADDRESS_TYPE_UNSPEC 0
#define TDI_ADDRESS_TYPE_UNIX 1
#define TDI_ADDRESS_TYPE_IP 2
#define TDI_ADDRESS_TYPE_IMPLINK 3
#define TDI_ADDRESS_TYPE_PUP 4
#define TDI_ADDRESS_TYPE_CHAOS 5
#define TDI_ADDRESS_TYPE_NS 6
#define TDI_ADDRESS_TYPE_IPX 6
#define TDI_ADDRESS_TYPE_NBS 7
#define TDI_ADDRESS_TYPE_ECMA 8
#define TDI_ADDRESS_TYPE_DATAKIT 9
#define TDI_ADDRESS_TYPE_CCITT 10
#define TDI_ADDRESS_TYPE_SNA 11
#define TDI_ADDRESS_TYPE_DECnet 12
#define TDI_ADDRESS_TYPE_DLI 13
#define TDI_ADDRESS_TYPE_LAT 14
#define TDI_ADDRESS_TYPE_HYLINK 15
#define TDI_ADDRESS_TYPE_APPLETALK 16
#define TDI_ADDRESS_TYPE_NETBIOS 17
#define TDI_ADDRESS_TYPE_8022 18
#define TDI_ADDRESS_TYPE_OSI_TSAP 19
#define TDI_ADDRESS_TYPE_NETONE 20
#define TDI_ADDRESS_TYPE_VNS 21
#define TDI_ADDRESS_TYPE_NETBIOS_EX 22
#define TDI_ADDRESS_TYPE_IP6 23
#define TDI_ADDRESS_TYPE_NETBIOS_UNICODE_EX 24
}

This is just a few copypastes from headers. It seems like ReacOS version is
just a quick copy of Microsoft TDI.H file, with removed comments, and
reordered definitions of strctures.

--
Volodymyr
NG tips:
http://msmvps.com/blogs/v_scherbina/pages/microsoft-newsgroups-tips.aspx
"Don Burn" <burn@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:uB1LVexTIHA.3400@xxxxxxxxxxxxxxxxxxxxxxx
I was not the one to comment on TDI, my comments are on other parts of the
code. Also, I did not say I would sue, I point out that there is no value
in a firm to sure an open source project since it just wastes money. I
will standby that the last time I looked I found many places that were too
close to the stolen Windows source for coincidence, and the fact that your
project was using Bo Branten';s GNU ntifs.h which is primarily stolen


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply




"Aleksey Bragin" <Aleksey Bragin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:B702E896-5278-46BE-A7C3-614FE60C3FB3@xxxxxxxxxxxxxxxx
I'm quite surprised about your discussions here.

Have a look at our tdi.sys driver:
http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/network/tdi/
it's almost empty, most functions are just stubbed. What kind of binary
1:1
similarity and comments(!) match are you speaking about, if the whole
tdi's
source code takes only 8 kilobytes?

It's nothing near real windows's TDI driver.

That's amazing how you all went further speaking about sueing our project
for having an empty driver with stubs, whose names correspond to the
exported
functions list of a windows tdi.sys driver!

With the best regards,
Aleksey Bragin
ReactOS Project Lead
http://www.reactos.org
Email: aleksey at reactos dot org

"Don Burn" wrote:

Yes even to the point of mis-spellings in the comments!


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

"Volodymyr Shcherbyna" <v_scherbina@xxxxxxxxxxxxxxx> wrote in message
news:%23y3Uv1uTIHA.4532@xxxxxxxxxxxxxxxxxxxxxxx
No, I am talking about identical sources.

--
Volodymyr
NG tips:
http://msmvps.com/blogs/v_scherbina/pages/microsoft-newsgroups-tips.aspx

"Kerem Gümrükcü" <kareem114@xxxxxxxxxxx> wrote in message
news:exRtJzuTIHA.4656@xxxxxxxxxxxxxxxxxxxxxxx
Hi Volodymyr,

do you mean binary-level identical, so that you could
take the image and run it on a windows e.g. 2000
System. The exports must be the same, since
they aim to be binary compatible to windows
systems, in majority to drivers, but are the algo's
the same, the internals bit-to-bit identical to ms
implementations? I mean they cant be 100% the
same, depending on the comilers output, but how
identical are they?


Regards

Kerem

--
-----------------------
Beste Grüsse / Best regards / Votre bien devoue
Kerem Gümrükcü
Microsoft Live Space: http://kerem-g.spaces.live.com/
Latest Open-Source Projects: http://entwicklung.junetz.de
-----------------------
"This reply is provided as is, without warranty express or implied."










.

Relevant Pages

  • Re: OT: Two ways Microsoft sabotages Linux desktop adoption
    ... Microsoft has no competition in the desktop os market, ... Somewhere else in this thread was mentioned windows success, ... linmodem driver project. ... to communicate with said card. ...
    (Fedora)
  • Re: Word 2003
    ... I am one who also uses Windows. ... Because Microsoft does not make the software that is causing the issue. ... chances are the graphics card is the same in many ... chances are it is running the same driver ...
    (microsoft.public.mac.office.word)
  • Re: AAA**BSODwhen playing games**AAA
    ... Run the driver verifier, see: ... aka "Nutcase" - Microsoft MVP ... Associate Expert - WindowsXP Expert Zone ... > Operating System: Microsoft Windows XP Professional ...
    (microsoft.public.windowsxp.general)
  • MowGreen, others - problems with KB819696
    ... I'm starting a new thread here, because now I have my Windows 98 ... Security Update for Microsoft Windows ... reinstall DirectX 9.0b on your computer. ... make a driver that supports DirectX 9.anything for Windows 98. ...
    (microsoft.public.windowsupdate)
  • Re: stop powerpoint graphics from constantly flashing
    ... Windows begins to crash. ... features itself rather than letting the video driver handle them. ... Microsoft MVP PowerPoint ... Try updating your 'graphics card driver' - an update normally found on the ...
    (microsoft.public.powerpoint)
Loading