Ros-dev

ros-dev@reactos.org

1 participants
5793 discussions

serial.sys
by Rick Parrish 25 Aug '06

25 Aug '06

This email is directed mostly to Herve and anyone else familiar with SERIAL.SYS and how it works. Two years ago I implemented a small (5 kilobyte) WDM driver that "wrapped" SERIAL.SYS. It's an ugly hack that (almost) works. What I did was "hook" the interrupt service routine by directly modifying the IDT. It works most of the time but occassionally I get BSOD (and I don't know why). The driver installed ISR reads the MSR (modem status register) of the UART. The RDTSC instruction is used to generate a timestamp of when the MSR changed. Both pieces of data are stored in a FIFO - on every interrupt. A user mode program can later retrieve the information at regular time intervals. Hint: using the CTS, DCD, and DSR pins on a standard RS232 port, you can create a Poor Man's 3 Channel Logic Analyzer. Other applications include packet radio interface for amateur radio. What I'd like to do is merge the functionality directly into SERIAL.SYS (eg. work with the OS instead of around it). The extra functionality would be exposed through IOCTL or some other means but would not break ordinary serial COMM functionality. Disclaimer: I'm not a veteran author of kernel mode drivers. This is a relatively obscure application so if you want to reply off-list, that's perfectly fine by me. Here are my questions: 1. how robust is the current SERIAL.SYS driver (I see a few "FIXME"s in the comments) ? 2. does ReactOS support or require code-signing of drivers? (probably not yet) 3. Can I run the "Genuine" Reactos SERIAL.SYS on "Genuine" Windows 2K/XP? I think so (setting WFP aside). 4. is anyone in the ReactOS community interested in such a driver extension as described above? (probably not) Also, if anyone would like to see the logic analyzer program and related driver - please send me an email. Regards, Rick

3 3

Re: [ros-dev] [ros-diffs] [gedmurphy] 23696: add an 'uptime' command. Available in either Windows or Linux output. (defaulted to Windows)
by Michele Cicciotti [Khamsa S.A.] 25 Aug '06

25 Aug '06

Alex Ionescu wrote: > Please don't add 3rd-party utilities to the tree. Such applications need to go in ros-apps. Base is only for BASE applications. "uptime" isn't. > besides, we already have one. I wrote it. It's called tickcount

1 0

Re: [ros-dev] [ros-diffs] [gedmurphy] 23696: add an 'uptime' command. Available in either Windows or Linux output. (defaulted to Windows)
by Alex Ionescu 25 Aug '06

25 Aug '06

gedmurphy(a)svn.reactos.org wrote: > Author: gedmurphy > Date: Fri Aug 25 04:33:27 2006 > New Revision: 23696 > > URL: http://svn.reactos.org/svn/reactos?rev=23696&view=rev > Log: > add an 'uptime' command. > Available in either Windows or Linux output. (defaulted to Windows) > Please don't add 3rd-party utilities to the tree. Such applications need to go in ros-apps. Base is only for BASE applications. "uptime" isn't. -- Best regards, Alex Ionescu Project Lead, TinyKRNL Kernel-Mode Software Design Engineer, ReactOS

3 4

Network card crash with Mozilla and Firefox.
by James Tabor 23 Aug '06

23 Aug '06

