Ros-dev

ros-dev@reactos.org

1 participants
5793 discussions

ReactOS cmd.exe
by Klemens Friedl 19 Aug '06

19 Aug '06

If someone has some freetime and want improve cmd.exe, the following website has listed a lof of undocumented commands, flags, tricks, etc. of several win version: http://www.robvanderwoude.com/ (click on batch files in the navigation bar)

2 1

RC3 What?!?
by Brandon Turner 18 Aug '06

18 Aug '06

We are actually going to have an RC3 this release because we got 2 last minute bug fixes and will be adding a wallpaper to the bootcd. It will go out Sunday Aug 18th. This should be the last RC before final. Thanks for you time and understanding! -- Brandon Turner ReactOS Release Engineer Blog: http://www.amateurgramming.com

1 0

[ros-kernel] How do device drivers fit into the project goal
by James Tabor 18 Aug '06

18 Aug '06

-------- Original Message -------- Subject: [ros-kernel] How do device drivers fit into the project goal Resent-Date: Fri, 16 Oct 1998 22:08:57 -0500 Resent-From: ros-kernel(a)sid-dis.com Date: Fri, 16 Oct 1998 20:05:44 -0700 From: rex <rex(a)lvcablemodem.com> Reply-To: <ros-kernel(a)sid-dis.com> To: ros-kernel(a)sid-dis.com <ros-kernel(a)sid-dis.com> In a recent response to a message I posted, dennis mentioned that the goal of the project is to build an OS that gives the user a Win32 compatable environment. He also stated in that message that the guts will not necessarily be the same as WinNT or Win98, insted that might actually work correctly. A while ago a similar discussion came up and it was agreed (or so I remember) that we would try to remain compatable with device drivers so we don't have to reinvent them all. I was reading a status message from Connor and I realized that he has some interesting ideas for building a high performance video subsystem, but my brief glance at his description left me thinking that legacy drivers probably will not plug into it. This does not bother me, however we should discuss this and decide on a clear goal for ReactOS regarding driver compatability. It's my impression that the following statement sums up the goal of the project: ReactOS will be a freely distributable operating system capable of running Win32 applications, that is Win98 and WinNT applications. The main project page states the following: "ReactOS will be a free operating system that can run software and drivers compatible with Windows NT." I hope I'm not stepping on any toes, but I think before Conner builds a fast but not necessarily compatable video system, or Arindam builds a compatable but not necessarily most effecient network subsystem, perhaps we should reaffirm the goal so noone takes the wrong path. Personally, I vote for driver compatability. I think there is enough room internally for improvement over the MS design (though I haven't actually seen it) that we dont need to change the structure of the driver interface. Of course, I haven't yet seen the Network or Video driver interface other than block diagrams and broad overviews. Rex.

4 4

[ros-kernel] Re: How do device drivers fit into the project goal
by James Tabor 18 Aug '06

18 Aug '06

-------- Original Message -------- Subject: [ros-kernel] Re: How do device drivers fit into the project goal Resent-Date: Sat, 17 Oct 1998 03:03:33 -0500 Resent-From: ros-kernel(a)sid-dis.com Date: Sat, 17 Oct 1998 01:03:07 -0700 (PDT) From: Jason Filby <jasonfilby(a)yahoo.com> Reply-To: <ros-kernel(a)sid-dis.com> To: ros-kernel(a)sid-dis.com Hi, ---rex <rex(a)lvcablemodem.com> wrote: >I hope I'm not stepping on any toes, but I think >before Conner builds a fast but not necessarily >compatable video system, or Arindam builds a >compatable but not necessarily most effecient >network subsystem, perhaps we should reaffirm >the goal so noone takes the wrong path. The goal states that WinNT drivers must be compatible with ReactOS. I should be able to take a graphics or network driver that was written for NT and use it with ReactOS. Compatibility is extremely important. That said, ReactOS drivers don't necessarily have to run under NT. See what I'm saying here? We MUST provide the mechanisms for NT drivers to work - but CAN also add additional mechanisms that only ReactOS drivers use so that they perform better. Personally, I'd prefer that the mechanisms that allow NT drivers to run 100% are implemented first -- then we can add our own mechanisms that only drivers written to take advantage of them use. But you don't necessarily have to go in that order. At the end of the day, we'll run drivers for NT perfectly (1st priority) and drivers for ReactOS even better (2nd priority). I don't know if I explain this all clearly enough -- so, if not, just tell me. - Jason Filby _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com

