[ros-dev] Off topic ;-)

timo.kreu...@web.de wrote: ... Ged Murphy wrote: ... Quotes should start with leading to make it more readable. Quoting signatures / footers is a waste of space. ros-dev-boun...@reactos.org wrote: Hi, sorry for OT, but http://learn.to/quote/ thanks From Wikipedia, the

Re: [ros-dev] Integration of ultracopier to reactOS

King InuYasha wrote: Except I doubt such functionality would ever get integrated for the simple reason that Windows doesn't have it. Only a few things ReactOS has that Windows didn't and it seems like those are disappearing soon (Read: virtual desktops). I beg to disagree. Just because

Re: [ros-dev] Integration of ultracopier to reactOS

Daniel Reimer wrote: There are many tools which try to be faster, especially if you copy several small files or on one hard driver with several partitions. I do believe you're thinking about xcopy. You didn't forget xcopy, did you ;-) It would perhaps be a good idea to integrate the concept of

Re: [ros-dev] Integration of ultracopier to reactOS

alpha_one_x86 wrote: On Monday 02 November 2009 05:38:01 Love Nystrom wrote: Well for starters, Windows Explorer aborts the entire copy list as soon as it hits any little snag, instead of continuing with the rest of the files in the list. This behavior is of course totally unacceptable

Re: [ros-dev] Integration of ultracopier to reactOS

As a result of this discussion I fetched the sources of both Ultra- and SuperCopier. I have made a very brief review of them and want to communicate my impression. While the basic idea of both are attractive, neither can be easily integrated in ROS as-is because of their dependencies, Ultra

Re: [ros-dev] Integration of ultracopier to reactOS

Wesley Parish wrote: Isn't the NT code base supposed to have multi-queued IO? to stop such problems? At least that was the NT-zealots' boast during the NT-vs-OS/2 days I'd say it's one thing what the system has ability to do do, and another thing entirely what Explorer does with it. Not

Re: [ros-dev] want to learn

rahul nagpal wrote: Hey, i can get th source code of reactos, but i can't understand the coding, your programmer who wrote these type of coding can also be refer any book/notes.You please tell me the name of that book, for which i can also take refrence for understanding the lower

Re: [ros-dev] A reimplementation of reactos' cache manager supporting alternate filesystems better (including ext2)

On Wed, Nov 11, 2009 at 4:32 AM, King InuYasha ngomp...@gmail.com wrote: Wouldn't that mean that we would need to support the extended attributes that Linux drivers support within ReactOS (like UNIX permissions, etc.)? They just need to be mapped to equivalent NT security attributes. On Tue,

Re: [ros-dev] A reimplementation of reactos' cache manager supporting alternate filesystems better (including ext2)

Brian wrote: i was always under the impression that having a swap partition meant that you did not have to hassle with the file system allowing for marginal performance boosts. That is generally true. In theory, APIs to access a swap partition can be implemented to use the disk device

Re: [ros-dev] A reimplementation of reactos' cache manager supporting alternate filesystems better (including ext2)

Alex Ionescu wrote: There would be no advantage to have a swap partition on Windows. There most certainly is, if that partition is on another physical drive! Two disks are faster than one ;-) Not to mention you could forget about crash dumps with a separate partition. Enlighten me..

Re: [ros-dev] A reimplementation of reactos' cache manager supporting alternate filesystems better (including ext2)

Ged Murphy wrote: What's next? Compiling drivers into the kernel? That's Linux I believe.. :-D What's wrong with installable file system drivers? ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] A reimplementation of reactos' cache manager supporting alternate filesystems better (including ext2)

Alex Ionescu wrote: 1) You would get the SAME ADVANTAGE by having the FILE on another physical drive! True enough. But I believe the issue was if there'd be a point in installing an IFS driver that would enable you to put the swap file on a swap partition.

Re: [ros-dev] A reimplementation of reactos' cache manager supporting alternate filesystems better (including ext2)

Alex Ionescu wrote: Not to mention you could forget about crash dumps with a separate partition. Alex.. I really don't know.. So please tell me why having the swap file on a swap partition precludes writing out a crash dump?? ___ Ros-dev

Re: [ros-dev] Microsoft PDC

