Hi Eric, are you sure this will not break compatibility with WIn2k3 applications? For example by quickly googling I've noticed some people rely on this Index value for their Time Zone stuff.
Example: https://www.experts-exchange.com/questions/24948382/How-to-get-Time-Zone-in…
Also, since http://microsoft.public.win32.programmer.ui.narkive.com/SOU9r3ef/time-zones… clearly says that the "IndexMapping" reg_multi_sz is for doing the mapping with the "Index" values of each time zone, you could have also deleted it! (note that this mapping value is indeed absent on Windows 7 for example).
Cheers,
Hermès
========================================
Message du : 03/07/2016 20:42
De : ros-diffs-request(a)reactos.org
A : ros-diffs(a)reactos.org
Copie à :
Sujet : Ros-diffs Digest, Vol 150, Issue 29
[...]
Today's Topics:
[...]
3. [ekohl] 71801: [BOOTDATA] Remove the Index value from the
time zone entries. We do not need it any more and it has been
removed from Windows Vista. (ekohl(a)svn.reactos.org)
----------------------------------------------------------------------
Message: 3
Date: Sun, 03 Jul 2016 18:40:27 -0000
From: ekohl(a)svn.reactos.org
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [ekohl] 71801: [BOOTDATA] Remove the Index value
from the time zone entries. We do not need it any more and it has been
removed from Windows Vista.
Message-ID:
Content-Type: text/plain; charset="utf-8"
Author: ekohl
Date: Sun Jul 3 18:40:27 2016
New Revision: 71801
URL: http://svn.reactos.org/svn/reactos?rev=71801&view=rev
Log:
[BOOTDATA]
Remove the Index value from the time zone entries. We do not need it any more and it has been removed from Windows Vista.
Modified:
trunk/reactos/boot/bootdata/hivesft.inf
Modified: trunk/reactos/boot/bootdata/hivesft.inf
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/bootdata/hivesft.inf?…
==============================================================================
--- trunk/reactos/boot/bootdata/hivesft.inf [iso-8859-1] (original)
+++ trunk/reactos/boot/bootdata/hivesft.inf [iso-8859-1] Sun Jul 3 18:40:27 2016
@@ -406,7 +406,6 @@
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Dateline Standard Time","Display",0x00000000,"(GMT-12:00) International Date Line West"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Dateline Standard Time","Dlt",0x00000000,"Dateline Daylight Time"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Dateline Standard Time","Std",0x00000000,"Dateline Standard Time"
-HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Dateline Standard Time","Index",0x00010001,0
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Dateline Standard Time","TZI",0x00000001,\
0xd0,0x02,0x00,0x00,0x00,0x00,0x00,0x00,0xc4,0xff,0xff,0xff,\
0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,\
(skipping........)
@@ -1125,7 +1046,6 @@
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Tonga Standard Time","Display",0x00000000,"(GMT+13:00) Nuku'alofa"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Tonga Standard Time","Dlt",0x00000000,"Tonga Daylight Time"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Tonga Standard Time","Std",0x00000000,"Tonga Standard Time"
-HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Tonga Standard Time","Index",0x00010001,300
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Tonga Standard Time","TZI",0x00000001,\
0xf4,0xfc,0xff,0xff,0x00,0x00,0x00,0x00,0xc4,0xff,0xff,0xff,\
0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,\
------------------------------
Subject: Digest Footer
_______________________________________________
Ros-diffs mailing list
Ros-diffs(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-diffs
------------------------------
End of Ros-diffs Digest, Vol 150, Issue 29
******************************************
This should probably be moved to \base\applications\cmdutils
-----Original Message-----
From: Ros-diffs [mailto:ros-diffs-bounces@reactos.org] On Behalf Of hbelusca(a)svn.reactos.org
Sent: 29 June 2016 01:39
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [hbelusca] 71695: [SUBST] - Update the resource program description. - Convert to full UNICODE. - Use Win32 functions where possible. - Factor-out the usage of QueryDosDevice into a QuerySubstedDri...
Author: hbelusca
Date: Wed Jun 29 00:38:51 2016
New Revision: 71695
URL: http://svn.reactos.org/svn/reactos?rev=71695&view=rev
Log:
[SUBST]
- Update the resource program description.
- Convert to full UNICODE.
- Use Win32 functions where possible.
- Factor-out the usage of QueryDosDevice into a QuerySubstedDrive function, that returns error codes according to whether the specified drive is a mapped (substed) drive, or is just an existing drive that is not a mapping, or if the drive does not exist. This allows us to detect attempts to use a drive letter that is not a mapped drive, to define a new mapping, and if so we reject such attempt.
This fixes CORE-10681 #resolve #comment Fixed with another patch according to my last remark.
Hello,
Let me invite you to the monthly status meeting taking place this
Thursday, 30rd of June, 19:00 UTC.
IRC service will only be started shortly before the meeting. Your
participation passwords and server address will be emailed to you
shortly before the meeting starts, and they are going to be different
once again as they are not stored in any database. Hopefully it's not
much of inconvenience.
Alternative place for the meeting is #reactos-meeting on Freenode.
Please send agenda proposals to me before the meeting. My proposal is
to discuss 0.4.2 release plans.
Regards,
Aleksey Bragin
Correct me if I'm wrong (Alex?), but isn't the biggest difference
between kernel 5.2 and 6.x that 6.x is *paging the kernel* ?
(A huge design mistake if you ask me. One I bet will bite MS on the a**.
If the kernel gets too fat it needs liposuction, not paging.)
IMHO, adding new APIs, while keeping the (non-paging) kernel seems ideal.
Best Regards
// Neo
On 2016-05-19 05.43, ros-dev-request(a)reactos.org wrote:
> Subject:
> Re: [ros-dev] Pale Moon drops ReactOS support
> From:
> Alex Ionescu <ionucu(a)videotron.ca>
> Date:
> 2016-05-19 02.33
>
> To:
> ReactOS Development List <ros-dev(a)reactos.org>
>
>
> I don't believe I said 'let's add random exports to our DLLs'. In
> fact, in your old thread, I was totally FOR your idea, I even wrote
> that the only sane way of doing it is with the app compat work.
>
> On Wed, May 18, 2016 at 9:27 PM, Timo Kreuzer<timo.kreuzer(a)web.de> wrote:
>> >We have been discussing this before and I wonder that Alex is not heavily
>> >opposing the idea of randomly adding new exports to our user mode DLLs. It
>> >is a well known fact that applications check for existance of exports to
>> >decide how to behave, so ... not going to go over this again.
>> >
>> >To addess this issue I suggested to implement a compatibility layer. And
>> >there was a detailed discussion about that on this mailing list.
>> >https://www.reactos.org/pipermail/ros-dev/2015-March/017216.html
>> >
>> >Please take your time to read the whole thread again so we can avoid wasting
>> >time, talking about the same things again.
>> >
>> >Timo
--
There is one thing stronger than all the armies in the world,
and that's an idea whose time has come. [Victor Hugo]
On 2016-06-15 12:10, zhu(a)svn.reactos.org wrote:
> --- branches/GSoC_2016/lwIP/drivers/network/tcpip/main.c [iso-8859-1] (original)
> +++ branches/GSoC_2016/lwIP/drivers/network/tcpip/main.c [iso-8859-1] Wed Jun 15 19:10:40 2016
> @@ -384,7 +384,9 @@
> Quickie:
> Irp->IoStatus.Status = Status;
>
> - return Irp->IoStatus.Status;
> + IoCompleteRequest(Irp, IO_NETWORK_INCREMENT);
> +
> + return Irp->IoStatus.Status;
> }
>
> static
This is illegal. IoCompleteRequest frees the IRP so you must not access
it afterwards, and use the local variable instead.
Hello developers,
After building ReactOS and Rostests successfully, I can't debug CoInitialize
function through Visual Studio 2015. It seems Visual Studio thinks I'm using
their CoInitialize of Windows kernel.
Anybody can help me?
Here is the steps I used to compile ReactOS and Rostests:
1. install Build Environment
https://reactos.org/wiki/ReactOS_Build_Environment
2. download code to the folder specified when by RosBE during installing
code: svn://svn.reactos.org/reactos/trunk/reactoshttp://svn.reactos.org/reactos/trunk/rostests/
reactOS directory -> E:\Work\reactos
rostests directory -> E:\Work\reactos\modules\rostests
3. generate reactos.sln for Visual Stdio
(a). Open a Windows DDK/WDK/Visual Studio 2015 command prompt.
(b). run the following command in the code root:
configure.cmd VSSolution
4. build the huge solutions
msbuild reactos.sln /m
5. open the 'ole32_winetest.vcxproj'
(E:\Work\reactos\output-VS-i386\modules\rostests\winetests\ole32)
Set the command arguments 'ole2', set breakpoint at CoInitialize
line, and start beginning by pressing F5, but Visual Studio can't get into
CoInitialize funtion
Best regards
Yonggang Chen
Hi,
Implementing MSAHCI would be "more correct" for the system, however MSAHCI
also doesn't use STORPORT, it uses ATAPORT, which requires changing our
PCIIDEX model to support that. Which I think would put Aman's work out of
scope.
Now, MSAHCI would be ported to use STORPORT instead, but then we'd
essentially be implementing a legacy component on top of a legacy port
driver.
At least, by implementing STORAHCI on top of STORPORT, we can implement a
'modern' component on top of the legacy port driver.
And for this, I would either recommend doing things like implementing
StorPortExtendedFunction
if Aman can do it -- or if someone can help him, or, avoiding its use with
temporary work/arounds, etc. _as long as those workarounds still work in
Windows_.
Best regards,
Alex Ionescu
On Sun, Jun 5, 2016 at 9:10 PM, Thomas Faber <thomas.faber(a)reactos.org>
wrote:
> I'm not an expert so I'm not sure what way is best. But I see at least
> 4 solutions:
> * There seems to be a way to get the extended function table through
> StorPortNotification/GetExtendedFunctionTable. This would provide
> some of the newer functionality even with older storport, but is
> potentially an undocumented hack
> * Avoid using the modern functionality and implement an old-storport
> compatible storahci, which implies using only memory from the adapter
> extension, and probably a few more things
> * Rely on a "modern" storport and do the testing in a newer Windows
> version. Then when ROS gets storport it simply needs to be a "modern"
> version
> * Do not use storport and implement msahci rather than storahci
>
> Option 2 would give the greatest compatibility but I can't pretend to
> understand what limitations it will imply.
>
>
> On 2016-06-05 21:43, Aman Priyadarshi wrote:
> > Yeah msahci is ataport miniport driver.
> > Then what would be the best idea? Leave it with the implementation I made
> > there. "Allocated memory for all port extension within device extension?"
> > ᐧ
> >
> >
> > Regards
> > *Aman Priyadarshi*
> > *www.atomixos.com <http://www.atomixos.com>*
> >
> >
> > On Mon, Jun 6, 2016 at 1:02 AM, Thomas Faber <thomas.faber(a)reactos.org>
> > wrote:
> >
> >> On 2016-06-05 14:40, apriyadarshi(a)svn.reactos.org wrote:
> >>> Author: apriyadarshi
> >>> Date: Sun Jun 5 12:40:49 2016
> >>> New Revision: 71530
> >>>
> >>> URL: http://svn.reactos.org/svn/reactos?rev=71530&view=rev
> >>> Log:
> >>> Added INF File for driver installation with minimal configuration.
> >>> Device Detection and Initialization working -- tested on VMware.
> >>> StorPortAllocatePool not working, so asked Storport to allocate all
> >> memory just after loading up the driver -- Bad idea (will change it
> later).
> >>
> >> StorPortAllocatePool uses StorPortExtendedFunction, which indeed is not
> >> implemented in Win2003. As you can see in WDK samples, 2003's msahci is
> >> not a storport miniport driver. Maybe storport wasn't advanced enough
> >> for complex drivers back then?
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
On 2016-06-05 14:40, apriyadarshi(a)svn.reactos.org wrote:
> Author: apriyadarshi
> Date: Sun Jun 5 12:40:49 2016
> New Revision: 71530
>
> URL: http://svn.reactos.org/svn/reactos?rev=71530&view=rev
> Log:
> Added INF File for driver installation with minimal configuration.
> Device Detection and Initialization working -- tested on VMware.
> StorPortAllocatePool not working, so asked Storport to allocate all memory just after loading up the driver -- Bad idea (will change it later).
StorPortAllocatePool uses StorPortExtendedFunction, which indeed is not
implemented in Win2003. As you can see in WDK samples, 2003's msahci is
not a storport miniport driver. Maybe storport wasn't advanced enough
for complex drivers back then?
On 2016-06-05 01:29, hbelusca(a)svn.reactos.org wrote:
> - rcDesk.left = GetSystemMetrics(SM_XVIRTUALSCREEN);
> - rcDesk.top = GetSystemMetrics(SM_YVIRTUALSCREEN);
> - rcDesk.right = rcDesk.left + GetSystemMetrics(SM_CXVIRTUALSCREEN);
> - rcDesk.bottom = rcDesk.top + GetSystemMetrics(SM_CYVIRTUALSCREEN);
> + rcDesk.left = GetSystemMetrics(SM_XVIRTUALSCREEN);
> + rcDesk.top = GetSystemMetrics(SM_YVIRTUALSCREEN);
> + rcDesk.right = GetSystemMetrics(SM_CXVIRTUALSCREEN);
> + rcDesk.bottom = GetSystemMetrics(SM_CYVIRTUALSCREEN);
Are you sure about this? "CX" normally means width, so right = left + cx
seems more logical. And SM_XVIRUTALSCREEN is probably 0 most of the
time so it would be hard to notice.
There's another one of these when the OS is running in test mode.
"Bcdedit -set TESTSIGNING ON" will display the following:
Test Mode
Windows (n)
Build (n)
Maybe you can add that one when Alex finishes his UEFI/BCD stuff :)
-----Original Message-----
From: Ros-diffs [mailto:ros-diffs-bounces@reactos.org] On Behalf Of hbelusca(a)svn.reactos.org
Sent: 01 June 2016 16:25
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [hbelusca] 71486: [WIN32K] Display a nice ReactOS version desktop watermark (with different fonts) when the corresponding registry values are set. See http://winaero.com/blog/a-new-way-to-display-t...
Author: hbelusca
Date: Wed Jun 1 15:24:38 2016
New Revision: 71486
URL: http://svn.reactos.org/svn/reactos?rev=71486&view=rev
Log:
[WIN32K]
Display a nice ReactOS version desktop watermark (with different fonts) when the corresponding registry values are set.
See http://winaero.com/blog/a-new-way-to-display-the-windows-version-on-your-de… for more details (which works on Windows 2003 too).
CORE-11349 #resolve
Would it not be better to do all this in C++ and let wine write a C interface around it?
When we're trying to move to C++, it seems like a step backwards in order to support wine's insistence on using C
-----Original Message-----
From: Ros-diffs [mailto:ros-diffs-bounces@reactos.org] On Behalf Of mjansen(a)svn.reactos.org
Sent: 28 May 2016 17:43
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [mjansen] 71439: [APPHELP] Begin shimlib implementation. CORE-11329 Implement some macro's and functions that help when registering shims. These are all written in C, so that wine can use the shim ...
Author: mjansen
Date: Sat May 28 16:42:57 2016
New Revision: 71439
URL: http://svn.reactos.org/svn/reactos?rev=71439&view=rev
Log:
[APPHELP] Begin shimlib implementation. CORE-11329 Implement some macro's and functions that help when registering shims.
These are all written in C, so that wine can use the shim libraries as well.
Hello all,
It seems that our Wikipedia page seems to have somewhat incorrect information in some sections on the page. Some of it seems to come from IP address which means that they are unregistered. Some of the information could be correct but some of the other information added could be incorrect. I propose that we can see if the wiki page could be Semi-Protected. If the page is Semi-Protected, that means that non-registered users (People logged as IPs in the log) and newly registered users (people that have less than 10 edits and that have been only registered for 4 days). This would mean that people that have been registered for a while and have made edits could edit the page. I hope that this would help with some of the incorrect information on the web page. Not sure what your thoughts are on this but I think it would be nice to have.
Jared
Hello,
Let me invite you to the monthly status meeting taking place next
Thursday, 2nd of June, 19:00 UTC, as I was busy before and general
consensuss on the IRC channel was to move it one week further.
IRC service will only be started shortly before the meeting. Your
participation passwords and server address will be emailed to you
shortly before the meeting starts, and they are going to be different
once again as they are not stored in any database. Hopefully it's not
much of inconvenience.
Please send agenda proposals to me before the meeting.
Regards,
Aleksey Bragin
On 2016-05-25 19.00, I wrote:
> Unfortunately, ntdll.pdb only exports 'SymTagPublicSymbol', no
> 'SymTagFunction' symbols,
If any of you is rich or fortunate enough to have a full MSDN subscription
you ought to be able to use a checked build of Win7SP1 to generate
the whole '.spec' enchilada.. I would if I was, but alas I'm not :/
If you could *lend me* ISO's of checked W7SP1 x86/x64,
I'll build checked virtual machines and generate the whole shebang
(provided SymSrv will fetch checked symbols (which I don't know)).
Best Regards
// Neo
Forget this issue... It remains, but I've moved on.
Thanks anyway.
// Neo
On 2016-05-24 19.00, Love Nystrom <love.nystrom(a)gmail.com> wrote:
> SymSrvIsStore keeps failing with error 0x7E no matter what I do :-/
--
There is one thing stronger than all the armies in the world,
and that's an idea whose time has come. [Victor Hugo]
@Timo,
I uploaded an ntdll.spec for Win7SP1.
Unfortunately, ntdll.pdb only exports 'SymTagPublicSymbol', no
'SymTagFunction' symbols, so it's not possible to generate the parameter
lists. If they're needed they'll have to be inserted manually or I'll
have to write a tool that gets them from "wInternl.h" :/
++ At least I was able to resolve the names of the 8 ordinal functions.
I won't go into all the skull dredging details of getting thus far..
Suffice to say it involved uttering various sulphur reeking curses in
nine different languages and threatening the entire human race with
extinction, writing a dummy program and running it in WinDbg to make
SymSrv fetch ntdll.pdb, and hacking CreateSpec beyond recognition with
various hardcoded path names.
Best Regards
// Neo
So I've been trying to get ReactOS installed on the Windows QEMU build from
https://qemu.weilnetz.de/ and during the file copy part of the first stage
installer the thing, slows down. Substantially. And then silently comes to
a standstill. I'm not sure whether this is an I/O issue in ReactOS or what,
the old qemu that we used for the older 0.3.x releases didn't have this
problem. Anyone have any ideas?
On 2016-05-24 19.00, "David Quintana (gigaherz)" <gigaherz(a)gmail.com> wrote:
> Wouldn't that make people MORE interested in using reactos if it
> becomes a way for them to have NT6, without pirating or buying Windows?
Yes it would, of course..
I understand there is, f.ex, a keen interest in India.
India has a long history of mathematics, philosophy, et c,
but has been quite poor for as long as I remember.
A free windows compatible OS would be most welcome, I'm sure.
Sidenote: They have good programmers too (even though they
have a tendency to "do as they're told" and say nothing
even if they see a better way to go. (A cultural thing.))
Here in Southeast Asia computer literacy is still
in it's infancy, and the people a far from wealthy,
so I'm sure a working ReactOS would be most welcome
if people knew about it.
Best Regards
// Neo
>
> On 23 May 2016 at 14:21, Love Nystrom <love.nystrom(a)gmail.com
> <mailto:love.nystrom@gmail.com>> wrote:
>
> Ok, I can understand if it has become uncommon in rich parts of
> the world like Europe and US,
> f.ex in Italy, but the rest of the world would probably seem
> arcane computerwise to you.
>
> Here in Southeast Asia where I live, many still run WinXP on their
> office workstations.
> Likewise, they run Server 2oo3, if they indeed have legitimate
> licenses at all.
> In the computer shops you'll only see Win10 OEM though, cause MS
> dictates it,
> while the black market for cracked software of every kind is huge.
>
--
There is one thing stronger than all the armies in the world,
and that's an idea whose time has come. [Victor Hugo]
@Timo, @Anyone,
I can't get a connection to the public symbol server, and my local
ntdll.pdb et.al
don't match the ones in my system, so the spec files I generate are
half-baked..
No parameters.
I can't figure out why SymSrv won't connect to
http://msdl.microsoft.com/download/symbols
(The malfunction does not seem to be isolated to CreateSpec, I see it in
VStudio 2oo8 and WinDbg too.)
SymSrvIsStore keeps failing with error 0x7E no matter what I do :-/
I'm on Win7SP1 x64 and SymSrv.dll and DbgHelp.dll are both 6.8.
Anybody got any clues to resolve this ?
Some kind of bitness issue (64<-->32) ?
Misconfigured sym server (65.55.10.11) ?
MS refuse to dish out symbols to north-east Thailand ?
The protocol is HTTP(s), so there shouldn't be blockage from my ISP.
My firewall don't trigger so it shouldn't be blocking either.
Googling for a solution yields zilch.. Only 1000 ways to set _NT_SYMBOL_PATH
and absolutely zero hints to resolve malfunctions :-/
A little help guys ?
Best Regards
// Neo