headers
King InuYasha | 1 Apr 2008 08:37
Picon
Gravatar

About ext2 driver installer

I looked at the ReactOS website and noticed that you guys are having problems getting an installer written for an ext2 driver for Windows XP? I would be happy to write an NSIS-based installer for the ext2 driver, if either someone could compile the driver for me, or tell me where the driver is in the ReactOS tree so I can build it myself and create an installer for it. I have written NSIS installers before, some that have advanced functionalities using Component Manager and ExperienceUI. Please let me know if you guys would like me to make this installer....

_______________________________________________
Ros-dev mailing list
Ros-dev@...
http://www.reactos.org/mailman/listinfo/ros-dev
Permalink | Reply | 7 comments |
headers
Christoph von Wittich | 1 Apr 2008 09:41
Picon
Favicon

Re: About ext2 driver installer

Don't use NSIS or other similar tools - the only working installer is 
MSI (WiX). NSIS has some issues with Vista and can't be installed trough 
Software distribution on Windows Domains.

Christoph von Wittich

King InuYasha schrieb:
> I looked at the ReactOS website and noticed that you guys are having 
> problems getting an installer written for an ext2 driver for Windows 
> XP? I would be happy to write an NSIS-based installer for the ext2 
> driver, if either someone could compile the driver for me, or tell me 
> where the driver is in the ReactOS tree so I can build it myself and 
> create an installer for it. I have written NSIS installers before, 
> some that have advanced functionalities using Component Manager and 
> ExperienceUI. Please let me know if you guys would like me to make 
> this installer....
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev@...
> http://www.reactos.org/mailman/listinfo/ros-dev
Permalink | Reply | 4 comments |
headers
gedmurphy | 1 Apr 2008 09:53
Picon

Re: About ext2 driver installer

Why do we need an installer for this driver, it should be installed with all
the other drivers in setup.
Or are you talking about 3rd party usage?

-----Original Message-----
From: ros-dev-bounces@...
[mailto:ros-dev-bounces@...] On
Behalf Of Christoph von Wittich
Sent: 01 April 2008 08:41
To: ReactOS Development List
Subject: Re: [ros-dev] About ext2 driver installer

Don't use NSIS or other similar tools - the only working installer is 
MSI (WiX). NSIS has some issues with Vista and can't be installed trough 
Software distribution on Windows Domains.

Christoph von Wittich

King InuYasha schrieb:
> I looked at the ReactOS website and noticed that you guys are having 
> problems getting an installer written for an ext2 driver for Windows 
> XP? I would be happy to write an NSIS-based installer for the ext2 
> driver, if either someone could compile the driver for me, or tell me 
> where the driver is in the ReactOS tree so I can build it myself and 
> create an installer for it. I have written NSIS installers before, 
> some that have advanced functionalities using Component Manager and 
> ExperienceUI. Please let me know if you guys would like me to make 
> this installer....
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev@...
> http://www.reactos.org/mailman/listinfo/ros-dev

_______________________________________________
Ros-dev mailing list
Ros-dev@...
http://www.reactos.org/mailman/listinfo/ros-dev
Permalink | Reply | 3 comments |
headers
Daniel Reimer | 1 Apr 2008 12:02
Picon
Favicon

Re: About ext2 driver installer

gedmurphy schrieb:
> Why do we need an installer for this driver, it should be installed with all
> the other drivers in setup.
> Or are you talking about 3rd party usage?
>
> -----Original Message-----
> From: ros-dev-bounces@...
[mailto:ros-dev-bounces@...] On
> Behalf Of Christoph von Wittich
> Sent: 01 April 2008 08:41
> To: ReactOS Development List
> Subject: Re: [ros-dev] About ext2 driver installer
>
> Don't use NSIS or other similar tools - the only working installer is 
> MSI (WiX). NSIS has some issues with Vista and can't be installed trough 
> Software distribution on Windows Domains.
>
> Christoph von Wittich
>
> King InuYasha schrieb:
>   
>> I looked at the ReactOS website and noticed that you guys are having 
>> problems getting an installer written for an ext2 driver for Windows 
>> XP? I would be happy to write an NSIS-based installer for the ext2 
>> driver, if either someone could compile the driver for me, or tell me 
>> where the driver is in the ReactOS tree so I can build it myself and 
>> create an installer for it. I have written NSIS installers before, 
>> some that have advanced functionalities using Component Manager and 
>> ExperienceUI. Please let me know if you guys would like me to make 
>> this installer....
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev@...
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>     
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev@...
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev@...
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>   

