Ros-dev March 2005

ros-dev@reactos.org

64 participants
200 discussions

by James Tabor

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"

18 years, 7 months

Ext2 Branch Tests

by James Tabor

Hi all, I tested some small files to and from root and subdirectories on the ext2 (D:) partition w/o any errors or lockups. Large file testing with 5147559 bytes. copy d:\ros.zip c:\ros.zip,,, it locked up. Only 4194304 bytes copied to drive C:. Does that number look anything familiar to anyone? How about 400000 Hex. ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 12 28 *** FCB Resource Released [Read] IRQL = 0 [src/read.c] Line No = 1244 Freeing = C0E1B950 [misc] IRQL = 0 [src/misc.c] Line No = 1159 Read IRP Received... IRQL = 0 [src/read.c] Line No = 47 === Read File Name : -ros-020-bin.zip- IRQL = 0 [src/read.c] Line No = 216 ->ByteCount = 0x 4000 IRQL = 0 [src/read.c] Line No = 223 ->ByteOffset.LowPart = 0x 3fc000 IRQL = 0 [src/read.c] Line No = 224 ->Can Wait IRQL = 0 [src/read.c] Line No = 228 ->Not Paging Io IRQL = 0 [src/read.c] Line No = 241 ->SynchronousIo IRQL = 0 [src/read.c] Line No = 246 ->BufferedIo IRQL = 0 [src/read.c] Line No = 259 ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 49 6 *** Attempting to acquire FCB Shared [Read] IRQL = 0 [src/read.c] Line N o = 498 State: FCBMain AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 *** FCB Acquired [Read] IRQL = 0 [src/read.c] Line No = 507 [File Read] BufferedIo IRQL = 0 [src/read.c] Line No = 561 State: Resource AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 12 28 *** FCB Resource Released [Read] IRQL = 0 [src/read.c] Line No = 1244 Freeing = C0E19F20 [misc] IRQL = 0 [src/misc.c] Line No = 1159 Read IRP Received... IRQL = 0 [src/read.c] Line No = 47 === Read File Name : -ros-020-bin.zip- IRQL = 0 [src/read.c] Line No = 216 ->ByteCount = 0x 4000 IRQL = 0 [src/read.c] Line No = 223 ->ByteOffset.LowPart = 0x 400000 IRQL = 0 [src/read.c] Line No = 224 ->Can Wait IRQL = 0 [src/read.c] Line No = 228 ->Not Paging Io IRQL = 0 [src/read.c] Line No = 241 ->SynchronousIo IRQL = 0 [src/read.c] Line No = 246 ->BufferedIo IRQL = 0 [src/read.c] Line No = 259 ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 49 6 *** Attempting to acquire FCB Shared [Read] IRQL = 0 [src/read.c] Line N o = 498 State: FCBMain AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 *** FCB Acquired [Read] IRQL = 0 [src/read.c] Line No = 507 [File Read] BufferedIo IRQL = 0 [src/read.c] Line No = 561 Read IRP Received... IRQL = 0 [src/read.c] Line No = 47 === Read File Name : -ros-020-bin.zip- IRQL = 0 [src/read.c] Line No = 216 Gets lost here, ByteCount mul's up by 16: ->ByteCount = 0x 40000 IRQL = 0 [src/read.c] Line No = 223 ->ByteOffset.LowPart = 0x 400000 IRQL = 0 [src/read.c] Line No = 224 ->Can't Wait IRQL = 0 [src/read.c] Line No = 232 ->Paging Io IRQL = 0 [src/read.c] Line No = 237 ->SynchronousIo IRQL = 0 [src/read.c] Line No = 246 ->NonBufferedIo IRQL = 0 [src/read.c] Line No = 255 ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 47 3 *** Attempting to acquire FCBPaging Shared [Read] IRQL = 0 [src/read.c] Line No = 475 State: FCBPaging AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 *** FCBPaging Acquired [Read] IRQL = 0 [src/read.c] Line No = 486 [File Read] Paging IO or NonBufferedIo IRQL = 0 [src/read.c] Line No = 634 Reading in some Single Indirect Blocks IRQL = 0 [src/read.c] Line No = 6 84 Reading in some Double Indirect Blocks IRQL = 0 [src/read.c] Line No = 7 23 State: Resource AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 12 28 *** FCB Paging Resource Released [Read] IRQL = 0 [src/read.c] Line No = 1240 === Asynchronous request. Deferring processing IRQL = 0 [src/misc.c] Li ne No = 1187 Ext2QueueHandlerThread Alerted!!! IRQL = 0 [src/ext2init.c] Line No = 36 1 === Serviceing IRP_MJ_READ request asynchronously . IRQL = 0 [src/misc. c] Line No = 1283 === Read File Name : -ros-020-bin.zip- IRQL = 0 [src/read.c] Line No = 216 ->ByteCount = 0x 40000 IRQL = 0 [src/read.c] Line No = 223 ->ByteOffset.LowPart = 0x 400000 IRQL = 0 [src/read.c] Line No = 224 ->Can Wait IRQL = 0 [src/read.c] Line No = 228 ->Paging Io IRQL = 0 [src/read.c] Line No = 237 ->SynchronousIo IRQL = 0 [src/read.c] Line No = 246 ->NonBufferedIo IRQL = 0 [src/read.c] Line No = 255 ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 47 3 *** Attempting to acquire FCBPaging Shared [Read] IRQL = 0 [src/read.c] Line No = 475 State: FCBPaging AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 *** FCBPaging Acquired [Read] IRQL = 0 [src/read.c] Line No = 486 [File Read] Paging IO or NonBufferedIo IRQL = 0 [src/read.c] Line No = 634 Reading in some Single Indirect Blocks IRQL = 0 [src/read.c] Line No = 6 84 Reading in some Double Indirect Blocks IRQL = 0 [src/read.c] Line No = 7 23 Read IRP Received... IRQL = 0 [src/read.c] Line No = 47 === Read File Name : -null- IRQL = 0 [src/read.c] Line No = 220 ->ByteCount = 0x 40000 IRQL = 0 [src/read.c] Line No = 223 ->ByteOffset.LowPart = 0x4ab00000 IRQL = 0 [src/read.c] Line No = 224 ->Can't Wait IRQL = 0 [src/read.c] Line No = 232 ->Paging Io IRQL = 0 [src/read.c] Line No = 237 ->ASynchronousIo IRQL = 0 [src/read.c] Line No = 250 ->NonBufferedIo IRQL = 0 [src/read.c] Line No = 255 ###### File Pointer 0xC0E18900 [Read] IRQL = 0 [src/read.c] Line No = 28 9 *** Attempting to acquire VCB Shared [Read] IRQL = 0 [src/read.c] Line N o = 294 State: VCBPaging AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 *** VCBPaging Acquired [Read] IRQL = 0 [src/read.c] Line No = 304 [Volume Read] PagingIo or NonBufferedIo IRQL = 0 [src/read.c] Line No = 336 State: Resource AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 ###### File Pointer 0xC0E18900 [Read] IRQL = 0 [src/read.c] Line No = 12 28 *** VCBPaging Released [Read] IRQL = 0 [src/read.c] Line No = 1236 Freei Freeing = C0E1C440 [io] IRQL = 2 [src/io.c] Line No = 426ng = C0E25770 [misc] IRQL = 0 [src/misc.c] Line No = 1159 Lockup..........