Ged Murphy wrote: This starts on Monday. So nobody’s going?? Shocker I’ll have to drink on my own then. I wish I could.. but I can't even afford to visit my mom.. Have a good time, don't miss Mark Russinovitch. ___ Ros-dev mailing list

Re: [ros-dev] A reimplementation of reactos' cache manager supporting alternate filesystems better (including ext2)

On Fri, Nov 13, 2009 at 10:50 PM, Steven Edwards winehac...@gmail.comwrote: On Thu, Nov 12, 2009 at 8:32 PM, Steven Edwards winehac...@gmail.com wrote: On Thu, Nov 12, 2009 at 8:29 PM, Steven Edwards winehac...@gmail.com wrote: On Thu, Nov 12, 2009 at 11:46 AM, Alex Ionescu

Re: [ros-dev] A reimplementation of reactos' cache manager supporting alternate filesystems better (including ext2)

Ping? Nobody? So no idea why a separate dedicate virtual drive is recommended for the pagefile.sys? Also, if the swap volume is connected to it's own disk controller, of course it has an entire IO channel to itself which makes a big difference. But I don't see how it could apply to a virtual

Re: [ros-dev] A reimplementation of reactos' cache manager supporting alternate filesystems better (including ext2)

Ping? Nobody? So no idea why a separate dedicate virtual drive is recommended for the pagefile.sys? Perhaps the virtual disk has a virtual hardware cache that will be dedicated to swap if it don't need to do other work? ___ Ros-dev mailing list

Re: [ros-dev] rbuild msvc backend

Ged Murphy wrote: I’d imagine a lot of larger corporations still use 2005 as their development environments are more tightly controlled. I didn’t want to alienate these users. Anyway, everything below msvc8 is now falling foul to my delete key. I’m going to do the same with the entire

Re: [ros-dev] rbuild msvc backend

Colin Finck wrote: Love Nystrom wrote: I beg you to not remove the possibility to generate project and workspace files for Code::Blocks. From what I know, Code::Blocks can open .vcproj files generated by the MSVC backend. What VS version does it support ? 2oo3/2oo5/2oo8 ?? So

Re: [ros-dev] rbuild msvc backend

Zachary Gorden wrote: To specifically address the points raised, the fact that something is open source does not automatically elevate it in priority for this project. Quite a few of us work for companies that make heavy use of Visual Studio and appreciate all the functionality in it. The

Re: [ros-dev] rbuild msvc backend

Ged Murphy wrote: I've just tried running 'make cb' from both the cmd environment and the powershell environment and it doesn't do anything on either. It worked like a charm about two-three weeks ago. Maybe your environment got clobbered, or 'make cb' broke in the last few weeks. Assuming

Re: [ros-dev] [ros-diffs] [tkreuzer] 44508: updates EFLAGS definitions

Alex Ionescu wrote: There is a reason this set and names was chosen, please don't change them. It is for SDK compatibility. I see mostly additions that reflect Intel flag identifiers.. ergo, no major panic. None of the EFLAGS_xx show up in my public MS headers, which must mean that they

Re: [ros-dev] [ros-diffs] [tkreuzer] 44508: updates EFLAGS definitions

Alex Ionescu wrote: On 2009-12-11, at 10:10 AM, Love Nystrom wrote: lex Ionescu wrote: There is a reason this set and names was chosen, please don't change them. It is for SDK compatibility. see mostly additions that reflect Intel flag identifiers.. ergo, no major panic. I

Re: [ros-dev] ShellExecuteEx

Gregor Schneider grschnei...@gmail.com wrote: That made me think: what happens to this field if the ShellExecuteEx call succeeds and the flag SEE_MASK_NOCLOSEPROCESS is not set? Since this check was thought to forward the actual result of the execution i switched to a simpler and (in my eyes)

[ros-dev] James T - Aleksey B misunderstanding

ros-dev-requ...@reactos.org wrote: Look at this as a signal warning before the ship hits the reef... The ship has turn into the reef! No need to give false signals here, they often lead to loss of investment (example from stock trading area). Trying to make money from ReactOS

[ros-dev] DecompressBitmap et alumni

Gregor Schneider grschnei...@gmail.com wrote: Concerning using an internal format: let's assume we got three 8bpp surfaces (source, destination, pattern), which are quite big pending for a raster operation. You would convert these three to another format like 32bpp, process them and convert

