- Ros-dev - ReactOS.org

Re: [ros-dev] Re: [ros-svn] [gvg] 14302: Build freeldr as elf executable, initial Xen support

by Steven Edwards

--- Filip Navara <xnavara(a)volny.cz> wrote: > Just to let you know, there's no need to change the wide-character > string literals. You can use the -fshort-wchar GCC switch to get the > desired behaviour without touching the sources... I was under the impression short-wchar could differ depending on the platform and thats why wide-characters were a no-no in wine. Or is it that only newer gcc's support this option? Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

20 years, 5 months

2
1
0 0

RE: [ros-dev] ping Alex regarding log2() for scheduler

by Waldo Alvarez Cañizares

Hi Royce: int highest_bit ( int i ) { int ret = 0; if ( i > 0xffff ) i >>= 16, ret = 16; if ( i > 0xff ) i >>= 8, ret += 8; if ( i > 0xf ) i >>= 4, ret += 4; if ( i > 0x3 ) i >>= 2, ret += 2; return ret + (i>>1); } Guys I think I have one of those optimizations manuals for asm that actually use only one multiplication by a called ¨magic number¨ to get the first bit set. I actually don´t want to trace this code in my head but if you are searching a fast BSF replacement... It was tested using brute force for the 2^32 possible values on the argumment. Maybe you could check the internet for ¨Agner Fog optimization¨. I have a very bad memory so maybe the name is wrong. This is all the info I can give until I get home. Ohh well i can do it myself: http://www.df.lth.se/~john_e/gems/gem0039.html It was Harley´s magic number. so I wasn´t that far. or you can read it here... I have a c version but I guess you don´t need that :) ---------------------------------------------------------------------------------------------------------- Fast BSF replacement ASM/80386 Macro EMBSF5 emulates the BSF instruction for non-zero argument <------------------------------------ remember to test for this!!!!!!! This macro utilizes an algorithm published in the news group comp.arch by Robert Harley in 1996. The algorithm converts the general problem of finding the position of the least significant set bit into a special case of counting the number of bits in a contiguous block of set bits. By computing x^(x-1), where x is the original input argument, a right-aligned contiguous group of set bits is created, whose cardinality equals the position of the least significant set bit in the original input plus 1. The input x is of the form (regular expression): {x}n1{0}m. x-1 has the form {x}n{0}(m+1), and x^(x-1) has the form {0}n{1}(m+1). This step is pretty similar to the one used by macro PREPBSF <http://www.df.lth.se/~john_e/gems/gem002e.html> , only that PREPBSF <http://www.df.lth.se/~john_e/gems/gem002e.html> creates a right-aligned group of set bits whose cardinality equals exactly the position of the least significant set bit. Harley's algorithm then employs a special method to count the number of bits in the right-aligned contiguous block of set bits. I am not sure upon which number theoretical argument it is founded, and it wasn't explained in the news group post. According to Harley, if a 32-bit number of the form 00...01...11 is multiplied by the "magic" number (7*255*255*255), then bits <31:26> of the result uniquely identify the number of set bits in that number. A 64 entry table is used to map that unique result to the bit count. Here, I have modified the table to reflect the bit position of the least significant set bit in the original argument, which is one less than the bit count of the intermediate result. I have tested the macro EMBSF5 exhaustively for all 2^32-1 possible inputs, i.e. for all 32-bit numbers except zero. Place the following table in the data segment: table db 0, 0, 0,15, 0, 1,28, 0,16, 0, 0, 0, 2,21,29, 0 db 0, 0,19,17,10, 0,12, 0, 0, 3, 0, 6, 0,22,30, 0 db 14, 0,27, 0, 0, 0,20, 0,18, 9,11, 0, 5, 0, 0,13 db 26, 0, 0, 8, 0, 4, 0,25, 0, 7,24, 0,23, 0,31, 0 And here follows the actual macro: ; ; emulate bsf instruction ; ; input: ; eax = number to preform a bsf on ( != 0 ) ; ; output: ; edx = result of bsf operation ; ; destroys: ; ecx ; eflags ; MACRO EMBSF5 mov edx,eax ; do not disturb original argument dec edx ; n-1 xor edx,eax ; n^(n-1), now EDX = 00..01..11 IFDEF FASTMUL imul edx,7*255*255*255 ; multiply by Harley's magic number ELSE mov ecx,edx ; do multiply using shift/add method shl edx,3 sub edx,ecx mov ecx,edx shl edx,8 sub edx,ecx mov ecx,edx shl edx,8 sub edx,ecx mov ecx,edx shl edx,8 sub edx,ecx ENDIF shr edx,26 ; extract bits <31:26> movzx edx,[table+edx] ; translate into bit count - 1 ENDM Note: FASTMUL can be defined if your CPU has a fast integer multiplicator, like the AMD. The IMUL replacement should run in about 8-9 cycles. Gem writer: Norbert Juffa <mailto:norbert.juffa@amd.com> last updated: 1999-09-02 ---------------------------------------------------------------------------------------------------------- >> updated micro-code << Wow where I can get this? Do you have an assembler/disassembler? I once asked Tigran Aizvian but he told me not to have the information at all. With that I could save myself some time reversing it by trial and error using the black box approach. Someday. As far as I know still Intel CPUs microcode updates are not digitally signed so it could be reprogrammed. Here's updated micro-code for BSR, if you really think AMD & Intel will actually do it... IF r/m = 0 THEN ZF := 1; register := UNDEFINED; ELSE ZF := 0; register := 0; temp := r/m; IF OperandSize = 32 THEN IF (temp & 0xFFFF0000) != 0 THEN temp >>= 16; register |= 16; FI; FI; IF (temp & 0xFF00) != 0 THEN temp >>= 8; register |= 8; FI; IF (temp & 0xF0) != 0 THEN temp >>= 4; register |= 4; FI; IF (temp & 0xC) != 0 THEN temp >>= 2; register |= 2; FI; register |= (temp>>1); FI;

20 years, 5 months

2
1
0 0

RE: I think I know how uxtheme works...

by Casper Hornstrup