Its meant for testing purposes on XP and newer Windows OSes. We need to 
try if it works correctly and some not so low level skilled cant install 
it manually.
Permalink | Reply | 2 comments |
headers
gedmurphy | 1 Apr 2008 14:21
Picon

Re: About ext2 driver installer

If it's just for testing, just copy the driver and add the service keys.
Or grab a copy of OSR's Driver Loader and use that to register it.

-----Original Message-----
From: ros-dev-bounces@...
[mailto:ros-dev-bounces@...] On
Behalf Of Daniel Reimer
Sent: 01 April 2008 11:03
To: ReactOS Development List
Subject: Re: [ros-dev] About ext2 driver installer

Its meant for testing purposes on XP and newer Windows OSes. We need to 
try if it works correctly and some not so low level skilled cant install 
it manually.
Permalink | Reply | 1 comment |
headers
Aleksey Bragin | 1 Apr 2008 14:39
Favicon
Gravatar

Re: About ext2 driver installer

3rd party usage is also good, I'd appreciate if a decent installer  
could be made for it.

WBR,
Aleksey Bragin.

On Apr 1, 2008, at 4:21 PM, gedmurphy wrote:

> If it's just for testing, just copy the driver and add the service  
> keys.
> Or grab a copy of OSR's Driver Loader and use that to register it.
>
> -----Original Message-----
> From: ros-dev-bounces@... [mailto:ros-dev- 
> bounces@...] On
> Behalf Of Daniel Reimer
> Sent: 01 April 2008 11:03
> To: ReactOS Development List
> Subject: Re: [ros-dev] About ext2 driver installer
>
> Its meant for testing purposes on XP and newer Windows OSes. We  
> need to
> try if it works correctly and some not so low level skilled cant  
> install
> it manually.
Permalink | Reply | 0 comments |
headers
James Tabor | 2 Apr 2008 05:42
Picon

[ros-diffs] [tkreuzer] 32743: - make Simplecall definitions (NtUserCallXxx) compatible to different Win versions

Hi!
Thank you Timo, I can not believe I missed this one....

This fixes a commit back at rev 14041.

With out starting a review in real world history,, once an enemy gains
control the first thing they do is erase history. New eras evolve and
build on top of old ones. Our old world ruins are a good example. Look
at Cuzco, Greece and Rome. You see them now uncovering the past.

Thanks again!
James
Permalink | Reply | 0 comments |
headers
Timo Kreuzer | 2 Apr 2008 18:21
Picon

win32k public headers

I am currently trying to clean up our win32k headers.

The situation so far:
- ntgdi.h in psdk which should be compatible to ms version of ntgdi.h 
from the sdk
- ntgdytyp.h containing a bunch of gdi related types in 
include/reactos/win32k
- ntgdihdl.h containing handle related types and macros in 
include/reactos/win32k
- ntgdibad.h containing private and ms incompatible functions and 
structures in include/reactos/win32k
- ntuser.h containing ntuser functions and types in include/reactos/win32k
- ntusertyp.h containing ntuser related types in include/reactos/win32k
- W32CLIENTINFO is defined in both ntusertyp.h and ntgdityp.h (less 
complete).
- there is the PATRECT structure in ntuser.h, and if ntuser.h is not 
included, also in ntgdityp.h, this should be named POLYPATBLT as defined 
in ntgdi.h, but there is only an incomplete type without the structure 
definition. (IMO ms should have put this structure into wingdi.h 
together with PolyPatBlt, but they don't seem to want anyone use that 
gdi32 exported function.)