Re: [ros-dev] Convert fat12/16 boot sector helper code to gas syntax.

Second that. If it ain't broke, don't bloody fix it. Best Regards L from Hell Alex Ionescu ion...@videotron.ca: This is retarded, GAS supports Intel syntax. Why did this require rewriting everything in ATT syntax and introducing bugs? And what's up with calling ATT syntax GAS Syntax. I wonder

Re: [ros-dev] Usetup

Hi, What You say makes sense of course. I can't find time to dig into the code, but it sounds like you acted correctly. We can of course improve the setup behavior as time goes and we learn how to do it right with various boot managers, no need to take after Microsoft here, but there will

Re: [ros-dev] MP/UP HAL issues

-- Forwarded message -- From: Timo Kreuzer timo.kreu...@web.de\ [abbreviated] I'm against wasting precious compile time for an MP hal that doesn't even work. And I would actually like to have the kernel being compiled the same way. I bet the performance improvements of

Re: [ros-dev] MP/UP HAL issues

-- Forwarded message -- From: Timo Kreuzer timo.kreu...@web.de Subject: Re: [ros-dev] MP/UP HAL issues Am 26.03.2011 11:45, schrieb Love Nystrom: To me, performance is *everything* .. I gladly spend a *week* to gain significant performance, especially if it also makes

Re: [ros-dev] Meeting on Thursday

Hi Colin, Please put me on the list as well, would You? Because of a real shitty RL situation I haven't been able to contribute the way I would like to, but believe me when I say I am committed to the success of the ReactOS project. I guess we all have our own reasons.. Mine is by and large to

[ros-dev] Brothers In Arms

get better soon mate. On Sun, 03 Apr 2011 16:55:38 +1000, Love Nystrom love.nyst...@gmail.com wrote: As a side note, my shitty RL situation is largely responsible for my occasional tantrums, for which I am truly sorry. Taking my RL frustrations out on my Brothers In Arms is *unfair*. I

Re: [ros-dev] IFS wrapper project proposal draft

Hi Bryan, Just like Aleksey, I would welcome an effort to simplify IFS implementation. Seen as NTFS is (and always will be?) not well documented, I've been thinking about supporting some alternative, OSS, journaling file system in ReactOS, e.g. ReiserFS, to allow us to provide the (relative)

Re: [ros-dev] IFS wrapper project proposal draft

supports things like ACLs too. On Tue, 05 Apr 2011 17:56:40 +1000, Love Nystrom love.nyst...@gmail.com wrote: Hi Bryan, Just like Aleksey, I would welcome an effort to simplify IFS implementation. Seen as NTFS is (and always will be?) not well documented, I've been thinking about

Re: [ros-dev] Windows Internals 5th Edition

really working on a 6.x kernel now, I need to know where we transcended from 5.x so I can archive a private branch of 5.x at it's last known version. WBR // Love On Tue, Apr 5, 2011 at 10:33 AM, Love Nystrom love.nyst...@gmail.comwrote: Hi James, Yes, most interesting, but isn't it a little

Re: [ros-dev] IFS wrapper project proposal draft

both better than all that ext1/ext2/ext3/ext4/extπ/whatever gibberish. The biggest problem is (and it has actually happened to me before) these guys can run out of inodes and what not. On Tue, 05 Apr 2011 19:40:09 +1000, Love Nystrom love.nyst...@gmail.com wrote: Hi Adam, Thanks

Re: [ros-dev] [EVENTVWR/EVENTLOG] Fix a double off-by-one bug

Hi Gabriel, Eric, Isn't the real issue why LogFile-Header.CurrentRecordNumber is off by one ? If that is found and fixed, this patch will make the error re-emerge as an off by -1. And if CurrentRecordNumber is actually used as the next *pending* record number, the identifier is somewhat

Re: [ros-dev] [EVENTVWR/EVENTLOG] Fix a double off-by-one bug

Hi Eric, Sounds like you got it licked, the right way. Good job ! Best Regards L. 2011/5/6 ros-dev-requ...@reactos.org From: Eric Kohl eric.k...@t-online.de To: ReactOS Development List ros-dev@reactos.org Date: Thu, 05 May 2011 22:41:24 +0200 Subject: Re: [ros-dev] [EVENTVWR/EVENTLOG] Fix