In copyright law it's the result that matter, not the process. To be protected by copyright law, it must be in tangible form. Looking at disassembled code is permitted by copyright law so it's only a problem if the person doing it lacks self-discipline and uses the disassembled code in a way that violates copyright law. That said, I don't believe there is a need for reverse engineering methods for implementing the majority of ReactOS and WINE. Our goal is to run Windows software on ReactOS and other free operating systems. We have some smart people on these projects. If the Windows software vendors could figure out how to use the interfaces using the public available documentation, then we can certainly implement the interfaces from that same information. If there is an interface that isn't documented, then certainly most Windows software won't use it and there is no need to implement the interface at all. Casper References: >From http://www.nus.edu.sg/intro/slides/021111_1_Wilson%20Wong.ppt What is protectable? Functionality? - not protected - must be an "expression...of a set of instructions" - Autodesk Inc v Dyason (Aust): copying function of AutoCAD lock but not code (no infringement) Program Structure? - (cf: plot elements in literary/dramatic works capable of protection) - eg. structural arrangements of modules and subroutines - yes if expression of idea, & no if ideas or functions: difficult line to draw - yes if organisation, sequence, arrangement or compilation - not protectable: elements of software which are: * ideas; * dictated by efficiency or external factors (eg h/w) specs, compatibility reqms, industry standards; or * public domain - not if similarity is due only to similar subject matter * analogy: drawing of a hand * eg any 2 word processors will have some structural similarities > -----Original Message----- > From: wine-devel-admin(a)winehq.org [mailto:wine-devel-admin@winehq.org] On Behalf Of Mike McCormack > Sent: 25. marts 2005 10:39 > To: Jonathan Wilson > Cc: wine-devel(a)winehq.org; ros-dev(a)reactos.com > Subject: Re: I think I know how uxtheme works... > > > Jonathan Wilson wrote: > > What I am doing here is clean-room reverse engineering. > > There's no reason that we need to expose ourselves to any legal risk at > all. It may be your opinion that reading assembly code and describing > it is legal and safe, but I don't agree and I'm sure others who work on > Wine don't either. > > The original IBM BIOS was clean room reverse engineered because there > was not enough documentation available for it. We have MSDN, which is > not 100% complete, but is good enough for most purposes. Other things > can be deduced from test programs. Information that cannot be deduced > by a test program is irrelevant. > > Reverse engineering does not help Wine. Casual observers will assume > that Wine is the result of reverse engineering by disassembly, which is > incorrect and harmful. > > Mike

20 years, 5 months

1
0
0 0

Re: [ros-svn] [gvg] 14302: Build freeldr as elf executable, initial Xen support

by Filip Navara

gvg(a)svn.reactos.com wrote: >Build freeldr as elf executable, initial Xen support > >Added files: >... > >Updated files: >... >branches/xen/reactos/boot/freeldr/freeldr/fs/ntfs.c >... > > Just to let you know, there's no need to change the wide-character string literals. You can use the -fshort-wchar GCC switch to get the desired behaviour without touching the sources... - Filip

20 years, 5 months

1
0
0 0

Re: [ros-dev] Re: Colinux crash : Lock the kernel - Debug traces for Bug512]

by Steven Edwards

Hi Hartmut, --- Hartmut Birr <hartmut.birr(a)gmx.de> wrote: > with my last changes (r14296), coLinux does start and does mount the > root partition. It exist an second problem. The coLinux window is only > shown for a very short time. I'm not so familiar with the gdi, user and > win32k code. I cannot fix the second problem. Nice! I will svn update, rebuild and test tommrow. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

20 years, 5 months

1
0
0 0

Re: I think I know how uxtheme works...

by Jonathan Wilson

What I am doing here is clean-room reverse engineering. Essentially it involves taking existing binary modules and sources of information and writing up what they do in a way that isnt violating the copyright on the origonal (IANAL but I dont think what I posted violates the copyright on the windows binaries). Then it involves someone else who hasnt seen the origonal copyrighted source using the resulting information to re-implement whatever the information describes. As long as the person who origonally did the reverse engineering never contributes anything to the resulting code, it is (AFAIK, IAMAL) perfectly legal (after all, this is exactly what was done when the first clone PC bios was written, one group disassembled the origonal IBM BIOS and wrote up documents on how it works and how to talk to it. Then another group not connected to the people who did the origonal reverse engineering took the documentation and re-implemented the BIOS from just the documentation without looking at the orgininal IBM implementation) I never had any plans to actually write code for this (since doing so is out of my skill range) and as long as I never do so in the future (thus "tainting" the code I write as being a potential Derived Work of the microsoft code I looked at), I dont see any way that the results of this investigation could be considered a derived work of any microsoft code. Although if I have a mis-understanding of this situation, please point out what I am doing that would make code written by someone else using the information in my posts a Derived Work of microsofts origonal binaries.

20 years, 5 months

2
1
0 0

Speed Tests (was: ping Alex regarding log2() for scheduler)

by Ash

Hello, I'd like to provide a small VS.NET project file with 5 different tests. - 46ffffe9 tells everything is alright with the function calculation - times are measured with QueryPerformanceCounter - loop run cnt: 0x2ffffff result orig function 46ffffe9 it took 1491052 result orig function inlined 46ffffe9 it took 1035547 result second proposal inlined 46ffffe9 it took 1244434 result optimized asm 46ffffe9 it took 1338367 result debug asm 46ffffe9 it took 8774815 The second proposal is the original proposal but more shifts - still slower tho. Interesting is the inlined version generated by MSVC, shaving off almost 1/3 of the overall time. Also stared as "optimized asm" - no gurantee on register safety tho ;) For portability and performance sake it should be considered to create a compiler macro. This function is terribly small, any optimisations inside are outweighted by the calling overhead in this case. The most impressive one is the original function inlined, althought the ASM would only work on x86. Please do not think about using 64k tables, thats what, 1/2 of a Sempron L2 cache? It would really really trash performance. Available at: <a href="http://hackersquest.org/kerneltest.html" title="Kernel Test Emulator">Kernel Test</a> <a href="http://wohngebaeudeversicherung.einsurance.de/">http://wohngebaeudeversicherung.einsurance.de</a>

20 years, 5 months

5
7
0 0

about changelog idea

by Magnus Olsen

Hi Why not create two diffrent changelog for each release. one that contain all svn commit msg next one is what is benefit for the user. I think this is good idea. ´Then the user can read what new for them. If some want really know what we have done. Then they can read all commit msg. I think this is good idea, and will benfit alot of people.

20 years, 5 months

3
5
0 0

Re: [ros-dev] I think I know how uxtheme works...

by rlangschultz＠cox.net