Hi, I forgot to leave this posted last thursday, @ revision 23605. sorry, James work/ndis/ndis/buffer.c:409)(NdisAllocatePacket) Status (0xA256B780) Packet (0xA256B784) PoolHandle (0x81355000). (drivers/network/ndis/ndis/protocol.c:223)(ProSend) Called. (drivers/network/ndis/ndis/protocol.c:245)(ProSend) acquiring miniport block lock (drivers/network/ndis/ndis/miniport.c:475)(MiniAdapterHasAddress) packet address: 0:c:76:2a:ffffffd8:ffffffc8 adapter address: 0:13:46:ffffffa4:ffffff91:66 (drivers/network/ndis/ndis/protocol.c:309)(ProSend) Not a loopback packet (drivers/network/ndis/ndis/miniport.c:617)(MiniQueueWorkItem) Called. (drivers/network/ndis/ndis/protocol.c:315)(ProSend) Queued a work item and returning (drivers/network/ndis/ndis/miniport.c:672)(MiniDequeueWorkItem) Called. (drivers/network/ndis/ndis/miniport.c:797)(MiniportDpc) Calling miniport's SendPackets handler (drivers/network/ndis/ndis/io.c:89)(ServiceRoutine) Called. Adapter (0x8123A590) (drivers/network/ndis/ndis/io.c:98)(ServiceRoutine) Queueing DPC. (drivers/network/ndis/ndis/io.c:102)(ServiceRoutine) Leaving. (drivers/network/ndis/ndis/miniport.c:808)(MiniportDpc) back from miniport's SendPackets handler (drivers/network/ndis/ndis/io.c:34)(HandleDeferredProcessing) Called. (drivers/network/ndis/ndis/buffer.c:830)(NdisFreePacket) Packet (0x81355370). (drivers/network/ndis/ndis/buffer.c:830)(NdisFreePacket) Packet (0x813553B8). (drivers/network/ndis/ndis/io.c:64)(HandleDeferredProcessing) re-enabling the interrupt (drivers/network/ndis/ndis/io.c:69)(HandleDeferredProcessing) Leaving. (drivers/network/ndis/ndis/io.c:89)(ServiceRoutine) Called. Adapter (0x8123A590) (drivers/network/ndis/ndis/io.c:98)(ServiceRoutine) Queueing DPC. (drivers/network/ndis/ndis/io.c:102)(ServiceRoutine) Leaving. (drivers/network/ndis/ndis/io.c:34)(HandleDeferredProcessing) Called. (drivers/network/ndis/ndis/memory.c:39)(NdisAllocateMemoryWithTag) Called. (drivers/network/ndis/ndis/miniport.c:311)(MiniIndicateReceivePacket) indicating a 60-byte packet (drivers/network/ndis/ndis/miniport.c:237)(MiniIndicateData) XXX (875d1862) 8134bf60 0 8228c1f0 e 8228c1fe 2e 2e XXX (drivers/network/ndis/ndis/buffer.c:409)(NdisAllocatePacket) Status (0xA1745B58) Packet (0xA1745B5C) PoolHandle (0x81355000). (ntoskrnl/ex/work.c:658) Requesting a new thread. CurrentCount: 0. MaxCount: 1 (drivers/network/ndis/ndis/miniport.c:257)(MiniIndicateData) Leaving. (drivers/network/ndis/ndis/memory.c:121)(NdisFreeMemory) Called. (drivers/network/ndis/ndis/io.c:64)(HandleDeferredProcessing) re-enabling the interrupt (drivers/network/ndis/ndis/io.c:69)(HandleDeferredProcessing) Leaving. (ntoskrnl/ex/work.c:658) Requesting a new thread. CurrentCount: 0. MaxCount: 1 (ntoskrnl/ex/work.c:397) EX: Creating new dynamic thread as requested (ntoskrnl/ps/thread.c:503) FIX PS SDs!! (ntoskrnl/ex/work.c:397) EX: Creating new dynamic thread as requested (ntoskrnl/ps/thread.c:503) FIX PS SDs!! (drivers/network/ndis/ndis/buffer.c:830)(NdisFreePacket) Packet (0x81355010). (driver(drivers/network/ndis/ndis/buffer.c:409)(NdisAllocatePacket) Status (0x80D7D9C8) Packet (0x80D7D9CC) PoolHandle (s/network/ndis/ndis/buffer.c:830)(NdisFreePacket) Packet (0x81355058).x81355000). (drivers/network/ndis/ndis/buffer.c:409)(NdisAllocatePacket) Status (0x80D7D964) Packet (0x80D7D968) PoolHandle (0x81355000). (drivers/network/ndis/ndis/protocol.c:223)(ProSend) Called. (drivers/network/ndis/ndis/protocol.c:245)(ProSend) acquiring miniport block lock (drivers/network/ndis/ndis/miniport.c:475)(MiniAdapterHasAddress) packet address : 0:c:76:2a:ffffffd8:ffffffc8 adapter address: 0:13:46:ffffffa4:ffffff91:66 (drivers/network/ndis/ndis/protocol.c:309)(ProSend) Not a loopback packet (drivers/network/ndis/ndis/miniport.c:617)(MiniQueueWorkItem) Called. (drivers/network/ndis/ndis/protocol.c:315)(ProSend) Queued a work item and returning (drivers/network/ndis/ndis/miniport.c:672)(MiniDequeueWorkItem) Called. (drivers/network/ndis/ndis/miniport.c:797)(MiniportDpc) Calling miniport's SendPackets handler (drivers/network/ndis/ndis/io.c:89)(ServiceRoutine) Called. Adapter (0x8123A590) (drivers/network/ndis/ndis/io.c:98)(ServiceRoutine) Queueing DPC. (drivers/network/ndis/ndis/io.c:102)(ServiceRoutine) Leaving. (drivers/network/ndis/ndis/miniport.c:808)(MiniportDpc) back from miniport's SendPackets handler (drivers/network/ndis/ndis/io.c:34)(HandleDeferredProcessing) Called. (drivers/network/ndis/ndis/buffer.c:830)(NdisFreePacket) Packet (0x81355010). (drivers/network/ndis/ndis/buffer.c:830)(NdisFreePacket) Packet (0x81355058). (drivers/network/ndis/ndis/io.c:64)(HandleDeferredProcessing) re-enabling the interrupt (drivers/network/ndis/ndis/io.c:69)(HandleDeferredProcessing) Leaving. (drivers/network/ndis/ndis/buffer.c:830)(NdisFreePacket) Packet (0x81355448). (drivers/network/ndis/ndis/buffer.c:409)(NdisAllocatePacket) Status (0x80D869C8) Packet (0x80D869CC) PoolHandle (0x81355000). (drivers/network/ndis/ndis/buffer.c:409)(NdisAllocatePacket) Status (0x80D86964) Packet (0x80D86968) PoolHandle (0x81355000). (drivers/network/ndis/ndis/protocol.c:223)(ProSend) Called. (drivers/network/ndis/ndis/protocol.c:245)(ProSend) acquiring miniport block lock (drivers/network/ndis/ndis/miniport.c:475)(MiniAdapterHasAddress) packet address: 0:c:76:2a:ffffffd8:ffffffc8 adapter address: 0:13:46:ffffffa4:ffffff91:66 (drivers/network/ndis/ndis/protocol.c:309)(ProSend) Not a loopback packet (drivers/network/ndis/ndis/miniport.c:617)(MiniQueueWorkItem) Called. (drivers/network/ndis/ndis/protocol.c:315)(ProSend) Queued a work item and returning (drivers/network/ndis/ndis/miniport.c:672)(MiniDequeueWorkItem) Called. (drivers/network/ndis/ndis/miniport.c:797)(MiniportDpc) Calling miniport's SendPackets handler (ntoskrnl/mm/mm.c:221) Page fault at high IRQL was 2, address c000009a Entered debugger on last-chance exception (Exception Code: 0xc0000005) (Page Fault) Memory at 0xC000009A could not be written: Page not present. kdb:> bt Eip: <fetnd5.sys:1b8e> Frames: <fetnd5.sys:2aba> <fetnd5.sys:26da> <ndis.sys:77bc (drivers/network/ndis/ndis/miniport.c:805 (MiniportDpc))> <ntoskrnl.exe:2628 (ntoskrnl/ke/dpc.c:558 (KiDispatchInterrupt))> <80550e52> <80550ece> <805511e3> <tcpip.sys:81bd (drivers/network/tcpip/tcpip/lock.c:27 (TcpipReleaseSpinLock))> <tcpip.sys:1f9f (drivers/network/tcpip/datalink/lan.c:688 (LANTransmit))> <tcpip.sys:11fc5 (lib/drivers/ip/network/neighbor.c:46 (NBSendPackets))> <tcpip.sys:12b6f (lib/drivers/ip/network/neighbor.c:467 (NBQueuePacket))> <tcpip.sys:14f0d (lib/drivers/ip/network/transmit.c:71 (IPSendFragment))> <tcpip.sys:15356 (lib/drivers/ip/network/transmit.c:212 (SendFragments))> <tcpip.sys:15573 (lib/drivers/ip/network/transmit.c:254 (IPSendDatagram))> <tcpip.sys:14633 (lib/drivers/ip/transport/tcp/event.c:107 (TCPPacketSend))> <tcpip.sys:231f5 (lib/drivers/oskittcp/oskittcp/ip_output.c:524 (ip_output))> <tcpip.sys:1b5be (lib/drivers/oskittcp/oskittcp/tcp_output.c:735 (tcp_output))> <tcpip.sys:1a544 (lib/drivers/oskittcp/oskittcp/tcp_input.c:1663 (tcp_input))> <tcpip.sys:16354 (lib/drivers/oskittcp/oskittcp/interface.c:426 (OskitTCPReceiveDatagram))> <tcpip.sys:d7e2 (lib/drivers/ip/transport/tcp/tcp.c:327 (TCPReceive))> <tcpip.sys:a467 (include/ddk/ndis.h:157 (IPDispatchProtocol))> --- Press q to abort, any other key to continue --- <tcpip.sys:c6c4 (lib/drivers/ip/network/receive.c:469 (ProcessFragment))> <tcpip.sys:c967 (lib/drivers/ip/network/receive.c:565 (IPv4Receive))> <tcpip.sys:c9d6 (lib/drivers/ip/network/receive.c:608 (IPReceive))> <tcpip.sys:1605 (drivers/network/tcpip/datalink/lan.c:331 (LanReceiveWorker))> <tcpip.sys:25d60 (lib/drivers/chew/workqueue.c:56 (ChewWorkItem))> <ntoskrnl.exe:305d0 (ntoskrnl/io/iomgr/iowork.c:30 (IopWorkItemCallback))> <ntoskrnl.exe:1dee8 (ntoskrnl/ex/work.c:162 (ExpWorkerThreadEntryPoint))> <ntoskrnl.exe:62637 (ntoskrnl/ps/thread.c:134 (PspSystemThreadStartup))> <ntoskrnl.exe:6b6f5 (ntoskrnl/ke/i386/ctxswitch.S:82 (KiThreadStartup))> kdb:>