Re: [ros-dev] New harddisk geometry

Hi People, I'm back after my ordeal in Europe and finally got an inet line.. But now I've over 300 mails from the list to wade through.. Ugh. It's gonna take some time to get up to speed. Hi Eric, That's all fine, it's just an educated choice of disk parameters as I see it. But anyway, all

Re: [ros-dev] Invisible dialogs

Filed as #6751. It's a Z-order problem .. Might be easy to fix (for you). Best Regards // Love ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] COM Monitor

Hi, I wrote a test/debug util (COM monitor) for logging ReactOS dbg/bt messages, and wonder if it will be better to submit it as a bugzilla patch, or start a sourceforge or codeproject page for it ? Most of you probably have other utils, but ComMon is quite handy with it's auto enumerated COM

Re: [ros-dev] COM Monitor

Happy New Year to you all. Holidays fade away and I celebrate by submitting this tool. Patches are filed as Bugzilla #6802 (not a bug duh.. ;) http://www.reactos.org/bugzilla/show_bug.cgi?id=6802 ComMon is a simple COM port monitor utility to capture debug strings. It is meant to be used with

Re: [ros-dev] EPIC: ReactOS@Samsung Galaxy S III mini

@Timo Yes of course.. It was a fleeting idea it would be cute to run on a computer 5x10x1 cm. ;-) I didn't realize the ARM branch was in poor condition though. But it stands to reason.. Porting Intel assembly to ARM assembly and considering all the archiectural differences is/would be a

Re: [ros-dev] RtlUlonglongByteSwap

@Timo, @Thomas, @Ged Byte order swappers should always be fastcall for perfomance reasons. They have no need for the benefits of the cdecl call convention. Using cdecl in this case would make the binary code pitifully slow. Think about it for a bit.. Some pseudocode show what I mean:

Re: [ros-dev] RtlUlonglongByteSwap (Thomas Faber)

function anyway. This is just about the export (or rather, importing it). On 2014-10-17 00:24, Love Nystrom wrote: @Timo, @Thomas, @Ged Byte order swappers should always be fastcall for perfomance reasons. They have no need for the benefits of the cdecl call convention. Using cdecl in this case

Re: [ros-dev] [hbelusca] 64773: [FAST486]: Do not call RtlCopyMemory for copying few bytes (2 and 4).

@Hermes, @Alex, May I suggest using my LITERAL macro for that sort of thing..? The explicit leftcast blurb is not exactly best for readability, and a call overhead for such a puny transfer is bad performance. #define LITERAL( type,var ) (*(type*)var) // Omnipotent cast Then

Re: [ros-dev] [ros-diffs] [akhaldi] 65249: [SHELL32] * bool = BOOL.

@Timo, @Amine A BOOL should merely distinguish between zero and non-zero, so extending an 8 bit bool (which I favor) to a 32 bit BOOL should always produce a valid result, even in the example case. If Foo becomes true after the mask test, it is expressed as non-zero, which persist through the

Re: [ros-dev] [ros-diffs] [akhaldi] 65249: [SHELL32] * bool = BOOL.

. More importantly, as Timo originally stated, and I illuminated above, changing bool to BOOL can potentially introduce code malfunctions, which I'm sure none of us would like. Best Regards // Love Am 09.11.2014 17:28, schrieb Love Nystrom: @Timo, @Amine A BOOL should merely distinguish

[ros-dev] Replacing unsafe TRUE comparisons (Following Re: bool = BOOL)

Grep'ing for [ \t]*==[ \t]*TRUE and [ \t]*!=[ \t]*TRUE revealed some 400 matches.. That's *400 potential malfunctions begging to happen*, as previously concluded. If you *must*, for some obscure reason, code an explicit truth-value comparison, for God's sake make it (boolVal != FALSE) or

Re: [ros-dev] Replacing unsafe TRUE comparisons (Following Re: bool = BOOL)

2014 10:48, Love Nystrom love.nyst...@gmail.com mailto:love.nyst...@gmail.com wrote: Grep'ing for [ \t]*==[ \t]*TRUE and [ \t]*!=[ \t]*TRUE revealed some 400 matches.. That's *400 potential malfunctions begging to happen*, as previously concluded. If you *must*, for some obscure