I would think that ReactOs is not anywhere near being ready for themeing partially because it needs to write much more of the system software. Themeing can always be an option later. I have mentioned an alternate filesystem, and other services, but since I have not submitted code, people on the mailing list think i can not program something of the sort. I think it is great that people are wanting to understand the process of themeing but keep in mind that loading a theme may cut down on the resources available to the opertating system or may interfere with someone elses environment. > > From: Jonathan Wilson <jonwil(a)tpgi.com.au> > Date: 2005/03/23 Wed PM 09:19:23 EST > To: wine-devel(a)winehq.org, ros-dev(a)reactos.com > Subject: [ros-dev] I think I know how uxtheme works... > > What I strongly suspect happens is this: > 1.The themes service is always loaded and running and holds the theme data > (and it contains details of which .msstyles file to use) > 2.At some point (either at startup if the changes are global or when an app > loads if the changes are app specific, I cant find where this bit happens > but I suspect the themes service does this) control passes to ordinal 34 in > uxtheme.dll (aka ThemeHooksInstall acording to uxtheme.pdb). This function > calls an undocumented function in user32 called RegisterUserApiHooks (which > appears to be taylor made for uxtheme to do what it needs to do). > The function hooks: > GetScrollInfo > SetScrollInfo > EnableScrollBar > SetWindowRgn > DefWindowProcW > DefWindowProcA > PreWndProc (probobly stuff that happens internally before the window > procedure gets called) > PostWndProc (probobly stuff that happens internally after the window > procedure gets called) > PreDefDlgProc (probobly connected to dialog boxes) > PostDefDlgProc (probobly connected to dialog boxes) > GetSystemMetrics > SystemParametersInfoA > SystemParametersInfoW > DrawFrameControl > DrawCaption > MDIRedrawFrame (probobly related to MDI frame windows) > This is what causes all apps (including non-theme-aware ones) to get themed > non-client areas (window borders etc) > 3.Apps that are theme aware have a manifest, load comctl32.dll 6.0 and > probobly have to call InitCommonControlsEx (although I think some of the > code in the dllmain for comctl32.dll 6.0 may also end up calling > InitCommonControlsEx). This causes new versions of the stock classes > (button, list box, edit, combo box etc etc etc) to be created and > registered. A cursory examination of some of these classes shows that they > dont seem to "pull code" from the stock implementation in user32.dll (i.e. > anything they dont themselves handle goes back to DefWindowProc). In > particular, it doesnt appear as though they have any knowledge of the > classes or window procedures contained in user32.dll. > then 4.Apps that need to do something extra call into functions exported by > uxtheme.dll to do whatever they need to do. > > user32.dll seems to have no knowledge whatsoever about themeing and > uxtheme. All that user32 has is RegisterUserApiHooks (and the matching > UnregisterUserApiHooks) that uxtheme uses to hook into user32.dll and do stuff. > > Exactly how the theme service and theme engine works "under the hood" > doesnt matter. > But for ReactOS and WINE purposes, I suggest we implement the following: > 1.A function similar to RegisterUserApiHooks/UnregisterUserApiHooks (either > reverse engineer the MS function or write our own). This will allow uxtheme > to hook into the global drawing for things like window borders without > user32 needing to care about uxtheme and what uxtheme does (just like how > MS hooks into user32 that way) > 2.Whatver code is necessary to get the hooks installed right so that all > apps get the "global" theming like on real windows > 3.Support to read the manifest and load a new comctl32.dll that would be > like the version 6 from microsoft (and would contain complete theme-aware > implementations of the stock controls just like MS comctl32.dll 6.0 does) > and 4.All the needed uxtheme exports to make stuff run > > This would be the same way Microsoft does things. > User32.dll would have no idea whatsoever about uxtheme and theming > All apps would get non-client-area themeing like on windows. > And only theme aware apps would get themed controls etc (the rest would get > "stock" windows controls) > > Oh and btw, if this "reverse engineering" is not "clean room" enough for > WINE and ReactOS, let me know and I will stop posting it :) > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev >

20 years, 5 months

1
0
0 0

Re: Colinux crash : Lock the kernel - Debug traces for Bug512]

by Hartmut Birr

Hi, with my last changes (r14296), coLinux does start and does mount the root partition. It exist an second problem. The coLinux window is only shown for a very short time. I'm not so familiar with the gdi, user and win32k code. I cannot fix the second problem. - Hartmut

20 years, 5 months

1
0
0 0

OpenOffice.Org 2.0 beta's installer causes kernel panic

by Wierd Wierd