I wonder why ms put ntgdi.h into the sdk at all, as it's completely 
useless to user mode application writers, but well, ncie to have the 
prototypes ;-)

So how do we clean up this mess?

Suggestions:
- when ms puts ntgdi.h into the sdk, we could also put ntuser.h there.
- if we want to stay 100% compatible with sdk headers, we can add a 
define, like
#ifdef USE_NON_SDK
// put non sdk compatible but still windows compatible definitions here
#endif
- use a version definition, like I did with the simplecall definitions 
in ntuser.h to make it compatible to different windows versions
- keep ntgdibad.h and create ntuserbad.h for incompatible definitions
- ntgdihdl.h is used by win32k and gdi32, both also import ntgdityp.h. 
So I'd suggest merging that stuff into ntgdityp.h
- maybe merge types into ntgdi.h and ntuser.h? Some definitions are 
already in there.
- create win32ktypes.h and put ntuser/ntgdi shared stuff there, like 
W32CLIENTINFO
- maybe add POLYPATBLT and PolyPatBlt() (others?) to wingdi.h inside 
USE_NON_SDK ifdef plus a POLYPATBLT_DEFINED

I don't think it's a problem to make our sdk headers more complete than 
ms ones. This might help if we don't want a header mess or extra 
definitions inside the .c files.

Comments appreciated.

Thanks,
Timo
Permalink | Reply | 3 comments |
headers
James Tabor | 2 Apr 2008 19:55
Picon

Re: win32k public headers

Hi!

On Wed, Apr 2, 2008 at 11:21 AM, Timo Kreuzer <timo.kreuzer@...> wrote:
> I am currently trying to clean up our win32k headers.
>
>  The situation so far:
>  - ntgdi.h in psdk which should be compatible to ms version of ntgdi.h
>  from the sdk
Yes! Should always be!!

>  - ntgdytyp.h containing a bunch of gdi related types in
>  include/reactos/win32k
>  - ntgdihdl.h containing handle related types and macros in
>  include/reactos/win32k
>  - ntgdibad.h containing private and ms incompatible functions and
>  structures in include/reactos/win32k

>  - ntuser.h containing ntuser functions and types in include/reactos/win32k
>  - ntusertyp.h containing ntuser related types in include/reactos/win32k
>  - W32CLIENTINFO is defined in both ntusertyp.h and ntgdityp.h (less
>  complete).

Gdi and User point to the ClientInfo area which is part of thread info
structures and like all thread structures should be place in some sort
of include/reactos/win32k/w32thread.h. This would allow Gdi and User
to access them both. I have placed #ifndef _NTUSRTYP_ so when both
headers are used there will be no compile errors.

>  - there is the PATRECT structure in ntuser.h, and if ntuser.h is not
>  included, also in ntgdityp.h, this should be named POLYPATBLT as defined
>  in ntgdi.h, but there is only an incomplete type without the structure
>  definition. (IMO ms should have put this structure into wingdi.h
>  together with PolyPatBlt, but they don't seem to want anyone use that
>  gdi32 exported function.)
>
>  I wonder why ms put ntgdi.h into the sdk at all, as it's completely
>  useless to user mode application writers, but well, ncie to have the
>  prototypes ;-)
>
>  So how do we clean up this mess?
>
>  Suggestions:
>  - when ms puts ntgdi.h into the sdk, we could also put ntuser.h there.
>  - if we want to stay 100% compatible with sdk headers, we can add a
>  define, like
>  #ifdef USE_NON_SDK
>  // put non sdk compatible but still windows compatible definitions here
>  #endif
If we are compatible why do we need this? All SDK headers should be
compatible and I have pointed this out. When NDK/DDK (WDK) or PSDK
(SDK) changes are made the developer should have access to these and
compare the changes to verify them as correct. I have made changes to
the NDK with some Rtl functions and I had to make logical choices and
assumptions. Since those Rtl functions are unknown and the research
was from Wine, I did go through the steps of verifying and cross
referencing them before I moved them into NDK.

