Ros-dev August 2005

ros-dev@reactos.org

62 participants
118 discussions

Via Vt6102 Net card
by James Tabor 14 Jun '06

14 Jun '06

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"

2 3

New Webserver System
by Rick Langschultz 03 Sep '05

03 Sep '05

I was kicking around the idea of installing a jabber server on my companies server to allow instant messaging on the local area network. Would reactos.com be willing to do something like that or is that too far out of the scope of the project. I was going to use OpenLDAP for authentication and save all of the conversations in XML files in both senders and recipients home folders. I also was going to write an XSL to display those messages. I think this would help out both developers and users of reactos. Including future RosMessenger or something like that... Just a though... Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

14 18

ReactOS 'Support Database' for the new ReactOS Homepage (ideas, goals, questions)
by Klemens Friedl 01 Sep '05

01 Sep '05

ReactOS 'Support Database' for the new ReactOS Homepage I wrote down a lot of ideas, questions, soulutions, goals, etc. for the upcoming Support Database! We need more ideas, suggestions, comments, etc! Please read the whole text and then write an email to the mailing list! This text should start discussion about that topic !!! Thanks! Note: * some of the ideas are not completely new, i copy&paste the from winehq's newsletter archive (i quoted the winehq's ideas and add the original post date)! * I have added some useful links at the of the text! Please try out the links and explore the compatibility databases from other projects! You will need it if you want to join the discussion. And I *hope* a lot of persons join the discussion! So please visite the links and write down what could be better or what's key features our database also should *clone*! The 'Support Database' will contain the following 'databases': * Compatibility Database (application, driver and hardware) * Package Database (a list of download-able applications/driver; principal for the ReactOS Package Manager) (* Media Database (like the ReactOS Fansite Media Database; maybe we can implement this later)) The 'Support Database' (project codename 'RosDB') will base on the package manager alpha page that i have created april 2005. Note: the package database will be combined with the compatibility datbase. Both 'databases' will share the same 'application tree'! So it will be easy e.g. you browse the compatibility db, you found a working app and think, "i also want to download this app", then you will be able to click on a link (on a central position) and you will be redirected to the package database. In near future it should be possible (if you run ReactOS or Win32 with installed and runing ReactOS Package Manager), that you can select your favorite apps/driver you want to install (navigation like amazone/ebay/compatibility db) and then click install (a normal link on the package manager page) and your running (maybe as a service) ReactOS Package Manager check/capture every clipboard item and if it is a valid 'package style link' then it will connect to the online database and download all the selected apps/driver and download it from mirror server (from their developers/sourceforge/etc.) and then install all items (without or with minimum of user interaction). In my (frik85) opinion, that would be one of the 'hottest' feature someone can imagine (in connection with a homepage, package manager, etc.). This feature will became a main feature and everyone will use that *hope* for ReactOs and also possible for Win32 (from MS). :) -- frik85 "ReactOS Compatibility Database ReactOS has an Compatibility Database where Windows application/driver/hardware compatibility is recorded. Registered users can submit new items, and comment on existing ones. Screen shots are also available for many apps. Users can also vote on their favorite apps." -- a possible description Design goals User wants to know following things: * Does my application/driver/hardware work? * How can I make it work? * Does it work in the new ReactOS/application/driver/hardware version? * Where can i download the application (maybe with the ReactOS Package Manager)? * list all working and non working application/driver/hardware Management Issues/Goals: We need a high 'input data quality', then the administration work will be a minimum. To reach this high data quality, i want to code a simple to use wizard for the 'submit item' page. You can view the sample wizard on the package manager alpha page (see link). Have some form of a moderation system to let end users know the quality of a given persons entry. Maybe like the appDB from winehq? Where a registered user can ask for a kind of moderator right for one specific item (e.g. application), so he can manage the comments, add new info, etc. -> taking ownership of an item (e.g. application): monitor comments on it, track bugs (close bugs), and make sure quality level is high for application description. NO redundant entries for the same product! We need moderators who review all new entries. The moderators should be able to read as many comments as possible and help the normal users, report bugs to the bugzilla system, etc. Reviews (aka user comments) should expire. (expire time 1 year?) Track hit counts on each item (auto magic way of knowing which apps are most desired) and maybe voting like in appDB (WineHQ) or in C4 (CodeWeaver). Some ideas i found in old winehq's neewsletters: (maybe useful for our project!) "Idea: Tie the apps database to the api database. The idea is that we know from the apps database which apps are the most popular. We know from the api database which DLLs/entry points are used by those apps. We can then create a report out of the api database of the list of the DLLs most needed by the top ten apps, and then people writing test scripts (something Alexandre and John Sturtz are working on), have a prioritized todo list. Again, this helps us find useful things for the many volunteers to do." -- winehq newsletter from 18 Oct 2000 Note: maybe a good idea to create such a api database; -> a simalar api status output is currently generated from the svn server (with a small console based application, see build tools). You can view the api status on the svn server. A great chance to import the data to the database and make the idea above possible! The only question, is it usefull for someone? -- frik85 "Idea: Tie the apps database to bugzilla. If users have a problem with an app, it's a bug, and should be in bugzilla. If we can get to a point where we can easily get a report that says 'here are all the bugs that Quicken depends on'. Or, here are the five bugs, the fixing of which will make 50 apps suddenly work. This would be wicked cool." -- winehq newsletter from 18 Oct 2000 Note: the bugzilla will be a subsystem of the RosCMS, so it will be (maybe) possible to implement the idea above. Is something like this usefull for someone? -- frik85 "if we add some 'relay statistics' in Wine code (of course, there will be problems with COM objects where relaying does not work for now) and incorporate these statistics in the database, we could have a list of the most frequently used Windows calls. (feel free to add new ideas for improvements :-) )" -- winehq newsletter from 28 Dec 2000 "He [who take ownership of an item] definitely should have the application installed and, very preferably, he should also be using it regularly (or testing it regularly if it is not yet in the usable state). You are right in pointing out that he cannot test all possible but I contend he does not have to. His role would be to: read the comments entered in the application's comment section. engage into a discussion with the users who post interesting tricks, information, report a sub-version as not working, report problems with a specific Wine/Windows combination extract and summarize the above in his application status report. This section would come first in the application's page and only the application maintainer would be allowed to modify it (whether it's strictly enforced or not is another issue) test the application regularly and update the information on the application's page help users having problems with that application " -- winehq newsletter from 28 Dec 2000 "Jeremy White proposed some scheme to help keeping the database usable: I think the biggest problem with the app database is that we get garbage in, it produces garbage out. I think we should not report or even use any user scores until a trusted app db maintainer has validated that user experience (and possibly users can become trusted reporters). Too many people say 'Hey! The main screen came up! That's a 5! Witness the Slashdot post about MS Office 2k. (anyone actually try to use Office 2K in Wine to author a sizable document?)." -- winehq newsletter from 28 Dec 2000 The information we will gain from the support database * the progress of ReactOS (for devs and normal user) * the most wanted applications (when we implement a voting / hit counts feature) * a reference for application/driver/hardware that doesn't work without tweaking, to get them working * people may be able taking 'ownership' of an application and do regular bug reports / regression testings). Several questions, where we need a answer: "How to 'classify' applications ?: the main point was how an application should be identified (think of Word 5 vs. WinWord 5 cs. Word 7.0, and lots of other quirks (limited versions, demo version, patched versions...) What information should we have about an application ?: this would help in knowing the correct context of execution of such an application (target Windows version, used DLLs, used APIs...)" -- winehq newsletter from 28 Dec 2000 * And about a ReactOS releases ? * How about scoring ? * What additional information should one application/driver/hardware have? We need as much ideas, (feedback after the relaunch/while the testing phase), comments, (and flames) as possible the next weeks. After the website relaunch We need volunteers to take responsibility for updating Apps in the Compatibility Database. We need to discuss this! Then after the discussions ... only remains the hours of coding and debugging to put it in place :) Compatibility Databases from other projects: http://appdb.winehq.org/ http://www.codeweavers.com/compatibility/ http://www.linuxcompatible.org/compatibility.html http://www.ntcompatible.com/compatibility.html http://www.microsoft.com/whdc/hcl/default.mspx ttp://www.realtimesoft.com/multimon/search.asp http://hardwaredb.suse.de/index.php?LANG=en_UK http://www.testingstandards.co.uk/compatibility_-_database.htm http://www.yellowtab.com/support/hardware/ http://www.iyonix.com/software/ http://www.ardi.com/compat_search.php?name=ALL&category=ALL&status=ALL A kind of Package Database: http://rpmseek.com/index.html?hl=en If you know other websites that should be listed here, please write an email to the mailing list! Best regards, Klemens Friedl <frik85> PS: if you write a comment, do NOT quote whole passages or do NOT quote the whole text! The reason, emails should be readable ... -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl

4 4

Ros VGA driver not working - To be confirmed
by Gge 31 Aug '05

31 Aug '05

Hello, Ros VGA driver does not work anymore in my real hardware configuration. I'd like to know if the problem is confirmed by somebody else. To reproduce it , disable the VBE drives in Hiveinst.inf file , make registry and reboot. The green Reactos logo displayed at boot is not displayed correctly ( color is red/yellow etc , the logo is not clearly displayed ) Here are the debug messages (DBG=1) --------------------------- (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\mpu401.sys (drivers\input\i8042prt\registry.c:218) Can't read registry: c0000034 (drivers\input\i8042prt\registry.c:224) Manually set defaults (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\xboxvmp.sys (ntoskrnl\ob\wait.c:246) Returning: 0 (subsys\win32k\ntuser\desktop.c:769) Trying to open desktop (\Windows\WindowStations\WinSta0\Default) (subsys\win32k\ntuser\desktop.c:580) IntShellHookNotify: No desktop! (subsys\win32k\ntuser\desktop.c:769) Trying to open desktop (\Windows\WindowStations\WinSta0\Winlogon) (subsys\win32k\ntuser\desktop.c:580) IntShellHookNotify: No desktop! (subsys\win32k\ntuser\desktop.c:769) Trying to open desktop (\Windows\WindowStations\WinSta0\Screen-Saver) (subsys\win32k\ntuser\desktop.c:580) IntShellHookNotify: No desktop! (lib\ntdll\ldr\utils.c:2072) Relocating (77a90000 -> 431000) C:\ReactOS\System32\version.dll FIXME: CopyImage doesn't support IMAGE_ICON correctly! (lib\ntdll\ldr\utils.c:1190) LdrGetExportByName(): failed to find mxdMessage (lib\ntdll\ldr\utils.c:2015) Failed to create or open dll section of 'msacm.drv' (Status c0000135) (lib\ntdll\ldr\utils.c:2015) Failed to create or open dll section of 'midimap.drv' (Status c0000135) (SAMLIB:lib\samlib\samlib.c:399) User already exists! (lib\setupapi\devinst.c:2513) not fully implemented (lib\setupapi\devinst.c:2513) not fully implemented (lib\setupapi\devinst.c:2513) not fully implemented (lib\setupapi\devinst.c:2513) not fully implemented (lib\setupapi\devinst.c:2513) not fully implemented (lib\setupapi\devinst.c:2513) not fully implemented Thanks Gge

2 1

Baby Steps
by Rick Langschultz 30 Aug '05

30 Aug '05

This is a suggestion: Can ReactOS implement an OpenLDAP backend to the ReactOS website. There are many benefits to implementing OpenLDAP into the reactos.com website. First, reactos.com can use this software to authenticate users in certain modules of the website such as future forums, wikis (via publishing), and possible later implementation into a mass- mailing system like squirrelmail or mailman, suggestions, hint hint, or perhaps in the future an instant messenger engine. Also OpenLDAP would be able to provide back-end website developers to verify status of community members. How is that for a baby step to implementing someone's ideas... Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

5 7

bootsect.ros
by dalfa the enlightenedone 30 Aug '05

30 Aug '05

hi i installed reactos on my hd but the installer doesnt give the option to install de loader to the mbr only on the floppy so i didnt installed because i dont have a floppy :p then i create: freeldr.ini ant copy the freeldr.ini but i didnt know what the bootsect.ros is i didnt find info about it in the wiky ¿how can i create one? -- [dalfa@MDK dalfa]$ cat .firma [UsuarioGnu/Linux326018] <Ymessenger> dalfa_id <WebPage> http://dalfa.tk <WebPage> http://dalfa.no-ip.org <Jabber> dalfa(a)jabber.org <skype> theenligthenedone <aMSN> dalfa.theenlightenedone(en)gmail.com <Blog> http://drakedalfa.blogspot.com/ <aim> drakedalfa -> Y la verdad os hara libres... - Hechos 4: 12 - Romanos 10: 9-13

2 2

Shouldn't errors be explained a bit better?
by Reuben Perelman 29 Aug '05

29 Aug '05

I was looking through the installer, and noticed that it generated an error for partitions created by linux fdisk. Shouldn't the user be informed about this, so they know why. This type of information will help a user solve the problem that caused the error. Below is the code for the error I'm talking about. if (WarnLinuxPartitions == TRUE && CheckForLinuxFdiskPartitions (PartitionList) == TRUE) { PopupError ("Setup found that at least one harddisk contains an incompatible\n" "partition table that can not be handled properly!\n" "\n" "Creating or deleting partitions can destroy the partiton table.\n" "\n" " \x07 Press F3 to quit Setup." " \x07 Press ENTER to continue.", "F3= Quit ENTER = Continue"); while (TRUE) { ConInKey (Ir); if ((Ir->Event.KeyEvent.uChar.AsciiChar == 0x00) && (Ir->Event.KeyEvent.wVirtualKeyCode == VK_F3)) /* F3 */ { return QUIT_PAGE; } else if (Ir->Event.KeyEvent.wVirtualKeyCode == VK_RETURN) /* ENTER */ { WarnLinuxPartitions = FALSE; return SELECT_PARTITION_PAGE; } } }

1 0

Nevermind
by Rick Langschultz 29 Aug '05

29 Aug '05

Since I heard of reactos, i have always considered it one day replacing my Windows 2000 and XP boxes. Because ReactOS was going to be an open-source alternative to the Windows NT API I felt that it had and has serious potential to hinder or greatly replace Microsoft Windows. I have suggested several ideas both through IRC (freenode) and email messages how the computing world does things. I understand that ReactOS is still in pre-production, and planning for the next release is greatly important to the community development and testing of the operating system, however I fail to grasp the concept behind the hindrance of ideas being passed the the development community. Some development plans I have talked about were: 1 - A 64 bit journaling file system with a SQL-like back-end. Lookout WinFS; there that plan went down the drain. 2 - Implementing an instant messenger server for developers and users to talk on, realtime, without IRC. Maybe not quite MSN Messenger, but why not? iChat even uses .mac. 3 - Implementing an OpenLDAP back-end to the website. Active Directory has nothing on you... Plan knocked out again. i would rather stick with something close minded like closed source software than having no ideas be recognized at all. I only suggest things like this because Microsoft will always be releasing newer software that will leave reactos in the dust if they not heed the advice of all, not just me, their developers, testers, and users. Why not; right? why envision something and it fail to be realized, waste of time if i ever knew it... Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

6 5

Installation procedure
by drake dalfa 28 Aug '05

28 Aug '05

|>hi, |> |>i have a problem with the installation from |>setup to a real hd the setup dies with this |>message: |> |>allowconsolo() failed (status = 0x0000001) |> |That one seems a well known bug: |http://www.reactos.com/wiki/index.php/ChangeLog-0.2.7 |http://reactos.com/bugzilla/show_bug.cgi?id=688 thanks that show me the way ;) the problem is my keyboard is usb one so i plug an ps2 one and now all work :) maybe a little more debug on the setup will help to others to figure this :) more easy thanks :) |>the installation procedure is only the copy |>of the reactos directory to the hd? |> |It also prepares the SYSTEM registry hive with values depending on the |operator choices and (little) hardware probing and installs the boot sector. thanks, now i can install the system and now i configure the grub but i have another question the file bootsect.ros, wath has to say? i made my freeldr.ini like this: [ReactOS] BootType=ReactOS SystemPath=multi(0)disk(0)rdisk(0)partition(7)\reactos Options=/DEBUGPORT=SCREEN but the bootsect.ros i didnt find a example :) thanks for the help

1 0

Re: [ros-bugs] [Bug 729] ftp.exe exit at start
by Gge 28 Aug '05

28 Aug '05

ReactOS.Bugzilla(a)reactos.com wrote: > http://reactos.com/bugzilla/show_bug.cgi?id=729 > > > > > > ------- Additional Comments From waxdragon(a)gmail.com 2005-27-08 18:14 ------- > Hartmut's 17563 commit fixed this. Thank you! There are still issues with ftp, > and I will file another bug. > Ftp.exe still fails for me as per debug messages below WARNING: WSHGetSockaddrType at drivers\net\wshtcpip\wshtcpip.c:103 is UNIMPLEMENTED! WARNING: WSHGetSockaddrType at drivers\net\wshtcpip\wshtcpip.c:103 is UNIMPLEMENTED! 8ce8fc10: 00 31 66 00 00 00 00 00 00 00 00 00 01 00 00 00 8ce8fc20: 0e 00 02 00 00 15 d4 1b 28 fc 00 00 00 00 00 00 8ce8fc30: 00 00 TCPConnect: Called Connecting to address fc281bd4:1500 so->so_state 102 so->so_state 102 so->so_state 102 so->so_state 102 (ntoskrnl\mm\mm.c:300) Address: ffffffff Unhandled exception Address: 7c815b1f C:\ReactOS\system32\KERNEL32.dll CS:EIP 1b:7c815b1f DS 23 ES 23 FS 3b GS 0 EAX: 00000001 EBX: 780263f0 ECX: 00000000 EDX: 0065fbf4 EBP: 00000000 ESI: 00020000 ESP: 0065fb30 EDI: 7c843cfc EFLAGS: 00010202 Frames: <error dumping stack trace: 0xc0000005> so->so_state 13b (lib\rtl\env.c:574) Return STATUS_VARIABLE_NOT_FOUND: PROMPT Regards

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev August 2005