19 years, 7 months

Re: [ros-web] New proposed frontpage for reactos.com

by Jason Filby

Hi all Jh sent me a better look: http://reactos.com/newsite/reactos_index.html I think it looks better! I've also reworded our slogan at the top to read what Steven suggested. Magnus: I'm sorry but your critism is not constructive! Which links do you want on the frontpage that aren't already there? You cannot link to everything on the frontpage either! Cheers Jason

19 years, 10 months

Re: [ros-dev] Package Manager

by Steven Edwards

Hi, --- Maarten Bosma <maarten.paul(a)bosma.de> wrote: > As you might remember firk85 and me have started coding a package > manager for ReactOS. More information and a download linkcan be found on > the wiki on http://wiki.reactos.com/PackageManager . > > Since it is now so far that it is at least a bit useful, I'd like to ask > what you think of adding it to the svn-tree ? MSI already does everything you want to do. Add support for loading MSI packages by developing your application on Windows and then it should work in ReactOS as we share msi.dll and msiexec with wine. Vendors can already use Wix to package thier applications. For bonus points make it tie in nicely with NSIS. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Personals - Better first dates. More second dates. http://personals.yahoo.com

19 years, 10 months

Re: [ros-dev] Package Manager

by Steven Edwards

--- Maarten Bosma <maarten.paul(a)bosma.de> wrote: > If I understood you correctly you said that there is no need for > developing a compleatly new system, a Packagemanager only had to provide > a interface for the msi files. Right, You can interface directly to the MSI database in the registry. > First of all, I have to say that I don't know much about that msi stuff. > So my question is how would the msi file and the program communicte ? > The point with a packagemanager is that you choose to install lots of > packages and leave your PC alone. So the package manager had to send the > dessions of the user to the msi file and then the msi file had to do > it's operations senlitly. And send reports to the package manager from > time to time. And if something went wrong, it has to send a compleate > error report. Well MSI packages have a lot of options, more so than are used by most people. Most people just write a Install Shield wizard and have the software packaged in a msi but it can do self-repair and modification and all sorts of cool stuff. Most third partys now ship apps as MSI as its what Microsoft supports or they use NullSoft Install System so making a easy to use interface to both of them will win the most support. Its like a mini-sql database so you can even use XML to mess with it in your Package Manager. If I understand correctly the Microsoft tool for creating MSI packages "WiX", uses a xml file for input. The only problem is that WiX is CPL and not GPL so we cannot ship it with ReactOS unless we make it a seperate download. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Personals - Better first dates. More second dates. http://personals.yahoo.com

