- Ros-dev - ReactOS.org

by Luke Kenneth Casson Leighton

regarding your offer to help with LSASS.... GREAT! because, coincidentally, this is exactly one of the areas required to tie in MSV1_0.DLL which will be a registererer with the LSASS, and MSV1_0.DLL is where all the nt authentication stuff happens. great, great. okay, here's something i found which describes the process, it looks pretty damn good: http://www.coresecurity.com/common/showdoc.php?idx=87&idxseccion=11 now, here's the bit that you _don't_ have to do: you do NOT have to do _any_ of the bits _behind_ "access the sam database". all of that is already written for you - in samba tng. i've had a _brief_ look at the implementation of lsass in reactos, and i believe it to be pretty good. it's just that there are no "registerers" e.g. there is no implementation of MSV1_0.DLL. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

19 years, 9 months

1
0
0 0

Can someone send me the MS sound blaster driver example code?

by Andrew "Silver Blade" Greenwood

Someone sent me this a while back, but I lost it. Basically I believe it was from a MS DDK, and it contained code for MMDRV.DLL and SNDBLST.SYS. At the time I was feeling lazy and just clumsily hacked in whatever I felt like, without any order to what I was doing. I want to have another stab at it, by reviewing the existing code, documenting it for my own understanding, and then writing my own solution. So if someone could send me those files, I'd appreciate it! -Andrew PS: The files in question were NOT obtained from the leaked Windows source code.

19 years, 9 months

1
0
0 0

Frequent commits?

by Reuben Perelman

Lately I've seen a lot of updates to svn. Is it just a lot of work being done, or is there some type of revert war?

19 years, 9 months

3
3
0 0

Re: [ros-svn] [hpoussin] 17751: Fix build, by correcting include paths and updating xml files of USB components

by TwoTailedFox

Corrected, just as I was trying to work out while it wasn't compiling with Mingw ;) On 9/8/05, hpoussin(a)svn.reactos.com <hpoussin(a)svn.reactos.com> wrote: > Fix build, by correcting include paths and updating xml files of USB components > > > Added files: > trunk/reactos/drivers/usb/usbport/usbport.def > > Updated files: > trunk/reactos/drivers/usb/miniport/linux/pci_hal.c > trunk/reactos/drivers/usb/miniport/usbohci/ohci-hcd.c > trunk/reactos/drivers/usb/miniport/usbohci/ohci_main.c > trunk/reactos/drivers/usb/miniport/usbohci/usbohci.xml > trunk/reactos/drivers/usb/miniport/usbuhci/uhci-hcd.c > trunk/reactos/drivers/usb/miniport/usbuhci/uhci.h > trunk/reactos/drivers/usb/miniport/usbuhci/usbuhci.xml > trunk/reactos/drivers/usb/usbhub/usbhub.h > trunk/reactos/drivers/usb/usbhub/usbhub.xml > trunk/reactos/drivers/usb/usbport/buffer_simple.c > trunk/reactos/drivers/usb/usbport/config.c > trunk/reactos/drivers/usb/usbport/core_drivers/usbkey.c > trunk/reactos/drivers/usb/usbport/core_drivers/usbmouse.c > trunk/reactos/drivers/usb/usbport/hcd-pci.c > trunk/reactos/drivers/usb/usbport/hcd.c > trunk/reactos/drivers/usb/usbport/hub.c > trunk/reactos/drivers/usb/usbport/message.c > trunk/reactos/drivers/usb/usbport/urb.c > trunk/reactos/drivers/usb/usbport/usb-debug.c > trunk/reactos/drivers/usb/usbport/usb.c > trunk/reactos/drivers/usb/usbport/usbcore.c > trunk/reactos/drivers/usb/usbport/usbport.xml > > Deleted files: > trunk/reactos/drivers/usb/usbport/usbcore.def > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-svn > -- "I had a handle on life, but then it broke"

19 years, 9 months

1
0
0 0

Re: [ros-svn] [ion] 17727: Implement NTDLL's CSR routines in a compatible way. Fix prototypes, argument count, deprecated functions and new functions. Some functions will not work (or are designed not to work) fully until the new CSR is committed, but they keep the same functionality as the previous versions (no regressions found; tested with cmd, cmt, putty, telnet, ps). Also added NtSecureConnectPort.

by Hartmut Birr

Hi, this changes does break booting for me. I get an error message: (subsys\csrss\api\wapi.c:198) CSR: NtListenPort() failed, status=c0000005 - Hartmut

19 years, 9 months

3
3
0 0

Replacement for Bitstream fonts

by Mikhail Y. Zvyozdochkin

Hi All. I think it's a good idea to use Dejavu fonts http://dejavu.sourceforge.net/ instead Bitstream Vera. Reasons are: - it based on Bitstream fonts (1.10); - it's distributing under SAME license; BUT - it supported MUCH more unicode pages than original Bitstream fonts; it was main goal of Dejavu Projects "to provide a wider range of characters", to support various languages and codepages. In particular, I tried to activate Russian language in ReactOS 0.2.7-REL with Dejavu fonts. It working correctly without any proprietary fonts :). Unicode coverage table: http://cvs.sourceforge.net/viewcvs.py/*checkout*/dejavu/dejavu-fonts/unicov… At this September they want make new release, 1.14. I think, it new version may be integrated with ReactOS 0.3 :) WBR, DarkHobbit

19 years, 9 months

1
0
0 0

problem with current svn

by Hartmut Birr

Hi, I'm trying to compile ros on ros with the current svn tree. It isn't possible. After some time, it fails with a message cannot execute 'bla bla'. The build does corrupt the file system. If I run chkdsk from w2k I get many messages about multiple files like 'wrc.ex'. It seems that something is wrong with the string functions. - Hartmut

19 years, 9 months

3
5
0 0

RE: Ros-dev Digest, Vol 13, Issue 14

by Lucio Diaz

Sorry, but i still cant see the point. 0.2.7 is a release, and thus is oriented to the user (maybe power user or fan at this moment), to test and play around. Users, like me, dont go to bugzilla cause most of us can not make sense of all that techicall information. I knew there was a problem, a blocking problem for anyone trying to install the OS in real hardware and i wrote about it where a user (like me) may find out, in the wiki. I can not understand why you become angry. I am just filling some documentation for the user, and that is the only whay i can colaborate ( i doubt you would apretiate my little pascal and delphy coding skill). Known problems is for that... enumerating the known problems of a determinated version, while 0.2.7 is the last version i consider relevant the fact that it can not be installed in Real Hardware. I wish i could debug and find the problem, but i dont have the experience or the tools to do so. with my best wishes to the team, Lucio Diaz. WaxDragon wrote--> Message: 5 Date: Wed, 7 Sep 2005 13:15:19 -0400 From: WaxDragon <waxdragon(a)gmail.com> Subject: Re: [ros-dev] RE: Ros-dev Digest, Vol 13, Issue 13 To: ReactOS Development List <ros-dev(a)reactos.com> Message-ID: <9b0d5f3205090710157abc163f(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 I think you missed the point. I'm talking about http://www.reactos.com/wiki/index.php/Known_Problems When calling things "known problems" I want bugs for them. I'm going to assume you are talking about this known problem: http://www.reactos.com/bugzilla/show_bug.cgi?id=688 Which was even noted on the 0.2.7 changelog page: http://www.reactos.com/wiki/index.php/ChangeLog-0.2.7#Known_Bugs PLEASE, if you write ANYWHERE that ReactOS has a "known bug" please provide a link to the bug in bugzilla. If there is no bug in BugZilla, then there is a great possibility the Testing team doesn't know about it. By filing bugs, we can reduce the amount of duplicate effort required to fix said bug. When filing bugs, please review http://www.reactos.com/wiki/index.php/File_Bugs first. With that out of the way, I know that noone has looked at that bug since 0.2.7 was released. If you can gather any useful info about the hardware (the i8042 controller specifically) that you are experienceing the problem with, update the bug, this may help with getting it resolved. WD PS. I'm very tempted to make the "Know Problems" page go away, or heavily modify it. ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

19 years, 9 months

1
0
0 0

RE: Ros-dev Digest, Vol 13, Issue 13

by Lucio Diaz

> Message: 1 > Date: Tue, 6 Sep 2005 08:42:13 -0400 > From: WaxDragon <waxdragon(a)gmail.com> > Subject: Re: [ros-dev] Bootcd installation failure > To: ReactOS Development List <ros-dev(a)reactos.com> > Message-ID: > <9b0d5f32050906054215dd322b(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Well, I have no idea what Lucio means by that "known > problem", since > he isn't very specific. 17600 is not even close to > where we forked > 0.2.7. I remember there were some problems around > then. Try 17604, I > personally tested that rev and it seemed to work ok. > > In the future, if you are going to call something a > "known problem" > please link to the bug in Bugzilla. If the "known > problem" isn't in > bugzilla, it isn't "known" as far as I care. > > Thanks > WD > I reported it in both the general and dev mailing lists, it happens in real hardware in two complitely diferent computers, one Intel and one AMD, with completely diferent OSes as base instalation and both with previus sucesfull reactos instalations. In both the instalation CD hangs before installing anything (maybe reading the partitions?) to the Hard drive. Not many people test reactos in Real Hardware, but i was told the problem was already known. I have not tested the SVN since long so i can not say if it is solved. Still it is a KNOW reproducible problem of 0.2.7. With best regards, Lucio Diaz. ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

19 years, 9 months

3
2
0 0

Re: [ros-dev] Re: [ros-svn] [hbirr] 17665: - Copy the map registers to the buffer only, if they are used (in IoFlushAdapterBuffers).

by Filip Navara

19 years, 9 months

1
0
0 0

Re: [ros-diffs] [gdalsnes] 17713: make co_WinPosShowWindow take pWnd, not hWnd

by Royce Mitchell III

gdalsnes(a)svn.reactos.com wrote: > > > >+ //faxme: temp hack >+ UserDereferenceWindowObjectCo(Window); >+ > > What's your fax #? :P

19 years, 9 months

1
0
0 0

Re: [ros-svn] [hbirr] 17665: - Copy the map registers to the buffer only, if they are used (in IoFlushAdapterBuffers).

by Filip Navara

hbirr(a)svn.reactos.com wrote: >- Copy the map registers to the buffer only, if they are used (in IoFlushAdapterBuffers). >- Do not use the byte offset into the page from a given buffer if the map registers are used, > because the caller didn't request for one additional register in the call to IoAllocateAdapterChannel > and it will not work for a 64k buffer. > > Sorry, but these changes are wrong. I won't argue that there isn't bug, but you're just workarounding it. - At first, the UseMapRegisters variable you added to MAP_REGISTER_ENTRY structure isn't needed. IoFlushAdapterBuffers can determine the information itself and the case was clearly marked as UNIMPLEMENTED and FIXME. - The byte offset is added for a reason. I know the stuff that it is supposed to solve is broken atm, but the rationale is that there can be more IoMapTransfer calls and together with MAP_REGISTER_ENTRY->Counter you can setup more transfers... It's explained in http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281-92cdfe…. I certainly welcome any help and review of the DMA code and I'll try to add comments where appropriate, but I would like to discuss these changes first on the Mailing List / IRC / mail since this piece of code is pretty complex and any changes are prone to break some feature... - Filip

19 years, 9 months

2
5
0 0

RE: [gdalsnes] 17695: naming changes:

by Ge van Geldorp

> From: gdalsnes(a)svn.reactos.com > > naming changes: > -remove annying "Object" from variables. prepend handles with > "h" instead. > -rename window->Self -> Window->hSelf I hope we're not going to convert everything to Hungarian notation? Personally I think that's both ugly and useless. Gé van Geldorp.

19 years, 9 months

2
1
0 0

Bootcd installation failure

by Gge

In the wiki page related to Known problems for R..2.7 -->> http://www.reactos.com/wiki/index.php?title=Known_Problems&curid=786&diff=0… , it is mentionned that "The install CD wont install reactos in some computers. LiveCD might boot in the same computers without problems" I cannot Boot using Boocd based on svn 17600 and created using the recommended "Built Environment" as indicated in the Wiki -->> http://blight.reactos.at/reactos-be/ReactOS%20Build%20Environment%200.1-3.4… The problem is reproductible on my 2 computers in real hardware , as per debug messages below. => Is it the same problem ? (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\sndblst.sys (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\mpu401.sys (registry.c:220) Can't read registry: c0000034 (registry.c:231) Manually set defaults (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\xboxvmp.sys Packet: DriverEntry (ndis/protocol.c:678)(NdisRegisterProtocol) Called. (ndis/protocol.c:685)(NdisRegisterProtocol) NDIS 3 protocol attempting to register (ndis/protocol.c:764)(NdisRegisterProtocol) Opening configuration key: \Registry\Machine\System\CurrentControlSet\Services\PacketDriver\Linkage (ndis/protocol.c:773)(NdisRegisterProtocol) Unable to open protocol configuration NPF: Failed to register protocol with NDIS (ntoskrnl\ob\object.c:157) Invalid Size: 18 or Attributes: 1 (ntoskrnl\ob\object.c:243) Failed to capture, cleaning up (ntoskrnl\ob\object.c:825) Capture failed (init.c:108) SM: InitSessionManager: failed to create \SmApiPort (Status=c000000d) (ntoskrnl\ob\wait.c:246) Returning: 1 KeBugCheckEx at ntoskrnl\ex\init.c:716 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. Technical information: *** STOP: 0x00000071 (0x00000001,0x00000000,0x00000000,0x00000000) Frames: <ntoskrnl.exe:24c6 (ntoskrnl/ke/bug.c:498 (KeBugCheckEx))> <ntoskrnl.exe:b8a5f (ntoskrnl/ex/init.c:716 (ExpInitializeExecutive))> <ntoskrnl.exe:6706 (ntoskrnl/ke/main.c:100 (KiSystemStartup))> <ntoskrnl.exe:b684e (ntoskrnl/ke/main.c:294 (_main))> <ntoskrnl.exe:104b ({standard input}:47 (_section_alignment__))> Regards Gge

19 years, 9 months

2
1
0 0

RE: [gdalsnes] 17671: -surround user part (most of it) with asingle lock (currently a mutex, but will be a resource). other now useless locks will be removednext.

by Ge van Geldorp

> From: gdalsnes(a)svn.reactos.com > > Updated files: > trunk/reactos/subsys/win32k/include/win32k.h Perhaps you forgot to commit a file? [PCH] obj-i386/subsys/win32k/w32k.h.gch In file included from subsys/win32k/w32k.h:44: subsys/win32k/include/win32k.h:12:28: include/ntuser.h: No such file or directory make[1]: *** [obj-i386/subsys/win32k/w32k.h.gch] Error 1

19 years, 9 months

1
0
0 0

Poll Results

by Alex Ionescu

Hi, I've compiled the results from the poll that I posted on the forum (some of you may know about it, some may not, that's fine, the presentation is quite clear about it) and published it as a slide presentation in four formats: Open Document Format: (For OO 2.0): http://www.relsoft.net/ReactOSResults.odp Adobe Acrobat Format: http://www.relsoft.net/ReactOSResults.pdf Macromedia Flash Format: http://www.relsoft.net/ReactOSResults.swf Microsoft Powerpoint Format: http://www.relsoft.net/ReactOSResults.ppt I hope I've been diverse enough with the formats ;) Best regards, Alex Ionescu

19 years, 9 months

5
4
0 0

RE: [ros-svn] [ion] 17650: - Fix kernel32 and ntoskrnl build issues.

by Ge van Geldorp

> From: ion(a)svn.reactos.com > > - Fix kernel32 and ntoskrnl build issues. > - Define public version of DEVOBJ_EXTENSION in DDK. Ok, I have to wonder, did you bother to do ANY testing on your DEVOBJ_EXTENSION/EXTENDED_DEVOBJ_EXTENSION changes at all? Like, uhm, just trying to boot? 'cause it seems very unlikely to me that you were able to successfully boot. IoCreateDevice allocates only enough room for DEVOBJ_EXTENSION, but the allocated pointer is cast to PEXTENDED_DEVOBJ_EXTENSION (a much larger struct) all over the place, so we're reading/writing outside allocated memory in a zillion places. Gé van Geldorp.

19 years, 9 months

2
2
0 0

Re: [ros-svn] [hpoussin] 17639: Implement SetComputerNameExA/W

by Hartmut Birr

hpoussin(a)svn.reactos.com wrote: >Implement SetComputerNameExA/W > > >Updated files: >trunk/reactos/lib/kernel32/misc/computername.c >trunk/reactos/lib/kernel32/misc/stubs.c >trunk/reactos/w32api/include/winbase.h > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > > Hi, this implementation breaks installing reactos. It does only accept 3 of 8 types to setting the computer name. The setup uses ComputerNameNetBIOS, which isn't implemented. - Hartmut

19 years, 9 months

1
0
0 0

Re: [ros-diffs] [hpoussin] 17641: Allow compilation of fs_rec driver with MSVC

by Alex Ionescu

hpoussin(a)svn.reactos.com wrote: >Allow compilation of fs_rec driver with MSVC > > > > > >+#ifdef _MSC_VER >+#define STDCALL >+#endif >+ > > This isn't really correct...what are you trying to do? Best regards, Alex Ionescu

19 years, 9 months

1
0
0 0

State of the Repository September 2nd 2005

by WaxDragon

First, some stats: In August there were: * 676 Commits * 49 bugs opened * 139 bugs touched * 44 bugs closed Looking over the logs, here are some of the big and/or highly visible changes: *sedwards bought in some winetests (in regtests/winetests) This resulted in some immediate fixes *navaraf replaced the pesum tool with pefixup *sedwards brought dosfsck in late July, and enabled writing in August. Still needs testing, but seems to work. *brandonturner implemented windows style tab completion, replacing the bash style we had before. I believe this can be toggled. Also, cmd has really been getting attention from brandonturner and greatlord, may little bugs have been fixed. Thanks guys! *ion removed the third-party driver info from the hives and placed them in the wiki. I felt this was a good move, since it will motivate people to fix/implement driver installation. The interim solution was going to be creating .reg files to import or just re-add the info to your local hives. This had the side affect of breaking our vmware video driver installer. After some bugfixes, vmwinst now loads the driver, but ReactOS seems unable to set the resolution. *navaraf fixed the i8042prt detection, partially fixing the AllocConsole bug. This was merged to 0.2.7 and we shipped it as a known bug. We have received just a few reports of the AllocConsole bug on IRC, so it seems to work for most. *navaraf fixed the translation of extended keys, fixing my bug hilighting text with Shift+Arrow keys. Merged to 0.2.7, thanks Filip! *ion twiddled the priority code, fixing some winetests * ea returned to work on subsystem code * gdalsnes fixed ftol, progressing Abiword 2.0.3 * ion corrected the LPC Message Structures * amunger fixed the freeldr.ini Timeout ;0) * hbirr fixed several bugs that were blocking selfhosting (ros-on-ros compilation) I am able to compile ros on ros with the patch from the selfhosting bug. Thanks Hartmut! * We found that release builds of msi.dll allow the VMWare Tools installer to run, several bugs were fixes in relation to this. Thanks everyone! *fireball got USB keyboards working on the XBOX, along with various USB fixes * ion cleaned up the NDK headers * gvg added the autogenerated DIB code for 32 and 8 bpp * navaraf reimplemented the HAL DMA routines * There was some work on the MSVC backend, thanks to sedwards and royce * navaraf fixed some bugs in NDIS * navaraf tweaked the explorer taskbar, fixing the misaligned buttons under windows This exposes a bug in ReactOS, so the taskbar looks a little off now. 17604 seems like a good way to start September: * shutdown bug fixed * Default Abiword 2.2.9 install works * Abiword 2.2.9 runs and opens documents. * 7-Zip 4.23 Installer works * 7-Zip GUI has several issues * 7za.exe (cli) works * OO installer unpacks, but bombs a few pages in * notepad opens and saves files properly * winemine doesn't work * solitare works * ps works * mc seems like it has issues (I'm not a user per se.) * format still doesn't work * calc doesn't even start * cat works * regedit can set values * wallpaper stays if set in registry, not if using desk.cpl Networking: * qemu networking fixed * ftp fixed * ping works * ipconfig has issues * finger works * "route print" works * netstat doesn't work * ncftp has issues * hostname works * arp doesn't work * mIRC installer works, fails creating icons (or start menu I don't remember) * mIRC has several issues, can't get it to connect and the usual implementing new functions, syncing to wine, and bugfixes. Overall 17604 "feels" good and stable. I was able to use the command line without too much trouble, installed many packages, and only saw a few BSODs, mainly in the network code. I think that is a pretty good summary, and since it's been the day of long emails, I won't go any further. Please reply to this email if there is something I forgot, overlooked, got wrong, etc.. WD -- #irc.freenode.net #reactos 01:03PM <filip2307> i don't know about any bug 01:04PM <filip2307> none exist 01:04PM <filip2307> ReactOS is prefect

19 years, 9 months

3
4
0 0

ReactOS Revision ISOs

by Sylvain Petreolle

Hi all, After doing some regression tests with SVN ISOs, it appears some are missing/badly numbered. Here is the updated list. ReactOS-trunk-rxxxxx.iso -> real revision ReactOS-trunk-r17465.iso -> r17560 ReactOS-trunk-r17466.iso -> r17539 ReactOS-trunk-r17468.iso -> r17559 ReactOS-trunk-r17471.iso -> r17567 ReactOS-trunk-r17472.iso -> r17553 ReactOS-trunk-r17473.iso -> r17565 ReactOS-trunk-r17478.iso -> r17552 ReactOS-trunk-r17479.iso -> r17569 ReactOS-trunk-r17490.iso -> r17572 ReactOS-trunk-r17495.iso -> r17553 These files did show the same version (md5sum proved they are different) ReactOS-trunk-r17480.iso -> r17564 ReactOS-trunk-r17482.iso -> r17564 ReactOS-trunk-r17476.iso -> r17566 ReactOS-trunk-r17483.iso -> r17566 ReactOS-trunk-r17489.iso -> r17566 Kind regards, Usurp (aka Sylvain Petreolle) humans are like computers, yesterday the BIOS was all - today its just a word

19 years, 9 months

2
3
0 0

SMSS & LSASS: Service Status

by Rick Langschultz

Hey all, I am thinking about starting, or helping write the SMSS and/or LSASS implementation on ReactOS. I was wondering what I can help with, or help someone to do the work... Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

19 years, 9 months

6
5
0 0

Re: [ros-diffs] [navaraf] 17604: Check for Request == NULL.

by Hartmut Birr

navaraf(a)svn.reactos.com wrote: >Check for Request == NULL. > >Modified: trunk/reactos/ntoskrnl/lpc/reply.c > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/ntoskrnl/lpc/reply.c* > >--- trunk/reactos/ntoskrnl/lpc/reply.c 2005-09-02 11:29:40 UTC (rev 17603) >+++ trunk/reactos/ntoskrnl/lpc/reply.c 2005-09-02 13:12:44 UTC (rev 17604) >@@ -263,6 +263,12 @@ > > Request = EiDequeueMessagePort(Port); > KeReleaseSpinLock(&Port->Lock, oldIrql); > > > >+ if (Request == NULL) >+ { >+ ObDereferenceObject(Port); >+ return STATUS_UNSUCCESSFUL; >+ } >+ > > > if (Request->Message.u2.s2.Type == LPC_CONNECTION_REQUEST) > { > PORT_MESSAGE Header; > > Hi, I think that this fix doesn't solve the real problem. The caller waits on a semaphore and the semaphore is only signaled if a message is in the queue. This means, the caller can't get a NULL pointer from EiDequeueMessagePort(). The real problem is anywhere in KeWaitForSingleObject, which does return STATUS_USER_APC for a non alertable wait. That is wrong. - Hartmut

19 years, 9 months

2
1
0 0

New Webserver System

by Rick Langschultz

I was kicking around the idea of installing a jabber server on my companies server to allow instant messaging on the local area network. Would reactos.com be willing to do something like that or is that too far out of the scope of the project. I was going to use OpenLDAP for authentication and save all of the conversations in XML files in both senders and recipients home folders. I also was going to write an XSL to display those messages. I think this would help out both developers and users of reactos. Including future RosMessenger or something like that... Just a though... Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

19 years, 9 months

14
18
0 0

Re: proper nt-style authentication (reactos, wine, samba tng)

by Luke Kenneth Casson Leighton

andrew bartlett, your sarcasm is totally inappropriate, and you are completely out of line, and you damn well know it. get a grip, and if you cannot do so, do not embarrass yourself or the reputation of the samba team, which you represent by utilising a "samba.org" email address, by replying at all. i also cannot reply and tell you this because of a decision made on the 15th december 2004 by the samba team to block all email sent by me to samba.org and to treat any such attempts as "net abuse". if you pick up this message on the mailing lists i hope that you will, should you wish to make useful contributions to this discussion, provide a suitable email address to which i can reply. anyway: in order to move discussions _forward_ rather than put it on an actively hostile footing, i will rewrite your message in a more appropriate manner and i trust that this meets with your approval. i will then reply to it. "dear luke, thank you for raising this issue. your message is a bit long, so i will skip most of it and mention just one thing. i trust that you are aware that NTLM authentication has been provided for quite some time to external services, in a number of ways. as you helped design one of those methods (the winbind_auth_crap :) and guided tim in its implementation, i am puzzled by the fact that it was not mentioned in your message. there is also an additional method which has been developed in samba 3, called ntlm_auth, which has even been utilised by a SOC Google student. both these methods avoid reimplementation of NTLMSSP: what therefore are you proposing that is, if at all, different from this? i don't understand: perhaps you could explain? anyway, it is good to hear from you and your design input even if it is a little bit mad is always welcome. best regards, andrew bartlett." now, pretending that you have written the above paragraphs instead of the ones below, i will proceed. without sarcasm and without endeavouring to be totally and blatantly and unnecessarily cruel. dear andrew, thanks for replying, okay. i re-read my message several times and i _knew_ i had missed something out - explicitly mentioning winbind. sorry! and no, i wasn't aware of ntlm_auth: it's good to hear of that because yes it might prove useful. no, of course i am not advocating that NTLMSSP be reimplemented: i will clarify this later in this reply. i should be clear (and this will help rob as well) that the specific focus of my message was directed towards _reactos_ not towards wine (per se). the requirements are therefore quite different. yes, for _wine_ - you (and rob) are absolutely correct: ntlm_auth and winbindd are perfectly adequate. the reason why? samba can be run ON THE SAME MACHINE. samba is a unix service: wine is a win32 emulation layer running _on unix_. the reason why that is inappropriate for reactos? samba cannot run on a win32 platform. therefore any attempt to contact a unix service will require implementation of a POSIX subsystem in reactos as a primary requirement!!! ... oops :) it's that straightforward. there is also a second difference (which isn't anything to do with what you mention - use of winbind or ntlm_auth) which is to do with the implementation: in reactos, things have to be done "properly" in this area (authentication) - and that means implementing an LSASS (lsa security service) MSV1_0.DLL and registering it with the LSASS running in NTOSKRNL. i do not know what has been picked / decided upon for Wine, but for reactos MSV1_0.DLL is definitely the way forward. what else is relevant that i may have missed... oh, yes: samba tng's winbindd. i added an extra "method" to winbindd, which was required for freedce's "ntlmsspauth.so". winbindd pre-modifications (and therefore also the version in samba afaik) does not contain a means to utilise NT+LM hashes plus domain name in unicode plus username in unicode, and it most certainly doesn't return a NET_USER_INFO_3 structure. this is an absolute critical requirement for "authorisation" purposes - not least because the NET_USER_INFO_3 structure, as you are undoubtedly aware (but others might not be so i mention it for completeness), contains the 16-bit "session key". it also contains the group SIDs etc. which are again essential to be returned to the LsaLogonUser (and LsaLogonUserEx) functions - see lsa.c in ReactOS code. so, anyway, this is what i added to samba tng's winbindd and also to a client-side function which freedce's ntlmsspauth.so module could then use. i do not know what nltm_auth does so i could not advise you as to whether it would be appropriate: perhaps you could help out by pointing people to some appropriate documentation on the ntlm_auth API, in order to evaluate whether it would be suitable (possibly even for reactos: i won't know until i see the API) okay. what else. oh, yes. the use of ntlm_auth and/or winbindd to "outsource" authentication is, i believe, a "temporary" measure, that allows the parallel development and maturisation of Wine / ReactOS specific code (in the case of ReactOS, that's MSV1_0.DLL) _without_ having to pull in a shed-load of code. the API is basically this: send (in unicode) a plaintext password, a domain name and a username, and receive a yes/no answer along with a NET_USER_INFO_3 structure, from which the session key and group sids can be "pulled". there's also the second function LsaLogonUserEx which is i believe "send NT+LM hashes, plus unicode domain name, unicode username, and receive..." but it would take a little reverse-engineering to double-check. so yes, in conclusion, i believe that the use of ntlm_auth and/or winbind _may_ be appropriate for Wine, is temporarily appropriate for proof-of-concept in ReactOS, but for final code in ReactOS, definitely not. that's the gist: hope this helps clarify things. l. On Fri, Sep 02, 2005 at 11:25:36PM +1000, Andrew Bartlett wrote: > On Fri, 2005-09-02 at 01:39 +0100, Luke Kenneth Casson Leighton wrote: > > I will leave the rest of this mail well aside, but I just wanted to > clarify exactly how long we have been providing NTLM authentication > services to external projects: > > > 2) write a lovely insecure method of "outsourcing" the username, > > domain and password to an external server - Samba TNG - which performs > > the authentication on your behalf and gets back "real" data. > > > > this could be done simply with a TCP connection, throw the data > > in-the-clear over to a simple temporary shim service blah blah, > > bob's your uncle. > > Like, say the winbind_auth_crap (thank Mr Potter for the name) function > in Samba's winbindd client interface, used successfully by external > projects (Squid in particular) since Samba 2.2? > > Or better still (avoiding reimplementing NTLMSSP) by calling ntlm_auth > (shipped with Samba 3.0 since release)? Oh wait, we hooked up a Google > SOC student to do just that, and it's working well! :-) > > Andrew Bartlett > > -- > Andrew Bartlett http://samba.org/~abartlet/ > Samba Developer, SuSE Labs, Novell Inc. http://suse.de > Authentication Developer, Samba Team http://samba.org > Student Network Administrator, Hawker College http://hawkerc.net -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

19 years, 9 months

1
1
0 0

Re: [ros-diffs] [gdalsnes] 17607: mostly naming changes

by Alex Ionescu

Hi, Somewhere in these 14000+ lines, these: - PUSER_OBJECT_HDR hdr; + PUSER_OBJECT_HDR* ppHdr; "naming" changes are going to turn into bugs. I can only see 1000 lines of your patch, and I can already see it's more then just "naming changes". You changed a "pointer" to a "pointer of a pointer". From experience, I can tell you that somewhere in those 14000 lines, there's a place where you forgot to change the dereference to match the new definition. But how can I ever check? The diff isn't posted here, and doing it manually would waste my time. And it also shows me that this patch probably has a lot more then "naming" changes. This is as of now, I think the 4th or 5th gigantic patch in this branch with 1) Dubious changes 2) Changes stuck together (naming changes with code changes, etc) 3) Still no changelog. I am voicing my public disagreement/outcry with the way this branch is being handled. gdalsnes(a)svn.reactos.com wrote: >mostly naming changes > > typedef struct _USER_REFERENCE_ENTRY > { > SINGLE_LIST_ENTRY Entry; > > >- PUSER_OBJECT_HDR hdr; > > >+ PUSER_OBJECT_HDR* ppHdr; > > > } USER_REFERENCE_ENTRY, *PUSER_REFERENCE_ENTRY; > > > > > *[truncated at 1000 lines; 13185 more skipped]* Best regards, Alex Ionescu

19 years, 9 months

4
4
0 0

Cash for Trademark - reallocate Donation to huricane efforts?

by Steven Edwards

Hello, We still have the cash in the foundation account for the trademark paperwork. ($525) plus about a hundred in paypal donations not sent to the bank yet. Our lawyer and I have not compleated the paperwork (his slackness and mine) and I have not cut him a check. Some of us would like to put the trademark filing on hold and donate the funds to the RedCross. I would like to have a vote on it among anyone that is a user, tester, developer, or random fan that has donated to the project in the past. If there is a unanimous vote then I will transfer the funds that are in our bank account and whatever is in paypal to the RedCross. If there is a single objection then I will not. I know this project did not get behind the tsunami relief effort (Which we should have) so even if there is a not a unanimous vote for reallocating the foundation funds then I ask that each of you personally donate if you can to the RedCross. The United States Government has really fucked it up and the truth is not being reported on. Thanks Steven __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

19 years, 9 months

11
12
0 0

Re: [ros-dev] Cash for Trademark - reallocate Donation to huricane efforts?

by PM

why are you even posting this? if big floods come to .cz as it came few years ago, you'll send the foundation money to .cz? you should probably realize that there is also live outside USA. anyway, this is ridiculous ... please cut it. -- Best regards Petr Matousek ... when you stare at the sun, what do you see ...

19 years, 9 months

1
0
0 0

Re: proper nt-style authentication (reactos, wine, samba tng)

by Luke Kenneth Casson Leighton