1 0

Summer of Code, status report
by Michele Cicciotti [Khamsa S.A.] 23 Aug '06

23 Aug '06

And so this year's Summer of Code is over. I am moderately optimistic about the outcome, but it could have gone much better... What's there: * the porting! I gutted rdesktop and isolated the smallest subset possible required for the protocol and nothing else. Then I made it re-entrant, as rdesktop was affected by the "accumulate and fire" anti-pattern, setting function arguments in global variables and preventing multiple instances of the library from running (a no-no for an ActiveX control, and for any library in general. Then, again, rdesktop was no library in the first place) * the porting, part 2. I implemented all the "orders" supported by the RDP protocol in terms of Win32 GDI, meaning the display is fully functional (barring the occasional artifact) * the porting, part 3. I implemented mouse/keyboard input. You can interact with your session. That's it. Basically, the RDP client just... works. That's it * the ActiveX control itself, in its glorious hundreds of methods and properties. By far the hardest part of the project. Friends don't let friends code ActiveX controls without ATL! What's not there: * the effort in learning as quickly as possible the most fucked up component model in the history of computing had by far the largest impact on the project, meaning in practice I was stopped halfway through integrating the *actual* code with the extensive ActiveX dressing. In other words, the code currently in the repository is non-functional. Go back a couple of revisions to skip the ugly ActiveX meatworks and see the working proof-of-concept. My biggest mistake was assuming I could tame the ActiveX beast only armed with a stick * some useless ActiveX glue that does not pertain to the kind of control the RDP client is, but has to be there nonetheless * the redirectors were not ported, and no support yet for virtual channel plug-in DLLs. Not a giant effort, though * the mstsc.exe shell Miscellaneous issues: dependency on OpenSSL. This will be hard to eradicate. CryptoAPI isn't an option, beacuse it was designed primarily for PKI, not random arbitrary encryption protocols. In particular, the following limitations make it unfit for use in the RDP protocol: * each provider only supports a single size for RC4 keys, either 40 or 128 bits. Not a major obstacle, but it gets worse * it cannot import plaintext RC4 session keys, at least not without a convoluted workaround (see <http://support.microsoft.com/kb/228786/en-us>). Still not major, but a little bit worse * it cannot perform RSA encryption without padding, required for the session key exchange protocol. CryptoAPI will always pad the cipher with PKCS #1 padding, limiting the plaintext to 11 bytes less than the key size. No workaround for this Best solution: reimplement the internal cryptography library used by Microsoft (the library exported as SystemFunctionXXX from advapi32.dll), which is what the original client uses Afterword: I'll certainly continue working on this. It felt extremely irritating to be so close to a working implementation and just burning time on a huge glue layer probably larger than the implementation itself. Watch this space for future news on my progress! (not in the immediate future though. I'm still recovering from the trauma of hand-coding an ActiveX control)

1 0

GSoC Status Report
by Pablo 23 Aug '06

23 Aug '06

Hi, Google Summer of Code is is ending, and I'm going to report what I've been doing this last months. (yes I know that is my first status report when all is ending, but as I said to Thomas, i'm little shamed of my English :) but it's my mistake. By the other hand I joined many times on IRC with my mentor, Thomas Weidenmüller, and he teach me, many basic concept about ReactOS and integration between kernel and user mode spaces, he's always been nice and helpful with me, and always ask at my questions, and it's was very appreciated by me. With time I'm learning more and more about ReactOS internal implementations, and the start was a little slow. My coding state was sometimes exceeded by external situations, like Alex's ob* implementation, I wrongly make an update of my tree, and many changes magically coming into my code! then sometimes of no-booting-trunk that annoying someone! then come some cm* issues, well, a joyride of code! well, here is a resume of what I've been doing (and done) in the clipboard: *Implemented the APIs to put and get data into clipboard in this formats: Ansi Text, Oem Text, Unicode Text, Bitmap, DIB and Application specific clipboard formats, with the ability of register new formats. Graphic formats still need some testing. *Implement the capability of Delayed Render Format, is like put a specific format type, but not the data, and then, when some application request this data, in this format, the requested application must render it and put it into the clipboard. * Implement the implicit data format conversions between some types of format, in example: if you put an Ansi text, then you can request a Unicode Text, and the same for graphics. * All the function to work with Formats, (not its data), like registering, counting, enumerating, getting the priority formats, query availability, etc. * Implement the window chaining, of the clipboard's viewers (when a format is getting into clipboard all this windows are notified), add, remove, query windows, in the chain. * Appropriate handling of owner window, that rules the clipboard! *Of course, open, close and empty clipboard functions. *Added many test cases to the regression tests of user32, clipboard area. and More: I worked very hard on shell32.dll to make work cut/copy & paste capabilities on shellfolders of explorer. (not on desktop ): now working! This implementation is indirectly related to clipboard, but is directly related to final user! Now you can copy a file and then paste its link, and create shortcuts of any file (even in desktop, but not from desktop), I don't test make a shortcut of a shortcut! I'm work now on that. This time I worked too on many small patches that I put in bugzilla. Some others patches still here on my working copy. Sorry again for my no communication. If someone want to ask me about this or else, my nick in IRC is P43LOk, I'm going there very often. Best Regards, Pablo

1 0

ReactOS 0.3.0 RC2 Released
by Brandon Turner 23 Aug '06

23 Aug '06

I just released 0.3.0 RC2 to SourceForge and you can download it here: https://sourceforge.net/project/showfiles.php?group_id=6553&package_id=6629 This is our final sanity check before we release the final version. I am planing on uploading the release to to SourceForge on Wednesday night and then Thursday morning will be our official release time. Frik or MGW, will you be able to update the home page on Thursday morning? If not let me know and I can do it if we have a graphic ready. Note to all devs and contributors: We need a change log! I have made a svn log for all commits. It can be found at http://www.brandonturner.org/log.txt . Please let me know if you are going to do your own change log, otherwise I will do a change log for everyone else on Tuesday night, but no promises I will find everything you did. -- Brandon Turner ReactOS Release Engineer Blog: http://www.amateurgramming.com

7 10

[Fwd: Indonesian translation for ReactOS]
by Alex Ionescu 22 Aug '06

22 Aug '06

-- Best regards, Alex Ionescu Project Lead, TinyKRNL Kernel-Mode Software Design Engineer, ReactOS

3 2

Request: SLOC stats of ReactOS 0.0.1.0, 0.1.0, 0.2.0 & 0.3.0
by Klemens Friedl 22 Aug '06

22 Aug '06

Request: SLOC stats of ReactOS 0.0.1.0, 0.1.0, 0.2.0 & 0.3.0 SLOC = source lines of code I would like to compose some neat statistics about ReactOS (for reactos.org) and I need help of people with unix compatible operating systems (because the only reasonable SLOC scan tool "sloccount") isn't available for Win32. If you get it working with Cygwin, CoLinux, etc. under Win32 it's fine too. sloccount: http://www.dwheeler.com/sloccount/ Please scan the source code (export it from svn; don't scan svn dir directly) of 0.0.1.0, 0.1.0, 0.2.0 & 0.3.0 (current 0.3.0 rc3 branch). General information about SLOC: http://en.wikipedia.org/wiki/Source_lines_of_code If you don't want to hassle with svn, then download the following source code archives from sourceforge: 0.0.1.0: http://prdownloads.sourceforge.net/reactos/0010_source.zip 0.1.0: http://prdownloads.sourceforge.net/reactos/0100_source.zip 0.2.0: http://prdownloads.sourceforge.net/reactos/reactos-0.2.0-source.zip 0.3.0 (rc2): http://prdownloads.sourceforge.net/reactos/reactos0.3.0-RC2-src.zip If you think you found a better tool to count SLOC's then share the results too. And please share the results from "sloccount", even someone else already posted stats about the same version. There might be differences in the results and it's better to have more stats of the same version to verify and use average values. Please scan the "reactos" dir (and all it's sub-dirs) and add specific of which version of ReactOS & sloccount you have used to gather the stats. Thanks for your help. Klemens

4 5

About coding style / GNU indent
by Aleksey Bragin 20 Aug '06

20 Aug '06

Hello, I've experimented a little with the DrFred's GNU indent settings, they were good, however I advanced them more and found out almost perfect set of settings which suits our proposed/official coding style (the only debateble part was using TAB vs. SPACEs, but for some areas like ntoskrnl TAB-based indentind is de-facto not used at all). For further info / remaining problems, look to the following URL: http://www.reactos.org/wiki/index.php/GNU_Indent WBR, Aleksey Bragin.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev