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
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.
But this discussion is a bit moot, isn't it? :)
Best Regards
// Neo
On 2016-05-23 15.53, Riccardo Paolo Bestetti <riccardo.kyogre(a)live.it>
wrote:
>
> Il 22/05/2016 23:14, Love Nystrom ha scritto:
>
>> Server 2oo3 might not be used in big corporations anymore, but I
>> think it's not uncommon to keep running it in small companies and
>> home servers (due to high licensing cost of Windows server versions).
> It /is/ pretty uncommon.
> I'm in contact with IT administrators from many small companies, at
> this point everyone has either (a) moved to Linux, (b) moved to some
> kind of cloud service or (c) upgraded to Server 2012.
> Even my school, which struggles to repaint walls, has done (c), lol.
> I don't know if it is any different in other parts of the world, but I
> suspect it is pretty much the same.
Server 2oo3 might not be used in big corporations anymore,
but I think it's not uncommon to keep running it in small companies
and home servers (due to high licensing cost of Windows server versions).
Anyway.. IMO there's nothing wrong in moving towards NT6x API-wise,
as long as we're not forced to re-architect the *core* of the system
(scheduler, et c). Paging the kernel would be a big mistake.
Best Regards
// Neo
On 2016-05-22 18.42, ros-dev-request(a)reactos.org wrote:
> They are not fucked up, since they legitimately don't care for the 3
> people out there still using 2k3.
> And we are not fucked up, we are only pushed to move to NT6+
>
> Timo
>
> Am 21.05.2016 um 06:12 schrieb Love Nystrom:
>> No, they are... Not we ;)
>> Same thing would happen if you try to run e.g. a Vista exe on NT4.
>>
>> // Neo
>>
>> On 2016-05-20 22.52, Javier Agustìn Fernàndez Arroyo
>> <elhoir(a)gmail.com> wrote:
>> > Subject: Re: [ros-dev] Pale Moon drops ReactOS support
>> > Date: 2016-05-20 22.51
>> >
>> > 4th scenario - App is actually "buggy" and doesnt check for any
>> export. We´re fucked up :P
--
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-05-23 04.21, "David Quintana (gigaherz)" <gigaherz(a)gmail.com> wrote:
> No one is suggesting paging the kernel. Stop being paranoid about that.
Ah.. Excellent.. That's such a relief to hear :)
> We are speaking about API interfaces for user apps and drivers.
> Whatever that implies, will be examined on a case by case basis. ;P
Good.. Then we are in full agreement :)
I'll sink my teeth into Timo's epic when I can.
I'm hoping there's some way we can avoid the mess SxS is causing on e.g
my Win7.
(I must have 10 versions of each RTL since 2oo5 installed by SxS ,
and dito with comctl32 versions, all with these obnoxiously long names.)
>
> On 22 May 2016 at 23:14, Love Nystrom <love.nystrom(a)gmail.com
> <mailto:love.nystrom@gmail.com>> wrote:
>
> Server 2oo3 might not be used in big corporations anymore,
> but I think it's not uncommon to keep running it in small companies
> and home servers (due to high licensing cost of Windows server
> versions).
>
> Anyway.. IMO there's nothing wrong in moving towards NT6x API-wise,
> as long as we're not forced to re-architect the *core* of the system
> (scheduler, et c). Paging the kernel would be a big mistake.
>
> Best Regards
> // Neo
>
On 2016-05-23 04.21, "David Quintana (gigaherz)" <gigaherz(a)gmail.com> wrote:
> I believe Riccardo referred to people developing apps for ReactOS/NT5,
> when they can write them for NT6 instead.
I guess I belong to a dying breed ;)
I always try to keep my API usage to the least common denominator
so that people may run my programs even on legacy systems.
I wish more programmers would do the same..
Using a newer API "just because it's there", when there is
*no real need* for it, is just plain rude to users IMHO.
(F.ex. using SHGetKnownFolderPath when SHGetFolderPath would suffice.)
Best Regards
// Neo
Oh.. I get it.. I thought you meant NT vs Unix.
I guess we may close the subject then :)
(I'm a usermode guy mostly, and I puke when I have to write for Linux,
since they don't have things like GDI, et cetera.)
Best Regards
// Neo
On 2016-05-23 04.21, ros-dev-request(a)reactos.org wrote:
> Il 22/05/2016 14:18, David Quintana (gigaherz) ha scritto:
>> I believe Riccardo referred to people developing apps for
>> ReactOS/NT5, when they can write them for NT6 instead.
> That's what I meant.
>
> I also agree with you, Neo, that NT, even version 5, is overall a
> better architecture than Linux.
> However, I agree with gigahertz that discussing this isn't all that
> useful: good != not obsolete.
>
> Best regards,
> --- /Riccardo Paolo Bestetti/