hi, rob, thanks for responding. On Fri, Sep 02, 2005 at 12:05:24AM -0500, Robert Shearman wrote: > Luke Kenneth Casson Leighton wrote: > >that you - the wine team - continue to reinvent an non-interoperable > >version of MSRPC, for binary-level "DCOM" interoperabiltiy ONLY, > >demonstrates quite how just as bloody stupid you are being. that _can_ > >be taken as a compliment, as i genuinely i mean it with the greatest of > >respect. > > > > > > Ok, I want to condense your huge message into a numbered list of things > you say we need: wheeeeee :) > 1. Type marshaling. > 2. IDL compiler. > 3. RPC Server. more specifically, rpc server "infrastructure" from which to develop, create, compile run and support RPC servic_es_. this you gain in the quickest possible way from FreeDCE and in the grungiest possible way from either samba or samba tng. > 4. Authentication. > 5. Services (lsa, netlogon, samr, etc). yep. > Ok, so we are we at with Wine and ReactOS? > 1: We need to implement this anyway because, like you crudely put it, we > are in the crazy business of getting real code like InstallShield and > Office 2003 to work. muhahahahah. hey, Security-Enhanced ReactOS, anyone? :) > 2. We can either use MIDL and accept the problems that go with it (like > not generating code that will compile with gcc 4.0) or we can finish > implementing proxy support in widl. okay. the amount of effort required to modify dceidl to support binary-interoperability with MIDL i do not believe to be very large, but the key bit which _will_ take some expertise (i.e. there are better people than myself to do the job) is the adding of Win32 threading model support to FreeDCE. going down THIS path will GET you code that will compile with gcc 4.0 (and mingw32) AND it would be binary interoperable with MIDL. AND it would actually work, without having to reimplement type marshalling, which if you look at FreeDCE's marshalling/unmarshalling code is SEVENTY THOUSAND LINES of immensely complex code. > 3. We have support for named pipes in the RPC server, what is the "RPC server"? i do not know of such a beast :) > but Wine doesn't > support remote named pipes and AFAIK ReactOS doesn't either. This is not > a problem that should be solved by the RPC runtime. no. it has nothing to do with the RPC runtime. you write a plugin that implements thirty or so functions (which have names like open, write, close etc. funnily enough :) and then register it with the RPC subsystem (yeh, okay, probably the rpc runtime :) e.g. the named pipe transport is called ncacn_np - network computing architecture CoNnection-based named pipes. and then MSRPC clients and MSRPC services can simply utilise that transport automatically or by name. > 4. Kai and Juan are working on delegating NTLM authentication to Samba. ah. brilliant. that's exactly what i outlined as "stage 1" and it should be done by implementing MSV1_0.DLL, for use by LSASS, see LsaLogonUser in the ntoskrnl code, it's a stub at the moment, in the reactos code. > We still need to tie this in to the RPC server though. i do not know what you mean by the "RPC server". no such entity actually exists afaik. > That should be a trivial task in comparison. yes, which is why it is mentioned about 2/3 of the way through my document, as "stage 1". > Not sure how this will fit in on ReactOS. in NTOSKRNL the LSASS implementation, which then has MSV1_0.DLL register with it. i mentioned it in my document. see the two occurrences of LsaLogonUser in reactos code. > 5. Wine isn't really interested in having those types of servers, tough luck for them. nt domain services are a necessary and integral part of supporting win32, even in a stand-alone environment. wine has _bypassed_ the MSRPC bits by instead of utilising MSRPC to split client from server they have "linked" the client-side code with its server-side code, cutting out the MSRPC runtime altogether. due to the incredible way that MSRPC (actually DCE/RPC) is designed, it is perfectly feasible to do this sort of thing, and actually have your code work (just with no networking and no distributed capability) anyway. if the wine team cannot be convinced of the necessity of adding MSRPC into the mix then wine will pretty much remain in the dark ages of interoperability along the lines of "win95 with networking removed". > but it > would be nice for the client code for those to work. I'm not sure that > porting them from Samba would be fruitful as they would fundamentally > need to tie into the registry. yes? :) and? :) i have no problem with that. i'd _love_ to see a registry service implemented in samba tng and then utilised in a samrd to access an NT SAM hive :) it's the way that reactos has gotta go, basically. > So, what you are suggesting is that we instead port FreeDCE and use it > for 1-3 (and 4?). basically and ultimately - yep! BUT, butbutbut - remember, i did say that it is _not_ strictly necessary at the moment. there are ways - and it appears that you are already considering them - to cut down the amount of work required to "GetThingsWorking(tm)", as i described. > This while still having to implement (1) anyway > because of the applications I mentioned that need it. no, you don't have to. you hack FreeDCE into interoperability because it IS the rpc runtime. remember, microsoft adopts code wholesale if they can get away with it. they started from DCE 1.1 reference implementation and ported it to NT. FreeDCE _is_ the DCE 1.1 reference implementation - autoconf'd and modularised. > Then we get to > test two different MSRPC infrastructures and get to fix bugs in one > without it fixing any bugs in the other. Just porting FreeDCE seems like > a lot of work; okay, the reason why it seems that way is because i actually know what's involved and have described to you what's involved. if you described to me what you are endeavouring to do in reimplementing the rpc runtime, i can give you some time estimates on how long it will actually take, and i guarantee you it will make the amount of time i've outlined for porting FreeDCE look like a walk in the park by comparison. that's all. remember, i did EXACTLY the same thing. i looked at the OpenGroup's DCE/RPC documentation, and went "christ almighty i can't possibly be doing with all this" and ignored it. THREE YEARS LATER i was wishing in some ways that i hadn't. the learning curve however of doing on-wire interoperability gave me enough understanding to appreciate just how good dce/rpc really is, and quite how much work is involved. you would do well to LISTEN to that advice of someone who wasted three years of their life NOT listening to advice, who followed the same path as you are following (the not-invented-here path). it will save you a lot of time. you would do well to bite the bullet and utilise your wealth of experience and knowledge learned to-date as a means to "tie in" to the freedce code. you _have_ enough knowledge and expertise now to be able to do that. you alone rob have been dealing with rpc type libraries for, what, two years now? a function-by-function comparison of freedce and wine's rpc runtime will show EXACTLY the same functions, EXACTLY the same arguments, and i started to show you that some six months ago, remember? now there is the reactos project to take into account, too. > perhaps more work than implementing the remaining > features in our own MSRPC infrastructure, even when including the task > of finishing the IDL compiler. Maybe I am being blind, but it seems to > make sense just to carry on in the direction we are going with having > our own MSRPC implementation and being able to "dogfood" our > implementation (i.e. use it for our own proxies/stubs at the same time > as letting applications use it). there is an opportunity to save _everybody_ time, right across the project board. i have said this in 2000 on the samba mailing lists. i have said it on that mailing list discussion six months ago on the wine-devel lists. i am saying it now. freedce is the key to interoperability for samba, wine, reactos, because it is the same code that microsoft hacked into submission to make the services which samba, wine and reactos are independently implementing, without proper reference to each other. samba is implementing "on-the-wire" interoperability without the type-libary interoperability and without the IDL-level and runtime-level interoperability. wine and reactos are implementing "binary-level" interoperability and are avoiding IDL-level and on-wire-level interoperability (by suggesting to developers that they utilise MIDL.EXE) this is complete madness. wine will end up with 100,000 lines of hacked-together and incomplete code. samba has two hacked-together projects of about 100,000 lines of code each. samba tng has its own hacked-together and equally but differently incomplete implementation. whereas FreeDCE is 250,000 lines of code that provides IDL-level interoperability, on-wire level interoperability, and the things that it is missing - win32 threading support, modern (posix) threading support and exact byte-for-byte type library interoperability are TRIVIAL trivial TRIVIAL computer-science first and second year university projects by comparison. each time i mention this, the people implementing their own non-interoperable projects in their own little worlds get deeper and deeper into the shit. if i can't convince people that this is the way forward then i will simply have to give up and come back in five years and see how people are getting on. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

19 years, 9 months

1
0
0 0

proper nt-style authentication (reactos, wine, samba tng)

by Luke Kenneth Casson Leighton

[please note: due to its cross-discipline and cross-project nature, this message is going out to SEVERAL related project mailing lists. when replying, please take EXTRA caution not least because some of these lists are subscriber-only. also, please note: i _would_ post this also to the samba mailing lists but due to the fascist censorship in place since the 15th dec 2004, i am unable to do so. this is their decision and it is their loss. i am not asking you to respect that decision i am simply making you aware of it.] hi, out the woodwork i pop - not necessarily ready to chew anything because i know just how much work's involved, but what i did want to do was say "hi, i'm still here" and do a brain-dump of how authentication ideally needs to be implemented in reactos. at 2,600 words and 16k, this message is quite long and so i have placed a copy at http://lkcl.net/software/reports/reactos-auth.txt, just in case it doesn't make it past various mailing-list limits (i'll find out in a couple of minutes... :) it breaks down into a number of sections: 1) i describe the timescales and ways to cut them, along with some warnings and stuff. 2) amonst other stuff i outline some background as to why i am posting this to so many lists. 3) i outline a project plan and the dependencies and "optional" steps, 4) i describe a recommended implementation roadmap starting with the "minimum" requirements, and expand on some technical info and references i found, which would help with some of the "nice-to-have" steps. so. first. please do not be scared by how much work is involved, and how much code there is. it all hinges one ONE function and that one function... you are _not_ going to believe how much code that one function drags in, kicking and screaming, behind it. please also please i beg you DO NOT consider going "bleedin 'ellfire, that's so much frakkin work we can't POSSIBLY do it the way you describe, we MUST do it our own way, starting with what we know, love and have already started tackling, and can't possibly back out of what we've already done". should you choose to exercise the "NIH" option, i frakkin guarantee you that you will waste about five to eight years of your (collective) lives reinventing the wheel. "The Plan" outlined here will shave that down to about 12 to 18 months, utilising some SIX HUNDRED THOUSAND lines of pre-existing code, and later in this message i also outline a prioritisation of the necessary work to "cut down" the time to maybe about ... mmm... three or so months, by leaving out some of the "nice-to-have" stuff. actually... _all_ of the nice-to-have stuff :) that will at least "GetItWorking(tm)" and the rest of the bits can be considered at leisure once people go "god that's awful, we can't possibly leave it like that" and hopefully hopefully things will actually progress from there. remember - please: this stuff is sufficiently complicated such that you really can't afford the niceties such as "It Must Be Perfect (tm)" before it can be accepted. i've seen that shit before, and it's a baad mxxxxxxxer path to go down, especially with such complex and heavily interdependant reverse-engineering projects as reactos, wine, samba and freedce. anyway. fyi - before i begin, i should mention a couple of things: 1) this message also goes out the the apache devel mailing list (specifically the APR one) because the NT style authentication thing is the sort of thing that really _should_ be in a (special?) APR util library, along with "NT Named Pipes" - see http://en.wikipedia.org/wiki/NamedPipes one of the reasons why NT-style NamedPipes is _not_ in an APR util is because it is believed that NT-style NamedPipes do not fit the "least common denominator". by having the infrastructure outlined below, it is possible to move things "up one level" to the point where unix _has_ that denominononmination. also, if APR still has support for that god-awful program-running program called Win95, it would, with not much extra effort, be possible to port some reactos components to Win95 (!) such that ThePlan outlined here would make Win95 have proper NT-style authentication (!) now there's a horrible thought that will give MS and free software people nightmares both: upgrading Win95 by installing free software components at it. muhahahahah ahem. 2) i have filled in a number of pages on wikipedia.org. see http://en.wikipedia.org/wiki/User:lkcl. please take the time to review these pages, PLEASE help me with my totally biased "POV" (point-of-view) comments, by either editing the pages direct or by adding comments on the "talk" pages as appropriate. or alternatively dumping me in the nearest pond if ever you meet me. wikipedia is supposed to be encyclopedia-ic and some of my comments are anything but that. help!!! 3) please due to the quite broad distribution of this message across multiple mailing lists, please do NOT ask stupid questions like "what the hell do we need to use samba tng for, why can't we use samba in reactos"? and "why is this guy bothering us with this insane stuff?" and "how do i use killfiles?" or terry pratchett's - more specifically the librarian's favourite - "where has all the pie and custard gone?" please do your research: see if nothing else http://en.wikipedia.org/wiki/Samba_TNG_software and then start googling. anyway. onward. roughly in order of dependence, with "nice-to-have" status added as well: 1) port FreeDCE to Win32 - more specifically add in autoconf support for an alternative threading model - the one in reactos. no, this is not a joke: MSRPC is a critical part of NT infrastructure it's just that very few people are actually aware of this (including the US DoJ and the EU commission...) see http://www.google.co.uk/search?q=lkcl+wine+freedce for discussion links as to why - it's a long story and it took me several dozen messages spanning over many days to outline it in sufficient detail for it to be understood (mostly me getting things straight in my head...) status: "nice to have" but you will soon wish that you _did_ have it!!! there is also an opportunity to support Wine, here: essentially it's the same job, for DCOM, for proper "authentication" purposes in Wine just like in ReactOS... it's a long story. 2) remove dependence on "unix" security model from Samba TNG's services starting with samrd (perhaps by finishing off samrtdbd?) status: "essential". sub-projects: a) in Samba TNG, rework winbindd such that it is a REQUIRED service, and it has "modes" that, instead of "inventing" links between unix uids and nt sids, it reads smbpasswd and correlates unix uids with nt sids _just_ like is done now - but hard-coded through the awful code that has had to dieee since... about two weeks after i wrote it, back in 1999. this one's a long story but it's not actually required for reactos but _might_ be required for wine... status: "pretty much essential" but not for reactos but for making life easy to share tng development between reactos and unix. b) in Samba TNG, make the authentication code (smb-side and rpc server back-end-wise) contact winbindd BUT ONLY for resolving unix uids and unix gids - which is actually a VERY small task involving a few hundred lines of code. this goes back to the "SURS" stuff i wrote up in 1999 - but instead of a library it hands off the responsibility for sid<->uid+gid lookups to winbindd. it _may_ also be essential for Wine to operate correctly with authentication (which is a "stub" at the moment just like it is in reactos), to interoperate with other programs, to cache login credentials in order to do smb client-side operations, that sort of thing, under which circumstances, it will be necessary for Wine to have the same sort of thing. it's no big deal :) status: same as for 2a). c) in Samba TNG, abandon all use of hard-coded MSRPC stuff and utilise FreeDCE instead, and do a rewrite of all services, one by one (and because samba tng is modular, this _can_ be done one-by-one, checking MSRPC interoperability along the way between the "old" services, the "new" services, and also with NT itself). in and of itself, this critically depends on making DCEThreads reliable, though, or adding support (finally!) for POSIX threads. status: "non-essential" but you would soon end up wishing that you had :) 3) complete LsaLogonUser, add LsaLogonUserEx, in NTOSKRNL.DLL, and friends. my favourites. the LSASS stuff. these functions are quite simple: they are "redirectors" - a vector table of functions is required to be passed in, which includes things like "authenticate with my lovely service" and "free some memory". there are many LSASS sub-services: one of them is Netware, one of them is MSV1_0.DLL, one of them is Kerberos. there are others. LSASS is based on _exactly_ the same technique that dlopen does e.g in libdvdcss, and in freedce's ntlmsspauth.so, and in... mmm... the freedce transport module infrastructure and _many_ other projects ... except of course it's NT-based table of higher-order-functions not unix "dlopen()" ones. i'll stop trying to teach people to suck eggs, now *embarrassed* :) status: "essential". sub-projects: a) write an MSV1_0.DLL which registers with the LSASS service. this will utilise MSRPC functions that call into the Samba TNG "NETLOGON" service. there already exists "basic" functions inside Samba TNG that... well... it's a bit messy, but they work. the key function to be calling is cli_nt_login_interactive, and you will notice _very_ quickly from the arguments hey, some of those look... kinda... familiar!! see http://viewcvs.samba-tng.org/cgi-bin/viewcvs.cgi/tng/source/rpc_client/cli_… status: "essential." the "porting" bit of this code to FreeDCE i would classify as "non-essential" but again, you will soon wish that you _were_ using FreeDCE. that's basically it: there are other sub-projects such as turning the "Registry" code in ReactOS (or Wine) into an MSRPC service (yes, i did say pretty much everything that's anything critical in NT is an MSRPC service, didn't i? :) but they aren't "essential". i say basically it, but that ONE stupid function, cli_nt_login_interactive, drags in quite literally HALF A MILLION lines of code - 250,000 lines of it in FreeDCE, alone (which, like i said, could possibly be avoided but the hard-coded MSRPC stuff in samba tng is sufficiently awkward to make a rewrite utilising FreeDCE very attractive). what i would suggest is the following: 1) write an MSV1_0.DLL "test stub" in combination with completing the LSASS functions, which supports a username "test", domain of "test" and password of "test". code up a hard-coded "blob" - a NET_USER_INFO_3 structure - that contains the response / essential information of groups, gids, sids, user session key etc. see http://viewcvs.samba-tng.org/cgi-bin/viewcvs.cgi/tng/source/include/rpc_net… (note: i _did_ say it would be nice to utilise FreeDCE didn't i? well, the NET_USER_INFO_3 structure in that header file is a "messy" version that i recreated from off-the-wire back in about ... mmmm... 1997. there _do_ exist IDL-generated versions of this data structure, thanks to matthew chapman - NETLOGON.idl for example). once that works... 2) write a lovely insecure method of "outsourcing" the username, domain and password to an external server - Samba TNG - which performs the authentication on your behalf and gets back "real" data. this could be done simply with a TCP connection, throw the data in-the-clear over to a simple temporary shim service blah blah, bob's your uncle. 3) port samba tng's netlogond, samrd and lsarpcd to ReactOS. this is quite straightforward: about the only really essential "missing" bit is to tie the services in to "NT Named Pipes" rather than unix domain sockets. _but_ - they only need to be plugged in to a back-end transport which all services - any of samba tng's MSRPC services - would use. so there's a key bit of work needed - probably under 400 lines of code - and the rest should fall into place. this is where it would be SO much easier to be utilising FreeDCE. all that's needed would be to write a FreeDCE "transport" plugin for ReactOS - ncacn_np - and then you'd be DONE. it's a long story... hey, has someone implemented TransactNamedPipe() and CreateNamedPipe() in ReactOS? if not, it's quite straightforward to do, and it involves dropping opaque data blobs onto smbd (again, smbd ported to reactos...) i _did_ say it's a long story, didn't i? :) 4) finally: track down how "LsaLogonUserEx" works. LsaLogonUser utilises cleartext passwords. LsaLogonUserEx i BELIEVE utilises NT and LM password hashes, or some brain-dead encrypted variant thereof. once 1) is completed, then TA-DAAAAA!!! lib/secur/lsa.c's "LsaLogonUser" function actually gets REAL DATA! okay. notes: 1) regarding FreeDCE. see http://en.wikipedia.org/wiki/FreeDCE freedce is an interoperable version of MSRPC that is derived from EXACTLY the same source code (DCE 1.0 reference implementation) that is present in Windows NT. DCE/RPC was co-opted / adopted / borg-ified by microsoft to form the basis of NT domains because paul leach, a co-founder of apollo computers and originator of NCS which became DCE/RPC, ended up working for microsoft back at the time when dave cutler was doing the original NT 3.1. using FreeDCE is non-essential for small projects of less than about 8,000 lines of code. Samba TNG's MSRPC code comprises OVER ONE HUNDRED THOUSAND lines of code. that i carried on hand-crafting MSRPC packets for three years simply demonstrates quite how bloody stupid i am. that you - the wine team - continue to reinvent an non-interoperable version of MSRPC, for binary-level "DCOM" interoperabiltiy ONLY, demonstrates quite how just as bloody stupid you are being. that _can_ be taken as a compliment, as i genuinely i mean it with the greatest of respect. 2) regarding a strategy to "minimise" the amount of time needed to "Get Things Working". a) utilise samba tng as-it-is, porting it as-is to ReactOS (mingw32) b) utilise cli_nt_login_interactive() as-it-is. c) complete MSV1_0.DLL. this will be SUFFICIENT and would only take a few months. enhancements come later, roughly in this order: a) complete a port of FreeDCE to ReactOS, by beating DCEthreads to death and replacing it with Win32 (NT) threads - #ifdef style, autoconf style. b) locate NETLOGON.idl, samr.idl and lsarpc.idl from matthew chapman's stuff, or from "todd sabin's" http://razor.bindview.com, or from the samba web site. actually... see: http://www.bindview.com/services/razor/utilities/ compile up CLIENT-SIDE ONLY, using dceidl, and create a library for use inside MSV1_0.DLL. i know todd developed interoperable versions of these idl files, because he was using them, compiled with MIDL.EXE, to do security tests against NT 4.0. remember: these IDL files are what microsoft DOESN'T want anyone to have, and there are very good _legitimate_ reasons for it: they are "behind-the-scenes" APIs which, if some idiot inside microsoft went and wrote a tool which became publicly used and relied on, they would be stuffed: they have ENOUGH apis which date back 15 years and they don't need any more. that having been said, i hate the fact that they are forcing people to pay $50k up-front and then $100 per-client for frakkin _information_. bastards. c) replace cli_nt_login_interactive() with a function that utilises the above library that utilises netlogon, samr and lsarpc client-side stuff from b) above. basically, what it boils down to is that the functions inside cli_nt_login_interactive i wrote BY HAND after examining MSRPC traffic. those functions neeeed too dieeee and they can easily be replaced one-by-one with the "proper" versions from doing "dceidl -client lsarpc.idl". it takes a couple of seconds and you get a header file lsarpc.h and a lsarpc.o and you're DONE. question. why did i spend so long doing hand-marshalling of the nt domains code. perhaps because i would not be able to give microsoft absolute hell for three frakkin years? d) consider porting, one-by-one, the Samba TNG services lsarpcd, netlogond and samrd (or better samrtdbd) to FreeDCE runtime infrastructure. this is NOT essential but it is very worthwhile. every project needs to do at least two throw-aways and with the samba tng code, there has been approximately one and a half throwaways so far... time for a major one, ESPECIALLY in light of the reactos project. FINALLY: e) consider writing that winregd service but actually picking up REAL registry hive files. someone did write a "reader" of registry files, i do not recall who it was. [note: YESSSS!!! yeeeeeehawww, todd i could KISS you!!] http://www.bindview.com/Services/RAZOR/Utilities/Unix_Linux/ntreg_readme.cfm todd wrote a registry-hive-reader as a linux filesystem driver!!!!! todd, you are bloody mad. *smooch*. f) consider writing a samr service with the FreeDCE runtime that utilises "registry" functions RegXXXX - _properly_. anyway, if you got this far: congratulations and welcome to a brief nightmare history of the development behind NT Domains Authentication. all of the infrastructure above _already_ exists - in Samba TNG. it's just... it works. it's a bit creaky at the edges, but it works. how about it? l. p.s. it almost goes without saying, but i will hint at it once again: you will not find the samba team's goals and strategic direction to be compatible with reactos. as a team, they lack the insight, vision and project management skills to be able to cope with such inter-dependant insane gibberish. this i say with much sadness because they are highly respected individuals in the free software community, and yet they are taking the samba project in very different - and ultimately time-consuming - directions from what is really really needed. due to pride they cannot admit this in public but they have been known to admit it in private. much much disappointment and sadness and there's absolutely nothing i can do about it. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

19 years, 9 months

2
1
0 0

ReactOS 'Support Database' for the new ReactOS Homepage (ideas, goals, questions)

by Klemens Friedl

ReactOS 'Support Database' for the new ReactOS Homepage I wrote down a lot of ideas, questions, soulutions, goals, etc. for the upcoming Support Database! We need more ideas, suggestions, comments, etc! Please read the whole text and then write an email to the mailing list! This text should start discussion about that topic !!! Thanks! Note: * some of the ideas are not completely new, i copy&paste the from winehq's newsletter archive (i quoted the winehq's ideas and add the original post date)! * I have added some useful links at the of the text! Please try out the links and explore the compatibility databases from other projects! You will need it if you want to join the discussion. And I *hope* a lot of persons join the discussion! So please visite the links and write down what could be better or what's key features our database also should *clone*! The 'Support Database' will contain the following 'databases': * Compatibility Database (application, driver and hardware) * Package Database (a list of download-able applications/driver; principal for the ReactOS Package Manager) (* Media Database (like the ReactOS Fansite Media Database; maybe we can implement this later)) The 'Support Database' (project codename 'RosDB') will base on the package manager alpha page that i have created april 2005. Note: the package database will be combined with the compatibility datbase. Both 'databases' will share the same 'application tree'! So it will be easy e.g. you browse the compatibility db, you found a working app and think, "i also want to download this app", then you will be able to click on a link (on a central position) and you will be redirected to the package database. In near future it should be possible (if you run ReactOS or Win32 with installed and runing ReactOS Package Manager), that you can select your favorite apps/driver you want to install (navigation like amazone/ebay/compatibility db) and then click install (a normal link on the package manager page) and your running (maybe as a service) ReactOS Package Manager check/capture every clipboard item and if it is a valid 'package style link' then it will connect to the online database and download all the selected apps/driver and download it from mirror server (from their developers/sourceforge/etc.) and then install all items (without or with minimum of user interaction). In my (frik85) opinion, that would be one of the 'hottest' feature someone can imagine (in connection with a homepage, package manager, etc.). This feature will became a main feature and everyone will use that *hope* for ReactOs and also possible for Win32 (from MS). :) -- frik85 "ReactOS Compatibility Database ReactOS has an Compatibility Database where Windows application/driver/hardware compatibility is recorded. Registered users can submit new items, and comment on existing ones. Screen shots are also available for many apps. Users can also vote on their favorite apps." -- a possible description Design goals User wants to know following things: * Does my application/driver/hardware work? * How can I make it work? * Does it work in the new ReactOS/application/driver/hardware version? * Where can i download the application (maybe with the ReactOS Package Manager)? * list all working and non working application/driver/hardware Management Issues/Goals: We need a high 'input data quality', then the administration work will be a minimum. To reach this high data quality, i want to code a simple to use wizard for the 'submit item' page. You can view the sample wizard on the package manager alpha page (see link). Have some form of a moderation system to let end users know the quality of a given persons entry. Maybe like the appDB from winehq? Where a registered user can ask for a kind of moderator right for one specific item (e.g. application), so he can manage the comments, add new info, etc. -> taking ownership of an item (e.g. application): monitor comments on it, track bugs (close bugs), and make sure quality level is high for application description. NO redundant entries for the same product! We need moderators who review all new entries. The moderators should be able to read as many comments as possible and help the normal users, report bugs to the bugzilla system, etc. Reviews (aka user comments) should expire. (expire time 1 year?) Track hit counts on each item (auto magic way of knowing which apps are most desired) and maybe voting like in appDB (WineHQ) or in C4 (CodeWeaver). Some ideas i found in old winehq's neewsletters: (maybe useful for our project!) "Idea: Tie the apps database to the api database. The idea is that we know from the apps database which apps are the most popular. We know from the api database which DLLs/entry points are used by those apps. We can then create a report out of the api database of the list of the DLLs most needed by the top ten apps, and then people writing test scripts (something Alexandre and John Sturtz are working on), have a prioritized todo list. Again, this helps us find useful things for the many volunteers to do." -- winehq newsletter from 18 Oct 2000 Note: maybe a good idea to create such a api database; -> a simalar api status output is currently generated from the svn server (with a small console based application, see build tools). You can view the api status on the svn server. A great chance to import the data to the database and make the idea above possible! The only question, is it usefull for someone? -- frik85 "Idea: Tie the apps database to bugzilla. If users have a problem with an app, it's a bug, and should be in bugzilla. If we can get to a point where we can easily get a report that says 'here are all the bugs that Quicken depends on'. Or, here are the five bugs, the fixing of which will make 50 apps suddenly work. This would be wicked cool." -- winehq newsletter from 18 Oct 2000 Note: the bugzilla will be a subsystem of the RosCMS, so it will be (maybe) possible to implement the idea above. Is something like this usefull for someone? -- frik85 "if we add some 'relay statistics' in Wine code (of course, there will be problems with COM objects where relaying does not work for now) and incorporate these statistics in the database, we could have a list of the most frequently used Windows calls. (feel free to add new ideas for improvements :-) )" -- winehq newsletter from 28 Dec 2000 "He [who take ownership of an item] definitely should have the application installed and, very preferably, he should also be using it regularly (or testing it regularly if it is not yet in the usable state). You are right in pointing out that he cannot test all possible but I contend he does not have to. His role would be to: read the comments entered in the application's comment section. engage into a discussion with the users who post interesting tricks, information, report a sub-version as not working, report problems with a specific Wine/Windows combination extract and summarize the above in his application status report. This section would come first in the application's page and only the application maintainer would be allowed to modify it (whether it's strictly enforced or not is another issue) test the application regularly and update the information on the application's page help users having problems with that application " -- winehq newsletter from 28 Dec 2000 "Jeremy White proposed some scheme to help keeping the database usable: I think the biggest problem with the app database is that we get garbage in, it produces garbage out. I think we should not report or even use any user scores until a trusted app db maintainer has validated that user experience (and possibly users can become trusted reporters). Too many people say 'Hey! The main screen came up! That's a 5! Witness the Slashdot post about MS Office 2k. (anyone actually try to use Office 2K in Wine to author a sizable document?)." -- winehq newsletter from 28 Dec 2000 The information we will gain from the support database * the progress of ReactOS (for devs and normal user) * the most wanted applications (when we implement a voting / hit counts feature) * a reference for application/driver/hardware that doesn't work without tweaking, to get them working * people may be able taking 'ownership' of an application and do regular bug reports / regression testings). Several questions, where we need a answer: "How to 'classify' applications ?: the main point was how an application should be identified (think of Word 5 vs. WinWord 5 cs. Word 7.0, and lots of other quirks (limited versions, demo version, patched versions...) What information should we have about an application ?: this would help in knowing the correct context of execution of such an application (target Windows version, used DLLs, used APIs...)" -- winehq newsletter from 28 Dec 2000 * And about a ReactOS releases ? * How about scoring ? * What additional information should one application/driver/hardware have? We need as much ideas, (feedback after the relaunch/while the testing phase), comments, (and flames) as possible the next weeks. After the website relaunch We need volunteers to take responsibility for updating Apps in the Compatibility Database. We need to discuss this! Then after the discussions ... only remains the hours of coding and debugging to put it in place :) Compatibility Databases from other projects: http://appdb.winehq.org/ http://www.codeweavers.com/compatibility/ http://www.linuxcompatible.org/compatibility.html http://www.ntcompatible.com/compatibility.html http://www.microsoft.com/whdc/hcl/default.mspx ttp://www.realtimesoft.com/multimon/search.asp http://hardwaredb.suse.de/index.php?LANG=en_UK http://www.testingstandards.co.uk/compatibility_-_database.htm http://www.yellowtab.com/support/hardware/ http://www.iyonix.com/software/ http://www.ardi.com/compat_search.php?name=ALL&category=ALL&status=ALL A kind of Package Database: http://rpmseek.com/index.html?hl=en If you know other websites that should be listed here, please write an email to the mailing list! Best regards, Klemens Friedl <frik85> PS: if you write a comment, do NOT quote whole passages or do NOT quote the whole text! The reason, emails should be readable ... -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl

19 years, 9 months

4
4
0 0

Re: [ros-dev] New Webserver System

by reactos

This makes it totally perfect for embedded applications like Set-top-boxes or Routers or why not game consoles right? /Jaix ----Ursprungligt meddelande----- From: Emanuele Aliberti ea(a)iol.it Date: Thu, 1 Sep 2005 06:37:19 +0200 To: ReactOS Development List ros-dev(a)reactos.com Subject: Re: [ros-dev] New Webserver System > Richard Campbell wrote: > > > Well, i don't know about other devs around here, but i don't WANT > > ReactOS to become another XP. > > > > Windows XP typically consumes over a GB of space. > > > > Remember NT4? It took between 30 and 100 mb of space depending on > > features. Windows 95? About 15 MB. If users want additional apps, > > they can either download them, or use a custom ROS distro that will > > include such things. The source tree is cluttered enough as it is. > > ReactOS should only include the basic software that earlier versions > > shipped with...a notepad clone, possibly a wordpad clone, basic net > > utils, etc. > > Also the Win32 subsystem is not technically necessary. All Win32 pieces > could be moved off the main reactos tree and included as optional > linking them from modules. I proposed it years ago. It is not an easy > task, though, because setup should know that, if the user asks for no > personalty at all, it should install none (now win32 is by default in). > Personalities (win, posix, os2, vms, ...) should come on the cd-rom as > separate cab files and post install procedures add registry entries, > create directoryes etc. A no-personality ReactOS will be a really light > OS, perfect for custom text/graphics boxes (you just need writing an > entry in the registry for the session manager to start your native > program, which will be the only user program in the box (excluding the > sm itself). > > -- > :Emanuele Aliberti > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev Yours sincerely, Jaix Bly

19 years, 9 months

2
1
0 0

Ros VGA driver not working - To be confirmed

by Gge

Hello, Ros VGA driver does not work anymore in my real hardware configuration. I'd like to know if the problem is confirmed by somebody else. To reproduce it , disable the VBE drives in Hiveinst.inf file , make registry and reboot. The green Reactos logo displayed at boot is not displayed correctly ( color is red/yellow etc , the logo is not clearly displayed ) Here are the debug messages (DBG=1) --------------------------- (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\mpu401.sys (drivers\input\i8042prt\registry.c:218) Can't read registry: c0000034 (drivers\input\i8042prt\registry.c:224) Manually set defaults (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\xboxvmp.sys (ntoskrnl\ob\wait.c:246) Returning: 0 (subsys\win32k\ntuser\desktop.c:769) Trying to open desktop (\Windows\WindowStations\WinSta0\Default) (subsys\win32k\ntuser\desktop.c:580) IntShellHookNotify: No desktop! (subsys\win32k\ntuser\desktop.c:769) Trying to open desktop (\Windows\WindowStations\WinSta0\Winlogon) (subsys\win32k\ntuser\desktop.c:580) IntShellHookNotify: No desktop! (subsys\win32k\ntuser\desktop.c:769) Trying to open desktop (\Windows\WindowStations\WinSta0\Screen-Saver) (subsys\win32k\ntuser\desktop.c:580) IntShellHookNotify: No desktop! (lib\ntdll\ldr\utils.c:2072) Relocating (77a90000 -> 431000) C:\ReactOS\System32\version.dll FIXME: CopyImage doesn't support IMAGE_ICON correctly! (lib\ntdll\ldr\utils.c:1190) LdrGetExportByName(): failed to find mxdMessage (lib\ntdll\ldr\utils.c:2015) Failed to create or open dll section of 'msacm.drv' (Status c0000135) (lib\ntdll\ldr\utils.c:2015) Failed to create or open dll section of 'midimap.drv' (Status c0000135) (SAMLIB:lib\samlib\samlib.c:399) User already exists! (lib\setupapi\devinst.c:2513) not fully implemented (lib\setupapi\devinst.c:2513) not fully implemented (lib\setupapi\devinst.c:2513) not fully implemented (lib\setupapi\devinst.c:2513) not fully implemented (lib\setupapi\devinst.c:2513) not fully implemented (lib\setupapi\devinst.c:2513) not fully implemented Thanks Gge

19 years, 9 months

2
1
0 0

Baby Steps

by Rick Langschultz

This is a suggestion: Can ReactOS implement an OpenLDAP backend to the ReactOS website. There are many benefits to implementing OpenLDAP into the reactos.com website. First, reactos.com can use this software to authenticate users in certain modules of the website such as future forums, wikis (via publishing), and possible later implementation into a mass- mailing system like squirrelmail or mailman, suggestions, hint hint, or perhaps in the future an instant messenger engine. Also OpenLDAP would be able to provide back-end website developers to verify status of community members. How is that for a baby step to implementing someone's ideas... Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

19 years, 9 months

5
7
0 0

bootsect.ros

by dalfa the enlightenedone

hi i installed reactos on my hd but the installer doesnt give the option to install de loader to the mbr only on the floppy so i didnt installed because i dont have a floppy :p then i create: freeldr.ini ant copy the freeldr.ini but i didnt know what the bootsect.ros is i didnt find info about it in the wiky ¿how can i create one? -- [dalfa@MDK dalfa]$ cat .firma [UsuarioGnu/Linux326018] <Ymessenger> dalfa_id <WebPage> http://dalfa.tk <WebPage> http://dalfa.no-ip.org <Jabber> dalfa(a)jabber.org <skype> theenligthenedone <aMSN> dalfa.theenlightenedone(en)gmail.com <Blog> http://drakedalfa.blogspot.com/ <aim> drakedalfa -> Y la verdad os hara libres... - Hechos 4: 12 - Romanos 10: 9-13

19 years, 9 months

2
2
0 0

Shouldn't errors be explained a bit better?

by Reuben Perelman

I was looking through the installer, and noticed that it generated an error for partitions created by linux fdisk. Shouldn't the user be informed about this, so they know why. This type of information will help a user solve the problem that caused the error. Below is the code for the error I'm talking about. if (WarnLinuxPartitions == TRUE && CheckForLinuxFdiskPartitions (PartitionList) == TRUE) { PopupError ("Setup found that at least one harddisk contains an incompatible\n" "partition table that can not be handled properly!\n" "\n" "Creating or deleting partitions can destroy the partiton table.\n" "\n" " \x07 Press F3 to quit Setup." " \x07 Press ENTER to continue.", "F3= Quit ENTER = Continue"); while (TRUE) { ConInKey (Ir); if ((Ir->Event.KeyEvent.uChar.AsciiChar == 0x00) && (Ir->Event.KeyEvent.wVirtualKeyCode == VK_F3)) /* F3 */ { return QUIT_PAGE; } else if (Ir->Event.KeyEvent.wVirtualKeyCode == VK_RETURN) /* ENTER */ { WarnLinuxPartitions = FALSE; return SELECT_PARTITION_PAGE; } } }

19 years, 9 months

1
0
0 0

Nevermind

by Rick Langschultz

Since I heard of reactos, i have always considered it one day replacing my Windows 2000 and XP boxes. Because ReactOS was going to be an open-source alternative to the Windows NT API I felt that it had and has serious potential to hinder or greatly replace Microsoft Windows. I have suggested several ideas both through IRC (freenode) and email messages how the computing world does things. I understand that ReactOS is still in pre-production, and planning for the next release is greatly important to the community development and testing of the operating system, however I fail to grasp the concept behind the hindrance of ideas being passed the the development community. Some development plans I have talked about were: 1 - A 64 bit journaling file system with a SQL-like back-end. Lookout WinFS; there that plan went down the drain. 2 - Implementing an instant messenger server for developers and users to talk on, realtime, without IRC. Maybe not quite MSN Messenger, but why not? iChat even uses .mac. 3 - Implementing an OpenLDAP back-end to the website. Active Directory has nothing on you... Plan knocked out again. i would rather stick with something close minded like closed source software than having no ideas be recognized at all. I only suggest things like this because Microsoft will always be releasing newer software that will leave reactos in the dust if they not heed the advice of all, not just me, their developers, testers, and users. Why not; right? why envision something and it fail to be realized, waste of time if i ever knew it... Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

19 years, 9 months

6
5
0 0

Installation procedure

by drake dalfa

|>hi, |> |>i have a problem with the installation from |>setup to a real hd the setup dies with this |>message: |> |>allowconsolo() failed (status = 0x0000001) |> |That one seems a well known bug: |http://www.reactos.com/wiki/index.php/ChangeLog-0.2.7 |http://reactos.com/bugzilla/show_bug.cgi?id=688 thanks that show me the way ;) the problem is my keyboard is usb one so i plug an ps2 one and now all work :) maybe a little more debug on the setup will help to others to figure this :) more easy thanks :) |>the installation procedure is only the copy |>of the reactos directory to the hd? |> |It also prepares the SYSTEM registry hive with values depending on the |operator choices and (little) hardware probing and installs the boot sector. thanks, now i can install the system and now i configure the grub but i have another question the file bootsect.ros, wath has to say? i made my freeldr.ini like this: [ReactOS] BootType=ReactOS SystemPath=multi(0)disk(0)rdisk(0)partition(7)\reactos Options=/DEBUGPORT=SCREEN but the bootsect.ros i didnt find a example :) thanks for the help

19 years, 9 months

1
0
0 0

Re: [ros-bugs] [Bug 729] ftp.exe exit at start

by Gge

ReactOS.Bugzilla(a)reactos.com wrote: > http://reactos.com/bugzilla/show_bug.cgi?id=729 > > > > > > ------- Additional Comments From waxdragon(a)gmail.com 2005-27-08 18:14 ------- > Hartmut's 17563 commit fixed this. Thank you! There are still issues with ftp, > and I will file another bug. > Ftp.exe still fails for me as per debug messages below WARNING: WSHGetSockaddrType at drivers\net\wshtcpip\wshtcpip.c:103 is UNIMPLEMENTED! WARNING: WSHGetSockaddrType at drivers\net\wshtcpip\wshtcpip.c:103 is UNIMPLEMENTED! 8ce8fc10: 00 31 66 00 00 00 00 00 00 00 00 00 01 00 00 00 8ce8fc20: 0e 00 02 00 00 15 d4 1b 28 fc 00 00 00 00 00 00 8ce8fc30: 00 00 TCPConnect: Called Connecting to address fc281bd4:1500 so->so_state 102 so->so_state 102 so->so_state 102 so->so_state 102 (ntoskrnl\mm\mm.c:300) Address: ffffffff Unhandled exception Address: 7c815b1f C:\ReactOS\system32\KERNEL32.dll CS:EIP 1b:7c815b1f DS 23 ES 23 FS 3b GS 0 EAX: 00000001 EBX: 780263f0 ECX: 00000000 EDX: 0065fbf4 EBP: 00000000 ESI: 00020000 ESP: 0065fb30 EDI: 7c843cfc EFLAGS: 00010202 Frames: <error dumping stack trace: 0xc0000005> so->so_state 13b (lib\rtl\env.c:574) Return STATUS_VARIABLE_NOT_FOUND: PROMPT Regards

19 years, 9 months

1
0
0 0

Installation procedure

by dalfa the enlightenedone

hi, i have a problem with the installation from setup to a real hd the setup dies with this message: allowconsolo() failed (status = 0x0000001) well, my question is: the installation procedure is only the copy of the reactos directory to the hd? Sorry to ask to the DevelList but in the users list no one answer me :) thanks -- [dalfa@MDK dalfa]$ cat .firma [UsuarioGnu/Linux326018] <Ymessenger> dalfa_id <WebPage> http://dalfa.tk <WebPage> http://dalfa.no-ip.org <Jabber> dalfa(a)jabber.org <skype> theenligthenedone <aMSN> dalfa.theenlightenedone(en)gmail.com <Blog> http://drakedalfa.blogspot.com/ <aim> drakedalfa -> Y la verdad os hara libres... - Hechos 4: 12 - Romanos 10: 9-13

19 years, 9 months

2
2
0 0

Re: [ros-svn] [royce] 17575: add . to list of include directories for all projects - Regression

by Gge

royce(a)svn.reactos.com wrote: > add . to list of include directories for all projects > > > Updated files: > trunk/reactos/tools/rbuild/backend/msvc/msvcmaker.cpp > Hello, This patch broke reactos trunk => Build Ros fails in tools/rbuild => Log file --> htttp://rafb.net/paste/results/qEE3zI12.html Regards

19 years, 9 months

1
0
0 0

Problem with booting reactos.

by Saveliy Tretiakov

Hi. I have a problem with booting reactos on vmware 4.5 (INACCESSIBLE_BOOT_DEVICE). Load of scsiport.sys fails because NTOSKRNL.RtlConvertUlongToLargeInteger is not found. Any ideas? (ntoskrnl\ke\main.c:289) --------------------------------------------------------------- (ntoskrnl\ke\main.c:290) ReactOS 0.3-SVN (Build 20050821-r17456) Used memory 65536Kb (ntoskrnl\mm\mminit.c:375) Kernel Stack Limits. InitTop = 0x800f8000, Init = 0x800f5000 (ntoskrnl\mm\mm.c:283) No current process (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\ne2000.sys (ntoskrnl\io\pnpmgr.c:1847) Initialization of service Ne2000 failed (Status c0000001) (ntoskrnl\io\pnpmgr.c:1847) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1847) Initialization of service serial failed (Status c0000034) (ntoskrnl\ldr\loader.c:1348) LdrPEGetExportByName(): failed to find NTOSKRNL.RtlConvertUlongToLargeInteger (ntoskrnl\ldr\loader.c:1436) Failed to import NTOSKRNL.RtlConvertUlongToLargeInteger from scsiport.sys (ntoskrnl\io\driver.c:1245) Driver 'atapi.sys' load failed, status (c0000001) (ntoskrnl\ldr\loader.c:1348) LdrPEGetExportByName(): failed to find NTOSKRNL.RtlConvertUlongToLargeInteger (ntoskrnl\ldr\loader.c:1436) Failed to import NTOSKRNL.RtlConvertUlongToLargeInteger from scsiport.sys (ntoskrnl\io\driver.c:1245) Driver 'buslogic.sys' load failed, status (c0000001) (ntoskrnl\io\driver.c:1274) Driver 'cdrom.sys' load failed, status (c000000e) (ntoskrnl\io\driver.c:1274) Driver 'disk.sys' load failed, status (c000000e) (ntoskrnl\io\arcname.c:362) Failed to find setup disk! (ntoskrnl\io\iomgr.c:407) IoCreateSystemRootLink FAILED: (0xc0000001) - KeBugCheck at ntoskrnl\io\iomgr.c:408 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. Technical information: *** STOP: 0x0000007B (0x00000000,0x00000000,0x00000000,0x00000000) Frames: <ntoskrnl.exe:24c6 (ntoskrnl/ke/bug.c:498 (KeBugCheckEx))> <ntoskrnl.exe:24fe (ntoskrnl/ke/bug.c:519 (KeBugCheck))> <ntoskrnl.exe:bafab (ntoskrnl/io/iomgr.c:408 (IoInit3))> <ntoskrnl.exe:b882a (ntoskrnl/ex/init.c:651 (ExpInitializeExecutive))> <ntoskrnl.exe:6706 (ntoskrnl/ke/main.c:100 (KiSystemStartup))> <ntoskrnl.exe:b684e (ntoskrnl/ke/main.c:294 (_main))> <ntoskrnl.exe:104b ({standard input}:47 (_section_alignment__))> KeBugCheckWithTf at ntoskrnl\ke\catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0x80000003,0x800a1b07,0x00000000,0x1f000000) *** ntoskrnl.exe - Address 0x800a1b07 base at 0x80000000, DateStamp 0x0