1 0

mkhive changes
by Aleksey Bragin 16 Aug '06

16 Aug '06

Hi, currently head has problems with the registry due to changes in structures which were not replicated in mkhive tool (thanks to a "good" code duplication between them). I'm now porting mkhive to use cmlib's headers so that there is no need to keep the same structure in a few places and forget to change it everywhere. It will be commited in a few hours when I get back. WBR, Aleksey Bragin.

1 1

OpenOffice.org 2.0.3
by David Ianno 15 Aug '06

15 Aug '06

I tried to install OpenOffice.org 2.0.3 using r23543. The installation stopped because of an ASSERT in cmlib. nl\ps\thread.c:503) FIX PS SDs!! (dll\ntdll\ldr\utils.c:1194) LdrGetExportByName(): failed to find FlsAlloc (dll\ntdll\ldr\utils.c:1194) LdrGetExportByName(): failed to find FlsGetValue (dll\ntdll\ldr\utils.c:1194) LdrGetExportByName(): failed to find FlsSetValue (dll\ntdll\ldr\utils.c:1194) LdrGetExportByName(): failed to find FlsFree (ntoskrnl\ps\thread.c:503) FIX PS SDs!! (dll\ntdll\ldr\utils.c:1194) LdrGetExportByName(): failed to find FlsAlloc (dll\ntdll\ldr\utils.c:1194) LdrGetExportByName(): failed to find FlsGetValue (dll\ntdll\ldr\utils.c:1194) LdrGetExportByName(): failed to find FlsSetValue (dll\ntdll\ldr\utils.c:1194) LdrGetExportByName(): failed to find FlsFree (dll\ntdll\ldr\utils.c:1194) LdrGetExportByName(): failed to find FlsAlloc (dll\ntdll\ldr\utils.c:1194) LdrGetExportByName(): failed to find FlsGetValue (dll\ntdll\ldr\utils.c:1194) LdrGetExportByName(): failed to find FlsSetValue (dll\ntdll\ldr\utils.c:1194) LdrGetExportByName(): failed to find FlsFree (ntoskrnl\cm\ntfunc.c:437) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\Classes\MIME\DataBase\Content Type\application/vnd.stardivision.writer"!) (ntoskrnl\cm\ntfunc.c:437) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\Classes\MIME\DataBase\Content Type"!) (ntoskrnl\cm\ntfunc.c:437) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\Classes\MIME\DataBase"!) (ntoskrnl\cm\ntfunc.c:437) NtCreateKey() doesn't create trees! (found '\' in remaining path: "\Classes\MIME"!) Assertion 'CellIndex != HCELL_NULL' failed at lib\cmlib\hivecell.c line 19 Entered debugger on embedded INT3 at 0x0008:0x8007fda0. kdb:> cont Assertion 'CellBlock < RegistryHive->Storage[CellType].BlockListSize' failed at lib\cmlib\hivecell.c line 29 Entered debugger on embedded INT3 at 0x0008:0x8007fda0. kdb:> cont Entered debugger on last-chance exception (Exception Code: 0xc0000005) (Page Fault) Memory at 0x003FFFFC could not be read: Page not present. kdb:> cont KeBugCheckWithTf at ntoskrnl\ke\i386\exp.c:1241 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,0x8007F050,0x00000000,0x003FFFFC) *** ntoskrnl.exe - Address 0x8007F050 base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:8007f050 <ntoskrnl.exe:7f050 (lib/cmlib/hivecell.c:30 (HvGetCell))> cr2 3ffffc cr3 299e000 Proc: 810401e8 Pid: 118 <msiexec.exe> Thrd: 820cb468 Tid: 134 DS 23 ES 23 FS 30 GS 0 EAX: 00000000 EBX: 8d22bd40 ECX: 00000032 EDX: 00000000 EBP: 9e879c98 ESI: 0007ffff ESP: 9e879c14 EDI: 8d22bcd8 EFLAGS: 00010286 kESP 9e879c14 kernel stack base 9e877000 Frames: <ntoskrnl.exe:fe79 (ntoskrnl/cm/regfile.c:1571 (CmiDeleteValueFromKey))> <ntoskrnl.exe:d94e (ntoskrnl/cm/ntfunc.c:2157 (NtDeleteValueKey))> <ntoskrnl.exe:6ec74 (ntoskrnl\ke\i386\trap.s:306 (KiFastCallEntry))> <advapi32.dll:88c0 (dll/win32/advapi32/reg/reg.c:2109 (RegDeleteValueA))> Entered debugger on embedded INT3 at 0x0008:0x8007fda6. kdb:> cont --------------------------------- Do you Yahoo!? Get on board. You're invited to try the new Yahoo! Mail Beta.

