rundll32 is a multi-purpose executable that helps shell
you can use it to load a library and call one of its functions with params:
runs control panel applets:
rundll32 shell32,Control_RunDLL "sysdm.cpl"
it is also called by services.exe for plug & play device installation, example:
rundll32.exe newdev.dll,ClientSideInstall \\.\pipe\PNP_Device_Install_Pipe_0.{A9751359-5B14-45B7-A31F-AF5C164D350F}
all windows have a menu, system icon menu is part of the window menu.
reactos really should unify about boxes and licenses in your apps, right now it looks
unprofessional like in linux where every app has its own, different about box and
license dialogs..
and a question to reactos developers: how can reactos uncompress cab files? they are propriatery format right?
words to developers (NT pnp internals, tops and a question)
Moderator: Moderator Team
Re: words to developers (NT pnp internals, tops and a questi
you an write that to wiki.Delfi wrote:rundll32 is a multi-purpose executable that helps shell
you can use it to load a library and call one of its functions with params:
runs control panel applets:
rundll32 shell32,Control_RunDLL "sysdm.cpl"
it is also called by services.exe for plug & play device installation, example:
rundll32.exe newdev.dll,ClientSideInstall \\.\pipe\PNP_Device_Install_Pipe_0.{A9751359-5B14-45B7-A31F-AF5C164D350F}
all windows have a menu, system icon menu is part of the window menu.
Well, we have grater problems right now.Delfi wrote:reactos really should unify about boxes and licenses in your apps, right now it looks
unprofessional like in linux where every app has its own, different about box and
license dialogs..
How do you define propriatery.Delfi wrote:and a question to reactos developers: how can reactos uncompress cab files? they are propriatery format right?
Where do you want ReactOS to go today ?
Re: words to developers (NT pnp internals, tops and a questi
I agree with that.Delfi wrote:reactos really should unify about boxes and licenses in your apps, right now it looks
unprofessional like in linux where every app has its own, different about box and
license dialogs..
I usually define it as closed source.Dr. Fred wrote:How do you define propriatery.Delfi wrote:and a question to reactos developers: how can reactos uncompress cab files? they are propriatery format right?
Re: words to developers (NT pnp internals, tops and a questi
Things like this is what i had in mind when the GUI discussion was going on. There needs to be a common look and feel to the whole interface. MSFT went through this battle for a long time but I think it pays off in the end.Harteex wrote:I agree with that.Delfi wrote:reactos really should unify about boxes and licenses in your apps, right now it looks
unprofessional like in linux where every app has its own, different about box and
license dialogs..
pax mei amici amorque et Iesus sacret omnia
Re: words to developers (NT pnp internals, tops and a questi
Yes it's close source but It's documented and as far as I can tell not patented.Harteex wrote:I usually define it as closed source.Dr. Fred wrote:How do you define propriatery.Delfi wrote:and a question to reactos developers: how can reactos uncompress cab files? they are propriatery format right?
Where do you want ReactOS to go today ?
-
- Posts: 1
- Joined: Fri Feb 25, 2005 3:28 pm
- Location: Ireland
Re: words to developers (NT pnp internals, tops and a questi
Their battle isn't finished quite yet, tried installing a font using the FILE > INSTALL FONT function in the fonts folder of a Windows XP box lately.Floyd wrote: Things like this is what i had in mind when the GUI discussion was going on. There needs to be a common look and feel to the whole interface. MSFT went through this battle for a long time but I think it pays off in the end.
Still uses old style Windows 3.1 dialog boxes.
-
- Posts: 32
- Joined: Thu Dec 02, 2004 7:29 am
- Location: ReactOS Inside [I'm a Spanish Member]
Re: words to developers (NT pnp internals, tops and a questi
I was searching about this in Google, and I've read that "the LZX format was purchased by Microsoft, slightly reduced in potency, and used in the CAB format". But nothing about "patents" or "proprietary algorithms" for CAB... Those are good news...Dr. Fred wrote:Yes it's close source but It's documented and as far as I can tell not patented.Harteex wrote:I usually define it as closed source.Dr. Fred wrote: How do you define propriatery.
Re: words to developers (NT pnp internals, tops and a questi
Gabriel Vigo wrote:I was searching about this in Google, and I've read that "the LZX format was purchased by Microsoft, slightly reduced in potency, and used in the CAB format". But nothing about "patents" or "proprietary algorithms" for CAB... Those are good news...Dr. Fred wrote:Yes it's close source but It's documented and as far as I can tell not patented.Harteex wrote: I usually define it as closed source.
actually the cab files support 2 types of compression - mszip and lzw.
Who is online
Users browsing this forum: Google [Bot] and 73 guests