Ros-dev April 2005

ros-dev@reactos.org

62 participants
114 discussions

Re: [ros-svn] [hbirr] 14505: Initialize the maximum length of the device description to allocate more than map register.
by James Tabor 05 Apr '05

05 Apr '05

Hi! hbirr(a)svn.reactos.com wrote: > Initialize the maximum length of the device description to allocate more than map register. > > > > Updated files: > trunk/reactos/drivers/storage/floppy/floppy.c > Does this fix floppy support? I haven't had floppy working for 6+ months! ha! floppy working! James

2 1

Re: [ros-diffs] [hbirr] 14421: - Use IoBuildAsynchronousFsdRequest instead IoBuildSynchronousFsdRequest in NtRead/WriteFile.
by Gunnar Dalsnes 04 Apr '05

04 Apr '05

hbirr(a)svn.reactos.com wrote: > - Use IoBuildAsynchronousFsdRequest instead IoBuildSynchronousFsdRequest in NtRead/WriteFile. > - Guard the calls to IoBuildAsynchronousFsdRequest with an exception frame. > > Modified: trunk/reactos/ntoskrnl/io/rw.c I dont understand these changes... Why did you change from sync. to asycn. version, and whats the point with try/except around IoBuildAsynchronousFsdRequest??? Gunnar

2 3

Re: [ros-dev] isoboot.bin: where is it from?
by Sylvain Petreolle 04 Apr '05

04 Apr '05

http://reactos.com:8080/archives/public/ros-svn/2005-April/002066.html or run "ARCH=i386 make bootcd" --- ea <ea(a)iol.it> wrote: > Hi all, > > I can't build the bootable cd image. > Is it just my local repository broken (14488)? > > --- > 3: directory ./../bootcd/disk\reactos\system32\ > 3: file ./../bootcd/disk\reactos\system32\ntdll.dll > 3: file ./../bootcd/disk\reactos\system32\smss.exe > Can't open ./../bootcd/disk/../isoboot.bin > > make: *** [bootcd_makecd] Error 1 > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev > Kind regards, Usurp (aka Sylvain Petreolle) humans are like computers, yesterday the BIOS was all - today its just a word

2 1

isoboot.bin: where is it from?
by ea 04 Apr '05

04 Apr '05

Hi all, I can't build the bootable cd image. Is it just my local repository broken (14488)? --- 3: directory ./../bootcd/disk\reactos\system32\ 3: file ./../bootcd/disk\reactos\system32\ntdll.dll 3: file ./../bootcd/disk\reactos\system32\smss.exe Can't open ./../bootcd/disk/../isoboot.bin make: *** [bootcd_makecd] Error 1

1 0

RE: [ros-dev] Ros 0.2.6-RC2 on sf.net
by Waldo Alvarez Cañizares 04 Apr '05

04 Apr '05

Hi Robert: Yes 7Zip compresses sometimes (most of the times) more than WinRAR. In fact as far as I know they both use the same algorithm for text compression. 7Zip has 3 compression algorithms so you could try all and see for yourself. It also supports streams so you can compress things from the output of one of the algorithms and make it the input of the other. For example to compress executables you could use jcc and it´s output pass it to LZMA. It also provides larger dictionaries if you want. WinRAR´s maximun size is 4 MB so usually WinRaR files are larger. When it comes about speed WinRAR is faster. But I guess that´s irrelevant right now. On the other side I think that sourceforge someday should be enhanced to give users the option to download the files in the selected format, maybe providing a link to the decompressor. Maybe I fill someday the feature request form for sourceforge It will save us and maybe will save them some time. Best Regards Waldo ________________________________ From: ros-dev-bounces(a)reactos.com on behalf of Robert Köpferl Sent: Sun 4/3/2005 5:08 PM To: ReactOS Development List Subject: Re: [ros-dev] Ros 0.2.6-RC2 on sf.net Having read your comments, I came to this conclusion: I'll have a try with 7zip and if it compresses slightly less or better than rar, I'll use 7zip (because it is free). For a test period I'll provide both, zip and 7zip/rar and the user may decide which one will win. Additionally I'll provide a file 'how to decompress.txt' in every release. Wheras I think, people who come to download an OS know enough to find one theirselves. Making exe-files is still an option but I don't like it. So you have to convince me. _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev

1 0

Invitation
by Robert Köpferl 04 Apr '05

04 Apr '05