19 years, 10 months

Idea for NTFS replacement

by Mike Swanson

NTFS is an important feature of Windows NT, it is one of the most advanced file systems devised. It contains many security devices that makes Windows NT secure. It is much more reliable than FAT. Perhaps instead of waiting for someone to make complete NTFS support in ReactOS (not that it shouldn't be done), we may make a filesystem of our own that is designed with NTFS features in mind (http://linux-ntfs.sf.net/ntfs/), but since we make it we have complete support for it. I was thinking of the name MUSCLE, a pun of FAT. I'm not exactly sure if the letter mean anything yet, but they could be in the future ;) -- Mike

19 years, 10 months

Package Manager

by Maarten Bosma

Hallo, As you might remember firk85 and me have started coding a package manager for ReactOS. More information and a download linkcan be found on the wiki on http://wiki.reactos.com/PackageManager . Since it is now so far that it is at least a bit useful, I'd like to ask what you think of adding it to the svn-tree ? Maarten Bosma

19 years, 10 months

Xen port of ReactOS

by Ge van Geldorp

Hello, After doing some research, I've decided to go ahead and start a port of ReactOS to Xen. For those in the Xen community not familiar with ReactOS: it's an open-source (GPL) re-implementation of the Microsoft Windows NT-based line of operating systems, aiming to provide binary compatibility for both applications and drivers (http://www.reactos.com). For those in the ReactOS community not familiar with Xen: it's an open-source (GPL) virtual machine monitor that supports execution of multiple guest operating systems with unprecedented levels of performance and resource isolation (http://www.cl.cam.ac.uk/Research/SRG/netos/xen/index.html). Initially I'll focus on getting ReactOS running as a guest OS. This should benefit ReactOS primarily, since this will make it possible to develop large parts of ReactOS (everything except for hardware drivers and some low-level memory management) inside Xen. It will also give ReactOS access to some hardware not natively supported yet (by using the Linux driver). The benefit for Xen at this stage would be the development of ReactOS device drivers for interfacing with Xen, which could also be used for a Windows XP port. On the longer term, I see no reason why ReactOS couldn't function as a driver domain. As driver compatibility improves in ReactOS, this could provide Xen guests access to hardware for which the manufacturer provides only Windows drivers (due to Xens nature, not every driver could be used this way, but I bet a large percentage of the drivers depend on the kernel to do the really low-level stuff). All in all, it seems a win-win proposition for both projects. And even more importantly, I think it's a cool project :-) I've made a branch in ReactOS svn, svn://svn.reactos.com/branches/xen, for this port. Of course, the goal is to merge the changes into trunk eventually. I expect the port to take at least a few months, my initial feeling is that it should be done by the end of the year (there's lots of other stuff in ReactOS I want to work on too). The wiki page at http://wiki.reactos.com/Xen_port will be used to keep track of progress. The game plan is just start working from the boot code, until a problem is hit. Fix that problem and continue until the next problem. Any support and help from the Xen and ReactOS communities are of course greatly appreciated. Gé van Geldorp.

19 years, 10 months

confusing smss routine (ea)

by Gunnar Dalsnes

I was doing some changes to RtlCreateUserProcess and saw the strage rotuine SmCreateUserProcess: http://svn.reactos.com/viewcvs/trunk/reactos/subsys/smss/smapiexec.c?rev=14… It has several bugs/problems/confusions: 1) RtlDestroyProcessParameters is not called if RtlCreateUserProcess failed. 2) If WaitForIt is TRUE and you specify a timeout, the caller in not notified if SmCreateUserProcess returned due to timeout. The process will stay running forever. 3) If TerminateIt is TRUE, handles are closed. This is wrong/confusing. Closing the handles does not terminate the process (wrong name?). 4) If you dont pass a UserProcessInfo and TerminateIt is FALSE, it will leak thread/process handles. 5) If you pass UserProcessInfo and TerminateIt is TRUE, the thread/process handles in UserProcessInfo will be invalid. etc.etc. VERY confusing and bug prone: SmCreateUserProcess is used once in the end of this file and it pass FALSE for TerminateIt and pass no UserProcessInfo thus the thread/process handles will never be closed. I should have fixed it myself if i just understod how this routine is _supposed_ to work:-D Regards Gunnar

19 years, 10 months

Network connection config dialog prototype

by Andrew "Silver Blade" Greenwood

Following some discussion with Art Yerkes via email, I've been toying around with a resource editor and shifted XP's network connection configuration dialog around: www.furrybeans.co.uk/stuff/netdlg.jpg Note that this will not be the final dialog, nor will that exact one be used - I'm using a resource editor just so I don't have to painstakingly recreate each control just to see what it looks like. It's just convenient for laying out a prototype. Ignore the image at the top left - that was there already. Compare with XP or 2000's dialog and let me know what improvements you can think of. -Andrew

19 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev March 2005