19 years, 9 months

4
4
0 0

Re: [ros-diffs] [hpoussin] 17569: Implement SetupDiSelectBestCompatDrv, by sorting drivers by rank in drivers list

by Thomas Weidenmueller

hpoussin(a)svn.reactos.com wrote: > + if (((struct DriverInfoElement *)PreviousEntry)->DriverRank >= Rank) Why not use the CONTAINING_RECORD macro? Best Regards, Thomas

19 years, 9 months

1
0
0 0

Getting started?

by Reuben Perelman

Hey, I know some basic C++, and I thought the reactos project would be a great way to learn more about c++ and programing. What's the best way to get involved in the reactos project?

19 years, 9 months

4
5
0 0

Re: [ros-diffs] [weiden] 17559: implemented CreateSymbolicLink() (not tested/verified yet!)

by Filip Navara

weiden(a)svn.reactos.com wrote: >+#define SYMLINK_FLAG_DIRECTORY 0x1 > > is there any reason not to name it SYMBOLIC_LINK_FLAG_DIRECTORY? (to be compatible) - Filip

19 years, 9 months

5
4
0 0

re: [ros-svn] [amunger] 17565: "." means current directory, not previous. Spotted by Talley.

by Sylvain Petreolle

This change is broken. The error comes from r16438, which actually did change the help from "CD[..|-]\n\n\" to "CD[..|.]\n\n\" see for yourself : http://svn.reactos.com/viewcvs/trunk/reactos/subsys/system/cmd/En.rc?rev=15… Kind regards, Usurp (aka Sylvain Petreolle) humans are like computers, yesterday the BIOS was all - today its just a word

19 years, 9 months

1
0
0 0

reactos.com or reactos.org?

by Ge van Geldorp

I was wondering if, together with the launch of the new website, we should switch our "primary" domain from reactos.com to reactos.org? We have control of both domains. An .org domain seems better suited for a open source project. What do you all think? Gé van Geldorp (aka gvg(a)reactos.org :-))

19 years, 9 months

13
17
0 0

console functions are broken

by Hartmut Birr

Hi, parts of the changes from r16213, 17417 and 17431 have broken most of the console functions like WriteConsoleOutputCharacter or WriteConsoleOutputAttribute. In many cases the length of the buffers in kernel32 and the check of the buffers in csrss are wrong. As a result of this, Midnight Commander shows only a black screen. - Hartmut

19 years, 9 months

2
1
0 0

New Homepage Content

by Maarten Bosma

Hi, Frik85 asked me write a suggestion how the structure of the content for the new homepage should look like. So here it is: http://wiki.reactos.com/New_Homepage_Content Let me know what you think about it. When we agreed about the headlines we can start to write the content into wiki. Some of it can be taken from the current wiki-pages and also some text from the old homepage can be reused. Maarten Bosma

19 years, 9 months

1
0
0 0

Re: [ros-diffs] [weiden] 17542: add stubs for CreateSymbolicLinkA/W

by Joseph Galbraith

weiden(a)svn.reactos.com wrote: > add stubs for CreateSymbolicLinkA/W > > Modified: trunk/reactos/lib/kernel32/file/create.c > Modified: trunk/reactos/lib/kernel32/kernel32.def > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/kernel32/file/create.c* > > --- trunk/reactos/lib/kernel32/file/create.c 2005-08-25 17:38:15 UTC (rev 17541) > +++ trunk/reactos/lib/kernel32/file/create.c 2005-08-25 18:21:50 UTC (rev 17542) > @@ -357,4 +357,51 @@ > > return FileHandle; > } > > > + > +/* > + * @unimplemented > + */ > +BOOL STDCALL > +CreateSymbolicLinkW(IN LPCWSTR lpSymlinkFileName, > + IN LPCWSTR lpTargetFileName, > + IN DWORD dwFlags) > +{ > + SetLastError(ERROR_CALL_NOT_IMPLEMENTED); > + return FALSE; > +} > + > + > +/* > + * @implemented > + */ > +BOOL STDCALL > +CreateSymbolicLinkA(IN LPCSTR lpSymlinkFileName, > + IN LPCSTR lpTargetFileName, > + IN DWORD dwFlags) > +{ > + PWCHAR SymlinkW, TargetW; > + BOOL Ret; > + > + if(!lpSymlinkFileName || !lpTargetFileName) > + { > + SetLastError(ERROR_INVALID_PARAMETER); > + return FALSE; > + } > + > + if (!(SymlinkW = FilenameA2W(lpSymlinkFileName, FALSE))) > + return FALSE; > + > + if (!(TargetW = FilenameA2W(lpTargetFileName, TRUE))) > + return FALSE; > + > + Ret = CreateSymbolicLinkW(SymlinkW, > + TargetW, > + dwFlags); > + > + RtlFreeHeap(RtlGetProcessHeap(), 0, TargetW); > + > + return Ret; > +} Does this leak SymlinkW ? Thanks, Joseph

19 years, 9 months

2
2
0 0

Re: [ros-svn] [royce] 17517: invoke _generate_dsp() have it open the output file, and fix some path parsing and const issues.

by Royce Mitchell III

royce(a)svn.reactos.com wrote: >invoke _generate_dsp() have it open the output file, and fix some path parsing and const issues. > > >Updated files: >trunk/reactos/tools/rbuild/backend/msvc/msvc.cpp >trunk/reactos/tools/rbuild/backend/msvc/msvc.h >trunk/reactos/tools/rbuild/backend/msvc/msvcmaker.cpp > > "make msvc" now creates a DSW file and DSP files such that msvc6 can load them. I seriously doubt anything will build yet, tho.

19 years, 9 months

3
5
0 0

Re: [ros-svn] [hbirr] 17538: Fixed a bug in RtlLeaveCriticalSection. We have only to signal the event if someone waits on it.

by Thomas Weidenmueller

hbirr(a)svn.reactos.com wrote: > Fixed a bug in RtlLeaveCriticalSection. We have only to signal the event if someone waits on it. I believe this change is incorrect. This change introduces the exact same bug I fixed in r14326. The reason why this change is incorrect is, that you can't rely on LockCount. It may be incremented anytime a thread enters a critical section and waits for it. That's why there's the RecursionCount field, it is the only information we can rely on to determine whether we're about to release the lock or not. In this code path we already know that we left the last recursion, so no matter what the LockCount is at the moment (depends on how many threads are waiting for the critical section), we always need to unwait one waiter! This change most likely will introduce a dead-lock of cygwin. Best Regards, Thomas

19 years, 9 months

2
3
0 0

Re: Re: [ros-dev] reactos.com or reactos.org?

by yash

>major Operating System manufacturer uses .org as their domain suffix. >Microsoft.com, Apple.com, Redhat.com. Given .ORG should be considered ROS is not a manufacturer, not a company, actually ROS community is a part of ReactOS source code and must be located at sourceforge. Will they register "dot sf" as a first level domain?

19 years, 9 months

2
1
0 0

Re: [ros-dev] reactos.com or reactos.org?

by yash

My humble point is like this. Once ROS get's to it's first production release, you'll get many commercial offers and may need .com site for doing some commerce, like selling CD's and rotating ads. So many end users will come for download and support. Is it FreeBSD or RedHat way? Turning into monster is no good, but ROS might get huge end (very end) user hit, it is not freebsd and not even linux, it positions as a replacement for windoze itself and windoze means so much commercial and end user.... Yet my personal vision is to have www.reactos.com displaying "Server not found". So you gogo google and type reactos and if you're lucky you get to reactos.org and think "oh dear it is so cool and open source". >I was wondering if, together with the launch of the new website, we should >switch our "primary" domain from reactos.com to reactos.org? We have control >of both domains. An .org domain seems better suited for a open source >project. What do you all think? > >Ge van Geldorp (aka gvg(a)reactos.org :-)) > > >_______________________________________________ >Ros-dev mailing list >Ros-dev(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-dev

19 years, 9 months

1
0
0 0

RE: [ros-diffs] [navaraf] 17511: Implement the most over-optimized lockin NT - the NDIS_RW_LOCK.

by Casper Hornstrup

