I've been trying to sync riched20 for the past hour but am not getting
anywhere.
Our last sync was 0.9.5, but since then quite a bit more code has been
added.
The 2 problematic lines are in 0.9.15, editor.c, lines 1093 and 1912.
They refer to IRichEditOleCallback callbacks in richole.idl, which is
new for us.
I'm not familiar with idl files, but we seem to implement them in
/include/reactos/idl.
I've tried dropping the idl in there, creating the respective .acf and
modding the rbuild file.
However I'm still having problems.
Can anyone shed any light on this?
I've dropped 0.9.15 into our vendor dir, if anyone wants to sync it for us.
It's a straight sync, we have no ROS specific code in this lib.
Ged
Hi all!
This is the hivesys.inf PCNet section. I copied fetnd5a.sys to pcnet.sys.
I can query network properties w/o a crash! All I get is IPHLPAPI.dll need
more work and GetAdapterInfo did not return the expected data.
Bus 0, device 18, function 0, Ven 1106/Dev 3065/class 0200.
Start->Settings->Settings Menu->Network Properties
Select VT6102->Properties, get the VIA PCNet Status Menu, select Properties,
get the VIA PCNet Pro~ Menu, select Internet Protocol (TCP/IP), select
Properties, get the Error menu.
Wow! Did not crash!
Need to check if I'm on the right track here!
Thanks,
James
; ReactOS PCNet NIC driver
; To use the AMD supplied driver change the driver name to pcntn5m.sys
;
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","ErrorControl",0x00010001,0x00000000
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","Group",0x00000000,"NDIS"
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","ImagePath",0x00020000,"system32\drivers\pcnet.sys"
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","Start",0x00010001,0x00000003
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","Type",0x00010001,0x00000001
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet\Enum","0",0x00000000,"PCI\VEN_1106&DEV_3065\0000"
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet\Enum","Count",0x00010001,0x00000001
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet\Enum","NextInstance",0x00010001,0x00000001
HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_10\0000","Service",0x00000000,"PCNet"
HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_10\0000","Class",0x00000000,"Net"
HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_10\0000","ClassGUID",0x00000000,"{4D36E972-E325-11CE-BFC1-08002BE10318}"
HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_10\0000","Driver",0x00000000,"{4D36E972-E325-11CE-BFC1-08002BE10318}\0000"
; Configuration Entries for the PCNet Adapter
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","Characteristics",0x00010001,0x00000000
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","DriverDesc",0x00000000,"VT6102"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ProviderName",0x00000000,"VIA
Tech"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","NetCfgInstanceId",0x00000000,"{RANDOMCFGGUIDFOR_PCNET1}"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000\Linkage","Export",0x00000000,"\Device\PCNet1"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000\Linkage","RootDevice",0x00000000,"PCNet1"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000\Linkage","UpperBind",0x00000000,"Tcpip"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BUS_TO_SCAN",0x00000000,"ALL"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BUSTIMER",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BUSTYPE",0x00000000,"5"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","EXTPHY",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","FDUP",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","LED0",0x00000000,"10000"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","LED1",0x00000000,"10000"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","LED2",0x00000000,"10000"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","LED3",0x00000000,"10000"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","MPMODE",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","TP",0x00000000,"1"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","AdapterCFID",0x00000000,"811929862"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","AdapterType",0x00000000,"5"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","SlotNumber",0x00000000,"8"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BusNumber",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","FunctionNumber",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","EarlyReceive",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","EarlyTransmit",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BurstLength",0x00000000,"1"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ReceiveBurstIndicate",0x00000000,"64"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ReceiveBuffers",0x00000000,"64"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","TransmitBuffers",0x00000000,"32"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ReceiveThreshold",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","TransmitThreshold",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","MapRegisters",0x00000000,"32"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ConnectionType",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ValidatePacketLen",0x00000000,"1"
HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","IPXSPXAutoFrame",0x00000000,"0"
HKLM,"SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{RANDOMCFGGUIDFOR_PCNET1}",,0x00000000,"Network
Adapters"
HKLM,"SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{RANDOMCFGGUIDFOR_PCNET1}\Connection","Name",0x00000000,"VIA
PCNet"
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet1\Parameters\Tcpip","DefaultGateway",0x00010000,"10.65.145.1"
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet1\Parameters\Tcpip","IPAddress",0x00010000,"10.65.145.79"
HKLM,"SYSTEM\CurrentControlSet\Services\PCNet1\Parameters\Tcpip","SubnetMask",0x00010000,"255.255.255.0"
We search an author for our "ReactOS Weekly Newsletter".
History:
Jason Filby had established the ReactOS Weekly Newsletter (called
"ReactOS Weekly") in 1999 as a useful weekly news summary located on
www.reactos.com. In 2000 the newsletter had been discontinued. With
the website redesign in summer 2005, the newsletter came back with
Stuart "TwoTailedFox" Robbins as author.
Requirements:
Here are requirements for an author:
1. Have enough time once a week to write the newsletter text (e.g. every sunday)
2. Be good in english language
3. Understand our technlogy (svn, reactos, windows nt, win32, kernel,
drivers, apps, etc.)
4. Be in frequent contact with the ReactOS developer, and come in our
IRC channels too (because mailing list traffic may be sometimes slow)
5. HTML knowledge is not required but an advantage
Goal:
The "ReactOS Weekly Newsletter" should be weekly (as the name implies)
and sum up the ongoing mailing list discussions as well as irc
conversations.
Additionally it should contain ReactOS news, like new releases.
>From time to time interviews, reviews (of apps compatibility and
reactos functions and releases) and maybe audio-podcasts, etc. would
be great too.
The layout of the newsletter issue page can be the same as the latest
one (e.g. http://www.reactos.org/xhtml/en/newsletter_11.html), similar
as WineHQ's one, or different.
Previous newsletters - links:
10/2005 - 02/2005:
http://www.reactos.org/?page=newsletters
1999 - 2000:
http://web.archive.org/web/20000522174140/reactos.com/public/weekly.html
WineHQ'S newsletters:
http://www.winehq.com/?issue=back
Mailing List Information:
http://www.reactos.org/?page=community_mailinglists
IRC Channel Information:
http://www.reactos.org/?page=community_irc
So... if this sounds like something you would like to do, please reply
to this mailing list email explaining why you you think you would be a
good newsletter author.
Klemens Friedl
Alex Ionescu wrote:
> In defense to Hervé, you actually need to clean *TWICE*. That's right,
> you must write:
> make intrlck_clean && make intrlck_clean & make ntdll_clean & make
> ntdll_install.
What does running 'make intrlck_clean' do the second time which it doesn't
do the first time round?
************************************************************************
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
Hi all!
When the install popup for the disk controller is displayed. I can install from
and select everything but NEXT!
Select *Next* this will happen, (tested this 4 times now, same thing)
(dll/win32/newdev/newdev.c:745) Installing Other ACPI device (ACPI\PNP0C04\1&7313ac9&0000)
(dll/win32/newdev/newdev.c:466) Include removable devices: no
(dll/win32/newdev/newdev.c:467) Include custom path : no
(dll/win32/newdev/newdev.c:534) Installing driver (Generic system devices): Math coprocessor
(dll/win32/newdev/newdev.c:745) Installing Disk controller (ACPI\PNP0700\1&7313ac9&0000)
(dll/win32/newdev/newdev.c:466) Include removable devices: no
(dll/win32/newdev/newdev.c:467) Include custom path : no
(dll/win32/shell32/classes.c:381) HCR_GetFolderAttributes should be called for simple PIDL's only!
(dll/win32/shell32/shellpath.c:1688) Failed to create directory 'L".\\Desktop"'.
(dll/win32/newdev/newdev.c:466) Include removable devices: yes
(dll/win32/newdev/newdev.c:467) Include custom path : no
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,0x80033CF6,0x00000000,0x00000030)
*** ntoskrnl.exe - Address 0x80033CF6 base at 0x80000000, DateStamp 0x0
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:80033cf6 <ntoskrnl.exe:33cf6 (ntoskrnl/io/file.c:970 (IoCreateFile))>
cr2 30 cr3 3be68000 Proc: 8178f328 Pid: d8 <umpnpmgr.exe> Thrd: 817a4558 Tid: e8
DS 23 ES 23 FS 30 GS 0
EAX: 00000000 EBX: 9fa43c34 ECX: 000023be
EDX: 81f5d6e4 EBP: 9fa43cf0 ESI: 00000000 ESP: 9fa43b50
EDI: 00000000 EFLAGS: 00010296 kESP 9fa43b50 kernel stack base 9fa3e000
Frames:
<ntoskrnl.exe:3459a (ntoskrnl/io/file.c:1527 (NtCreateFile))>
<ntoskrnl.exe:66657 (ntoskrnl/ke/i386/trap.s:306 (KiFastCallEntry))>
<KERNEL32.dll:9c6f (dll/win32/kernel32/file/volume.c:57 (InternalOpenDirW))>
I think my hardware is not ReactOS compatible.
Thanks,
James
Hi,
Annoyed by the ever-growing blame on my patches as well as the
continuing lack of attention regarding the SESSION_5 BSOD, I've taken
the liberty to momentarily put on hold my current paid work and take a
look at the issue (which thankfully only took 30 minutes).
As I suspected, it has absolutely nothing to do with any Ob stuff and is
the result of ntdll being messed up after the recent changes to
lib\intrlck. Revert them, clean interlck/ntdll, rebuild, and voila,
you're back to a working ROS.
In defense to Hervé, you actually need to clean *TWICE*. That's right,
you must write:
make intrlck_clean && make intrlck_clean & make ntdll_clean & make
ntdll_install.
It is *NOT* enough to merely write ntdll_clean, either.
I'm going to assume that Hervé only cleaned interlck once (as anyone
would normally do) and kept using the "correct" library. As soon as he
(and others) built a new copy of the tree (probably around one of my
patches), the interlck lib now got cleaned twice and the broken one
started coming into use. Score one for my complaints against rbuild.
If I could give some advice, next time, spend less time assigning blame
on me, and actually try to find the bug (yes, this sounds arrogant, but
it DOES get annoying to be the poster boy for boot BSODs. The last one I
caused was over 12 months ago).
Best regards,
Alex Ionescu
Hi,
With ROS_LEAN_AND_MEAN and DBG = 1, with all drivers and the bells and
whistles, a boot to NCLI with 8MB gave me a working system with still
2MB to spare (perhaps for a native FTP server or other application).
If I remove the network layer, I can boot with 6MB, and I still have 1MB
free.
I'm trying with DBG = 0 now. Maybe I can boot with 4MB :D.
Best regards,
Alex Ionescu
