[NewIdea]A new way to push ReactOS Development [NewIdea]

Here you can discuss ReactOS related topics.

Moderator: Moderator Team

DOSGuy
Posts: 582
Joined: Wed Sep 14, 2011 5:55 pm
Contact:

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by DOSGuy »

clancg2003 wrote:How about we get as many community members to donate 15€ each month. That's not a lot at all, and if we can get a couple hundred people to do this (I know there's at least 500 people in the community) we could definitely get a few developers to dedicate more time to the project.
I just don't think that's realistic. A Windows license is $140, so why would anyone pay $180 per year for a "free" Windows clone? I absolutely believe that there is enough goodwill in the community that people will donate some amount of money to help ReactOS develop into a viable alternative to Windows, but I think only a small, hardcore minority would donate more to the ReactOS project than it would cost to just stick with Microsoft. If you could get a couple hundred people to donate $15 even once, that would be a major accomplishment.
Today entirely the maniac there is no excuse with the article. Get free DOS, Windows and OS/2 games at RGB Classic Games.

clancg2003
Posts: 29
Joined: Sat Apr 10, 2010 3:24 am

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by clancg2003 »

Bblaauw wrote:* requesting features, rather than helping general progress.
This was already tried before with the community funded ideas; It didn't go so well.
Bblaauw wrote:Donating for getting features implemented is pleasant, donating so developers get rid of bugs isn't. Perhaps wait till 0.4.0 is out?
I have to disagree with you completely there. Fixing bugs is WAY more important than adding on new features. Adding new features while leaving other parts bugged is a terrible idea. Not only will it lead to more bugs, but the older ones will be even harder to find and fix. You can't build a skyscraper on top of a defective base; computer programs are just like this, if the "base" isn't working you can't go and add on new features. In the computer world, fixing bugs always comes before adding new features.

Bblaauw
Posts: 149
Joined: Mon Aug 03, 2009 12:59 am

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by Bblaauw »

clancg2003 wrote: I have to disagree with you completely there. Fixing bugs is WAY more important than adding on new features. Adding new features while leaving other parts bugged is a terrible idea. Not only will it lead to more bugs, but the older ones will be even harder to find and fix. You can't build a skyscraper on top of a defective base; computer programs are just like this, if the "base" isn't working you can't go and add on new features. In the computer world, fixing bugs always comes before adding new features.
I think we actually agree here. My point in bringing up 0.4.0 is a bit exaggerated, but features should only be implemented once bugs have been resolved. As I only want to donate for features, not for sorting out bugs, I'd wait with donating till these obvious bugs (with probably a not so obvious solution) are gone/resolved/fixed. Fix the foundation and people might see things get worthwile.

All bugs mentioned before were also already reported (be it by SomeGuy, Vicmarcal, me or someone else). I don't expect someone to magically give priority to these reports, it can wait. But meanwhile I consider it a personal showstopper for even wanting to donate. No (polished) solid foundation, no additional funds. I do recognise ReactOS's (code) quality, but it's still missing a tiny few things I'd like to be present.

That's also the reason I mentioned a user blog here. Forum topics are usually concise. My end goal for example has always been running World of Warcraft on top of ReactOS. No DirectX (be it an implementation from ROS, WINE or just an illegal install of DirectX which by coincidence would work somehow) means OpenGL. OpenGL means 3D video driver has to install. Hardware/vendor video driver installation in ReactOS..unlikely to work still. Besides, modern systems depend on USB stacks bigtime.

What I'd donate for (say, 50 euro per subject, provided the financial system isn't collapsing any time soon.. ) :
* console implementation (like Windows Server Core, or ReactOS before it had GUI) if GUI is too heavy for the machine. Not a CMD window on top of explorer, but CMD itself. Let's call it 32bit DOS :oops:
* implementation of WinVBlock driver (written by Shao Miller). Boot (and mount) a ReactOS LiveCD/BootCD ISO file using Syslinux/Memdisk and continue to work. If PartedMagic (protected mode Linux) can do it..
* implementation of Shared Folders in VMware. There's a GPL3 (yeah..I know..) DOS implementation of it at http://sourceforge.net/projects/vmsmount/ . GPL2 release might be negotiable.
* being able to install/boot/run from USB disks.

I'll not even start about the long time between 0.3.13 and upcoming 0.3.14 (hi daily trunk downloads), RosBE releases, CMAKE switch etc. All in due time, followed by showing progress followed by being impressed followed by donating.

FlyingIsFun1217
Posts: 475
Joined: Sun Jun 10, 2007 3:56 am

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by FlyingIsFun1217 »

Bblaauw wrote:My end goal for example has always been running World of Warcraft on top of ReactOS. No DirectX (be it an implementation from ROS, WINE or just an illegal install of DirectX which by coincidence would work somehow) means OpenGL. OpenGL means 3D video driver has to install. Hardware/vendor video driver installation in ReactOS..unlikely to work still. Besides, modern systems depend on USB stacks bigtime.

What I'd donate for (say, 50 euro per subject, provided the financial system isn't collapsing any time soon.. ) :
* console implementation
* implementation of WinVBlock driver (written by Shao Miller). Boot (and mount) a ReactOS LiveCD/BootCD ISO file using Syslinux/Memdisk and continue to work.
* implementation of Shared Folders in VMware.
* being able to install/boot/run from USB disks.
I'm confused. You want to just have Windows with DirectX? What about people who only want it to check email and work on Word documents for school?

And why is it important to have SYSLINUX instead of the default bootloader? This isn't me being rude, I'm just curious.

Personally, I love the track they're taking in development so far. They're building and refining the base, whilst working on the GUI and compatibility elements (especially with hardware), and once the stuff that most people use is done with (or at least working), they'll move onto the other aspects like DirectX. One thing I would love to donate for though is fixing of blocker bugs. Darn you mshtml.dll!

FlyingIsFun1217

clancg2003
Posts: 29
Joined: Sat Apr 10, 2010 3:24 am

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by clancg2003 »

bblaauw wrote:I think we actually agree here. My point in bringing up 0.4.0 is a bit exaggerated, but features should only be implemented once bugs have been resolved. As I only want to donate for features, not for sorting out bugs, I'd wait with donating till these obvious bugs (with probably a not so obvious solution) are gone/resolved/fixed. Fix the foundation and people might see things get worthwile.
I agree with you actually, from the user's pov features are the most important thing. However, the stark reality is that a lot of the cool features that users would like right now just can't be implemented yet, because other parts of the operating system that they rely on are bugged or incomplete. Like it would be great to have full NTFS support for ReactOS, but it simply can't be done right now. Why not just let the developers dedicate their time to what's most important for the OS right now?

Bblaauw
Posts: 149
Joined: Mon Aug 03, 2009 12:59 am

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by Bblaauw »

FlyingIsFun1217 wrote:I'm confused. You want to just have Windows with DirectX? What about people who only want it to check email and work on Word documents for school?
That's fine also ofcourse, I'm just aiming for a slightly more complex goal for myself, including features in ReactOS that WindowsXP/7 doesn't have at all (or not by default) like booting from USB or memory
And why is it important to have SYSLINUX instead of the default bootloader? This isn't me being rude, I'm just curious.
It's an addition. If FreeLDR can do it by itself, also fine. The idea is:
"syslinux -> memdisk -> livecd.iso -> freeldr -> winvblock -> ReactOS live environment running from RAM". It solves booting BootCD/LiveCD from unsupported hardware (USB flash disk or USB CD Drive) also because you're mounting data from memory instead of from disk. MEMDISK requires GRUB or Syslinux. It simply copies entire ISO to RAM then chain-boots it, all in 16bit mode still. ReactOS will likely choke if not using WinVblock (unless own drivers) due to this memdisk-copied data not being found in protected mode.
Personally, I love the track they're taking in development so far. They're building and refining the base, whilst working on the GUI and compatibility elements (especially with hardware), and once the stuff that most people use is done with (or at least working), they'll move onto the other aspects like DirectX. One thing I would love to donate for though is fixing of blocker bugs. Darn you mshtml.dll!

I like their development process also. Being able to have time to develop usually requires ignoring mailinglists, forums etc though :)
That usually ends up with end-users being left in the cold a bit. That along with the absolute lack of hard performance metrics/requirements so things can be considered efficient or a regression.
One such example I've been hammering on is bootCD part being able to copy files in a reasonable time (say, 5mins) with a reasonable amount amount of memory (say 32MB). If that's not possible there's a huge memory leak somewhere.

As for me wanting to run WoW on ReactOS, I'm easily satisfied: ReactOS in VMware, VMware 3d-accelerated drivers working, Furmark working (OpenGL), then ReactOS tried on hardware, followed by Nvidia/AMD graphics drivers working, then Furmark working, then WoW working with a bit of luck. All in due time. What I think we should do is get complete logs of each phase and file a bug at each error listed. Some have remained for ages (like QEMU screen log starting with 0 MB or FreeLDR lacking 1MB reported).

FlyingIsFun1217
Posts: 475
Joined: Sun Jun 10, 2007 3:56 am

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by FlyingIsFun1217 »