[ros-dev] ReactOS/Wine patches.

@Sylvain, It occurred to me that since we have a lot of Wine code in ReactOS, there will often be cases where ReactOS patches target Wine code. Instead of just rejecting those patches, which is likely to make them never see the light of day, the ReactOS programmers who maintain our Wine code

Re: [ros-dev] Replacing unsafe TRUE comparisons (Following Re: bool = BOOL)

OR boolRm, boolRm instead). I expect some people will use the former. Personally I much prefer the latter. Best Regards // Love On Wed, Nov 12, 2014 at 10:03 PM, Love Nystrom love.nyst...@gmail.com mailto:love.nyst...@gmail.com wrote: Thanks.. Well, someone had to do it, and I had

Re: [ros-dev] Replacing unsafe TRUE comparisons (Following Re: bool = BOOL)

On 2014-11-16 05.22, Timo Kreuzer wrote: Am 14.11.2014 15:32, schrieb Love Nystrom: On 2014-11-14 00.41, Alex Ionescu wrote: I would much rather see if (f != FALSE) instead of if ( f ). Well, it's certainly a valid option, and C++ compilers seem to generate [abbrev] if (f != FALSE

Re: [ros-dev] ReactOS/Wine patches. BOOLs and the art of motorcycle repair.

.. The problem exists if we assign value obtained from bit operators e.g. BOOLEAN HasFlag = a SOME_FLAG Best Regards // Love *De :* Love Nystrom love.nyst...@gmail.com *À :* ReactOS Development List ros-dev@reactos.org *Envoyé

Re: [ros-dev] Replacing unsafe TRUE comparisons (Following Re: bool = BOOL)

On 2014-11-21 04.00, Timo Kreuzer wrote: Am 20.11.2014 14:18, schrieb Love Nystrom: Well... Actually not exactly the same.. ;) if (f != FALSE) requires an explicit comparison with a second operand, No, it does not. It requries the compiler to generate code that executes the following

Re: [ros-dev] Replacing unsafe TRUE comparisons (Following Re: bool = BOOL)

On 2014-11-22 18.47, Timo Kreuzer wrote: Am 22.11.2014 11:39, schrieb Love Nystrom: On 2014-11-21 04.00, Timo Kreuzer wrote: Am 20.11.2014 14:18, schrieb Love Nystrom: Well... Actually not exactly the same.. ;) if (f != FALSE) requires an explicit comparison with a second operand

Re: [ros-dev] [CORE-11291] Create Windows 7 spec files for core DLLs

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

Re: [ros-dev] [BOOTLIB]: Cleanup, less magic.

On 2016-01-24 19.00, ros-dev-requ...@reactos.org wrote: +if (Length != Length) Now that's what we call an unlikely condition :-D The CPU branch predictor will have no problem. Magic indeed.. Hope it's not indicative.. L. ___ Ros-dev mailing

[ros-dev] ReactOS versioning

Excuse my extremely late thoughts on this issue.. Perhaps they're moot already. Regarding pt.3 in Timo's very succinct post (a year ago), I see a possibility in a "proxy" scheme as follows.. The "standard" dlls knows the 6.x APIS, while implementing the "base" 5.2 functions, and forward newer

Re: [ros-dev] Pale Moon drops ReactOS support

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

Re: [ros-dev] 4th scenario

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 wrote: > Subject: Re: [ros-dev] Pale Moon drops ReactOS support > Date: 2016-05-20 22.51 > > 4th scenario - App is

Re: [ros-dev] Ros-dev Digest, Vol 141, Issue 21

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, ros-dev-requ...@reactos.org wrote: Subject: Re: [ros-dev] Pale Moon drops ReactOS support From: Javier Agustìn Fernàndez Arroyo Date: 2016-05-20 22.51

Re: [ros-dev] 4th scenario

y SxS , and dito with comctl32 versions, all with these obnoxiously long names.) On 22 May 2016 at 23:14, Love Nystrom <love.nyst...@gmail.com <mailto:love.nyst...@gmail.com>> wrote: Server 2oo3 might not be used in big corporations anymore, but I think it's not uncommon to keep r