Steven asked me to do a quick trial to see if any of the recent fixes in ROS had fixed this problem with the OOo 2.0 beta installer, then asked me to provide this debug dump. *************************** Used memory 131072Kb (mm/mminit.c:375) Kernel Stack Limits. InitTop = 0x800be000, Init = 0x800bb000 (mm/virtual.c:214) FIXME: MEMORY_AREA_SYSTEM case incomplete (or possibly wrong) for NtQueryVirtualMemory() (ke/bug.c:56) Found Bugcheck Resource Data! (ke/bug.c:67) Got Pointer to Bugcheck Resource Data! (ke/clock.c:80) KiInitializeSystemClock() (ke/clock.c:99) Finished KiInitializeSystemClock() (ex/timer.c:232) ExpInitializeTimerImplementation() (io/pnproot.c:676) DeviceID: Root\Ne2000 PDO 805451f8 (io/pnproot.c:689) InstanceID: 0000 PDO 805451f8 (io/pnproot.c:676) DeviceID: Root\PCI PDO 80545300 (io/pnproot.c:689) InstanceID: 0000 PDO 80545300 (io/pnproot.c:676) DeviceID: Root\LEGACY_UNKNOWN PDO 80545448 (io/pnproot.c:689) InstanceID: 0000 PDO 80545448 DriverBase for \SystemRoot\system32\drivers\pci.sys: 9cdaf000 Peripheral Component Interconnect Bus Driver DriverBase for acpi.sys: 9cdb7000 Advanced Configuration and Power Interface Bus Driver ACPI: System firmware supports: +------------------------------------------------------------ | Sx states: +S0 -S1 -S2 -S3 -S4 +S5 +------------------------------------------------------------ Sleep Button: found DriverBase for scsiport.sys: 9cde6000 DriverBase for atapi.sys: 9cdf1000 DriverBase for class2.sys: 9cdfb000 DriverBase for disk.sys: 9ce04000 DriverBase for vfatfs.sys: 9ce0c000 DriverBase for bootvid.sys: 9ce1f000 DriverBase for ndis.sys: 9ce3e000 DriverBase for \SystemRoot\system32\drivers\pcnet.sys: 9ce66000 DriverBase for \SystemRoot\system32\drivers\vmx_svga.sys: 9cea2000 DriverBase for \SystemRoot\system32\drivers\VIDEOPRT.SYS: 9cebe000 DriverBase for \SystemRoot\system32\drivers\floppy.sys: 9e0db000 DriverBase for \SystemRoot\system32\drivers\cdrom.sys: 9e0fb000 DriverBase for \SystemRoot\system32\drivers\fs_rec.sys: 9e10a000 DriverBase for \SystemRoot\system32\drivers\beep.sys: 9e118000 DriverBase for \SystemRoot\system32\drivers\null.sys: 9e126000 DriverBase for \SystemRoot\system32\drivers\psaux.sys: 9e13e000 DriverBase for \SystemRoot\system32\drivers\keyboard.sys: 9e157000 DriverBase for \SystemRoot\system32\drivers\mouclass.sys: 9e167000 DriverBase for \SystemRoot\system32\drivers\blue.sys: 9e175000 DriverBase for \SystemRoot\system32\drivers\msfs.sys: 9e18b000 DriverBase for \SystemRoot\system32\drivers\npfs.sys: 9e1a1000 (mm/virtual.c:235) FIXME: MEMORY_AREA_KERNEL_STACK case incomplete (or possibly wrong) for NtQueryVirtualMemory() DriverBase for \??\C:\ReactOS\system32\win32k.sys: 9e4fe000 DriverBase for \??\C:\ReactOS\system32\freetype.dll: 9e5e6000 DriverBase for \SystemRoot\System32\kbdus.dll: 9e66b000 (ntuser/desktop.c:574) IntShellHookNotify: No desktop! (ntuser/desktop.c:574) IntShellHookNotify: No desktop! (ntuser/desktop.c:574) IntShellHookNotify: No desktop! WL-Status: ReactOS is starting up... DriverBase for \SystemRoot\system32\drivers\tcpip.sys: 9eaa2000 DriverBase for \SystemRoot\system32\drivers\afd.sys: 9eadf000 (umpnpmgr.c:160) Device arrival event: HTREE\Root\0 (umpnpmgr.c:160) Device arrival event: Root\LEGACY_UNKNOWN\0000 (umpnpmgr.c:160) Device arrival event: Root\PCI\0000 (umpnpmgr.c:160) Device arrival event: Root\Ne2000\0000 (umpnpmgr.c:160) Device arrival event: Root\LEGACY_UNKNOWN\0000 (umpnpmgr.c:160) Device arrival event: Root\LEGACY_UNKNOWN\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_1274&DEV_1371&SUBSYS_13711274&REV_02\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_1022&DEV_2000&SUBSYS_20001022&REV_10\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_8086&DEV_7113&SUBSYS_197615AD&REV_08\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_8086&DEV_7112&SUBSYS_197615AD&REV_00\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_8086&DEV_7111&SUBSYS_197615AD&REV_01\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_8086&DEV_7110&SUBSYS_197615AD&REV_08\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_8086&DEV_7191&SUBSYS_00000000&REV_01\0000 (umpnpmgr.c:160) Device arrival event: PCI\VEN_8086&DEV_7190&SUBSYS_197615AD&REV_01\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0A03\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0C02\31 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0200\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0001\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0100\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0B00\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0800\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0303\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0F13\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0A05\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0400\0000 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0501\1 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0501\2 (umpnpmgr.c:160) Device arrival event: ACPI\PNP0700\0000 LAN WORKER BUSY 9eac0380 8055f590 LAN WORKER BUSY 9eac0380 8055f590 LAN WORKER BUSY 9eac0380 8055f590 LAN WORKER BUSY 9eac0380 8055f590 LAN WORKER BUSY 9eac0380 8055ec28 LAN WORKER BUSY 9eac0380 8080be88 DriverBase for \SystemRoot\System32\vmx_fb.DLL: 9ec49000 (misc/driver.c:244) Unsupported DDI function 0x6 (misc/driver.c:244) Unsupported DDI function 0x47 (misc/driver.c:244) Unsupported DDI function 0x46 (misc/driver.c:244) Unsupported DDI function 0x45 FIXME: CopyImage doesn't support IMAGE_ICON correctly! (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find mxdMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find auxMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find mxdMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find midMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find modMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find widMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find wodMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find auxMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find mxdMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find midMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find widMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find wodMessage LAN WORKER BUSY 9eac0380 808a8798 LAN WORKER BUSY 9eac0380 808a8840 LAN WORKER BUSY 9eac0380 808a88e8 LAN WORKER BUSY 9eac0380 805bb5a0 LAN WORKER BUSY 9eac0380 806ef608 LAN WORKER BUSY 9eac0380 806ef648 (ntuser/class.c:114) Failed to lookup class atom! LAN WORKER BUSY 9eac0380 805c6138 LAN WORKER BUSY 9eac0380 805c7f80 LAN WORKER BUSY 9eac0380 805c8028 LAN WORKER BUSY 9eac0380 8069d090 LAN WORKER BUSY 9eac0380 8069d138 LAN WORKER BUSY 9eac0380 805c6138 Using shell hooks for notification of shell events. (ntuser/hook.c:504) Not implemented: HookId 3 Global TRUE SHELLHOOK 1 SHELLHOOK 4 SHELLHOOK 1 LAN WORKER BUSY 9eac0380 806fe7a8 SHELLHOOK 4 SHELLHOOK 4 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 806f7988 LAN WORKER BUSY 9eac0380 806f7a30 LAN WORKER BUSY 9eac0380 806f7ad8 LAN WORKER BUSY 9eac0380 806f7b80 LAN WORKER BUSY 9eac0380 806f7c28 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 806f7988 LAN WORKER BUSY 9eac0380 80601110 LAN WORKER BUSY 9eac0380 806f7ad0 SHELLHOOK 4 LAN WORKER BUSY 9eac0380 806f7988 LAN WORKER BUSY 9eac0380 806f7ad8 LAN WORKER BUSY 9eac0380 806fac18 LAN WORKER BUSY 9eac0380 806facc0 (ntuser/painting.c:619) PAINTING BUG: Thread marked as containing dirty windows, but no dirty windows found! LAN WORKER BUSY 9eac0380 806fac18 LAN WORKER BUSY 9eac0380 806fff60 LAN WORKER BUSY 9eac0380 806fac18 LAN WORKER BUSY 9eac0380 806fac18 LAN WORKER BUSY 9eac0380 806facc0 SHELLHOOK 1 SHELLHOOK 1 SHELLHOOK 4 LAN WORKER BUSY 9eac0380 8069aa98 LAN WORKER BUSY 9eac0380 8069ab40 LAN WORKER BUSY 9eac0380 8069aa98 LAN WORKER BUSY 9eac0380 8069aa98 LAN WORKER BUSY 9eac0380 8069aa98 LAN WORKER BUSY 9eac0380 806f8b10 LAN WORKER BUSY 9eac0380 8069aa98 LAN WORKER BUSY 9eac0380 808aad80 LAN WORKER BUSY 9eac0380 808aad80 LAN WORKER BUSY 9eac0380 808aad80 LAN WORKER BUSY 9eac0380 808aad80 LAN WORKER BUSY 9eac0380 808aad80 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5b60 LAN WORKER BUSY 9eac0380 808b5c08 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5b60 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5b60 LAN WORKER BUSY 9eac0380 808b5c08 LAN WORKER BUSY 9eac0380 808b5cb0 LAN WORKER BUSY 9eac0380 808b5d58 LAN WORKER BUSY 9eac0380 808b5e00 LAN WORKER BUSY 9eac0380 808b5ea8 LAN WORKER BUSY 9eac0380 808b5f50 LAN WORKER BUSY 9eac0380 808ac070 LAN WORKER BUSY 9eac0380 808ac118 LAN WORKER BUSY 9eac0380 808ac1c0 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5b60 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5b60 LAN WORKER BUSY 9eac0380 808b5c08 LAN WORKER BUSY 9eac0380 808b5cb0 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5600 LAN WORKER BUSY 9eac0380 808b5640 LAN WORKER BUSY 9eac0380 808b5b60 LAN WORKER BUSY 9eac0380 808b5c08 LAN WORKER BUSY 9eac0380 808b5cb0 LAN WORKER BUSY 9eac0380 808b5d58 (api/handle.c:71) CsrGetObject returning invalid handle (NTDLL:ldr/utils.c:2097) Relocating (777c0000 -> 750000) C:\ReactOS\system32\winmm.dll FIXME: CopyImage doesn't support IMAGE_ICON correctly! (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find mxdMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find auxMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find mxdMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find midMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find modMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find widMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find wodMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find auxMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find mxdMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find midMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find widMessage (NTDLL:ldr/utils.c:1216) LdrGetExportByName(): failed to find wodMessage (msi.c:390:MsiInstallProductW) L"openofficeorg1979.msi" (null) (action.c:1413:ACTION_PerformUIAction) UNHANDLED MSI ACTION L"SetupInitialization" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"FindRelatedProducts" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"ValidateProductID" LAN WORKER BUSY 9eac0380 80900b28 LAN WORKER BUSY 9eac0380 80900bd0 LAN WORKER BUSY 9eac0380 80907360 LAN WORKER BUSY 9eac0380 80907408 LAN WORKER BUSY 9eac0380 809074b0 LAN WORKER BUSY 9eac0380 80907558 LAN WORKER BUSY 9eac0380 80907600 LAN WORKER BUSY 9eac0380 80907280 LAN WORKER BUSY 9eac0380 80907440 LAN WORKER BUSY 9eac0380 80907558 LAN WORKER BUSY 9eac0380 80907600 LAN WORKER BUSY 9eac0380 80908908 LAN WORKER BUSY 9eac0380 80909628 LAN WORKER BUSY 9eac0380 8090ad58 LAN WORKER BUSY 9eac0380 8090b298 LAN WORKER BUSY 9eac0380 8090b420 LAN WORKER BUSY 9eac0380 8090b230 LAN WORKER BUSY 9eac0380 8090b500 LAN WORKER BUSY 9eac0380 8090b5a8 LAN WORKER BUSY 9eac0380 8090b6d0 LAN WORKER BUSY 9eac0380 8090b778 (action.c:1823:load_file) Unfound Component L"g_f_registry_spool_oo_td_internalgraphics_filters_xcu__share_registry_modules_o_"... (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"IsolateComponents" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"MigrateFeatureStates" (action.c:1413:ACTION_PerformUIAction) UNHANDLED MSI ACTION L"InstallWelcome" (action.c:1413:ACTION_PerformUIAction) UNHANDLED MSI ACTION L"SetupProgress" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveExistingProducts" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"AllocateRegistrySpace" (cm/ntfunc.c:251) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\Installer\Components"!) LAN WORKER BUSY 9eac0380 80918ac0 LAN WORKER BUSY 9eac0380 80918e58 LAN WORKER BUSY 9eac0380 8090a070 LAN WORKER BUSY 9eac0380 8090a210 LAN WORKER BUSY 9eac0380 8090a5b0 LAN WORKER BUSY 9eac0380 8090b118 LAN WORKER BUSY 9eac0380 80918ac0 LAN WORKER BUSY 9eac0380 809122d0 LAN WORKER BUSY 9eac0380 80918e58 LAN WORKER BUSY 9eac0380 8090a210 LAN WORKER BUSY 9eac0380 8090a5b0 LAN WORKER BUSY 9eac0380 8090b118 LAN WORKER BUSY 9eac0380 80910138 LAN WORKER BUSY 9eac0380 809122d0 LAN WORKER BUSY 9eac0380 80916578 (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnpublishComponents" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"MsiUnpublishAssemblies" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnpublishFeatures" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"StopServices" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"DeleteServices" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterComPlus" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"SelfUnregModules" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterTypeLibraries" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveODBC" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterFonts" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveRegistryValues" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterClassInfo" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterExtensionInfo" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterProgIdInfo" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"UnregisterMIMEInfo" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveIniValues" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveShortcuts" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveEnvironmentStrings" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveDuplicateFiles" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveFiles" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"RemoveFolders" (action.c:1321:ACTION_HandleStandardAction) UNHANDLED Standard Action L"MoveFiles" LAN WORKER BUSY 9eac0380 8094b8b8 LAN WORKER BUSY 9eac0380 8098c5e0 LAN WORKER BUSY 9eac0380 8098ccd0 LAN WORKER BUSY 9eac0380 8098cd78 LAN WORKER BUSY 9eac0380 8099c9e0 LAN WORKER BUSY 9eac0380 809a45b0 LAN WORKER BUSY 9eac0380 8099c9e0 LAN WORKER BUSY 9eac0380 8099c9e0 LAN WORKER BUSY 9eac0380 809aa588 LAN WORKER BUSY 9eac0380 809aa630 LAN WORKER BUSY 9eac0380 809aa6d8 LAN WORKER BUSY 9eac0380 809aa780 LAN WORKER BUSY 9eac0380 809aa828 LAN WORKER BUSY 9eac0380 809aa8d0 LAN WORKER BUSY 9eac0380 809aa978 LAN WORKER BUSY 9eac0380 809b7478 LAN WORKER BUSY 9eac0380 809b7520 LAN WORKER BUSY 9eac0380 809b75c8 LAN WORKER BUSY 9eac0380 809b7670 LAN WORKER BUSY 9eac0380 809beb88 (ntuser/painting.c:619) PAINTING BUG: Thread marked as containing dirty windows, but no dirty windows found! LAN WORKER BUSY 9eac0380 809ca050 LAN WORKER BUSY 9eac0380 809c8aa8 LAN WORKER BUSY 9eac0380 809c7900 LAN WORKER BUSY 9eac0380 809cd280 LAN WORKER BUSY 9eac0380 809cd328 LAN WORKER BUSY 9eac0380 809cd3d0 LAN WORKER BUSY 9eac0380 809ef990 LAN WORKER BUSY 9eac0380 809f0fd0 LAN WORKER BUSY 9eac0380 809f2850 LAN WORKER BUSY 9eac0380 809ef990 LAN WORKER BUSY 9eac0380 809f0fd0 LAN WORKER BUSY 9eac0380 809f2850 LAN WORKER BUSY 9eac0380 809f2ca8 LAN WORKER BUSY 9eac0380 809f2850 LAN WORKER BUSY 9eac0380 809f2ca8 LAN WORKER BUSY 9eac0380 809fcc50 LAN WORKER BUSY 9eac0380 809fccf8 LAN WORKER BUSY 9eac0380 809f2850 LAN WORKER BUSY 9eac0380 809f2ca8 LAN WORKER BUSY 9eac0380 809feb50 LAN WORKER BUSY 9eac0380 809febf8 LAN WORKER BUSY 9eac0380 809feca0 LAN WORKER BUSY 9eac0380 809fed48 LAN WORKER BUSY 9eac0380 809fedf0 LAN WORKER BUSY 9eac0380 809fee98 LAN WORKER BUSY 9eac0380 809fef40 LAN WORKER BUSY 9eac0380 809fefe8 LAN WORKER BUSY 9eac0380 809ff090 LAN WORKER BUSY 9eac0380 809ff138 LAN WORKER BUSY 9eac0380 809ff1e0 LAN WORKER BUSY 9eac0380 809ff288 LAN WORKER BUSY 9eac0380 809f2850 LAN WORKER BUSY 9eac0380 80a07570 LAN WORKER BUSY 9eac0380 80a07618 LAN WORKER BUSY 9eac0380 80a076c0 LAN WORKER BUSY 9eac0380 80a07768 LAN WORKER BUSY 9eac0380 80a07810 LAN WORKER BUSY 9eac0380 80a078b8 LAN WORKER BUSY 9eac0380 80a14f10 LAN WORKER BUSY 9eac0380 80a14fb8 LAN WORKER BUSY 9eac0380 80a15060 LAN WORKER BUSY 9eac0380 80a206b8 LAN WORKER BUSY 9eac0380 80a20a88 LAN WORKER BUSY 9eac0380 80a20b30 LAN WORKER BUSY 9eac0380 80a23e50 LAN WORKER BUSY 9eac0380 80a23ef8 LAN WORKER BUSY 9eac0380 80a23fa0 LAN WORKER BUSY 9eac0380 807a42a8 LAN WORKER BUSY 9eac0380 80769f10 LAN WORKER BUSY 9eac0380 80784578 LAN WORKER BUSY 9eac0380 808b9ec0 LAN WORKER BUSY 9eac0380 80541698 LAN WORKER BUSY 9eac0380 80a44ff0 LAN WORKER BUSY 9eac0380 80a45098 LAN WORKER BUSY 9eac0380 805b6538 LAN WORKER BUSY 9eac0380 805b6578 LAN WORKER BUSY 9eac0380 806ab958 LAN WORKER BUSY 9eac0380 806ab998 LAN WORKER BUSY 9eac0380 805cb660 LAN WORKER BUSY 9eac0380 805cb708 Freeing mapped page (0x5ff4000 count 1) KeBugCheck at mm/freelist.c:749 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The bug code is undefined. Please use an existing code instead. Technical information: *** STOP: 0x00000000 (0x00000000,0x00000000,0x00000000,0x00000000) Frames: <ntoskrnl.exe: a311> <ntoskrnl.exe: a337> <ntoskrnl.exe: 43a03> <ntoskrnl.exe: 4049e> <ntoskrnl.exe: 4f02e> <ntoskrnl.exe: 4c802> <ntoskrnl.exe: 127f7> <ntoskrnl.exe: 405ca> <ntoskrnl.exe: 40852> <ntoskrnl.exe: 1217b> <ntoskrnl.exe: 12442> <ntoskrnl.exe: 10151> <ntoskrnl.exe: 10818> <vfatfs.sys: 972c> <vfatfs.sys: ad6f> <ntoskrnl.exe: 32975> <ntoskrnl.exe: 32991> <ntoskrnl.exe: 3830b> <ntoskrnl.exe: 318b> <7FFE0304> ******************************** Enjoy. __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

20 years, 5 months

2
1
0 0

svn.reactos.com disturbances

by Casper Hornstrup

On 24-28 of March, between 05:00 and 08:00 CET, svn.reactos.com may be unavailable for a duration of up to 1 hour each day due to maintenance work at the hosting center. Sorry for the inconvenience, Casper

20 years, 5 months

1
0
0 0

Re: registry TODO

by Steven Edwards

Hi, --- Boaz Harrosh <boaz(a)hishome.net> wrote: > How is ReactOS's current (future) system? I think ReactOS's registry is binary compatible with NT4. It and the windows 2000 format was documented/reversed for samba and the linux ntchpwd bootdisk projects. If I remeber right Eirc Kohl offered to release some of his work to Wine for the binary format so you might want to ping him about the implementation details. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

20 years, 5 months

3
2
0 0

Re: [ros-dev] Re: [ros-svn] [ea] 14244: SM: init system reading the registry

by Steven Edwards

Hi Emanuele, --- ea <ea(a)iol.it> wrote: > I tested twice fresh builds before committing and the 3rd time right now > with local repository at revision 14248. For me it compiles, installs > and boots correctly (qemu 0.6.1). Can you tell me more about the lock? I > can't rollback right now because I am going out to work in a few > seconds. Feel free to restore subsys/csrss and subsys/smss to 14243 if > you feel this is a blocking bug for you. Sorry, its not your problem. I rm -fr'd my reactos tree and did a clean CVS checkout and things are cool now. I guess the current build system left some crap around that caused problems. Nice work btw on the smss stuff. How much trouble do you think it would be possible to make a native mode console application in smss like the Windows recovery console? I have been thinking about doing this for the boot CD for a while but would like to make it more powerful than the Windows recovery console. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

20 years, 5 months

7
6
0 0

Re: registry TODO

by Boaz Harrosh

James Hawkins wrote: >>Nobody's working on it, so it won't be supported until someone cares >>enough to do it. I encouraged a few people to start working on it but >>nobody did, so taking out the existing support is a way to provide >>more encouragement. If that's not enough then the feature simply won't >>be supported anymore. >> >> I started toying around the current and old code, Gathering knowledge and ideas. What I think of doing is: keep the boot registry as is (more less). Put in on wine/wine/config a key system that enables a "plugin" system of registry loaders/savers. Builtin plugins are current format and Windows binary format. Other formats could be easily implemented; candidates could be XML, MySQL etc... The system I thought of would also save the hives and sub trees, to the files/plugins it was loaded from. Each plugin could also implement a write behind so Data don't get lost in case of a crash or power lost. Good point with the on demand-loading/cache of keys. It should be done this way. So in summary: 1. Implement a Memory registry with plugin drivers and mount semantics. This driver goes here, that driver mounts there. 2. Implement 2 basic drivers: Wine builtin format, Windows binary format. 3. Enable dynamic load of external drivers. The Initial registry system is always loaded from system.reg builtin format which is also the "fstab" file of the registry. At minimum every thing is exactly like now one (two) files builtin format, and that's it. At the maximum it can be highly object oriented with per user, per application, per group management. Please tell me what you think. Any libraries I should look into? How is ReactOS's current (future) system? Free Life Boaz

20 years, 5 months

4
4
0 0

Re: [ros-svn] [ea] 14244: SM: init system reading the registry

by Steven Edwards

Hi, --- ea(a)svn.reactos.com wrote: > trunk/reactos/subsys/smss/initss.c "Debug Windows" fails to be registered causing it to not boot the Win32 subsystem and hard lock. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250

20 years, 5 months

3
2
0 0

RC1 of ros 0.2.6 is out

by Robert Köpferl

Hi, I just finished uploading the RC1 to sf.net The last build worked quite well, but improvements to the branch are welcome. If no major issues occour, we may perhaps advance to Release as next step, already. BTW: RosApps is from 2003, still. They are already in the installation, aren't they? So should they be hidden?

20 years, 5 months

3
3
0 0

GetCommProperties implementation

by Saveliy Tretiakov

Here is my implementation of GetCommProperties. I've also implemented IOCTL_SERIAL_GET_PROPERTIES in serial driver.

20 years, 5 months

2
2
0 0

Build failure in setupapi

by Steven Edwards

Hi, I am running clean on the trunk and I am getting this error. [CC] pnp_c.c pnp_c.c: In function `PNP_GetVersion': pnp_c.c:72: error: syntax error before '%' token pnp_c.c:83: warning: use of cast expressions as lvalues is deprecated make: *** [pnp_c.o] Error 1 My gcc is a cross-compiler 3.3.4 My pnp_c.c has the following at line 72 NdrGetBuffer( (PMIDL_STUB_MESSAGE)&_StubMsg, _StubMsg.BufferLength, %_Handle); Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

20 years, 5 months

6
5
0 0

Serial port IRQ detection

by Mark Junker

Hi, is there a requirement for the serial port IRQ detection? This was also part of my old sources but currently I simply don't know how to do it inside the ReactOS serial driver. BTW: How does the "serenum" stuff works? Regards, Mark

20 years, 5 months

2
1
0 0

Re: [ros-dev] Update reported version to Windows 2000 (Service Pack?)

by Steven Edwards

--- art yerkes <ayerkes(a)speakeasy.net> wrote: > We need a convenient way to report a different version on a per application > basis. I think there's some code to do this but I could not determine > whether it works (despite several people telling me how to do it). While > we're at it, can we verify that this code works and post a howto about > reporting a specific windows version to an application? I don't know much about it but it is supposed to be possible. There is a app compatiblity shell extention that Thomas wrote that is supposed to do it under Windows. Anyone know if this really works under ReactOS? Thanks Steven __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs

20 years, 5 months

1
0
0 0

Serial port type detection

by Mark Junker

Hi, I found some old sources from me where I detect the IRQ and the type (8250, 16450, 16550, 16550A) of a COM port. I converted the type detection sources to C. The detection if there is a COM port at all is made by inverting all bits of the LCR twice. All chips > 8250 have a scratch pad and all 16550A+ have a usable FIFO. I attached the diff for reactos/drivers/dd/serial/legacy.c. BTW: I'm sorry about it but my editor always changes TABs to spaces ... Regards, Mark Index: drivers/dd/serial/legacy.c =================================================================== --- drivers/dd/serial/legacy.c (revision 14202) +++ drivers/dd/serial/legacy.c (working copy) @@ -1,72 +1,101 @@ /* $Id: * * COPYRIGHT: See COPYING in the top level directory * PROJECT: ReactOS kernel * FILE: drivers/bus/serial/legacy.c * PURPOSE: Legacy serial port enumeration * * PROGRAMMERS: Hervé Poussineau (poussine(a)freesurf.fr) */ #define NDEBUG #include "serial.h" +#define SER_TYPE_NONE 0 +#define SER_TYPE_8250 1 +#define SER_TYPE_16450 2 +#define SER_TYPE_16550 3 +#define SER_TYPE_16550A 4 + +static BYTE +DetectPortType(PUCHAR BaseAddress) +{ + BYTE Lcr, TestLcr; + BYTE OldScr, Scr5A, ScrA5; + BOOLEAN FifoEnabled; + BYTE NewFifoStatus; + + Lcr = READ_PORT_UCHAR(SER_LCR(BaseAddress)); + WRITE_PORT_UCHAR(BaseAddress, (BYTE) (Lcr ^ 0xFF)); + TestLcr = (BYTE) (READ_PORT_UCHAR(SER_LCR(BaseAddress)) ^ 0xFF); + WRITE_PORT_UCHAR(BaseAddress, Lcr); + + /* Accessing the LCR must work for a usable serial port */ + if (TestLcr!=Lcr) + return SER_TYPE_NONE; + + /* Ensure that all following accesses are done as required */ + READ_PORT_UCHAR(SER_RBR(BaseAddress)); + READ_PORT_UCHAR(SER_IER(BaseAddress)); + READ_PORT_UCHAR(SER_IIR(BaseAddress)); + READ_PORT_UCHAR(SER_LCR(BaseAddress)); + READ_PORT_UCHAR(SER_MCR(BaseAddress)); + READ_PORT_UCHAR(SER_LSR(BaseAddress)); + READ_PORT_UCHAR(SER_MSR(BaseAddress)); + READ_PORT_UCHAR(SER_SCR(BaseAddress)); + + /* Test scratch pad */ + OldScr = READ_PORT_UCHAR(SER_SCR(BaseAddress)); + WRITE_PORT_UCHAR(SER_SCR(BaseAddress), 0x5A); + Scr5A = READ_PORT_UCHAR(SER_SCR(BaseAddress)); + WRITE_PORT_UCHAR(SER_SCR(BaseAddress), 0xA5); + ScrA5 = READ_PORT_UCHAR(SER_SCR(BaseAddress)); + WRITE_PORT_UCHAR(SER_SCR(BaseAddress), OldScr); + + /* When non-functional, we have a 8250 */ + if (Scr5A!=0x5A || ScrA5!=0xA5) + return SER_TYPE_8250; + + /* Test FIFO type */ + FifoEnabled = (READ_PORT_UCHAR(SER_IIR(BaseAddress)) & 0x80)!=0; + WRITE_PORT_UCHAR(SER_FCR(BaseAddress), SR_FCR_ENABLE_FIFO); + NewFifoStatus = READ_PORT_UCHAR(SER_IIR(BaseAddress)) & 0xC0; + if (!FifoEnabled) + WRITE_PORT_UCHAR(SER_FCR(BaseAddress), 0); + switch (NewFifoStatus) { + case 0x00: + return SER_TYPE_16450; + case 0x80: + return SER_TYPE_16550; + } + + /* FIFO is only functional for 16550A+ */ + return SER_TYPE_16550A; +} + static BOOLEAN SerialDoesPortExist(PUCHAR BaseAddress) { - BOOLEAN Found; - BYTE Mcr; - BYTE Msr; - - Found = FALSE; - - /* save Modem Control Register (MCR) */ - Mcr = READ_PORT_UCHAR(SER_MCR(BaseAddress)); - - /* enable loop mode (set Bit 4 of the MCR) */ - WRITE_PORT_UCHAR(SER_MCR(BaseAddress), 0x10); - - /* clear all modem output bits */ - WRITE_PORT_UCHAR(SER_MCR(BaseAddress), 0x10); - - /* read the Modem Status Register */ - Msr = READ_PORT_UCHAR(SER_MSR(BaseAddress)); - - /* - * the upper nibble of the MSR (modem output bits) must be - * equal to the lower nibble of the MCR (modem input bits) - */ - if ((Msr & 0xf0) == 0x00) - { - /* set all modem output bits */ - WRITE_PORT_UCHAR(SER_MCR(BaseAddress), 0x1f); - - /* read the Modem Status Register */ - Msr = READ_PORT_UCHAR(SER_MSR(BaseAddress)); - - /* - * the upper nibble of the MSR (modem output bits) must be - * equal to the lower nibble of the MCR (modem input bits) - */ - if ((Msr & 0xf0) == 0xf0) - { - /* - * setup a resonable state for the port: - * enable fifo and clear recieve/transmit buffers - */ - WRITE_PORT_UCHAR(SER_FCR(BaseAddress), - (SR_FCR_ENABLE_FIFO | SR_FCR_CLEAR_RCVR | SR_FCR_CLEAR_XMIT)); - WRITE_PORT_UCHAR(SER_FCR(BaseAddress), 0); - READ_PORT_UCHAR(SER_RBR(BaseAddress)); - WRITE_PORT_UCHAR(SER_IER(BaseAddress), 0); - Found = TRUE; - } - } - - /* restore MCR */ - WRITE_PORT_UCHAR(SER_MCR(BaseAddress), Mcr); - - return Found; + BYTE Type; + + Type = DetectPortType(BaseAddress); + if (Type==SER_TYPE_NONE) + return FALSE; + + if (Type==SER_TYPE_16550A) { + /* + * setup a resonable state for the port: + * enable fifo and clear recieve/transmit buffers + */ + WRITE_PORT_UCHAR(SER_FCR(BaseAddress), + (SR_FCR_ENABLE_FIFO | SR_FCR_CLEAR_RCVR | SR_FCR_CLEAR_XMIT)); + WRITE_PORT_UCHAR(SER_FCR(BaseAddress), 0); + } + + READ_PORT_UCHAR(SER_RBR(BaseAddress)); + WRITE_PORT_UCHAR(SER_IER(BaseAddress), 0); + + return TRUE; } NTSTATUS

20 years, 5 months

2
2
0 0

Update reported version to Windows 2000 (Service Pack?)

by Steven Edwards

Hi, Most of the dev team seems to be in agreement with bumping the reported version number to Win2k but if anyone has any objections speak now or forever maintain a patch. I need Win2k to be reported as the version number as many newer applications such as Office 2003 will not install unless that is the latest version. If you find any places where a function, resource or anything reports a value as NT4 or something ReactOS dependant please change it to match Windows 2000 behavior. Also I propose we just report Service Pack 4. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

20 years, 5 months

6
7
0 0

BootCD not Formatting

by Jason Filby

Hi all Currently when running a BootCD, if I ask to format the partition, I'm told that the setup could not complete. This is on trunk, not sure about the 0.2.6 build; can anyone confirm? Thanks Jason

20 years, 5 months

2
1
0 0

Explorer compile bug

by Wesley Parish

This is the text of the final few seconds before the compilation ran out of steam. The compiler is the standard MinGW32-gcc plus MinGW-g++, etc, in the MinGW-3.1.0-1.exe package; the computer's a Compaq 4000 Deskpro; the OS is MS Win95, bog-standard as far as I know. Wesley Parish C:/MINGW/include/c++/3.2.3/bits/stl_tree.h:1068: instantiated from `std::_Rb_t ree_iterator<_Val, _Val&, _Val*> std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare , _Alloc>::insert_unique(std::_Rb_tree_iterator<_Val, _Val&, _Val*>, const _Val& ) [with _Key = String, _Val = std::pair<const String, ICON_ID>, _KeyOfValue = st d::_Select1st<std::pair<const String, ICON_ID> >, _Compare = std::less<String>, _Alloc = std::allocator<std::pair<const String, ICON_ID> >]' C:/MINGW/include/c++/3.2.3/bits/stl_map.h:262: instantiated from `std::_Rb_tre e<_Key, std::pair<const _Key, _Tp>, std::_Select1st<std::pair<const _Key, _Tp> > , _Compare, _Alloc>::iterator std::map<_Key, _Tp, _Compare, _Alloc>::insert(std: :_Rb_tree<_Key, std::pair<const _Key, _Tp>, std::_Select1st<std::pair<const _Key , _Tp> >, _Compare, _Alloc>::iterator, const std::pair<const _Key, _Tp>&) [with _Key = String, _Tp = ICON_ID, _Compare = std::less<String>, _Alloc = std::alloca tor<std::pair<const String, ICON_ID> >]' C:/MINGW/include/c++/3.2.3/bits/stl_map.h:225: instantiated from `_Tp& std::ma p<_Key, _Tp, _Compare, _Alloc>::operator[](const _Key&) [with _Key = String, _Tp = ICON_ID, _Compare = std::less<String>, _Alloc = std::allocator<std::pair<cons t String, ICON_ID> >]' explorer.cpp:398: instantiated from here C:/MINGW/include/c++/3.2.3/bits/stl_pair.h:88: invalid use of undefined type ` struct String' utility/utility.h:737: forward declaration of `struct String' make[1]: *** [explorer.o] Error 1 make: *** [explorer] Error 2 -- Clinersterton beademung, with all of love - RIP James Blish ----- Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people.

20 years, 5 months

2
2
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev