Hi,
First, I'd like to apologize since what I'm asking doesn't directly relate to
ReactOS however I'm hoping someone here might be able to shed some light.
I've built a rudimentary win32k profiler and I've hooked the win32k SDT and
hooked onto the NtUserCreateWindowEx function in the hope of studying values
returned by it. I see some strange (to me) values for the x and y
coordinates - values such as 1547372 etc. I'm not sure how to interpret these
values and convert them into pixel units or traditional coordinate
mechanisms. I first thought there must be something wrong with my code
however I'm not so sure anymore.
Would someone here be able to guide me on how to interpret these values???
Thanks and sorry again
Bye for now
> > 7. Running on 16-bit systems like 286/386/486 in a "ReactOS Essentials"
> > (equivalent to a stripped-down XP) mode *
> > It should be the same operating system, but in 16-bit mode only. That's
> > an ideal scenario and I'm sure it cannot be done no matter how good the
> > programmers are. So, what can someone do on a 286 ? Listen to mp3's ? No
Safe Mode. Just load Video, File and network drivers and allow direct access to int13
so fdisk and format can run so user can diag/fix it.
Curious if ReactOS has a an Emergency Boot Disk
system that it can make ? Perhaps, keep a Freedos 1.44m
disk image and allow suer to rawrite it when needed. Or even a
dual bootable Freedos partition (FAT16) with the appropriate recovery tools on it.
--chris
1-916-410-7677
http://nxdos.sourceforge.net/http://bbx.flnet.org/http://teknopup.angelfire.com/
For consistency, I would think OB, IO, PS and other modules having
such tracing system should be turned off by default then too.
WBR,
Aleksey.
On Sep 23, 2008, at 11:54 PM, sginsberg(a)svn.reactos.org wrote:
> Author: sginsberg
> Date: Tue Sep 23 14:54:13 2008
> New Revision: 36436
>
> URL: http://svn.reactos.org/svn/reactos?rev=36436&view=rev
> Log:
> - Attempt to satisfy Alex
There is a big problem with this change, originally this was added
only for "our own" .spec files, which don't have comments starting
with #.
Wine .spec files have such comments, and thus will be preprocessed
incorrectly.
WBR,
Aleksey.
On Sep 21, 2008, at 6:34 PM, tkreuzer(a)svn.reactos.org wrote:
> Author: tkreuzer
> Date: Sun Sep 21 09:34:48 2008
> New Revision: 36379
>
> URL: http://svn.reactos.org/svn/reactos?rev=36379&view=rev
> Log:
> preprocess all spec files
>
> Modified:
> branches/ros-amd64-bringup/reactos/tools/rbuild/backend/mingw/
> modulehandler.cpp
>
> Modified: branches/ros-amd64-bringup/reactos/tools/rbuild/backend/
> mingw/modulehandler.cpp
> URL: http://svn.reactos.org/svn/reactos/branches/ros-amd64-bringup/
> reactos/tools/rbuild/backend/mingw/modulehandler.cpp?
> rev=36379&r1=36378&r2=36379&view=diff
Hi,
I just joined in the mail list and I want to ask a question.
I have a question about scsiport module. I have seen the code
scsiport.c and tried to find where it create the physical device
object for scsi disk however I didn't find it. I just saw the
function SpiScanAdapter which would send inquiry scsi command to scsi
miniport driver.
So I want to know who create the pdo for scsi disk?
Gang Chen
I think if it's a generic buffer-allocating function, its callers
should not rely on the memory being zeroed. (like they don't rely on
pool and heap allocations, unless called with zero-heap flag).
At least the comments to the function does not say "it returns a
zeroed buffer".
WBR,
Aleksey.
On Sep 20, 2008, at 4:31 AM, cgutman(a)svn.reactos.org wrote:
> Author: cgutman
> Date: Fri Sep 19 19:31:02 2008
> New Revision: 36337
>
> URL: http://svn.reactos.org/svn/reactos?rev=36337&view=rev
> Log:
> - Zero the memory after we allocate it
>
> Modified:
> branches/aicom-network-fixes/drivers/network/tcpip/tcpip/pool.c
Our LoadIcon is broken and can result in badly drawn / ugly icons.
You should use LoadImage instead.
LoadIcon is deprecated anyway, no one should be using it anymore.
Ged.
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of janderwald(a)svn.reactos.org
Sent: 17 September 2008 22:59
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [janderwald] 36295: - Update Status Icon when there is activity - Also update the Taskbar Notification Icon
+ hIcon = NULL;
+ if (pContext->dwInOctets == IfEntry.dwInOctets && pContext->dwOutOctets == IfEntry.dwOutOctets && pContext->Status != 0)
+ {
+ hIcon = LoadIcon(netshell_hInstance, MAKEINTRESOURCE(IDI_NET_IDLE));
+ pContext->Status = 0;
+ }
+ else if (pContext->dwInOctets != IfEntry.dwInOctets && pContext->dwOutOctets !=