Uhm, yes, specifically, cromwell's usb 2.4/2.5 stack + wrapper lack
synchronization somewheh (AFAIR). I tried to fix all that in the usb 2.6
attempt, however I don't have motivation anymore, since adapting woodhead's
usb stack into reactos, which *just works* :-).
It will be even better when usb storage devices support will be finished
too. And then, with time, we can implement a proper Win2k3 USB drivers
stack, including HID devices.
WBR,
Aleksey.
----- Original Message -----
From: "James Tabor" <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net>
To: "ReactOS Development List" <ros-dev(a)reactos.org>
Sent: Thursday, April 19, 2007 11:44 PM
Subject: Re: [ros-dev] Boot Rev 26382
> Hi!
> Aleksey wrote:
>> I will finally move those cromwell usb drivers somewhere so they won't be
>> installed even by "make install" :-)
>>
>> WBR,
>> Aleksey Bragin.
>
> It's due to the new kernel structure, I would think. If and when I get
> time I can
> check into it. No telling when.
> Thanks,
> James
> OT:
> Did we decide to place RosBE in our svn? Did the question ever come up?
> Thanks,
> James
Do you mean the src code of the RosBE? It should already be there. As for
binaries - as always we put them to sf.net.
WBR,
Aleksey.
I will finally move those cromwell usb drivers somewhere so they won't be
installed even by "make install" :-)
WBR,
Aleksey Bragin.
----- Original Message -----
From: "James Tabor" <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net>
To: "ReactOS Development List" <ros-dev(a)reactos.org>
Sent: Wednesday, April 18, 2007 10:47 PM
Subject: Re: [ros-dev] Boot Rev 26382
> Hi!
> I did get it to boot by removing the usb drivers.
> 8^D
> James
Aleksey Bragin wrote:
---------------------------
That shows you really did not even slightly
investigated how the
website
works. And instead you're proposing a whole workflow
for developers, so
they
mandatory spent a few hours per week maintaining all
the stuff you.
During that 2 years you should have spent just a bit
of time, even 20
minutes, to overview our website and systems we have
there, and another
20
minutes to read online manuals/help for them. Excuses
like "I didn't
have
time" hardly apply here.
-------------------------
-Irony on- I suppouse that copying each individual
resource file, every time it is updated, dont waste
developers time.-Irony off- It is your operating
system, your servers and your time, you can do as you
please.
It is not my intention to propose a whole workflow to
developers, i only sugested an idea for an easy to use
translation tool, noone have to waste time, something
similar to the compilation environments, and the IDEs,
but some people prefer making things by hand in the
command line, but again, is your os and your time, i
will decide what to do with my time and if i can or i
want to use bugzilla.
I feel molested by your tone, i have spent more time
on reactos than what you could imagine, but thats not
the matter, i think this is a good project, with a
great goal, i believe that the easier for everybody to
get involved, the best for the project, and my
sugestion was going in that direction. I have read the
ML for years, and almost never posted a word, i dont
have the skill to help much, but offer what "i can",
you can take it or not.
Regards,
Lucio Diaz.
____________________________________________________________________________________
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
May these VESA drivers be useful for ros testing ?
----- Message transféré ----
De : Jan Jezabek <jezabek(a)poczta.onet.pl>
À : qemu-devel(a)nongnu.org
Envoyé le : Mercredi, 18 Avril 2007, 21h25mn 40s
Objet : [Qemu-devel] Re: QEMU drivers repository
Natalia Portillo wrote:
> Hi all,
> I have collected all drivers I could for GD-5446 in
> http://www.claunia.com/qemu/drivers/index.html
>
Hi,
If you're interested in NT 3.51 you can find a graphics driver here:
http://www.navozhdeniye.narod.ru/vbemp.htm
It's a generic VESA driver, but it was the only one I could find that
supported high resolution true-color display in NT 3.51, so maybe it's
worth to put a link on your page.
As for network - I had a good experience with the Realtek 8029 drivers:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=15&PFi…
WBR,
JJ
Hi Peter,
it's a good idea to post an explanation here (might be someone will edit
this into a page in our wiki).
1. Traditional DPRINT debug printing ("old way"): All source code files have
an #define NDEBUG atop of them, a developer could get a detailed tracing of
function calls inside this src code file. DPRINT1()s are used when that code
branch must always notify a user / developer (examples are: critical error,
not fully implemented branch with a reminder to finish implementation, and
any other kind of a situation which occurs rarely and may have a severe
impact on a system).
2. "Wine-way" of debug print messages. The printing is done using three
macros: TRACE(), WARN(), ERR(). Respectively, TRACE() is the most frequently
printed, WARN() is less frequently, and ERR() is an equivalent of a
DPRINT1() - always printed, in error situations.
In order to enable TRACE() and WARN() debug prints, one must add a #define
YDEBUG to the respective place inside an interesting source code file. (Wine
has a concept of debug channels, which can be turned on and off, however
ReactOS for now does not implement this).
3. Other ways exist, specific for drivers / applications (e.g. for miniport
/ port / class drivers, client drivers usually use their class's driver's
debug print routine, a custom one, having custom severities levels).
4. Newer ways of debug printing (kernel-specific, look for debug channels in
windows 2003, debug printing in Vista, -- OSR magazine had a nice article
about these).
WBR,
Aleksey Bragin.
----- Original Message -----
From: <breakoutbox(a)web.de>
To: <Ros-dev(a)reactos.org>
Sent: Thursday, April 19, 2007 4:21 PM
Subject: [ros-dev] DbgPrint() - DPRINT() - DPRINT1()
> Hello,
>
> can please anybody explain me how You want DbgPrint() - DPRINT() -
> DPRINT1() to be used ?
> I found a lot of DPRINT() _for_example_ in "win32/in32k/objects/dc.c" but
> it is not shown on serial debug (?)
> (and also SOME ot these DPRINT1() .. )
>
> 1)
> If I use DPRINT1() instead, it is always shown.
> If I use DbgPrint() instead, it is only shown when #DEBUG is defined in
> the file + in *.rbuild
> But what's the sense of DPRINT() then ?
> =>
>
> 2)
> 2nd stage: on installing from BootCD I can see serial debug only when I
> select DEBUG from startup options.
> Is this DPRINT1() suppressed when I DON'T select DEBUG ?
>
> 3)
> Why is there not one DbgPrint() in "win32/in32k/objects/dc.c" (and also in
> other files in /DRIVER/ and /NTOSKRNL/ ..) ?
> I now have to change every serial debug output to be able to see anything
> .. ( if You don't explain me ... ;-) )
>
>
> Best regards,
> Peter.
Hello,
can please anybody explain me how You want DbgPrint() - DPRINT() - DPRINT1() to be used ?
I found a lot of DPRINT() _for_example_ in "win32/in32k/objects/dc.c" but it is not shown on serial debug (?)
(and also SOME ot these DPRINT1() .. )
1)
If I use DPRINT1() instead, it is always shown.
If I use DbgPrint() instead, it is only shown when #DEBUG is defined in the file + in *.rbuild
But what's the sense of DPRINT() then ?
=>
2)
2nd stage: on installing from BootCD I can see serial debug only when I select DEBUG from startup options.
Is this DPRINT1() suppressed when I DON'T select DEBUG ?
3)
Why is there not one DbgPrint() in "win32/in32k/objects/dc.c" (and also in other files in /DRIVER/ and /NTOSKRNL/ ..) ?
I now have to change every serial debug output to be able to see anything .. ( if You don't explain me ... ;-) )
Best regards,
Peter.
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
----- Original Message -----
From: "Lucio Diaz" <reactos_translate(a)yahoo.es>
To: <ros-dev(a)reactos.org>
Sent: Wednesday, April 18, 2007 11:08 PM
Subject: Re: [ros-dev] Ros-dev Digest, Vol 32, Issue 12
> -Irony on- I suppouse that copying each individual
> resource file, every time it is updated, dont waste
> developers time.-Irony off-
I don't want to disappoint you even more, but there is a whole concept of a
so-called patches (or diffs), which are the thing to be placed in bugzilla,
not whole files.
I suggest some investigation in this area, like
http://en.wikipedia.org/wiki/Patch_%28Unix%29 (it's automated on win32 using
TortoiseSVN for example, in GUI mode, etc). And in general about version
control systems, bug tracking systems, changesets, and other related terms.
WBR,
Aleksey Bragin.
Hi!
FYI:
Real hardware boot log,
(ntoskrnl\kd\kdio.c:193) -----------------------------------------------------
(ntoskrnl\kd\kdio.c:194) ReactOS 0.4-SVN (Build 20070417-r26382)
(ntoskrnl\kd\kdio.c:195) Command Line: DEBUGPORT=COM1
(ntoskrnl\kd\kdio.c:199) ARC Paths: multi(0)disk(0)rdisk(0)partition(1) \
multi(0)disk(0)rdisk(0)partition(1) \ReactOS\
(ntoskrnl\ke\i386\cpu.c:518) Not handling AMD caches yet
Used memory 1015744Kb
(ntoskrnl\se\semgr.c:36) FIXME: SeAccessCheck has been HACKED to always grant access!
(ntoskrnl\se\semgr.c:37) FIXME: Please fix all the code that doesn't get properrights!
(ntoskrnl\ke\i386\kiinit.c:43) Large Page support detected but not yet taken advantage of!
WARNING: HaliQuerySystemInformation at hal\halx86\generic\sysinfo.c:26 is UNIMPLEMENTED!
(ntoskrnl\ke\i386\patpge.c:62) Advanced Memory features detected but not yet taken advantage of.
(ntoskrnl\ke\i386\mtrr.c:24) Your machine supports MTRR but ReactOS doesn't yet.
0 bytes requested - initiating pool verification
0 bytes requested - initiating pool verification
(ntoskrnl\io\iomgr\iorsrce.c:701) IoReportResourceUsage is unimplemented
(ntoskrnl\io\iomgr\iorsrce.c:701) IoReportResourceUsage is unimplemented
(ntoskrnl\io\iomgr\driver.c:798) Driver 'BUSLOGIC.SYS' load failed, status (c00000c0)
(ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1
MmPageEntireDriver at ntoskrnl\mm\drvlck.c:87 is unimplemented, have a nice day
MmPageEntireDriver at ntoskrnl\mm\drvlck.c:87 is unimplemented, have a nice day
MmPageEntireDriver at ntoskrnl\mm\drvlck.c:87 is unimplemented, have a nice day
(ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 10001
(ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1
(ntoskrnl\vdm\vdmmain.c:42) VME detected but not yet supported
(lib\rtl\registry.c:362) RTL: Expand variables for %SystemRoot%\system32\cmd.exe failed - Status ==
c0000023 Size a8 > 7e <e>
(lib\rtl\registry.c:362) RTL: Expand variables for
%SystemRoot%\bin;%SystemRoot%\system32;%SystemRoot% failed - Status == c0000023 Size f4 > ac <14>
(lib\fslib\vfatlib\vfatlib.c:215) VfatChkdsk() unimplemented!
(lib\rtl\registry.c:362) RTL: Expand variables for %SystemRoot%\system32 failed - Status == c0000023
Size a4 > 7e <6>
(ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff
(ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff
(ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff
(ntoskrnl\se\semgr.c:1161) FIX caller rights (granted 0x8, desired 0x28, generic mapping 80C049E0)!
(dll\win32\iphlpapi\ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034
(dll\win32\iphlpapi\ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034
(ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff
(dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find mxdMessage
(dll\ntdll\ldr\utils.c:2025) Failed to create or open dll section of 'msacm.drv' (Status c0000135)
(dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find auxMessage
(dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find mxdMessage
(dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find midMessage
(dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find widMessage
(dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find wodMessage
(dll\win32\shell32\shellpath.c:1688) Failed to create directory 'L".\\Local Settings\\Temporary
Internet Files"'.
(dll\win32\shell32\shellpath.c:1688) Failed to create directory 'L".\\Local Settings\\History"'.
(dll\win32\shell32\shellpath.c:1688) Failed to create directory 'L".\\Cookies"'.
(dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find mxdMessage
(dll\ntdll\ldr\utils.c:2025) Failed to create or open dll section of 'msacm.drv' (Status c0000135)
(dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find auxMessage
(dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find mxdMessage
(dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find midMessage
(dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find widMessage
(dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find wodMessage
(dll\win32\newdev\newdev.c:680) SetupDiOpenDeviceInfoW() failed with error 0xe000020b (InstanceId
HTREE\ROOT\0)
(dll\win32\newdev\newdev.c:736) Installing PCI BIOS (Root\*PNP0A03\0000)
(dll\win32\newdev\newdev.c:525) Installing driver (Generic system devices): PCIbus
(dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\pci.sys" ->
L"C:\\ReactOS\\System32\\drivers\\pci.sys"
(dll\win32\rpcrt4\ndr_marshall.c:928) unhandled data type=09
(drivers\bus\pci\fdo.c:535) Unknown IOCTL 0xd
(drivers\bus\pci\fdo.c:373) No bus number resource found (bug in acpi.sys?), assuming bus number #0
(0,8D7D0178,36)
(dll\win32\newdev\newdev.c:736) Installing <NULL> (Root\*PNP0F13\0000)
(dll\win32\newdev\newdev.c:525) Installing driver (Standard mice): PS/2 port for PS/2-style mice
(dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\i8042prt.sys" ->
L"C:\\ReactOS\\System32\\drivers\\i8042prt.sys"
(dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\mouclass.sys" ->
L"C:\\ReactOS\\System32\\drivers\\mouclass.sys"
(dll\win32\rpcrt4\ndr_marshall.c:928) unhandled data type=09
(dll\win32\newdev\newdev.c:736) Installing <NULL> (Root\*PNP0303\0000)
(dll\win32\newdev\newdev.c:525) Installing driver (Standard keyboards): IBM PC/AT keyboard
(dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\i8042prt.sys" ->
L"C:\\ReactOS\\System32\\drivers\\i8042prt.sys"
(dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\kbdclass.sys" ->
L"C:\\ReactOS\\System32\\drivers\\kbdclass.sys"
(dll\win32\rpcrt4\ndr_marshall.c:928) unhandled data type=09
(dll\win32\newdev\newdev.c:736) Installing COM1 (Root\*PNP0501\0000)
(dll\win32\newdev\newdev.c:525) Installing driver (Standard ports): Serial communication port
(dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\serial.sys" ->
L"C:\\ReactOS\\System32\\drivers\\serial.sys"
(dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\serenum.sys" ->
L"C:\\ReactOS\\System32\\drivers\\serenum.sys"
(dll\win32\rpcrt4\ndr_marshall.c:928) unhandled data type=09
(dll\win32\rpcrt4\ndr_marshall.c:928) unhandled data type=09
(drivers\serial\serenum\fdo.c:209) IRP_MJ_PNP / unknown minor function 0xd
(drivers\serial\serial\pnp.c:400) Unknown minor function 0xd
(drivers\serial\serial\pnp.c:221) KdComPort: D11025FF=üà <two lines of junk>
Comm dies, it does continue to boot with a BSOD with the usb driver.
Thanks,
James