Re: [ros-dev] Ros-dev Digest, Vol 141, Issue 24

On 2016-05-23 04.21, "David Quintana (gigaherz)" 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

Re: [ros-dev] ReactOS versioning

Ah.. Ok, I'll peruse it soon as I get a chance. Best Regards // Neo On 2016-05-22 18.42, Timo Kreuzer wrote: I created an epic with a few subtasks regarding ReactOS versioning: https://jira.reactos.org/browse/CORE-11288 Timo

Re: [ros-dev] 4th scenario

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 <elh...@gmail.com> wrote: > Su

Re: [ros-dev] Actually a GOOD architecture.

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-requ...@reactos.org wrote: Il

[ros-dev] Actually a GOOD architecture.

On 2016-05-18 02.10, Riccardo Paolo Bestetti wrote: It's not like developers are gonna pick up again an old (and, honestly, bad!) architecture just because it is made free, when *here and now* we already have a better alternative. Bad architecture ? Compared to

Re: [ros-dev] 4th scenario

, Riccardo Paolo Bestetti <riccardo.kyo...@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

[ros-dev] rosapps CreateSpec (Fw: ReactOS versioning)

@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

[ros-dev] [CORE-11291] Create Windows 7 spec files for core DLLs

@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

Re: [ros-dev] rosapps CreateSpec (Fw: ReactOS versioning)

Forget this issue... It remains, but I've moved on. Thanks anyway. // Neo On 2016-05-24 19.00, Love Nystrom <love.nyst...@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

Re: [ros-dev] [ros-diffs] [gadamopoulos] 72398: [SHELL32] - Fail to delete any file if one is invalid. - Patch by andy-123 CORE-9959

On 2016-08-28 19.00, ros-dev-requ...@reactos.org wrote: Subject: Re: [ros-dev] [ros-diffs] [gadamopoulos] 72398: [SHELL32] - Fail to delete any file if one is invalid. - Patch by andy-123 CORE-9959 From: Thomas Faber Date: 2016-08-28 15.42 To: ros-dev@reactos.org

Re: [ros-dev] [ros-diffs] [dchapyshev] 72787: [NTOSKRNL] Remove unneeded sanity checks

I don't want to trod on anyone's tail, but assigning _Thread = KeGetCurrentThread(), and then asserting _Thread == KeGetCurrentThread() on the next line does seem excessively myopic, yes ? Unless you expect KeGetCurrentThread() to be fubar and return rand(), in which case the assert should be

Re: [ros-dev] Ros-dev Digest, Vol 145, Issue 16

Agreed.. When the assignment and assert are separated by a call of X distance, the assert is certainly warranted. Just not as it stands in ke_x.h Perhaps you could factorize as suggested, Dmitri? Best regards L. On 2016-09-26 10.28, ros-dev-requ...@reactos.org wrote: Rationale is simple:

Re: [ros-dev] [ros-diffs] [dchapyshev] 72787: [NTOSKRNL] Remove unneeded sanity checks

Agreed.. When the assignment and assert are separated by a call of X distance, the assert is certainly warranted. Just not as it stands in ke_x.h Perhaps you could factorize as suggested, Dmitri? Best regards L. On 2016-09-26 10.28, ros-dev-requ...@reactos.org wrote: Rationale is simple:

Re: [ros-dev] KD trace during ROS installation

Good afternoon gentlemen... Seems the list server has gone on a vacation. Still waiting on the digest where Hermes added to Thomas answer.. Anyway Hermes pasted his answer to my mailbox (thank you) and so.. One more step is required in addition to the answers from Thomas and Hermes.. A small

[ros-dev] KD trace during ROS installation

Good afternoon gentlemen.. Can anyone tell me at what point during ROS installation KD becomes operative? And if there is a way to change the default KD COM port from COM1 to COM2 in order to trace KD output during installation? (I run my ROS tests on VMware with a com0com connection from

Re: [ros-dev] KD trace during ROS installation

e able to simply add an Options=... line to the [Setup] section in boot/bootdata/bootcd.ini to modify the setup's freeldr options. That file becomes freeldr.ini in the root dir of the BootCD. On 2016-09-27 12:21, Love Nystrom wrote: >Good afternoon gentlemen.. > >Can anyone tell me at wh