Some constants for the magic numbers would be nice. ________________________________________ From: ros-diffs-bounces(a)reactos.com [mailto:ros-diffs-bounces@reactos.com] On Behalf Of navaraf(a)svn.reactos.com Sent: 24. august 2005 14:21 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [navaraf] 17511: Implement the most over-optimized lockin NT - the NDIS_RW_LOCK. Implement the most over-optimized lock in NT - the NDIS_RW_LOCK. Modified: trunk/reactos/drivers/net/ndis/ndis/control.c Modified: trunk/reactos/drivers/net/ndis/ndis/main.c Modified: trunk/reactos/drivers/net/ndis/ndis/stubs.c +/* + * @implemented + */ +VOID +EXPORT NdisAcquireReadWriteLock( IN PNDIS_RW_LOCK Lock, IN BOOLEAN fWrite, @@ -29,13 +48,88 @@ * NDIS 5.0 */ { - UNIMPLEMENTED + ULONG RefCount; + UCHAR ProcessorNumber; + UCHAR BusyLoop; + + ASSERT_IRQL(DISPATCH_LEVEL); + + if (fWrite) { + if (Lock->Context == PsGetCurrentThread()) { + LockState->LockState = 2; + } else { + KeAcquireSpinLock(&Lock->SpinLock, &LockState->OldIrql); + /* Check if any other processor helds a shared lock. */ + for (ProcessorNumber = KeNumberProcessors; ProcessorNumber--; ) { + if (ProcessorNumber != KeGetCurrentProcessorNumber()) { + /* Wait till the shared lock is released. */ + while (Lock->RefCount[ProcessorNumber].RefCount != 0) { + for (BusyLoop = 32; BusyLoop--; ) + ; + } + } + } + Lock->Context = PsGetCurrentThread(); + LockState->LockState = 4; + } + } else { + KeRaiseIrql(DISPATCH_LEVEL, &LockState->OldIrql); + RefCount = InterlockedIncrement((PLONG)&Lock->RefCount[KeGetCurrentProcessorNumber()].RefCount); + /* Racing with a exclusive write lock case. */ + if (Lock->SpinLock != 0) { + if (RefCount == 1) { + if (Lock->Context != PsGetCurrentThread()) { + /* Wait for the exclusive lock to be released. */ + Lock->RefCount[KeGetCurrentProcessorNumber()].RefCount--; + KefAcquireSpinLockAtDpcLevel(&Lock->SpinLock); + Lock->RefCount[KeGetCurrentProcessorNumber()].RefCount++; + KefReleaseSpinLockFromDpcLevel(&Lock->SpinLock); + } + } + } + LockState->LockState = 3; + } } /* * @implemented */ +VOID +EXPORT +NdisReleaseReadWriteLock( + IN PNDIS_RW_LOCK Lock, + IN PLOCK_STATE LockState) +/* + * FUNCTION: + * ARGUMENTS: + * NOTES: + * NDIS 5.0 + */ +{ + switch (LockState->LockState) { + case 2: /* Exclusive write lock, recursive */ + return; + + case 3: /* Shared read lock */ + Lock->RefCount[KeGetCurrentProcessorNumber()].RefCount--; + LockState->LockState = -1; + if (LockState->OldIrql < DISPATCH_LEVEL) + KeLowerIrql(LockState->OldIrql); + return; + + case 4: /* Exclusive write lock */ + Lock->Context = NULL; + LockState->LockState = -1; + KfReleaseSpinLock(&Lock->SpinLock, LockState->OldIrql); + return; + } +} + +

19 years, 9 months

1
0
0 0

ATTN frik85: Website related bugs in Bugzilla

by WaxDragon

Here is the list of website related bugs currently in Bugzilla. Please keep these in mind when implementing the new site. When the new site is in place, please resolve the applicable bugs. "Bugzilla username/password weirdness" http://www.reactos.com/bugzilla/show_bug.cgi?id=22 "Roles on reactos.com" http://www.reactos.com/bugzilla/show_bug.cgi?id=68 "Various minor reactos.com issues" http://www.reactos.com/bugzilla/show_bug.cgi?id=76 "Taking a bug in bugzilla doesn't change the assignee" http://www.reactos.com/bugzilla/show_bug.cgi?id=196 "Hardware Compatiblity List (HCL)" http://www.reactos.com/bugzilla/show_bug.cgi?id=296 "rss feeds for reactos would be nice" http://www.reactos.com/bugzilla/show_bug.cgi?id=383 "users.reactos.com" http://www.reactos.com/bugzilla/show_bug.cgi?id=438 "Account Creation and Bugzilla is flaky" http://www.reactos.com/bugzilla/show_bug.cgi?id=459 "invisible graphic on the website seems not to exist" http://www.reactos.com/bugzilla/show_bug.cgi?id=612 "News Section on User Site is screwed up" http://www.reactos.com/bugzilla/show_bug.cgi?id=613 Thanks! WD -- #irc.freenode.net #reactos 01:03PM <filip2307> i don't know about any bug 01:04PM <filip2307> none exist 01:04PM <filip2307> ReactOS is prefect

19 years, 9 months

2
2
0 0

We are linked from microsoft.com!!!

by reactos

Hello guys, Just want to encourage you about that we are linked from Microsoft.com!!! Nothing really nice, but we are... ...that's what matters, right? http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsoftware… Yours sincerely, Jaix Bly

19 years, 9 months

3
2
0 0

RE: Ros-dev Digest, Vol 12, Issue 38

by Lucio Diaz

The bug appears only in the instalation. I tried the livecd and it works fine. Best regards, Lucio Diaz. --------------------------------- Correo Yahoo! Comprueba qué es nuevo, aquí http://correo.yahoo.es

19 years, 9 months

1
0
0 0

Re: ReactOS

by Jason Filby

Thanks Jim, I passed your regards on to the development team. I think sometimes we forget the great promise that ReactOS holds, but then someone like yourself reminds us. Cheers Jason On 8/23/05, Jim101 <jim101(a)bellsouth.net> wrote: > > I had hoped beyond hopes that someone was working on a truly open source > alternative to windows that could easily run any program ever made for > it, and I stumble across this project. > > All I can say is THANK YOU, and I wish your whole group the most > heartfelt best of luck. It would be the one thing that squared a wrong > done many years back by that little thief. To have an OS that would be > completely compatible with them all is a dream that far to many of us > share, and for it to be open source well. I just don't know what to say > I am ecstatic about it. Once again the very very best to each and > everyone of you that make it happen. > > For people like myself being disabled and on a fixed income the prices > that MS puts on their programs just sickens me. I have never intended to > be a thief in my life, I served my County and worked up until the day I > fell to the ground, never to recover completely. Then fought nearly 3 > years to get the measly little they give me back of my own money. And it > just irks me to see then do as they do, I mean I am all for a person > getting paid for their time and effort, it is only fair. but to charge > prices that most people can not archive, that is not how it was meant to > be. Anyway I am rambling, I just wanted to be sure you all knew that > there are many of us that would love to see your dream "and ours" come > true! > Best of luck! and God Bless! > >

19 years, 9 months

2
1
0 0

ROS-release prepared

by Robert Köpferl

Hi, I prepared a distribution of ros 0.2.7 release. However, I have no good feeling. Not very reproducable (at least I didn't get the rule, yet) it makes problems in qemu. -Sometimes the setup without format doesn't work (crash) -Then the creation of some hive didn't work -> freeldr can't boot -Install works, boot fails At least I have an archive with qemu and working 0.2.7 Maybe that's all related. Possibly am I operating at some limit. Moving the mouse fills up the last bit of memory. Actually, however, if this is the same on our customers pcs, I don't like the idea of delivering that... Opinions

19 years, 9 months

8
19
0 0

ReactOS 0.2.7 setup bug

by Lucio Diaz

Tested in real software. Sintoms: Setup start loading files, after the load a blue screen with the sentence "reactos setup" and two red lines appears in the top and the system lights become busy. After ten minutes of business nothing have happened and the bloq num keys of the keyboard are blocked (no light) so a hang or eternal cicle must be suspected. This computer used to load 0.2.5 (no hardware changes that i know, only software ones) Hardware: Semperon 2800+ 2 Ide HDD -Linux in the second (master boot record of the computer is here) with Grub loading both Suse and Yoper.(Filesystems a bit complex layout: fat, ext2, ReiserF, swap) -Windows 98 with a screwed MBR cause on installing grub i selected the wrong HDD once and my reactos loader was overwriten with grub.(all fat) A PS2 mouse and a PS2 keyboard. Gygabyte 2004 RZ mainboard with integrated ethernet and sound. Winfast graphic card. Realtek netcard (dont remember the model). DVD writemaster CD burner polaroid Any idea? Best Regards, Lucio Diaz. ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

19 years, 9 months

2
1
0 0

ReactOS 0.2.7 Release is out

by Robert Köpferl

After a long time and some delays, the next version of Reactos is out. Reactos 0.2.7 is out on sourceforge.net, ready to download and explore. For your convenience, here's the official change log: ChangeLog-0.2.7 From ReactOS The changelog for 0.2.7 in terms meaningful to technical end-users. Table of contents 1 Generic 1.1 Overview 1.2 Main 0.2.7 Changes 1.3 Known Bugs 1.4 Translation 1 ReactOS Core 1.1 Kernel + Executive (NTOSKRNL) 1.2 Kernel Mode Drivers 1.2.1 Input Device 1.2.2 ACPI 1.2.3 PCI 1.2.4 SERIAL 1.2.5 USB 1.2.6 VFAT 1.2.7 VGA 2 Networking 3 Session Manager (SMSS) 4 Win32(tm) Personality 4.1 User mode subsystem server (CSRSS) 4.2 Kernel mode subsystem server (WIN32K) 4.3 Win32(tm) Libraries 4.3.1 ADVAPI32 4.3.2 KERNEL32 4.3.3 SETUPAPI 4.3.4 DirectX 4.3.5 Userenv 4.4 Libraries shared with Wine 4.4.1 USER32 4.5 Win32(tm) Applications 4.5.1 IPConfig 4.5.2 CMD 4.5.3 TASKMGR 4.5.4 EXPLORER 4.5.5 WINEFILE Generic Overview With the release of 0.2.7 we, the ReactOS Team, have once again gained further compatibility with Microsoft Windows. We have aligned our headers with those of the Windows SDK which gives us a greater range of driver compatibility. We have also kept ourselves compliant with the latest GCC compiler which with our new build system provides a faster and more efficient building processing. We have elected a new UI coordinator and work has begun to redo the interfaces seen by the user. Many of our advancements aren't obvious to the end user, but rest assured that the inner workings are coming together with work in USB, Plug and Play, and networking that will blow you away in our next release. Main 0.2.7 Changes * Header clean up to compatible Windows SDK headers. Implemented and used NDK. ReactOS is now built with our own headers. Alex Ionescu, Filip Navara, Steven Edwards * New My computer, Command Prompt, and Logo Icons. Mindflyer * New build system called rbuild. Based on xml, it allows for auto generated makefiles. Casper Hornstup * Improved appearance of the first stage installer. Alex Ionescu * GCC 4.x.x build fixes. Thomas Weidenmueller, Alex Ionescu Known Bugs ReactOS will fail to boot with a AllocConsole error when a ps/2 mouse is not attached on some hardware. Bug 688 (http://reactos.com/bugzilla/show_bug.cgi?id=688) This ReactOS release requires 64MB RAM to complete the first stage installer. Bug 703 (http://reactos.com/bugzilla/show_bug.cgi?id=703) Translation * Swedish translations by Andreas Bjerkeholt (harteex(a)gmail.com) * Swedish translations by Kris Engeman * Czech translations by Potapnik <jirka(a)studioprojekt.cz> * Swedish translations by David Nordenberg * French translation by Usurp * Polish translation by Sebastian Gasiorek <zebasoftis(a)gmail.com> * Belgian (point/Flemish) keyboard layout by i386DX <i386dx(a)hotmail.com> ReactOS Core Kernel + Executive (NTOSKRNL) (Hervé Poussineau) * Implemented: o IoRegisterDeviceInterface o IoSetDeviceInterfaceState o IoRegisterPlugPlayNotification o IoUnregisterPlugPlayNotification o PoRequestPowerIrp o IRP_MN_QUERY_RESOURCE_REQUIREMENTS for devices enumerated by Root bus (Eric_Kohl) * Implemented: o PLUGPLAY_GET_RELATED_DEVICE and PLUGPLAY_DEVICE_STATUS. o PlugPlayControlProperty and PlugPlayControlGetDeviceDepth o CM_Get_Global_State/CM_Get_Global_State_Ex (Alex Ionescu) * Kernel (Ke) o Implemented Guarded Mutex: + KeAcquireGuardedMutex, KeEnterGuardedRegion, KeLeaveGuardedRegion, KeInitializeGuardedMutex, KeAcquireGuardedMutexUnsafe, KeReleaseGuardedMutexUnsafe, KeAcquireGuardedMutex, KeReleaseGuardedMutex, KeTryToAcquireGuardedMutex o Fixed critical APC queuing and delivery bugs o Optimized Entering/Leaving critical sections and enabled APC delivery after each leave, if required. o Fix KeWaitForMultipleObjects if WaitAll was used. o Rewrote Context Switching to be faster. o Fixed KINTERRUPT structure and fixed KeDisconnectInterrupt o Fixed a bug where Kernel Queues were inserted on the Ready Thread list. * Input/Output (Io) o Implemented IoIsfileOriginRemote, IoGetLowerDeviceObject, IoGetDiskDeviceObject, IoGetRequestorSessionId, IoGetRequestorProcessId, IoRegisterBootDriverRetinialization, IoAttachDevicetoDeviceStackSafe, IoEnumerateDeviceObjectList, IoGetDeviceAttachmentBaseRef, IoDetachDevice, IoRaiseHardError o Fixed Controller Objects implementation. o Fixed Attaching to devices (IoAttachDevice) the driver will be notified with IO_ATTACH_DEVICE_API. o Fixed IoAttachDevicetoDeviceStack and IoAttachDevice to call the Safe cuntion. o Optimized IoGetRelatedDeviceObject o Removed IoOpenDeviceInstanceKey and IoQueryDeviceEnumInfo. o Cleaned up IopAllocateVpb o Optimized IoCreateDevice, add support for more flags and remove hard-coded sector size and incorrect sizes being set. o Fixed IRP Code not to zero out the IRP, free MDLs in failure cases, set the right IRP flags and set the I/O Object Type. o Reimplemtented 2nd-stage completion for IRPs to free ALL MDLs, free memory depending on the flags used, don't call I/O Completion if an APC is registered, don't set event/call APCs in some failure cases, don't use certain fields after the pointer can become invalid. o Use the right stack count in I/O Operations. o Fixed IopDeleteFile to fix a memory leak and dereference the completion port. o Fixed IopCloseFile, NtQueryInformationFile, NtFlushBuffersFile, NtQueryDirectoryFile, NtReadFile, NtWriteFile, NtSetInformationFile, IopSecurityFile, IopQueryFileName, NtDeviceIoControlFile, NtLockFile, NtUnlockFile which contained several bugs related to IRPs and completion, which were making assumptions or not supporting all the possibilities, as well as signlaing the wrong event or making the wrong kind of call, or using the wrong device object. o Implemented Lookaside lists for IRP packets to increase the allocation/deallocation speed by over 400%. o Optimized Completion Packets by piggybacking them on IRP packets if possible, and added the right memory flags to free them properly. o Share NtDeviceIoControlFile and NtFsIoControlFile o Fixed IRP cancelation. o Rewrote I/O Interrupt Functions to match new structure and optimized some code paths. * Process Manager (Ps) o Created Memory Manager (Mm) functions when toucing process/memory o Created Kernel (Ke) functins when touching kernel structures and semantics. o Cached and optimized System DLL (ntdll) Loading/Mapping, so it is done only at startup. o Implemented NtOpenProcess, PsRemoveLoadImageNotifyRoutine, PsGetCurrentProcessSessionId, PsSetLegoNotifyRoutine, PsRemoveCreateThreadNotifyroutine, PsGetVersion o Rewrote Process/Thread creation and exit functions. * Memory Manager (Mm) o PEB and TEB are now properly allocated in memory, allowing 4KB granularity instead of 64KB, removed all the hacks which allowed this earlier. o Implement MmCreateKernelStack and MmDeleteKernelStack o Took out many system structures from NonPaged Pool to Paged Pool to reduce physical memory consumption. o Removed pool debugging functions in retail builds to increase the speed. o Don't allorw NtQueryVirtualMemory for kernel-mode addresses. o Fixed bug in memory mapping which caused large applications to BSOD the system. o Made the PE Loader more lenient so it can load some other valid executables. * Executive (Ex) o Fixed the lookaside functions, their macros and the way the functions were being exported. o Moved Win32k Object Registration inside Win32k. The pointers and initlization is now done when Win32k loads. * Debugging Services (Dbgk/Kd) o Implemented some Dbgk code for user-mode bugging. o Implemented modular debugging services for Bochs, GDB, etc. * Object Manager (Ob) o Implemented Fast Referencing stubs. o Rewrote ObQueryNameString. o Rewrote ObjectType creation to match the structures, flags and semantics present in NT's Object Manager, from the caller's point of view. o Implemented Object Create Information structure and semantics when capturing data from user-mode, securing and removing a lot of kernel exloits. o Fixed ObCreateObject and ObInsertObject to work like on Windows. ObCreateObject only allocates the Object, while ObInsertObject does everything else. * File System Runtime (FsRtl) o FsRtlMdlRead, FsRtlMdlReadComplete, FsMdlReadCompleteDev, FsRtlMdlWRiteComplete, FsRtlMdlWriteCompleteDev, FsRtlPrepareMdlWrite, CcMdlReadCompleted, CcMdlWriteComplete, CcMdlReadCompleteDev, FsRtlAllocateResource, FsRtlIsPagingFile, FsRtlBalanceReads * Security Subsystem (Se) o Implemented SeCreateAccessState, SeDeleteAccessState, SeSetAccessStateGenericMapping based on a patch fy Javier M. Mellid. (Thomas_Weidenmueller) * Implemented RtlHashUnicodeString * Moved ntdll's atom table implementation to rtl, rewrote it to use proper structures and share the generic implementation between ntoskrnl and ntdll * Updated the rtl handle table implementation to use proper structures. Reserved handles are not yet supported correctly. Kernel Mode Drivers Input Device * i8042prt driver by tinus. ACPI * Implement IRP_MN_QUERY_RESOURCE_REQUIREMENTS (Hervé Poussineau) PCI * Report correct list in IRP_MN_QUERY_RESOURCE_REQUIREMENTS (Hervé Poussineau) SERIAL (Hervé Poussineau) * serial.sys driver completed except control handflow (XON/XOFF) * serenum.sys driver completed. It enumerates mice plugged on serial ports USB * UHCI HCD driver supports recognizing Memory type of resource (Aleksey_Bragin) (Hervé Poussineau) * UHCI controller driver, that uses Cromwell USB stack * Basic USB hub driver, that sometimes reports connected devices VFAT * Implement FSCTL_IS_VOLUME_DIRTY and FSCTL_MARK_VOLUME_DIRTY (Hervé Poussineau) VGA * Implement IOCTL_VIDEO_QUERY_AVAIL_MODES, IOCTL_VIDEO_QUERY_CURRENT_MODE, IOCTL_VIDEO_QUERY_NUM_AVAIL_MODES (Hervé Poussineau) * VMWare 5 video driver works (GvG) and (Filip_Navara) * Qemu video drive works (GvG), (Alex_Ionescu), and (Filip_Navara) Networking * Implemented WSAStringToAddressA and WSAStringToAddressW in ws2_32 (Magnus Olsen) * Added dhcp service and make it start. (Art_Yerkes) (WaxDragon) * Implement get* integer reading. * Properly implement ipv4addrs (validates a set of IPv4 addresses) * Limit returned DNS servers to 1 until we fix iphlpapi. Session Manager (SMSS) * Removed loading of the kernel mode part of Win32 emulator (win32k.sys). * Removed running winlogon.exe Win32(tm) Personality User mode subsystem server (CSRSS) * Added loading of the kernel mode part of the Win32 emulator (win32k.sys); * Run winlogon.exe * Implemented EnumSystemLocalesW (Aleksey_Bragin) Kernel mode subsystem server (WIN32K) (Magnus Olsen) * Implement NtGdiDdCanCreateSurface and NtGdiDdBlt for DirectX (untested) * StrechBitBlt for all Bpp (not full implemet use the code as ref) * partially implemented fullscreen in changedisplay setting I can play winquake in fullscreen now :) * Implement NtGdiGetSystemPaletteUse and NtGdiSetSystemPaletteUse this code have been taken from wine * fix winquake color glitc bug the text are now whie instead for black (Magnus Olsen) * Implement NtGdiAnimatePalette (partly ripped from Wine does not anime 100% of the palette) (Hervé Poussineau) * Speed optimze the bitblt By (Magnus Olsen), (Gregor_Anich), (Alex_Ionescu), (GvG) see svn log * Repair GDI handle debugging functionality. (Filip_Navara) * Implement NtGdiUnrealizedObject (James_Tabor) * Implement WH_KEYBOARD_LL hook (GvG) Win32(tm) Libraries ADVAPI32 (Eric_Kohl) * Implemented LockServiceDatabase, UnlockServiceDatabase, ControlService, QueryServiceStatus. * Implemented OpenSCManagerA, OpenServiceA, OpenServiceW and QueryServiceStatus (Thomas_Weidenmueller) * Ported BuildTrusteeWithObjectsAndName and BuildTrusteeWithObjectsAndSid from wine. * Implemented RegOpenCurrentUser * Implemented OpenAndMapFileForRead, RetreiveFileSecurity, StampFileSecurity, TakeOwnershipOfFile and UnmapAndCloseFile. * Implemented RegOpenUserClassesRoot * Implemented IsTokenRestricted(), inspired by a patch to winehq by James Hawkins * Implemented TokenRestrictedSids KERNEL32 * Implemented GetCommProperties, ClearCommError, CommConfigDialogA, CommConfigDialogW (Saveliy Tretiakov) * Implemented GetCommConfig, SetCommConfig, FindFirstFileExW (Dmitry Philippov) SETUPAPI (Hervé Poussineau) * Work on devices enumeration by implementing: o CM_Enumerate_Classes(_Ex) o SetupDiCreateDeviceInfoA o SetupDiCreateDeviceInfoListExW o SetupDiEnumDeviceInfo o SetupDiGetActualSectionToInstallA o SetupDiGetClassDescriptionExA o SetupDiGetClassDevs(Ex)A/W o SetupDiGetDeviceInterfaceDetailA/W o SetupDiGetDeviceRegistryPropertyA/W (Eric_Kohl) * Implemented: o ConcatenatePaths o MyGetFileTitle o GetVersionInfoFromImage o StringTableDuplicate DirectX Dorp last sync with wine and userhook Before we can sync with wine we need to rewrite the enum and reg of device so it working fine in reactos and windows. Add svn rev 15043 + only userhooks for the mouse at last the mouse are working in tribles windows mode but in full screen it is bit chopy. Not tested tribles in reactos with the new code. Userenv David Nordenberg: Swedish translation, proofread by Andreas Bjerkeholt Libraries shared with Wine (GvG) * Sync to Wine-20050419 * Sync to Wine-20040419 * Sync to Wine-20050524 * Sync to Wine-20050628 USER32 * Implementation of DragDetect. Based on Wine code (C) 1993, 1994 Alexandre Julliard. (Filip_Navara) (James_Tabor) * Implemented: o TrackMouseEvent. o NtUserGetAsyncKeyState and support for TrackMouseEvent. o DrawMenuBar. o CheckMenuRadioItem. Not fully tested. o GetMenuString A & W. Not fully tested. o ModifyMenu A & W. o MDICascade, MDITile and WIN_ListChildren Win32(tm) Applications IPConfig (Tim Jobling <tjob800(a)yahoo.co.uk>) * Relicense to GPL. * Display NodeType with meaningfull Human readable names. * Exclusively use TCHAR strings. * Display Physical Address, DHCP enabled state, IP Addresses/Netmasks, * Default Gateway, DHCP server and DHCP Lease times. * Parse command line options. * Default to only showing the IP/SM/DG is no options specified * Handel option: /All and /? * Display message about all unimplemented options. * Changed C++ style commenting to C style CMD (Magnus Olsen) * Remove all hardcode string to own rc file. * Cache codepage instead call on win32 api for it whole time. * Add *.* syntax to Dir * Bugfix Color now it work as it should * Bugfix CD "program files" so it works * Implement CD s* * translate %errorlevel% to a value when it pass at command line. Now is errorlevel implement as it should. left todo check all cmd command that they are setting right value * fix a small bug in choice.c so it does print out choice "sadsad" right * add %time% and %cd% internal value. Example echo %cd% or echo %time%. * add %DATE% example echo %date% are working now. Bugfix date so it print out the week days names. * adding %RANDOM% example how to use it echo %random% * adding %cmdcmdline%, example how to use it echo %CMDCMDLINE% * add %CMDEXTVERSION% example to use it echo %CMDEXTVERSION% the value are hardcode to 2. for it is that value ms win2k / winxp report back. thx arty to test it in win xp. * quick dirty hack getting our copy working with 1>null by me, thanks to Hartex and Brandon to hunt down where the bug was. (Frik85) * Add Help command (By Frik85) * Add german language resource to the ReactOS Command Processor (not completely finished, I will update it as soon as possible) Martin Rottensteiner (2005only(a)pianonote.at): * set errorlevel to 9009 if command not found * implemented exit /b # in batchfiles (Brandon_Turner) * Added exclusive deletion "del * -abc.txt -text*.txt" * Fixed bug to allow MS style wildcards + code clean up added /y and /-y in move.c * simple check to fix > and | bug with 'rem' * Implemented /A in delete, example "del /A:H /A:-R *.exe -ping.exe" * Bug fix color.c, now it is working as ms cmd color. * Fix bug "mv foo.txt c:\temp gives you c:\tempfoo.txt" TASKMGR * Remove some hardcode string tested by Harteex (Filip_Navara) EXPLORER * Stepwise taskbar resizing (charn <charn89(a)hotmail.com>) * Swedish translation ([[David Nordenberg (dnordenberg [at] users.sourceforge.net) ]]) * option to build Explorer as ROS Shell without integrated explorer part (Martin Fuchs) * display of custom folders in start menu root (Martin Fuchs) * fix of listbox insert algorithmus (Martin Fuchs) * Czech translation of Explorer (Luk _ "denzil" Frolka <d3nzil(a)gmail.com>) * Russian Translation (Done by Dmitry Philippov, checked by fireball, DarkHobbit and others) * French Translation (hpoussin) * split of big explorer resource file into smaller language specific rescource scripts (Martin Fuchs) * Implemented part of screensaver functions, get values from reg, and show screensaver (<sikker2004(a)yahoo.com>) WINEFILE * Czech translation (Denzil <d3nzil(a)gmail.com>) * Swedish translation (David Nordenberg, proofread by Andreas Bjerkeholt) * implementation of owner drawn context menus (Martin Fuchs) * from WINE: add czech and swedish resource files (Martin Fuchs) * from WINE: Change SUBLANG_DEFAULT to SUBLANG_NEUTRAL for LANG_SPANISH in all resources, so that Spanish locales other than Spain also use Spanish resources. (Alex Villacís Lasso <a_villacis(a)palosanto.com>) * from WINE: Spanish translation (José Manuel Ferrer Ortiz <jmfo1982(a)yahoo.es>) * from WINE: Update of Portuguese translation (Marcelo Duarte <wine-devel(a)bol.com.br>, Am‚rico Jos‚ Melo <mmodem00(a)netvisao.pt>, Francois Gouget <fgouget(a)codeweavers.com>) * from WINE: Update of German translation. (Henning Gerhardt <henning.gerhardt(a)web.de>) * display source path in "move file" dialog (Martin Fuchs) * network connect and disconnect dialogs (Martin Fuchs) * "format disk" dialog (Martin Fuchs) * display free and total disk space (Martin Fuchs) * switching of file sort order (Martin Fuchs) * from WINE: add polish resource file (Martin Fuchs) * window refresh in shell mode (Martin Fuchs) * implement file filtering (matching file name patterns and file types) (Martin Fuchs) * refresh display after executing a context menu command (Martin Fuchs) * file copy, move and delete commands (Martin Fuchs) * file properties dialog ([Martin Fuchs], partly based on Rob D.'s winfile code) * from WINE: Update German resource files (Henning Gerhardt <henning.gerhardt(a)web.de>) * switch to WIN32 API string functions (Martin Fuchs) * Updated winefile French resources (Jonathan Ernst <Jonathan(a)ErnstFamily.ch>) * Sync source code and resource scripts between WINE and ROS WINE and switch to UNICODE compilaton in Wine (Martin Fuchs)

19 years, 9 months

4
3
0 0

Problems bochs and reactos

by Jeroen van Iddekinge

Hi all, I downloaded ReactOS 0.2.7 iso. THe installation whent fine, but after booting the system stops and bochs keeps outputting the following messages: 00311505974i[CPU0 ] allow_io(): IO addr 3c4 (len 1) outside TSS IO permission map (base=ffff, limit=2068) #GP(0) 00311506230i[CPU0 ] allow_io(): IO addr 3c5 (len 1) outside TSS IO permission map (base=ffff, limit=2068) #GP(0) 00311506532i[CPU0 ] allow_io(): IO addr cf8 (len 4) outside TSS IO permission map (base=ffff, limit=2068) #GP(0) 00311506815i[CPU0 ] allow_io(): IO addr cfc (len 4) outside TSS IO permission map (base=ffff, limit=2068) #GP(0) what whrong? The bochsrc.txt is: ata0:enabled=1, ioaddr1=0x1f0,ioaddr2=0x3f0,irq=14 ata1:enabled=1, ioaddr1=0x170,ioaddr2=0x370,irq=15 ata0-master: type=disk, path="c.img", mode=flat, cylinders=1040, heads=16, spt=63 ata1-master: type=cdrom,path=ReactOS.iso,status=inserted megs:64 romimage:file=/usr/share/bochs/BIOS-bochs-latest, address=0xf0000 vgaromimage:file=/usr/share/bochs/VGABIOS-lgpl-latest-cirrus vga: extension=cirrus boot:c config_interface:textconfig display_library:sdl log:bochs.log debug:action=ignore info:action=report error:action=report panic:action=ask vga_update_interval: 250000 keyboard_serial_delay: 200 keyboard_paste_delay: 100000 ips: 10000000 Regards, Jer

19 years, 9 months

1
1
0 0

Re: [ros-diffs] [weiden] 17474: added a macro IsKernelPointer() to test whether a pointer value points to the kernel address space. This is needed because on IA-64 the MSB is not necessarily set for pointers to the kernel address space.

by Filip Navara

weiden(a)svn.reactos.com wrote: >added a macro IsKernelPointer() to test whether a pointer value points to the kernel address space. This is needed because on IA-64 the MSB is not necessarily set for pointers to the kernel address space. > >Modified: trunk/reactos/ntoskrnl/include/internal/ntoskrnl.h >Modified: trunk/reactos/ntoskrnl/ob/wait.c > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/ntoskrnl/include/internal/ntoskrnl.h* > >--- trunk/reactos/ntoskrnl/include/internal/ntoskrnl.h 2005-08-22 10:51:05 UTC (rev 17473) >+++ trunk/reactos/ntoskrnl/include/internal/ntoskrnl.h 2005-08-22 13:38:30 UTC (rev 17474) >@@ -147,8 +147,26 @@ > > #define ProbeForReadLargeInteger(Ptr) ((LARGE_INTEGER)ProbeForReadGenericType(&(Ptr)->QuadPart, LONGLONG, 0)) > #define ProbeForReadUlargeInteger(Ptr) ((ULARGE_INTEGER)ProbeForReadGenericType(&(Ptr)->QuadPart, ULONGLONG, 0)) > > > >+/* >+ * Use IsKernelPointer to test whether a pointer points to the kernel address >+ * space >+ */ >+#if defined(_X86_) || defined(_M_AMD64) > > > > > >+/* for x86 and x86-64 the MSB is 1 so we can simply test on that */ >+#define IsKernelPointer(Ptr) ((LONG_PTR)(Ptr) < 0) >+ >+#elif defined(_IA64_) >+ >+/* on Itanium if the 24 most significant bits are set, we're not dealing with >+ user mode pointers. */ >+#define IsKernelPointer(Ptr) (((ULONG_PTR)(Ptr) & 0xFFFFFF0000000000ULL) != 0) >+ >+#else >+#error IsKernelPointer() needs to be defined for this architecture > > > #endif > > >+ >+#endif > > This looks really really wrong ... the macro will incorrectly evaluate to TRUE for user mode pointers on 3GB kernels. I don't understand the purpose of the code, but why don't you just check for Ptr >= MM_SYSTEM_RANGE_START ? - Filip

19 years, 9 months

2
1
0 0

dma problem

by Hartmut Birr

Hi, it seems that the routines for allocating a dma adapter object are broken. For a pci cards, the channel is always -1. The adapter object is stored at HalpEisaAdapter[-1]. It does overwrite something. This adapter object is used for all pci cards (scsi controller, network cards, ...). Usually every pci card must have its own adapter object. - Hartmut

19 years, 9 months

2
1
0 0

include file problem

by Hartmut Birr

Hi, I need for some modifications the definitions of the resource structures (CM_FULL_RESOURCE_DESCRIPTOR, ..) in usetup. The structures are defined in winddk.h. It seems that it isn't possible to include winndk.h if ntndk.h is already included. I get errors like this: ... include/ndk/extypes.h:37:1: warning: "SEMAPHORE_QUERY_STATE" redefined In file included from w32api/include/ddk/ntddk.h:67, from subsys\system\usetup\usetup.h:38: w32api/include/ddk/winddk.h:342:1: warning: this is the location of the previous definition In file included from include/ndk/ntndk.h:43, from subsys\system\usetup\usetup.h:41: include/ndk/cmtypes.h:23: error: redeclaration of `enum _KEY_INFORMATION_CLASS' include/ndk/cmtypes.h:24: error: conflicting types for 'KeyBasicInformation' ... Our headers are broken. - Hartmut

19 years, 10 months

2
1
0 0

RE: [ros-dev] Website Design Voting

by Murphy, Ged (Bolton)

This has been 2 weeks now. Can we finalise it and start working towards getting the new site up please? Thanks, Ged. > -----Original Message----- > From: ros-dev-bounces(a)reactos.com [mailto:ros-dev-bounces@reactos.com] On Behalf Of Freeworld > Sent: 4. august 2005 23:28 > To: ros-dev(a)reactos.com; ros-general(a)reactos.com; ros-web(a)reactos.com > Subject: [ros-dev] Website Design Voting > > Hello folks! > > Things are going very well with the new site and it is time that the > community/developers choose a design for our now homepage. The choices: > (Thanks to Klemens Friedl for carrying the suggestions together and for > all his other work.) > > 1) Jason Filby: > http://reactos.com/newsite/reactos_index.html > <http://reactos.com/newsite/reactos_index.html> > > 2) Klemens Friedl: > http://frik85.fr.funpic.de/reactos/ <http://frik85.fr.funpic.de/reactos/> > > 3) Mikko Tikkanen (created the layaut, only a pic) > http://devnet.dnsalias.net/guidesign/web_mockup.jpg > <http://devnet.dnsalias.net/guidesign/web_mockup.jpg> (Mikko Tikkanen > design) > Brandon Turner (created a html version): > http://brandonturner.org/ROS/index.html > <http://brandonturner.org/ROS/index.html> (Brandon Turner work) > > 4) Mindflyer (based on mikko's design): > http://www.mufunyo.net/reactos/web/ > <http://www.mufunyo.net/reactos/web/> (currently not available!) > > 5) jh: > http://reactos.com:8080/pipermail/ros-web/attachments/20050614/624eb1e9/ros- 0001.png > <http://reactos.com:8080/pipermail/ros-web/attachments/20050614/624eb1e9/ros -0001.png> > > 6) Gennadiy Dolzhenko: > http://optim.sorb.com.ua/ros > http://optim.sorb.com.ua/ros2 > > Allowed votes are: > 1) Jason Filby > 2) Klemens Friedl > 3) Mikko Tikkanen > 4) Mindflyer > 5) jh > 6) Gennadiy Dolzhenko 1 > 7) Gennadiy Dolzhenko 1 > > If the designers name is not right or you want the respective > mailinglist-posting please send me an email. > > The voting will last for two weeks. > > Greetings > Michael Wirth ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

19 years, 10 months

4
3
0 0

Re: [ros-svn] [gvg] 17434: Import VMware open source BusLogic driver

by Alex Ionescu

gvg(a)svn.reactos.com wrote: >Hartmut made it work in ReactOS. > > I hope Hartmut made ReactOS work with *it*. We don't have the liberty of patching every single NT driver that we will want to run on ROS :) Best regards, Alex Ionescu

19 years, 10 months

2
1
0 0

Re: [ros-dev] Website Design Voting

by reactos

I think: just go ahead and publish it as fast as you can, the world has been waiting long enough. By the way, really nice result, it's simple and nice! Yours sincerely, Jaix Bly ----Ursprungligt meddelande----- From: Freeworld michael(a)freeworld.net Date: Thu, 18 Aug 2005 15:47:11 +0200 To: ReactOS Development List ros-dev(a)reactos.com Subject: Re: [ros-dev] Website Design Voting > Yes you're right. > > The votin is closed now. And the winner is... > > Klemens Friedl > http://frik85.fr.funpic.de/reactos/ > > He's got far the most votes. We're heavily working on the new site and > hope to get it up soon. What do you think of releasing it concurrent to > ReactOS 0.3? > > Greetings > Michael > > Murphy, Ged (Bolton) wrote: > > >This has been 2 weeks now. > >Can we finalise it and start working towards getting the new site up please? > > > >Thanks, > >Ged. > > > > > > > > > >>-----Original Message----- > >>From: ros-dev-bounces(a)reactos.com [mailto:ros-dev-bounces@reactos.com] On > >> > >> > >Behalf Of Freeworld > > > > > >>Sent: 4. august 2005 23:28 > >>To: ros-dev(a)reactos.com; ros-general(a)reactos.com; ros-web(a)reactos.com > >>Subject: [ros-dev] Website Design Voting > >> > >>Hello folks! > >> > >>Things are going very well with the new site and it is time that the > >>community/developers choose a design for our now homepage. The choices: > >>(Thanks to Klemens Friedl for carrying the suggestions together and for > >>all his other work.) > >> > >>1) Jason Filby: > >> http://reactos.com/newsite/reactos_index.html > >><http://reactos.com/newsite/reactos_index.html> > >> > >>2) Klemens Friedl: > >> http://frik85.fr.funpic.de/reactos/ > >> > >> > ><http://frik85.fr.funpic.de/reactos/> > > > > > >>3) Mikko Tikkanen (created the layaut, only a pic) > >> http://devnet.dnsalias.net/guidesign/web_mockup.jpg > >><http://devnet.dnsalias.net/guidesign/web_mockup.jpg> (Mikko Tikkanen > >> design) > >> Brandon Turner (created a html version): > >> http://brandonturner.org/ROS/index.html > >><http://brandonturner.org/ROS/index.html> (Brandon Turner work) > >> > >>4) Mindflyer (based on mikko's design): > >> http://www.mufunyo.net/reactos/web/ > >><http://www.mufunyo.net/reactos/web/> (currently not available!) > >> > >>5) jh: > >> > >> > >> > >http://reactos.com:8080/pipermail/ros-web/attachments/20050614/624eb1e9/ros- > >0001.png > > > > > ><http://reactos.com:8080/pipermail/ros-web/attachments/20050614/624eb1e9/ros > >-0001.png> > > > > > >>6) Gennadiy Dolzhenko: > >> http://optim.sorb.com.ua/ros > >> http://optim.sorb.com.ua/ros2 > >> > >>Allowed votes are: > >>1) Jason Filby > >>2) Klemens Friedl > >>3) Mikko Tikkanen > >>4) Mindflyer > >>5) jh > >>6) Gennadiy Dolzhenko 1 > >>7) Gennadiy Dolzhenko 1 > >> > >>If the designers name is not right or you want the respective > >>mailinglist-posting please send me an email. > >> > >>The voting will last for two weeks. > >> > >>Greetings > >>Michael Wirth > >> > >> > > > >************************************************************************ > >The information contained in this message or any of its > >attachments is confidential and is intended for the exclusive > >use of the addressee. The information may also be legally > >privileged. The views expressed may not be company policy, > >but the personal views of the originator. If you are not the > >addressee, any disclosure, reproduction, distribution or other > >dissemination or use of this communication is strictly prohibited. > >If you have received this message in error, please contact > >postmaster(a)exideuk.co.uk > ><mailto:postmaster@exideuk.co.uk> and then delete this message. > > > >Exide Technologies is an industrial and transportation battery > >producer and recycler with operations in 89 countries. > >Further information can be found at www.exide.com > > > > > >_______________________________________________ > >Ros-dev mailing list > >Ros-dev(a)reactos.com > >http://reactos.com:8080/mailman/listinfo/ros-dev > > > > > > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

19 years, 10 months

1
0
0 0

RE: [ros-dev] Website Design Voting

by Murphy, Ged (Bolton)

Freeworld wrote: > What do you think of releasing it > concurrent to ReactOS 0.3? Do you mean 0.2.7 ? 0.3 could be another year away ! Ged. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

19 years, 10 months

1
0
0 0

0.2.7 Status

by Brandon Turner

Hey Robert, How are things looking for 0.2.7? Should be expecting it soon? http://www.reactos.com/wiki/index.php/ChangeLog-0.2.7 is still looking kinda bare, we might want to make sure that gives a better repersentation of 0.2.7 when it comes out. Brandon

19 years, 10 months

5
4
0 0

RE: [ros-svn] [ion] 17417: Remove all non-official LPCstructures/defines/hardcoded hacks, and use actual correct sizes and structures.

by Ge van Geldorp

> From: ion(a)svn.reactos.com > > Remove all non-official LPC structures/defines/hardcoded > hacks, and use actual correct sizes and structures. This breaks a simple boot. ntoskrnl/include/internal/port.h previously defined QUEUEDMESSAGE as: typedef struct _QUEUEDMESSAGE { PEPORT Sender; LIST_ENTRY QueueListEntry; PORT_MESSAGE Message; UCHAR MessageData [MAX_MESSAGE_DATA]; } QUEUEDMESSAGE, *PQUEUEDMESSAGE; r17417 removed the MessageData member. Now in ntoskrnl/lpc/reply.c function EiReplyOrRequestPort() line 52: memcpy(&MessageReply->Message, LpcReply, LpcReply->u1.s1.TotalLength); writes outside allocated memory (MessageReply is a PQUEUEDMESSAGE, LpcReply->u1.s1.TotalLength is 292). This causes a subsequent ExFreePool to generate a page fault. Gé van Geldorp.

19 years, 10 months

1
0
0 0

End-of-merge for some components shared with Wine

by Ge van Geldorp

It's becoming impossible for me to keep some components synced with Wine. For some components, we have too many changes in our tree which were not submitted to Wine. I've tried to submit some of "our" changes, but was unable to answer questions asked by the Wine people, since I simply do not have enough knowledge of those particular DLLs. The original (ReactOS) authors of the changes are not interested or currently unable to answer either. So, the following components are now effectively forked: - tools/widl - lib/dinput - lib/setupapi - lib/winmm Gé van Geldorp.

19 years, 10 months

6
14
0 0

gdb stub patch

by Samuel Bronson

I was poking around in gdbstub.c, trying to get it to work a bit better. I managed to drastically reduce the time it takes GDB to attach, among other things, by not trying to send a stop reply packet (and so not responding to GDB's queries). The only reason it worked before is that, after all the other replies had timed out a few times each, it issued a `?' query, and finally interpreted the stop reply packet as the answer to that... there are some other changes, hopefully for the better.

19 years, 10 months

1
0
0 0

Website Design Voting

by Freeworld

Hello folks! Things are going very well with the new site and it is time that the community/developers choose a design for our now homepage. The choices: (Thanks to Klemens Friedl for carrying the suggestions together and for all his other work.) 1) Jason Filby: http://reactos.com/newsite/reactos_index.html <http://reactos.com/newsite/reactos_index.html> 2) Klemens Friedl: http://frik85.fr.funpic.de/reactos/ <http://frik85.fr.funpic.de/reactos/> 3) Mikko Tikkanen (created the layaut, only a pic) http://devnet.dnsalias.net/guidesign/web_mockup.jpg <http://devnet.dnsalias.net/guidesign/web_mockup.jpg> (Mikko Tikkanen design) Brandon Turner (created a html version): http://brandonturner.org/ROS/index.html <http://brandonturner.org/ROS/index.html> (Brandon Turner work) 4) Mindflyer (based on mikko's design): http://www.mufunyo.net/reactos/web/ <http://www.mufunyo.net/reactos/web/> (currently not available!) 5) jh: http://reactos.com:8080/pipermail/ros-web/attachments/20050614/624eb1e9/ros… <http://reactos.com:8080/pipermail/ros-web/attachments/20050614/624eb1e9/ros…> 6) Gennadiy Dolzhenko: http://optim.sorb.com.ua/ros http://optim.sorb.com.ua/ros2 Allowed votes are: 1) Jason Filby 2) Klemens Friedl 3) Mikko Tikkanen 4) Mindflyer 5) jh 6) Gennadiy Dolzhenko 1 7) Gennadiy Dolzhenko 1 If the designers name is not right or you want the respective mailinglist-posting please send me an email. The voting will last for two weeks. Greetings Michael Wirth

19 years, 10 months

17
23
0 0

RE: [ros-diffs] [ea] 17400: Add winemine.

by Casper Hornstrup

Can't we use "optional" here instead of "o"? I know it will require two more seconds to write, but it is much more self-documenting than "o". Casper ________________________________________ From: ros-diffs-bounces(a)reactos.com [mailto:ros-diffs-bounces@reactos.com] On Behalf Of ea(a)svn.reactos.com Sent: 15. august 2005 19:31 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [ea] 17400: Add winemine. Add winemine. Modified: trunk/reactos/bootdata/packages/reactos.dff ________________________________________ Modified: trunk/reactos/bootdata/packages/reactos.dff --- trunk/reactos/bootdata/packages/reactos.dff 2005-08-15 17:04:34 UTC (rev 17399) +++ trunk/reactos/bootdata/packages/reactos.dff 2005-08-15 17:30:20 UTC (rev 17400) @@ -299,6 +299,7 @@ modules\rosapps\cmdutils\mode\mode.exe 1 o modules\rosapps\cmdutils\touch\touch.exe 1 o modules\rosapps\games\solitaire\sol.exe 1 o +modules\rosapps\games\winemine\winemine.exe 1 o modules\rosapps\mc\mc.exe 1 o modules\rosapps\net\ncftp\ncftp.exe 1 o modules\rosapps\net\niclist\niclist.exe 1 o

19 years, 10 months

2
1
0 0

Re: [ros-svn] [greatlrd] 17380: change CMDLINE_LENGTH to 8192 to keep rbuild happy until dymatic alloc are in place

by James Tabor

greatlrd(a)svn.reactos.com wrote: > change CMDLINE_LENGTH to 8192 to keep rbuild happy until dymatic alloc are in place > > > Updated files: > trunk/reactos/subsys/system/cmd/cmd.h > Hi! My problem with building is fix with this patch. I would make sure this setting is the, no other, only minimum setting. Due to speed of allocating memory every time cmd is running. Thanks, James

19 years, 10 months

4
4
0 0

Re: [ea] 17396: CABMAN: add support for optional files (they are listed in the reactos.dff, but may not exist in the output-??? directory).

by Sylvain Petreolle

It seems you missed a test into your dfp.cxx change. The change of the series of if() else if() into a switch(){} is ok, except now it always returns CAB_STATUS_SUCCESS. + case CAB_STATUS_NOMEMORY: + printf("Insufficient memory to add file: %s.\n", SrcName); + break; + default: + printf("Cannot add file: %s (%lu).\n", SrcName, Status); + break; } - return CAB_STATUS_SUCCESS; } To restore the correct behaviour, you have to return Status; Kind regards, Usurp (aka Sylvain Petreolle) humans are like computers, yesterday the BIOS was all - today its just a word

19 years, 10 months

1
0
0 0

Re: [ros-diffs] [hbirr] 17397: Fixed a terminating NULL in IoRegisterDeviceInterface.

by Joseph Galbraith

I'm curious why we are making this string nul terminated? IoCreateSymbolicLink() should not care (I'm virtually certain it doesn't under windows.) And I'm pretty sure that IoRegisterDeviceInterface isn't expected to return a nul terminated string either. And I'm also pretty sure our implementation doesn't actually return it NUL terminated because the length doesn't include the NUL termination (rightly so or the symbolic link would actually have a NUL character as part of it's name) and the RtlMoveMemory() at the end of the function is based of off Length(). I'm pretty sure that virtually no windows kernel mode function taking a UNICODE_STRING structure (or a STRING structure) expects nul termination... Thanks, Joseph hbirr(a)svn.reactos.com wrote: > Fixed a terminating NULL in IoRegisterDeviceInterface. > > Modified: trunk/reactos/ntoskrnl/io/deviface.c > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/ntoskrnl/io/deviface.c* > > --- trunk/reactos/ntoskrnl/io/deviface.c 2005-08-15 16:41:43 UTC (rev 17396) > +++ trunk/reactos/ntoskrnl/io/deviface.c 2005-08-15 16:47:15 UTC (rev 17397) > @@ -815,7 +815,7 @@ > > RtlAppendUnicodeToString(SymbolicLinkName, L"\\"); > RtlAppendUnicodeStringToString(SymbolicLinkName, ReferenceString); > } > > - SymbolicLinkName->Buffer[SymbolicLinkName->Length] = '\0'; > > + SymbolicLinkName->Buffer[SymbolicLinkName->Length/sizeof(WCHAR)] = L'\0'; > > > /* Create symbolic link */ > DPRINT("IoRegisterDeviceInterface(): creating symbolic link %wZ -> %wZ\n", SymbolicLinkName, &PdoNameInfo->Name); >

19 years, 10 months

2
1
0 0

Caution, Wine Tests maybe Wrong!

by James Tabor

Hi all, When running ntdll_test or ntdll_crosstest with rtl selected, it will fail at the last test, test_HandleTables. Right at first I checked the wine headers and noticed the handle table structures are not the same as ros. B^| Wow, -what- -a- -sur- -prise-. Convert tests to Ros? 8^> James

19 years, 10 months

10
20
0 0

Test This App! Was: Untested (open source) software list Volunteers needed !!!

by James Tabor

James Tabor wrote: > > It's not gpl. I do consider this a good test app, but poorly written. > http://www.smidgeonsoft.prohosting.com/download/PEBrowse.zip > Haa! It really illustrates some weaknesses in Ros. > Hi! Has anyone bothered to test this application? Thanks, James

19 years, 10 months

2
1
0 0

Icons for CIS

by Casper Hornstrup

Hi. Is there any graphics artist here that can and want to create four icons for our Continuous Integration System? At http://sin.csh-consult.dk/ there is a table of changes committed to the repository. I want to add a new column "Build type" at the end containing these icons. The four icons are: ? = Unknown build type P = Partial build F = Full build F (underlined) = Required full build Casper

19 years, 10 months

2
1
0 0

Re: [ros-bugs] [Bug 708] Selfhosting (ros-on-ros compilation) fails.

by Brandon Turner

Hey, do you know when this started happening or has rbuild always had lines that are too long for ROS cmd? Should we just change CMDLINE_LENGTH to something else, because apparently CMDLINE_LENGTH is not really the max a line can be as rbuild works with MS cmd. Brandon ReactOS.Bugzilla(a)reactos.com wrote: >http://reactos.com/bugzilla/show_bug.cgi?id=708 > > > > > >------- Additional Comments From hartmut.birr(a)gmx.de 2005-12-08 16:14 ------- >cmd.exe uses a fixed size command and batch line buffer. 512 characters are >not enough for our current build system. > > >

19 years, 10 months

3
2
0 0

RE: [ros-svn] [hpoussin] 17162: Implement SetupGetInfFileListW andSetupGetInfInformationW

by Ge van Geldorp

> From: hpoussin(a)svn.reactos.com > > Implement SetupGetInfFileListW and SetupGetInfInformationW > Inf file parser now accept UNICODE files with FF FE header > Return required buffer size when buffer is too small in > SetupGetLineTextA/W, SetupGetStringFieldA/W > > > Updated files: > trunk/reactos/lib/setupapi/parser.c > trunk/reactos/lib/setupapi/setupapi.spec SetupGetStringFieldW() (and possibly others too) now return failure and set an error of ERROR_INSUFFICIENT_BUFFER when the passed in buffer and size are NULL and 0 resp. I think this is not correct. MSDN says: "If this function is called with a ReturnBuffer of NULL and a ReturnBufferSize of zero, the function puts the buffer size needed to hold the specified data into the variable pointed to by RequiredSize. If the function succeeds in this, the return value is a nonzero value." So buffer == NULL and size == 0 is a special case. Other code (e.g. the call in lib/setupapi/install.c line 328) depends on this behaviour and is now broken too. Gé van Geldorp.

19 years, 10 months

1
0
0 0

reactos.dff and optional files

by Emanuele Aliberti

Is there a way to declare a file 'optional' in reactos.dff? With 'optional' I mean a file that will go in the ISO image, if present, otherwise the declaration will be silently ignored. -- :Emanuele Aliberti

19 years, 10 months

1
0
0 0

To: WaxDragon re: msi crash

by Royce Mitchell III

apply this patch to latest svn and send me debug log Index: create.c =================================================================== --- create.c (revision 17328) +++ create.c (working copy) @@ -445,7 +445,7 @@ PDEVICE_EXTENSION DeviceExt; ULONG RequestedDisposition, RequestedOptions; PVFATCCB pCcb; - PVFATFCB pFcb; + PVFATFCB pFcb = NULL; PVFATFCB ParentFcb; PWCHAR c, last; BOOLEAN PagingFileCreate = FALSE; @@ -564,6 +564,10 @@ vfatReleaseFCB (DeviceExt, ParentFcb); if (NT_SUCCESS (Status)) { +#if defined(DBG) || defined(KDBG) + ASSERT ( pFcb ); + CcRosTraceCacheMap ( pFcb->SectionObjectPointers.SharedCacheMap, TRUE ); +#endif Status = vfatAttachFCBToFileObject (DeviceExt, pFcb, FileObject); if ( !NT_SUCCESS(Status) ) { @@ -577,6 +581,9 @@ pFcb, DeviceExt, &Irp->Overlay.AllocationSize); +#if defined(DBG) || defined(KDBG) + CcRosTraceCacheMap ( FileObject->SectionObjectPointer->SharedCacheMap, FALSE ); +#endif VfatSetExtendedAttributes(FileObject, Irp->AssociatedIrp.SystemBuffer, Stack->Parameters.Create.EaLength);

19 years, 10 months

1
1
0 0

RE: [ros-bugs] [Bug 715] New: random crash after recompiling trun k and at loading reactoOS

by Murphy, Ged (Bolton)

ReactOS.Bugzilla(a)reactos.com wrote: > > After successfull > make depends > make > make install > > I have copied the files inside the 2.6 hard disk image of ReactOS. Although I can't answer your initial problem, I can suggest that do a 'make bootcd' instead of 'make install', and then boot ROS in QEMU using the generated iso. Then you will have an install better suited to QEMU. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

19 years, 10 months

1
0
0 0

Re: [ros-svn] [hbirr] 17306: - Removed the hole pool allocation, because it needs to much memory and ros will not boot.

by Royce Mitchell III

hbirr(a)svn.reactos.com wrote: >- Removed the hole pool allocation, because it needs to much memory and ros will not boot. >- Allocate short blocks in one page. >- Split the used and free header. It makes it easier to implement a red zone check. > > > Can we use rpoolmgr.h for npool? I wrote it to be useable by both.

19 years, 10 months

3
3
0 0

UsbUhci Boot Falure

by James Tabor

At revision 17321. hivesys, ;USB UHCI Driver HKLM,"SYSTEM\CurrentControlSet\Services\usbuhci","Type",0x00010001,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Services\usbuhci","ErrorControl",0x00010001,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Services\usbuhci","Start",0x00010001,0x00000003 HKLM,"SYSTEM\CurrentControlSet\Services\usbuhci","Group",0x00000000,"Base" HKLM,"SYSTEM\CurrentControlSet\Services\usbuhci","ImagePath",0x00020000,"System32\DRIVERS\usbuhci.sys" HKLM,"SYSTEM\CurrentControlSet\Services\usbuhci","Tag",0x00010001,0x0000000f HKLM,"SYSTEM\CurrentControlSet\Services\usbuhci","DisplayName",0x00000000,"ReactOS USB UHCI controller miniport driver" HKLM,"SYSTEM\CurrentControlSet\Services\usbuhci\Enum","0",0x00000000,"PCI\VEN_1106&DEV_3104&SUBSYS_73401462&REV_82" HKLM,"SYSTEM\CurrentControlSet\Services\usbuhci\Enum","Count",0x00010001,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Services\usbuhci\Enum","NextInstance",0x00010001,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3104&SUBSYS_73401462&REV_82\0000","Service",0x00000000,"usbuhci" Debug, (drivers/usb/cromwell/uhci/fdo.c:293) UHCI: unknown minor function 0x8 (drivers/usb/cromwell/sys/linuxwrapper.c:479) IoGetDmaAdapter done 0x8D3EA638, m apRegisterCount=2 (drivers/usb/cromwell/uhci/uhci-hcd.c:2556) INF: drivers/usb/cromwell/uhci/uhci- hcd.c: USB Universal Host Controller Interface driver v2.1 (drivers/usb/cromwell/core/hcd-pci.c:74) usbcore: usb_hcd_pci_probe() called (drivers/usb/cromwell/sys/linuxwrapper.c:201) driver_register 0: 9d60e0b8 9d607d e4(drivers/usb/cromwell/core/usb.c:168) INF: drivers/usb/cromwell/core/usb.c: re gistered new driver hub (drivers/usb/cromwell/sys/linuxwrapper.c:137) usbcore: Created system thread 72 (drivers/usb/cromwell/sys/linuxwrapper.c:201) driver_register 1: 9d60e0e0 9d607d d0(drivers/usb/cromwell/core/hcd-pci.c:74) usbcore: usb_hcd_pci_probe() called (drivers/usb/cromwell/core/../linux/pci_hal.c:13) pci_enable_device() called... (drivers/usb/cromwell/core/../linux/pci_hal.c:21) pci_resource_start() called, x =0x0 (drivers/usb/cromwell/core/../linux/pci_hal.c:33) pci_resource_len() called, x=0 x0 (drivers/usb/cromwell/core/../linux/pci_hal.c:129) request_mem_region(): addr=0x de000000, len=0x100 (drivers/usb/cromwell/core/../linux/pci_hal.c:146) ioremap_nocache(): addr=0xde0 00000, len=0x100 (drivers/usb/cromwell/core/../linux/pci_hal.c:58) pci_set_drvdata() called... (drivers/usb/cromwell/core/hcd-pci.c:163) UnivHCI PCI-USB Controller (drivers/usb/cromwell/core/hcd-pci.c:183) irq 9, pci mem 9d61b000 (drivers/usb/cromwell/core/hcd.c:678) new USB bus registered, assigned bus numbe r 1 (drivers/usb/cromwell/uhci/../linux/pci_hal.c:33) pci_resource_len() called, x=0 x0 (drivers/usb/cromwell/sys/linuxwrapper.c:252) schedule_timeout: 5 ms (drivers/usb/cromwell/sys/linuxwrapper.c:286) schedule DONE!!!!!! (drivers/usb/cromwell/sys/linuxwrapper.c:252) schedule_timeout: 1 ms (drivers/usb/cromwell/sys/linuxwrapper.c:286) schedule DONE!!!!!! (drivers/usb/cromwell/sys/linuxwrapper.c:793) pci_alloc_consistent() size=8196 (drivers/usb/cromwell/sys/linuxwrapper.c:639) pci_pool_create(): UHCD PCI Slot/u hci_td size 48, 85/page (4096 alloc) (drivers/usb/cromwell/sys/linuxwrapper.c:639) pci_pool_create(): UHCD PCI Slot/u hci_qh size 48, 85/page (4096 alloc) (drivers/usb/cromwell/uhci/uhci-hcd.c:2264) INF: drivers/usb/cromwell/uhci/uhci- hcd.c: detected 4088 ports (drivers/usb/cromwell/uhci/uhci-hcd.c:2269) INF: drivers/usb/cromwell/uhci/uhci- hcd.c: port count misdetected? forcing to 2 ports (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e08ac0:0:0:0 (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e09000:0:0:0 (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e09000:0:0:1 (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e09000:0:0:2 (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e09000:0:0:3 (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e09000:0:0:4 (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e09000:0:0:5 (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e09000:0:0:6 (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e09000:0:0:7 (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e09000:0:0:8 (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e09000:0:0:9 (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e09000:0:0:10 (drivers/usb/cromwell/sys/linuxwrapper.c:704) pci_pool_alloc(): Allocating block 80e09000:0:0:11 (drivers/usb/cromwell/uhci/uhci-hcd.c:2098) ERR: uhci: USBCMD_HCRESET timed out! (drivers/usb/cromwell/core/message.c:159) usb_control_msg: devnum=1, size=0, tim eout=500 (drivers/usb/cromwell/core/message.c:43) usb_start_wait_urb(): urb devnum=1, tim eout=500, urb->actual_length=0 (drivers/usb/cromwell/core/urb.c:205) sub dev 8d3eb018 bus 8d3ec808 num 1 op 9d6 0e020 sub 9d603549 (drivers/usb/cromwell/core/hcd.c:985) submit_urb 8d3ea4c8, # 1, t 2 (drivers/usb/cromwell/core/hcd.c:400) root hub device address 1 (drivers/usb/cromwell/core/message.c:61) TRACE 3.1, timeout=500, awd.done=1 (drivers/usb/cromwell/core/message.c:159) usb_control_msg: devnum=1, size=8, tim eout=500 (drivers/usb/cromwell/core/message.c:43) usb_start_wait_urb(): urb devnum=1, tim eout=500, urb->actual_length=0 (drivers/usb/cromwell/core/urb(drivers/usb/cromwell/uhci/uhci-hcd.c:1898) ERR: d rivers/usb/cromwell/uhci/uhci-hcd.c: 9d61b000: host system error,.c:205) sub dev 8d3eb018 bus 8d3ec808 num 1 op 9d60e020 sub 9d603549 (drivers/usb/cromwell/core/hcd.c:985) submit_urb 8d3ea4c8, # 1, t 2 (drivers/usb/cromwell/core/message.c:61) TRACE 3.1, timeout=500, awd.done=1 <Snip... > (drivers/usb/cromw PCI problems? (drivers/usb/cromwell/uhci/uhci-hcd.c:1900) ERR: drivers/usb/cromwell/uhci/uhci- hcd.c: 9d61b000: host controller process error. something bad happened (drivers/usb/cromwell/uhci/uhci-hcd.c:1902) ERR: drivers/usb/cell/core/message.c :43) usb_start_wait_urb(): urb devnum=1, timeout=100, urb->actual_length=0 (drivers/usb/cromwell/core/urb.c:205) sub dev 8d3eb018 bus 8d3ec808 num 1 op 9d6 0e020 sub 9d603549 (drivers/usb/cromwell/core/hcd.c:985)romwell/uhci/uhci-hcd.c: 9d61b000: host con troller halted. very bad (drivers/usb/cromwell/uhci/uhci-hcd.c:1898) ERR: drivers/usb/cromwell/uhci/uhci- hcd.c: 9d61b000: host system error, PCI problems? (drivers/usb/cromwell/uhci/uhci submit_urb 8d3e1620, # 1, t 2 (drivers/usb/cromwell/core/message.c:61) TRACE 3.1, timeout=100, awd.done=1 (drivers/usb/cromwell/core/message.c:159) usb_control_msg: devnum=1, size=0, tim eout=100 (drivers/usb/cromwell/core/messa-hcd.c:1900) ERR: drivers/usb/cromwell/uhci/uhci -hcd.c: 9d61b000: host controller process error. something bad happened (drivers/usb/cromwell/uhci/uhci-hcd.c:1902) ERR: drivers/usb/cromwell/uhci/uhci- hcd.c: 9d61b000: host controlge.c:43) usb_start_wait_urb(): urb devnum=1, timeou t=100, urb->actual_length=0 (drivers/usb/cromwell/core/urb.c:205) sub dev 8d3eb018 bus 8d3ec808 num 1 op 9d6 0e020 sub 9d603549 (drivers/usb/cromwell/core/hcd.c:985) submit_urb 8dler halted. very bad 3e1568, # 1, t 2 (drivers/usb/cromwell/core/message.c:61) TRACE 3.1, timeout=100, awd.done=1 (drivers/usb/cromwell/sys/linuxwrapper.c:181) probe1 9d607dd0 (drivers/usb/cromwell/uhci/pdo.c:289) UHCI: IRP_MJ_PNP / unknown minor function 0xc (drivers/usb/cromwell/uhci/pdo.c:289) UHCI: IRP_MJ_PNP / unknown minor function 0xc (drivers/usb/cromwell/uhci/pdo.c:289) UHCI: IRP_MJ_PNP / unknown minor function 0x15 KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0xc0000005,0x80015b51,0x00000000,0xccccccd0) *** ntoskrnl.exe - Address 0x80015b51 base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:80015b51 <ntoskrnl.exe:15b51 (ntoskrnl/cm/regfile.c:2761 ( CmiScanKeyForValue))> cr2 ccccccd0 cr3 22000 Proc: 80c30af0 Pid: 4 <System> Thrd: 80c31630 Tid: 0 DS 10 ES 10 FS 30 GS 10 EAX: 00000000 EBX: 000000cb ECX: 00000000 EDX: cccccccc EBP: 800f6360 ESI: 800f6470 ESP: 800f62c4 EDI: 800f63e0 EFLAGS: 00210286 kESP 800f62c4 kernel stack base 800f4000 Frames: <ntoskrnl.exe:10bec (ntoskrnl/cm/ntfunc.c:1742 (NtSetValueKey))> <ntoskrnl.exe:967c2 ({standard input}:177 (KiSystemService))> <FFFD6085> <usbuhci.sys:2166 (drivers/usb/cromwell/uhci/pdo.c:140 (UhciPnpStartDevice))> <usbuhci.sys:21c8 (drivers/usb/cromwell/uhci/pdo.c:172 (UhciPnpPdo))> <usbuhci.sys:29ee (drivers/usb/cromwell/uhci/uhci.c:271 (DispatchPnp))> <ntoskrnl.exe:4223f (ntoskrnl/io/irp.c:1080 (IofCallDriver))> <usbhub.sys:2197 (drivers/usb/cromwell/hub/misc.c:42 (ForwardIrpAndWait))> <usbhub.sys:1862 (drivers/usb/cromwell/hub/fdo.c:223 (UsbhubPnpFdo))> <usbhub.sys:2cb5 (drivers/usb/cromwell/hub/usbhub.c:164 (DispatchPnp))> <ntoskrnl.exe:4223f (ntoskrnl/io/irp.c:1080 (IofCallDriver))> <ntoskrnl.exe:45033 (ntoskrnl/io/pnpmgr.c:752 (IopInitiatePnpIrp))> <ntoskrnl.exe:30cb4 (ntoskrnl/io/device.c:145 (IopStartDevice))> <ntoskrnl.exe:46652 (ntoskrnl/io/pnpmgr.c:1831 (IopActionInitChildServices))> <ntoskrnl.exe:466e5 (ntoskrnl/io/pnpmgr.c:1871 (IopActionInitAllServices))> <ntoskrnl.exe:450a8 (ntoskrnl/io/pnpmgr.c:782 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:450db (ntoskrnl/io/pnpmgr.c:796 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:4511e (ntoskrnl/io/pnpmgr.c:822 (IopTraverseDeviceTree))> <ntoskrnl.exe:4674e (ntoskrnl/io/pnpmgr.c:1931 (IopInitializePnpServices))> <ntoskrnl.exe:469f6 (ntoskrnl/io/pnpmgr.c:2073 (IopInvalidateDeviceRelations))> <ntoskrnl.exe:30ce6 (ntoskrnl/io/device.c:162 (IopStartDevice))> <ntoskrnl.exe:46652 (ntoskrnl/io/pnpmgr.c:1831 (IopActionInitChildServices))> <ntoskrnl.exe:466e5 (ntoskrnl/io/pnpmgr.c:1871 (IopActionInitAllServices))> <ntoskrnl.exe:450a8 (ntoskrnl/io/pnpmgr.c:782 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:450db (ntoskrnl/io/pnpmgr.c:796 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:450db (ntoskrnl/io/pnpmgr.c:796 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:4511e (ntoskrnl/io/pnpmgr.c:822 (IopTraverseDeviceTree))> <ntoskrnl.exe:4674e (ntoskrnl/io/pnpmgr.c:1931 (IopInitializePnpServices))> <ntoskrnl.exe:b9fd7 (ntoskrnl/io/iomgr.c:421 (IoInit3))> <ntoskrnl.exe:b782a (ntoskrnl/ex/init.c:651 (ExpInitializeExecutive))> <ntoskrnl.exe:66d6 (ntoskrnl/ke/main.c:100 (KiSystemStartup))> <ntoskrnl.exe:b584e (ntoskrnl/ke/main.c:294 (_main))> <0>

19 years, 10 months

1
0
0 0

rev. 17166 - hbirr / hartmut

by Brandon Turner

Hello, This commit has broken compiling ROS with ROS cmd.exe. While building it is rbuild is not deleting all the temp files it is creating(ROS only). When trying to delete them doing "del *.*aaa" it does not delete _all_ files it should however running the command again will pick up what it left before(reported by WD). Make install and make clean are both effected in some way as well. Here is the output: C:\Documents and Settings\Brandon\Desktop\ROS>mingw32-make install [CC] ntoskrnl\se\lsa.c [CC] ntoskrnl\se\luid.c [CC] ntoskrnl\se\priv.c [CC] ntoskrnl\se\sd.c [CC] ntoskrnl\se\semgr.c [CC] ntoskrnl\se\sid.c [CC] ntoskrnl\se\token.c [WRC] obj-i386\ntoskrnl\ntoskrnl.coff Bad command or filename mingw32-make: *** [obj-i386\ntoskrnl\ntoskrnl.coff] Error -1073741819 C:\Documents and Settings\Brandon\Desktop\ROS>mingw32-make clean [CC] tools\cdmake\cdmake.c [CC] tools\cdmake\llmosrt.c [LD] output-i386\tools\cdmake\cdmake.exe [CC] tools\mkhive\binhive.c [CC] tools\mkhive\infcache.c [CC] tools\mkhive\mkhive.c [CC] tools\mkhive\reginf.c [CC] tools\mkhive\registry.c [LD] output-i386\tools\mkhive\mkhive.exe mingw32-make: [rbuild_clean] Error -1073741819 (ignored) mingw32-make: [unicode_clean] Error -1073741819 (ignored) mingw32-make: [freeldr_base64k_clean] Error -1073741819 (ignored) mingw32-make: [freeldr_base_clean] Error -1073741819 (ignored) mingw32-make: [freeldr_main_clean] Error -1073741819 (ignored) mingw32-make: [hal_generic_clean] Error -1073741819 (ignored) mingw32-make: [glu32_clean] Error -1073741819 (ignored) mingw32-make: [kernel32_base_clean] Error -1073741819 (ignored) mingw32-make: [cmd_base_clean] Error -1073741819 (ignored) mingw32-make: [explorer_clean] Error -1073741819 (ignored) mingw32-make: [explorer_clean] Error -1073741819 (ignored) mingw32-make: [win32k_base_clean] Error -1073741819 (ignored)

19 years, 10 months

3
3
0 0

Re: [ros-diffs] [gdalsnes] 17267: more stuff

by Filip Navara

Gunnar Dalsnes wrote: > i know, the msg sux. ill create a summary commit msg when/if i merge > with trunk. > > G. I pretty much disagree with the USER_MESSAGE_QUEUE -> W32THREAD changes. It would be all nice and correct if there wasn't the AttachThreadInput function. On Windows there is also a message queue stucture (called simply "Q"), so why are you trying to make the stuff different and imho more complicated? - Filip

19 years, 10 months

1
0
0 0

Re: [ros-diffs] [gdalsnes] 17265: move WM_SYSTIMER where it belongs

by Filip Navara

gdalsnes(a)svn.reactos.com wrote: >move WM_SYSTIMER where it belongs > >Modified: trunk/reactos/include/win32k/ntuser.h >Modified: trunk/reactos/w32api/include/winuser.h > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/include/win32k/ntuser.h* > >--- trunk/reactos/include/win32k/ntuser.h 2005-08-10 18:42:27 UTC (rev 17264) >+++ trunk/reactos/include/win32k/ntuser.h 2005-08-10 19:19:13 UTC (rev 17265) >@@ -1,7 +1,6 @@ > > #ifndef __WIN32K_NTUSER_H > #define __WIN32K_NTUSER_H > > > >-#define WM_SYSTIMER 280 > > > > ULONG STDCALL > NtUserGetSystemMetrics(ULONG Index); > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/w32api/include/winuser.h* > >--- trunk/reactos/w32api/include/winuser.h 2005-08-10 18:42:27 UTC (rev 17264) >+++ trunk/reactos/w32api/include/winuser.h 2005-08-10 19:19:13 UTC (rev 17265) >@@ -1497,6 +1497,7 @@ > > #define WM_TCARD 82 > #define WM_TIMECHANGE 30 > #define WM_TIMER 275 > > >+#define WM_SYSTIMER 280 > > > #define WM_UNDO 772 > #define WM_USER 1024 > #define WM_USERCHANGED 84 > > It is not definition present in the PSDK headers, so this change is wrong! - Filip

19 years, 10 months

1
0
0 0

Re: [ros-diffs] [gdalsnes] 17264: add missing define

by Filip Navara

gdalsnes(a)svn.reactos.com wrote: >add missing define > >Modified: trunk/reactos/w32api/include/oleacc.h > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/w32api/include/oleacc.h* > >--- trunk/reactos/w32api/include/oleacc.h 2005-08-10 18:10:45 UTC (rev 17263) >+++ trunk/reactos/w32api/include/oleacc.h 2005-08-10 18:42:27 UTC (rev 17264) >@@ -108,6 +108,7 @@ > > #define STATE_SYSTEM_PRESSED 0x00000008 > #define STATE_SYSTEM_CHECKED 0x00000010 > #define STATE_SYSTEM_MIXED 0x00000020 > > >+#define STATE_SYSTEM_INDETERMINATE STATE_SYSTEM_MIXED > > > #define STATE_SYSTEM_READONLY 0x00000040 > #define STATE_SYSTEM_HOTTRACKED 0x00000080 > #define STATE_SYSTEM_DEFAULT 0x00000100 > > Can you please update winuser.h too?

19 years, 10 months

1
0
0 0

Re: [ros-svn] [royce] 17274: initialize StringBuffer to NULL, as some code paths lead to it being tested without ever being set.

by Royce Mitchell III

royce(a)svn.reactos.com wrote: >initialize StringBuffer to NULL, as some code paths lead to it being tested without ever being set. > > I forgot to give credit to WaxDragon for the find, I humbly beg your forgiveness...

19 years, 10 months

1
0
0 0

RE: [ros-svn] [gdalsnes] 17267: more stuff

by Casper Hornstrup

~3600 lines of what "stuff"? Casper > -----Original Message----- > From: ros-svn-bounces(a)reactos.com [mailto:ros-svn-bounces@reactos.com] On Behalf Of > gdalsnes(a)svn.reactos.com > Sent: 10. august 2005 21:53 > To: ros-svn(a)reactos.com > Subject: [ros-svn] [gdalsnes] 17267: more stuff > > more stuff > > > Added files: > branches/win32k rewrite attempt/win32k/include/win32.h > > Updated files: > branches/win32k rewrite attempt/win32k/eng/driverobj.c > branches/win32k rewrite attempt/win32k/include/desktop.h > branches/win32k rewrite attempt/win32k/include/input.h > branches/win32k rewrite attempt/win32k/include/msgqueue.h > branches/win32k rewrite attempt/win32k/include/ntuser.h > branches/win32k rewrite attempt/win32k/include/painting.h > branches/win32k rewrite attempt/win32k/include/prop.h > branches/win32k rewrite attempt/win32k/include/timer.h > branches/win32k rewrite attempt/win32k/include/userfuncs.h > branches/win32k rewrite attempt/win32k/include/vis.h > branches/win32k rewrite attempt/win32k/include/win32k.h > branches/win32k rewrite attempt/win32k/include/window.h > branches/win32k rewrite attempt/win32k/main/dllmain.c > branches/win32k rewrite attempt/win32k/misc/copy.c > branches/win32k rewrite attempt/win32k/ntuser/caret.c > branches/win32k rewrite attempt/win32k/ntuser/desktop.c > branches/win32k rewrite attempt/win32k/ntuser/focus.c > branches/win32k rewrite attempt/win32k/ntuser/hook.c > branches/win32k rewrite attempt/win32k/ntuser/hotkey.c > branches/win32k rewrite attempt/win32k/ntuser/input.c > branches/win32k rewrite attempt/win32k/ntuser/keyboard.c > branches/win32k rewrite attempt/win32k/ntuser/message.c > branches/win32k rewrite attempt/win32k/ntuser/misc.c > branches/win32k rewrite attempt/win32k/ntuser/msgqueue.c > branches/win32k rewrite attempt/win32k/ntuser/painting.c > branches/win32k rewrite attempt/win32k/ntuser/timer.c > branches/win32k rewrite attempt/win32k/ntuser/vis.c > branches/win32k rewrite attempt/win32k/ntuser/window.c > branches/win32k rewrite attempt/win32k/ntuser/winpos.c > branches/win32k rewrite attempt/win32k/w32k.h > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-svn

19 years, 10 months

2
1
0 0

failure

by Royce Mitchell III

Updated and built latest version. It installs ok, but when I try to boot, I get this ( I enabled some debug messages after the first failure ): (ntoskrnl\ke\main.c:289) --------------------------------------------------------------- (ntoskrnl\ke\main.c:290) ReactOS 0.3-SVN (Build 20050809-r17251) Used memory 65536Kb (ntoskrnl\mm\mminit.c:375) Kernel Stack Limits. InitTop = 0x800f7000, Init = 0x800f4000 (ntoskrnl\mm\mm.c:283) No current process (ntoskrnl\io\driver.c:442) IopLoadServiceModule(Pci, 0x800f6a80) (ntoskrnl\io\driver.c:518) Initializing boot module (ntoskrnl\io\driver.c:562) Module loading (Status 0) Peripheral Component Interconnect Bus Driver (ntoskrnl\io\driver.c:442) IopLoadServiceModule(PCNet, 0x800f6850) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\pcnet.sys (ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001) (ntoskrnl\io\driver.c:562) Module loading (Status c0000001) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service PCNet failed (Status c0000001) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(usbuhci, 0x800f6850) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\System32\DRIVERS\usbuhci.sys (ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001) (ntoskrnl\io\driver.c:562) Module loading (Status c0000001) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service usbuhci failed (Status c0000001) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(PCNet, 0x800f6a60) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\pcnet.sys (ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001) (ntoskrnl\io\driver.c:562) Module loading (Status c0000001) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service PCNet failed (Status c0000001) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(usbuhci, 0x800f6a60) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\System32\DRIVERS\usbuhci.sys (ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001) (ntoskrnl\io\driver.c:562) Module loading (Status c0000001) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service usbuhci failed (Status c0000001) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(Ne2000, 0x800f6a80) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\ne2000.sys (ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001) (ntoskrnl\io\driver.c:562) Module loading (Status c0000001) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service Ne2000 failed (Status c0000001) Advanced Configuration and Power Interface Bus Driver ACPI: System firmware supports: +------------------------------------------------------------ | Sx states: +S0 -S1 -S2 -S3 -S4 +S5 +------------------------------------------------------------ Power Button: found Sleep Button: found (ntoskrnl\io\driver.c:442) IopLoadServiceModule(serial, 0x800f6980) (ntoskrnl\io\driver.c:465) RtlQueryRegistryValues() failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(serial, 0x800f6980) (ntoskrnl\io\driver.c:465) RtlQueryRegistryValues() failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(serial, 0x800f6bc0) (ntoskrnl\io\driver.c:465) RtlQueryRegistryValues() failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(serial, 0x800f6bc0) (ntoskrnl\io\driver.c:465) RtlQueryRegistryValues() failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(PCNet, 0x800f6bc0) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\io\driver.c:562) Module loading (Status 0) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(usbuhci, 0x800f6bc0) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\System32\DRIVERS\usbuhci.sys (ntoskrnl\io\driver.c:559) Module loading failed (Status c0000034) (ntoskrnl\io\driver.c:562) Module loading (Status c0000034) (ntoskrnl\io\pnpmgr.c:1750) Initialization of service usbuhci failed (Status c0000034) (ntoskrnl\io\driver.c:442) IopLoadServiceModule(Ne2000, 0x800f6be0) (ntoskrnl\io\driver.c:541) Loading module (ntoskrnl\io\driver.c:562) Module loading (Status 0) (ne2000/8390.c:86)(NICCheck) Adapter NOT found! (ndis/miniport.c:1425)(NdisIPnPStartDevice) MiniportInitialize() failed for an adapter. (drivers\input\i8042prt\registry.c:215) Can't read registry: c0000034 (drivers\input\i8042prt\registry.c:226) Manually set defaults (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\sndblst.sys (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\mpu401.sys (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\xboxvmp.sys NtSetEaFile at ntoskrnl\io\file.c:2873 is unimplemented, have a nice day

19 years, 10 months

4
4
0 0

Re: [ros-svn] [greatlrd] 17218: fixing bug 690 by Brandon Turner. note ms only allown start "notepad" or "note"pad not notep"ad or notepad" but we do that, for we think it is a bug in ms cmd that only allowing " at start of a file name to start the apps.

by Hartmut Birr

greatlrd(a)svn.reactos.com wrote: >fixing bug 690 by Brandon Turner. note ms only allown start "notepad" or "note"pad not notep"ad or notepad" but we do that, for we think it is a bug in ms cmd that only allowing " at start of a file name to start the apps. > > >Updated files: >trunk/reactos/subsys/system/cmd/cmd.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > > > This change is broken, because the input strings may be longer than MAX_PATH. This is always true for compilung ros on ros. - Hartmut

19 years, 10 months

2
1
0 0

Re: [ros-svn] [navaraf] 17154: Fix mutex unlocking in NpfsWaiterThread and add ASSERT.

by Hartmut Birr

navaraf(a)svn.reactos.com wrote: >Fix mutex unlocking in NpfsWaiterThread and add ASSERT. > > >Updated files: >trunk/reactos/drivers/fs/np/rw.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > > > Something is wrong with this change or r17157. Compiling ros on ros reports hundreds of errors if pipes are enabled. Reverting npfs to r17153 does fix this problem. - Hartmut

19 years, 10 months

4
13
0 0

Re: [ros-diffs] [hbirr] 17248: If the file object is for a device, we must gather some information

by Filip Navara

hbirr(a)svn.reactos.com wrote: >- DPRINT("%wZ\n", ObjectAttributes->ObjectName); > > > > > >+ DPRINT1("%wZ\n", ObjectAttributes->ObjectName); >+ > > Do we really need to be verbose? ;-) - Filip

19 years, 10 months

2
1
0 0

Re: [ros-diffs] [ion] 17235: - Last patch was incomplete, apologies. SVN @ 5AM = bad idea.

by Hartmut Birr

ion(a)svn.reactos.com wrote: >- Last patch was incomplete, apologies. SVN @ 5AM = bad idea. >- Do not report that ROS is running on 0 active processors, that's a bad idea. >- Actually check the affinity mask set by NtSetInformationThread >- Fix the check in KeSetAffinityThread >- Give a valid affinity to the system thread (corresponding to the active cpu affinity set). > >This removes all bugchecks from the kernel32 thread winetest. > >Modified: trunk/reactos/ntoskrnl/include/internal/ke.h >Modified: trunk/reactos/ntoskrnl/ke/kthread.c >Modified: trunk/reactos/ntoskrnl/ke/main.c >Modified: trunk/reactos/ntoskrnl/ps/psmgr.c >Modified: trunk/reactos/ntoskrnl/ps/query.c > > > ------------------------------------------------------------------------ > > *Modified: trunk/reactos/ntoskrnl/ps/psmgr.c* > >--- trunk/reactos/ntoskrnl/ps/psmgr.c 2005-08-09 08:02:05 UTC (rev 17234) >+++ trunk/reactos/ntoskrnl/ps/psmgr.c 2005-08-09 08:50:57 UTC (rev 17235) >@@ -213,7 +213,7 @@ > > > /* System threads may run on any processor. */ > RtlZeroMemory(PsInitialSystemProcess, sizeof(EPROCESS)); > > >- PsInitialSystemProcess->Pcb.Affinity = 0xFFFFFFFF; > > >+ PsInitialSystemProcess->Pcb.Affinity = KeActiveProcessors; > > > PsInitialSystemProcess->Pcb.IopmOffset = 0xffff; > PsInitialSystemProcess->Pcb.BasePriority = PROCESS_PRIO_NORMAL; > PsInitialSystemProcess->Pcb.QuantumReset = 6; > > > ------------------------------------------------------------------------ * *This is change is possible incorrect. PsInitProcessManagment is called after the boot processor is started and before the application processors are started (on a smp machine). All system threads will only run on the boot processor. - Hartmut

19 years, 10 months

2
1
0 0

Re: [ros-dev] dma problem

by Filip Navara

19 years, 10 months

1
0
0 0

Re: [ros-diffs] [mbosma] 17213: Fix another bug thanks to GreatLord.

by Royce Mitchell III

mbosma(a)svn.reactos.com wrote: >Fix another bug thanks to GreatLord. > >Modified: trunk/reactos/lib/ddraw/main/ddraw.c > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/ddraw/main/ddraw.c* > >--- trunk/reactos/lib/ddraw/main/ddraw.c 2005-08-08 16:09:48 UTC (rev 17212) >+++ trunk/reactos/lib/ddraw/main/ddraw.c 2005-08-08 16:18:44 UTC (rev 17213) >@@ -24,7 +24,7 @@ > > This->lpGUID = lpGUID; > > // get the HDC > > >- This->hdc = CreateDC (L"Display", NULL, NULL, NULL); > > >+ This->hdc = GetWindowDC(GetDesktopWindow()); > > > This->Height = GetDeviceCaps(This->hdc, HORZRES); > This->Width = GetDeviceCaps(This->hdc, VERTRES); > This->Bpp = GetDeviceCaps(This->hdc, BITSPIXEL); > > I wondered about this when I first saw it. What about GetDC(NULL) ?

19 years, 10 months

2
2
0 0

Message recieved four times?

by Rick Langschultz

Are any of you receiving messages four times. I am using Microsoft Outlook 2003, and there seems to be four posts to every message.

19 years, 10 months

4
4
0 0

Bugzilla comments wrongly attributed

by Ge van Geldorp

Some of the comments in bugzilla are now attributed to "Bug Zilla" instead of the real submitter. I messed up trying to clean up an inconsistency in the database. These are the days I hate I can't just "rollback"... My apologies to those who's name got lost. Gé van Geldorp.

19 years, 10 months

1
0
0 0

ReacOS 0.2.7-RC [2] bug found

by Wesley Parish

An oops, a brain-fart. I meant 0.2.7 RC 2. Apologies. "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: 1bea> <ntoskrnl.exe: 1c01> <ntoskrnl.exe: 31cd3> <ntoskrnl.exe: 2eddd> <ntoskrnl.exe: 32b43> <ntoskrnl.exe: 831e> <ntoskrnl.exe: 87d5> <ntoskrnl.exe: 8bef> <ntoskrnl.exe: 4686a> <ntoskrnl.exe: 4ef95> " What I was doing? I left it sitting in qemu with the ReactOS start menu open at the Search entry while I checked my email. When I returned, I found this on the screen. Prior to that it had been working well, opening the submenus of the start menu without any problem. Wesley Parish -- 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.

19 years, 10 months

2
2
0 0

Ext2 installable FS for Windows - might be of interest

by Radovan Skolnik

I know there's Filip working on Ext2 support but to day I received a link to working read/write Ext2 IFS for Windows. See here: http://www.fs-driver.org/index.html Best regards Radovan Skolnik ------------------------------------------------------------------ Ing. Radovan Skolnik TEMPEST s.r.o. Department of Enterprise Management Plynarenska 7/B 821 09 Bratislava Slovak Republic E-mail: radovan_skolnik(a)tempest.sk www: http://www.tempest.sk Tel: +421 (2) 502 67 174 Fax: +421 (2) 502 67 100 ITIL, SLM, Networking, Telecomm, Management, CORBA, Java and XML ------------------------------------------------------------------

19 years, 10 months

2
1
0 0

Re: [ros-diffs] [ion] 17221: Fix exception handling by not reseting PreviousMode to kernel when a user-mode exception occurs. This fixes some winetest bugchecks

by Filip Navara

19 years, 10 months

1
0
0 0

ReacOS 0.2.7-RC 1 bug found

by Wesley Parish

"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: 1bea> <ntoskrnl.exe: 1c01> <ntoskrnl.exe: 31cd3> <ntoskrnl.exe: 2eddd> <ntoskrnl.exe: 32b43> <ntoskrnl.exe: 831e> <ntoskrnl.exe: 87d5> <ntoskrnl.exe: 8bef> <ntoskrnl.exe: 4686a> <ntoskrnl.exe: 4ef95> " What I was doing? I left it sitting in qemu with the ReactOS start menu open at the Search entry while I checked my email. When I returned, I found this on the screen. Prior to that it had been working well, opening the submenus of the start menu without any problem. Wesley Parish -- 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.

19 years, 10 months

1
0
0 0

Re: [ros-diffs] [greatlrd] 17219: Add a check to see if surface can be create, it return it can be create, but still createsurface return invaild param

by Royce Mitchell III

greatlrd(a)svn.reactos.com wrote: >Add a check to see if surface can be create, it return it can be create, but still createsurface return invaild param > >Modified: trunk/reactos/lib/ddraw/main/surface.c > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/ddraw/main/surface.c* > >--- trunk/reactos/lib/ddraw/main/surface.c 2005-08-08 18:59:56 UTC (rev 17218) >+++ trunk/reactos/lib/ddraw/main/surface.c 2005-08-08 21:29:25 UTC (rev 17219) >@@ -63,12 +63,26 @@ > > CreateData.dwSCnt = 1; > CreateData.lplpSList = &pLocal; > > > >- if(This->owner->DriverCallbacks.DdMain.CreateSurface (&CreateData) != DDHAL_DRIVER_HANDLED) >- return DDERR_INVALIDPARAMS; > > >+ DDHAL_CANCREATESURFACEDATA CanCreateData; >+ memset(&CanCreateData, 0, sizeof(DD_CANCREATESURFACEDATA)); >+ CanCreateData.lpDD = &This->owner->DirectDrawGlobal; >+ CanCreateData.lpDDSurfaceDesc = (DDSURFACEDESC*)pDDSD; > > > > > >+ >+ if (This->owner->DriverCallbacks.DdMain.CanCreateSurface (&CanCreateData) == DDHAL_DRIVER_NOTHANDLED) >+ return DDERR_INVALIDPARAMS; >+ > > > if(CreateData.ddRVal != DD_OK) > > shouldn't this be "if(CanCreateData.ddRVal != DD_OK)" ??? >+ return CanCreateData.ddRVal; >+ >+ >+ if(This->owner->DriverCallbacks.DdMain.CreateSurface (&CreateData) == DDHAL_DRIVER_NOTHANDLED) >+ return DDERR_INVALIDPARAMS; >+ >+ if(CreateData.ddRVal != DD_OK) > > > return CreateData.ddRVal; > > > >+ > > > OutputDebugString(L"This does not get hit."); > > return DD_OK; > >

19 years, 10 months

2
1
0 0

reactos 0.2.7-RC2 is out

by Robert Köpferl

As of Revision 17175 Reactos 0.2.7 RC-2 has been built and is donwloadable at sf.net Since RC1 a couple of blocking bugs have been solved. We welcome you to test this pre-release on your hardware. And report problems. Most interesting to us is the behavour of your keyboard. Lately there occoured some problems in detecting always a keyboard on any hardware or to correctly detect release codes of different keys. Please report problems in this area with details to your hardware.

19 years, 10 months

4
5
0 0

bugcheck: kernel32_winetest sync 17198

by Steven Edwards

kernel32_winetest sync *** STOP: 0x0000001E (0xc0000047,0x80007cfb,0x000f0350,0x9e956c60) *** ntoskrnl.exe - Address 0x8002ae09 base at 0x80000000, DateStamp 0x0 Exception: -1634374428(0) Processor: 0 CS:EIP 8:8002ae09 <ntoskrnl.exe:2ae09 ({standard input}:1521 (ZwRaiseException))> cr2 30 cr3 5879000 Proc: 80fa8968 Pid: 124 <kernel32_winete> Thrd: 80fc9f90 Tid: 128 DS 10 ES 10 FS 30 GS 0 EAX: 00000096 EBX: 0000009e ECX: 00000000 EDX: 9e956d74 EBP: 9e956c10 ESI: 006afe2c ESP: 9e9568a0 EDI: 9e956d74 EFLAGS: 00000286 kESP 9e9568a0 kernel stack base 9e954000 Frames: <ntoskrnl.exe:1bb4a (ntoskrnl/ex/error.c:64 (ExRaiseStatus))> <ntoskrnl.exe:7cfb (ntoskrnl/ke/sem.c:104 (KeReleaseSemaphore))> <ntoskrnl.exe:24aba (ntoskrnl/ex/sem.c:326 (NtReleaseSemaphore))> <ntoskrnl.exe:96312 ({standard input}:177 (KiSystemService))> <kernel32.dll:33788 (lib/kernel32/synch/sem.c:205 (ReleaseSemaphore))> KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0x80000003,0x800a07f7,0x00000000,0x9e9560e4) *** ntoskrnl.exe - Address 0x800a07f7 base at 0x80000000, DateStamp 0x0 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

19 years, 10 months

2
1
0 0

bugcheck: kernel32_winetest thread

by Steven Edwards

*** STOP: 0x0000001E (0xc0000005,0x80072474,0x00000000,0x00000000) *** ntoskrnl.exe - Address 0x80072474 base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(2) Processor: 0 CS:EIP 8:80072474 <ntoskrnl.exe:72474 (ntoskrnl/ob/handle.c:647 (ObpCreateHandle))> cr2 0 cr3 58c8000 Proc: 80fc9bd8 Pid: 124 <kernel32_winete> Thrd: 80fa6570 Tid: 128 DS 10 ES 10 FS 30 GS 0 EAX: 000000d4 EBX: 00000064 ECX: 80fcd00c EDX: 00000000 EBP: 9e95ec5c ESI: 006afdf0 ESP: 9e95ebb0 EDI: 9e95ed74 EFLAGS: 00000202 kESP 9e95ebb0 kernel stack base 9e95c000 Frames: <ntoskrnl.exe:7538c (ntoskrnl/ob/object.c:933 (ObOpenObjectByPointer))> <ntoskrnl.exe:82e62 (ntoskrnl/ps/thread.c:744 (NtOpenThread))> <ntoskrnl.exe:96312 ({standard input}:177 (KiSystemService))> <kernel32.dll:34fb2 (lib/kernel32/thread/thread.c:279 (OpenThread))> KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0x80000003,0x800a07f7,0x00000000,0x9e95e364) *** ntoskrnl.exe - Address 0x800a07f7 base at 0x80000000, DateStamp 0x0 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

19 years, 10 months

1
0
0 0

RE: [ros-svn] [ion] 17182: - Remove cid.c

by PETREOLLE Sylvain

Hi Alex, what do you call "remove" cid.c ? -----Message d'origine----- De : ion(a)svn.reactos.com [mailto:ion@svn.reactos.com] Envoyé : lundi 8 août 2005 00:48 À : ros-svn(a)reactos.com Objet : [ros-svn] [ion] 17182: - Remove cid.c - Remove cid.c Updated files: trunk/reactos/ntoskrnl/include/internal/ps.h trunk/reactos/ntoskrnl/ntoskrnl.xml trunk/reactos/ntoskrnl/ps/cid.c Best regards, Usurp ---------------------------------------------------------------------------- Ce message ainsi que toutes pièces jointes (le "message") sont confidentiels et sont exclusivement destinés à l'usage de la personne à laquelle ils sont adressés. Tout point de vue ou toute opinion contenus dans ce message expriment la pensée personnelle de leur auteur et ne représentent pas nécessairement la position des sociétés du Groupe GEFCO. Si vous n'êtes pas la personne à laquelle ce message est destiné, veuillez noter que vous avez reçu cet e-mail par erreur et qu'il vous est strictement interdit d'utiliser, de diffuser, de transférer, d'imprimer ou de copier ce message. Si vous avez reçu ce message par erreur, merci de contacter la personne qui vous l'a adressé et de l'effacer immédiatement. Les sociétés du Groupe GEFCO déclinent toute responsabilité en cas d'altération, de modification, d'édition, de diffusion sans autorisation de ce message ou en cas d'affection de ce message par un virus. This message and any attachments (the "message") are confidential and intended solely for the use of the individual to whom they are addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the GEFCO Group of Companies. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this message is strictly prohibited. If you have received this message in error please contact the sender and delete the message immediately. The GEFCO Group of Companies shall not be liable for the message if altered, changed, falsified, edited, diffused without authorization or affected by any virus. ----------------------------------------------------------------------------

19 years, 10 months

1
0
0 0

Re: [ros-dev] Hiveinst.inf file

by Filip Navara

19 years, 10 months

1
0
0 0

Current trunk breakage

by Alex Ionescu

Hi Thomas, I've found why trunk freezes. It seems that win32k creates the stock objects while loading, which in turns calls a GDIOBJ conversion routine, which in turn calls PsLookupProcessByThreadId which in turn calls ExMapHandletoPointer which in turns calls ExLockHandleTableEntry. This one seems to loop forever, but I'm way too tired and don't your handle code so well in order to determine what's wrong.. Best regards, Alex Ionescu

19 years, 10 months

3
3
0 0

Hiveinst.inf file

by Gge

Hello, This Hiveinst.inf file is used to overwrite registry informations located in Hivesys.inf file . Is it really needed as updating hivesys.inf is sufficient ? Regards Gerard

19 years, 10 months

1
0
0 0

Re: [ros-svn] [ion] 17189: Retry waiting if STATUS_ALERTED is returned

by Alex Ionescu

ion(a)svn.reactos.com wrote: >Retry waiting if STATUS_ALERTED is returned > > > Hi, I suspect many will read MSDN and tell me that this patch is wrong since MSDN says "If Alertable is TRUE, the wait will return early". Before you do so, please note that MSDN is WRONG and/or refers to the NtWaitForXXX functionality. Win32 will actually loop and never early-return for an Alertable WaitForXXX call. Best regards, Alex Ionescu

19 years, 10 months

1
1
0 0

Re: [ros-svn] [weiden] 17152: fixed uninitialized variable warning

by Hartmut Birr

weiden(a)svn.reactos.com wrote: >fixed uninitialized variable warning > > >Updated files: >trunk/reactos/subsys/csrss/win32csr/conio.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > > > This changes is wrong. Sting is changed inside the routine. It isn't possible to use String for deallocating. - Hartmut

19 years, 10 months

2
1
0 0

Re: [ros-diffs] [ion] 17182: - Remove cid.c

by Filip Navara

19 years, 10 months

1
0
0 0

some ROS 0.27RC1 LiveCD feedback

by Bernd Blaauw

Hi ReactOS project, I've tried your 0.27RC1 LiveCD in VMware Workstation 4.5.2 for Windows, and it's great to have a win32 compatible LiveCD. things I noticed. *CTRL-ALT-DEL (eh..INS for VMware) doesn't bring up Taskmgr, but rightclicking on start menu, then selecting taskmgr, does, as well as running START/RUN/TASKMGR.EXE does. *In VMware, the third tab (with graphs) looks strange *bootCD doesn't start LiveCD automatically when no bootable harddisk is present. It still prompts for 'press a key to start CD'. MS Win2000/XP cdrom behave different depending on if an active bootable primary partition is present (press a key to boot cdrom), or not (automatically boot into cdrom) *LiveCD gets assigned drive C:. I hope you're able to change this into 'start with D: or higher' Reason: partition from a ROS LiveCD, at least a primary partition with driveletter C: should be able to be created. *Rightclick on Start, then Settings. The window show up too low (tab page Desktop shows top 8 items, not all 11). Also the checkbox doesn't have any noticeable effect, I expected some version number to be displayed on the desktop, like in beta Windows builds. *Shutdown EXPLORER causes reboot (why not just fallback into TASKMGR which can start programs, or in CMD.EXE ?) *Logoff causes reboot *Shutdown option is followed by a dialogue, in which answering YES doesn't shut duwn the computer *Where is the cdrom bootsector as a file? Copying all files from cdrom to a directory on harddisk followed by running MKISOFS should be possible, but to create a bootable cdrom you'd also need the bootsector as a 2KB file. I'd really dislike needing some 'extract bootsector from (Live)CD' program, or needing to download additional files just to compile/extract a bootsector. Can the target file which the bootsector should load be configured at boottime? Enough space for '\12345678.ABC\12345678.ABC' ? The Windows bootsector usually is limited (in binary form ofcourse) to 'i386\somefile.ext' (4 characters for directory). Would be cool if a modified ROS cdrom bootsector could boot Win2000/XP setup as the cdrom bootsector for these operating systems might be copyrighted officially (and no public license for distribution of it). Despite these comments, I'm VERY impressed by the current progress since 0.24/0.25 ! 0.35 or so might have a moderately usable system working (OpenOffice, FireFox, Thunderbird, Winrar/7Zip, WinAMP perhaps) Bernd PS: normal ROS cd: ICON.ICO still in root of cdrom, which is not necessary and pollutes your DVD if you add ROS to a multi-OS compilation ( WinPE + Win2000 setup + FreeDOS + ReactOS setup + Knoppix + ... ) Bernd

19 years, 10 months

2
1
0 0

bugcheck: kernel32_winetest thread

by Steven Edwards

Hi, Nice work on nailing down the bugchecks. I think this is one of the last ones. KeBugCheck at ntoskrnl/ps/thread.c:678 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. Technical information: *** STOP: 0x00000000 (0x00000000,0x00000000,0x00000000,0x00000000) Frames: <ntoskrnl.exe:2516 (ntoskrnl/ke/bug.c:498 (KeBugCheckEx))> <ntoskrnl.exe:254e (ntoskrnl/ke/bug.c:519 (KeBugCheck))> <ntoskrnl.exe:82df6 (ntoskrnl/ps/thread.c:678 (NtOpenThread))> <ntoskrnl.exe:96362 ({standard input}:177 (KiSystemService))> <kernel32.dll:34f82 (lib/kernel32/thread/thread.c:279 (OpenThread))> KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0x80000003,0x800a0847,0x80fa44c0,0x1f000000) *** ntoskrnl.exe - Address 0x800a0847 base at 0x80000000, DateStamp 0x0 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

19 years, 10 months

1
0
0 0

Publish - new sub project

by Robert Köpferl

Hi, since it is not the only time I do a 'publish-build', I have already some kind of publish program/script. I intend to create a new sub project i.e. 'ros-publish' to more or less automate the process of building reactos, installing ros plus upping it to a ftp. Currently, this is a horrible mixture of bash script and win32-programs plus batch files. However I intend to rewrite it in a general purpose script language like ruby, perl or python. Comments welcome

19 years, 10 months

2
1
0 0

Re: [ros-dev] Website Design Voting

by Vegard Edvardsen

If I'm allowed to vote, my vote is for 4) Mindflyer.

19 years, 10 months

1
0
0 0

Re: [ros-svn] [ion] 17150: Fix NtSignalAndwaitForSingleObject: Use SEH when appropriate, use direct Mutant release call, query handle info and write fixmes when permission checking needed, optimize failure cases, fix horrid tab/space formatting mismatches

by Royce Mitchell III

ion(a)svn.reactos.com wrote: >Fix NtSignalAndwaitForSingleObject: Use SEH when appropriate, use direct Mutant release call, query handle info and write fixmes when permission checking needed, optimize failure cases, fix horrid tab/space formatting mismatches > > >Updated files: >trunk/reactos/include/ndk/extypes.h >trunk/reactos/ntoskrnl/ob/wait.c > > > Alex, May I please request that we not mix reformatting with real changes. It makes it hard to see what was really changed. Thanks, Royce3

19 years, 10 months

1
0
0 0

Re: [ros-svn] [hpoussin] 17162: Implement SetupGetInfFileListW and SetupGetInfInformationW

by Thomas Weidenmueller

hpoussin(a)svn.reactos.com wrote: > Implement SetupGetInfFileListW and SetupGetInfInformationW > Inf file parser now accept UNICODE files with FF FE header > Return required buffer size when buffer is too small in SetupGetLineTextA/W, SetupGetStringFieldA/W I think you forgot to commit changes to a header file: lib\setupapi\parser.c: In function 'SetupGetInfInformationW': lib\setupapi\parser.c:1874: error: 'INFINFO_INF_SPEC_IS_HINF' undeclared (first use in this function) lib\setupapi\parser.c:1874: error: (Each undeclared identifier is reported only once lib\setupapi\parser.c:1874: error: for each function it appears in.) lib\setupapi\parser.c:1875: error: 'INFINFO_INF_NAME_IS_ABSOLUTE' undeclared (fi rst use in this function) lib\setupapi\parser.c:1876: error: 'INFINFO_DEFAULT_SEARCH' undeclared (first us e in this function) lib\setupapi\parser.c:1877: error: 'INFINFO_REVERSE_DEFAULT_SEARCH' undeclared ( first use in this function) lib\setupapi\parser.c:1877: error: 'INFINFO_INF_PATH_LIST_SEARCH' undeclared (fi rst use in this function) lib\setupapi\parser.c: In function 'SetupGetInfFileListW': lib\setupapi\parser.c:2019: error: 'INFINFO_INF_SPEC_IS_HINF' undeclared (first use in this function)

19 years, 10 months

2
1
0 0

Re: [ros-svn] [ion] 17139: Add failure cases for more things then a WINE test could shake a stick at (hopefully)

by Steven Edwards

Hi Alex, --- ion(a)svn.reactos.com wrote: > Add failure cases for more things then a WINE test could shake a stick at (hopefully) Great! The virtual test no longer causes a bugcheck. Want to try this one? =) kernel32_test sync sync.c:93: Test failed: should succeed KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0xc0000047,0x80007cfb,0x000ef350,0x9e89bc5c) *** ntoskrnl.exe - Address 0x8002ad39 base at 0x80000000, DateStamp 0x0 Exception: -2131009312(0) Processor: 0 CS:EIP 8:8002ad39 <ntoskrnl.exe:2ad39 ({standard input}:1521 (ZwRaiseException))> cr2 8069be40 cr3 5522000 Proc: 80fa3cb0 Pid: 128 <kernel32_test.e> Thrd: 80f98718 Tid: 12c DS 10 ES 10 FS 30 GS 0 EAX: 00000096 EBX: 000000ce ECX: 00000000 EDX: 9e89bd74 EBP: 9e89bc0c ESI: 006afdf0 ESP: 9e89b89c EDI: 9e89bd74 EFLAGS: 00000292 kESP 9e89b89c kernel stack base 9e899000 Frames: <ntoskrnl.exe:1bc3a (ntoskrnl/ex/error.c:64 (ExRaiseStatus))> <ntoskrnl.exe:7cfb (ntoskrnl/ke/sem.c:104 (KeReleaseSemaphore))> <ntoskrnl.exe:77df0 (ntoskrnl/ob/wait.c:276 (NtSignalAndWaitForSingleObject))> <ntoskrnl.exe:95ca2 ({standard input}:177 (KiSystemService))> <kernel32.dll:341c4 (lib/kernel32/synch/wait.c:283 (SignalObjectAndWait))> KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0x80000003,0x800a0187,0x00000000,0x9e89b0e0) *** ntoskrnl.exe - Address 0x800a0187 base at 0x80000000, DateStamp 0x0 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

19 years, 10 months

2
1
0 0

VirtualAlloc Bugcheck

by Steven Edwards

With the trunk. kernel32_test.exe virtual virtual.c:36: Test failed: VirtualAlloc should fail on zero-sized allocation virtual.c:37: Test failed: got -559038737, expected ERROR_INVALID_PARAMETER Assertion 'marea->StartingAddress != Node->StartingAddress' failed at ntoskrnl/mm/marea.c line 437 KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0x80000003,0x8009fe71,0x80fc6364,0x9e89bb70) *** ntoskrnl.exe - Address 0x8009fe71 base at 0x80000000, DateStamp 0x0 Breakpoint Exception: 3(0) Processor: 0 CS:EIP 8:8009fe71 <ntoskrnl.exe:9fe71 ({standard input}:23 ())> cr2 6ad9a8 cr3 589f000 Proc: 80fc48d8 Pid: 12c <kernel32_test.e> Thrd: 80f984d8 Tid: 124 DS 10 ES 10 FS 30 GS 0 EAX: 00000063 EBX: 0000000b ECX: 00000000 EDX: 000003f8 EBP: 9e89bc54 ESI: 006afdf8 ESP: 9e89bbc4 EDI: 9e89bd74 EFLAGS: 00000296 kESP 9e89bbc4 kernel stack base 9e899000 Frames: <ntoskrnl.exe:5a309 (ntoskrnl/mm/marea.c:437 (MmInsertMemoryArea))> <ntoskrnl.exe:5ad47 (ntoskrnl/mm/marea.c:1015 (MmCreateMemoryArea))> <ntoskrnl.exe:53f65 (ntoskrnl/mm/anonmem.c:640 (NtAllocateVirtualMemory))> <ntoskrnl.exe:95992 ({standard input}:177 (KiSystemService))> <kernel32.dll:100e5 (lib/kernel32/mem/virtual.c:31 (VirtualAllocEx))> KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0x80000003,0x8009fe77,0x00000000,0x9e89b388) *** ntoskrnl.exe - Address 0x8009fe77 base at 0x80000000, DateStamp 0x0 ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

19 years, 10 months

2
1
0 0

Re: [ros-dev] mouse and keyboaed

by Filip Navara

19 years, 10 months

4
4
0 0

mouse and keyboaed

by Hartmut Birr

Hi, something is wrong with the keyboard and mouse. I get the following message on real hardware and keyboard and mouse are not usable: (drivers\input\i8042prt\registry.c:215) Can't read registry: c0000034 (drivers\input\i8042prt\registry.c:226) Manually set defaults (drivers\input\i8042prt\i8042prt.c:538) Got fe instead of 55 (drivers\input\i8042prt\i8042prt.c:565) Basic keyboard detection failed: c0000185 - Hartmut

19 years, 10 months

2
1
0 0

wiki

by Hartmut Birr

Hi, I've described the procedure to install ReactOS on a scsi disk. It would be nice, if someone can correct the spelling mistakes of my poor english. http://www.reactos.com/wiki/index.php/Disk_and_SCSI_miniport_drivers - Hartmut

19 years, 10 months

4
3
0 0

RE: [ros-svn] [navaraf] 17064: Fix shell32 build.

by Ge van Geldorp

> From: navaraf(a)svn.reactos.com > > Fix shell32 build. Sorry, forgot to commit the changes to include files.

19 years, 10 months

1
0
0 0

install problem

by Hartmut Birr

Hi, since some time, I'm not able to change the screen resolution after a fresh installation. It isn't possible to move the display dialog in a position, where it is possible to hit the 'OK' button. This has worked in the past. - Hartmut

19 years, 10 months

2
1
0 0

RE: [ros-dev] RE: [ros-bugs] [Bug 695] New: Tracert - Wrong outpo ut

by Murphy, Ged (Bolton)

> -----Original Message----- > From: Murphy, Ged (Bolton) [mailto:MurphyG@cmpbatteries.co.uk] > Sent: 05 August 2005 08:18 > To: 'ros-dev(a)reactos.com' > Subject: [ros-dev] RE: [ros-bugs] [Bug 695] New: Tracert - > Wrong outpout > > This is because GetNameInfo is not implememted in ROS. I > originally used > GetHostByAddr, but if the IP does not have a hostname, it > takes a long time > for the function to return, blocking the flow of the program. > This is the > reason tracert hasn't been added to the bootcd yet. > > Alex's ws2_32 rewrite should solve this. I'm hoping he's used > GetNameInfo, > as GetHostByAddr is depricieted anyway now in favour of this. > > I also need to do testing with tracert in ROS, as it is > currently untested > and will more that likely contain a few bugs. (such > confidence I have in my > code :) ) > > I'm also wondering why node 11 and 12 are the same in the > above windows > output. I haven't seen that happen before. Again, I'll look into it. > > Ged. Sorry, I also forgot to mention that TTL support is not yet acessable via the SetSockOpt routine. TTL will therefore default to 128 IIRC, which will break out of the loop imidietly as it would if it had hit the default maximum of 30 hops in tracert. All this info is available in the usage screen which can be viewed by entering 'tracert' with no args. Ged. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

19 years, 10 months

1
0
0 0

RE: [ros-bugs] [Bug 695] New: Tracert - Wrong outpout

by Murphy, Ged (Bolton)

> -----Original Message----- > From: ReactOS.Bugzilla(a)reactos.com > [mailto:ReactOS.Bugzilla@reactos.com] > Sent: 05 August 2005 06:52 > To: ros-bugs(a)reactos.com > Subject: [ros-bugs] [Bug 695] New: Tracert - Wrong outpout > > > http://reactos.com/bugzilla/show_bug.cgi?id=695 > > Summary: Tracert - Wrong outpout > Product: ReactOS > Version: 0.3.0-SVN > Platform: x86 Hardware > OS/Version: ReactOS > Status: NEW > Severity: normal > Priority: P3 > Component: Networking > AssignedTo: ros-bugs(a)reactos.com > ReportedBy: gerard.gatineau(a)laposte.net > > > Test done with svn 17040 > > The "tracert command" does not display correct result as below > > Ros Tracert in Ros > ------------------ > > Tracing route to www.laposte.net [81.255.54.10] > over a maximum of 30 hops: > > 1 164 ms 80 ms 81 ms > aaaAAaaaaaaAaaaa-LIBGCCW32-EH-2-SJLJ-GTHR-MINGW32 [81.255.54.10] > > Trace complete. > > The tracert command ( from Ros ) ran in windows displays correctly . > It means that the tracert program in Reactos is correct but > the Ros networking > support is the problem > > Ros Tracert in Windows > ---------------------- > > Tracing route to www.laposte.net [81.255.54.10] > > over a maximum of 30 hops: > > 1 1 ms <1 ms <1 ms 192.168.0.254 > 2 83 ms 84 ms 84 ms 192.168.254.254 > 3 61 ms 59 ms 59 ms > vlq-6k-2-a11.routers.proxad.net [212.27.37.190] > 4 62 ms 61 ms 62 ms > p19-6k-2-v800.intf.routers.proxad.net [212.27.50.6] > 5 62 ms 62 ms 62 ms > aub-6k-1-v806.routers.proxad.net [212.27.50.162] > 6 60 ms 62 ms 61 ms > GE0-3-0-0.noaub101.Aubervilliers.francetelecom.net [193.252.161.97] > 7 60 ms 59 ms 62 ms > pos5-0.ntaub301.Aubervilliers.francetelecom.net > [193.252.103.86] > 8 69 ms 69 ms 70 ms pos9-0.nrlyo201.Lyon.francetelecom.net > [193.252.103.77] > 9 73 ms 72 ms 75 ms pos6-0.ncnic201.Nice.francetelecom.net > [193.252.101.157] > 10 74 ms 73 ms 74 ms 81.255.54.252 > 11 76 ms 75 ms 74 ms www.laposte.net [81.255.54.10] > 12 74 ms 76 ms 77 ms www.laposte.net [81.255.54.10] > > Trace complete. > This is because GetNameInfo is not implememted in ROS. I originally used GetHostByAddr, but if the IP does not have a hostname, it takes a long time for the function to return, blocking the flow of the program. This is the reason tracert hasn't been added to the bootcd yet. Alex's ws2_32 rewrite should solve this. I'm hoping he's used GetNameInfo, as GetHostByAddr is depricieted anyway now in favour of this. I also need to do testing with tracert in ROS, as it is currently untested and will more that likely contain a few bugs. (such confidence I have in my code :) ) I'm also wondering why node 11 and 12 are the same in the above windows output. I haven't seen that happen before. Again, I'll look into it. Ged. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

19 years, 10 months

1
0
0 0

Website Design Voting

by Murphy, Ged (Bolton)

Would it not be easier to wait until the website is back up and use the poll feature. This could get confusing. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

19 years, 10 months

1
0
0 0

Re: [ros-svn] [weiden] 17031: implemented OffsetClipRgn()

by James Tabor

Hi! weiden(a)svn.reactos.com wrote: > implemented OffsetClipRgn() > > > Updated files: > trunk/reactos/subsys/win32k/objects/cliprgn.c > Yeah!!! 8^D Thanks, James

19 years, 10 months

1
0
0 0

Installed X-Chat 2.4.4 and Gdi32_crosstest

by James Tabor

Hi! I can install Xchat 2.4.4 from http://www.silverex.org/news/. It look horrible but it does run with some exceptions. One, you may have to start the app from it's lib directory, "..\xchat". I do not have a screen- shot 8^P. But here is a debug print, this does not happen often, only when exiting the app from the X button. It looks like something I posted before. GTK+ apps are starting to work under ROS, this alone should speak volumes! Btw! We need to implement NtGdiOffsetClipRgn, I dont care if it is a haxed wine port, atleast something. Bitmap seems broken too. X-Chat, WARNING: NtGdiOffsetClipRgn at subsys/win32k/objects/cliprgn.c:330 is UNIMPLEME NTED! WARNING: NtGdiOffsetClipRgn at subsys/win32k/objects/cliprgn.c:330 is UNIMPLEME NTED! (subsys/win32k/misc/object.c:463) Object type mismatch 0x2 0x5 (subsys/win32k/misc/object.c:463) Object type mismatch 0x2 0x5 (lib/comctl32/toolbar.c:416) bitmap for ID 0, index 1 is not valid, number of bi tmaps in imagelist: 0 (subsys/win32k/misc/object.c:463) Object type mismatch 0x2 0x5 (subsys/win32k/objects/gdiobj.c:545) GdiHdr->Locks: 1 Assertion 'FALSE' failed at subsys/win32k/objects/gdiobj.c line 549 KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0x80000003,0x8009fdf1,0x9dcf622e,0x00000009) *** ntoskrnl.exe - Address 0x8009fdf1 base at 0x80000000, DateStamp 0x0 Breakpoint Exception: 3(0) Processor: 0 CS:EIP 8:8009fdf1 <ntoskrnl.exe:9fdf1 ({standard input}:23 ())> cr2 77ee23f6 cr3 20c91000 Proc: 817108e0 Pid: 128 <gtk2_prefs.exe> Thrd: 81c744b 8 Tid: 120 DS 10 ES 10 FS 30 GS 0 EAX: 00000044 EBX: 000000d5 ECX: 00000000 EDX: 000003f8 EBP: 9db53c14 ESI: 0068fec0 ESP: 9db53b84 EDI: 9db53d74 EFLAGS: 00000292 kESP 9db53b84 kernel stack base 9db51000 Frames: <win32k.sys:802b8 (subsys/win32k/objects/gdiobj.c:549 (GDIOBJ_FreeObj))> <win32k.sys:805d2 (subsys/win32k/objects/gdiobj.c:670 (GDI_CleanupForProcess))> <win32k.sys:3aea3 (subsys/win32k/main/dllmain.c:102 (Win32kProcessCallback))> <ntoskrnl.exe:82c0e (ntoskrnl/ps/win32.c:99 (PsTerminateWin32Process))> <ntoskrnl.exe:7a5f2 (ntoskrnl/ps/kill.c:295 (PspExitThread))> <ntoskrnl.exe:7ad74 (ntoskrnl/ps/kill.c:593 (NtTerminateProcess))> <ntoskrnl.exe:958f2 ({standard input}:177 (KiSystemService))> <kernel32.dll:32142 (lib/kernel32/process/proc.c:592 (ExitProcess))> gdi32_crosstest bitmap, (subsys/win32k/objects/gdiobj.c:802) Attempted to lock object 0x0 that is delete d! (subsys/win32k/objects/gdiobj.c:802) Attempted to lock object 0x0 that is delete d! (subsys/win32k/objects/gdiobj.c:939) Attempted to lock object 0x0 that is delete d! Assertion 'Dest != NULL && Source != NULL && DestRect != NULL && SourcePoint != NULL' failed at subsys/win32k/eng/copybits.c line 53 KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0x80000003,0x8009fdf1,0x00000296,0x0a32ec37) *** ntoskrnl.exe - Address 0x8009fdf1 base at 0x80000000, DateStamp 0x0 Breakpoint Exception: 3(0) Processor: 0 CS:EIP 8:8009fdf1 <ntoskrnl.exe:9fdf1 ({standard input}:23 ())> cr2 930000 cr3 3aeda000 Proc: 816eb508 Pid: 120 <gdi32_crosstest> Thrd: 816f63c0 Tid: 124 DS 10 ES 10 FS 30 GS 0 EAX: 00000085 EBX: 0000106a ECX: 00000000 EDX: 000003f8 EBP: 9f32e8c0 ESI: 006cee54 ESP: 9f32e830 EDI: 9f32ed74 EFLAGS: 00000282 kESP 9f32e830 kernel stack base 9f32c000 Frames: <win32k.sys:30ce0 (subsys/win32k/eng/copybits.c:53 (EngCopyBits))> <win32k.sys:7a1e3 (subsys/win32k/objects/dib.c:508 (NtGdiGetDIBits))> <ntoskrnl.exe:958f2 ({standard input}:177 (KiSystemService))> <gdi32_crosstest.EXE:565c>

19 years, 10 months

2
2
0 0

0.2.7 needs help!

by WaxDragon

This is a call to all devs! The 0.2.7 branch has a input bug that is currently listed as a blocker for the release. We have been unable to get ahold of tinus (the i8042prt author) to take a look at this particular bug. If anyone is capable and interested in fixing this, please contact myself or simply join #reactos and offer help. Bug info: http://www.reactos.com/bugzilla/show_bug.cgi?id=657 WD -- #irc.freenode.net #reactos 01:03PM <filip2307> i don't know about any bug 01:04PM <filip2307> none exist 01:04PM <filip2307> ReactOS is prefect

19 years, 10 months

1
0
0 0

svn.reactos.com unavailable

by Casper Hornstrup

Hi. Svn.reactos.com will be unavailable in the next 15 min. to ½ hour. Casper

19 years, 10 months

1
0
0 0

Warning: filename case change

by Ge van Geldorp

> From: gvg(a)svn.reactos.com > > Added files: > trunk/reactos/lib/cpl/intl/sv.rc > > Deleted files: > trunk/reactos/lib/cpl/intl/Sv.rc The main intl.rc file referred to "sv.rc", but the file was named "Sv.rc". I've corrected this, but it might give problems when svn up'ing on windows. Just delete lib/cpl/intl/Sv.rc before doing an update. Gé van Geldorp.

19 years, 10 months

1
0
0 0

Re: [ros-dev] rdesktop

by reactos

Well, look at this page to find other nice things we would like to have, we need more then client: http://www2.reactos.com/wiki/index.php/ReactOS_Terminal_Services or http://www.reactos.com/wiki/index.php/ReactOS_Terminal_Services Yours sincerely, Jaix Bly ----Ursprungligt meddelande----- From: Wesley Parish wes.parish(a)paradise.net.nz Date: Mon, 1 Aug 2005 15:07:19 +0200 To: ReactOS Development List ros-dev(a)reactos.com Subject: [ros-dev] rdesktop > http://www.rdesktop.org/ > Another link in the chain of compatibility. > > All we need for it is for the networking code to become mature. > > Wesley Parish > -- > 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. > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

19 years, 10 months

4
3
0 0

Compiling error!

by David Eckert

I keep getting the following error: lib\ntdll\string\ctype.c:280: warning: '_pctype' defined locally after being referenced with dllimport linkage mingw32-make: *** [obj-i386\lib\ntdll\string\ctype.o] Error 1 I found a cheap little trick to it, commenting out line 280 in ctype.c will fix it (for now) -- -David W. Eckert

19 years, 10 months

1
0
0 0

www.reactos.com back up

by Ge van Geldorp

Most reactos.com services should be available again. The forum is still offline. Mailing lists, main website, wiki and bugzilla are functional again. It might take a little while for the DNS changes to trickle down the system, so if it doesn't work for you yet just try again in half a day or so. Gé van Geldorp.

19 years, 10 months

1
0
0 0

www.reactos.com back up

by Ge van Geldorp

Most reactos.com services should be available again. The forum is still offline. Mailing lists, main website, wiki and bugzilla are functional again. It might take a little while for the DNS changes to trickle down the system, so if it doesn't work for you yet just try again in half a day or so. Gé van Geldorp.

19 years, 10 months

1
0
0 0

rdesktop

by Wesley Parish

http://www.rdesktop.org/ Another link in the chain of compatibility. All we need for it is for the networking code to become mature. Wesley Parish -- 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.

19 years, 10 months

3
2
0 0

Re: Document pch and linkerflag elements.

by Martin Fuchs

Hello, the main XML build file "ReactOS.xml" is referencing a DTD file "tools/rbuild/project.dtd". But it's not included in the SVN repository. Is there already such a file? And in that case - could you please check it in? Thanks, Martin

19 years, 10 months

4
9
0 0

Re: [ros-diffs] [weiden] 16941: define common build flags so they can easily be changed for all tools

by Royce Mitchell III

weiden(a)svn.reactos.com wrote: >define common build flags so they can easily be changed for all tools > >Modified: trunk/reactos/tools/cdmake/cdmake.c > > > *Modified: trunk/reactos/tools/cdmake/cdmake.c* > >--- trunk/reactos/tools/cdmake/cdmake.c 2005-08-01 10:21:20 UTC (rev 16940) >+++ trunk/reactos/tools/cdmake/cdmake.c 2005-08-01 10:58:28 UTC (rev 16941) >@@ -423,6 +423,9 @@ > > if (d->extension_on_cd[0] != 0) > identifier_size += 1 + strlen(d->extension_on_cd); > break; > > >+ default: >+ identifier_size = 1; >+ break; > > > } > } > record_size = 33 + identifier_size; > > > ------------------------------------------------------------------------ This change appears to not relate to your commit message. Was it an accident or intentional?