SDK and WDK are open to the public and there is nothing preventing
that developer from referencing them for research and standards.

One of my best patent guys always said,"Once someone publishes their
patent in text book form, they just gave it away." If your lawyer
doesn't know that, go find one that does!

>  - use a version definition, like I did with the simplecall definitions
>  in ntuser.h to make it compatible to different windows versions
>  - keep ntgdibad.h and create ntuserbad.h for incompatible definitions
>  - ntgdihdl.h is used by win32k and gdi32, both also import ntgdityp.h.
>  So I'd suggest merging that stuff into ntgdityp.h
>  - maybe merge types into ntgdi.h and ntuser.h? Some definitions are
>  already in there.

>  - create win32ktypes.h and put ntuser/ntgdi shared stuff there, like
>  W32CLIENTINFO

This will due too!

>  - maybe add POLYPATBLT and PolyPatBlt() (others?) to wingdi.h inside
>  USE_NON_SDK ifdef plus a POLYPATBLT_DEFINED
>
>  I don't think it's a problem to make our sdk headers more complete than
>  ms ones. This might help if we don't want a header mess or extra
>  definitions inside the .c files.
>
>  Comments appreciated.
>
>  Thanks,
>  Timo
>
>
Thanks,
James
Permalink | Reply | 2 comments |
headers
Timo Kreuzer | 3 Apr 2008 00:20
Picon

Re: win32k public headers

James Tabor schrieb:

Gdi and User point to the ClientInfo area which is part of thread info structures and like all thread structures should be place in some sort of include/reactos/win32k/w32thread.h. This would allow Gdi and User to access them both. I have placed #ifndef _NTUSRTYP_ so when both headers are used there will be no compile errors.
Placing an undocumented and partly unknown structure inside two different headers will lead to problems, like the two different versions we have now ;-)
Suggestions: - when ms puts ntgdi.h into the sdk, we could also put ntuser.h there. - if we want to stay 100% compatible with sdk headers, we can add a define, like #ifdef USE_NON_SDK // put non sdk compatible but still windows compatible definitions here #endif
If we are compatible why do we need this? All SDK headers should be compatible and I have pointed this out. When NDK/DDK (WDK) or PSDK (SDK) changes are made the developer should have access to these and compare the changes to verify them as correct. I have made changes to the NDK with some Rtl functions and I had to make logical choices and assumptions. Since those Rtl functions are unknown and the research was from Wine, I did go through the steps of verifying and cross referencing them before I moved them into NDK. SDK and WDK are open to the public and there is nothing preventing that developer from referencing them for research and standards.
Well I'm not sure if I got you right, so I just try to make my thinking more clear:
There's compatible and there's compatible:
A) our sdk headers will contain 100% the same as ms sdk headers, not less, not more
B) our sdk headers will contain everything that is in ms sdk headers, but can contain more.
The ms sdk you can download is the public sdk. It's probably not what ms uses to compile their stuff. It's partly limited. ntgdi.h contains "typedef struct _POLYPATBLT  POLYPATBLT, * PPOLYPATBLT";
But where's the real structure definition? Somewhere else? Does that make sense? Well it does when ms uses different headers that contain all the complete types, but then they don't even need this typedef.. So where do we put it?
I suggested the #ifdef's to have compatibility A when it's not defined and B when it's defined.
ntuser.h doesn't belong to the ms sdk. But for what reason? Do ms people really have ntuser stuff somewhere else? Probably not, they just decided not to ship it (I think they shipped ntuser.h with DDK some time ago)

Timo

_______________________________________________
Ros-dev mailing list
Ros-dev@...
http://www.reactos.org/mailman/listinfo/ros-dev
Permalink | Reply | 1 comment |

Gmane