Hi,
> Subject: [ros-diffs] [ekohl] 23521:
> - Implement ScmStartServiceA and revert the last modification of
StartServiceA.
> - Fix EnumServicesStatusExW.
We now have an exact code duplication between StartServiceA/StartServiceW
(except strlen/wcslen and strcpy/wcscpy) and
ScmrStartServiceA/ScmrStartServiceW.
I don't think it's a good thing because we will have some problems to keep
the code in sync.
I did r23519 to prevent this code duplication and because
ScmrStartServiceA() was not called except in StartServiceA.
By the way, I also implemented argument conversion between ANSI and Unicode
in StartServiceA before calling StartServiceW, which meant that arguments
were ignored only in ScmrStartServiceW. Now, you have 2 places to take care
of them (ScmrStartServiceA/W)...
That was just to say my feeling...
Hervé
> Commit by *fireball* :: r*23508* *reactos*/ntoskrnl/ (cm/regobj.c
> ob/obhandle.c):
>
> Goodbye REGISTRY_ERROR bsod!
>
> * Change UserMode -> KernelMode in ObReferenceObject*() calls,
> because that calls failed
> * Remove Cm-specific hack from Ob "advapi32_winetest.exe registry"
> shows 0 failures on the first run and 2 failures on further
> runs. I suppose there might be a leakage in the CM. To be
> investigated further (or wait till complete Cm rewrite in October).
>
Still regedit crashes when trying to open a key that contains one or
more values.
From http://reactos.dyndns.org:8010/
[CC] drivers\network\ndis\ndis\control.c
drivers\network\ndis\ndis\control.c: In function `NdisAcquireReadWriteLock':
drivers\network\ndis\ndis\control.c:63: warning: assignment makes integer from pointer without a cast
make: *** [obj-i386\drivers\network\ndis\ndis\control.o] Error 1
program finished with exit code 2
From Linux,
[CC] drivers/network/ndis/ndis/control.c
drivers/network/ndis/ndis/control.c: In function `NdisAcquireReadWriteLock':
drivers/network/ndis/ndis/control.c:63: warning: assignment makes integer from pointer without a cast
make[1]: *** [obj-i386/drivers/network/ndis/ndis/control.o] Error 1
make: *** [ndis] Error 2
8^)
James
fireball(a)svn.reactos.org wrote:
> Author: fireball
> Date: Sun Aug 6 01:39:29 2006
> New Revision: 23491
>
> URL: http://svn.reactos.org/svn/reactos?rev=23491&view=rev
> Log:
> [AUDIT]
> Configuration Manager
>
> After going through the code, it doesn't have any signs of questionable origin.
If it did, where are all those REGISTRY_ERROR bugchecks I should be
getting in Windows NT? :P
--
Best regards,
Alex Ionescu
Project Lead, TinyKRNL
Kernel-Mode Software Design Engineer, ReactOS
fireball(a)svn.reactos.org wrote:
> Author: fireball
> Date: Sun Aug 6 00:57:36 2006
> New Revision: 23489
>
> URL: http://svn.reactos.org/svn/reactos?rev=23489&view=rev
> Log:
> Fix DbgPrint / DbgPrintEx definitions to use PCCHAR instead of PCCH (recent WDK uses PCCHAR).
> This change fixes compiling.
>
Um, no, this is the latest definition:
ULONG
__cdecl
DbgPrint (
__in PCCH Format,
...
);
Why do you think I had changed it in the first place?!
A PCCHAR is *NOT* a const char, it's just typedef char*.
So my change correctly changed the definition to use const char (Because
dbgprint fails if you're not sending a const char), and also allowed
building with the fixed WDKs, and you just reverted that... when you
asked on Google Talk if you could fix it, I assumed you know what you
were doing :)
--
Best regards,
Alex Ionescu
Project Lead, TinyKRNL
Kernel-Mode Software Design Engineer, ReactOS
Hi,
I'm really excited by all the recent WinLogon work! Congratulations to
Hervé for working on this.
Some questions:
Will the GINA be 100% compatible with NT WinLogon? I hope so. Also,
there is a fully FOSS GINA project out there, I'm sure it can be useful.
MSDN also has a lot of information, and I can help with some Winlogon
internals, by email only please, I'm not and won't be on IRC for a while.
Are we also going to support GUI-on-demand? That was largely the big
problem with Winlogon, and both Thomas and I (And others) think GUI On
Demand is a big hack that currently screws up more stuff then it
helps... If yes, then how's winlogon going to work? As a text-mode login
problem as well? Hopefully that won't hack GINA compatibility.
Since this was supposed to be an SoC program, I propose that we setup a
personal fund (and advertise) on the website for Hervé to get paid. I'll
also try talking to Google (since our SoC GINA guy failed) to see if
they'd be willing to set up an exchange. Unless Hervé disagrees, of course.
Good luck to all.
--
Best regards,
Alex Ionescu
Project Lead, TinyKRNL
Kernel-Mode Software Design Engineer, ReactOS
Hello,
it looks like it is a common problem that people don't like to read
commit messages :-)
So I post here - starting from the introduction of cmlib patch into
our tree, the binary hives became compatible with Windows XP binary
hives, BUT incompatible to ReactOS binary hives made with the
previous versions of ReactOS (this includes the current 0.3 release).
In order to overcome this problem, simply reinstall your reactos with
formatting the harddrive partition during setup. Or manually delete
the contents of \system32\config directory, issue a "make
install_registry" command, and don't forget to upgrade your
freeldr.sys too (in case you install all that manually without bootcd).
WBR,
Aleksey Bragin.
Felipe Villarroel wrote:
> Its ok to typecast the char* to LPCWSTR? as in
> file = CreateFile((LPCWSTR) SrcFileNames[i],GENERIC_READ , 0,
> NULL, OPEN_EXISTING, 0, 0); ?
No. If you wanted to use an ASCI where a Unicode char was expected, you
would have to first convert it to Unicode using a function like
MiltiByteToWideChar.
However, CreateFile actually expects LPCTSTR as it's first parameter. It is
then converted to LPCSTR or LPCWSTR dependant on whether you have Unicode
defined. (In your case, you must have)
If this is the case, and you are using TCHAR within your code, then what is
the reason for the char? Maybe it's a value returned from a network read?
Could it be a TCHAR?
My first approach would be to see why it's a char, and not a TCHAR (or
WCHAR), and check whether you can change it in the source (perhaps it's just
something the PICE devs missed)
Secondly, if it must remain a char, but you still want to have Unicode
defined (as we mentioned, not having Unicode defined will call the ASCI
version, which will be fine for your char as it's first member is LPSTR),
then you could call the ASCI version of CreateFile exclusively by calling
CreateFileA.
> and also i have another question. Currently in the source
> (main.c) we assume in line 368 that sizeof(DWORD) ==
> sizeof(INT) and the compiler issues a warning. Its ok to
> typecast this too?
> find_stab_sections(p,IMAGE_FIRST_SECTION(pNTHeaders),pNTHeader
> s->FileHeader.NumberOfSections,&pStab,(PINT)
> &nStabLen,&pStr,&nStabStrLen);
I'm assuming from '(PINT)&nStabLen' that you have a DWORD which you are
typecasting to an INT.
Whilst a DWORD and an INT are of the same size, a DWORD is an unsigned long,
and an INT is signed, which means typecasting from DWORD to INT could result
in data loss if nStabLen is a very high value i.e. more than an INT can
hold. (check your limits.h for this value, it's 2147483647 for 4 byte ints)
Is making nStabLen a DWORD not an option?
> Also, i'm a native spanish speaker. I would be happy to help
> in anyway i could.
Pop into IRC. There is always plenty for people to do ;)
Ged.
Hi ReactOS devs!,
currently i'm trying to get PICE compiling and working again (and learning something about the ReactOS internals in the process). Currently i have a question related to what i'm doing.
To fix some warnings in the compilation of the PICE loader i have to fix the first parameter to CreateFile, because CreateFile expects the first parameter to be a LPCWSTR and its a char* instead. Its ok to typecast the char* to LPCWSTR? as in
file = CreateFile((LPCWSTR) SrcFileNames[i],GENERIC_READ , 0, NULL, OPEN_EXISTING, 0, 0); ?
and also i have another question. Currently in the source (main.c) we assume in line 368 that sizeof(DWORD) == sizeof(INT) and the compiler issues a warning. Its ok to typecast this too?
find_stab_sections(p,IMAGE_FIRST_SECTION(pNTHeaders),pNTHeaders->FileHeader.NumberOfSections,&pStab,(PINT) &nStabLen,&pStr,&nStabStrLen);
Well, thats all i have to say. Hmm, i forgot, thanks for all your hard work done in ReactOS!. I'm watching the project and the mailing list from 2000 onwards but i only speak if i need to say anything :). I always try to get people interested in this project, explaining to people what is and what its not. Also, i'm a native spanish speaker. I would be happy to help in anyway i could.
thanks again for your great work,
Best regards,
Logan_V8
--
_______________________________________________
Check out the latest SMS services @ http://www.linuxmail.org
This allows you to send and receive SMS through your mailbox.
Powered by Outblaze
Aleksey Bragin wrote:
> We have a rather nice presentation done by Steven Edwards, I suggest we
use it as a base.
I've looked at Stevens in the past, but didn't think there was much in there
we can use anymore.
Also, whilst the theme was pretty, I think it could be made a little more
professional.
> Though we need something fresh and reworked too, because the Steven's one
is already outdated in some parts
> (ReactOS progressed quite a while since presentation were used last time).
I agree, plus Stevens was aimed at a Wine audience, which also needs to be
changed to a general audience.
How about I put together a new base presentation and submit it to SVN once
approved?
An anyone interested in contributing to the presentation can then work
through SVN.
Ged.
I have a few large presentations to give on ReactOS in September, and as a
group we don't have any previous presentations stored. Although not a weekly
event, a few of us do give presentations from time to time, which means we
are probably going through the same process of compiling a presentation from
scratch.
So I was wondering if anyone was interested in putting our heads together
and compiling a default presentation which we can use.
This first default presentation should cover topics such as what ROS is and
what it's goals are, and then move onto a description of the system,
finalising with a short demonstration.
As ROS grows, requests for us to give these sort of things will obviously
grow too, including more detailed discussions on ROS internals. Therefore,
as more specialised presentations are given, we could store these too,
eventually offering a nice collection of presentations which we can pull out
when a need arises.
So, any volunteers?
Ged.
Timo Kreuzer wrote:
> This is the code:
>
> RtlFormatCurrentUserKeyPath(&CurrentUserKeyPath);
>
>
InitializeObjectAttributes(&ObjectAttributes,&CurrentUserKeyPath,OBJ_CASE_IN
SENSITIVE,NULL,NULL);
> Status = ZwOpenKey(&CurrentUserKeyHandle, KEY_READ, &ObjectAttributes);
>
> And I always get Status == STATUS_OBJECT_NAME_NOT_FOUND
What makes you sure ZwOpenKey is failing, and not one of the functions above
it?
You should use error checking where nessesary.
Ged.
WaxDragon wrote:
> Maybe the first order of business would be picking a file format!
Whenever I give presentations, whether it be at work, uni or a company I've
never had anything other than MS PowerPoint available.
I would say this is a must for a base format, and people can convert from
this is need be.
Ged.
Hi,
I tried to read the Values of the SysColors from registry in win32k. But
I get an error opening the CurrentUserKey.
This is the code:
RtlFormatCurrentUserKeyPath(&CurrentUserKeyPath);
InitializeObjectAttributes(&ObjectAttributes,&CurrentUserKeyPath,OBJ_CASE_INSENSITIVE,NULL,NULL);
Status = ZwOpenKey(&CurrentUserKeyHandle, KEY_READ, &ObjectAttributes);
And I always get Status == STATUS_OBJECT_NAME_NOT_FOUND
This is in trunk.
Is there something wrong with my code or is there something wrong with
Registry functions?
Greetings,
Timo
Hi,
I just tested OOo 2.0.3, I get up to most of files are unzipping, then a pop up!
"This package requires a newer version of the Windows Installed.
Do you want to update the version of windows Installed on you system?"
[Yes] [No]
NO! 8^o
I thought we had this fixed! BTW, I can install it under wine.
James
Hi,
build is broken. sorry to find out like this,
[CC] tools/widl/write_msft.c
In file included from tools/widl/widltypes.h:25,
from tools/widl/write_msft.c:48:
include/reactos/wine/guiddef.h:48: warning: redefinition of `LPGUID'
include/psdk/winnt.h:1545: warning: `LPGUID' previously declared here
tools/widl/write_msft.c: In function `ctl2_find_name':
tools/widl/write_msft.c:261: warning: implicit declaration of function `_strnicmp'
[CC] tools/widl/parser.tab.c
In file included from tools/widl/widltypes.h:25,
from tools/widl/widl.h:24,
from parser.y:36:
include/reactos/wine/guiddef.h:48: warning: redefinition of `LPGUID'
include/psdk/winnt.h:1545: warning: `LPGUID' previously declared here
[CC] tools/widl/port/mkstemps.c
[LD] output-i386/tools/widl/widl
obj-i386/tools/widl/write_msft.o(.text+0x25c): In function `ctl2_find_name':
: undefined reference to `_strnicmp'
collect2: ld returned 1 exit status
make: *** [output-i386/tools/widl/widl] Error 1
Thanks,
James
Katarzyna Chauca wrote:
> Couse MSCoder publishes in Spain, France and Germany but you
> can write in english.
Sorry, I thought it was an e-mag, I hadn't realise it was hard copy only.
> As far as I know you have developers from all over the world
> so I hope you will be interested in promote ReactOS in those
> countries.
As a collective group, we are certainly interested in promoting ROS in every
country.
> I saw one magazine from France with ReactOS so why you don't
> want to cooperate with us?
I assume that was written by a 3rd party author, not a ROS dev.
I didn't say I don't want to cooperate, but I personally don't want to write
a 10 page article for a magazine which I can't read.
> I think that such proyects as ReactOS are for developers from
> all countries.
I agree, which is why I personally wouldn't want to write an article limited
to those languages.
However, this doesn't mean someone else won't, you've already had an offer
from weird_w, who is a native English speaker.
Have you ever considered an English release? It would open your magazine up
to a much greater audience.
As for the current status, you would probably have more success targeting
ROS devs who's native language is one of the magazines published languages.
If you popped into IRC, I could point out some of the culprits for you ;)
> Will you please cooperate with us?
Of course, my cooperation was never an issue, hence my replies to your past
emails :)
Ged.
Katarzyna Chauca wrote:
>
> Hi again
> I have no confirmation if someone will write an article about
> ReactOS for
> MSCoder magazine.
> Please let me know
Is there a reason your website is only available in German, French and
Spanish?
I wouldn't want write an article for a magazine which followed the same
pattern.
Ged
Hi again
I have no confirmation if someone will write an article about ReactOS for
MSCoder magazine.
Please let me know
Best Regards
--
Katarzyna Chauca
Market Manager
www.mscoder.org/eswww.hakin9.org/es
Hi,
This could be from 23325 but I started to get this in 23228. Networking is lighting
fast! I had the full ReactOS page less than a second! Once in a while I get this fault.
Thanks,
James
(ntoskrnl/mm/mm.c:221) Page fault at high IRQL was 2, address c000009a
Entered debugger on last-chance exception (Exception Code: 0xc0000005) (Page Fault)
Memory at 0xC000009A could not be read: Page not present.
kdb:> bt
Eip:
<fetnd5.sys:2296>
Frames:
<fetnd5.sys:2053>
<00000002>
Hi,
Some time ago, I thought about implementing the appearance tab of the
desk.cpl, to allow some basic theming.
This is what I've done so far:
http://static.flickr.com/76/200954523_5f103460fd_o.png
On win XP you can change and apply the colors correctly. Fonts / size is
not yet implemented, nor loading of themes from the registry.
But it doesn't work on ROS.
On 0.3.0 RC1 the ColorPicker dialog doesn't work at all. On trunk you
can at least change the color by editing the values.
But they are not applied and either not saved to the registry (regedit
always crashes) or not loaded from registry at startup.
The color button on the background page doesn't work either.
1.) Is loading of syscolors from the registry already implemented? Is
someone going to do it in the near future?
2.) How should storage of themes be done on ROS? Exactly the same way XP
does it (Control Panel\Appearance\New Schemes\xx\...) or in a ROS
specific way?
On XP Scheme names are stored in themeui.dll, I think this is pretty
complicated and is only needed for systems with users having different
languages.
Greetings,
Timo
I manage to get it to boot and play on the net with mozilla and play quake in demo
mode and this bug check. Graphics mode was set to 32 bit 1024x7xx.
(./subsystems/win32/win32k/ntuser/message.c:1107) Copy message to kernel from t8
(dll/win32/winmm/mci.c:900) Couldn't load driver for type L"CDAUDIO".
If you don't have a windows installation accessible from Wine,
you perhaps forgot to create a [mci] section in system.ini
NPOOL: Low-side redzone overwritten, Block 8124d6c0, Size 4, Tag 656e6f4e(enoN)b
KeBugCheck at ntoskrnl/mm/npool.c:1514
(ntoskrnl/mm/mm.c:221) Page fault at high IRQL was 2, address c5b62
(ntoskrnl/mm/mm.c:221) Page fault at high IRQL was 2, address 5c39
Entered debugger on last-chance exception (Exception Code: 0xc0000005) (Page Fa)
(Look here, read on)
Memory at 0x00005C39 could not be written: Page not present.
kdb:> bt
Eip:
<ntoskrnl.exe:71d92 (ntoskrnl/ke/i386/v86m_sup.S:122 (KiV86Complete))>
Frames:
<ntoskrnl.exe:6cabe (ntoskrnl/ke/i386/bios.c:70 (Ke386CallBios))>
<videoprt.sys:2722 (drivers/video/videoprt/int10.c:181 (IntInt10CallBios))>
<vbemp.sys:1ae5 (drivers/video/miniport/vbe/vbemp.c:773 (VBEResetDevice))>
<vbemp.sys:1b2f (drivers/video/miniport/vbe/vbemp.c:543 (VBEResetHw))>
<videoprt.sys:1f26 (drivers/video/videoprt/dispatch.c:49 (IntVideoPortResetDisp>
<8053881c>
<ntoskrnl.exe:1bd6 (ntoskrnl/ke/bug.c:311 (KeBugCheckWithTf))>
<ntoskrnl.exe:1d50 (ntoskrnl/ke/bug.c:493 (KeBugCheckEx))>
<ntoskrnl.exe:1d67 (ntoskrnl/ke/bug.c:514 (KeBugCheck))>
<ntoskrnl.exe:46b25 (ntoskrnl/mm/npool.c:1514 (check_redzone_header))>
<ntoskrnl.exe:46c24 (ntoskrnl/mm/npool.c:1579 (ExFreeNonPagedPool))>
<ntoskrnl.exe:5742b (ntoskrnl/ob/oblife.c:151 (ObpDeleteObject))>
<ntoskrnl.exe:12a45 (ntoskrnl/cm/registry.c:296 (CmiWorkerThread))>
<ntoskrnl.exe:63cd1 (ntoskrnl/ps/thread.c:126 (PspSystemThreadStartup))>
<ntoskrnl.exe:6cb45 (ntoskrnl/ke/i386/ctxswitch.S:82 (KiThreadStartup))>
kdb:>
Hi NG,
first I want to say that it is a great project which I want to join…
I develop since 5 years in C++, but I have only used M$ Dev Studio …
- Is there anything that can I do for the team ?
- Are there documents which describe the coding guidelines ?
BTW:
I have checked out the trunk and build the boot CD. During the setup I got a
BSOD for information check the attached screenshot…
The BSOD comes after the setup has copied the last file …
Kr
Christian
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.3/395 - Release Date: 21.07.2006
Myria wrote:
> I personally think ReactOS should support UTF-8 as a default code page, but I doubt that others agree. This function is one of the many that would have to change...
>
I should warn you: setting UTF-8 as the default codepage instantly
breaks all multibyte-aware code. How so you might wonder? UTF-8 is
"multibyte", only not "Windows multibyte": it doesn't have lead
bytes/trail bytes. Any code that parses multibyte strings needs a
special case for UTF-8 (try it yourself. Set a console's codepage to
UTF-8 and try to run a batch file). You can do it for code you write,
but for code that has already been written...
I've been looking forward to this :)
Would you like a native speaker to provide suggestions for text and grammar
improvements?
-----Original Message-----
From: fireball(a)svn.reactos.org [mailto:fireball@svn.reactos.org]
Sent: 24 July 2006 14:10
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [fireball] 23265: ReactOS Status Report July 2006. If
no major issues will be found, it's going to be published today
Author: fireball
Date: Mon Jul 24 17:10:18 2006
New Revision: 23265
URL: http://svn.reactos.org/svn/reactos?rev=23265&view=rev
Log:
ReactOS Status Report July 2006. If no major issues will be found, it's
going to be published today
Added:
trunk/press-media/Status Reports/July 2006/
trunk/press-media/Status Reports/July 2006/ReactOS status report.doc
(with props)
Added: trunk/press-media/Status Reports/July 2006/ReactOS status report.doc
URL:
http://svn.reactos.org/svn/reactos/trunk/press-media/Status%20Reports/July%2
02006/ReactOS%20status%20report.doc?rev=23265&view=auto
============================================================================
==
Binary file - no diff available.
Propchange: trunk/press-media/Status Reports/July 2006/ReactOS status
report.doc
----------------------------------------------------------------------------
--
svn:mime-type = application/octet-stream
10 pages is quite an order, but I will do my best.
Can I get an approximate wordcount that you would be
looking for?
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Brandon Turner wrote:
> http://sourceforge.net/project/showfiles.php?group_id=6553&pac
> kage_id=6629
>
> I just released 0.3.0 RC1 to sourceforge. Enjoy.
I'm going to bring this up again. It's been well over a month now since RC1
was released.
What are we waiting for to get the final release out?
IMO, we should get 0.3.0 out of the door and immediately branch for 0.3.1.
More than enough work has been done to justify it.
Ged.
How long would you like the article to be? I have
nothing better to do, since I finished my Catia class
for this class cycle, and will be idleing until mid August.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
A Taiwanese user of ReactOS came into the IRC channel to report a bug. If
you set ReactOS's code page to 936, the function RtlMultiByteToUnicodeSize
will crash during startup.
I can't code a fix for it, but I can say how. The algorithm should work
like this:
- If the code page is not DBCS, don't bother, and just set *UnicodeSize to
MbSize * sizeof(WCHAR). This is already done.
- Begin counting with a length of 0.
- While MbSize is not zero:
-- Grab a byte and decrement MbSize.
-- Determine whether it is a DBCS lead byte for the code page.
-- If it is a lead byte:
--- If MbSize is now zero, increment length, set *UnicodeSize to your length
* sizeof(WCHAR) and return STATUS_SUCCESS. The broken half-character is
counted.
--- Decrement MbSize and increment your length. Two DBCS bytes just became
a single Unicode character. We ignore the value of the second byte.
-- If it is not:
--- Increment length.
- Set *UnicodeSize to length * sizeof(WCHAR) and return STATUS_SUCCESS.
Is it possible for a DBCS character's mapping to be a UTF-16 surrogate? If
so, the routine becomes more complicated.
I personally think ReactOS should support UTF-8 as a default code page, but
I doubt that others agree. This function is one of the many that would have
to change...
Melissa
ion(a)svn.reactos.org wrote:
>DstBuffer = (PWSTR)(DstPath + 1);
>
>
that looks pretty eye-burning itself... perhaps I'm just seeing things but,
1) you're incrementing a pointer without checking if it's null ( I
realize this might be safe if we can trust our caller ).
2) do we really want the address: DstPath + sizeof(PUNICODE_STRING)? I
realize this too might work, but do we want to assume that
sizeof(PUNICODE_STRING) == 2*sizeof(USHORT) ???
Hi,
Okay~ I am finishing up rewriting menu mask setting in win32 and use32. The reason
for so much junk in the menus was due to doing a full mask set for setting nothing
other than "Rect" so if the structure was packed with S$@%! it would keep it and
think it was valid data. MenuGetRosMenuItemInfo was naughty too. It set a full
mask and it was passed to MenuSetRosMenuItemInfo and saved! Until I figured this
out it was two weeks later! So I'm fixing this, Set will be selective and create
errors if the wrong combination is used.
Strings may have;
MIIM_TYPE & MFT_STRING == good
MIIM_STRING & MFT_STRING == good
MIIM_STRING == good
so you might have this -> if ((miiW.fMask & MIIM_STRING) || (IS_STRING_ITEM(miiW.fType)))
and this is good due to there might be one of them.
You can not have.
MIIM_TYPE & MIIM_STRING == bad
MIIM_TYPE & MIIM_FTYPE == bad
MIIM_TYPE & MIIM_BITMAP == bad
MIIM_FTYPE & MFT_BITMAP == bad
just read msdn doc on MENUITEMINFO structure, once you decode their logic it starts to make
sense. Remember one supersedes another.
What a mess,
James
WaxDragon wrote:
> The only bug
> I'm concerned about right now is the broken links in the start menu,
> which I think is even fixed in trunk. Nothing else can really be
> addressed at this point.
That is easily fixed with a small hack in the explorer code.
It's certainly not a correct fix, but it will ensure the links work for this
release and allow us to move on.
If you agree, I'll change it tonight.
Ged.
Dear ReactOS Developers,
I apologize for taking these extra ordinary steps in this matter but I
could not locate another way of bringing this issue to attention on your
site.
I was in the IRC channel on the 11th July '06 from about 3am to 5am
GMT... I was posing some very interesting and fundamental questions
about how the project began, it's direction. I was pleased that after a
few minutes most of the users had agreed that ReactOS is intending to be
much more than just NT compatible but in a sense 'Windows + Better'.
After this there was many hours of discussion of how to make it more
than just a windows clone, many of such involving the idea of ReactOS
being similar to Linux in some senses and how to get a Linux feel while
maintaining windows compatibility.
Near the end of the log (I hope these are saved, I have no copies
myself) an 'Alex_Ionescu' joined in on the conversation. He had many
interesting views that greatly heightened the debate to whether ReactOS
should intend to be more than windows now, or at a later date. I was
for the view that in order to gain a user base quicker that it must at
least intent to be more than a clone and was trying to illustrate why.
I first tried to illustrate this and got shot down due to my poor
phrasing of what I meant.
I tried to rephrase my point, and I began with a sentence talking about
firefox as a metaphor of another great piece of floss software. I was
interrupted by Alex_Ionescu (whom is an op in that channel) who told me
i 'must' state my reason using a single statement only and began quoting
regulations of the English language and structuring a proper argument...
so many regulations in fact i feel even if I did comply it would be
difficult to fit it in one statement.
I decided to wait until Alex_Ionescu had given up on such a silly and
clear attempt at limiting my free speech in this matter. However he
persisted to want to know what my point was on this matter, when trying
again... he shut me down. Eventually he set the entire channel to
moderated status only so only those he selected could discuss the
matter. Apparently this was until I could phrase my argument using just
one statement.
I waited until this was lifted and it was not, eventually I came back...
spoke Spanish and under another nick! Granted this was to yet again
give my point across... instead of this they knew who I was and quickly
identified me. A silly tactic I know, but having done this I was
quickly misquoted in the channel from my conversation with Alex_Ionescu
about things I was trying to explain to him as well as very childish
remarks as tho I had said "I love cock". I have high hopes for this
project and wish it every success, I had a very enlightened experience
up until meeting this person with the arguments put and listened and
responded to them well. Alex_Ionescu on the other hand obviously has no
understanding of what it means to express oneself freely, and it would
seem has a childish nature too.
I ask that the decision to give this person power of the level of
communication about the project in the channel be reviewed as quickly as
possible in light of these or other past events.
Thank you,
--
Steven Maddox
(Cyorxamp)
Cyorxamp
http://www.cyorxamp.info
Reactos can be ported to VMI instead:
http://www.vmware.com/interfaces/vmi_specs.htmlhttp://www.vmware.com/pdf/vmi_specs.pdf
It will allow reactos to switch between VMI and native HW on the fly.
Dmitriy Budko
VMware
________________________________
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On
Behalf Of Jerry
Sent: Saturday, July 08, 2006 11:54 AM
To: ReactOS Development List
Subject: Re: [ros-dev] Status of xen port?
Can reactos be made to run on Xen or native hardware by detecting either one
on the fly?
Steven Edwards wrote:
On 7/7/06, Pablo Menichini <pablo(a)menichini.com.ar>
<mailto:pablo@menichini.com.ar> wrote:
I look at xen port and it hasn't been touch in a year. Is it possible
to
port reactos to xen or is the kernel not mature enought? If it's
possible, how long can it take to have a bare minimum port?
Its possible there has just been a lack of developer resources. One of
the developers had the boot loader ported however those changes were
not merged in to the trunk.
fireball(a)svn.reactos.org wrote:
> Author: fireball
> Date: Tue Jul 11 01:03:26 2006
> New Revision: 23005
>
> URL: http://svn.reactos.org/svn/reactos?rev=23005&view=rev
> Log:
> [FORMATTING] / [AUDIT]
> - Cleanup a big coding-style mess
> - Add UNIMPLEMENTED macro in empty functions (otherwise we will never know if they are being called by a 3rd-party driver)
> - Add proper debug headers inclusion in every file
> - Add documentation headers into almost every file (except mcb.c and context.c - will be added later)
> - Standardize per-file headers (some files still lack contributors names, they will be added later too)
>
> No code change except for adding UNIMPLEMENTED macros in the code. Name.c unlocked because the implementations of functions are trivial and in fact could be derived from their names. Not documented functions will be further reviewed.
>
Good work... two things:
1) I think Brandon wrote a tool which does documentation headers using
TinyKRNL syntax. Since ROS's is the same (afaik), maybe you could talk
to him about it instead of doing everything by hand :).
2) Most of the functions are documented in te IFS, I'm not aware of any
undocumented FsRtl stuff... Captive also has implementations for nearly
all of them, and Captive was clean-roomed.
Best regards,
Alex Ionescu
Brandon Turner wrote:
> I have added a debug bootcd build of RC1 to sourceforge.
> So anyone out there looking to get there hands one for
> troubleshooting 0.3.0 can hop on there and grab it.
We've had this up for 3 weeks now.
Changes to trunk have been so heavy since we branched 0.3, we effectively
now have two _very_ different versions of ReactOS .... heh
Maybe our release process needs reviewing slightly ;)
Ged.
Brandon Turner wrote:
> Perhaps I am
> mistaken on the process and missed the time I should have
> made another
> release. If this is the case please feel free to let me know
> what I can
> do to resolve the the problem.
>
> Brandon
No no, nothing has gone wrong, I was just making an observation and putting
some traffic on ros-dev ;)
IIRC, a 2 month release cycle has been mentioned in the past.
Going off our recent release speed, we'd struggle to hit 1 per year ;)
At least we know ROS development is moving fast internally, even if releases
aren't.
Ged.
I opted for a different porting strategy than I originally thought. I
simply couldn't work effectively outside of Visual Studio, so I decided
to create a test application (rdesktop-core-tester), and turn the
smallest subset possible of rdesktop into a statically-linked library
(rdesktop-core). It needs a lot more work, but the results are very
encouraging
Here is the first screenshot *ever* of rdesktop running on pure Win32:
<http://img209.imageshack.us/my.php?image=whohoo3ts.png>
What's wrong with this picture, and why? All text is missing: text
output in RDP is tedious. I'll rip the code off from the X11 version,
but it's not vital for now. All bitmaps are black: this is a bug, or
rather a peculiarity, of rdesktop, which passes only part of raster
operation codes (specifically, the "source" mask), forcing me to do some
bit-juggling to turn them back into valid GDI raster operation codes -
just passing the "mutilated" code resulted in the code for the BLACKNESS
operation every time, and I think it shows. "Shut down..." is upside
down: this is a bitmap painted directly to the screen, without a raster
operation, so it worked out of the box, unlike the Windows logo in the
upper half of the dialog. It turns out RDP bitmaps are top-down, like
the framebuffer but unlike regular bitmaps. Easily solved by creating
all bitmaps with negative heights!
Also, I could not go further than this point at the time, because
keyboard input wasn't hooked up yet! I whipped up some quick support
(very easy, just pass the scancodes on the wire), and of course fixed
the aforementioned issues, tweaked a couple more things, blind-typed the
password (no text output) and...
<http://img62.imageshack.us/my.php?image=meh9ct.png>
... eh. I expected a lot better. So many bugs. And I really don't
understand why the strange "tile" effect... debugging drawing routines
is a pain, let me tell you. I would love to have a night-time bug-hunt,
but I have some *terrible* back pain, and it's becoming really hard to
sit at my desk
All in all, I must say I'm a bit disappointed that the rdesktop authors,
who in general stayed true to the Win32 equivalents of RDP features,
here and there placed annoying little idiosyncracies - like mutilating
rasterops, or using their own structures instead of the "standard"
LOGPEN, LOGBRUSH, etc. or calculating and passing around coordinates of
left-top + dimensions when they're actually RECTs on the wire, forcing
me to recalculate the RECT, and so on, and so on - that I *know* are
going to cause me headaches in the days to come (the off-by-one-pixel
bug must be caused by something like that)
Well, that's all for this week! see you soon!
Aleksey Bragin wrote:
> thanks for sharing, we appreciate more often and better communication
> with our SoC participants.
sorry for the long periods of silence, but I'm currently without
internet connectivity outside of weekends. It should go a lot better
starting next week!
I thought I might share my current progress on my Google Summer of Code
project with this lovely project... Briefly, I don't have a lot of code
but, I believe, a pretty solid design & a well laid down plan. Here is a
writeup I have made about it on my PlanetSoC 2006 blog:
<http://2006.planet-soc.com/node/361>
It's quite long, so I hope you understand why this here post is so short
:-) I'd love any kind of comment on it
See you all soon(er)!
Hi,
I look at xen port and it hasn't been touch in a year. Is it possible to
port reactos to xen or is the kernel not mature enought? If it's
possible, how long can it take to have a bare minimum port?
Thanks,
Pablo
Hello,
in the process of writing a ReactOS quarterly Status Report, I need
every ReactOS Developer (with some exceptions to passive developers
too) to write me a private email, stating what they have been doing
recently, what they plan to do in near future (near future == 6
months), and what did you achieve from the last status report
(january 1st) -- I suppose this will be your favorite section,
because it actually gives every developer a chance to show his most
prominent work, and make others be proud of it.
These emails must be sent as soon as possible, but preferably not
later than Wednesday, 5th of July, 2006. If you are really late and
did not warn me, you risk not being included into this issue of
Status Report.
Thank you,
With the best regards,
Aleksey Bragin
ReactOS Project Coordinator
turner(a)svn.reactos.org wrote:
> + bc->raw_params = malloc(_tcslen(param));
> + _tcscpy(bc->raw_params,param);
Please check the docs, I don't have access to any at the moment, but if I
recall correctly both strlen and wcslen return the number of chars, not
including the '/0'.
This will therefore mean we miss off the '/0' for ASCII builds and only have
half the required space for unicode builds.
Ged.
Aleksey Bragin wrote:
>
> But it's a nice excuse to raise traffic in [ros-dev] !
> :-)
People love a good soap opera.
Although we're still no closer to solving the issue ;)
Ged.
Alex Ionescu wrote:
>
> Like I said, PROGRAMMER implies the person who wrote this
> file, not the
> programmer of the entire project (I don't see why you'd think that...
> just because my name is in lib\rtl\foo.c doesn't mean I wrote
> *all* the kernel).
I don't. Maybe I'm missing something here, but looking at the diff the code
was already in sol.rc.
This code was moved into En.rc, then a copy was taken of En.rc and named as
De.rc, and translated into German
So if 2 copies were made of existing code in sol.rc, and one of these copies
was translated, all the original code still remains (with the exception of
the translations). Thus, the programmer who wrote the original code is still
the programmer.
It's similar to me taking lib\rtl\foo.c splitting it into 2 files and naming
myself as the programmer.
As I said though, I might have something wrong here.
Ged.
Alex Ionescu wrote:
> Probably because on the IRC channel you went all "hahah!! LOL @
> EmuandCo!!!" which I found extremly disrespectful attitude
It has nothing to do with a disrespectful attitude.
It's because I thought is was funny / cheeky, which I still agree with.
People know me better than that.
Can we save the cattiness for IRC please.
Daniel Reimer wrote:
> I did not want to cause problems with that...
I know, which is why I didn't want to drag this through the mud.
Anyway, now as we're on the topic, we might as well try and resolve it.
So, should we be adding headers to resource file?
If yes, what info should be in there. It's clear that the translator and
programmer should be separate headings.
My personal view is that we should leave headers out of resource files.
If translators wanted to add their mark, then a line should be added at the
top of the file saying /* translated by FOO */
Ged.
Whether headers are added or not, my point was simply that a translator
shouldn't put himself into the header as the programmer.
It's a little discourteous to the actual programmer (although most devs
won't actually care), and it creates a false piece of information.
Consider the following scenario:
foo: Hi. one of the buttons is sending the wrong message in the German
dialog. Can you fix it please
bar: Sorry, I'm not a programmer
foo: But it has your name as the programmer in the header...
Perhaps if translators want to be named in resource files, and we feel a
need to put headers in all our resource files too (which I think is a bit
overkill, they should be kept in the main code only) we could include an
extra line for TRANSLATOR:
Anyway, it wasn't my intention to drag this through ros-dev.
-----Original Message-----
From: Peter Dolding [mailto:oiaohm@bluebottle.com]
Sent: 27 June 2006 14:27
To: ReactOS Development List
Subject: Re: [ros-dev] [ros-diffs] [ion] 22649: - Lesson One: Don't revert
commits b ecause your eyes are inventing the word "copyright". I tried
really hard, I really did, but I could not find even the word "copy", much
less "copy right". - Lesson Two: What do yo
Sorry to stick my nose in here.
Two critical points have been missed. Fine in this case since the code
was declare public domain.
Other cases it will not be fine. The new alterations started under a
new copyright. Can override public domain. If it was a GPL licence
even a BSD licence how can you say it up the creek without a paddle.
If a document was created by X person then altered by Y. X persons
copyright still stands until what time it becomes public domain. Even
that Y holds copyright on the alterations so is also allowed a credit
mark under the most country's.
Personally think both have stuffed up minorly. Note strange I could not
find the files in the Reactos tree.
Its also a fault I find with MSVS it does not licence tag the .rc
files. It would make job simpler. If there is no simpler code as all
between the .rc files it would be fine. I totally don't expect that.
The lines I would normally add are.
/*
From project Solitaire
That was under license: Freeware, permission to use under Public Domain
based on <filename>
By Daniel "EmuandCo" Reimer (reimer.daniel(a)freenet.de)
New content licensed under <GPL Reactos as per above>
Translation/Alterations by
<list people here><< People to track down to prove that the license
change was done under permitted grounds ie new content.
*/
Now the file has two licences ie GPL alterations and Public domain
content. If person takes the new content they are stuffed. But a
person could return it to public domain if the remove the content we
have altered.
The other option is just to over license it since its public domain and
it part of a new work. Its still a good idea to leave a marker in case
of future audits.
If someone comes along and said hey your file looks like ours. And we
have markers can quickly say hey did you acquire that file from there.
Yes I know its large. It gets more complex with BSD and GPL. Its all
about tracking. GPL master copyrighter stays. No option to relicense
is given. Alteration by the Reactos team or author marks is all that
could be added. BSD can be overlicened as long as the old BSD header
with first copyright holder stays and the new license is not
incomparable with BSD.
Playing with these things can turn into breach of copyright very quickly.
Murphy, Ged (Bolton) wrote:
> This is still James' code, it's just been moved out of sol.rc and into a
> separate file.
> My point was, if someone translated my code and named themselves as the
> programmer (ok, not using the word copyright) it would p!ss me off a
little
> bit.
>
> I wasn't having a go at anyone, my commit message was entirely civil and
> just correcting something which seemed wrong to me. God only knows why
> you've taken offence, or needed to revert to belittling.
>
> Apologies to EmuandCo, this is not aimed at you.
>
>
> -----Original Message-----
> From: ion(a)svn.reactos.org [mailto:ion@svn.reactos.org]
> Sent: 27 June 2006 00:50
> To: ros-diffs(a)reactos.org
> Subject: [ros-diffs] [ion] 22649: - Lesson One: Don't revert commits
because
> your eyes are inventing the word "copyright". I tried really hard, I
really
> did, but I could not find even the word "copy", much less "copyright". -
> Lesson Two: What do you know! En and D
>
>
> Author: ion
> Date: Tue Jun 27 03:50:03 2006
> New Revision: 22649
>
> URL: http://svn.reactos.org/svn/reactos?rev=22649&view=rev
> Log:
> - Lesson One: Don't revert commits because your eyes are inventing the
word
> "copyright". I tried really hard, I really did, but I could not find even
> the word "copy", much less "copyright".
> - Lesson Two: What do you know! En and De.rc actually *are* our files, not
> James Brown's (his is sol.rc, which hasn't been altered with a ROS
Header).
> - Lesson Three: It is official (voted) ROS Policy that all ROS files have
a
> header. Reverting this header violated it.
>
> Modified:
> trunk/reactos/base/applications/games/solitaire/de.rc
> trunk/reactos/base/applications/games/solitaire/en.rc
>
> Modified: trunk/reactos/base/applications/games/solitaire/de.rc
> URL:
>
http://svn.reactos.org/svn/reactos/trunk/reactos/base/applications/games/sol
> itaire/de.rc?rev=22649&r1=22648&r2=22649&view=diff
>
============================================================================
> ==
> --- trunk/reactos/base/applications/games/solitaire/de.rc (original)
> +++ trunk/reactos/base/applications/games/solitaire/de.rc Tue Jun 27
> 03:50:03 2006
> @@ -1,3 +1,10 @@
> +/*
> + * PROJECT: Solitaire
> + * LICENSE: Freeware, permission to use under Public Domain
> + * FILE: base/applications/games/solitaire/de.rc
> + * PURPOSE: German Language File for Solitaire
> + * PROGRAMMERS: Daniel "EmuandCo" Reimer (reimer.daniel(a)freenet.de)
> + */
> #include "resource.h"
>
> #define APSTUDIO_READONLY_SYMBOLS
>
> Modified: trunk/reactos/base/applications/games/solitaire/en.rc
> URL:
>
http://svn.reactos.org/svn/reactos/trunk/reactos/base/applications/games/sol
> itaire/en.rc?rev=22649&r1=22648&r2=22649&view=diff
>
============================================================================
> ==
> --- trunk/reactos/base/applications/games/solitaire/en.rc (original)
> +++ trunk/reactos/base/applications/games/solitaire/en.rc Tue Jun 27
> 03:50:03 2006
> @@ -1,3 +1,10 @@
> +/*
> + * PROJECT: Solitaire
> + * LICENSE: Freeware, permission to use under Public Domain
> + * FILE: base/applications/games/solitaire/en.rc
> + * PURPOSE: English Language File for Solitaire
> + * PROGRAMMERS: Daniel "EmuandCo" Reimer (reimer.daniel(a)freenet.de)
> + */
> #include "resource.h"
>
> #define APSTUDIO_READONLY_SYMBOLS
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
This is still James' code, it's just been moved out of sol.rc and into a
separate file.
My point was, if someone translated my code and named themselves as the
programmer (ok, not using the word copyright) it would p!ss me off a little
bit.
I wasn't having a go at anyone, my commit message was entirely civil and
just correcting something which seemed wrong to me. God only knows why
you've taken offence, or needed to revert to belittling.
Apologies to EmuandCo, this is not aimed at you.
-----Original Message-----
From: ion(a)svn.reactos.org [mailto:ion@svn.reactos.org]
Sent: 27 June 2006 00:50
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [ion] 22649: - Lesson One: Don't revert commits because
your eyes are inventing the word "copyright". I tried really hard, I really
did, but I could not find even the word "copy", much less "copyright". -
Lesson Two: What do you know! En and D
Author: ion
Date: Tue Jun 27 03:50:03 2006
New Revision: 22649
URL: http://svn.reactos.org/svn/reactos?rev=22649&view=rev
Log:
- Lesson One: Don't revert commits because your eyes are inventing the word
"copyright". I tried really hard, I really did, but I could not find even
the word "copy", much less "copyright".
- Lesson Two: What do you know! En and De.rc actually *are* our files, not
James Brown's (his is sol.rc, which hasn't been altered with a ROS Header).
- Lesson Three: It is official (voted) ROS Policy that all ROS files have a
header. Reverting this header violated it.
Modified:
trunk/reactos/base/applications/games/solitaire/de.rc
trunk/reactos/base/applications/games/solitaire/en.rc
Modified: trunk/reactos/base/applications/games/solitaire/de.rc
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/base/applications/games/sol
itaire/de.rc?rev=22649&r1=22648&r2=22649&view=diff
============================================================================
==
--- trunk/reactos/base/applications/games/solitaire/de.rc (original)
+++ trunk/reactos/base/applications/games/solitaire/de.rc Tue Jun 27
03:50:03 2006
@@ -1,3 +1,10 @@
+/*
+ * PROJECT: Solitaire
+ * LICENSE: Freeware, permission to use under Public Domain
+ * FILE: base/applications/games/solitaire/de.rc
+ * PURPOSE: German Language File for Solitaire
+ * PROGRAMMERS: Daniel "EmuandCo" Reimer (reimer.daniel(a)freenet.de)
+ */
#include "resource.h"
#define APSTUDIO_READONLY_SYMBOLS
Modified: trunk/reactos/base/applications/games/solitaire/en.rc
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/base/applications/games/sol
itaire/en.rc?rev=22649&r1=22648&r2=22649&view=diff
============================================================================
==
--- trunk/reactos/base/applications/games/solitaire/en.rc (original)
+++ trunk/reactos/base/applications/games/solitaire/en.rc Tue Jun 27
03:50:03 2006
@@ -1,3 +1,10 @@
+/*
+ * PROJECT: Solitaire
+ * LICENSE: Freeware, permission to use under Public Domain
+ * FILE: base/applications/games/solitaire/en.rc
+ * PURPOSE: English Language File for Solitaire
+ * PROGRAMMERS: Daniel "EmuandCo" Reimer (reimer.daniel(a)freenet.de)
+ */
#include "resource.h"
#define APSTUDIO_READONLY_SYMBOLS
Thomas Weidenmueller wrote
>
> Ged Murphy wrote:
> > IMO, this change is wrong and should be reverted.
>
> Yes, this change is wrong and should be reverted. Search paths aren't
> correctly supported at the moment, that's why it doesn't
> always find the
> executables...
Might be worth dropping into the 0.3 branch though as a quick fix if the
real issue isn't solved before RC2.
Ged.
WinFS is (more or less) dead, it has been announced on their official web blog:
http://blogs.msdn.com/winfs/archive/2006/06/23/644706.aspx
Some useful parts go to SQL Server development branch.
Reminds me of Cairo (early 90-ties), MSFT never achived that task.
Only some parts were integrated as ActiveDirectory in Win2k and
improved OLE in Win 9x/NT.
The Vista search seems to be very same technology as it has been
shipped with WinNT 5.0+ (but deactivated by default). Just a new
frontend has been added which looks more confusing than the WinXP
variant.
The channel9 videos featuring WinFS looks promising, although I heard
(from beta1 testers) the technology was not .
DrFred just mangers getting a answers
DrFred: [09:54] EdgyEft: nachos: they're having spasms after some idiots hacked them
(10:01:08) DrFred: I got voice in #freenet-social
(10:01:29) DrFred: [09:55] rob: the servers are working fine, we are just working on a fix for the previous issue
[09:56] rob: shoudn't be much longer until everything is back to normal
hpoussin(a)svn.reactos.org wrote:
> Author: hpoussin
> Date: Sun Jun 25 04:52:40 2006
> New Revision: 22607
>
> URL: http://svn.reactos.org/svn/reactos?rev=22607&view=rev
> Log:
> Let StartService really start the service.
> This enables the plug and play manager during second stage setup
>
For anyone interested in NT services, we now have the ability to start
services with StartService.
The following is a log taken when starting tcpsvcs with servman:
(base\system\services\database.c:50) ScmGetServiceEntryByName() called
(base\system\services\database.c:60) Found service: 'tcpsvcs'
(./dll/win32/advapi32/service/scm.c:1993) dwBufSize: 0
(base\system\services\rpcserver.c:1760) ScmrStartServiceW() called
(base\system\services\database.c:748) ScmStartService() called
(base\system\services\database.c:751) Service->Type: 32
(base\system\services\database.c:632) ImagePath:
'C:\ReactOS\system32\tcpsvcs.exe'
(base\system\services\database.c:633) Type: 20
(base\system\services\database.c:644) CreateNamedPipeW() done
(base\system\services\database.c:681) Process Id: 428 Handle cc
(base\system\services\database.c:684) Thread Id: 432 Handle d0
(base\system\services\database.c:701) Control pipe connected!
(base\system\services\database.c:716) Received process id 428
(base\system\services\database.c:543) ScmSendStartCommand() called
(base\system\services\database.c:591) ScmSendStartCommand() done
(base\system\services\database.c:766) ScmStartService() done (Status 0)
Hi
it is working now after alot of hours down.
so we are back at freenode.net
I sugest if some thing happen to freenode.net
we meetings in efnet until freenode.net is working again
what do people think of that backup plan
He's on Linux, so RosBE is no use.
If someone could just initialise that pointer to NULL it would fix it for
him.
I would do it, but I don't have access to the tree until I get home from
work.
Cheers,
Ged.
p.s. I've no http access at the mo, hence the reply to ros-dev ;)
-----Original Message-----
From: ReactOS.Bugzilla(a)reactos.org [mailto:ReactOS.Bugzilla@reactos.org]
Sent: 23 June 2006 08:33
To: ros-bugs(a)reactos.org
Subject: [ros-bugs] [Bug 1618] internettime.c broken, lpAddress possibly
uninitialized in "InetTimePageProc"
http://www.reactos.org/bugzilla/show_bug.cgi?id=1618
hpoussin(a)reactos.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Comment #3 from hpoussin(a)reactos.org 2006-06-23 09:33 CET -------
Works for me with official ReactOS build environment (GCC 3.4.2, ld 2.16.91)
See
http://www.reactos.org/wiki/index.php/HOWTO/setup_a_build_environment_for_Wi
ndows#ReactOS_Build_Environment_.28RosBE.29
for more details
--
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Ros-bugs mailing list
Ros-bugs(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-bugs
I know I've mentioned this before, but I'll do it officially now :)
Can we change the text format svn-diff sends its messages In from rich text
to plain text?
Every diff I read, I have to click 'reply' first in order for it to be
readable. (my client changes to plain text when replying)
Diff's in rich text are pretty ugly and difficult to follow.
Cheers,
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Hi all!
I've installed 0.3RC1 on HD. Besides that it didn't overwrite
the MBR, the install went fine.
* FireFox 1.5.0.4 doesn't install correctly - XUL error window
pops up at startup.
* when dragging and dropping a file in explorer from CD to the
desktop, it immediately shut down the box, just like pulling
the plug. Later drag/drop in explorer didn't work at all.
* when trying to install other progs (clicking on the install
EXE) nothing happens - not even an error dialog
* tried to install the Java Runtime - installation went fine,
but there are no java related files anywhere, except
Program Files\Java\jre1.5.....\COPYRIGHT
Let me know if you want some details and how I can provide them.
I'm primarily a linux geek ;-)
Best regards,
Hannes.
Since our MmNotPresentFault handler and kin need to lock the
associated MADDRESS_SPACE, we often need to lock an address space
when it's already been locked. Until now, this has caused a
recursive acquisition of a kernel mutex.
The current kernel bugchecks for me when running the wget binary
here:
http://www.superheterodyne.net/reactos/mm_edit/wget.exe
So I've added a boolean to MADDRESS_SPACE to specify that it's been
locked and propogated its use (and also disentangled this flag from
the one specifying that pages are locked in various cases).
The patch is here:
http://www.superheterodyne.net/reactos/mm_edit/mm.diff
There's a sore spot in section.c at line 684 where I got a bugcheck,
but it was easy enough to check for a NULL region. This probably
isn't right however.
jimtabor was seeing bugchecks at startup that are at least
apparently solved by this patch, but I'm sure that those more in
tune with the kernel can weigh in on whether we should do something
like this or whether the real problem is deeper or different.
--
Discordant is the murmur at such treading down of lovely things while
god's most lordly gift to man is decency of mind. Call that man only
blest who has in sweet tranquility brought his life to close.
If only I could act as such, my hope is good.
-- Aeschylus' Agamemnon (translated by H. W. Smyth)
sata harddisk support needed
2006/6/20, ros-dev-request(a)reactos.org <ros-dev-request(a)reactos.org>:
>
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
> 1. 0.3.0 RC1 Update (Brandon Turner)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 19 Jun 2006 12:48:35 -0400
> From: Brandon Turner <turnerb7(a)msu.edu>
> Subject: [ros-dev] 0.3.0 RC1 Update
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <4496D563.5090201(a)msu.edu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I have added a debug bootcd build of RC1 to sourceforge. So anyone out
> there looking to get there hands one for troubleshooting 0.3.0 can hop
> on there and grab it.
>
> Brandon
>
>
> ------------------------------
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> End of Ros-dev Digest, Vol 22, Issue 23
> ***************************************
>
I have added a debug bootcd build of RC1 to sourceforge. So anyone out
there looking to get there hands one for troubleshooting 0.3.0 can hop
on there and grab it.
Brandon
After I made some german translation updates and new translations, I
spotted a small problem. I dont know if you see a problem here, but
thats why I post it here. While looking through the .rc Files I found
out that most apps use one font (Most use MS Shell Dlg which I think is
the best one) but not all. Some use Tahoma, others use MS Sans Serif and
one even uses Bitstream Verdana. I think this way it does not look like
a professional work. It more looks like a thrown together bunch of work,
which does not fit together. Especially if a app uses different fonts in
some parts than in others. Thats why I made some patches to set the Font
to MS Shell Dlg Size 8 except for Asian Languages (Like XP uses it and
we should do, too for compatibility) and talked to frik85 about it. He
said I should ask you all and that's what I do here. How do you think
about it?
Daniel "EmuandCo" Reimer
What are we waiting on for this now?
I see RC1 still isn't on sourceforge, I thought this was meant to be out a
few weeks ago??
Can someone list the requirements and any potential blockers to try and
prompt some action
Cheers,
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
I've been trying to sync riched20 for the past hour but am not getting
anywhere.
Our last sync was 0.9.5, but since then quite a bit more code has been
added.
The 2 problematic lines are in 0.9.15, editor.c, lines 1093 and 1912.
They refer to IRichEditOleCallback callbacks in richole.idl, which is
new for us.
I'm not familiar with idl files, but we seem to implement them in
/include/reactos/idl.
I've tried dropping the idl in there, creating the respective .acf and
modding the rbuild file.
However I'm still having problems.
Can anyone shed any light on this?
I've dropped 0.9.15 into our vendor dir, if anyone wants to sync it for us.
It's a straight sync, we have no ROS specific code in this lib.
Ged
Hi all!
This is the hivesys.inf PCNet section. I copied fetnd5a.sys to pcnet.sys.
I can query network properties w/o a crash! All I get is IPHLPAPI.dll need
more work and GetAdapterInfo did not return the expected data.
Bus 0, device 18, function 0, Ven 1106/Dev 3065/class 0200.
Start->Settings->Settings Menu->Network Properties
Select VT6102->Properties, get the VIA PCNet Status Menu, select Properties,
get the VIA PCNet Pro~ Menu, select Internet Protocol (TCP/IP), select
Properties, get the Error menu.
Wow! Did not crash!
Need to check if I'm on the right track here!
Thanks,
James
; ReactOS PCNet NIC driver
; To use the AMD supplied driver change the driver name to pcntn5m.sys
;
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","ErrorControl",0x00010001,0x00000000
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","Group",0x00000000,"NDIS"
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","ImagePath",0x00020000,"system32\drivers\pcnet.sys"
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","Start",0x00010001,0x00000003
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","Type",0x00010001,0x00000001
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet\Enum","0",0x00000000,"PCI\VEN_1106&DEV_3065\0000"
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet\Enum","Count",0x00010001,0x00000001
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet\Enum","NextInstance",0x00010001,0x00000001
HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_10\0000","Service",0x00000000,"PCNet"
HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_10\0000","Class",0x00000000,"Net"
HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_10\0000","ClassGUID",0x00000000,"{4D36E972-E325-11CE-BFC1-08002BE10318}"
HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_10\0000","Driver",0x00000000,"{4D36E972-E325-11CE-BFC1-08002BE10318}\0000"
; Configuration Entries for the PCNet Adapter
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","Characteristics",0x00010001,0x00000000
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","DriverDesc",0x00000000,"VT6102"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ProviderName",0x00000000,"VIA
Tech"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","NetCfgInstanceId",0x00000000,"{RANDOMCFGGUIDFOR_PCNET1}"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000\Linkage","Export",0x00000000,"\Device\PCNet1"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000\Linkage","RootDevice",0x00000000,"PCNet1"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000\Linkage","UpperBind",0x00000000,"Tcpip"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BUS_TO_SCAN",0x00000000,"ALL"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BUSTIMER",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BUSTYPE",0x00000000,"5"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","EXTPHY",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","FDUP",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","LED0",0x00000000,"10000"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","LED1",0x00000000,"10000"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","LED2",0x00000000,"10000"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","LED3",0x00000000,"10000"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","MPMODE",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","TP",0x00000000,"1"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","AdapterCFID",0x00000000,"811929862"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","AdapterType",0x00000000,"5"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","SlotNumber",0x00000000,"8"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BusNumber",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","FunctionNumber",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","EarlyReceive",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","EarlyTransmit",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BurstLength",0x00000000,"1"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ReceiveBurstIndicate",0x00000000,"64"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ReceiveBuffers",0x00000000,"64"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","TransmitBuffers",0x00000000,"32"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ReceiveThreshold",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","TransmitThreshold",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","MapRegisters",0x00000000,"32"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ConnectionType",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ValidatePacketLen",0x00000000,"1"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","IPXSPXAutoFrame",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{RANDOMCFGGUIDFOR_PCNET1}",,0x00000000,"Network
Adapters"
HKLM,"SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{RANDOMCFGGUIDFOR_PCNET1}\Connection","Name",0x00000000,"VIA
PCNet"
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet1\Parameters\Tcpip","DefaultGateway",0x00010000,"10.65.145.1"
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet1\Parameters\Tcpip","IPAddress",0x00010000,"10.65.145.79"
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet1\Parameters\Tcpip","SubnetMask",0x00010000,"255.255.255.0"
We search an author for our "ReactOS Weekly Newsletter".
History:
Jason Filby had established the ReactOS Weekly Newsletter (called
"ReactOS Weekly") in 1999 as a useful weekly news summary located on
www.reactos.com. In 2000 the newsletter had been discontinued. With
the website redesign in summer 2005, the newsletter came back with
Stuart "TwoTailedFox" Robbins as author.
Requirements:
Here are requirements for an author:
1. Have enough time once a week to write the newsletter text (e.g. every sunday)
2. Be good in english language
3. Understand our technlogy (svn, reactos, windows nt, win32, kernel,
drivers, apps, etc.)
4. Be in frequent contact with the ReactOS developer, and come in our
IRC channels too (because mailing list traffic may be sometimes slow)
5. HTML knowledge is not required but an advantage
Goal:
The "ReactOS Weekly Newsletter" should be weekly (as the name implies)
and sum up the ongoing mailing list discussions as well as irc
conversations.
Additionally it should contain ReactOS news, like new releases.
>From time to time interviews, reviews (of apps compatibility and
reactos functions and releases) and maybe audio-podcasts, etc. would
be great too.
The layout of the newsletter issue page can be the same as the latest
one (e.g. http://www.reactos.org/xhtml/en/newsletter_11.html), similar
as WineHQ's one, or different.
Previous newsletters - links:
10/2005 - 02/2005:
http://www.reactos.org/?page=newsletters
1999 - 2000:
http://web.archive.org/web/20000522174140/reactos.com/public/weekly.html
WineHQ'S newsletters:
http://www.winehq.com/?issue=back
Mailing List Information:
http://www.reactos.org/?page=community_mailinglists
IRC Channel Information:
http://www.reactos.org/?page=community_irc
So... if this sounds like something you would like to do, please reply
to this mailing list email explaining why you you think you would be a
good newsletter author.
Klemens Friedl
Alex Ionescu wrote:
> In defense to Hervé, you actually need to clean *TWICE*. That's right,
> you must write:
> make intrlck_clean && make intrlck_clean & make ntdll_clean & make
> ntdll_install.
What does running 'make intrlck_clean' do the second time which it doesn't
do the first time round?
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Hi all!
When the install popup for the disk controller is displayed. I can install from
and select everything but NEXT!
Select *Next* this will happen, (tested this 4 times now, same thing)
(dll/win32/newdev/newdev.c:745) Installing Other ACPI device (ACPI\PNP0C04\1&7313ac9&0000)
(dll/win32/newdev/newdev.c:466) Include removable devices: no
(dll/win32/newdev/newdev.c:467) Include custom path : no
(dll/win32/newdev/newdev.c:534) Installing driver (Generic system devices): Math coprocessor
(dll/win32/newdev/newdev.c:745) Installing Disk controller (ACPI\PNP0700\1&7313ac9&0000)
(dll/win32/newdev/newdev.c:466) Include removable devices: no
(dll/win32/newdev/newdev.c:467) Include custom path : no
(dll/win32/shell32/classes.c:381) HCR_GetFolderAttributes should be called for simple PIDL's only!
(dll/win32/shell32/shellpath.c:1688) Failed to create directory 'L".\\Desktop"'.
(dll/win32/newdev/newdev.c:466) Include removable devices: yes
(dll/win32/newdev/newdev.c:467) Include custom path : no
KeBugCheckWithTf at ntoskrnl/ke/i386/exp.c:1241
A problem has been detected and ReactOS has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
Technical information:
*** STOP: 0x0000001E (0xC0000005,0x80033CF6,0x00000000,0x00000030)
*** ntoskrnl.exe - Address 0x80033CF6 base at 0x80000000, DateStamp 0x0
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:80033cf6 <ntoskrnl.exe:33cf6 (ntoskrnl/io/file.c:970 (IoCreateFile))>
cr2 30 cr3 3be68000 Proc: 8178f328 Pid: d8 <umpnpmgr.exe> Thrd: 817a4558 Tid: e8
DS 23 ES 23 FS 30 GS 0
EAX: 00000000 EBX: 9fa43c34 ECX: 000023be
EDX: 81f5d6e4 EBP: 9fa43cf0 ESI: 00000000 ESP: 9fa43b50
EDI: 00000000 EFLAGS: 00010296 kESP 9fa43b50 kernel stack base 9fa3e000
Frames:
<ntoskrnl.exe:3459a (ntoskrnl/io/file.c:1527 (NtCreateFile))>
<ntoskrnl.exe:66657 (ntoskrnl/ke/i386/trap.s:306 (KiFastCallEntry))>
<KERNEL32.dll:9c6f (dll/win32/kernel32/file/volume.c:57 (InternalOpenDirW))>
I think my hardware is not ReactOS compatible.
Thanks,
James
Hi,
Annoyed by the ever-growing blame on my patches as well as the
continuing lack of attention regarding the SESSION_5 BSOD, I've taken
the liberty to momentarily put on hold my current paid work and take a
look at the issue (which thankfully only took 30 minutes).
As I suspected, it has absolutely nothing to do with any Ob stuff and is
the result of ntdll being messed up after the recent changes to
lib\intrlck. Revert them, clean interlck/ntdll, rebuild, and voila,
you're back to a working ROS.
In defense to Hervé, you actually need to clean *TWICE*. That's right,
you must write:
make intrlck_clean && make intrlck_clean & make ntdll_clean & make
ntdll_install.
It is *NOT* enough to merely write ntdll_clean, either.
I'm going to assume that Hervé only cleaned interlck once (as anyone
would normally do) and kept using the "correct" library. As soon as he
(and others) built a new copy of the tree (probably around one of my
patches), the interlck lib now got cleaned twice and the broken one
started coming into use. Score one for my complaints against rbuild.
If I could give some advice, next time, spend less time assigning blame
on me, and actually try to find the bug (yes, this sounds arrogant, but
it DOES get annoying to be the poster boy for boot BSODs. The last one I
caused was over 12 months ago).
Best regards,
Alex Ionescu
Hi,
With ROS_LEAN_AND_MEAN and DBG = 1, with all drivers and the bells and
whistles, a boot to NCLI with 8MB gave me a working system with still
2MB to spare (perhaps for a native FTP server or other application).
If I remove the network layer, I can boot with 6MB, and I still have 1MB
free.
I'm trying with DBG = 0 now. Maybe I can boot with 4MB :D.
Best regards,
Alex Ionescu
> > I spoke with Gé and he explained me the vendor import process in
> > short. As soon as I find some time I will try out it myself and update
> > the Wine libs in our SVN tree, if you don't mind.
I have just updated comctl32 to 0.9.15, and will continue to keep this lib
updated at every Wine release. Although r22329 was not mailed out via
svn-diff (any ideas Aleksey??)
I may also look after one or two other libs along with this.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
I'm answering to ros-dev so all developers could share their point of
view (Klemens' original email is attached below).
As I basically outlined in an irc conversation, there are 3 possible
ways for us to sync with the Wine project:
1) Do manual syncs (the current way), keeping their code in our tree,
building with our build system
2) Do auto-import of their source code into our tree, plus
automatically detect changes in their build files and propogate them
to our .rbuild files
3) Do binary-syncing of the dlls which are free from reactos and wine
hacks, and do manual syncs for dlls which are forked (like setupapi
which is better implemented, directx dlls which are partly shared and
partly implemented differently, etc).
However, it was not possible to easily come to a solution what to do.
I will give a small overview of all ways:
1) We lag behind, providing outdated, featureless and buggy version
of dlls. And even more, we depend on dlls bugs, reactos hacks in
them. Syncing them requires time and constant efforts.
From the good side we have absolute control over the libraries - we
can enable/disable debug messages, build them for different
architectures, optimize for different CPUs etc
2) This could sound like an ideal way, because it keeps advantages of
1. plus removing disadvantages of having to waste time doing syncs.
However conversion from Wine's build system makefiles to ReactOS's
build system .rbuild isn't trivial. Plus developing an auto-syncer
between Cvs/Git and our SVN doesn't look like an easy task too.
3) Reduces compilation time, however wine dlls are built on another
server, and just downloaded during build process (or kept in SVN
server in binary form). It'd be needed to adjust building mechanism
to be able to produce other platform binaries. Updates will be
"heavy" (but initial download smaller).
I'm listening to your (all ReactOS and Wine devs) comments, and
probably I will write answers to Klemens' email later.
WBR,
Aleksey Bragin.
On Jun 12, 2006, at 2:35 PM, Klemens Friedl wrote:
> Hi Aleksey,
>
> I spoke with Gé and he explained me the vendor import process in
> short. As soon as I find some time I will try out it myself and update
> the Wine libs in our SVN tree, if you don't mind.
>
> Or do you want to switch to a binary wine files in trunk anyway?
>
> I will try to update Wine files about every months after the first
> time, if that is okay. The changes of wine 0.9.x of every two week are
> minor things so, every months should be fine. sdwards mentioned that
> timeframe too, as we discussed about that topic about one week ago on
> #winehackers and #reactos (the first time).
>
> btw. Gé mentioned there ARE reasons why our Wine libs DO differ from
> WineHQ's one. Well Gé is not a ros dev anymore but he had not done the
> vendor import work and maintain all the changes for fun, it's
> important to have our adjustments in there.
> Imagine for example all icons would got lost.
>
> Wine does use Unix specific functions like "unixfs" in several libs,
> the sound libs will get a lot different in near future too
> (silverblade is working in this area) and several directx libs. So a
> quick auto vendor import won't work anyway.
>
>
> In my opinion, the binary idea is not worth any efford:
>
> In my opinion, binary files on in a svn dir is a very bad solution.
> You cannot view the source and commit the changes, you have to
> download all binary files every time (every 2 weeks), binary files are
> not portable, etc.
> The advantages of source code is in addition to the oposite of the
> facts above that you have to download only the diffs of the file
> changes (svn client does that for you) and that have everything
> (source) on your local hdd.
> Sure the build-time would decrease about 10-15% if we use binary
> files, but i don't bother about 15% time.
>
> And please shift the wine lib conversation to ros-dev(a)reactos.org.
> The irc chat is not suitable for such a discussion where more than 3-4
> devs are involved. It is not possible to answer to more then one msg
> the same time. And while you write, several other persons post other
> msg's.
> Mailing lists does have a purpose and does make sense here!
> E-Mail's are written in a better english, no short abbreviations, etc.
> and the devs does think a bit longer about what the write (no offence
> here!).
>
>
> Best regards,
> Klemens
Someone on this mailing list gave me a crash-course on using COM
(possibly KJK, but it was a while ago so I'm not sure.)
Anyway, I'm fairly comfortable with the various macros and sort of
understand how it works now.
== SOUND ARCHITECTURE ==
I've been told that Windows Vista has a new user-mode set of
audio/multimedia APIs, which replace kernel-mode streaming. Evidently
most of the kernel-mode components for this no longer exist in Vista.
Instead, communication goes via user-mode components until PORTCLS.SYS,
the only remaining kernel-streaming related component.
PORTCLS.SYS interacts with WDM audio drivers. WDMAUD.DRV interacts with
the MME API (winmm.dll). So the path from the MME API to the WDM driver
may be different, but older applications and drivers should see no
difference there.
I think implementing the audio system used in Vista would be a good
thing to do - since the kernel streaming components have been completely
removed from Vista, there is no point in implementing them in ReactOS.
There should be no reason why an NT4 audio driver wouldn't work even on
Vista, and XP drivers should work too. Obviously this won't be the case,
though, as all drivers will probably need to be designed specifically
for Vista. My point however, is that the MME API has changed slightly,
but will still work with older drivers.
(As a side-note, I recall that our implementation of WINMM.DLL - as
copied over from WINE - doesn't appear to deal with Plug and Play at
all. This is something that will need to be remedied.)
== PORTCLS.SYS : COM IN THE KERNEL ==
This took a while for me to get my head around, and I'm at the stage now
where I can happily declare a COM interface or class. But I'm having
difficulty figuring out how I should actually create an instance of one
in the kernel.
Apparently, there exists some kernel equivalent of CoCreateInstance.
In any case, I'd prefer to work with classes using C++, which I believe
can be done with COM. So I just need to know how to implement a COM
class using C++. Up until now I've guessed it as being:
class IBlahBlah_Impl : public IBlahBlah
Is this right?
I'm working on the IPort code at the moment, and am wondering how to
implement this:
PORTCLASSAPI NTSTATUS NTAPI
PcNewPort(
OUT PPORT *OutPort,
IN REFCLSID ClassId)
{
/*
ClassId must be one of:
CLSID_PortDMus (IPortDMus) defined in dmusicks.h
CLSID_PortMidi (IPortMidi)
CLSID_PortTopology (IPortTopology)
CLSID_PortWaveCyclic (IPortWaveCyclic)
CLSID_PortWavePci (IPortWavePci)
*/
}
Yes, it's just a commented function. From the documentation, the caller
passes one of the CLSID's from the above list, and receives a pointer to
an IPort.
Question is, how do I compare the parameter with one of the CLSIDs? And
again, how do I create an instance of the class in kernel-mode?
If anyone can shed a little light on this, I'd appreciate it.
-Andrew
I would like to propose a target hardware list.
Like a type of motherboard that should be used.
Sound card and video card.
Thoughts?
--
Dave Johnson
http://www.davefilms.us DaveFILMS(r)
http://thevoicezone.us The Voice Zone™
Voice Talent
Writer, Producer, Director
Independent Audio Theater Producer
http://www.perditioncity.us
voiceoverjobs(a)gmail.com
Member of the Darker Projects team.
http://www.darkerprojects.comShadoeWorld.com Correspondent
----------------------------------------------------------
Tired of a proprietary Windows on your computer ?
Use free ReactOS instead ( http://www.reactos.org )
Hi,
I am aware that I broke trunk. This is because I've removed the code in
ObReferenceObjectByHandle which allowed GENERIC access masks to be
converted. This API does NOT support GENERIC access masks and converting
to them was incorrect, however, as always, plenty of code in ROS abused
the system and calls this API incorrectly. Although ObOpenObjectByName
should return a handle and IoCreateFile should be done with it, because
parsing is broken (so it creeps up again!), we try to re-reference it by
handle to get its pointer... however, this attempt is made with the
current AccessMode, which happens to be User, and if the AccessMask was
GENERIC... we fail. ObOpenObjectByName is made to be used with GENERIC
access masks so that's really not a problem. Hopefully the I/O File
stuff is the only place where this happens, so I will implement a simple
hack - call ObReferenceObjectByHandle with a KernelMode parameter so
that access checks are skipped (we've already done them in
ObOpenObjectByName anyways!).
Best regards,
Alex Ionescu
Should ReactOS copy unnecessary restrictions that Windows has?
The example I'm thinking of is NtSetLdtEntries. In Windows NT (and
currently ReactOS as well), this function will not let you create an LDT
entry whose limit is above the user/kernel barrier. This restriction sounds
like it was made with security in mind, but it doesn't affect security. The
processor's page table will already block access to kernel memory no matter
what selector you use. After all, the default user CS and DS already have a
limit of FFFFFFFF.
Should such a problem be fixed?
Fireball said "no, unless some 3rd party app or driver depends on them" when
I asked about whether such restrictions should be copied. Pretty much the
only thing using NtSetLdtEntries is NTVDM, and this restriction already
causes some DOS programs to break that would otherwise work. (Such programs
are usually setting selectors that wrap the address space.)
Melissa
I've noticed that in the ReactOS source code, there are many places where a
parameter or structure is ULONG when it should really be SIZE_T. Using
ULONG instead of SIZE_T is not portable. It will be difficult to port
ReactOS to x64 and Itanium in the future because of this.
I think the project should stop the bleeding by requiring all new code to
make proper use of ULONG versus SIZE_T. This does mean going against the
documentation of native syscalls on the Internet, but it must be done
sometime.
Of course, I'm not really part of the project...
Melissa
Hi all
Could be all based on wine patches, I can no longer get xchat 2 and the new one to run. I noticed it
can not find the lib directory in the launch directory. Wine has this problem too. Also when
installing the new X-Chat 2 from http://www.silverex.org/download/xchat-2.6.2-1.exe, It installs the
Font to C:\ReactOS\Fonts not C:\ReactOS\media\fonts. I had to create C:\ReactOS\Fonts so I can have
a clean install.
I tested my GGO patch and the SVN and the result are the same.
Okay, wine does this too, I tested it.
(dll/ntdll/ldr/utils.c:2019) Failed to create or open dll section of 'libgtk-win
32-2.0-0.dll' (Status c0000135)
(dll/ntdll/ldr/utils.c:1347) failed to load libgtk-win32-2.0-0.dll
(dll/ntdll/ldr/utils.c:1812) failed to load libgtk-win32-2.0-0.dll
(dll/ntdll/ldr/utils.c:1934) LdrFixupImports() failed for xchat.EXE
(dll/ntdll/ldr/startup.c:485) Failed to initialize image
Then do it from lib, "..\xchat"
(dll/ntdll/ldr/utils.c:2019) Failed to create or open dll section of
'pango-1.8.2/lib/pango/1.4.0/modules/pango-basic-win32.dll"' (Status c0000135)
You will get a popup.
This has been a problem for years!
Thanks,
James
Hi,
I'm getting this with Mozilla, Firefox and SeaMonkey.
KeBugCheck at ntoskrnl/cm/regobj.c:528
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
Technical information:
*** STOP: 0x00000051 (0x00000000,0x00000000,0x00000000,0x00000000)
Frames:
<ntoskrnl.exe:1d50 (ntoskrnl/ke/bug.c:493 (KeBugCheckEx))>
<ntoskrnl.exe:1d67 (ntoskrnl/ke/bug.c:514 (KeBugCheck))>
<ntoskrnl.exe:129c6 (ntoskrnl/cm/regobj.c:528 (CmiObjectDelete))>
<ntoskrnl.exe:52c6b (ntoskrnl/ob/oblife.c:151 (ObpDeleteObject))>
<ntoskrnl.exe:1290c (ntoskrnl/cm/regobj.c:523 (CmiObjectDelete))>
<ntoskrnl.exe:52c6b (ntoskrnl/ob/oblife.c:151 (ObpDeleteObject))>
<ntoskrnl.exe:50f4c (ntoskrnl/ob/obhandle.c:153 (ObpDecrementHandleCount))>
<ntoskrnl.exe:510b0 (ntoskrnl/ob/obhandle.c:244 (ObpDeleteHandle))>
<ntoskrnl.exe:52166 (ntoskrnl/ob/obhandle.c:1125 (NtClose))>
<ntoskrnl.exe:66527 (ntoskrnl/ke/i386/trap.s:306 (KiFastCallEntry))>
<ADVAPI32.dll:7dd9 (dll/win32/advapi32/reg/reg.c:1178 (RegDeleteKeyA))>
All three are the same,
James
I cant seem to make a stable qemu install for the release, wmare works
fine though. On the first boot to the installed desktop, it just shuts
down after about 1 sec. I usually see the device wizard pop up for a
sec and then it just turns off. Anyone else having thse problems? Any
hints?
Brandon
Do we have a target harware spec?
Or will ROS be for general harware like regular Windows?
--
Dave Johnson
http://www.davefilms.us DaveFILMS(r)
http://thevoicezone.us The Voice Zone™
Voice Talent
Writer, Producer, Director
Independent Audio Theater Producer
http://www.perditioncity.us
voiceoverjobs(a)gmail.com
Member of the Darker Projects team.
http://www.darkerprojects.comShadoeWorld.com Correspondent
----------------------------------------------------------
Tired of a proprietary Windows on your computer ?
Use free ReactOS instead ( http://www.reactos.org )
0.3.0 is now RC1. Hopefully Brandon will have time to put up RC1 on
SF soon, but those inclined can check out a copy now. While I will
allow a wallpaper to be added before release, anything else needs to
be a bugfix against a bug in Bugzilla.
WD
--
ReactOS is a hub, follow the spokes and you'll
immediately find absolutely everything you need
to know about Windows. ReactOS is not just
software, it's people.
kjk_hyperion
My name is Kate Chauca and I represent MSCoder Independent magazine for
developers using Microsoft platforms (www.mscoder.eu/es).
We would like to invite all of you to help us to promote ReactOS. We are
looking for people who will write articles about ReactOS for our magazine.
We would like to place live ReactOS on the CD of our magazine.
If you find it interesting please let me know. Every one can cooperate with
us.
Best Regards
Kate Chauca
katarzyna.chauca(a)software.com.pl
www.mscoder.eu/es
There are three integrated systems needed for authentication in ReactOS:
1. Winlogin
2. MSGINA (ROSGINA would work better, no?)
3. Some sort of Identity Management system with support for local and
remote authentication (remote can come with SMB support later)
Tiers 2 & 3 can be developed and tested on a non ReactOS system (aka a
real Windows system) initially (tho with the code staying in the ROS
Subversion tree), while Tier 1 is ReactOS specific.
I thus see three stages (aligned with the systems mentioned above):
1. Identity Management System with basic tools (get Setup to use it, at
least some basic command line tools to add and remove users and change
passwords, no need for a UI yet)
2. A ROSGINA that uses the Identity Management System
3. Get Winlogin back up and running and using the ROSGINA for
authentication.
Since its stage 1:
The identity management system's sole purpose is to create a
cross-subsystem, ReactOS-wide way to authenticate users. How each
subsystem uses the information provided is up to the individual
subsystem. As such, I see a database (Berkerly DB or Sqlite) of users
(and possibly a separate one with groups) with some basic metadata
describing the user:
1. Username
1. Real Name / Nickname
2. Encrypted Password (encrypted with a choice of algorithms, AES,
Blowfish, etc..)
4. Groups user belongs in (by name)
Any other metadata that should be stored in the authentication database?
The identity management system's API can be quite simple:
BOOL AuthenticateUserA( LPCSTR username, LPCSTR password );
BOOL AuthenticateUserW( LPCWSTR username, LPCWSTR password );
Basically, returning a TRUE if the particular user is valid and FALSE
otherwise. Other APIs to get other metadata can come later?
Any other ideas?
--Justin Haygood
justin.haygood(a)gmail.com
There has been very little activity in 0.3.0, so I am putting out a
last call before feature freeze. If no one comes forward, we will
feature freeze during the weekend so we can start bughunting.
I've also bumped trunk to 0.4.0-SVN, and created an 0.3.0 entry in Bugzilla.
WD
--
ReactOS is a hub, follow the spokes and you'll
immediately find absolutely everything you need
to know about Windows. ReactOS is not just
software, it's people.
kjk_hyperion
I'm interested in translate any article about ReactOs or the ReacOs to
Portuguese.
What article is interesting to Brazilian comunity?
How can I help to translate the ReactOs to Portuguese?
Thanks,
Sandro.
Looks like r22100 breaks the build (at least for me):
[CC] ntoskrnl\cm\ntfunc.c
ntoskrnl\cm\ntfunc.c: In function `NtCreateKey':
ntoskrnl\cm\ntfunc.c:474: warning: implicit declaration of function
`ObpReleaseCapturedName'
make: *** [obj-i386\ntoskrnl\cm\ntfunc.o] Error 1
The ReactOS website frontpage content has remained the same for
several months and it has lead to some confused visitors who has asked
a lot questions in the forums.
We need a high quality text for the frontpage which need to be
reviewed by native speekers. The current text is good, but not
brilliant. There is for example no single line where it states that
ReactOS not using the linux kernel. Or the following sentense is not
optimal: "Finally, a FOSS operating system for everyone!". End-User
does not need to know what "FOSS" is nor any other technical slang.
This are just a few example which shows some downsides of the current
frontpage content.
I am talking about the following page:
http://www.reactos.org/xhtml/en/index.html
... to be exactly, the main part, starting with "ReactOS Project" and
ending with the "W3C" icons.
Please take some time and review the text and post your suggestions
here (ReactOS Mailing List).
The text does not have to have the same length or same
structure/layout. It would be great to have a longer text splitted up
into several sub-topics suitable for a website frontpage.
Visit other website's and compare the content.
To sum up, we need a lot of volunteers (with good english language and
grammar knowledge) who want to help ito improve the ReactOS website.
Even if you are not a native speaker and/or not good in english, you
are welcome to post your suggestions/ideas/etc.
I hope this email will get a lot of response and I am looking forward
to an efficient conversation.
Klemens Friedl
ReactOS Dev & Website Admin
http://www.reactos.org
amunger(a)svn.reactos.org schrieb:
> Author: amunger
> Date: Fri May 26 19:14:13 2006
> New Revision: 22052
>
> URL: http://svn.reactos.ru/svn/reactos?rev=22052&view=rev
> Log:
> Bump trunk to 0.4.0, no turning back now.
Wouldn't it be smater set it to 0.3.1 ? I mean the next version is 0.4.0
actually very unlikely.
Maarten Bosma
Hi,
It is based on Wine implementation. It has other hax with it mostly tests.
There is a hax for NtGdiGetCharABCWidths to allow it to pass one of the
"gdi32_crosstest font" tests.
Over all, it is truly Ugly and going to change. WYSIWUG ATM.
Thanks,
James
I was just looking at the graphics system at many open source
operating systems. Seems to be most of them rely on other engines to
take care of their GUI system. I was thinking what about creating a
GUI or Window Server that draws MPEG2 or MPEG4 compliant graphics.
This implention is wrong please revert it
it shall and must be implement in win32k not direcly to gdi32
NtGdiGetCharWidth
----- Original Message -----
From: <jimtabor(a)svn.reactos.org>
To: <ros-svn(a)reactos.org>
Sent: den 21 January 2006 01:52
Subject: [ros-svn] [jimtabor] 20958: Port Wine GetCharWidth32A.
> Port Wine GetCharWidth32A.
>
>
> Updated files:
> trunk/reactos/lib/gdi32/objects/font.c
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-svn
I think few of the devs ever read the Design forum (???)
There are a some nice GUI designs, mostly done with a drawing program.
So I thought it would be great to make those designs available inside
ROS. Some of them (I think kokodin made a good and quite good
programmable design) could be done by changing the user32 code, but it's
not a good idea to make theming by changing user32 code. So I had the
following idea: all code really needed to draw the GUI elements could be
exported into an external dll (gui.dll or something like that) so some
basic theming would be pretty easy and still fast. We would only need a
kind of GUI API that would allow changing most things, but would not be
too complex.
What do you think of this?
If you think it's a good idea, I would try to outsource the gui code out
of user32 and try to develop a basic and a secondary (based on kokodin's
design) dll.
greatlrd(a)svn.reactos.org wrote:
> Author: greatlrd
> Date: Fri May 26 23:23:34 2006
> New Revision: 22062
>
> URL: http://svn.reactos.ru/svn/reactos?rev=22062&view=rev
> Log:
> replace djgpp hell bugs fcvtbuf with project http://www.jbox.dk/sanos/source/lib/fcvt.c.html with small modification's to match ReactOS arch. Floating point to string conversion routines Copyright (C) 2002 Michael Ringgaard. All rights reserved.
>
> Make wine test for fcvt shut up we are failing 64 of wine test in msvrt printf, but we pass all fcvt test. before we did fail 75 test in wine test of msvrt printf test. Before we did fail almost all test case for fcvt in wine test
>
I've been actually importing a LOT of the SanOS code into rtl back when
I was working on fixing many of the broken inlined GAS routines, and his
code REALLY kicks ass. I strongly recommend using the SanOS CRT
functions when possible.
Best regards,
Alex Ionescu
Murphy, Ged (Bolton) wrote:
>
>
> amunger(a)svn.reactos.org wrote:
> >
> > URL: http://svn.reactos.ru/svn/reactos?rev=22052&view=rev
> > Log:
> > Bump trunk to 0.4.0, no turning back now.
> >
>
> Ehh???
Oh I see, nevermind.
I read it wrong initially.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
amunger(a)svn.reactos.org wrote:
>
> URL: http://svn.reactos.ru/svn/reactos?rev=22052&view=rev
> Log:
> Bump trunk to 0.4.0, no turning back now.
>
Ehh???
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Hi!
ReactOS.Bugzilla(a)reactos.org wrote:
> http://www.reactos.org/bugzilla/show_bug.cgi?id=1172
>
>
> hpoussin(a)reactos.org changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC|hpoussin(a)reactos.org |
> Summary|Network driver will not |VIA Rhine II net driver
> |install. |doesn't detect miniport
>
>
>
>
> ------- Comment #9 from hpoussin(a)reactos.org 2006-05-23 22:18 CET -------
> Changing title, as it is no more a installation problem.
> (btw, the wrong name in ncpa control panel is due to a missing entry in
> [Strings] section)
>
>
Funny, it once worked.
[MANUF]
%PCI\VEN_1106&VT3065.DeviceDesc% = VT3065_ndi,PCI\VEN_1106&DEV_3065
;%PCI\VEN_1106&VT3065.DeviceDesc% = VT3065_ndi,PCI\VEN_1106&DEV_3065&SUBSYS_734C1462
<snip >
Manuf = "VIA Technologies, Inc."
VT3106S.DeviceDesc = "VIA Rhine III Management Adapter"
VT3106J.DeviceDesc = "VIA Rhine III Fast Ethernet Adapter"
VT3065.DeviceDesc = "VIA Rhine II Fast Ethernet Adapter"
VT3043.DeviceDesc = "VIA VT86C100A Rhine Fast Ethernet Adapter"
FET.Service.DispName = "VIA Rhine Family Fast Ethernet Adapter Driver Service"
Not that I am aware of... but I could be wrong too because I never
hang around the bugzilla site lol
>> Can someone actually fix the radio buttons? It's getting annoying to
>> see it with no outlining on it, not sure why whoever wrote the code
>> for it left the outline of it out...
>>
>Hi,
>Is there a bug report for it already? I think we never finished it.
>Thanks,
>James
--
-David W. Eckert
Hey all,
Well, since time has been very restricted for me I have not done as
much code auditing as I would have liked.
However, I did add a page to the wiki about writing secure code
(Secure_Programming). I hope people find it useful and will add
ReactOS specific items to it.
I decided to use another page rather than add to
Programming_Guidelines as it could grow quite big on its own. It is
not linked from any other pages as I didn't want to tread on anyones
toes or get in the way of someone else.
Hope this helps people write a bit more securely :)
Martin
Can someone actually fix the radio buttons? It's getting annoying to
see it with no outlining on it, not sure why whoever wrote the code
for it left the outline of it out...
--
-David W. Eckert
WaxDragon wrote:
> I have the UIC's approval.
I never approved it to be non-user-selectable in the first place.
IRC log (18 Apr 2006):
22:27 -!- Irssi: Starting query in FreeNode with Christoph_vW
22:27 <Christoph_vW> http://www.ApiViewer.de/downloads/test.png
22:29 <mf> nice
22:29 <Christoph_vW> ok
22:30 <Christoph_vW> that is what I wanted to hear :-)
22:31 <mf> yeah i saw someone on the forum do that too
22:31 <Christoph_vW> I thought we should differ from windows in some way
22:31 <mf> now make a corner-to-corner gradient :)
22:31 <mf> a-la openstep
22:34 <mf> left-top to right-bottom
22:34 <Christoph_vW> not yet
22:49 <mf> it IS optional though, right?
22:49 <Christoph_vW> no...
22:49 <Christoph_vW> I replaced the old gradient
22:49 <mf> ...
22:50 <mf> please revert it until you can turn it on/off
22:50 <mf> or else there'll be a lot of complaints from devs and useres
22:50 <mf> users*
23:02 <Christoph_vW> http://www.ApiViewer.de/downloads/test2.png
23:05 <mf> slightly better ;)
23:05 <Christoph_vW> good
Not that anyone ever listens to what I have to say, though.
David Hinz wrote:
> What about a vote on this "problem"?
There is no vote necessary. The only thing that needs to be done is an
interface so people can turn it on/off to their own tastes.
Last week I have tested ReactOS build 21942.
And I wondern about the ugly changes:
- wrong gradient on the top of the windows.
- the symbols which say, which icon on the desktop is a link and which not,
is now on the right bottom, instead of the left bottom
But some icon-designer have the icons so designed, that its ok, if there
is something on the left bottom of the icon lost. But the icons are
not so designed, that it is lost on any other place.
It seems, there are now some ReactOS-developer, who don't like Windows.
I would prefering it, if ReactOS looks most as possible like Windows.
And if anybody wants to have its own look, that then existing options to
change the look of ReactOS.
Greatings
theuserbl
There is a hotkey meta bug please mark that bug as "depending on" the
last two you file.
Brandon
ReactOS.Bugzilla(a)reactos.org wrote
>http://www.reactos.org/bugzilla/show_bug.cgi?id=1514
>
> Summary: Edit control: Ctrl+Backspace/Delete doesn't work
> (correctly)
> Product: ReactOS
> Version: TRUNK
> Platform: VMWare 5
> OS/Version: ReactOS
> Status: NEW
> Severity: minor
> Priority: P3
> Component: Win32
> AssignedTo: ros-bugs(a)reactos.org
> ReportedBy: trondsg(a)gmail.com
> QAContact: ros-bugs(a)reactos.org
>
>
>In all edit controls, like the one you get when go to Start -> Run, Ctrl +
>Backspace does not work at all. It is supposed to delete the previous
>word.Ctrl+Delete deletes the rest of the contents (after the caret) instead of
>deleting the next word.
>
>
>
>
Exactly one months ago, I annouced the beta test for the ReactOS
Compatibility Database:
http://www.reactos.org/xhtml/en/news_page_18.htmlhttp://www.reactos.org/support/
We have currently 71 categories and 99 applications/drivers in the database.
I got some feedback from users. This lead to several interface
improvements. For example, some user commented that the submit process
is to confusing. It was confusing, well let say the submit pages were
too overloaded.
I tried with several updates to improve th interface and especially
the submit pages step by step.
As of today, the latest update bring a complete redesigned submit
process, a wizard like look&feel which looks and interact similar to
Wizard '97 / Vista (from the Win32 world) and has a lot of usability
improvements.
It has many user interacting feedback included so that the user will
see instantly if he e.g. inputted an invalid value. The submit pages
are using ajax, dhtml (=> javascript).
I want to invite you to visit the ReactOS Compatibility Database:
http://www.reactos.org/support/
Feedback is welcome, please use the mailing list and/or the website
sub-forum (http://www.reactos.org/forum/viewforum.php?f=18) to write
replies.
Klemens Friedl
ReactOS Dev & Website Admin
http://www.reactos.org/support/
> Nobody (ok, many didn't) objected to attacking Iraq at first either.
> Nor did they to the beginnings of the Holocaust.
>
> Best regards,
> Alex Ionescu
Whatever. I've had it having to justify my every breath in here. I'm
stepping down as UIC and icon designer.
Fireball, you can close my SVN account. It seems some people are
thinking we didn't lose enough developers from the Hartmut drama. I am
officially fed up with everyone's fucking around and bitching. The
person I expected it from the least is GreatLord.
> Why I wanted a UI coordinator, is because HE should solve SUCH
> questions [in a more or less diplomatic way :) ].
How am I supposed to impartially solve an issue I am personally
involved in? If people aren't willing to accept my condition of
"discuss with me first", then I don't know what I should do.
(sorry for initially having accidentally sent this mail to ros-general
instead of ros-dev)
> The ReactOS logo is an ugly design.
Until you manage to get that wonky off-balance thing you prefer to be
accepted as the official logo, whether it is ugly or not is not
relevant. There is a procedure for changing established things. Your
method of just going ahead and changing things without asking is not
only rude but wrong. If you want to change things, you will have to go
through me first. If you have a problem with me, you have a problem
with changing things. So I suggest you consider your options.
> Also, it's far too complex to be used as a start button image and looks out
of place.
It's a bloody orb with wisps (rings) around it. Complex my eye.
> The official Windows logo isn't used on the start button. A neater version
is used in the same way.
A "neater version". You mean the shadow? I have employed a similar way
to make the icon clear at 16x16:
http://img55.imageshack.us/img55/4972/startthingie3yn.png
As you can see, both with Windows and with ReactOS, it's practically
the same thing. I'm beginning to get the idea you are making arguments
up for the sake of having arguments in your offence.
> This logo is the original ReactOS start menu logo and should be kept IMO.
It's as much a placeholder as the "original" Everaldo icons were.
mf
> I know it is alot people reactos user and
> devloper dislike the new logo.
> if u do not revert it, (restore to the old one)
> I will do it this weekend.
GreatLord, there *IS* no new logo. The icon I re-committed has been in
ReactOS since r14357. That's March 27th 2005. Nobody objected back
then, yet now there's a fuss? Please mind your own business if you
don't know exactly what's going on. Thanks.
mf
mf wrote:
> Until you manage to get that wonky off-balance thing you prefer to be
> accepted as the official logo, whether it is ugly or not is not
> relevant. There is a procedure for changing established things. Your
> method of just going ahead and changing things without asking is not
> only rude but wrong.
I highly disagree with the fact that everyone must go through you. If we
initiated a kernel coordinator, do you also suggest that all kernel work
must be approved by them too?
Taking into account the smarmy comment which went along with the change,
it was my impression you changed it back just to try and annoy me.
Many of the developers I have spoken to agree that the original icon is
better. Nobody seems to want to say anything to you for fear of
upsetting you though. Great!
> If you want to change things, you will have to go
> through me first. If you have a problem with me, you have a problem
> with changing things. So I suggest you consider your options.
>
I have just considered my options. I choose to stop work on the UI as of
now.
The fact that you've tried to alienate me many times, and now in public
seals the fact that we can't work together.
I was the only person interested in working on the UI, and you managed
to take the fun out of it for me, are you sure you are the right man for
the job? I tend to think not.
Ged.
Hi
The new logo se does not look like reactos any longer
it is to dark and pixel, the balas and constrast in the new
logo is bad, it does not match at all, and it look not prof
have made it. more like a childer. So please revert
the new logo and keep, the old one.
If u look in ros it does not match the constrast or
any think. A logo should not be pixel or constat
does not match. That is exacly in the new logo
u have done MF.
I know it is alot people reactos user and
devloper dislike the new logo.
if u do not revert it, (restore to the old one)
I will do it this weekend.
Magnus Olsen (GreatLord)
ReactOS Devloper
----- Original Message -----
From: "mf" <mf(a)mufunyo.net>
To: <ros-general(a)reactos.org>
Sent: Thursday, May 18, 2006 11:53 PM
Subject: [ros-general] RE: [ros-diffs] [mflyer] 21918: Sorry Ged,but that's
not the Rea ctOS logo.
> > The ReactOS logo is an ugly design.
> Until you manage to get that wonky off-balance thing you prefer to be
> accepted as the official logo, whether it is ugly or not is not
> relevant. There is a procedure for changing established things. Your
> method of just going ahead and changing things without asking is not
> only rude but wrong. If you want to change things, you will have to go
> through me first. If you have a problem with me, you have a problem
> with changing things. So I suggest you consider your options.
>
> > Also, it's far too complex to be used as a start button image and looks
out
> of place.
> It's a bloody orb with wisps (rings) around it. Complex my eye.
>
> > The official Windows logo isn't used on the start button. A neater
version
> is used in the same way.
>
> A "neater version". You mean the shadow? I have employed a similar way
> to make the icon clear at 16x16:
>
> http://img55.imageshack.us/img55/4972/startthingie3yn.png
>
> As you can see, both with Windows and with ReactOS, it's practically
> the same thing. I'm beginning to get the idea you are making arguments
> up for the sake of having arguments in your offence.
>
> > This logo is the original ReactOS start menu logo and should be kept
IMO.
> It's as much a placeholder as the "original" Everaldo icons were.
>
> mf
>
> _______________________________________________
> Ros-general mailing list
> Ros-general(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-general
Aleksey and I thought it would be a good idea to end rumours and write
up an official stance on the topic, so here is a paste from the website,
for those of you that don't read it:
--
The official letter written by project coordinators of these projects
by fireball on 2006-05-18
ReactOS and TinyKRNL projects' official relationship
Prepared by Aleksey Bragin and Alex Ionescu, Project Coordinators.
There is a little information posted officially about TinyKRNL project
and this provides a base for gossip to appear. This short article is
intended to clear up official relations between these two projects.
TinyKRNL is an educational and documentation project which creates
plug-in replacements for various modules of Windows 2003 SP 1
(ultimately replacing the kernel too) and a series of papers ultimately
combined into a book. The methods used for development of TinyKRNL’s
modules source code involve all possible methods of achieving the end
result of having a 100% compatible (or even identical) result. Reverse
engineering is one of them (mainly so-called ‘dirty’ way, for further
reference see Wikipedia’s article about clean room reverse engineering
vs. dirty room reversing).
Unfortunately, due to copyright laws and other law-related stuff,
ReactOS (which aims at commercial usage too) can not directly utilize
methods of development like dirty reverse engineering, and thus ReactOS
can not share all code with the TinyKRNL project like we are sharing
code with WINE.
However, there are some very useful exceptions:
* Firstly, all interfaces are shared. This gives ReactOS project an
unbeatable level of compatibility and legal freedom too (interfaces can
not be copyrighted).
* Secondly, the great thing is that TinyKRNL will provide the most
complete documentation of the most recent and technically advanced
version of a released NT-famility operating system – Windows 2003 SP1.
ReactOS developers can use this documentation for reference when
creating a clean implementation of functions or improving already
developed code.
* Thirdly, any code in TinyKRNL which respects the ReactOS policies
regarding development can directly be added into ReactOS, as well as any
build tools or 3rd-party files.
For more detailed information regarding TinyKRNL project, please look at
http://www.tinykrnl.org. We also encourage you to signup on the TinyKRNL
. We also encourage you to signup on the TinyKRNL development Mailing
List by sending a blank email to devel-subscribe(a)tinykrnl.org as well as
joining the #tinykrnl channel on the same IRC server as #reactos; many
of the ReactOS developers and users are usually present and discuss
interesting and challenging kernel issues as well as general off-topic chat.
--
mflyer(a)svn.reactos.org wrote:
> Sorry Ged, but that's not the ReactOS logo.
The ReactOS logo is an ugly design.
Also, it's far too complex to be used as a start button image and looks out
of place.
The official Windows logo isn't used on the start button. A neater version
is used in the same way.
This logo is the original ReactOS start menu logo and should be kept IMO.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Can we agree on the following goals for 0.3.1 ?
- NDK
- Cache Manager Rewrite
- VMware Tools
- Ext2
It would mean that we would release 0.3.1 very closely after 0.3.0.
Maarten Bosma
Steven Edwards wrote:
> On 5/11/06, Murphy, Ged (Bolton) <MurphyG(a)cmpbatteries.co.uk> wrote:
> > The Wine syncs aren't quite as simple as Gé made them look.
> I think we took
> > them for granted back when Gé was doing them.
> > IIRC, comctl32 still needs doing. Last time it introduced
> regressions and
> > was reverted.
>
> I have offered to sync up a bunch of changes for the 0.3 cycle. I'm
> going to start doing this Friday evening for the dlls that are a 100%
> drop-in. There are a few other things that could be updated as well in
> advapi32, kernel32, etc as well as new regression tests. I expect its
> going to take me a while to do it all and make sure there is no
> regression.
Gé has a great awk script which automates a vast majority of the process,
including the laborious task of generating the logs/credits.
If he isn't around today, I can forward a copy on to you later.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Alex committed the NDK today, so I went ahead and branched 0.3.0 at
the previous revision. Aleskey and I decided that the NDK and CC
patches can go in trunk whenever they are ready, for inclusion into
0.3.1. 0.3.0 is still in need of bugfixing and regression testing.
Therefore, we are going to leave the 0.3.0 branch open to
development for a bit before we release RC1. Please discuss any large
changes on the list before commiting to the branch. I don't care of
the branch stays open for a month, as long as it's a good release in
the end.
Thanks for all your hard work,
WD
--
ReactOS is a hub, follow the spokes and you'll
immediately find absolutely everything you need
to know about Windows. ReactOS is not just
software, it's people.
kjk_hyperion
Aleksey Bragin wrote:
> If some of you wants to merge components which are left - please go
> ahead. Wine vendor import was done (some 10, some 12), so it's just
> the merge which is left. And main problem is merging 0.9.5->0.9.10,
> while 0.9.10-0.9.12 is quite easy due to not so big amount of changes.
The Wine syncs aren't quite as simple as Gé made them look. I think we took
them for granted back when Gé was doing them.
IIRC, comctl32 still needs doing. Last time it introduced regressions and
was reverted.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
David Hinz wrote:
Hey guys,
when I just translated format, I stunbled over one
thing:
What if somebody changed the content of a string after
I translated it?
After some minutes, I had a easy solution for that
problem:
The En.rc gets a little line in it's head-comment with
a revision
number. Each time somebody changes or adds a string in
the En.rc, he
sets the revision number +1 and so all translators
have an easy to
control indicator, if they need to translate something
or not.
But I think one thing should be clear, if there just
has been corrected
a spelling mistake and not something important, the
revision number
won't be touched.
Now some example headers:
in the EN.rc:
/*
* Moved all hardcoded strings to En.rc.
* By Magnus Olsen 2005
*
* Revision: 1
*/
in my De.rc:
/*
* Moved all hardcoded strings to En.rc.
* By Magnus Olsen 2005
* First German Translation by David Hinz 20051010
*
* Translated Revision 1 of En.rc
*/
This is just an idea, but I think this could save a
lot of work on
bigger applications than format...
Greets,
David Hinz
---------------------------------------
I agree, in fact i am working in a program to manage
translation in reactos, i am using Delphi 2.0 but as i
am not much skilled (long time since i used pascal)
and my time is on the limit it is going slowly but it
should work as follow:
Part 1:
- You select your language
- You select the working directory of reactos source.
- The program scans all files for en.rc files and list
their directories (as their names are all the same).
- With each file the program check a text file with a
list of en.rc files, and if it is not there it adds
it, and it is shown in the GUI as highlighted (pending
translation).
- If the file is found in the list, it check if
translating language file is current--> if it is not
current then the file is highlighted (pending
translation).
- If the file is found in the list, and found a
translation file current--> the file is listed but not
highlighted.
- It does with all rc files till no more rc files in
the directory.
Part 2:
- On clicking in a file in the listbox (highlighted or
not) it will be shown in an Richtext edit panel and
besides another panel with the material already
translated (if there is any language related file
already done), if not, the english text will be shown
with the "probable translatable" areas highligthed
(those between "").
-A save button, that will save the changes in the
second panel automatically into the right directory in
a language working copy.
What do you think?
______________________________________________
Renovamos el Correo Yahoo!
Nuevos servicios, más seguridad
http://correo.yahoo.es
ReactOS.Bugzilla(a)reactos.org wrote:
>http://www.reactos.org/bugzilla/show_bug.cgi?id=1460
>
>
>greatlord(a)reactos.com changed:
>
> What |Removed |Added
>----------------------------------------------------------------------------
> Status|NEW |RESOLVED
> Resolution| |WONTFIX
>
>
>
>
>------- Comment #2 from greatlord(a)reactos.com 2006-05-08 21:13 CET -------
>you can not install any os on exstions partions
>what I know, a OS need be on primary partions
>
>This bug report is invaild in my eyes
>
>
Umm... this is not strictly true. You *can* install an OS on an extended
partition. You just can't put the boot strap on an extended partition.
Note that this is not a discussion about how *wise* such a thing would be...
greatlrd(a)svn.reactos.org wrote:
> if u update En.rc please update all other langues files, use
> the english text if no translatesion is not availbal, other
> wise it will bsd in windows or in reactos and we get diffent
> functions on each langues. DO NOT DO THIS MISTAKE
If it's just 1 or 2 lines, it generally not a big deal to alter all the
files. However when the changes are large, and considering programmers are
generally lazy ;) it can be a real pain to change all the resources.
This problem is only going to get worse as more languages are added.
I think it could be worthwhile setting up official translation teams who are
contacted when a resource file changes. It'd be relatively easy to script.
It would benefit both ReactOS, and people who want to get involved but
aren't programmers.
Our translation teams are a bit of a grey area at the moment. Our website is
much better organised in this department than our actual operating system.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
> From: greatlrd(a)svn.reactos.org
>
> Log:
> if u update En.rc please update all other langues files, use
> the english text if no translatesion is not availbal, other
> wise it will bsd in windows or in reactos and we get diffent
> functions on each langues. DO NOT DO THIS MISTAKE
The resource loader will load the English text if the text is not available in the selected language (at least that's what is supposed to happen, if it doesn't there's a bug in the resource loader).
GvG
> > Log:
> > if u update En.rc please update all other langues files, use
> > the english text if no translatesion is not availbal, other
> > wise it will bsd in windows or in reactos and we get diffent
> > functions on each langues. DO NOT DO THIS MISTAKE
>
> The resource loader will load the English text if the text is not available in the
> selected language (at least that's what is supposed to happen, if it doesn't
> there's a bug in the resource loader).
Correct with one small exception: String table resources are loaded in chunks
of 16 strings, so strings should be updates with great care:
If one inserts new strings into the string table only in English, the
resource IDs of
this new strings should be aligned to a boundary of 16.
Regards,
Martin
If the ImageBase for a given executable is in the kernel range (above
0x7FFE1000 or whatever), from reading the code it seems like no validation
will stop it from going above that address. I have no way to try it out
because I don't have reactos installed.
Interestingly, in Windows XP SP2, the only illegal ImageBase values are:
7C800000 - Causes a dialog box to appear during the ntdll process
initialization APC saying that the program can't run because kernel32.dll
was relocated.
7C900000 - Causes PspMapSystemDll to fail. As a result, the process is
never created and NtCreateProcessEx returns an error.
These errors occur even when /fixed:no is used. Every other address is
allowed by Windows as long as /fixed:no is specified, even above the
user-kernel barrier.
Personally I think reactos should allow user mode programs to shove ntdll
and kernel32 out of the way, but that's just me =)
Finally,
04477 MmUnlockAddressSpace(AddressSpace);
04478 return(STATUS_UNSUCCESSFUL);
and the one below it should return STATUS_CONFLICTING_ADDRESSES, determined
by attempting to load an image based at a kernel address without a
relocation section.
MmCreatePeb has an invalid assertion:
ASSERT(Peb == (PVOID)0x7FFDF000);
If the process's .exe already is at that address, the PEB will be at the
wrong address.
There's also a nice way for a user-mode program to bugcheck the kernel or
leak a small amount of information in MmCreatePeb:
ImageConfigData = RtlImageDirectoryEntryToData(Peb->ImageBaseAddress,
To crash the kernel, put a bogus load config directory entry pointer in your
.exe.
To read an arbitrary dword or two, set up the load config pointer such that
it aims at your desired memory address, then read the PEB's OSCSDVersion and
ImageProcessAffinityMask values once your process starts.
Melissa
IsPowerOf2 in the kernel is badly inefficient. It should be this:
__inline BOOLEAN IsPowerOf2(IN ULONG Number)
{
if (Number == 0)
return FALSE;
return (Number & (Number - 1)) == 0;
}
Not that this function is called frequently, shrug.
Melissa
okay, so these are the options:
1) forget redhat and forget them ever being helpful and supporting
strategically important free software projects, and go back to using
dcethreads posix draft 4 "emulation".
2) forget redhat and forget them ever being helpful and supporting
strategically important free software projects, and put the cancellation
"wrapper" side back into the dcethreads library - just keep the same
posix "final draft" API.
lord only knows what would happen on pthreads-win32 when compiling
freedce with mingw32, with the "wrapper" stuff back in, but i'd be
fascinated to find out.
3) think of ways to persuade the developers of glibc to enter into
reasonable conversations and dialog to help support a strategically
important free software project. how does any other project manage
this (and what in hell's name prompted ulrich to be so dismissive?)
On Fri, Apr 21, 2006 at 05:26:44PM +0200, thomas.schuetzkowski(a)web.de wrote:
> Hi Luke,
>
>
> > To make this work with libc we need to "un-cancel" a thread.
> > ...
> > Of course, using this in a third-party application is problematic as it
> > depends on internal glibc structures.
> >
> > I know the chances of such an API being added to glibc are about nil, but
> > I thought I'd mention this anyway! :-)
>
> We thought about adding a detection of the glibc version to autoconf stuff and choose the right version of the function. (see Loic's patch)
> Then of course someone has to maintain this for every new version of glibc. :-(
>
> This idea was skipped, because no one had the time to do this.
>
> regards,
> Thomas
> _______________________________________________________________
> SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
> kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
>
--
--
lkcl.net - mad free software computer person, visionary and poet.
--
Hi!
Running at revision 21793, is this bug known to anyone? Doesn't happen often.
Thanks,
James
(dll/ntdll/ldr/utils.c:1193) LdrGetExportByName(): failed to find mxdMessage
(dll/ntdll/ldr/utils.c:2018) Failed to create or open dll section of 'msacm.drv' (Status c0000135)
(dll/ntdll/ldr/utils.c:2018) Failed to create or open dll section of 'midimap.drv' (Status c0000135)
(./subsystems/win32/win32k/objects/gdiobj.c:600) Attempted to free global gdi handle 0xe0500c1,
caller needs to get ownership first!!!
(./subsystems/win32/win32k/objects/gdiobj.c:600) Attempted to free global gdi handle 0x3e050301,
caller needs to get ownership first!!!
(lib/rtl/exception.c:75) RtlRaiseStatus(Status 0xc0000005)
(./subsystems/win32/win32k/ntuser/message.c:1109) Failed to copy message to kernel: invalid usermode
buffer
(dll/win32/shell32/dialogs.c:420) LogoffWindowsDialog is UNIMPLEMENTED
(./subsystems/win32/win32k/ntuser/window.c:648) thread cleanup: while destroy wnds, wnd=0x9e1bedac
(./subsystems/win32/win32k/ntuser/window.c:648) thread cleanup: while destroy wnds, wnd=0x9e1bee9c
(./subsystems/win32/win32k/ntuser/window.c:648) thread cleanup: while destroy wnds, wnd=0x9e1bef94
(./subsystems/win32/win32k/ntuser/window.c:648) thread cleanup: while destroy wnds, wnd=0x9e1bf08c
(./subsystems/win32/win32k/ntuser/window.c:648) thread cleanup: while destroy wnds, wnd=0x9e1bf914
(./subsystems/win32/win32k/ntuser/window.c:648) thread cleanup: while destroy wnds, wnd=0x9e1bfb0c
(./subsystems/win32/win32k/ntuser/window.c:648) thread cleanup: while destroy wnds, wnd=0x9e1c00ec
(./subsystems/win32/win32k/objects/gdiobj.c:805) Attempted to lock object 0x80063 that is deleted!
KeBugCheckWithTf at ntoskrnl/ke/i386/exp.c:1241
A problem has been detected and ReactOS has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
Technical information:
*** STOP: 0x0000001E (0xc0000005,0x80067d3a,0x00000000,0xfffffffc)
*** ntoskrnl.exe - Address 0x80067d3a base at 0x80000000, DateStamp 0x0
Page Fault Exception: 14(2)
Processor: 0 CS:EIP 8:80067d3a <ntoskrnl.exe:67d3a (ntoskrnl/ex/i386/fastinterlck_asm.S:580
(InterlockedDecrement))>
cr2 fffffffc cr3 3cb2e000 Proc: 813df968 Pid: 70 <csrss.exe> Thrd: 817b0158 Tid: a4
DS 23 ES 23 FS 30 GS 0
EAX: ffffffff EBX: 00000001 ECX: fffffffc
EDX: 00000001 EBP: 9ed9ebb4 ESI: 8d6d8328 ESP: 9ed9eb3c
EDI: 00000003 EFLAGS: 00010297 kESP 9ed9eb3c kernel stack base 9ed99000
Frames:
<win32k.sys:3dd22 (./subsystems/win32/win32k/eng/xlate.c:280 (IntEngCreateXlate))>
<win32k.sys:71df3 (./subsystems/win32/win32k/objects/brush.c:64 (IntGdiCreateBrushXlate))>
<win32k.sys:8bec8 (./subsystems/win32/win32k/objects/dc.c:2126 (NtGdiSelectObject))>
<win32k.sys:8c1a1 (./subsystems/win32/win32k/objects/dc.c:2327 (DC_InitDC))>
<win32k.sys:8ca37 (./subsystems/win32/win32k/objects/dc.c:923 (IntGdiCreateDC))>
<win32k.sys:4ff56 (./subsystems/win32/win32k/ntuser/windc.c:121 (DceAllocDCE))>
<win32k.sys:54678 (./subsystems/win32/win32k/ntuser/windc.c:441 (UserGetDCEx))>
<win32k.sys:6498f (./subsystems/win32/win32k/ntuser/painting.c:770 (NtUserBeginPaint))>
<ntoskrnl.exe:652b7 (ntoskrnl/ke/i386/trap.s:306 (KiFastCallEntry))>
<win32csr.dll:5779 (subsystems/win32/csrss/win32csr/desktopbg.c:57 (DtbgWindowProc))>
Hi!
--- trunk/reactos/base/applications/notepad/notepad.h (original)
+++ trunk/reactos/base/applications/notepad/notepad.h Wed May 3 20:17:12 2006
@@ -5,7 +5,9 @@
#include <stdio.h>
#include <windows.h>
#include <commdlg.h>
+#include <commctrl.h>
#include <tchar.h>
+#include <Richedit.h>
#include "main.h"
#include "dialog.h"
[PCH] obj-i386/base/applications/notepad/notepad.h.gch
base/applications/notepad/notepad.h:10:22: Richedit.h: No such file or directory
make[1]: *** [obj-i386/base/applications/notepad/notepad.h.gch] Error 1
make[1]: Leaving directory `/home/ros/reactos'
This patch breaks compile on a linux box! Please fix and remember!, This is a
multi compiled platform operating system! So DoN't uSe CaSe! 8^D
Thanks,
James
guys, hi,
am on the mailing list (subscribed) but am not receiving posts: please
cc me if this would be an issue.
for win32, i am using pthreads-win32: will reactos be able to support
the trick that luke howard is referring to?
l.
----- Forwarded message from Luke Howard <lukeh(a)padl.com> -----
Envelope-to: lkcl@localhost
Delivery-date: Mon, 24 Apr 2006 12:51:50 +0100
X-Original-To: lkcl(a)lkcl.net
Resent-Date: 24 Apr 2006 10:22:43 -0000
From: Luke Howard <lukeh(a)padl.com>
Organization: PADL Software Pty Ltd
To: freedce-devel(a)lists.sourceforge.net
Subject: NPTL and FreeDCE
Cc: opendce(a)opengroup.org
Reply-To: lukeh(a)padl.com
Versions: dmail (bsd44) 2.6d/makemail 2.10
X-Spam-Status: NO, hits=-5.60 required=5.00
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on au.padl.com
X-Spam-Flag: NO
X-Spam-Level:
Resent-Message-ID: <UQB5HC.A.7PG.ubKTEB@mailman>
Resent-To: opendce(a)opengroup.org
Resent-From: opendce(a)opengroup.org
X-Mailing-List: opendce:archive/latest/626
Resent-Sender: opendce-request(a)opengroup.org
X-hands-com-MailScanner: Found to be clean
X-MailScanner-From: opendce-request(a)opengroup.org
Resent-Date: Mon, 24 Apr 2006 12:51:50 +0100
It may be possible to integrate DCE exception handling and NPTL so that
longjmp() is never explicitly called from a cancellation cleanup handler.
In fact, cleanup handlers need not be used at all.
This approach requires the NPTL r ather than the LinuxThreads, API and
is orthogonal to the previous issue about removing thread cancellation
(that was a runtime issue present with NPTL regardless of which header
one compiles against).
Instead of calling _pthread_cleanup_push_defer(), we can store a
__pthread_unwind_buf_t in the exception context and call __sigsetjmp()
and __pthread_register_cancel_defer(). If __sigsetjmp() returns from a
longjmp(), then we call dce_pthread_test_exit_np() to test whether the
thread was cancelled, and set the current exception to pthread_cancel_e
if necessary. No cleanup handler is necessary.
The trick is that the code that raises an exception needs to call the
internal API __pthread_unwind(), rather than longjmp(). Of course this
ends up calling longjmp() anyway but hopefully does the right thing
with respect to any other cleanup handlers that are registered.
Another idea is to use the _Unwind_XXX API, but this strikes me as a
little ambitious for now and I don't have any desire to interleave
C++ and DCE exceptions.
/*
* For the NPTL API we share a setjmp/longjmp buffer between the
* pthreads cancellation and DCE exception handling APIs.
*
* Note that we never actually call the cancellation function, we
* just change the current exception context directly; this is the
* same as calling dce_ptdexc_raise(&pthread_cancel_e) except that
* __pthread_unwind() is not called.
*/
#define dce_exc_cleanup_push(cu, routine, arg) do \
{ \
__exc_occured = __sigsetjmp((struct __jmp_buf_tag *)(cu)->__cancel_buf.__cancel_jmp_buf, 0); \
if (__exc_occured) \
{ \
void *__status; \
\
if (dce_pthread_test_exit_np(&__status) == PTHREAD_STATUS_EXIT_NP \
&& __status == PTHREAD_CANCELED) \
__exc_ctxt.exc = &pthread_cancel_e; \
} \
else \
{ \
__pthread_register_cancel_defer(&(cu)->__cancel_buf); \
} \
} while (0)
#define dce_exc_cleanup_pop(cu, execute) do \
{ \
__pthread_unregister_cancel_restore(&(cu)->__cancel_buf); \
} while (0)
/* make this a NOOP because we called it above */
#define dce_exc_setjmp(jmpbuf, val)
/* we call __pthread_unwind() directly from dce_ptdexc_raise() */
#undef dce_exc_longjmp
-- Luke
--
----- End forwarded message -----
--
--
lkcl.net - mad free software computer person, visionary and poet.
--
This bug is on our side we can not test oo2 installer current in trunk. lest
last time I try 1-2 Month back.
for Reactos was to unstable to confrim if this bug still exists or not. It
should not exits any longer.
----- Original Message -----
From: <ReactOS.Bugzilla(a)reactos.org>
To: <ros-bugs(a)reactos.org>
Sent: Tuesday, May 02, 2006 5:43 PM
Subject: [ros-bugs] [Bug 1185] OOo2 fails to install with an msi error.
> http://www.reactos.org/bugzilla/show_bug.cgi?id=1185
>
>
>
>
>
> ------- Comment #7 from w3seek(a)reactos.com 2006-05-02 17:43 CET -------
> What's the status on this bug? Has the missing feature been implemented in
> WINE?
>
>
> --
> Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the QA contact for the bug, or are watching the QA contact.
> You are the assignee for the bug, or are watching the assignee.
> _______________________________________________
> Ros-bugs mailing list
> Ros-bugs(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-bugs
Hello Everyone,
I've been lurking on this list for a few years and I'm considering
applying for the Google Summer of Code 2006. I am a Computer Systems
Engineer at Rensselaer Polytechnic Institute, just finishing up my
junior year. My GPA is 3.06, and I have taken a good amount of computer
science courses including Data Structures and Algorithms and Database
Systems. I have programmed in C, C++, C#, VB, Perl, PHP, Java and
Javascript before. I'm also familiar with Sybase and MySQL and HTML
design. I have also done some Win32 programming on my spare time, you
can look at some of my projects at:
http://www.rpi.edu/~desimn <http://www.rpi.edu/%7Edesimn>
I have never done kernel mode programming before and I'm not certain
if I'm quite ready for it yet, so if possible I would like to stay in
the user mode space. The enhance explorer and add "wow factor" sounds
interesting to me. Is there anything else that would involve at least
almost all user mode work? Also I was wondering, approximately how many
hours would you expect me to put forth every week should I be accepted?
Thank You,
Nate DeSimone
Hi all,
I'm new to ROS but I've had a few patches accepted to Wine.
I'm having difficulty with the website and I can't seem to login (even
after enabling multisession) so I can't use bugzilla or the forums.
So anyways, I've got ROS to compile (RosBE is great!)/build/install on
two systems but I'm getting the following problems on one system (Dell
Inspiron 5150 Laptop):
During install it shows a 17592185991168 MB unused space partition after
my 60 GB FAT32 partition. But install still works okay.
During 1st boot I get a bsod, I don't have a COM port (USB only) so I
tried to use the SCREEN output option but it's too fast to read. I've
try to use the FILE option but only 600+ bytes are written to the
debug.log file. I know the cache_manager isn't being flushed because
everytime it crashes the contents of the folders in "Documents &
settings" folder are corrupt (ie: "All Users.Reactos", etc.)
So my question is : How can I disable the cache_manager? Or can I
place sync() commands somewhere in the source for testing. (is there
such a function available?).
The bsod seems to be related to gdi issues during creating the primary
surface. Somewhere the DeviceObject for the screen is NULL and is not
caught till it causes a GPE much later.
I'll give a little info that I've written down.
/ntoskrnl/io/irp.c:570 - GPE
/ntoskrnl/io/irp.c:911
/subsystems/win32/win32k/objects/dc.c:693
/subsystems/win32/win32k/ntuser/winsta.c:348
/subsystems/win32/win32k/ntuser/guicheck.c:57
/subsystems/win32/win32k/objects/dc.c:853
/subsystems/win32/win32k/ntuser/windc.c:121
/subsystems/win32/win32k/ntuser/windc.c:441
/subsystems/win32/win32k/ntuser/windc.c:529
/subsystems/win32/win32k/ntuser/windc.c:101
/ntoskrnl/ke/traps.c:306
/dll/win32/user32/windows/dialog.c:696
Hope this helps.
I was using the lastest SVN at the time (21738 I think).
Thanks.
Peter Quiring
Hi!
There existing two bugs from which I know, which existing not in older
SVN/CVS-Snapshot ROS versions.
Windows Tetris don't show the Highscore correct.
With build 21549 there was still all ok. But with 21639 and all above the
Highscore shows only curios symbols as text.
AbiWord no longer runs.
On build 21323 still all runs correct.
But with 21549 the complete ROS hangs up. It ends with
"A problem has been detected and ReactOS has been shut down to prevent
damage to your computer
APC_INDEX_MISMATCH"
And so on.
Don't know if in the current CVS/SVN-Version the bugs are already fixed. But
they existing for some days/weeks.
Greatings
theuserbl
Ge van Geldorp wrote:
>
> The status of the applet when I worked on it was that the UI
> was complete
> and I was starting to work on transfering the data from the
> dialog to the
> TCP/IP driver (via the DHCP client). That part simply isn't
> implemented yet.
Is there a particular reason you were doing this via the DHCP client and not
just using functions provided by iphlpapi?
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
There are still lots of little bugs in the explorer resources, but they will
be ironed out as we go along.
Ged.
-----Original Message-----
From: theUser BL [mailto:theuserbl@hotmail.com]
Sent: 28 April 2006 13:28
To: ros-dev(a)reactos.org
Subject: [ros-dev] Re: Oh, and then the ROS-Explorer bug with the
Folder-Icons
>What do you mean by "files" ?
>If "files" refer to unknown type,
Yes, that is what I mean.
Thats when I go over "My Computer" in "C:\". Then all directories and
unknown files looks like the same.
>I can confirm they have different icons that folders in r21750.
Oh, thanks for information. Then the bug was fixed.
I will later at home first testing r21747, because I take my snapshots from
http://svn.reactos.ru/iso/
and 21747 is the latest which is there published.
But the snapshot from yesterday have had the still the problem, that the
icons for directories is an empty letter. And thats the same icon like for
unknown files.
Greatings
theuserbl
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
>What do you mean by "files" ?
>If "files" refer to unknown type,
Yes, that is what I mean.
Thats when I go over "My Computer" in "C:\". Then all directories and
unknown files looks like the same.
>I can confirm they have different icons that folders in r21750.
Oh, thanks for information. Then the bug was fixed.
I will later at home first testing r21747, because I take my snapshots from
http://svn.reactos.ru/iso/
and 21747 is the latest which is there published.
But the snapshot from yesterday have had the still the problem, that the
icons for directories is an empty letter. And thats the same icon like for
unknown files.
Greatings
theuserbl
>From Wine-devel and jwhite
Jeremy White
to wine-devel, wineconf
More options 11:33 am (53 minutes ago)
Hi folks,
I am pleased to announce that Rob Shearman has arranged
for us to have Wineconf in his home town, Reading, in the UK.
It will be held at the University of Reading:
http://www.fmd.rdg.ac.uk/res/CommercialAccommodation.asp
It will be on the weekend of September 16 and 17.
We have a wrinkle we need your help on. That is, as
we make our deposit (which we need to do quickly),
we have to tell them how many rooms we want to reserve.
The have a good deal on rooms (40 pounds/night, which
is quite good, afaict).
The trick is that we have to pay for all the rooms
we reserve ahead of time; we can't ask for 50 rooms
and then only use 43. We have to pay for all 50.
We may be able to ask for 50 rooms, and then get another
3 or 4, although that's not guaranteed.
So, *if you want a room at Wineconf*, please fill in this form ASAP:
http://www.winehq.org/site/wineconf/survey06
If you're not sure you'll make it, but think you might,
we have a choice for that too <grin>.
Act now or you'll be sleeping in Swindon...
Cheers,
Jeremy
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Are you not able to use a VM?
It' makes life much easier, and IMO, it's essential for development work.
ROS does have one or two problems with real hardware at the moment, and it's
hard to pinpoint without a debugger.
If you can get a photo of the BSOD, it would help.
-----Original Message-----
From: Peter Quiring [mailto:pquiring@gmail.com]
Sent: 26 April 2006 17:23
To: ros-dev(a)reactos.org
Subject: [ros-dev] need help debugging
Hi all,
I'm new to ROS but I've had a few patches accepted to Wine.
I'm having difficulty with the website and I can't seem to login (even
after enabling multisession) so I can't use bugzilla or the forums.
So anyways, I've got ROS to compile (RosBE is great!)/build/install on
two systems but I'm getting the following problems on one system (Dell
Inspiron 5150 Laptop):
During install it shows a 17592185991168 MB unused space partition after
my 60 GB FAT32 partition. But install still works okay.
During 1st boot I get a bsod, I don't have a COM port (USB only) so I
tried to use the SCREEN output option but it's too fast to read. I've
try to use the FILE option but only 600+ bytes are written to the
debug.log file. I know the cache_manager isn't being flushed because
everytime it crashes the contents of the folders in "Documents &
settings" folder are corrupt (ie: "All Users.Reactos", etc.)
So my question is : How can I disable the cache_manager? Or can I
place sync() commands somewhere in the source for testing. (is there
such a function available?).
The bsod seems to be related to gdi issues during creating the primary
surface. Somewhere the DeviceObject for the screen is NULL and is not
caught till it causes a GPE much later.
I'll give a little info that I've written down.
/ntoskrnl/io/irp.c:570 - GPE
/ntoskrnl/io/irp.c:911
/subsystems/win32/win32k/objects/dc.c:693
/subsystems/win32/win32k/ntuser/winsta.c:348
/subsystems/win32/win32k/ntuser/guicheck.c:57
/subsystems/win32/win32k/objects/dc.c:853
/subsystems/win32/win32k/ntuser/windc.c:121
/subsystems/win32/win32k/ntuser/windc.c:441
/subsystems/win32/win32k/ntuser/windc.c:529
/subsystems/win32/win32k/ntuser/windc.c:101
/ntoskrnl/ke/traps.c:306
/dll/win32/user32/windows/dialog.c:696
Hope this helps.
I was using the lastest SVN at the time (21738 I think).
Thanks.
Peter Quiring
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Ge van Geldorp wrote:
>
> > From: Murphy, Ged (Bolton)
> >
> > I was thinking along the lines of stopping the DHCP service
> > and calling AddIPAddress, which should be the same as
> > inserting the address manually in the registry. I haven't
> > looked into this though, so might not work.
>
> I kind of like the Windows design: the DHCP client service is actually
> implemented in dhcpcsvc.dll (you can see the "ServiceMain"
> export). This
> allows concentration of all usermode IP address/registry
> stuff in one DLL.
> AddIPAddress would then call into dhcpcsvc.
Do you know how much work would be involved in moving our DHCP client into
dhcpcsvc and implementing everything around this?
If it's quite a lot of work it might be worth me trying out what I
mentioned, just has a hack until we have time to do things the Windows way.
If your ReactOS work is going to concentrate solely on the kernel now, we
might be waiting a long time to get this implemented as nobody seems to want
to pick ncpa up. It's become the ReactOS forbidden fruit ;)
Any method would be good at this stage to get ncpa working, as it's our only
missing feature for the 0.3 release.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Ge van Geldorp wrote:
>
> > From: Murphy, Ged (Bolton)
> >
> > Is there a particular reason you were doing this via the DHCP
> > client and not just using functions provided by iphlpapi?
>
> I couldn't find iphlpapi functions to do this. But even if
> they're there,
> iphlpapi will need to inform the DHCP client about the change
> to static IP
> address (basically telling the DHCP client to shut up and go
> to sleep).
I was thinking along the lines of stopping the DHCP service and calling
AddIPAddress, which should be the same as inserting the address manually in
the registry. I haven't looked into this though, so might not work.
(stopping the service would need a temporary hack, as it's not been
converted to an NT service yet, plus we don't have StartService to restart
it)
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
After I had linux complain at me during a file copy onto a ReactOS
partition, I checked it with dosfsck, and found all some issues.
Since then I have been checking the partition I use for vmware after
installs. dosfsck has been finding errors every time. I ran a quick
regression test and it seems the was introduced between 0.2.8 and
0.2.9. It seems that most of these errors are non fatal, as myself
and others have not noticed this causing any problems. Still, it
bothers me, since it could be causing a problem somewhere. GreyGhost
claimed Windows was not finding any issues with his ros partition, can
anyone confirm?
I'm using flat disk images under vmware and qemu, and I'm seeing this
issue under both. I'm using both IDE and SCSI drives under vmware,
and see the issues with both types.
Anyone who is more famliar with filesystems care to comment?
dosfsck of a 0.2.9(and HEAD) install:
root@phoenix:/home/ford/public/virtuals/vmware/ReactOS# dosfsck -v /dev/loop0
dosfsck 2.10 (22 Sep 2003)
dosfsck 2.10, 22 Sep 2003, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "MSWIN4.1"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
8192 bytes per cluster
1 reserved sector
First FAT starts at byte 512 (sector 1)
2 FATs, 16 bit entries
102400 bytes per FAT (= 200 sectors)
Root directory starts at byte 205312 (sector 401)
512 root directory entries
Data area starts at byte 221696 (sector 433)
51125 data clusters (418816000 bytes)
63 sectors/track, 16 heads
63 hidden sectors
818433 sectors total
/ReactOS/SYSTEM32/CONFIG/SYSTEM
File size is 61440 bytes, cluster chain length is > 65536 bytes.
Truncating file to 61440 bytes.
/ReactOS/SYSTEM32/CONFIG/SOFTWARE
File size is 122880 bytes, cluster chain length is > 122880 bytes.
Truncating file to 122880 bytes.
Checking for unused clusters.
Leaving file system unchanged.
/dev/loop0: 361 files, 6907/51125 clusters
dosfsck of a 0.2.8 install:
root@phoenix:/home/ford/public/virtuals/vmware/ReactOS# dosfsck -v /dev/loop0
dosfsck 2.10 (22 Sep 2003)
dosfsck 2.10, 22 Sep 2003, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "MSWIN4.1"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
8192 bytes per cluster
1 reserved sector
First FAT starts at byte 512 (sector 1)
2 FATs, 16 bit entries
102400 bytes per FAT (= 200 sectors)
Root directory starts at byte 205312 (sector 401)
512 root directory entries
Data area starts at byte 221696 (sector 433)
51125 data clusters (418816000 bytes)
63 sectors/track, 16 heads
63 hidden sectors
818433 sectors total
Checking for unused clusters.
/dev/loop0: 324 files, 5501/51125 clusters
Here is a dosfsck of the scsi build disk I use under vmware, after a
partial build:
root@phoenix:/home/ford/public/virtuals/vmware/ReactOS# losetup -o
32256 /dev/loop0 build-scsi-flat.vmdk
root@phoenix:/home/ford/public/virtuals/vmware/ReactOS# dosfsck -v /dev/loop0
dosfsck 2.10 (22 Sep 2003)
dosfsck 2.10, 22 Sep 2003, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "MSWIN4.1"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
4096 bytes per cluster
32 reserved sectors
First FAT starts at byte 16384 (sector 32)
2 FATs, 32 bit entries
4185088 bytes per FAT (= 8174 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 8386560 (sector 16380)
1046185 data clusters (4285173760 bytes)
63 sectors/track, 255 heads
63 hidden sectors
8385867 sectors total
/REACTOS/makefile.auto
File size is 2274845 bytes, cluster chain length is > 2277376 bytes.
Truncating file to 2274845 bytes.
/REACTOS/MEDIA/FONTS/COUR.TTF
File size is 144456 bytes, cluster chain length is > 147456 bytes.
Truncating file to 144456 bytes.
/REACTOS/MEDIA/FONTS/.svn/text-base/cour.ttf.svn-base
File size is 144456 bytes, cluster chain length is > 147456 bytes.
Truncating file to 144456 bytes.
/REACTOS/MEDIA/NLS/C_949.NLS
File size is 196642 bytes, cluster chain length is > 200704 bytes.
Truncating file to 196642 bytes.
/REACTOS/MEDIA/NLS/C_932.NLS
File size is 162850 bytes, cluster chain length is > 163840 bytes.
Truncating file to 162850 bytes.
/REACTOS/MEDIA/NLS/C_950.NLS
File size is 196642 bytes, cluster chain length is > 200704 bytes.
Truncating file to 196642 bytes.
/REACTOS/MEDIA/NLS/C_936.NLS
File size is 196642 bytes, cluster chain length is > 200704 bytes.
Truncating file to 196642 bytes.
/REACTOS/MEDIA/NLS/.svn/text-base/c_949.nls.svn-base
File size is 196642 bytes, cluster chain length is > 200704 bytes.
Truncating file to 196642 bytes.
/REACTOS/MEDIA/NLS/.svn/text-base/c_932.nls.svn-base
File size is 162850 bytes, cluster chain length is > 163840 bytes.
Truncating file to 162850 bytes.
/REACTOS/MEDIA/NLS/.svn/text-base/c_950.nls.svn-base
File size is 196642 bytes, cluster chain length is > 200704 bytes.
Truncating file to 196642 bytes.
/REACTOS/MEDIA/NLS/.svn/text-base/c_936.nls.svn-base
File size is 196642 bytes, cluster chain length is > 200704 bytes.
Truncating file to 196642 bytes.
/REACTOS/MEDIA/DRIVERS/ETC/SERVICES
File size is 398472 bytes, cluster chain length is > 401408 bytes.
Truncating file to 398472 bytes.
/REACTOS/MEDIA/DRIVERS/ETC/.svn/text-base/services.svn-base
File size is 390238 bytes, cluster chain length is > 393216 bytes.
Truncating file to 390238 bytes.
/REACTOS/subsystems/WIN32/WIN32K/INCLUDE/NAPI.H
File size is 34990 bytes, cluster chain length is > 36864 bytes.
Truncating file to 34990 bytes.
/REACTOS/subsystems/WIN32/WIN32K/DIB/DIB8GEN.C
File size is 678744 bytes, cluster chain length is > 679936 bytes.
Truncating file to 678744 bytes.
/REACTOS/subsystems/WIN32/WIN32K/DIB/DIB16GEN.C
File size is 527182 bytes, cluster chain length is > 528384 bytes.
Truncating file to 527182 bytes.
/REACTOS/subsystems/WIN32/WIN32K/DIB/DIB32GEN.C
File size is 254584 bytes, cluster chain length is > 258048 bytes.
Truncating file to 254584 bytes.
/REACTOS/INCLUDE/DDRAW.H
File size is 155097 bytes, cluster chain length is > 155648 bytes.
Truncating file to 155097 bytes.
/REACTOS/INCLUDE/STRMIF.H
File size is 271851 bytes, cluster chain length is > 274432 bytes.
Truncating file to 271851 bytes.
/REACTOS/INCLUDE/WINUSER.H
File size is 137624 bytes, cluster chain length is > 139264 bytes.
Truncating file to 137624 bytes.
/REACTOS/INCLUDE/.svn
Has a large number of bad entries. (37/61)
Drop directory ? (y/n)
some more
/REACTOS/LIB/3RDPARTY/LIBXML2/.svn/PROPS/ormation.s f
Start cluster beyond limit (1952542496 > 1046186). Truncating file.
/REACTOS/LIB/3RDPARTY/LIBXML2/.svn/PROPS/ormation.s f
File size is 1634887024 bytes, cluster chain length is 0 bytes.
Truncating file to 0 bytes.
/REACTOS/LIB/3RDPARTY/LIBXML2/.svn/PROPS/FSCK0004.REN
Start cluster beyond limit (1882144357 > 1046186). Truncating file.
/REACTOS/LIB/3RDPARTY/LIBXML2/.svn/PROPS/FSCK0004.REN
File size is 1751347823 bytes, cluster chain length is 0 bytes.
Truncating file to 0 bytes.
/REACTOS/LIB/3RDPARTY/LIBXML2/.svn/PROPS/FSCK0005.REN
Start cluster beyond limit (1953394021 > 1046186). Truncating file.
/REACTOS/LIB/3RDPARTY/LIBXML2/.svn/PROPS/FSCK0005.REN
File size is 544830063 bytes, cluster chain length is 0 bytes.
Truncating file to 0 bytes.
/REACTOS/LIB/3RDPARTY/LIBXML2/.svn/PROPS/--noout.tes
Directory has non-zero size. Fixing it.
/REACTOS/LIB/3RDPARTY/LIBXML2/.svn/PROPS/--noout.tes
Start cluster beyond limit (1852991008 > 1046186). Truncating file.
/REACTOS/LIB/3RDPARTY/LIBXML2/.svn/PROPS/d to loa.d e
Directory has non-zero size. Fixing it.
/REACTOS/LIB/3RDPARTY/LIBXML2/.svn/PROPS/d to loa.d e
Start cluster beyond limit (1953395746 > 1046186). Truncating file.
/REACTOS/LIB/3RDPARTY/LIBXML2/WIN32/WINCE/LIBXML2.VCP
File size is 150203 bytes, cluster chain length is > 151552 bytes.
Truncating file to 150203 bytes.
/REACTOS/LIB/3RDPARTY/LIBXML2/WIN32/WINCE/.svn/text-base/libxml2.vcp.svn-base
File size is 144930 bytes, cluster chain length is > 147456 bytes.
Truncating file to 144930 bytes.
/REACTOS/NTOSKRNL/BUGCODES.RC
File size is 12664 bytes, cluster chain length is > 16384 bytes.
Truncating file to 12664 bytes.
/REACTOS/NTOSKRNL/INCLUDE/INTERNAL/NAPI.H
File size is 13786 bytes, cluster chain length is > 16384 bytes.
Truncating file to 13786 bytes.
/REACTOS/NTOSKRNL/MM/SECTION.C
File size is 145682 bytes, cluster chain length is > 147456 bytes.
Truncating file to 145682 bytes.
/REACTOS/NTOSKRNL/MM/.svn/text-base/section.c.svn-base
File size is 140762 bytes, cluster chain length is > 143360 bytes.
Truncating file to 140762 bytes.
/REACTOS/NTOSKRNL/EX/ZW.S
File size is 42498 bytes, cluster chain length is > 45056 bytes.
Truncating file to 42498 bytes.
/REACTOS/DLL/DIRECTX/DPLAYX/DPLAY.C
File size is 175774 bytes, cluster chain length is > 176128 bytes.
Truncating file to 175774 bytes.
/REACTOS/DLL/DIRECTX/DPLAYX/.svn/text-base/dplay.c.svn-base
File size is 170323 bytes, cluster chain length is > 172032 bytes.
Truncating file to 170323 bytes.
WD
--
ReactOS is a hub, follow the spokes and you'll
immediately find absolutely everything you need
to know about Windows. ReactOS is not just
software, it's people.
kjk_hyperion
christoph, christoph, why are you trying to insult someone who is
looking to further the long-term aims and goals of free software,
by putting people in touch on perceived unrelated projects and
explaining to them the relevance?
you have a specific area of expertise (according to your 2005
ukuug bio) - kernel development.
i would welcome an opportunity for you to explain why my life,
which happens to be quite poignantly sad and unfulfilling in
many ways, has any relevance to the discussion at hand - and,
also, if you could possibly elaborate on why i am "beeeing an asshole"
likewise has any relevance.
also: i would strongly advise you to consider objectively what
i am trying to do - and forget what you do not know about me
[you know nothing about me].
forget that i am involved in this discussion, because it is
clearly affecting your (and evidently other people's) objective
judgement.
freedce is an important and under-recognised project that can
save literally man-decades of development time currently
being wasted by key free software projects, and lack of recognition
for it is also stopping several interoperability projects from even
_happening_.
you want to know how many incompatible free software
implementations there are of MSRPC around? i count FOUR,
all written in c.
EACH of those projects has had at least two full-time members working on
them for AT LEAST three years, and each of those projects will require
those full-time members to continue working on those incompatible and
fundamentally non-interoperable development environments for another
three to five years, to make them useful - as development environments,
rather than to "fill one project's needs".
[whereas, if one of the fat cat free software "supporting"
companies would actually get off their backsides and fund
freedce, it would save everybody several decades worth of money]
you see - until such time as those non-interoperable MSRPC
projects are completed, microsoft still dominates the market.
MSRPC is the key infrastructure which binds everything together in the
microsoft world: it's what the European Union is trying to get out of
microsoft in the anti-trust case: information on how they use MSRPC;
how they do their authentication; the IDL files; specifications on the
nt domain services; etc. etc.
you indicated in an earlier email that (please correct me if my
impressions are wrong) that freedce is archaic and therefore irrelevant.
nothing could be further from the truth, and your distaste
for freedce is very short-sighted.
mark, from ibm: you should be advocating to ibm's free software
departments to back freedce and to KEEP the employees who worked
on DCE 3.0 and move them to freedce and MSRPC interoperability.
get some of that multi-hundred-million-dollar free software
advertising budget and put a fractional percentage of it
behind freedce.
you don't have to _like_ freedce.
you don't have to like its history.
you don't have to like that it is me that is advocating its use.
but don't you _dare_ insult me and think it doesn't have any effect.
so. i look forward to receiving an apology from you - not
for my benefit, but because it will mean that you are willing to
demonstrate to the hundreds of people to whom your message has been
distributed, and to the thousands of people who will encounter it
in the future, that you can be trusted to make objective and
important decisions.
and that you don't deliberately go out of your way to
belittle and bully other people.
if you are unable to apologise, then you demonstrate, to me and
to others, that you do not deserve any position of responsibility.
am i making myself clear?
l.
On Tue, Apr 25, 2006 at 07:22:16PM +0200, Christoph Hellwig wrote:
> luke, please get a life and stop beeing an asshole, thanks.
>
--
--
lkcl.net - mad free software computer person, visionary and poet.
--
The ReactOS Compatibility Database has reached beta status.
URL: http://www.reactos.org/support/
The compatibility database has been designed to store application and
driver data.
Simply click on one of the 5 green start buttons on the frontpage to
begin to browse through the database.
To submit an application/driver, click on "Submit Application" (menu bar).
Please have a look at the help and faq section for more information.
The goal of the whole compatibility database is to provide one single
unified place where a lot of compatibility data can be found.
This has several advantages:
For user it is easy to find out which software does already work in
ReactOS and how good it work.
Everyone (with a myReactOS account) can submit applications/drivers,
additional information, vendor data, compatbility test reports,
screenshots and post "compatibility forum" entries.
In the last few months, several people asked how they could help in
the ReactOS project. Now there is a way for people who don't know
programming languages, etc., they can now submit their testing results
to one place, the compatibility database. Note, in the compatibility
database there is a link to the bugzilla related page.
>From now on it will be easier for developers to check regression data, etc.
There might be some glitches and bugs, if you find some please post a
bugzilla bug entry, write a forum entry or write a reply here (mailing
list).
If someone has suggestions and/or ideas how to improve the
compatibility database please write a reply, thx.
Klemens Friedl
On Mon, Apr 24, 2006 at 10:42:43AM -0500, Mark Brown wrote:
> BTW: IBM stopped selling DCE/DFS years ago. The end of support
> for the product is this month.
yeh. there are universities (e.g. the authors of eLion) now hunting
around to find ways to keep their systems going.
ah well.
ReactOS.Bugzilla(a)reactos.org wrote:
> http://www.reactos.org/bugzilla/show_bug.cgi?id=1431
>
> Summary: Regression of setup
> Product: ReactOS
> Version: unspecified
> Platform: VMWare 5
> OS/Version: ReactOS
> Status: NEW
> Severity: normal
> Priority: P3
> Component: Win32
> AssignedTo: ros-bugs(a)reactos.org
> ReportedBy: email1562000(a)yahoo.com
> QAContact: ros-bugs(a)reactos.org
>
>
> filezilla FTP server setup works properly in build 21454(apr-8-2006) but in
> build 21725(apr-25-2006) all the drop down lists just show a series of squares
> where text should be displayed.
>
>
Could you post pics to the bug list?
Thanks,
James
On Fri, Apr 21, 2006 at 01:52:58PM -0700, Roland McGrath wrote:
> Have you considered instead using standard features as specified in POSIX
> since around 1996?
dce predates the posix standards - that's why all dce projects, some of
them multi-hundred-million-dollar projects by ibm, fujitsu, EDS etc -
have had to use posix draft 4 threading.
the opengroup developers had to make a decision: they couldn't wait
around for a few years while the POSIX committee made up their minds.
so all the companies who were running dce/rpc applications had to write
POSIX Draft 4 threading libraries for their operating systems.
ibm did it. sun microsystems did it. microsoft did it (Win32 threads)
when they ported the BSD-compatible OSF/1.0 licensed DCE 1.1 reference
implementation to win32, as the basis of MSRPC.
> What's your plan for other POSIX systems, such as Solaris?
forget solaris: sun microsystems can deal with solaris.
linux is the innovation leader, now, not solaris.
> If you don't want to cancel threads as cancellation is defined by POSIX,
> then why use cancellation instead of another mechanism that matches your needs?
[long answers first, short one at end]
because, despite being an absolutely critical strategic project that
could save key strategic free software projects who are _not_ using it
about a man-decade of development effort _each_, there is absolutely
zero recognition of this and therefore absolutely zero funding of the
project.
luke howard uses freedce for his XAD project, which is a (proprietary)
Active Directory replacement that he released THREE YEARS ago (and the
samba team _still_ haven't got an active directory server replacement
yet).
XAD is capable of running on IBM z390 mainframes, and luke howard
has won business awards for his work.
because, as it is "old" code, with a very archaic and interesting
development history, it needs work to be brought up-to-date. and
because it needs work, and _because_ it is so very comprehensive
in what it does, people misunderstand and do not appreciate its
complexity, and therefore think, "i can do better than this", and
fail miserably, and so it gets ignored.
the gist is this: the use of cancellation is embedded very deeply into
the design of this code.
and there isn't anyone with the time, money, resources or
immediately-available knowledge to rip a quarter of a million lines of
code apart looking for a way to shoe-horn some very complex and subtle
interaction _out_ of freedce so that it fits nicely with POSIX.
anyone think i should try to put the "emulation" bit back
into dcethreads (to re-wrap the cancellation rules of posix
draft 4 but to keep the new API) and write redhat off (just
like charles advised right at the beginning of this thread),
let me know.
l.
> http://www.reactos.org/bugzilla/show_bug.cgi?id=1300
>
>
> greatlord(a)reactos.com changed:
>
> What |Removed |Added
> --------------------------------------------------------------
> --------------
> Status|REOPENED |RESOLVED
> Resolution| |INVALID
>
>
>
>
> ------- Additional Comments From greatlord(a)reactos.com
> 2006-04-20 16:45 CET -------
> This is not a vaild bug report, each program is response for
> the icon for the
> file format
>
Sorry to reply directly to this, but I don't have web access at the moment.
The above is not true. Some default file icons are controled by the
operating system, like .txt, .jpg, or .bmp for example. They can be
over-ridden by 3rd party apps.
This is a valid bug report.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
On Thu, Apr 20, 2006 at 03:04:21PM +1000, Luke Howard wrote:
luke, you are a star: thank you for helping out with this.
just for people's information (in case it's not been mentioned here - i
must admit i forgot to notify opendce(a)opengroup.org!)
about 6-8 months ago i did a coding-spree on freedce, with a view to
achieving two, maybe three, major things:
1) porting to win32 (if you use pthreads-win32)
2) using posix final draft (7?) threads not posix draft 4.
3) proving to the people on wine and reactos that they have
a hell of a lot of work to do (measured in man-decades)
by not using the open group's DCE/RPC reference
implementation.
here's the gotchas that i encountered, and had to give up:
- udp worked, but tcp did not
- reactos had some problems at the time with the code behind
ipconfig.exe (NetTransportEnum i think it was)
- pthreads-win32 was too strictly posix compliant (!)
and there is a cancellation exception or something which
makes it fail in the dcethreads exception library tests,
where linux does not fail (!)
maybe this is related to what lukeh is talking about.
*shrug*.
anyway, the upshot is that freedce/latest-cvs also doesn't work
on TCP, and thank you so much people for helping track down why.
it's only been ten years so far: hopefully some time within the next
decade, freedce will be used for some real MSRPC-related free
software projects.
l
> >In rpc__cn_network_receiver(), rpc__socket_close() is called without an
> >exception handler in place. According to IEEE Std 1003.1 (2004), close()
> >is a cancellation point, see:
> >
> >http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_09.html
> >
> >Given this, a receiver thread could receive a cancel whilst closing the
> >socket, which will cause to entire program to abort. (We have seen this
> >occur when the RPC server is under load.)
> >
> >A suggested fix is to move the call to rpc__socket_close() inside the
> >TRY/CATCH_ALL block that removes any pending cancels.
>
> It seems like the real fix is to disable cancellation within
> rpc__socket_close(), because in other places the OSF code appears to
> assume that this is not a cancellation point.
>
> Ditto for open(), socket(), etc (but not I/O routines that may block).
>
> I should note that the Linux dcethreads library does actually disable
> cancellation for these calls, however in our own DCE thread library
> we opted not to override any system calls to avoid changing semantics
> when used by non-DCE code.
>
> -- Luke
>
> --
>
--
--
lkcl.net - mad free software computer person, visionary and poet.
--
I just did some digging around, and this issue was introduced
somewhere between 20902 and 20911. Alex was working on the kernel
heavily at the time, and there are several intertwined commmits IIRC.
I just tested 20902 with both kqemu (and -kernel-kqemu) and it
installed fine, and ran as well as I remember it did. It was
noticably faster.
On 4/17/06, WaxDragon <waxdragon(a)gmail.com> wrote:
> This bug has been around for a while.
>
> On 4/17/06, Víctor Córcoles López <vcorcoles25(a)hotmail.com> wrote:
> > Reactos 0.3.0 SVN + kqemu fails as guest O.S. It fails in both systems,
> > Linux host and Windows Host. Without kqemu the reactos 0.3.0 SVN runs with
> > less bugs.
> >
> > In VMWARE host, this bug not apear.
> >
> > I Send a screenshot of failure.
> >
WD
--
ReactOS is a hub, follow the spokes and you'll
immediately find absolutely everything you need
to know about Windows. ReactOS is not just
software, it's people.
kjk_hyperion
greatlrd(a)svn.reactos.org wrote:
> Author: greatlrd
> Date: Sun Apr 16 20:04:28 2006
> New Revision: 21611
>
> URL: http://svn.reactos.ru/svn/reactos?rev=21611&view=rev
> Log:
> kjk_hyperion : "Breaking auditing lock for a temporary fix: allow ExEnterCriticalRegionAndAcquireFastMutexUnsafe and ExReleaseFastMutexUnsafeAndLeaveCriticalRegion to be called from any thread; fixes UserEnterShared, UserEnterExclusive and UserLeave in win32k"
>
> Modified:
> trunk/reactos/ntoskrnl/ex/fmutex.c
>
> Modified: trunk/reactos/ntoskrnl/ex/fmutex.c
> URL: http://svn.reactos.ru/svn/reactos/trunk/reactos/ntoskrnl/ex/fmutex.c?rev=21…
This fix is broken. The real problem is win32k, you should fix that instead.
Best regards,
Alex Ionescu
> From: greatlrd(a)svn.reactos.org
>
> Log:
> fix 16 to 16 soyrce dest why the hell does th 16bitmap surface calls
> into this
The "16 -> 16 copy" in the DPRINT1 is a copy/paste mistake, it should read "24 -> 24 copy". Your fix is incorrect. What needs to be done in this case is process one pixel at a time, calling XLATEOBJ_iXlate on each one.
GvG
Hi. I'm trying to debug ros with gdb (according to GvG's tutorial) and I
have a problem. After I attach gdb, reactos boots into desktop and then
freezes with endless sigservs. Mouse cursor is not moving. Any ideas?
(gdb) target remote localhost:567
Remote debugging using localhost:567
0x800a8297 in ?? ()
(gdb) continue
Continuing.
*** Now ros boots into desktop. ***
Program received signal SIGSEGV, Segmentation fault.
0x0040aa12 in ?? ()
(gdb) continue
Continuing.
Can't send signals to this remote system. SIGSEGV not sent.
Program received signal SIGSEGV, Segmentation fault.
0x0040aa12 in ?? ()
(gdb) continue
Continuing.
Can't send signals to this remote system. SIGSEGV not sent.
Program received signal SIGSEGV, Segmentation fault.
0x0040aa12 in ?? ()
......
> [CC] dll/win32/wininet/cookie.c
> [CC] dll/win32/wininet/dialogs.c
> [CC] dll/win32/wininet/ftp.c
> [CC] dll/win32/wininet/gopher.c
> [CC] dll/win32/wininet/http.c
> dll/win32/wininet/http.c:62:23: inet_ntop.c: No such file or directory
> dll/win32/wininet/http.c: In function `HTTP_HttpOpenRequestW':
> dll/win32/wininet/http.c:1154: warning: implicit declaration of
> function `inet_ntop'
> make: *** [obj-i386/dll/win32/wininet/http.o] Error 1
It looks like it's trying to include a file that doesn't exist. Maybe
somebody forgot to run "svn add inet_ntop.c" before they committed their
changes?
> From: Gunnar Modin <gunnar.modin(a)telia.com>
> Sent: Saturday, April 15, 2006 21:31
> To: ros-dev-owner(a)reactos.org
> Subject: React OS
>
> I just woder if there is any way I can perticipate in the
> development of the OS.
>
> I have an masterthesis to do on my education at the Mid
> Sweden university.
> The project shell due for about four mounth on full time. The
> plan is to do it on half time the coming winter.
>
> The topics that I have studied are Distributed Systems and
> Networkning.
> I have jused both C++ and Java as programming laguage. I also
> did an projekt in Distrubuted system regarding XML and acess.
> In Networking I studied IPv6 in more detail.
>
> Best regards
>
> Gunnar Modin
>
Hi,
I'd like to give you a little report on the status of the cache manager
rewrite branch. Since Filip and Hartmut are gone no one worked on it,
though the actual functionality is already completed since the first
commit in February 2005 and the code just needs to debugged.
So decided to give it a try and merged the changes from trunk in there.
I had to recreated the branch, from the last unlocked revision because
of all the directory movements and tortoise merge having problems with
them.
I also did some debugging work on it. I have stored my results in the
bugzilla bugs 942, 1360 and 1362. These are the only bugs I know of
which hinder the branch from being merged to trunk. I am going on
holiday tomorrow, so it would be nice if anyone else could continue
working on fixing them.
You can also help testing because we should do a lot of testing before
merging. Especially file IO intensive applications, like installers need
testing. Also the ext2fs branch, Microsoft's ntfs.sys and Vmware tools
could work. But I haven't tested any of them.
I will provide a patch to trunk so you do not have to check out or
switch to the branch which is quite annoying, because all the locked
entries are checked out again.
Hopefully the new cache manager will be in place when I am back.
Best Regards
Maarten Bosma
Hi!
URL: http://svn.reactos.ru/svn/reactos?rev=21550&view=rev
Log:
revert comctl32 Wine sync. There are some issues with it and I don't have time to fix it at the moment.
Tonight, I will have time to check and see what we need to make this work.
Thanks,
James
ReactOS.Bugzilla(a)reactos.org wrote:
> http://www.reactos.org/bugzilla/show_bug.cgi?id=1358
>
>
> tomasgroth(a)yahoo.dk changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> BugsThisDependsOn|1342 |
>
>
>
>
Hi!
What is the status of these bugs? Have all of them been added to the tree yet?
Thanks,
James
Aleksey Bragin wrote:
> 'I read this code and it looked clean to me' line means that
> the commiter
> read the code, and assures all or some parts of the following:
> 1. The code doesn't match any reverse-engineered rules (as on
> wiki page regarding Audit)
> 2. The code is publically documented
> 3. The code has nothing to do with reverse engineering (has either
> completely different implementation from the windows one -
> example freeldr
> vs. ntldr/osloader, or doesn't have any counterpart in
> windows at all).
Then why not describe it using one of the above reasons?
A note such as 'This code uses MSDN documented functions only' is clear and
useful.
A note saying 'I read this code and it looked clean to me' isn't and could
mean anything.
> > It gives a good base point for us to start our defence from.
> We are not under attack. We are just doing some preventive measures.
I know. I said 'if the cleanliness of the code is ever questioned again'.
If that does happen, it could be in the form of an attack from an outside
company.
Having a better analysis as to why something was unlocked would be
advantageous if this situation ever arose.
> > This was all decided when we originally locked the code,
> > but no one has been following it.
> arty, w3seek, me have been following this rules on the
> possibly dirty code, so please don't speak for everyone.
I don't mean the auditing methods, I mean the lack of useful message.
I'm not accusing or judging anyone, I'm just trying to get a better
unlocking system in place.
As the code we audit gets closer to the border line of clean and dirty,
we're gonna need to ensure we don't leave messages like 'yep, looks ok to
me'
I hope mail this isn't coming across to anyone as argumentative. It's
difficult to have a conversation over email without it sounding hostile. It
isn't meant that way :)
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
If the author has been contacted, it should be noted in the commit log. That
alone is enough reason to squash any doubts anyone had. The authors word is
always trusted.
If the author couldn't be contacted, then the code should go through the
audit procedure Art put forward. Whichever part of that procedure was passed
should be noted in the commit log.
Even if it's just something as simple as 'this code uses is fully documented
on XYZ: http://..'
Doing things this way ensures we can look back at the code if the
cleanliness of the reversing methods is ever questioned again. It gives a
good base point for us to start our defence from.
This was all decided when we originally locked the code, but no one has been
following it. Thus we have terms like 'I read this code and it looked clean
to me'.
IMO, that isn't worth anything. I could read parts of the kernel and it
appear to be clean to me. Contacting Alex or correctly auditing the code
would prove otherwise.
In light of this, I think some of the audit measures we went to were a bit
of an over reaction. Perhaps we should have only decided to audit kernel
mode code, or subsections of it.
However we choose to do everything and I'm a firm believer in the phrase 'If
you going to do something, do it right'
Ged.
-----Original Message-----
From: Saveliy Tretiakov [mailto:saveliyt@mail.ru]
Sent: 07 April 2006 13:52
To: ReactOS Development List
Subject: Re: [ros-dev] ncpa
I always contact authors when it is possible. Some authors have left
project years ago and are unreachable.
Murphy, Ged (Bolton) wrote:
>The authors of the code should always be contacted before unlocking unless
>the app it produces isn't a part of Windows.
>
>Not doing so undermines the audit process and commit lines like 'I looked
at
>this code and it appears clean' is doing just that.
>
>Ged.
>
>-----Original Message-----
>From: Saveliy Tretiakov [mailto:saveliyt@mail.ru]
>Sent: 07 April 2006 13:11
>To: ReactOS Development List
>Subject: Re: [ros-dev] ncpa
>
>
>Do we need to audit ncpa?
>
>_______________________________________________
>Ros-dev mailing list
>Ros-dev(a)reactos.org
>http://www.reactos.org/mailman/listinfo/ros-dev
>************************************************************************
>The information contained in this message or any of its
>attachments is confidential and is intended for the exclusive
>use of the addressee. The information may also be legally
>privileged. The views expressed may not be company policy,
>but the personal views of the originator. If you are not the
>addressee, any disclosure, reproduction, distribution or other
>dissemination or use of this communication is strictly prohibited.
>If you have received this message in error, please contact
>postmaster(a)exideuk.co.uk
><mailto:postmaster@exideuk.co.uk> and then delete this message.
>
>Exide Technologies is an industrial and transportation battery
>producer and recycler with operations in 89 countries.
>Further information can be found at www.exide.com
>
>
>_______________________________________________
>Ros-dev mailing list
>Ros-dev(a)reactos.org
>http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
>
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
The authors of the code should always be contacted before unlocking unless
the app it produces isn't a part of Windows.
Not doing so undermines the audit process and commit lines like 'I looked at
this code and it appears clean' is doing just that.
Ged.
-----Original Message-----
From: Saveliy Tretiakov [mailto:saveliyt@mail.ru]
Sent: 07 April 2006 13:11
To: ReactOS Development List
Subject: Re: [ros-dev] ncpa
Do we need to audit ncpa?
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
This is all that stands in the way of getting 0.3.0 out the door.
As soon as we can config the network adapters via the dialog, we can branch
and start bug hunting.
This would also be a good time to enlist some more testers under the Munger
wing ;)
I'm going to have a look at this tonight, but I've had a look before and
IIRC, I had trouble hunting the bug down.
It would be good if someone with a bit more experience in this area could
have a look.
I think Gé was working on this before Christmas, so I'm hopefully gonna
catch up with him tonight via IM, as I'm not sure if he's subscribed to
ros-dev anymore.
We've been promising this for about 18 months now. I know a hell of a lot of
work has been done in other areas (in fact, the jump from 0.3 to 0.4 should
be relatively small as much of the 0.4 work is done), but we need to
deliver.
After all the recent goings on, getting 0.3.0 would be a nice boost for the
project, in terms of both morale and PR.
Is anyone willing to help?
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Hello!
In an effort to put ReactOS development into higher scales, I would
like to announce that I am creating a global list of all possible
development tasks, broken down into modules/sections/etc. By the time
all tasks in this list are fully completed, ReactOS would result in
transition to a beta-stage and bumping version number to >= 0.5 (so
you understand how big this todolist will be).
This list would be a base to the global ReactOS Roadmap which is
going to show a current status of reactos, expected times before
future releases, and what future releases will contain exactly.
And the most important: It makes every programmer willing to
participate in the project to find a task he feels familiar with,
actually do it, and see how it advances the project. All the way
before, the only really managed part of development was fixing bugs,
because Bugzilla is storing all bugs descriptions/patches/
assignations/etc. Now, similar thing will come in help to the general
development.
Creating such a list is quite a hard task, and it can't be done by an
individual, so:
Attention all ReactOS Developers, please! Your word is very valuable
here! Please, compile a list of tasks you think ReactOS needs and
send it here as a reply to this message (I will put a preliminary
draft of what I already compiled so far too somewhere in the wiki).
Each task should be a clearly outlined work if possible, however all
information is important so you can add something like "//TODO: Add
more details about this task later" too.
Example of a task considered as "good" to me:
- Boot manager
-- Make Loader Parameter Block compatible with Windows XP one
Example of a less exact task, but which is still "good"
- Boot manager
-- Make boot process conforming to NTLDR boot process, so that
FreeLdr can boot Windows without NTLDR.
Example of a "bad" task
- NTOSKRNL
-- Improve kernel
Thank you for the collaboration, I know this maybe a quite hard to
do, but it's the first steps of an effort to get development to the
speed and quality we never had before. Other things to mention are
continuos integration system, regression testing frameworks, etc, etc.
With the best regards,
Aleksey Bragin.