19 years, 10 months

2
1
0 0

EventLog

by Saveliy Tretiakov

Hi. I'm implementing an EventLog service now. I want to make it 100% compatible with windows. Windows machines will be able to access reactos eventlog via rpc. Undocumented rpc interface is almost reversed now. You can find it in attached archive with some tests. Ansi functions work very well, but I have some problems with unicode ones. When I pass initialized with nulls UNICODE_STRING to a function, it works. When I initialize structure with some other values, exception is raised on server side (1783 Stub received bad data). I don't know why this happens. Advapi32 initializes structures with RtlInitUnicodeString, nothing special. Any ideas? And I don't know how to compile this with widl and gcc. SEH is not implemented in gcc, right? How rpc exceptions are handled in ROS? Widl returns strange errors. Somebody familiar with widl please help me =)

19 years, 10 months

4
5
0 0

Networking broken in 15400/15402 confirmed

by Gge

I summarize below the networking status for nic rtl8139 in real hardware , with the help of Alex , Filip and Hpoussin - Ping ok with svn 15400 - ping Nok with SVN15402+15404 and > - ping ok with head (svn 16894) + patch 15402/15404 removed The interesting part is this: 1) svn 15400 (ndis/io.c:824)(NdisMRegisterInterrupt) Called. InterruptVector (0xA) InterruptLevel (0xA) SharedInterrupt (1) InterruptMode (0x0) (ndis/io.c:843)(NdisMRegisterInterrupt) Connecting to interrupt vector (0x4A) Affinity (0xFFFFFFFF). (ndis/io.c:848)(NdisMRegisterInterrupt) Leaving. Status (0x0). 2) svn 15402/15404 (ndis/io.c:824)(NdisMRegisterInterrupt) Called. InterruptVector (0x0) InterruptLevel (0x0) SharedInterrupt (1) InterruptMode (0x0) (ndis/io.c:843)(NdisMRegisterInterrupt) Connecting to interrupt vector (0x40) Affinity (0xFFFFFFFF). (ndis/io.c:848)(NdisMRegisterInterrupt) Leaving. Status (0x0). 3) Svn 16860 (ndis\ndis\io.c:824)(NdisMRegisterInterrupt) Called. InterruptVector (0x9) InterruptLevel (0x9) SharedInterrupt (1) InterruptMode (0x0) (ndis\ndis\io.c:843)(NdisMRegisterInterrupt) Connecting to interrupt vector (0x49) Affinity (0xFFFFFFFF). (ndis\ndis\io.c:848)(NdisMRegisterInterrupt) Leaving. Status (0x0). Regards Gerard

19 years, 10 months

1
1
0 0

Re: [ros-dev] USB mouse support

by reactos

You used the BIOS USB to PS/2 bridge, not a USB driver. Yours sincerely, Jaix Bly ----Ursprungligt meddelande----- From: TwoTailedFox twotailedfox(a)gmail.com Date: Sat, 30 Jul 2005 17:52:59 +0200 To: Andrew Murphy andrewm1986(a)gmail.com Subject: Re: [ros-dev] USB mouse support > Oddly enough, I used 0.2.6 with a USB Mouse on my P4 System. The > cursor did appear, but the mouse sensitivity was way off. I could > roughly get it where I wanted to by moving very, very slowly, but this > wasn't practical, so I switched back to my USB-to-PS/2 way of using > the mouse. > > Good to hear it's near to being useable. > > On 7/30/05, Andrew Murphy <andrewm1986(a)gmail.com> wrote: > > > > > > On 30/07/05, Jonathan Wilson <jonwil(a)tpgi.com.au> wrote: > > > Good to hear. > > > > > > Working support for my Microsoft Optical Intellimouse Explorer USB Optical > > > Mouse is one of the 2 things I want before I will try ROS on real hardware > > > again. (the other is support for my Belikn Wireless Network Card and > > > software and enough networking support so I can talk to the wireless > > router > > > and from there to the internet) > > > > > > > > > _______________________________________________ > > > Ros-dev mailing list > > > Ros-dev(a)reactos.com > > > http://reactos.com:8080/mailman/listinfo/ros-dev > > > > > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.com > > http://reactos.com:8080/mailman/listinfo/ros-dev > > > > > > > -- > "I had a handle on life, but then it broke" > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

19 years, 10 months

1
0
0 0

Re: [ros-diffs] [hbirr] 16901: If a mutex already exist, open it instead of create.

by Joseph Galbraith

Are you sure that we should be acquiring the mutex in the open case? MSDN says: bInitialOwner [in] Specifies the initial owner of the mutex object. If this value is TRUE and the caller created the mutex, the calling thread obtains ownership of the mutex object. Otherwise, the calling thread does not obtain ownership of the mutex.... Thanks, Joseph hbirr(a)svn.reactos.com wrote: > If a mutex already exist, open it instead of create. > Modified: trunk/reactos/lib/kernel32/synch/mutex.c > Modified: trunk/reactos/lib/kernel32/synch/mutex.c > --- trunk/reactos/lib/kernel32/synch/mutex.c 2005-07-30 19:00:33 UTC (rev 16900) > +++ trunk/reactos/lib/kernel32/synch/mutex.c 2005-07-30 19:03:34 UTC (rev 16901) > @@ -92,10 +92,24 @@ > MUTEX_ALL_ACCESS, > &ObjectAttributes, > (BOOLEAN)bInitialOwner); > + if (Status == STATUS_OBJECT_NAME_COLLISION) > + { > + Status = NtOpenMutant(&MutantHandle, > + MUTEX_ALL_ACCESS, > + &ObjectAttributes); > + if (NT_SUCCESS(Status)) > + { > + if(bInitialOwner) > + { > + WaitForSingleObject(MutantHandle, INFINITE); > + } > + SetLastError(ERROR_ALREADY_EXISTS); > + } > + } > if (!NT_SUCCESS(Status)) > { > - SetLastErrorByStatus(Status); > - return NULL; > + SetLastErrorByStatus(Status); > + return NULL; > } > > return MutantHandle;

19 years, 10 months

1
0
0 0

rbuild: module attributes

by Emanuele Aliberti

