--- Rouven We�ling rouven@rouvenwessling.de wrote: Thomas Larsen schrieb:
- Disam shell32 and scsiport.sys Theire where lot of places where it where
identical
The M$ compiler and gcc is very different. If you compare the assembler code which is compiled from the same source, you can found the same functions bodies, but inside the functions there are many differences. Some time ago, I've ported a simple driver for an eprom programer from M$ tools to the ReactOS build system. At the start it hasn't worked, because I forgot the stdcall attributes for some functions. The reassembled code was very different.
Their are not that big difference agre that scsiport is in c code when you compile it you get machine code right when you compare the "C CODE from scsiport.sys from REACTOS" with microsoft asm from ida pro it will list the functions used and the params used and what cases it used around in the code what internal function their are called not so hard BUT if you compare GNU Asm Vs. Ms Asm their will be a big diff.
- Microsoft Source leak my friend just downloaded it i got parts of the
code what could be on my 1,33 mb floppy
If you was interessted to compare the ros and M$ code, you have neverworked with a floppy. It is too simple to burn a cd or dvd.
If i want to use a floppy i use a fucking floppy the parts i wanted to find out where small sections from shell32 and scsiport.sys just to get some invidence from winnt4.0 and i got those thing one my so simple floppy i could use a dvd a cdrom a harddisk but why i could be on my floppy
- Saw scsiport.sys where 90% identical i layout and code and alittel of
shell32
Some parts of scsiport are from me. I've never seen the scsiport sources from M$. I'm not sure which code from M$ you know. Our scsiport is more compatible with the NT4.0 one. I've test many scsi controller with its NT 4.0 drivers (adaptect 2940, ataptec on asus p2d, dmx3194uw, diamond fireport, tekram dc390, initio a100, some with different lsi chipset, some with initio 950 chip set). I think M$ has lost the W2K sourcesand not the NT4.0 one. Our scsiport is very different from W2k and it is different from NT4.0. I've add a list of imported functions. Some functions are very specific for the implemention. ReactOS doesn't use IoFreeMdl, IoFreeIrp, the DeviceQueu functions and some others. Many things may nearly the same, bcause they must implement the some functions. Our implementation is different from M$. The different imported functions shows this. You cannot find 90% identical, if you compare our source with the M$ source.
1. You point is GNU Asm / Microsoft Asm is Different - SO
2. I Dont use a cdrom or other media when its so easy - SO i still use floppy for small items dont think you know that in denmark their are taxes on the cdroms
3. Saying that microsoft uses some function witch reactos dont; i leave up to you to take an asm program Ida Pro 4.7 remember debug info is a good start see the exports in Winnt 4.0 Scsiport Driver and the imports and come back to me.. then you can open your mouth once again.- else its it would be a waste of time writing to me
Thomas
__________
__________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/
Thomas Larsen schrieb:
- Saying that microsoft uses some function witch reactos dont; i leave up to you to take an asm
program Ida Pro 4.7 remember debug info is a good start see the exports in Winnt 4.0 Scsiport Driver and the imports and come back to me.. then you can open your mouth once again.- else its it would be a waste of time writing to me
Thomas
You have found out, that the imported and exported functions are nearly the same? Great job to find out that our scsiport is 90% identicly to M$ one :-D . You know, that we will use third party miniport drivers? Miniport drivers do only import functions from scsiport. All of the dll's, drivers and so on will have the some imported and exported function like M$ windows.
- Hartmut
-
Hartmut Birr -
Thomas Larsen