--- Rouven We�ling <rouven(a)rouvenwessling.de> wrote:
Thomas Larsen schrieb:
>4. 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.
>5. 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
>6. 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/
My english is sometimes poor
For the first i give a shit public or not
1. One day i found reactos
2. Where looking on how you made reactos drivers and got (exiting=happy dont know how to spell)
3. Got Ida Disam in demo version
4. Disam shell32 and scsiport.sys Theire where lot of places where it where identical
5. Microsoft Source leak my friend just downloaded it i got parts of the code what could be on my
1,33 mb floppy
6. Saw scsiport.sys where 90% identical i layout and code and alittel of shell32
7. Wrote one mail or two dont remember saying it should newer have done so
8. Got many really unhappy ppl. email answers (they want to see the source and No i dident)
9. Talked with alot of ppl and i discover that i where not right
10. Worked on with reactos
11. The mail today
;I'm not quite sure what you're driving at, but are you saying you
;posess(ed) the leaked sources? And - by comparing it with ReactOS/WINE -
;we must have been tainted with it? I really hope I mistook that.
i dident possess (in my word book its is "showing" the source) And no that where not what i meant
to say
Im Saying that i could just have changed email and name (NO Worry i dident do that)
And my point only where give me a chance the only thing i want to is to help reactos..
but it seems that their are no chance so saying goodbye.. sry..
Thomas
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Hi,
--- Thomas Larsen <sikker2004(a)yahoo.com> wrote:
> 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
If I am reading this right, he is saying that he has looked at Microsoft source code and compared
it to ReactOS. Is that right? Or just compared disassembled functions? In anycase, if Microsoft
thinks there is a copyright violation in ReactOS please have them contact us and stop spaming the
list.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
The Problem with this would be that the dll files or perhaps any compiled file would be large. Think of all the words that the German, English, French, portuguese, etc languages have. Doing this would make a binary executable be extremely large. I know that i only can use a limited amount of space with my vmware, bochs, and qemu images. about 256mbs is all. even if ReactOS did something like shell32.us-en.dll or shell32.us-es.dll or perhaps even shell32.1033.dll would be difficult because some executables come precompiled to use a staticly named dll file. I would think that adding every language would be very time consuming, and tax your disk space.
>
> From: "Magnus Olsen" <magnus(a)itkonsult-olsen.com>
> Date: 2005/03/11 Fri PM 01:08:08 EST
> To: "ReactOS Development List" <ros-dev(a)reactos.com>
> Subject: Re: [ros-dev] Idea to save time in future - Language Support AndUse
> in Reactos
>
> I want see driffnet langues in the dll and change langues on fly
> instead compile a dll file for each langues. I am mising that feturtuer in
> windows.
> If you look at Amiga OS (Workbench 2.0 or higher) you can change the hole os
> langues
> when it was running. in windows you are stuck with one langues.
>
> So I think it is good idea to compile all langues into all dll file.
> then select in the os wich langues you want use.
>
>
> ----- Original Message -----
> From: "Thomas Weidenmueller" <w3seek(a)reactos.com>
> To: "ReactOS Development List" <ros-dev(a)reactos.com>
> Sent: Friday, March 11, 2005 11:16 AM
> Subject: Re: [ros-dev] Idea to save time in future - Language Support AndUse
> in Reactos
>
>
> > Thomas Larsen wrote:
> >
> > >Language Support And Use in Reactos
> > >
> > >Idea: Split the files by using config and only include whats needed by
> dev and end user
> > >goal: Saves time in compiling and get smaller fil sizes.
> > >
> > >
> > Resource files usually compile pretty fast and are usually not that big
> > unless they contain large bitmaps.
> >
> > >If not done imagine 256 languages in each file getting included then we
> would get pretty large
> > >files just see shell32.dll and its a waste both for the end users and us
> it takes a while extra to
> > >include all those extra langs
> > >
> > >
> > I wouldn't consider it as a waste of space, applications that use other
> > locales then work correctly and dialogs etc work in all the same
> > language. It's been bugging me that for instance german applications
> > that run on an english system are completely german except the message
> > box buttons, common controls, ....
> >
> > >The Config File i Reactos Root path
> > ># Which default language would you like to use
> > ># Select Between: English:En, Danish:Dk, France:Fr etc.
> > >DEFAULTOSLANG=Dk
> > >
> > >The Ressource.rc file in each paths
> > >#if DEFAULTLANG
> > >#include %DEFAULTLANG%.rc // Need to test if exist if not include en.rc a
> littel app could check
> > >for this it would be pretty fast else include english res
> > >#else
> > >#include "En.rc"
> > >#endif
> > >
> > >Just an idea.. Thomas
> > >
> > >
> > Specifying a default language is indeed good, however I don't think it's
> > good to compile just with this chosen language. But that's just my
> > personal opinion.
> >
> > Best Regards,
> > Thomas
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.com
> > http://reactos.com:8080/mailman/listinfo/ros-dev
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
>
Language Support And Use in Reactos
Idea: Split the files by using config and only include whats needed by dev and end user
goal: Saves time in compiling and get smaller fil sizes.
If not done imagine 256 languages in each file getting included then we would get pretty large
files just see shell32.dll and its a waste both for the end users and us it takes a while extra to
include all those extra langs
The Config File i Reactos Root path
# Which default language would you like to use
# Select Between: English:En, Danish:Dk, France:Fr etc.
DEFAULTOSLANG=Dk
The Ressource.rc file in each paths
#if DEFAULTLANG
#include %DEFAULTLANG%.rc // Need to test if exist if not include en.rc a littel app could check
for this it would be pretty fast else include english res
#else
#include "En.rc"
#endif
Just an idea.. Thomas
Ps. alot of patches new files and translation on bugzilla if any want to use it. :-)
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
I Where pist that day from my point
Illegal code in reactos in project i want to be in to
Angry a took some maybe lille fast conclusions
you just love to take old things up... or what..
Thomas
__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
Its a long time ago now Geldorp i no longer got the source code yes i look at it but only because
some drivers and shell code where extreme close to microsofts old ones and i dident want to work
on a project if it gets closed but now i know you and wine dident.. still sry for the accousing
but i can do anything execpt saying that im sry
And i could have changed e-mail and called me bob if it where that but i dident just to give you
some to think about..
Im not mad or angry i where not clear about the policy back their and it where just to help you
and reactos..
Thomas Larsen
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
--- Royce Mitchell III <royce3(a)ev1.net> wrote:
> Someone mentioned recently that we should name all the xml build system
> files makefile.rbuild, or something to that effect.
>
> I didn't have an opinion at the time, but I have recently developed a
> very strong one...
>
> If all the build system's files are named the same, and if you have 3 of
> them open in notepad, you can't tell which is which from the window's
> title. This is IMNSHO a bad thing.
What do you do when you have 3 "makefile" open in notepad then ?
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word