Hi all, I think the *module* node needs two more attributes - *subsystem* and *windows* - because at present module type and module subsystem are merged in the *type* attribute and its values are a bit confusing to me; also cui/gui information is hidden into value names. I don't know the rbuild code and I can't therefore say if it is an easy task splitting the logic behind the *type* attribute into tree attributes whitout affecting the whole program logic. A short rationale follows. ___ Valid values for the *type* attribute should be: - library (static) - hal - driver - program - dll Valid values for the *subsystem* attribute should be: - none - native - windows - posix - os2 - vms (default "windows"; "none" required for type "library"; "native" required for types "hal", "driver") Valid values for the *windows* attribute should be: - no - yes (default "no"; "no" required for types "library", "hal", "driver") ___ Examples: *ntdll.dll* <module name="ntdll" type="dll" ...> note that, at present, it is incorrectly described this way <module name="ntdll" type="dll" subsystem="native" ...> *ntoskrnl.exe* <module name="ntoskrnl" type="program" subsystem="native" ...> *atapi.sys* <module name="atapi" type="driver" subsystem="native" ...> -- :Emanuele Aliberti

19 years, 10 months

2
4
0 0

Reactos.com problems

by Ge van Geldorp

There are pretty strong indications that the reactos.com box was cracked. It took part in a DDoS attack. As a consequence, it was isolated from the network. Unfortunately, I'm on vacation right now so I don't have physical access to the box and am unable to fix/reinstall. For the moment, I've moved the mailing lists to a backup box. I am not moving the website, since it seems the attack was carried out via the website (a vulnerability in one of the php script packages we use). I'll put up a dummy page informing visitors. Not sure how far along the release of 0.2.7 is, but I'd like to suggest to put it off for at least another week, until I'm back and can sort things out. Apologies for the inconvenience, Ge van Geldorp.

19 years, 10 months

4
5
0 0

[Fwd: Re: [ros-dev] Regression in 15402 - fix in 16860

by Gge

Svn 16860 has fixed this problem (drivers\net\ndis\ndis\io.c:824)(NdisMRegisterInterrupt) Called. InterruptVector (0x9) InterruptLevel (0x9) SharedInterrupt (1) InterruptMode (0x0) (drivers\net\ndis\ndis\io.c:843)(NdisMRegisterInterrupt) Connecting to interrupt vector (0x49) Affinity (0xFFFFFFFF). (drivers\net\ndis\ndis\io.c:848)(NdisMRegisterInterrupt) Leaving. Status (0x0). I'll test again "ping" command with head Regards Gerard

19 years, 10 months

1
0
0 0

Re: [ros-dev] USB mouse support

by reactos

Hello mr. Wilson and all others who is interested in USB mouse & keyboard. USB mouse and keyboard is being worked on right now, and it will be ready before 0.3.0 and probably after 0.2.7. We are talking weeks not months. Then again, this will be the USB Key and mouse driver, so expect some time for it to mature. Keyboard drivers is probably to be released first because this driver doesn't need HID stack, then the mouse driver will be developed, but there is a need there if some one could find a USB mouse driver C source that doesn't use a HID stack it will be done a lot faster. One interesting detail is that the development will be tested on XBox hardware which will make the XBox-port usable as a development platform. Yours sincerely, Jaix Bly ----Ursprungligt meddelande----- From: Jonathan Wilson jonwil(a)tpgi.com.au Date: Sat, 30 Jul 2005 02:21:02 +0200 To: ReactOS Development List ros-dev(a)reactos.com Subject: [ros-dev] USB mouse support > How far away is support for USB mice? > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

19 years, 10 months

4
3
0 0

RE: [ros-svn] [sedwards] 16887: dos line endings

by Casper Hornstrup

Put svn:eol-style = native on them, then the svn client will take care of it: svn propset -R svn:eol-style "native" dosfsck Casper > -----Original Message----- > From: ros-svn-bounces(a)reactos.com [mailto:ros-svn-bounces@reactos.com] On Behalf Of > sedwards(a)svn.reactos.com > Sent: 30. juli 2005 01:04 > To: ros-svn(a)reactos.com > Subject: [ros-svn] [sedwards] 16887: dos line endings > > dos line endings > > > Updated files: > trunk/rosapps/sysutils/dosfsck/boot.c > trunk/rosapps/sysutils/dosfsck/boot.h > trunk/rosapps/sysutils/dosfsck/byteorder.h > trunk/rosapps/sysutils/dosfsck/byteswap.h > trunk/rosapps/sysutils/dosfsck/byteswap1.h > trunk/rosapps/sysutils/dosfsck/check.c > trunk/rosapps/sysutils/dosfsck/check.h > trunk/rosapps/sysutils/dosfsck/common.c > trunk/rosapps/sysutils/dosfsck/common.h > trunk/rosapps/sysutils/dosfsck/compiler.h > trunk/rosapps/sysutils/dosfsck/dosfsck.c > trunk/rosapps/sysutils/dosfsck/dosfsck.h > trunk/rosapps/sysutils/dosfsck/fat.c > trunk/rosapps/sysutils/dosfsck/fat.h > trunk/rosapps/sysutils/dosfsck/file.c > trunk/rosapps/sysutils/dosfsck/file.h > trunk/rosapps/sysutils/dosfsck/getopt.c > trunk/rosapps/sysutils/dosfsck/io.c > trunk/rosapps/sysutils/dosfsck/io.h > trunk/rosapps/sysutils/dosfsck/lfn.c > trunk/rosapps/sysutils/dosfsck/lfn.h > trunk/rosapps/sysutils/dosfsck/msdos_fs.h > trunk/rosapps/sysutils/dosfsck/swab.h > trunk/rosapps/sysutils/dosfsck/version.h > trunk/rosapps/sysutils/dosfsck/vfat.h > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-svn

19 years, 10 months

2
1
0 0

Wallpaper and Registry Keys

by James Tabor

Hi all! In Mastering, Win 2K Registry, Sybex books, Pages 282-285. We need some registry fixup to save the wallpaper. HKEY_USERS\.DEFAULT\Control Panel\Desktop, entry Wallpaper, type REG_SZ and value: fully qualified bitmap image filename, entry WallpaperStyle, type REG_SZ and value: 0, entry TileWallpaper, type REG_SZ and value: 0, and on... Same with Mastering, Win XP Registry, Sybex books, Pages 230-231, nothing changed. Is there a problem with implementing some of these? What was the show stopper? Thanks, James

19 years, 10 months

2
1
0 0

USB mouse support

by Jonathan Wilson

How far away is support for USB mice?

19 years, 10 months

1
0
0 0

RE: [ros-svn] [gdalsnes] 16793: my 1st

by Murphy, Ged (Bolton)

gdalsnes(a)svn.reactos.com wrote: > my 1st > > > Added files: > branches/hardons1stbranch/ > > Updated files: > branches/hardons1stbranch/kapi.h branches/hardons1stbranch/ntuser.h > > Deleted files: > branches/hardons1stbranch/debug.h branches/hardons1stbranch/debug1.h Hi Hardon. Out of interest, what's the purpose of this branch? (probably been discussed in IRC, but I missed it) Thanks, Ged. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

19 years, 10 months

10
17
0 0

Re: [ros-dev] RE: [ros-svn] [gdalsnes] 16793: my 1st

by ayerkes＠speakeasy.net

> -----Original Message----- > From: Richard [mailto:eek2121@comcast.net] > Sent: Friday, July 29, 2005 12:18 AM > To: 'ReactOS Development List' > Subject: Re: [ros-dev] RE: [ros-svn] [gdalsnes] 16793: my 1st > > Then where is this effort? Why is one developer wandering off on his > own? How about setting a 'win32k rewrite' as a goal for 0.4? That is, > if 0.3 ever makes it out the door... > > Honestly, i think that devs should work towards the feature set we > planned for 0.3, however that is just me. Granted, there is no money > involved in this project, but not setting goals and randomly doing > rewrites is the fast way to code burnout, boredom, and lost interest. > Drowning yourself in an impossibly large project is nuts. > > Richard Not meeting 0.3 is largely my fault. I don't even know when I'll be able to return to writing on it in a consistent way, given my new job :-(. I've had several offers from others to write on it but it seems that most people either aren't very interested in what remains, or don't feel confident about working on kernel code. The remaining kernel tasks don't actually involve much know-how about the kernel, and my components are designed to be easy to understand (with minimal concurrency). Only three things are needed to meet the 0.3 goal: 1) retest apps on the 0.3 list and fix regressions 2) finish the net cpl and possibly fix bugs in npfs that make CallNamedPipe bugcheck 3) (big) finish needed stuff for mozilla compatibility There are a lot of generic tasks in net that need doing, and could really be done by anybody. They affect the kernel but won't use very much specific kernel code: 1) Plumb remaining ioctls into kernel land (afd/info.c,tcpip/*info.c) - Keepalive - Nagle - TTL (datagram and tcp) - Verify behavior of nonblocking sockets - send/rcv buf 2) Plumb ARP cache requests (tcpip/iinfo.c,network/neighbor.c) 3) Put together a test matrix for socket end conditions (when I get my stuff from chicago next saturday, I'll be able to pass on my test apps and notes), and emulate winsock properly. 4) Finish the NTSTATUS -> winsock error conversion and use it everywhere 5) Finish off errno -> NTSTATUS conversion in tcp.c 6) Finish any kernel-related IOCTL changes 7) Write a test tool and verify WSAEnumNetworkEvents 8) Do some refactoring in afd/select.c to make it easier to understand Hard kernely tasks: 1) Fix IRP cancellation in tcpip 2) Verify CLOSE/CLEANUP in afd and tcpip 3) Better buffer management in afd 4) Fix use of TDI_TRANSPORT_ADDRESS vs TA_ADDRESS and verify correctness based on osr docs 5) Test out our AFD and TCPIP on real windows with kd 6) Replace recursive mutex

19 years, 10 months

1
0
0 0

Re: [ros-svn] [ion] 16811: - Fix debug header nonsense

by Hartmut Birr

ion(a)svn.reactos.com wrote: > - Fix debug header nonsense > - Fix some w32api definitions > - MSVC/PSDK Compatibility fixes. > - Clean up user32 headers for greater PCH usage. > > >Added files: >trunk/reactos/lib/user32/include/controls.h >trunk/reactos/lib/user32/include/dde_private.h >trunk/reactos/w32api/include/winnls32.h > >Updated files: >trunk/reactos/apps/utils/ps/ps.c >trunk/reactos/drivers/dd/mpu401/settings.c >trunk/reactos/include/reactos/debug.h >trunk/reactos/include/wine/debug.h >trunk/reactos/lib/ntdll/inc/ntdll.h >trunk/reactos/lib/user32/controls/button.c >trunk/reactos/lib/user32/controls/combo.c >trunk/reactos/lib/user32/controls/edit.c >trunk/reactos/lib/user32/controls/icontitle.c >trunk/reactos/lib/user32/controls/listbox.c >trunk/reactos/lib/user32/controls/scrollbar.c >trunk/reactos/lib/user32/include/user32.h >trunk/reactos/lib/user32/include/user32p.h >trunk/reactos/lib/user32/misc/dde.c >trunk/reactos/lib/user32/misc/ddeclient.c >trunk/reactos/lib/user32/misc/ddeserver.c >trunk/reactos/lib/user32/misc/display.c >trunk/reactos/lib/user32/misc/dllmain.c >trunk/reactos/lib/user32/misc/exticon.c >trunk/reactos/lib/user32/misc/object.c >trunk/reactos/lib/user32/misc/stubs.c >trunk/reactos/lib/user32/windows/bitmap.c >trunk/reactos/lib/user32/windows/clipboard.c >trunk/reactos/lib/user32/windows/cursor.c >trunk/reactos/lib/user32/windows/defwnd.c >trunk/reactos/lib/user32/windows/dialog.c >trunk/reactos/lib/user32/windows/draw.c >trunk/reactos/lib/user32/windows/font.c >trunk/reactos/lib/user32/windows/hook.c >trunk/reactos/lib/user32/windows/icon.c >trunk/reactos/lib/user32/windows/input.c >trunk/reactos/lib/user32/windows/mdi.c >trunk/reactos/lib/user32/windows/menu.c >trunk/reactos/lib/user32/windows/message.c >trunk/reactos/lib/user32/windows/messagebox.c >trunk/reactos/lib/user32/windows/nonclient.c >trunk/reactos/lib/user32/windows/paint.c >trunk/reactos/lib/user32/windows/window.c >trunk/reactos/w32api/include/winuser.h > >Deleted files: >trunk/reactos/lib/user32/controls/controls.h >trunk/reactos/lib/user32/include/debug.h >trunk/reactos/lib/user32/misc/dde_private.h > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > > Please revert the changes in include/wine/debug.h. Your changes enables the TRACE and WARN statements for all wine dlls. The debug messages are no longer useful, because the output is flooded with thausends of unwanted messages. - Hartmut

19 years, 10 months

2
1
0 0

Please commit these patches

by Saveliy Tretiakov