2 3

ReactOS 0.3.0 RC2 problems
by Andrew Smith 14 Aug '06

14 Aug '06

Hi, I'm not sure if this is the correct place to post this, if it's not I'm sorry, just let me know where I should post things like this to. Right then, I downloaded the VMware RC2 image and loaded it up in VMware player. Booted fine (and i like the boot time ;-) and thought that I'd try the networking out. I was able to open up ibrowser and download the mozilla control fine and browse like that to a few sites (getfirefox.com, sf.net, 7-zip.org and guildwars.com). I wanted to try out Guild Wars (a DirectX MMORPG, very ambitious I know). I was able to go to the site fine and download the client, however, when I went to download 7-zip I was given a BSoD. I restarted and tried to download firefox instead and install that. The download was fine however part way through the install it just dropped out. I tried again and the same thing happened. I then noticed the 'Get Firefox' link in the start menu, which didn't do anything (just opened the download window and sat there). I looked around the C: drive and noticed that Firefox had installed the exe so I tried to run it but didn't get anything. I closed the 'Get Firefox' window and tried that again, same problem as before, this time though it wouldn't close. Opened up task manager and saw 2 firefox.exe running so I tried to kill them, this didn't worked. Tried to kill 'Get Firefox' process and that worked, but then a few seconds after that I got another BSoD. I've attached the vmware.log in case it's any use. The debug.txt file is empty for some reason, so I've not attached that. I'm going to try a few more things and I'll let you know what happens. If this kind of feedback isn't useful let me know, or let me know where to post it so it can become useful :-) -- Andy Smith - Def since birth

1 0

[ros-diffs] [hpoussin] 23540: Add code to start the screensaver from winlogon
by James Tabor 12 Aug '06

12 Aug '06

Hi, It's worse! > This code should replace the existing one in win32k/csrss, but is not activated (yet) due to some bugs: > - Calling SetWindowsHookEx with WH_KEYBOARD_LL gives a BSOD when pressing a key Not sure,,, The hook code is a Wineie/GvG/w3seek hod podge thingy. > - Time field in PKBDLLHOOKSTRUCT/PMSLLHOOKSTRUCT should be in milliseconds > - Screen saver parameters can't be retrieved with SystemParametersInfoW > - Probably others... In ntuser/message.c & desktop.c, I noticed that the switch code uses a static PW_O InputDesktop. This is used in message.c when looking for broadcasting,, etc. It's indirectly called by IntGetDesktopWindow which returns the active desktop that is stored in InputDesktop. SO,,,,, multi desktops w/o a common root message hook?,,,,,, > > Plus a few less important ones: > - When sending a message with HWND_BROADCAST, the invisible SAS window doesn't get the message In ntuser/message.c, co_IntDoSendMessage doesn't support recursive entry for HWND_BROADCAST. A good example for doing this is UserPostMessage. If it does, I did not see yet. > - When calling (NtUser)SystemParametersInfo, WM_SETTINGSCHANGE message is not sent > - desk.cpl doesn't save (some) screensaver parameters to registry > SendNotifyMessage is UNIMPLEMENTED! Oh the Shock of seeing that! 8^O !NOOOOOOO! Okay, James

1 1

svcctl.idl: Why "Scmr"-prefix?
by Elrond 11 Aug '06

11 Aug '06

Hi, I was looking at svcctl.idl in ros. I wonder, where the "Scmr"-prefix comes from? googling for say "ScmrCloseServiceHandle" gives only results from reactos, nothing else. "CloseServiceHandle" gives lots of results, of course. Was the prefix choosen arbitrarily and could have well been "Ros" instead? Elrond

4 6

(no subject)
by Alex Ionescu 11 Aug '06

11 Aug '06

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

1 1

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