Hi, it might seem stupid or girlish, but I want to invite any of you to visit me in Vienna (wien.AT) for a couple of days. I would like to just see some of these people (and of course have freeky kernel talks) who make up this project. Get to know personally. Don't be shy and have a try with my private email. (possibly use gpg/x.509). If you think this Vienna is too far away - maybe next year I live less far away from you.

1 0

NTOSKRNL bugcheck when clicking on "My Computer C disk icon"
by Gge 04 Apr '05

04 Apr '05

With svn 14668 , Ros bugchecks when I click on the "my computer " icon and o then on the "C" disk drive icon as per debug messages below. This is a regression and it is always reproductible . I cannot say exactly when it has been broken. Any idea ? ----------------------------- PM_OPEN_WINDOW: path=C:\ KeBugCheckWithTf at ke/catch.c:237 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 KMODE_EXCEPTION_NOT_HANDLED Technical information: *** STOP: 0x0000001E (0xc0000005,0x8004773e,0x00000000,0x00000006) *** ntoskrnl.exe - Address 0x8004773e base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:8004773e <ntoskrnl.exe:4773e (io/mdl.c:130 (IoFreeMdl))> cr2 6 cr3 d896000 Proc: 80d46990 Pid: f0 <explorer> Thrd: 80d50a68 Tid: f4 DS 10 ES 10 FS 30 GS 23 EAX: 00000000 EBX: 8004635f ECX: 00000003 EDX: 00000002 EBP: a1f76a88 ESI: 007ecdd8 ESP: a1f769d8 EDI: a1f76d74 EFLAGS: 00010282 kESP a1f769d8 kernel stack base a1f74000 Frames: <ntoskrnl.exe:3c7d0 (io/cleanup.c:112 (IoReadWriteCompletion))> <ntoskrnl.exe:3c8e0 (io/cleanup.c:211 (IoSecondStageCompletion))> <ntoskrnl.exe:4694d (io/irp.c:498 (IofCompleteRequest))> <vfatfs.sys:c65c (rw.c:775 (VfatRead))> <vfatfs.sys:dcc9 (misc.c:110 (VfatDispatchRequest))> <vfatfs.sys:de94 (misc.c:168 (VfatBuildRequest))> <ntoskrnl.exe:4627d (io/irp.c:211 (IofCallDriver))> <ntoskrnl.exe:46293 (io/irp.c:226 (IoCallDriver))> <ntoskrnl.exe:4e6b0 (io/rw.c:154 (NtReadFile))> <ntoskrnl.exe:38f2 (C:\DOCUME~1\home\LOCALS~1\Temp/ccucbaaa.s:178 (KiSystemService))> <kernel32.dll:278f6 (file/rw.c:154 (ReadFile))> Reaards Gerard

2 2

Re: [ros-dev] Guess who's back
by Steven Edwards 04 Apr '05

04 Apr '05

Hi, --- Phillip Susi <psusi(a)cfl.rr.com> wrote: > Are you talking about being able to create usable ram disks at runtime > and use them for general file storage instead of holding the system > volume? I don't really see any use for ram disks other than holding the > system volume so the media used to boot the system can be removed. Yes thats the idea. We tend to get requests for one every so often though I don't know what people use them for. There is a example driver with source code on support.microsoft.com that I always point people to. Thanks Steven __________________________________ Yahoo! Messenger Show us what our next emoticon should look like. Join the fun. http://www.advision.webevents.yahoo.com/emoticontest

5 8

Re: [ros-dev] Building Freeloader
by Steven Edwards 03 Apr '05

03 Apr '05

--- Phillip Susi <psusi(a)cfl.rr.com> wrote: > I seem to remember you added a special multiboot header to the kernel > image but it looks to me like ntoskrnl.exe has a standard PE image header. Alex changed this. ntoskrnl now is PE loaded from freeldr. I think it was needed for dynamic ACPI and 3GB support. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Personals - Better first dates. More second dates. http://personals.yahoo.com

3 2

Re: [ros-svn] [hbirr] 14443: - Fixed ExTimerRundown.
by Alex Ionescu 03 Apr '05

03 Apr '05

hbirr(a)svn.reactos.com wrote: >- Fixed ExTimerRundown. > > Hi, Can you please explain some of your changes? You have introduced several changes that I don't understand, such as cancelling the timer's APC without actually making sure that it has an APC associated, as well as slowing down the path and forcing additionnal locking of the DB lock by using KeCancelTimer (which also uselessly checks if the timer is inserted -- we are sure it already is). Apart from that, thanks for fixing the silly bugs! Best regards, Alex Ionescu

3 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev April 2005