I sent this to ros-dev about 3 months ago but nobody commited. ChangeLog: Correct return values. Fix suggested by w3seek. Index: misc/comm.c =================================================================== --- misc/comm.c (revision 16707) +++ misc/comm.c (working copy) @@ -834,7 +834,7 @@ CommConfigDialogA(LPCSTR lpszName, HWND hWnd, LPCOMMCONFIG lpCC) { PWCHAR NameW; - BOOL result; + DWORD result; /* don't use the static thread buffer so operations in serialui don't overwrite the string */ @@ -858,9 +858,9 @@ STDCALL CommConfigDialogW(LPCWSTR lpszName, HWND hWnd, LPCOMMCONFIG lpCC) { - BOOL (STDCALL *drvCommDlgW)(LPCWSTR, HWND, LPCOMMCONFIG); + DWORD (STDCALL *drvCommDlgW)(LPCWSTR, HWND, LPCOMMCONFIG); HMODULE hSerialuiDll; - BOOL result; + DWORD result; //FIXME: Get dll name from registry. (setupapi needed) if(!(hSerialuiDll = LoadLibraryW(L"serialui.dll"))) @@ -869,7 +869,8 @@ return FALSE; } - drvCommDlgW = GetProcAddress(hSerialuiDll, "drvCommConfigDialogW"); + drvCommDlgW = (DWORD (STDCALL *)(LPCWSTR, HWND, LPCOMMCONFIG)) + GetProcAddress(hSerialuiDll, "drvCommConfigDialogW"); if(!drvCommDlgW) { @@ -879,8 +880,10 @@ } result = drvCommDlgW(lpszName, hWnd, lpCC); + SetLastError(result); FreeLibrary(hSerialuiDll); - return result; + + return (result == ERROR_SUCCESS ? TRUE : FALSE); } Index: serialui.h =================================================================== --- serialui.h (revision 16707) +++ serialui.h (working copy) @@ -11,8 +11,7 @@ #include "resource.h" #define UNIMPLEMENTED \ - SetLastError(ERROR_CALL_NOT_IMPLEMENTED); \ - return FALSE; + return ERROR_CALL_NOT_IMPLEMENTED ; #define DEFAULT_BAUD_INDEX 6 #define DEFAULT_BYTESIZE_INDEX 3 @@ -45,27 +44,27 @@ * ************************************/ -BOOL WINAPI drvCommConfigDialogW(LPCWSTR lpszDevice, +DWORD WINAPI drvCommConfigDialogW(LPCWSTR lpszDevice, HWND hWnd, LPCOMMCONFIG lpCommConfig); -BOOL WINAPI drvCommConfigDialogA(LPCSTR lpszDevice, +DWORD WINAPI drvCommConfigDialogA(LPCSTR lpszDevice, HWND hWnd, LPCOMMCONFIG lpCommConfig); -BOOL WINAPI drvSetDefaultCommConfigW(LPCWSTR lpszDevice, +DWORD WINAPI drvSetDefaultCommConfigW(LPCWSTR lpszDevice, LPCOMMCONFIG lpCommConfig, DWORD dwSize); -BOOL WINAPI drvSetDefaultCommConfigA(LPCSTR lpszDevice, +DWORD WINAPI drvSetDefaultCommConfigA(LPCSTR lpszDevice, LPCOMMCONFIG lpCommConfig, DWORD dwSize); -BOOL WINAPI drvGetDefaultCommConfigW(LPCWSTR lpszDevice, +DWORD WINAPI drvGetDefaultCommConfigW(LPCWSTR lpszDevice, LPCOMMCONFIG lpCommConfig, LPDWORD lpdwSize); -BOOL WINAPI drvGetDefaultCommConfigA(LPCSTR lpszDevice, +DWORD WINAPI drvGetDefaultCommConfigA(LPCSTR lpszDevice, LPCOMMCONFIG lpCommConfig, LPDWORD lpdwSize); Index: serialui.c =================================================================== --- serialui.c (revision 16707) +++ serialui.c (working copy) @@ -98,7 +98,7 @@ /* * @implemented */ -BOOL WINAPI drvCommConfigDialogW(LPCWSTR lpszDevice, +DWORD WINAPI drvCommConfigDialogW(LPCWSTR lpszDevice, HWND hWnd, LPCOMMCONFIG lpCommConfig) { @@ -106,7 +106,7 @@ if(!lpszDevice || !lpCommConfig) { - return FALSE; + return ERROR_INVALID_PARAMETER; } DialogInfo.lpszDevice = lpszDevice; @@ -119,7 +119,7 @@ /* * @implemented */ -BOOL WINAPI drvCommConfigDialogA(LPCSTR lpszDevice, +DWORD WINAPI drvCommConfigDialogA(LPCSTR lpszDevice, HWND hWnd, LPCOMMCONFIG lpCommConfig) { @@ -136,13 +136,13 @@ return result; } else - return FALSE; + return ERROR_NOT_ENOUGH_MEMORY; } /* * @unimplemented */ -BOOL WINAPI drvSetDefaultCommConfigW(LPCWSTR lpszDevice, +DWORD WINAPI drvSetDefaultCommConfigW(LPCWSTR lpszDevice, LPCOMMCONFIG lpCommConfig, DWORD dwSize) { @@ -152,7 +152,7 @@ /* * @unimplemented */ -BOOL WINAPI drvSetDefaultCommConfigA(LPCSTR lpszDevice, +DWORD WINAPI drvSetDefaultCommConfigA(LPCSTR lpszDevice, LPCOMMCONFIG lpCommConfig, DWORD dwSize) { @@ -162,7 +162,7 @@ /* * @unimplemented */ -BOOL WINAPI drvGetDefaultCommConfigW(LPCWSTR lpszDevice, +DWORD WINAPI drvGetDefaultCommConfigW(LPCWSTR lpszDevice, LPCOMMCONFIG lpCommConfig, LPDWORD lpdwSize) { @@ -172,7 +172,7 @@ /* * @unimplemented */ -BOOL WINAPI drvGetDefaultCommConfigA(LPCSTR lpszDevice, +DWORD WINAPI drvGetDefaultCommConfigA(LPCSTR lpszDevice, LPCOMMCONFIG lpCommConfig, LPDWORD lpdwSize) { @@ -231,7 +231,7 @@ /* Initialize baud rate combo */ if(!(hBox = GetDlgItem(hDlg, IDC_BAUDRATE))) - EndDialog(hDlg, 0); + EndDialog(hDlg, ERROR_CANCELLED); for(i = 0; Bauds[i]; i++) { @@ -246,7 +246,7 @@ /* Initialize byte size combo */ if(!(hBox = GetDlgItem(hDlg, IDC_BYTESIZE))) - EndDialog(hDlg, 0); + EndDialog(hDlg, ERROR_CANCELLED); for(i = 0; ByteSizes[i]; i++) { @@ -261,7 +261,7 @@ /* Initialize parity combo */ if(!(hBox = GetDlgItem(hDlg, IDC_PARITY))) - EndDialog(hDlg, 0); + EndDialog(hDlg, ERROR_CANCELLED); for(i = 0; Parities[i].StrId; i++) { @@ -278,7 +278,7 @@ /* Initialize stop bits combo */ if(!(hBox = GetDlgItem(hDlg, IDC_STOPBITS))) - EndDialog(hDlg, 0); + EndDialog(hDlg, ERROR_CANCELLED); for(i = 0; StopBits[i].StrId; i++) { @@ -295,7 +295,7 @@ /* Initialize flow control combo */ if(!(hBox = GetDlgItem(hDlg, IDC_FLOW))) - EndDialog(hDlg, 0); + EndDialog(hDlg, ERROR_CANCELLED); if(LoadStringW(hDllInstance, IDS_FC_NO, wstr, sizeof(wstr) / sizeof(wstr[0]))) { @@ -337,11 +337,11 @@ switch(wParam) { case IDC_CANCELBTN: - EndDialog(hDlg, FALSE); + EndDialog(hDlg, ERROR_CANCELLED); break; case IDC_OKBTN: OkButton(hDlg); - EndDialog(hDlg, TRUE); + EndDialog(hDlg, ERROR_SUCCESS); break; } return TRUE; @@ -349,11 +349,11 @@ case WM_CLOSE: { - EndDialog(hDlg, FALSE); + EndDialog(hDlg, ERROR_CANCELLED); return TRUE; } /* WM_CLOSE */ - default: + default: return FALSE; }

19 years, 10 months

2
2
0 0

API status

by Casper Hornstrup

Hi. I've set up the API status at: http://svn.reactos.com/api/ Casper

19 years, 10 months

2
2
0 0

RE: [ros-diffs] [ea] 16854: Various fixex to make HEAD compile.

by Casper Hornstrup

Why not just remove the code in #if 0/#endif? It serves no purpose. ________________________________________ From: ros-diffs-bounces(a)reactos.com [mailto:ros-diffs-bounces@reactos.com] On Behalf Of ea(a)svn.reactos.com Sent: 29. juli 2005 12:05 To: ros-diffs(a)reactos.com Subject: [ros-diffs] [ea] 16854: Various fixex to make HEAD compile. Various fixex to make HEAD compile. I hope I did break nothing. Modified: trunk/reactos/hal/halx86/generic/processor.c Modified: trunk/reactos/lib/advapi32/sec/trustee.c Modified: trunk/reactos/lib/advapi32/service/scm.c Modified: trunk/reactos/subsys/csrss/win32csr/desktopbg.c Modified: trunk/reactos/subsys/ntvdm/ntvdm.c Modified: trunk/reactos/subsys/smss/client.c Modified: trunk/reactos/subsys/system/setup/setup.c Modified: trunk/reactos/subsys/system/winlogon/setup.c Modified: trunk/reactos/subsys/win32k/ntuser/keyboard.c ________________________________________ Modified: trunk/reactos/hal/halx86/generic/processor.c --- trunk/reactos/hal/halx86/generic/processor.c 2005-07-29 09:51:08 UTC (rev 16853) +++ trunk/reactos/hal/halx86/generic/processor.c 2005-07-29 10:04:38 UTC (rev 16854) @@ -39,7 +39,9 @@ HalStartNextProcessor(ULONG Unknown1, ULONG ProcessorStack) { +#if 0 DPRINT("HalStartNextProcessor(%x %x)\n", ProcessorNumber, ProcessorStack); +#endif return TRUE; }

19 years, 10 months

2
1
0 0

Re: [ros-dev] Regression in 15402

by Filip Navara

19 years, 10 months

2
1
0 0

Geda Tool GSchem with Gdi Object Bug

by James Tabor

Hi, If anyone likes EDA programming tools and stuff. I've been testing geda tools from http://geda.seul.org/. The mingw32 tool set. At least I had the canvas and the info window popped up. Still more work to be done, but better than ~9 mo ago. Here is the debug log, (lib/ntdll/ldr/utils.c:2037) Failed to create or open dll section of 'Wintab32.d ll' (Status c0000135) GDI32: GetTextCharsetInfo is unimplemented, please try again later. (lib/ntdll/ldr/utils.c:2094) Relocating (10000000 -> dc1000) C:\geda\lib\pango\1 .2.0\modules\pango-basic-win32.dll (lib/ntdll/ldr/utils.c:1215) LdrGetExportByName(): failed to find g_module_check _init (lib/ntdll/ldr/utils.c:1215) LdrGetExportByName(): failed to find g_module_unloa d (lib/ntdll/ldr/utils.c:2037) Failed to create or open dll section of 'usp10.dll' (Status c0000135) WARNING: NtGdiGetGlyphOutline at subsys/win32k/objects/text.c:2163 is UNIMPLEME NTED! WARNING: NtGdiGetGlyphOutline at subsys/win32k/objects/text.c:2163 is UNIMPLEME NTED! <snip... .> WARNING: NtGdiGetGlyphOutline at subsys/win32k/objects/text.c:2163 is UNIMPLEME NTED! (ntoskrnl/io/file.c:3366) Invalid access rights (lib/ntdll/ldr/utils.c:2094) Relocating (10000000 -> de1000) C:\geda\lib\gtk-2.0 \2.2.0\loaders\libpixbufloader-xpm.dll (lib/ntdll/ldr/utils.c:1215) LdrGetExportByName(): failed to find g_module_check _init (lib/ntdll/ldr/utils.c:1215) LdrGetExportByName(): failed to find g_module_unloa d WARNING: NtGdiGetGlyphOutline at subsys/win32k/objects/text.c:2163 is UNIMPLEME NTED! <snip... .> WARNING: NtGdiOffsetClipRgn at subsys/win32k/objects/cliprgn.c:330 is UNIMPLEME NTED! WARNING: NtGdiOffsetClipRgn at subsys/win32k/objects/cliprgn.c:330 is UNIMPLEME NTED! WARNING: NtGdiOffsetClipRgn at subsys/win32k/objects/cliprgn.c:330 is UNIMPLEME NTED! (ntoskrnl/mm/mm.c:300) Address: ffffffff _SEHCallHandler: REG 006de75c _SEHCallHandler: REG 006dec28 _SEHCallHandler: REG 006dec28 Unhandled exception Address: 7c819641 C:\ReactOS\system32\kernel32.dll CS:EIP 1b:7c819641 DS 23 ES 23 FS 3b GS 0 EAX: 7c8b95c8 EBX: 27100250 ECX: 006df0f0 EDX: 00005453 EBP: 006df148 ESI: 10043ea3 ESP: 006df100 EDI: 000003d7 EFLAGS: 00010217 Frames: 7c800000+199b9 C:\ReactOS\system32\kernel32.dll 80b000+62493 C:\geda\lib\libglib-2.0-0.dll 10000000+4e718 C:\geda\lib\libgdk-win32-2.0-0.dll 10000000+442b0 C:\geda\lib\libgdk-win32-2.0-0.dll 10000000+334d6 C:\geda\lib\libgdk-win32-2.0-0.dll 10000000+33b67 C:\geda\lib\libgdk-win32-2.0-0.dll 10000000+3ea1 C:\geda\lib\libgdk-win32-2.0-0.dll 10000000+3ea1 C:\geda\lib\libgdk-win32-2.0-0.dll 10000000+1f133 C:\geda\lib\libgdk-win32-2.0-0.dll 10000000+3ea1 C:\geda\lib\libgdk-win32-2.0-0.dll 9de000+1512a3 C:\geda\lib\libgtk-win32-2.0-0.dll 9de000+1571b2 C:\geda\lib\libgtk-win32-2.0-0.dll 9de000+21090e C:\geda\lib\libgtk-win32-2.0-0.dll 9de000+2109af C:\geda\lib\libgtk-win32-2.0-0.dll 9de000+eeffa C:\geda\lib\libgtk-win32-2.0-0.dll 966000+4469 C:\geda\lib\libgobject-2.0-0.dll 966000+3cbc C:\geda\lib\libgobject-2.0-0.dll 966000+1727f C:\geda\lib\libgobject-2.0-0.dll 966000+166f1 C:\geda\lib\libgobject-2.0-0.dll 966000+16b36 C:\geda\lib\libgobject-2.0-0.dll 9de000+1fe4bb C:\geda\lib\libgtk-win32-2.0-0.dll 9de000+ed9dd C:\geda\lib\libgtk-win32-2.0-0.dll 10000000+2123e C:\geda\lib\libgdk-win32-2.0-0.dll 10000000+212da C:\geda\lib\libgdk-win32-2.0-0.dll 9de000+44160 C:\geda\lib\libgtk-win32-2.0-0.dll 80b000+1c865 C:\geda\lib\libglib-2.0-0.dll 80b000+1d07c C:\geda\lib\libglib-2.0-0.dll 80b000+1d6e3 C:\geda\lib\libglib-2.0-0.dll 80b000+1a21f C:\geda\lib\libglib-2.0-0.dll 9de000+ed0e9 C:\geda\lib\libgtk-win32-2.0-0.dll 400000+8f60 C:\geda\bin\gschem.exe 6eb00000+1dae1 C:\geda\lib\libguile.dll 6eb00000+2113c C:\geda\lib\libguile.dll 6eb00000+45696 C:\geda\lib\libguile.dll 6eb00000+20ef8 C:\geda\lib\libguile.dll 6eb00000+20dcb C:\geda\lib\libguile.dll 6eb00000+1db0b C:\geda\lib\libguile.dll 400000+9266 C:\geda\bin\gschem.exe 400000+1182 C:\geda\bin\gschem.exe 400000+1018 C:\geda\bin\gschem.exe 7c800000+2efec C:\ReactOS\system32\kernel32.dll _SEHCallHandler: REG 006deca8 _SEHCallHandler: REG 006dffb8 _SEHCallHandler: REG 006dffb8 (subsys/win32k/objects/gdiobj.c:545) GdiHdr->Locks: 1 Assertion 'FALSE' failed at subsys/win32k/objects/gdiobj.c line 549 KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0x80000003,0x8009fdc1,0x9dcf624e,0x00000009) *** ntoskrnl.exe - Address 0x8009fdc1 base at 0x80000000, DateStamp 0x0 Breakpoint Exception: 3(0) Processor: 0 CS:EIP 8:8009fdc1 <ntoskrnl.exe:9fdc1 ({standard input}:23 ())> cr2 76179ed5 cr3 3ac9d000 Proc: 816d71b0 Pid: 120 <gschem.exe> Thrd: 816d8c40 Ti d: 124 DS 10 ES 10 FS 30 GS 0 EAX: 00000044 EBX: 000000d5 ECX: 00000000 EDX: 000003f8 EBP: 9f0ffc14 ESI: 006dfef0 ESP: 9f0ffb84 EDI: 9f0ffd74 EFLAGS: 00000292 kESP 9f0ffb84 kernel stack base 9f0fd000 Frames: <win32k.sys:802d8 (subsys/win32k/objects/gdiobj.c:549 (GDIOBJ_FreeObj))> <win32k.sys:805f2 (subsys/win32k/objects/gdiobj.c:670 (GDI_CleanupForProcess))> <win32k.sys:3aea3 (subsys/win32k/main/dllmain.c:102 (Win32kProcessCallback))> <ntoskrnl.exe:82bce (ntoskrnl/ps/win32.c:99 (PsTerminateWin32Process))> <ntoskrnl.exe:7a6a2 (ntoskrnl/ps/kill.c:295 (PspExitThread))> <ntoskrnl.exe:7ae16 (ntoskrnl/ps/kill.c:591 (NtTerminateProcess))> <ntoskrnl.exe:958b2 ({standard input}:177 (KiSystemService))> <kernel32.dll:32222 (lib/kernel32/process/proc.c:592 (ExitProcess))>

19 years, 10 months

1
0
0 0

Forward to or put a link to http://reactosde.re.funpic.de on the ROS homepage?

by reactos

Wouldn't it be good to forward web-users to http://reactosde.re.funpic.de ? or at least put a link for those wanting to go on with something? Yours sincerely, Jaix Bly

19 years, 10 months

2
1
0 0

Upgrading Subversion to 1.2.1

by Casper Hornstrup

Hi. I'm upgrading Subversion on svn.reactos.com to version 1.2.1 to correct some memory leaks in svnserve. Subversion 1.2.x also brings us: Faster access to old revisions. svn blame, svn checkout, svn update, svn diff, svn merge will be faster. Locking. If you have an 1.2.x client you can lock files and directories. This is mostly useful for binaries so it's possibly not something we will use much. For faster access to old revisions, a "dump and load" of the repository is needed so the repository will be unavailable for a few hours today. Casper

19 years, 10 months

1
1
0 0

Regression in 15402

by Alex Ionescu

Hi, It seems that the problem regarding Ged's RTL network card is related to patch 15402: http://svn.reactos.com/viewcvs?view=rev&rev=15402. Is it possible that the card is incorrectly (or not in the same way we are expecting) telling us its resource data? Or that somethign has been overlooked? Ged has done a terrible deal of network testing for us but he's been unable to work since his network card couldn't even ping anymore. I've helped him find the regression and I hope someone more experienced in PnP can help him out... at least we know what patch did it. Best regards, Alex Ionescu

19 years, 10 months

1
1
0 0

Re: [ros-diffs] [ion] 16730: - Final ROSRTL removal patch. The next patch will remove the actual library and code.

by Hartmut Birr

ion(a)svn.reactos.com wrote: >- Final ROSRTL removal patch. The next patch will remove the actual library and code. >- Changes: > - CreateProcess > * Cleanup creation of the initial thread using new utility functions and remove rosrtl > * Almost entirely rewrote the function to support features such as: > - SxS (locally only, patch will follow), > - SFP (SAFER) (locally only, patch will follow), > - DllPaths (locally only, patch will follow), > - Proper process environment/paramter block creation > - Proper console handle management (needs more work in kernel32/csr), > - Tokens/CreateProcessAsUser (locally only, patch will follow), > - Simpler code for path lookup, and more robust. > - Support for "auto-correction" (see Raymond Chen's blog) > - 16-bit/NE detection > - A variety of creation flags are now properly supported > - Added support for an undocumented-yet-known (see comment) shell flag > - Alert for flags we don't support yet > - Catch invalid flag combinations and other caller errors > - Improve and correct path searcing to use documented behaviours > - Created a multitude of helper functions to make the code easier to read > and allow them to be used for other apis as time goes on. > > - BaseProcessStartup > * Call NtSetThreadInformation to let the Kernel know of the Thread's Start Address. > * Correct prototype of Thread Startup function for this case. > >This fixes MANY things, some of which may not be evident, and possibly creates regressions which I have not yet seen but will try to correct. Some of these may be caused by the fact that I've seen code send CreateProcessW incorrect flags. Some things of note: DO NOT send partial names as "lpApplicationName". It's not supposed to work unless you're in the same current directory. Also, do NOT send CREATE_UNICODE_ENVIRONMENT if you don't have a unicode environement, and vice-versa. I've seen lots of code doing mistakes related to this. I hope you appreciate this patch and won't all jump on me for possbile regressions :(. > >Modified: trunk/reactos/lib/kernel32/process/create.c >Modified: trunk/reactos/lib/kernel32/thread/i386/thread.S >Modified: trunk/reactos/lib/kernel32/thread/thread.c >Modified: trunk/reactos/ntoskrnl/mm/process.c > > > ------------------------------------------------------------------------ Hi, your rewrite of CreateProcess is broken. Before you can inform csrss about the process creation, you have to gather all informations about handles and creation options. After your commit, each console application creates its own console window and the redirection of standard handles is broken. It seems also that the inheritance of msvcrt file id's is broken. This stops compiling ros on ros. - Hartmut

19 years, 10 months

3
2
0 0

Crash by starting OOo1.4 setup.exe (r16740)

by reactos

OOo1.4 Setup is crashing ROS, here comes a crashreport ROS r16740 Yours sincerely, Jaix Bly

19 years, 10 months

3
2
0 0

Re: [ros-svn] [ion] 16728: - Don't try to get the length of a possibly empty string. This fixes many menu applications (such as WinRAR). However I'm now getting a bug due to a double-free. It seems a GDI Object is being freed twice. Can anyone check this out please?

by Alex Ionescu

ion(a)svn.reactos.com wrote: > - Don't try to get the length of a possibly empty string. This fixes many menu applications (such as WinRAR). However I'm now getting a bug due to a double-free. It seems a GDI Object is being freed twice. Can anyone check this out please? > > > With the combination of this patch + Hartmut's patch + DBG = 0 build (and/or disabling RZ detection), Winrar runs fine again. However, pressing OK in the dialog bug causes a crash in RtlFreeUnicodeString->RtlpFreeMemory->ExFreePool. It seems the buffer is invalid. So it looks like two things have to be fixed for Winrar and other apps to work fine (Windows Commander does work now): 1) Stop the GDI Object from being freed twice. This will fix the first bugcheck and allow Winrar to work in DBG = 1 with RZ enabled. Disabling RZ is only a hack and shouldn't be used a solution. The stack trace ships the double-free routine pretty well, but I'm not well versed in win32k to fix this. 2) Find out why we are RtlFreeUnicodestring-ing what seems to be an invalid pointer. I think if we can fix these two issues we'll have many more apps working again! I've tested Winrar 3.50 b7, btw. Best regards, Alex Ionescu

19 years, 10 months

3
3
0 0

Re: [ros-diffs] [ion] 16804: - Include ctype.h by default.

by Hartmut Birr

ion(a)svn.reactos.com wrote: >- Include ctype.h by default. > >Modified: trunk/reactos/w32api/include/winnt.h > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/w32api/include/winnt.h* > >--- trunk/reactos/w32api/include/winnt.h 2005-07-27 16:34:14 UTC (rev 16803) >+++ trunk/reactos/w32api/include/winnt.h 2005-07-27 16:55:40 UTC (rev 16804) >@@ -34,6 +34,7 @@ > > extern "C" { > #endif > > > >+#include <ctype.h> > > > #include <winerror.h> > > #ifndef RC_INVOKED > > Hi, this changing is wrong (and some other with ctype.h). You can't include ctype.h from mingw for optimized builds (DBG = 0), because ctype.h from mingw needs to import msvcrt.dll. - Hartmut

19 years, 10 months

2
1
0 0

Blockers...

by Alex Ionescu

Hi, Here is a current update on the 0.2.7 blockers...if you can help, please DO! BUG: - Green icon in run dialog REGRESSION IDENTIFIED: Yes. By WaxDragon. Regression due to BUILD. CAUSE: Incorrect icon was added to resource file. FIXED: Yes. Fix needs to be merged into 0.2.7 branch. ------------------- BUG: - Common Dialog Control Broken for File/Save. REGRESSION IDENTIFIED: Yes. By WaxDragon. Regression due to 15669. CAUSE: Building shell32 as ANSI causes this problem. Building it as UNICODE however breaks the My computer dialog. Shell32 should be built as Unicode, and the My computer dialog should appear when double-clicked. So this bug needs to be fixed. ---------------------- BUG: - If you use the arrow keys in the explorer start menu to expand an entry, you cannot use them anymore to go up and down. No further information has been researched yet. Martin, explorer is your baby, and I'm sure is an easy fix...it doesnt' happen with the right-click context menu on the desktop, so maybe this is localized to some bug in your start menu code? --------------------- BUG: - If you right-click on the desktop to show the context menu, then right-click again, then left-click (or other similar combinations), your next right-click is not registered anymore. No further information is available, although I belive hpoussin said the problem is above win32k. I haven't heard from tinus in a long time, but i8042prt might be where this problem resides. ------------------- BUG: - Several applications have regressed due to "memory corruption" and a bugcheck related to NtGdiRealizePallette. More information is on the Bugzilla DB, but it's down atm. I have heard reports that the error always happened before, but wasn't seen because red zone pool protection was disabled. In any case, it breaks a large number of apps. -------------------- BUG: - AllocConsole failure in 1st-stage setup on Dell Laptops (and maybe others). REGRESSION IDENTIFIED: Yes. By BrandonTurner. A regression range has been identified and 3 key builds are being tested to find the actual regression. Best Regards, Alex Ionescu

19 years, 10 months

21
36
0 0

Re: [ros-svn] [gdalsnes] 16793: my 1st

by Alex Ionescu

gdalsnes(a)svn.reactos.com wrote: >my 1st > > >Added files: >branches/hardons1stbranch/ > >Updated files: >branches/hardons1stbranch/kapi.h >branches/hardons1stbranch/ntuser.h > >Deleted files: >branches/hardons1stbranch/debug.h >branches/hardons1stbranch/debug1.h > > > Hi, I thought our pre-established branching rules recommend using an actual meaningful branch name? Not a generic user branch, but a feature branch. Best regards, Alex Ionescu

19 years, 10 months

1
0
0 0

RE: [ros-svn] [gdalsnes] 16793: my 1st

by Casper Hornstrup

Can't you rename it to something that reflects its purpose? Casper > -----Original Message----- > From: ros-svn-bounces(a)reactos.com [mailto:ros-svn-bounces@reactos.com] On Behalf Of > gdalsnes(a)svn.reactos.com > Sent: 27. juli 2005 13:07 > To: ros-svn(a)reactos.com > Subject: [ros-svn] [gdalsnes] 16793: my 1st > > my 1st > > > Added files: > branches/hardons1stbranch/ > > Updated files: > branches/hardons1stbranch/kapi.h > branches/hardons1stbranch/ntuser.h > > Deleted files: > branches/hardons1stbranch/debug.h > branches/hardons1stbranch/debug1.h > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-svn

19 years, 10 months

2
1
0 0

Re: [ros-svn] [ion] 16727: - Message Queue Fix, resolves a number of application regressions (Total Commander works again, for example). Patch by Hartmut Birr. To be commited into 0.2.7 after more testing.

by Hartmut Birr

ion(a)svn.reactos.com wrote: > - Message Queue Fix, resolves a number of application regressions (Total Commander works again, for example). Patch by Hartmut Birr. To be commited into 0.2.7 after more testing. > > >Updated files: >trunk/reactos/subsys/win32k/ntuser/window.c > > > Hi, this fix wasn't for commiting, because it doesn't solve the real problem. The destroying of the message queues is intitiated by calling Win32kThreadCallback which calls MsqDestroyMessageQueue. After this call, it shouldn't exist anymore a window for this thread. - Hartmut

19 years, 10 months

2
1
0 0

Re: [ros-svn] [hbirr] 16758: Lock the handle table if we trying to get a pointer from a handle.

by Thomas Weidenmueller

hbirr(a)svn.reactos.com wrote: > Lock the handle table if we trying to get a pointer from a handle. These changes are incorrect. Please revert them. Actually, a handle lookup requires _no_ locks at all. If you don't believe me, read up Windows Internals (4th Edition). The algorithms to allocate subtables are implemented in such a way that it is impossible to page fault on a lookup. However, it is not allowed to do a lookup in a table unless attached to the process that owns it (except it is a global handle table). Best Regards, Thomas

19 years, 10 months

1
0
0 0

Mozilla Embedded locks in ROS r16740

by reactos

Hello all devs, I am running Mozilla-Embedded (same as BartPE) because I can not get the Mozilla Controll to work, usually this is alright, but since some weeks ago Moz-Embedded locks the computer after the shell says "You're embedded man..." and before the mainwindow starts. It usually took a long time for the mainwindow to start, but it used to work, and I think it takes aproximately the same time for the mouse (and the rest of the system) to lock in r16740. I do not get any error-messages, someone with debugging skills has to look at this. Mozilla embedded can be found here: http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.6a/mozilla… Yours sincerely, Jaix Bly

19 years, 10 months

1
0
0 0

Re: [ros-diffs] [hbirr] 16714: - Removed R_EXTRA_STACK because R_EXTRA_STACK and R_STACK must have the same size.

by Royce Mitchell III

hbirr(a)svn.reactos.com wrote: >- Initialized an allocated block completely before release the lock. > >@@ -719,9 +725,9 @@ > > > { > if ( (NewBlock = RQueRemove ( &pool->Que[que][align] )) ) > { > > >- R_RELEASE_MUTEX(pool); > > > RiUsedInit ( NewBlock, Tag ); > RiUsedInitRedZone ( NewBlock, NumberOfBytes ); > > >+ R_RELEASE_MUTEX(pool); > > > return RHdrToBody(NewBlock); > } > queBytes = 16 << que; >@@ -865,11 +871,10 @@ > > > NewBlock = (PR_USED)BestBlock; > RiUsedInit ( NewBlock, Tag ); > > > >- R_RELEASE_MUTEX(pool); >- > > > /* RtlZeroMemory(RHdrToBody(NewBlock), NumberOfBytes);*/ > > RiUsedInitRedZone ( NewBlock, NumberOfBytes ); > > >+ R_RELEASE_MUTEX(pool); > > > > return RHdrToBody(NewBlock); > } > > Hartmut, If you don't mind, I'm curious how this was causing a problem, the stuff that was being initialized outside of the lock shouldn't (in my feeble mind) have been "visible" upon reentry until this block is freed again. Thanks, Royce

19 years, 10 months

2
1
0 0

win32k message queue problem

by Hartmut Birr

Hi, it seems there exist a problem with the message queues. If a process is terminated (killed) from outside, the thread message queue is deleted before the last window is deleted. If there is a message (key or mouse) for this window, the window does access the already freed message queue. This will crash the system. Possible it is related to the paged pool memory corruption bug. I've a (dirty) fix for this problem. - Hartmut Index: subsys/win32k/ntuser/window.c =================================================================== --- subsys/win32k/ntuser/window.c (Revision 16707) +++ subsys/win32k/ntuser/window.c (Arbeitskopie) @@ -1577,6 +1577,7 @@ IntSetMenu(WindowObject, hMenu, &MenuChanged); } WindowObject->MessageQueue = PsGetWin32Thread()->MessageQueue; + IntReferenceMessageQueue(WindowObject->MessageQueue); WindowObject->Parent = (ParentWindow ? ParentWindow->Self : NULL); if((OwnerWindow = IntGetWindowObject(OwnerWindowHandle))) { @@ -2180,7 +2181,7 @@ if (Window->MessageQueue->CaptureWindow == Window->Self) Window->MessageQueue->CaptureWindow = NULL; IntUnLockMessageQueue(Window->MessageQueue); - + IntDereferenceMessageQueue(Window->MessageQueue); /* Call hooks */ #if 0 /* FIXME */ if (HOOK_CallHooks(WH_CBT, HCBT_DESTROYWND, (WPARAM) hwnd, 0, TRUE))

19 years, 10 months

2
2
0 0

Off Topic: Programming Salaries...

by Rick Langschultz

Hey all, I am hiring an entry level web programmer for the winter and would like to know what you would suggest to be a good starting salary. We are a small company that deals with serving users with portal services, such as database portals, collaboration portals, e-learning portals, web services, and simple PHP + MySQL websites. What would you want to be paid? Please be reasonable cause I am going to base someones salary on these statistics. Also please only respond directly to me, not to this list. No use clogging it up. Thanks, Rick Langschultz

19 years, 10 months

1
0
0 0

ReactOS crash on vmware 4.5 when usb controller is enabled .

by Saveliy Tretiakov

(ntoskrnl\ke\main.c:284) --------------------------------------------------------------- (ntoskrnl\ke\main.c:285) ReactOS 0.3-SVN (Build 20050723-r16704) Used memory 65536Kb (ntoskrnl\mm\mminit.c:375) Kernel Stack Limits. InitTop = 0x800f5000, Init = 0x800f2000 (ntoskrnl\mm\mm.c:283) No current process (ntoskrnl\io\pnpmgr.c:1749) Initialization of service vmx_svga failed (Status c0000001) (ntoskrnl\ldr\loader.c:315) Could not open module file: \SystemRoot\System32\DRIVERS\usbuhci.sys (ntoskrnl\io\pnpmgr.c:1749) Initialization of service usbuhci failed (Status c0000001) (ntoskrnl\io\pnpmgr.c:1749) Initialization of service vmx_svga failed (Status c0000001) (ntoskrnl\ldr\loader.c:315) Could not open module file: \SystemRoot\System32\DRIVERS\usbuhci.sys (ntoskrnl\io\pnpmgr.c:1749) Initialization of service usbuhci failed (Status c0000001) (ntoskrnl\ldr\loader.c:315) Could not open module file: \SystemRoot\system32\drivers\ne2000.sys (ntoskrnl\io\pnpmgr.c:1749) Initialization of service Ne2000 failed (Status c0000001) (ntoskrnl\ldr\loader.c:315) Could not open module file: \SystemRoot\system32\drivers\i8042prt.sys (ntoskrnl\io\pnpmgr.c:1749) Initialization of service i8042prt failed (Status c0000001) (ntoskrnl\ldr\loader.c:315) Could not open module file: \SystemRoot\system32\drivers\i8042prt.sys (ntoskrnl\io\pnpmgr.c:1749) Initialization of service i8042prt failed (Status c0000001) (ntoskrnl\io\pnpmgr.c:1749) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1749) Initialization of service serial failed (Status c0000034) (drivers\input\i8042prt\registry.c:215) Can't read registry: c0000034 (drivers\input\i8042prt\registry.c:226) Manually set defaults (drivers\input\i8042prt\registry.c:215) Can't read registry: c0000034 (drivers\input\i8042prt\registry.c:226) Manually set defaults (drivers\input\i8042prt\i8042prt.c:570) Basic keyboard detection failed: c00000b5 (ntoskrnl\io\pnpmgr.c:1749) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1749) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1749) Initialization of service vmx_svga failed (Status c0000001) (drivers\usb\cromwell\uhci\fdo.c:293) UHCI: unknown minor function 0x8 (drivers\usb\cromwell\sys\linuxwrapper.c:466) IoGetDmaAdapter done 0x8CD02938, mapRegisterCount=2 (drivers\usb\cromwell\uhci\uhci-hcd.c:2556) INF: drivers\usb\cromwell\uhci\uhci-hcd.c: USB Universal Host Controller Interface driver v2.1 (drivers\usb\cromwell\core\hcd-pci.c:74) usbcore: usb_hcd_pci_probe() called (drivers\usb\cromwell\sys\linuxwrapper.c:201) driver_register 0: 9d0070b8 9d0008a4(drivers\usb\cromwell\core\usb.c:164) INF: drivers\usb\cromwell\core\usb.c: registered new driver hub (drivers\usb\cromwell\sys\linuxwrapper.c:137) usbcore: Created system thread 60 (drivers\usb\cromwell\sys\linuxwrapper.c:201) driver_register 1: 9d0070e0 9d000890(drivers\usb\cromwell\core\hcd-pci.c:74) usbcore: usb_hcd_pci_probe() called (drivers\usb\cromwell\core\/../linux/pci_hal.c:13) pci_enable_device() called... (drivers\usb\cromwell\core\/../linux/pci_hal.c:44) pci_resource_flags() called, x=0x0 (drivers\usb\cromwell\core\/../linux/pci_hal.c:21) pci_resource_start() called, x=0x0 (drivers\usb\cromwell\core\/../linux/pci_hal.c:33) pci_resource_len() called, x=0x0 (drivers\usb\cromwell\core\/../linux/pci_hal.c:86) request_region(): addr=0x1060, len=0x20 (drivers\usb\cromwell\core\/../linux/pci_hal.c:58) pci_set_drvdata() called... (drivers\usb\cromwell\core\hcd-pci.c:163) UnivHCI PCI-USB Controller (drivers\usb\cromwell\core\hcd-pci.c:183) irq 9, io base 00001060 (drivers\usb\cromwell\core\hcd.c:678) new USB bus registered, assigned bus number 1 (drivers\usb\cromwell\uhci\/../linux/pci_hal.c:33) pci_resource_len() called, x=0x0 (drivers\usb\cromwell\sys\linuxwrapper.c:249) schedule_timeout: 5 ms (drivers\usb\cromwell\sys\linuxwrapper.c:278) schedule DONE!!!!!! (drivers\usb\cromwell\sys\linuxwrapper.c:249) schedule_timeout: 1 ms (drivers\usb\cromwell\sys\linuxwrapper.c:278) schedule DONE!!!!!! (drivers\usb\cromwell\sys\linuxwrapper.c:795) pci_alloc_consistent() size=8196 (drivers\usb\cromwell\sys\linuxwrapper.c:626) pci_pool_create(): UHCD PCI Slot/uhci_td size 48, 85/page (4096 alloc) (drivers\usb\cromwell\sys\linuxwrapper.c:626) pci_pool_create(): UHCD PCI Slot/uhci_qh size 48, 85/page (4096 alloc) (drivers\usb\cromwell\uhci\uhci-hcd.c:2264) INF: drivers\usb\cromwell\uhci\uhci-hcd.c: detected 2 ports (drivers\usb\cromwell\sys\linuxwrapper.c:656) pci_pool_alloc() called, blocks already allocated=0 (drivers\usb\cromwell\sys\linuxwrapper.c:656) pci_pool_alloc() called, blocks already allocated=0 KeBugCheckWithTf at ntoskrnl\ke\catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0xc0000005,0x80059827,0x00000000,0x0000000b) *** ntoskrnl.exe - Address 0x80059827 base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:80059827 <ntoskrnl.exe:59827 (ntoskrnl/mm/marea.c:86 (MmIterateNextNode))> cr2 b cr3 22000 Proc: 8050a7d8 Pid: 4 <System> Thrd: 8050b1d0 Tid: 0 DS 10 ES 10 FS 30 GS 10 EAX: ffffffff EBX: 80699640 ECX: 800ef1a0 EDX: 9cf67fff EBP: 800f477c ESI: 00000000 ESP: 800f4700 EDI: 00076514 EFLAGS: 00210286 kESP 800f4700 kernel stack base 800f2000 Frames: <ntoskrnl.exe:59e59 (ntoskrnl/mm/marea.c:505 (MmFindGapBottomUp))> <ntoskrnl.exe:5a0b9 (ntoskrnl/mm/marea.c:638 (MmFindGap))> <ntoskrnl.exe:5a578 (ntoskrnl/mm/marea.c:957 (MmCreateMemoryArea))> <ntoskrnl.exe:54be5 (ntoskrnl/mm/cont.c:60 (MmAllocateContiguousAlignedMemory))> <hal.dll:2681 (hal/halx86/generic/dma.c:64 (HalAllocateCommonBuffer))> <ntoskrnl.exe:4302a (ntoskrnl/io/pnpdma.c:46 (IopAllocateCommonBuffer))> <usbuhci.sys:8eb3 (drivers/usb/cromwell/sys/linuxwrapper.c:663 (my_pci_pool_alloc))> <usbuhci.sys:3f2f (drivers/usb/cromwell/uhci/uhci-hcd.c:313 (uhci_alloc_qh))> <usbuhci.sys:7897 (drivers/usb/cromwell/uhci/uhci-hcd.c:2289 (uhci_start))> <usbcore.sys:45b3 (drivers/usb/cromwell/core/hcd-pci.c:193 (usb_hcd_pci_probe))> <usbuhci.sys:1202 (drivers/usb/cromwell/uhci/fdo.c:56 (InitLinuxWrapper))> <usbuhci.sys:152e (drivers/usb/cromwell/uhci/fdo.c:192 (UhciFdoStartDevice))> <usbuhci.sys:1627 (drivers/usb/cromwell/uhci/fdo.c:243 (UhciPnpFdo))> <usbuhci.sys:2a74 (drivers/usb/cromwell/uhci/uhci.c:269 (DispatchPnp))> <ntoskrnl.exe:414ff (ntoskrnl/io/irp.c:1080 (IofCallDriver))> <ntoskrnl.exe:4409b (ntoskrnl/io/pnpmgr.c:636 (IopInitiatePnpIrp))> <ntoskrnl.exe:30894 (ntoskrnl/io/device.c:145 (IopStartDevice))> <ntoskrnl.exe:45738 (ntoskrnl/io/pnpmgr.c:1733 (IopActionInitChildServices))> <ntoskrnl.exe:457cb (ntoskrnl/io/pnpmgr.c:1773 (IopActionInitAllServices))> <ntoskrnl.exe:44110 (ntoskrnl/io/pnpmgr.c:666 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:44143 (ntoskrnl/io/pnpmgr.c:680 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:44143 (ntoskrnl/io/pnpmgr.c:680 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:44186 (ntoskrnl/io/pnpmgr.c:706 (IopTraverseDeviceTree))> <ntoskrnl.exe:45834 (ntoskrnl/io/pnpmgr.c:1833 (IopInitializePnpServices))> <800B7BC0> <800B5428> <ntoskrnl.exe:6456 (ntoskrnl/ke/main.c:95 (KiSystemStartup))> <800B384E> <0> KeBugCheckWithTf at ntoskrnl\ke\catch.c:228 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0x80000003,0x80091527,0x00000000,0x00000000) *** ntoskrnl.exe - Address 0x80091527 base at 0x80000000, DateStamp 0x0

19 years, 10 months

2
1
0 0

services in livecd

by Saveliy Tretiakov

I found that SCM is not started in livecd. This is wrong imho (I use livecd to debug ROS and I need SCM). This small patch will fix this. Index: winlogon.c =================================================================== --- winlogon.c (revision 16707) +++ winlogon.c (working copy) @@ -593,6 +593,8 @@ DbgPrint("WL: Cannot switch to Winlogon desktop (0x%X)\n", GetLastError()); } + InitServices(); + /* Check for pending setup */ if (GetSetupType () != 0) { @@ -616,8 +618,6 @@ return 2; } - InitServices(); - #if 0 /* real winlogon uses "Winlogon" */ RtlInitUnicodeString((PUNICODE_STRING)&ProcessName, L"Winlogon");

19 years, 10 months

1
0
0 0

RE: [ros-dev] Re: Reactos.com problems

by Murphy, Ged (Bolton)

Agreed. This is a perfect opportunity to bring in the new website. -----Original Message----- From: mf [mailto:mf@mufunyo.net] Sent: 23 July 2005 11:27 To: ros-dev(a)reactos.com Cc: ros-general(a)reactos.com Subject: [ros-dev] Re: Reactos.com problems Ge van Geldorp wrote: > For the moment, I've moved the mailing lists to a backup box. I am not > moving the website, since it seems the attack was carried out via the > website (a vulnerability in one of the php script packages we use). > I'll put up a dummy page informing visitors. Am I the only one thinking this is the perfect moment to put up the new static webpage along with the new design *hint hint* ? _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

19 years, 10 months

1
0
0 0

Re: [ros-svn] [ion] 16675: - Freetype Update to 2.1.10. Reduces memory usage, increases speed and fixes drawing bugs.

by Steven Edwards

--- ion(a)svn.reactos.com wrote: > - Freetype Update to 2.1.10. Reduces memory usage, increases speed and fixes drawing bugs. > - Enable Bytecode. Weird_W's fonts finally look humanly readable. Turn it off. ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

19 years, 10 months

8
12
0 0

Re: [ros-svn] [ekohl] 16685: Add parameter checks.

by James Tabor

Hi, ekohl(a)svn.reactos.com wrote: > Add parameter checks. > > > Updated files: > trunk/reactos/lib/setupapi/cfgmgr.c > [CC] lib/setupapi/cfgmgr.c lib/setupapi/cfgmgr.c: In function `CM_Locate_DevNode_ExW': lib/setupapi/cfgmgr.c:991: error: `CM_LOCATE_DEVNODE_BITS' undeclared (first use in this function) lib/setupapi/cfgmgr.c:991: error: (Each undeclared identifier is reported only once lib/setupapi/cfgmgr.c:991: error: for each function it appears in.) make: *** [obj-i386/lib/setupapi/cfgmgr.o] Error 1 I found /w32api/include/ddk/cfgmgr32.h adding <ddk/cfgmgr32.h> did help, but it created more problems. Thanks, James

19 years, 10 months

2
1
0 0

Reactos.com unavailable

by Ge van Geldorp

There are strong indications that the reactos.com box got cracked. Unfortunately, I'm on vacation right now and unable to fix things. Since it is causing problems on the network it will be isolated, meaning no network traffic in or out. This will mean the website will go down and the mailing lists will become inactive. I'm sorry about this, but there is not much I can do for the next week. Ge van Geldorp.

19 years, 10 months

1
0
0 0

Re: [ros-svn] [ekohl] 16685: Add parameter checks.

by Thomas Weidenmueller

ekohl(a)svn.reactos.com wrote: > Add parameter checks. > > > Updated files: > trunk/reactos/lib/setupapi/cfgmgr.c > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-svn > lib\setupapi\cfgmgr.c: In function `CM_Locate_DevNode_ExW': lib\setupapi\cfgmgr.c:991: error: `CM_LOCATE_DEVNODE_BITS' undeclared (first use in this function) lib\setupapi\cfgmgr.c:991: error: (Each undeclared identifier is reported only o nce lib\setupapi\cfgmgr.c:991: error: for each function it appears in.) mingw32-make: *** [obj-i386\lib\setupapi\cfgmgr.o] Error 1

19 years, 10 months

1
0
0 0

UsbView Crash

by James Tabor

Hi! This is the latest from USBView. Not to bad. Everyone knows it was working yesterday. I did update the hivesys and reinstalled everything from the current svn, revision 16634. Clean rebuild. Thank, James (drivers/usb/cromwell/uhci/create.c:30) UHCI: IRP_MJ_CREATE (drivers/usb/cromwell/uhci/create.c:41) UHCI: open HCDx successfull (drivers/usb/cromwell/uhci/devctrl.c:76) USB: IRP_MJ_DEVICE_CONTROL dispatch (drivers/usb/cromwell/uhci/devctrl.c:89) USB: IOCTL_GET_HCD_DRIVERKEY_NAME (drivers/usb/cromwell/uhci/devctrl.c:76) USB: IRP_MJ_DEVICE_CONTROL dispatch (drivers/usb/cromwell/uhci/devctrl.c:89) USB: IOCTL_GET_HCD_DRIVERKEY_NAME (drivers/usb/cromwell/uhci/devctrl.c:109) USB: IOCTL_GET_HCD_DRIVERKEY_NAME retu rns 'PCI\VEN_1106&DEV_3104&SUBSYS_73401462&REV_82' Unhandled exception Address: 76673d70 C:\ReactOS\system32\SETUPAPI.dll CS:EIP 1b:76673933 DS 23 ES 23 FS 3b GS 23 EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000 EBP: 0055f9e4 ESI: 00000000 ESP: 0055f9ec EDI: 00000000 EFLAGS: 00000212 Frames: 76660000+13d70 C:\ReactOS\system32\SETUPAPI.dll 400000+3f73 C:\ReactOS\usbview.EXE 400000+1ddc C:\ReactOS\usbview.EXE 400000+1ba1 C:\ReactOS\usbview.EXE 400000+188e C:\ReactOS\usbview.EXE 400000+16d0 C:\ReactOS\usbview.EXE 77e50000+53ece C:\ReactOS\system32\USER32.dll 77e50000+5409a C:\ReactOS\system32\USER32.dll 77e50000+3925f C:\ReactOS\system32\USER32.dll 77e50000+53ece C:\ReactOS\system32\USER32.dll 77e50000+54b7c C:\ReactOS\system32\USER32.dll 77e50000+376df C:\ReactOS\system32\USER32.dll 77e50000+38da3 C:\ReactOS\system32\USER32.dll 77e50000+38ec5 C:\ReactOS\system32\USER32.dll 400000+14a7 C:\ReactOS\usbview.EXE 400000+1417 C:\ReactOS\usbview.EXE 400000+457f C:\ReactOS\usbview.EXE 7c800000+2f105 C:\ReactOS\system32\KERNEL32.dll (drivers/usb/cromwell/uhci/uhci.c:484) UHCI: IRP_MJ_CLEANUP (drivers/usb/cromwell/uhci/close.c:30) UHCI: IRP_MJ_CLOSE

19 years, 11 months

1
1
0 0

Re: [ros-svn] [ion] 16660: Dmitry Philippov <shedon@mail.ru>:

by Hartmut Birr

ion(a)svn.reactos.com wrote: > Dmitry Philippov <shedon(a)mail.ru>: > > - Implemented FindFirstFileExW() and have removed InternalFindFirstFile() in /lib/kernel32/file/find.c, now FindFirstFileA (), FindFirstFileExA () and FindFirstFileW called FindFirstFileExW () > >NOTE: Filip has asked revision "16661" (the next one) to be done by him... sorry if this sounds silly, but please respect his wish :) > > >Updated files: >trunk/reactos/lib/kernel32/file/find.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > > > The implemention of FindFirstFileExW is very buggy. On errors, the allocated buffers are not cleanup correctly. The fourth parameter is wrong in the call to RtlDosPathNameToNtPathName_U. It isn't possible to cast a unicode string to a directory structure. The using of the results from the call to RtlDosPathNameToNtPathName_U is wrong. The buffer from the returned directory structure isn't always null terminated. - Hartmut

19 years, 11 months

2
1
0 0

RE: [ros-dev] Pending 0.2.7 RC2

by Murphy, Ged (Bolton)

Robert k. <rob(a)koepferl.de> wrote: > Hi, > > since there was just one change to the branch 0.2.7 I did not yet > publish the RC2 version. I decided to wait until monday to publishing > RC2. > It seems RC1 is being forgotten about. I know this has been discussed a few times before, but can we not look into the possibility of branching off for releases in a different way. Although it means changing SVN URL for HEAD, is it not better to follow the path of branching a new HEAD and freezing the current address for the next release. This may help people to remember to concentrate more on bugfixes for the upcoming release and not on implementing new features to HEAD. I'd hate to see another buggy release like 0.2.6, which was possibly a regression on 0.2.5 Ged. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

19 years, 11 months

3
2
0 0

Pending 0.2.7 RC2

by Robert k.

Hi, since there was just one change to the branch 0.2.7 I did not yet publish the RC2 version. I decided to wait until monday to publishing RC2.

19 years, 11 months

9
9
0 0

ReactOS Homepage Design Suggestions (vote soon)

by Klemens Friedl

ReactOS Homepage Design Suggestions: I collected all homepage design suggestions that has been posted to the mailing list(s) and copy&paste it together. I hope this will be useful for the new ReactOS Homepage. If you also have created a design and you are not on this list please write a mail to the mailing list! I will call for a "homepage design vote" soon. All suggestions: Jason Filby http://reactos.com/newsite/reactos_index.html Hi all A new proposed frontpage for reactos.com can be found here: http://reactos.com/newsite/reactos_index.html None of the links go anywhere yet. ezPublish will be phased out and most of the content hosted in a wiki (editable only by people trusted in the project). The wiki/forums/blogs would require a bit of a face-lift so as to look similar. Comments? Cheers Jason http://reactos.com:8080/archives/public/ros-web/2005-March/000050.html Klemens Friedl <frik85> ReactOS design suggestion and "RosCMS" (simple CMS that generate static pages) example. http://frik85.fr.funpic.de/reactos/en/index.htm (HTML version) http://frik85.fr.funpic.de/reactos/xhtml/en/index.html (XHTML version) Original mail from mailing list (June 2005): New ReactOS homepage design suggestion: I created a new ros hp design today. What's your opinion about the design? -> http://frik85.fr.funpic.de/ros_newhp/ Klemens Friedl <frik85> PS: Maybe we can use it (or parts of it). http://reactos.com:8080/archives/public/ros-web/2005-June/000086.html Brandon Turner http://brandonturner.org/ROS/index.html Hey, I like Mikko's design as well as others did i think(?) for the new website. All he had the was picture i think, so i went ahead and made the picture into a website if you were planning on using the design this might save ya some time. http://brandonturner.org/ROS/index.html Brandon http://reactos.com:8080/archives/public/ros-web/2005-May/000083.html Mindflyer's design He took Mikko's design and redesign it. http://www.mufunyo.net/reactos/web/ Hiya, First preview of what's to come: http://www.mufunyo.net/reactos/web Have fun, mf. http://reactos.com:8080/archives/public/ros-web/2005-June/000107.html ScoTTie scotteh at netspace.net.au http://www.wizzer-it.com/scott/reactos/ Hey, Ive played a little bit around with the design you initially did and came up with this http://www.wizzer-it.com/scott/reactos/ it looks Pretty much the same bar some minor alignment changes and some fonts. Basiclly ive just removed all the unneeded nested tables. Ive also Tested it in IE6, Firefox 1.0.4, Opera 8 and Links and it seems to Work fine in all of them. -- ScoTTie http://reactos.com:8080/archives/public/ros-web/2005-June/000098.html jh replies at mrnobody.uklinux.net http://reactos.com:8080/pipermail/ros-web/attachments/20050614/624eb1e9/ros… Hi all, Please find attached a screen shot of a page made entirely without tables. The general style is a combination of frick85 and mf, altered somewhat by me. You will see the link high-light styles for both navigation bar (mouse activated) and page (keyboard activated). Note, that all links can be activated by mouse and keyboard. So jump in, pull it apart and let use all know your opinions. Regards, jh http://reactos.com:8080/archives/public/ros-web/2005-June/000131.html Best regards, Klemens Friedl <frik85> -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl

19 years, 11 months

9
9
0 0

Re: [ros-svn] [navaraf] 16661: Get rid of windows.h include in win32k. Fixes bug #666.

by TwoTailedFox

Hehe... Bug 666 in 16661... OK, I get the Joke ;) On 7/20/05, navaraf(a)svn.reactos.com <navaraf(a)svn.reactos.com> wrote: > Get rid of windows.h include in win32k. Fixes bug #666. > > > Updated files: > trunk/reactos/include/ndk/extypes.h > trunk/reactos/include/ndk/i386/ketypes.h > trunk/reactos/include/subsys/csrss/csrss.h > trunk/reactos/subsys/win32k/eng/xlate.c > trunk/reactos/subsys/win32k/ntuser/misc.c > trunk/reactos/subsys/win32k/ntuser/scrollbar.c > trunk/reactos/subsys/win32k/objects/text.c > trunk/reactos/subsys/win32k/w32k.h > trunk/reactos/w32api/include/basetyps.h > trunk/reactos/w32api/include/ddk/ddrawi.h > trunk/reactos/w32api/include/ddk/ddrawint.h > trunk/reactos/w32api/include/ddraw.h > trunk/reactos/w32api/include/oleacc.h > trunk/reactos/w32api/include/winuser.h > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-svn > -- "I had a handle on life, but then it broke"

19 years, 11 months

2
1
0 0

Re: [ros-svn] [ion] 16649: - Update ASM header file with more offsets.

by James Tabor

Hi! ion(a)svn.reactos.com wrote: > - Update ASM header file with more offsets. > > > Updated files: > trunk/reactos/ntoskrnl/include/internal/asm.h > [PCH] obj-i386/ntoskrnl/include/ntoskrnl.h.gch In file included from ntoskrnl/include/internal/ntoskrnl.h:14, from ntoskrnl/include/ntoskrnl.h:43: ntoskrnl/include/internal/asm.h:132:1: "CONTEXT_FULL" redefined In file included from w32api/include/windef.h:249, from w32api/include/ddk/ntddk.h:35, from ntoskrnl/include/ntoskrnl.h:18: w32api/include/winnt.h:1482:1: this is the location of the previous definition In file included from ntoskrnl/include/internal/ntoskrnl.h:14, from ntoskrnl/include/ntoskrnl.h:43: ntoskrnl/include/internal/asm.h:133:1: "CONTEXT_FLOATING_POINT" redefined In file included from w32api/include/windef.h:249, from w32api/include/ddk/ntddk.h:35, from ntoskrnl/include/ntoskrnl.h:18: w32api/include/winnt.h:1479:1: this is the location of the previous definition make: *** [obj-i386/ntoskrnl/include/ntoskrnl.h.gch] Error 1 Did I miss a memo or should I delete something to make this work? Thanks, James 8^>

19 years, 11 months

1
0
0 0

Re: [ros-svn] [greatlrd] 16563: Change some error msg from ConErr to ConOut for they are being pipe so the behover are equal with ms windows cmd

by Hartmut Birr

greatlrd(a)svn.reactos.com wrote: >Change some error msg from ConErr to ConOut for they are being pipe so the behover are equal with ms windows cmd > > > >Updated files: >trunk/reactos/subsys/system/cmd/error.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > > > Hi, I think this change is wrong (also some parts from 16579). The error messages have always to go to the error output (STD_ERROR_HANDLE). - Hartmut

19 years, 11 months

2
3
0 0

Re: [ros-svn] [ion] 16635: - Fix nasty APC delivery bug (in case a Kernel-Mode Special APC still returned with a Normal Routine, the Normal Routine was called with incorrect values (Special Routines take PVOID* arguments, while Normal Routines do not!))

by Hartmut Birr

ion(a)svn.reactos.com wrote: > - Fix nasty APC delivery bug (in case a Kernel-Mode Special APC still returned with a Normal Routine, the Normal Routine was called with incorrect values (Special Routines take PVOID* arguments, while Normal Routines do not!)) > - Remove APC from list before setting it to non-inserted. > - Do proper thread termination piggybacking; terminate threads in user-mode as Hartmut correctly fixed. > > >Updated files: >trunk/reactos/ntoskrnl/ke/apc.c >trunk/reactos/ntoskrnl/ps/kill.c > > > Hi, I do not agree to this changes. For a non system thread, we use a kernel mode apc first, which uses a second user mode apc. This overhead isn't necessary. For system threads it isn't possible to use a kernel mode apc which calls PspExitThread. A system thread must terminate it self. It is only possible to help by marking a flag, setting an event or unwait the thread. - Hartmut

19 years, 11 months

2
1
0 0

RE: [ros-diffs] [chorns] 16647: Generate RPC interface headers inintermediate directory

by Casper Hornstrup

You need to "del include\idl\*.h" after this change. Casper

19 years, 11 months

2
1
0 0

re: ps/kill.c change

by Alex Ionescu

Hi, Sorry but I accidentally lost 60 emails including the one I'm supposed to reply to. Hartmut, you have done a recent change in kill.c in which you change the APC inside PspTerminateThreadByPointer to a user-mode APC. This is incorrect and I don't understand why it was done... furthermore, I've even documented a source of information which proves my code was correct (on top of the function header), so why did you change it? Best regards, Alex Ionescu

19 years, 11 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