Bblaauw wrote:What I think we should do is get complete logs of each phase and file a bug at each error listed. Some have remained for ages (like QEMU screen log starting with 0 MB or FreeLDR lacking 1MB reported).
Definitely agree! Hopefully there will be more synergy between users and developers, which in turn hopefully expands the base of both.

FlyingIsFun1217

Bblaauw
Posts: 149
Joined: Mon Aug 03, 2009 12:59 am

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by Bblaauw »

FlyingIsFun1217 wrote:Definitely agree! Hopefully there will be more synergy between users and developers, which in turn hopefully expands the base of both.
test, I'll edit this if it gets one big mess.
Hm it actually does get one big mess. Not sure how to keep this shortened like in code blocks yet allow the bb-code to be parsed.

Code: Select all

[list]
line + bug +++++++++++++++++++++++++++++++ SVN-file +++++++++ line +++ message
=======================================================================================================================================================================================================================================
001 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/kd/kdio.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\kd\kdio.c:326[/url]) -----------------------------------------------------
002 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/kd/kdio.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\kd\kdio.c:327[/url]) ReactOS 0.4-SVN (Build 20111207-r54606)
003 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/kd/kdio.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\kd\kdio.c:329[/url]) 1 System Processor [0 MB Memory]
004 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/kd/kdio.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\kd\kdio.c:330[/url]) Command Line: /NOGUIBOOT /DEBUGPORT=COM1 /FIRSTCHANCE
005 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/kd/kdio.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\kd\kdio.c:334[/url]) ARC Paths: multi(0)disk(0)cdrom(96) \ multi(0)disk(0)cdrom(96) \reactos\
006 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/cpu.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\ke\i386\cpu.c:494[/url]) Supported CPU features :  KF_RDTSC KF_CR4 KF_CMOV KF_GLOBAL_PAGE KF_LARGE_PAGE  KF_CMPXCHG8B KF_MMX  KF_PAT KF_FXSR KF_FAST_SYSCALL KF_XMMI   KF_XMMI64    
007 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/cpu.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\ke\i386\cpu.c:801[/url]) Prefetch Cache: 64 bytes	L2 Cache: 2097152 bytes	L2 Cache Line: 64 bytes	L2 Cache Associativity: 8
008 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/ARM3/mminit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\ARM3\mminit.c:1316[/url]) HAL I/O Mapping at FFFE0000 is unsafe
009 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/mminit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\mminit.c:243[/url])           0x80000000 - 0x80C00000	Boot Loaded Image
010 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/mminit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\mminit.c:247[/url])           0xB0000000 - 0xB00C1000	PFN Database
011 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/mminit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\mminit.c:251[/url])           0xB00C1000 - 0xB02C1000	ARM³ Non Paged Pool
012 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/mminit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\mminit.c:255[/url])           0xBC000000 - 0xBD000000	System View Space
013 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/mminit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\mminit.c:259[/url])           0xBD000000 - 0xC0000000	Session Space
014 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/mminit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\mminit.c:262[/url])           0xC0000000 - 0xC0300000	Page Tables
015 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/mminit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\mminit.c:265[/url])           0xC0300000 - 0xC0400000	Page Directories
016 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/mminit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\mminit.c:268[/url])           0xC0400000 - 0xC0800000	Hyperspace
017 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/mminit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\mminit.c:272[/url])           0xE1000000 - 0xE6C00000	ARM³ Paged Pool
018 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/mminit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\mminit.c:275[/url])           0xF7800000 - 0xFCFFD000	System PTE Space
019 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/mminit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\mminit.c:278[/url])           0xFCFFD000 - 0xFFBE0000	Non Paged Pool Expansion PTE Space
020 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/hal/halx86/legacy/bussupp.c?view=markup]P:\Trunk_slave\x86_CMake\build\hal\halx86\legacy\bussupp.c:620[/url]) Found parent bus (indicating PCI Bridge). PCI devices may fail!
021
022 [bug]0000[/bug] ====== PCI BUS HARDWARE DETECTION =======
023
024 [bug]0000[/bug] 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [[url=http://pci-ids.ucw.cz/read/PC?restrict=]8086:1237[/url]] (rev 02)
025 [bug]0000[/bug] 	Subsystem: [url=http://qemu.weilnetz.de/]Qemu[/url] virtual machine [1af4:1100]
026 [bug]0000[/bug] 	Flags: latency 0
027
028 [bug]0000[/bug] 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Trito [[url=http://pciids.sourceforge.net/]8086:7000[/url]] (rev 00)
029 [bug]0000[/bug] 	Subsystem: [url=http://lassauge.free.fr/qemu/]Qemu[/url] virtual machine [1af4:1100]
030 [bug]0000[/bug] 	Flags: medium devsel, latency 0
031
032 [bug]0000[/bug] 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Trito [8086:7010] (rev 00)
033 [bug]0000[/bug] 	Subsystem: [url=http://wiki.qemu.org/Download]Qemu[/url] virtual machine [1af4:1100]
034 [bug]0000[/bug] 	Flags: medium devsel, latency 0
035 [bug]0000[/bug] 	I/O ports at c120 [size=32]
036
037 [bug]0000[/bug] 00:01.2 USB Controller [0c03]: Intel Corporation 82371SB PIIX3 USB [Natoma/Trito [8086:7020] (rev 01)
038 [bug]0000[/bug] 	Subsystem: [url=http://en.wikipedia.org/wiki/Qemu]Qemu[/url] virtual machine [1af4:1100]
039 [bug]0000[/bug] 	Flags: bus master, latency 0, IRQ 11
040 [bug]0000[/bug] 	I/O ports at c100 [size=256]
041 [bug]0000[/bug] 	Device is using IRQ 11! ISA Cards using that IRQ may fail!
042 [bug]0000[/bug] 	Device is an Intel UHCI (USB) Controller. Turn off Legacy USB in your BIOS!
043
044 [bug]0000[/bug] 00:01.3 Secondary bus towards host CPU [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03)
045 [bug]0000[/bug] 	Subsystem: [url=http://qemu.weilnetz.de/qemu-doc.html]Qemu[/url] virtual machine [1af4:1100]
046 [bug]0000[/bug] 	Flags: medium devsel, latency 0, IRQ 09
047 [bug]0000[/bug] 	Device is using IRQ 9! ISA Cards using that IRQ may fail!
048
049 [bug]0000[/bug] 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8] (rev 00)
050 [bug]0000[/bug] 	Subsystem: [url=http://lists.nongnu.org/archive/html/qemu-devel/]Qemu[/url] virtual machine [1af4:1100]
051 [bug]0000[/bug] 	Flags: latency 0
052 [bug]0000[/bug] 	Memory at fc000000 (32-bit, prefetchable) [size=64M]
053 [bug]0000[/bug] 	Memory at febf0000 (32-bit, non-prefetchable) [size=64K]
054
055 [bug]0000[/bug] 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8029(AS) [10ec:8029] (rev 00)
056 [bug]0000[/bug] 	Subsystem: [url=http://lists.nongnu.org/archive/html/qemu-discuss/]Qemu[/url] virtual machine [1af4:1100]
057 [bug]0000[/bug] 	Flags: latency 0, IRQ 11
058 [bug]0000[/bug] 	I/O ports at c000 [size=16K]
059 [bug]0000[/bug] 	Device is using IRQ 11! ISA Cards using that IRQ may fail!
060
061 [bug]0000[/bug] ====== PCI BUS DETECTION COMPLETE =======
062 
063 [bug]0000[/bug] PC Compatible Eisa/Isa HAL Detected
064 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/pnpmgr/pnpinit.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\pnpmgr\pnpinit.c:404[/url]) Need to build DACL
065 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/pnpmgr/pnpmgr.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\pnpmgr\pnpmgr.c:2817[/url]) ZwOpenKey(\Registry\Machine\SYSTEM\CURRENTCONTROLSET\Control\Pnp) failed with status 0xc0000034
066 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/pnpmgr/pnpmgr.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\pnpmgr\pnpmgr.c:2820[/url]) Firmware mapper is enabled
067 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/pnpmgr/pnpreport.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\pnpmgr\pnpreport.c:346[/url]) Reported device: DETECTEDInternal\PCI_HAL (Root\PCI_HAL\0)
077 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/iorsrce.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\iorsrce.c:882[/url]) IoReportResourceUsage is halfplemented!
078 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/iorsrce.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\iorsrce.c:882[/url]) IoReportResourceUsage is halfplemented!
079 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/driver.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\driver.c:1558[/url]) '\Driver\buslogic' initialization failed, status (0xc00000c0)
080 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/driver.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\driver.c:1558[/url]) '\Driver\floppy' initialization failed, status (0xc000000e)
081 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/arcname.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\arcname.c:338[/url]) Boot device found
082 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/file.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\file.c:421[/url]) Using IopParseDevice() hack. Requested invalid attributes: 1
083 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/fstub/disksup.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\fstub\disksup.c:255[/url]) ZwOpenSymbolicLinkObject failed for \ArcName\multi(0)disk(0)rdisk(1), status=c0000034
084 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/fstub/disksup.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\fstub\disksup.c:255[/url]) ZwOpenSymbolicLinkObject failed for \ArcName\multi(0)disk(0)rdisk(1), status=c0000034
085 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ex/init.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\ex\init.c:1918[/url]) Free non-cache pages: 6f14
086 [bug]0000[/bug] WARNING:  RtlSetUnhandledExceptionFilter at [url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/rtl/exception.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\rtl\exception.c:186[/url] is UNIMPLEMENTED!
087 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/rtl/path.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\rtl\path.c:1005[/url]) don't keep the directory handle open on removable media
088 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ps/query.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\ps\query.c:1268[/url]) Unsupported or unimplemented: 22
089 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/base/setup/usetup/interface/devinst.c?view=markup]P:\Trunk_slave\x86_CMake\build\base\setup\usetup\interface\devinst.c:82[/url]) Using driver 'pci.sys' for device 'Root\*PNP0A03\0000'
090 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/ARM3/sysldr.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\ARM3\sysldr.c:174[/url]) Loading: \SystemRoot\system32\drivers\pci.sys at FCDA5000 with 11 pages
091 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/bus/pci/fdo.c?view=markup]P:\Trunk_slave\x86_CMake\build\drivers\bus\pci\fdo.c:586[/url]) Unknown IOCTL 0x9
092 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/bus/pci/fdo.c?view=markup]P:\Trunk_slave\x86_CMake\build\drivers\bus\pci\fdo.c:586[/url]) Unknown IOCTL 0x14
093 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/pnpmgr/pnproot.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\pnpmgr\pnproot.c:1137[/url]) IRP_MJ_PNP / Unknown minor function 0x14
094 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/pnpmgr/pnpmgr.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\pnpmgr\pnpmgr.c:3662[/url]) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
095 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/base/setup/usetup/interface/devinst.c?view=markup]P:\Trunk_slave\x86_CMake\build\base\setup\usetup\interface\devinst.c:82[/url]) Using driver 'pci.sys' for device 'PCI_HAL\PNP0A03\0'
096 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/hal/halx86/legacy/halpnpdd.c?view=markup]P:\Trunk_slave\x86_CMake\build\hal\halx86\legacy\halpnpdd.c:710[/url]) Start device received
097 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/bus/pci/fdo.c?view=markup]P:\Trunk_slave\x86_CMake\build\drivers\bus\pci\fdo.c:586[/url]) Unknown IOCTL 0x9
098 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/bus/pci/fdo.c?view=markup]P:\Trunk_slave\x86_CMake\build\drivers\bus\pci\fdo.c:586[/url]) Unknown IOCTL 0x14
099 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/pnpmgr/pnpmgr.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\pnpmgr\pnpmgr.c:3662[/url]) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
100 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/base/setup/usetup/interface/devinst.c?view=markup]P:\Trunk_slave\x86_CMake\build\base\setup\usetup\interface\devinst.c:82[/url]) Using driver 'pciide.sys' for device 'PCI\VEN_8086&DEV_7010&SUBSYS_11001AF4&REV_00\1&f103bba4&21'
101 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/ARM3/sysldr.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\ARM3\sysldr.c:174[/url]) Loading: [url=http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/storage/ide/pciide/pciide.c?view=markup]\SystemRoot\system32\drivers\pciide.sys[/url] at FCDBE000 with 8 pages
102 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/ARM3/sysldr.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\ARM3\sysldr.c:174[/url]) Loading: [url=http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/storage/ide/pciidex/pciidex.c?view=markup]\SystemRoot\system32\drivers\pciidex.sys[/url] at FCD97000 with e pages
103 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/storage/ide/pciidex/fdo.c?view=markup]P:\Trunk_slave\x86_CMake\build\drivers\storage\ide\pciidex\fdo.c:464[/url]) IRP_MJ_PNP / Unknown minor function 0x9
104 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/base/setup/usetup/interface/devinst.c?view=markup]P:\Trunk_slave\x86_CMake\build\base\setup\usetup\interface\devinst.c:82[/url]) Using driver '[url=http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/storage/ide/uniata/]uniata.sys[/url]' for device 'PCIIDE\IDEChannel\2&52f18517&1'
105 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/base/setup/usetup/interface/devinst.c?view=markup]P:\Trunk_slave\x86_CMake\build\base\setup\usetup\interface\devinst.c:82[/url]) Using driver '[url=http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/storage/ide/uniata/]uniata.sys[/url]' for device 'PCIIDE\IDEChannel\2&52f18517&0'
106 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/file.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\file.c:421[/url]) Using IopParseDevice() hack. Requested invalid attributes: 1
107 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/file.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\file.c:421[/url]) Using IopParseDevice() hack. Requested invalid attributes: 11f
108 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/fslib/vfatlib/vfatlib.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\fslib\vfatlib\vfatlib.c:210[/url]) WARNING: Failed to lock volume for formatting! Format may fail! (Status: 0xc0000010)
109 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/fslib/vfatlib/vfatlib.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\fslib\vfatlib\vfatlib.c:266[/url]) Failed to unlock volume (Status: 0xc0000010)
110 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ex/init.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\ex\init.c:1960[/url]) Free non-cache pages: 6dff
111 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/ARM3/zeropage.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\mm\ARM3\zeropage.c:40[/url]) Free non-cache pages: 6dff
112 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/base/setup/usetup/progress.c?view=markup]P:\Trunk_slave\x86_CMake\build\base\setup\usetup\progress.c:325[/url]) CHECKPOINT:HALF_COPIED
113 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/base/setup/usetup/progress.c?view=markup]P:\Trunk_slave\x86_CMake\build\base\setup\usetup\progress.c:325[/url]) CHECKPOINT:HALF_COPIED
114 [bug]0000[/bug] Boot took 88356588183 cycles!
115 [bug]0000[/bug] Interrupts: 15780 System Calls: 18668 Context Switches: 1746
116 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/base/setup/usetup/bootsup.c?view=markup]P:\Trunk_slave\x86_CMake\build\base\setup\usetup\bootsup.c:2237[/url]) No or unknown boot loader found
117 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/file.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\file.c:421[/url]) Using IopParseDevice() hack. Requested invalid attributes: 9
118 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/file.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\file.c:421[/url]) Using IopParseDevice() hack. Requested invalid attributes: 9
119 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/file.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\file.c:421[/url]) Using IopParseDevice() hack. Requested invalid attributes: 116
120 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/file.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\file.c:421[/url]) Using IopParseDevice() hack. Requested invalid attributes: 9
121 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/file.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\file.c:421[/url]) Using IopParseDevice() hack. Requested invalid attributes: 116
122 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ex/shutdown.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\ex\shutdown.c:45[/url]) Setting state to: 5
123 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:847[/url]) ERROR: Privilege not held for shutdown
124 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:859[/url]) Stopping lazy flush
125 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:867[/url]) Notifying callbacks
126 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:871[/url]) Swapping worker threads
127 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:911[/url]) Flushing volumes, cache flushed 128 pages
128 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/povolume.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\povolume.c:205[/url]) Opening registry
129 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/povolume.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\povolume.c:215[/url]) Flushing registry
130 [bug]0000[/bug] WARNING:  HvpWriteLog at [url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/cmlib/hivewrt.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\cmlib\hivewrt.c:26[/url] is UNIMPLEMENTED!
131 [bug]0000[/bug] WARNING:  HvpWriteLog at [url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/cmlib/hivewrt.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\cmlib\hivewrt.c:26[/url] is UNIMPLEMENTED!
132 [bug]0000[/bug] WARNING:  HvpWriteLog at [url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/cmlib/hivewrt.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\cmlib\hivewrt.c:26[/url] is UNIMPLEMENTED!
133 [bug]0000[/bug] WARNING:  HvpWriteLog at [url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/cmlib/hivewrt.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\cmlib\hivewrt.c:26[/url] is UNIMPLEMENTED!
134 [bug]0000[/bug] WARNING:  HvpWriteLog at [url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/cmlib/hivewrt.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\cmlib\hivewrt.c:26[/url] is UNIMPLEMENTED!
135 [bug]0000[/bug] WARNING:  HvpWriteLog at [url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/cmlib/hivewrt.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\cmlib\hivewrt.c:26[/url] is UNIMPLEMENTED!
136 [bug]0000[/bug] WARNING:  HvpWriteLog at [url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/cmlib/hivewrt.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\cmlib\hivewrt.c:26[/url] is UNIMPLEMENTED!
137 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/povolume.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\povolume.c:306[/url]) Local flush
138 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/povolume.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\povolume.c:143[/url]) Opening: \Device\Harddisk0\Partition1
139 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/file.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\io\iomgr\file.c:421[/url]) Using IopParseDevice() hack. Requested invalid attributes: 3
140 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/povolume.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\povolume.c:163[/url]) Sending flush to: 800002bc
141 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/povolume.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\povolume.c:310[/url]) Waiting for flushes
142 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/povolume.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\povolume.c:312[/url]) Flushes have completed
143 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:918[/url]) Queueing shutdown thread
144 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/poshtdwn.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\poshtdwn.c:135[/url])        smss.exe is still RUNNING (48)
145 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/poshtdwn.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\poshtdwn.c:143[/url]) HAL shutting down
146 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/poshtdwn.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\poshtdwn.c:147[/url]) I/O manager shutting down in phase 0
147 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/poshtdwn.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\poshtdwn.c:151[/url]) Configuration Manager shutting down
148 [bug]0000[/bug] WARNING:  HvpWriteLog at [url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/cmlib/hivewrt.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\cmlib\hivewrt.c:26[/url] is UNIMPLEMENTED!
149 [bug]0000[/bug] WARNING:  HvpWriteLog at [url=http://svn.reactos.org/svn/reactos/trunk/reactos/lib/cmlib/hivewrt.c?view=markup]P:\Trunk_slave\x86_CMake\build\lib\cmlib\hivewrt.c:26[/url] is UNIMPLEMENTED!
150 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/poshtdwn.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\poshtdwn.c:157[/url]) I/O manager shutting down in phase 1
151 [bug]0000[/bug] WARNING:  CcWaitForCurrentLazyWriterActivity at [url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/cc/copy.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\cc\copy.c:590[/url] is UNIMPLEMENTED!
152 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/poshtdwn.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\poshtdwn.c:168[/url]) Disabling wake timers
153 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/poshtdwn.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\poshtdwn.c:172[/url]) Taking the system down
154 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/poshtdwn.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\poshtdwn.c:73[/url]) It's the final countdown...5
155 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:231[/url]) No system power driver available
156 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'Root\*PNP0F13\0000' failed IRP_MN_QUERY_POWER
157 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'Root\*PNP0400\0000' failed IRP_MN_QUERY_POWER
158 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'Root\*PNP0501\0000' failed IRP_MN_QUERY_POWER
159 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'Root\*PNP0A00\0000' failed IRP_MN_QUERY_POWER
160 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'Root\*PNP0A03\0000' failed IRP_MN_QUERY_POWER
161 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'PCI\VEN_10EC&DEV_8029&SUBSYS_11001AF4&REV_00\1&f103bba4&03' failed IRP_MN_QUERY_POWER
162 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'PCI\VEN_1013&DEV_00B8&SUBSYS_11001AF4&REV_00\1&f103bba4&02' failed IRP_MN_QUERY_POWER
163 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'PCI\VEN_8086&DEV_7113&SUBSYS_11001AF4&REV_03\1&f103bba4&61' failed IRP_MN_QUERY_POWER
164 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'PCI\VEN_8086&DEV_7020&SUBSYS_11001AF4&REV_01\1&f103bba4&41' failed IRP_MN_QUERY_POWER
165 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'PCI\VEN_8086&DEV_7010&SUBSYS_11001AF4&REV_00\1&f103bba4&21' failed IRP_MN_QUERY_POWER
166 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'PCI\VEN_8086&DEV_7000&SUBSYS_11001AF4&REV_00\1&f103bba4&01' failed IRP_MN_QUERY_POWER
167 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'PCI\VEN_8086&DEV_1237&SUBSYS_11001AF4&REV_02\1&f103bba4&00' failed IRP_MN_QUERY_POWER
168 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'Root\PCI_HAL\0' failed IRP_MN_QUERY_POWER
169 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:175[/url]) Device 'Root\*PNP0303\0000' failed IRP_MN_QUERY_POWER
170 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/hal/halx86/legacy/halpnpdd.c?view=markup]P:\Trunk_slave\x86_CMake\build\hal\halx86\legacy\halpnpdd.c:818[/url]) HAL: PnP Driver Power!
171 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'Root\*PNP0F13\0000' failed IRP_MN_SET_POWER
172 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'Root\*PNP0400\0000' failed IRP_MN_SET_POWER
173 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'Root\*PNP0501\0000' failed IRP_MN_SET_POWER
174 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'Root\*PNP0A00\0000' failed IRP_MN_SET_POWER
175 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'Root\*PNP0A03\0000' failed IRP_MN_SET_POWER
178 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'PCI\VEN_10EC&DEV_8029&SUBSYS_11001AF4&REV_00\1&f103bba4&03' failed IRP_MN_SET_POWER
179 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'PCI\VEN_1013&DEV_00B8&SUBSYS_11001AF4&REV_00\1&f103bba4&02' failed IRP_MN_SET_POWER
180 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'PCI\VEN_8086&DEV_7113&SUBSYS_11001AF4&REV_03\1&f103bba4&61' failed IRP_MN_SET_POWER
181 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'PCI\VEN_8086&DEV_7020&SUBSYS_11001AF4&REV_01\1&f103bba4&41' failed IRP_MN_SET_POWER
182 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'PCI\VEN_8086&DEV_7010&SUBSYS_11001AF4&REV_00\1&f103bba4&21' failed IRP_MN_SET_POWER
183 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'PCI\VEN_8086&DEV_7000&SUBSYS_11001AF4&REV_00\1&f103bba4&01' failed IRP_MN_SET_POWER
184 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'PCI\VEN_8086&DEV_1237&SUBSYS_11001AF4&REV_02\1&f103bba4&00' failed IRP_MN_SET_POWER
185 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'Root\PCI_HAL\0' failed IRP_MN_SET_POWER
186 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/po/power.c?view=markup]P:\Trunk_slave\x86_CMake\build\ntoskrnl\po\power.c:208[/url]) Device 'Root\*PNP0303\0000' failed IRP_MN_SET_POWER
187 [bug]0000[/bug] ([url=http://svn.reactos.org/svn/reactos/trunk/reactos/hal/halx86/legacy/halpnpdd.c?view=markup]P:\Trunk_slave\x86_CMake\build\hal\halx86\legacy\halpnpdd.c:818[/url]) HAL: PnP Driver Power!
[/list]
Last edited by Bblaauw on Sun Dec 11, 2011 10:58 pm, edited 1 time in total.

FlyingIsFun1217
Posts: 475
Joined: Sun Jun 10, 2007 3:56 am

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by FlyingIsFun1217 »

Why did you post a log?

FlyingIsFun1217

Bblaauw
Posts: 149
Joined: Mon Aug 03, 2009 12:59 am

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by Bblaauw »

ehm because of "What I think we should do is get complete logs of each phase and file a bug at each error listed" ?
I'll edit it to put it in code blocks so it gets smaller. The idea was to assign 1 bugzilla bug to each errorline, but I didn't get to that yet, as it's a lot of lookup work finding (and filing) bugs.
Some message are of diagnostic nature rather than an error warning though, and some lines are duplicates.

Besides, a normal errorlog doesn't allow you to click/open the sourcefile as it's flat text instead of hypertext. Same as those cia.vc commit messages kinda.

clancg2003
Posts: 29
Joined: Sat Apr 10, 2010 3:24 am

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by clancg2003 »

DosGuy wrote:I just don't think that's realistic. A Windows license is $140, so why would anyone pay $180 per year for a "free" Windows clone?
Fair enough, even $5-$10 a month would be better than what the project is currently receiving, provided that enough people do this.
DosGuy wrote:I absolutely believe that there is enough goodwill in the community that people will donate some amount of money to help ReactOS develop into a viable alternative to Windows
Unfortunately, this hasn't been the case so far. While ReactOS has received some great donations from some people, it is really just a tiny fraction of the overall community that donates.

Anyways, the main gripe I hear about ReactOS from the community is its slow development speed. If we want to see this alleviated, then the community has to get more serious about donating money. With more money the developers can devote much more time to the project then they do currently. Right now, as far as I know, they receive nothing monetarily speaking. We can do better than this folks. If you want to see 0.4.0 or 0.5.0 in the not to distant future, then donate donate donate! Like I said before, ReactOS is free software, but that doesn't mean that the developers shouldn't get compensated for the time they spend working on it.

Webunny
Posts: 1201
Joined: Sat Apr 28, 2012 1:30 pm

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by Webunny »

Well, five months later, and we see the idea of a 'donation-bar' has actually had some success: we are now above the highest amount we ever had (in 2008). And that in the middle of a crisis. It's possible we won't make it to 30000 (is a bit much that), but at least it's getting us more than before. As some have said; it's also primarily getting people to take interest (and keep it going), and for that we need press/internet exposure AND an active-looking site too.

BTW, an easy marketing-trick to augment the donations even further is to put a ranking in the donations (instead of just randomised or by time), where the one that gives most is up, going down the lower the amount/donation was. It's a proven concept that, when introducing a ranking of this sort, people tend to spend/donate more. And it doesn't even involve much work to do so.

Webunny
Posts: 1201
Joined: Sat Apr 28, 2012 1:30 pm

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by Webunny »

Is it just me, or does this page of the thread goes on beyond the normal viewable frame, without there being a scrollbar at the bottom?
It doesn't do this on the other pages, so I think there is a bug or something.

edit: after this last post, it's back to normal, it would seem. Strange.

milon
Posts: 969
Joined: Sat Sep 05, 2009 9:26 pm

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by milon »

No, happens to me too. I think it's the Code box in Bblaauw's post.

Bblaauw
Posts: 149
Joined: Mon Aug 03, 2009 12:59 am

Re: [NewIdea]A new way to push ReactOS Development [NewIdea]

Post by Bblaauw »

Want me to clear it? I don't mind doing so as I didn't continue with filing bugs for a while now.
I've halted ReactOS real hardware testing till USB hubs are supported (as my keyboard has one, and is internally connected to that) and Ramdisk booting is working as well.

Post Reply

Who is online

Users browsing this forum: Ahrefs [Bot], irony and 2 guests