Menu
▾
▴
reactos-kernel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(64) |
Oct
(438) |
Nov
(183) |
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(132) |
May
(466) |
Jun
(366) |
Jul
(392) |
Aug
(31) |
Sep
(18) |
Oct
|
Nov
|
Dec
|
|
From: Rex J. <re...@lv...> - 2001-11-02 06:30:42
|
I just checked in some code to deal with GDI handles. At least a few things remain to be done: When a process exits, a win32k function will need to be called that will clean up all outstanding handles in the table. This can be called from GDI32 DLL rundown I think. I used a fast mutex to protect access to the table. Is this a reasonable sync object to use across processes? GDI handles keep the process id as a field, but PsGetCurrentProcess does not seem to be available to a kernel mode dll. Which function is available that returns the current process id? Accoring to all I can find, GDI handles (and GDI functions) are not thread safe. So I removed all the code that was locking and unlocking individual handles. I originally added the handle locking code based on a hint from Wine. However, is code involving User handles expected to be thread safe? I dont see how if the underlying GDI calls are not, but its possible. If so we cannot reuse the GDI handle routines for User handles as I would like to. Rex Jolliff re...@lv... ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Phillip S. <ps...@cf...> - 2001-11-02 01:09:37
|
I can't build regexpl because the include search dirs passed to windres are not correct for some reason, and it can't find the includes. I can't for the life of me find where the makefile defines how to build a .coff from a .rc with windres. Anyone got any idea here, cause I'm confused. ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Phillip S. <ps...@cf...> - 2001-11-02 00:40:57
|
That fixed it... odd... thanks. At 12:24 PM 11/1/2001 +0100, you wrote: >I just had a look at my binary mingw tree. Libstdc++.a exists but 'make >bindist' seems to cripple its name. I found 'libstdc++.a.2.10.0' in the lib >subdirectory. Rename it to 'libstdc++.a' and everything should be okay. >Please, tell me if it works. > >Guess this is just another makefile bug. :-/ > >- Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Phillip S. <ps...@cf...> - 2001-11-02 00:36:07
|
What is the status with the bus drivers? acpi and pci. What do they do and should I be loading them? I think the purpose of the drivers is to be the root bus driver to enumerate all other devices in the system for the WDM PnP system to load PnP drivers. Are we trying to move to WDM and PnP, and if so, how far are we? ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-11-01 23:48:38
|
cool, I'm rebuilding now. I'll test everything tonight and let you know how it works out. -----Original Message----- From: Eric Kohl To: ros...@re... Sent: 11/1/01 6:24 PM Subject: [ros-kernel] Re: Build Errors was RE: New ide driver "Steven Edwards" <Ste...@kn...> wrote: > Thats cool about the new ATAPI spec but we will still have a problem with > older drive right? Unless we do like Jakob said a build a table for older > brands. I don't see any problems because I have never heared of ATA drives with a non-'512 bytes' sector size. Only ATAPI devices can have different sector sizes, for example cd-roms (2048 bytes) or mo-disks (512/1024/2048 bytes). > When I try to rebuild ROS from a clean source tree (3 hours ago) I get the > following crash in services/bus/pci due to redefinitions. What definitions > are the right ones for pci? > I removed PCI_COMMON_CONFIG. It resides in the ddk headers now. - Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ |
|
From: Eric K. <ek...@rz...> - 2001-11-01 23:25:10
|
"Steven Edwards" <Ste...@kn...> wrote: > Thats cool about the new ATAPI spec but we will still have a problem with > older drive right? Unless we do like Jakob said a build a table for older > brands. I don't see any problems because I have never heared of ATA drives with a non-'512 bytes' sector size. Only ATAPI devices can have different sector sizes, for example cd-roms (2048 bytes) or mo-disks (512/1024/2048 bytes). > When I try to rebuild ROS from a clean source tree (3 hours ago) I get the > following crash in services/bus/pci due to redefinitions. What definitions > are the right ones for pci? > I removed PCI_COMMON_CONFIG. It resides in the ddk headers now. - Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-11-01 22:46:56
|
Thats cool about the new ATAPI spec but we will still have a problem with
older drive right? Unless we do like Jakob said a build a table for older
brands.
When I try to rebuild ROS from a clean source tree (3 hours ago) I get the
following crash in services/bus/pci due to redefinitions. What definitions
are the right ones for pci?
make -C services/bus/pci
make[1]: Entering directory `C:/user/src/reactos/services/bus/pci'
windres --include-dir ../../../include pci.rc -o pci.coff
gcc -D__NTDRIVER__ -I./ -I../../../include -pipe -march=i386 -c fdo.c -o
fdo.o
In file included from pci.h:7,
from fdo.c:10:
pcidef.h:310: redefinition of `struct _PCI_COMMON_CONFIG'
pcidef.h:326: redefinition of `struct _PCI_HEADER_TYPE_0'
pcidef.h:342: redefinition of `PCI_COMMON_CONFIG'
../../../include/ddk/haltypes.h:157: `PCI_COMMON_CONFIG' previously declared
her
e
pcidef.h:342: redefinition of `PPCI_COMMON_CONFIG'
../../../include/ddk/haltypes.h:157: `PPCI_COMMON_CONFIG' previously
declared he
re
make[1]: *** [fdo.o] Error 1
make[1]: Leaving directory `C:/user/src/reactos/services/bus/pci'
make: *** [pci] Error 2
C:\user\src\reactos>
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
|
|
From: Eric K. <ek...@rz...> - 2001-11-01 22:33:14
|
"Steven Edwards" <Ste...@kn...> wrote: > could freeldr pass this information to ros? > No. I had a look at the ATA/ATAPI-5 specification. The 'BytesPerSector' and 'BytesPerTrack' data (word 4 & 5) are now obsolete. IMO, this means that *all* ATA devices use 512 byte sectors. This does not apply to ATAPI devices. We should be able to get media information by using a SCSI command. - Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-11-01 20:37:55
|
I saw on the homepage that developers sometimes meet to discuss things on openprojects. I would like to suggest that mabey we set some time(s) we could all chat once a week or something. Steven########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ |
|
From: Steven E. <Ste...@kn...> - 2001-11-01 20:34:51
|
could freeldr pass this information to ros? -----Original Message----- From: Jakob Eriksson To: ros...@re... Sent: 11/1/01 2:57 PM Subject: [ros-kernel] Re: AW: AW: Re: RE: Re: RE: New ide driver On Thu, Nov 01, 2001 at 06:38:18PM +0100, Eric Kohl wrote: > > "Hartmut Birr" <har...@te...> wrote: > > > > The problem is in IDEGetDriveIdentification(). Two of my disks reports a > > sector size of 580 Byte. When I set DrvParms->BytesPerSector to 512, it > > works fine. > > > Arrrgh! What kind of disk is this? Any special IBM mainframe disk? Doesn't it work with 580 byte sector size? > I don't really like the idea of hardcoding the sector size. Perhaps 512 > bytes should be a kind of default value if the reported sector size is not > 1024 or 2048. > > Any ideas?? > A table with disk brands? Ignoring the problem and hoping that non-ancient disks behave better? regards, Jakob ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ |
|
From: Jakob E. <ja...@vm...> - 2001-11-01 19:59:50
|
On Thu, Nov 01, 2001 at 06:38:18PM +0100, Eric Kohl wrote: > > "Hartmut Birr" <har...@te...> wrote: > > > > The problem is in IDEGetDriveIdentification(). Two of my disks reports a > > sector size of 580 Byte. When I set DrvParms->BytesPerSector to 512, it > > works fine. > > > Arrrgh! What kind of disk is this? Any special IBM mainframe disk? Doesn't it work with 580 byte sector size? > I don't really like the idea of hardcoding the sector size. Perhaps 512 > bytes should be a kind of default value if the reported sector size is not > 1024 or 2048. > > Any ideas?? > A table with disk brands? Ignoring the problem and hoping that non-ancient disks behave better? regards, Jakob ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-11-01 19:38:24
|
Is Fat32 write support working now? -----Original Message----- From: Jason Filby To: ros...@re... Sent: 11/1/01 1:20 PM Subject: [ros-kernel] Re: Next version ? FORWARDING TODO LIST by Eric Shouldn't those versions be moved one up? For instance shouldn't 0.0.18 in this list be 0.0.19? - Jason --- Robert Dickenson <od...@pn...> wrote: > At 07:03 PM 23/10/2001 +0100, you wrote: > > > >Hi > > > >When will the next version of reactos be released ? Is there a > TODO list > for version 0.0.19 ? > > > >Greetings > >Max > > > > > > I was thinking about a combination between a road-map and a to-do > list: > > > Version 0.0.18: > - FreeLoader: int13 extensions (high priority) > - FAT32 write support (high priority) > - fix Gditest (medium priority) > - ide driver split (low priority) > - pci bus driver (optional) > > Version 0.0.19: > - FreeLoader: registry support (high priority) > - Split ntoskrnl and hal (high priority) > - basic cdrom support (medium priority) > - registry write support (medium priority) > - run user-mode services (low priority) > - security functions (low priority) > - usb drivers (optional) > > Version 0.0.20: > - ReactOS bootable from cdrom (high priority) > - FreeLoader: hardware detection (high priority) > - setup program (medium priority) > - basic gui functionality (medium priority) > - eventlog service (low priority) > - smb network support (optional) > - rtl8139 nic driver (optional) > > Version 0.0.21: > - ReactOS installable from cdrom (high priority) > - network services (medium priority) > - ntfs driver (low priority) > - rpc support (low priority) > - scandisk tool (optional) > - ip6 support (optional) > - pcmcia/pc-card services (optional) > > > Priorities: > High: Topic must be included in release (delays release until > done). > Medium: Topic should be included in release (delays release for > max 2 > weeks). > Low: Topic should be included in release (does not delay > release). > Optional: Nice to have but not needed. > > Priorities of a topic can change. For example, a topic can be > optional for > one release but since it was not finished for this release, the > priority > will be raised to medium because it is needed for the next release. > > This can give newbies an idea where we are heading and they can > choose a low > priority or optional component for their first contribution. > > - Eric > > ==================================================== > = To remove yourself from this mailing list, go to = > = http://www.reactos.com/home/mailing.html = > ==================================================== > __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ |
|
From: Andrew W. <an...@ds...> - 2001-11-01 19:33:47
|
I'm not sure this is relavent, but it might be interesting to follow up on if the details come out this way. Rumors seem to be flying about a possible Microsoft settlement with the U.S. DOJ on the antitrust lawsuit. While the entire thing sounded too much like a sell out to me in general, I thought one of the rumored settlement details about MS having to allow code inspection for interoperability purposes could be interesting for Reactos. In otherwords, MS having to show Reactos people their code to allow Reactos to better "interoperate" with Windows. Obviously no code could be copied, or would MS allow it to be, but it would allow Reactos to verify compatibility and architecture details. Could be fun. The source of the rumor.. http://www.theregister.co.uk/content/4/22595.html **snip** Microsoft and the DoJ seem close to cutting a deal, and from the sound of the terms leaking from the settlement talks, the Beast stands a good chance of emerging relatively unscathed. That is, if the States attorneys general can be persuaded to go along with it. ... The final part of the deal to have made it into the public domain concerns access to Microsoft code. Rather than going for any of the more drastic solutions such as forcing Microsoft to license Windows or to make source code public, the DoJ appears to be settling for a much more limited option. Qualified personnel from software and hardware companies would be allowed to inspect Microsoft code in some form of secure facility - you may well wonder what the blazes that's supposed to mean. It's not as yet clear who would be deemed to be qualified, and who would have the final say-so on their access. Nor is it obvious that this kind of arrangement differs massively from the existing source access deals Microsoft has with some of its major customers, and some hardware suppliers. We can be pretty sure that Sun, which most certainly could not achieve such access at the moment, will be in there inspecting, shouting and screaming if this part of the deal goes ahead, but we can't be entirely sure how helpful these insepction rights will be, if at all. ... ***snip*** --Andrew (Yet another list lurker) ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Jason F. <jas...@ya...> - 2001-11-01 18:24:30
|
Shouldn't those versions be moved one up? For instance shouldn't 0.0.18 in this list be 0.0.19? - Jason --- Robert Dickenson <od...@pn...> wrote: > At 07:03 PM 23/10/2001 +0100, you wrote: > > > >Hi > > > >When will the next version of reactos be released ? Is there a > TODO list > for version 0.0.19 ? > > > >Greetings > >Max > > > > > > I was thinking about a combination between a road-map and a to-do > list: > > > Version 0.0.18: > - FreeLoader: int13 extensions (high priority) > - FAT32 write support (high priority) > - fix Gditest (medium priority) > - ide driver split (low priority) > - pci bus driver (optional) > > Version 0.0.19: > - FreeLoader: registry support (high priority) > - Split ntoskrnl and hal (high priority) > - basic cdrom support (medium priority) > - registry write support (medium priority) > - run user-mode services (low priority) > - security functions (low priority) > - usb drivers (optional) > > Version 0.0.20: > - ReactOS bootable from cdrom (high priority) > - FreeLoader: hardware detection (high priority) > - setup program (medium priority) > - basic gui functionality (medium priority) > - eventlog service (low priority) > - smb network support (optional) > - rtl8139 nic driver (optional) > > Version 0.0.21: > - ReactOS installable from cdrom (high priority) > - network services (medium priority) > - ntfs driver (low priority) > - rpc support (low priority) > - scandisk tool (optional) > - ip6 support (optional) > - pcmcia/pc-card services (optional) > > > Priorities: > High: Topic must be included in release (delays release until > done). > Medium: Topic should be included in release (delays release for > max 2 > weeks). > Low: Topic should be included in release (does not delay > release). > Optional: Nice to have but not needed. > > Priorities of a topic can change. For example, a topic can be > optional for > one release but since it was not finished for this release, the > priority > will be raised to medium because it is needed for the next release. > > This can give newbies an idea where we are heading and they can > choose a low > priority or optional component for their first contribution. > > - Eric > > ==================================================== > = To remove yourself from this mailing list, go to = > = http://www.reactos.com/home/mailing.html = > ==================================================== > __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Jason F. <jas...@ya...> - 2001-11-01 18:09:26
|
My late reply: Well the first thing wrong with gditest was that line clipping is not implemented in either win32k.sys or the vga driver. So I altered the background routine in gditest not to draw offscreen. The second problem is when creating a compatible DC (W32kCreateCompatibleDC) which is supposed to, when passed a NULL, create a DC compatible with the application's current screen. Now previously I had some really ugly code to do this, which I removed. I assume that the correct way to get the application's current DC would be via functionality provided by window stations / desktops. This is only going to be implemented once the new GDI handles are implemented. Rex signed up for this but is probably under a heavy work load at this time. I've just mailed Rex saying I can try and help with this task. - Jason --- Phillip Susi <ps...@cf...> wrote: > I got everything needed for a gditest run onto a compressed > bootable floppy > and tested it in several machines today, and it ran on all of them, > but > hangs drawing the initial background. The first two lines from 0,0 > to 640, > 480 and from 0,0 to 2,480 are drawn, and then the kernel freezes up > - the > caps lock toggle doesn't work. I've got a little clean up work to > do on > the ramdisk driver, then I'll wait until gditest works correctly > before > posting a downloadable test floppy image for people to check out on > the web > site. > > ==================================================== > = To remove yourself from this mailing list, go to = > = http://www.reactos.com/home/mailing.html = > ==================================================== > __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Eric K. <ek...@rz...> - 2001-11-01 17:42:04
|
"Hartmut Birr" <har...@te...> wrote: > The problem is in IDEGetDriveIdentification(). Two of my disks reports a > sector size of 580 Byte. When I set DrvParms->BytesPerSector to 512, it > works fine. > Arrrgh! What kind of disk is this? Any special IBM mainframe disk? I don't really like the idea of hardcoding the sector size. Perhaps 512 bytes should be a kind of default value if the reported sector size is not 1024 or 2048. Any ideas?? - Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Hartmut B. <har...@te...> - 2001-11-01 17:23:44
|
The problem is in IDEGetDriveIdentification(). Two of my disks reports a sector size of 580 Byte. When I set DrvParms->BytesPerSector to 512, it works fine. - Hartmut > -----Ursprungliche Nachricht----- > Von: Hartmut Birr [SMTP:har...@te...] > Gesendet am: Donnerstag, 1. November 2001 17:09 > An: 'ros...@re...' > Betreff: [ros-kernel] AW: Re: RE: Re: RE: New ide driver > > The new ide driver fails. > > ... > IDE Driver V0.1.5 > xHalIoReadPartitionTable failed (Status = 0xc000000d) > IoReadPartitionTable() failed > \Device\Harddisk1\Partition1 27MB > \Device\Harddisk1\Partition2 460MB > \Device\Harddisk1\Partition3 496MB > \Device\Harddisk1\Partition4 66MB > xHalIoReadPartitionTable failed (Status = 0xc000000d) > IoReadPartitionTable() failed > No ATA drive 1 found on controller 1... > Did not find any devices for controller 1 > ... > (ke/main.c:472) NtOpenSymbolicLinkObject() '\ArcName\multi(0)disk(0)rdisk(0)partition(1)' failed (Status 0xc0000001) > Bug detected (code 0) > ... > > The old ide driver prints this partition table: > \Device\Harddisk0\Partition1 750MB > \Device\Harddisk0\Partition2 63MB > \Device\Harddisk1\Partition1 27MB > \Device\Harddisk1\Partition2 460MB > \Device\Harddisk1\Partition3 496MB > \Device\Harddisk1\Partition4 66MB > > On the PC are two disks on the first controller and a disk + cdrom at the second. > > - Hartmut > > > > -----Ursprungliche Nachricht----- > > Von: Eric Kohl [SMTP:ek...@rz...] > > Gesendet am: Donnerstag, 1. November 2001 16:32 > > An: ros...@re... > > Betreff: [ros-kernel] Re: RE: Re: RE: New ide driver > > > > > > "Steven Edwards" <Ste...@kn...> wrote: > > > > > > > I have a 30 gig on the secound channel along with my CDrom > > > > Okay, the modifications are in the CVS tree now. It should recognize your 30 > > gig disk but not the cdrom drive. If the harddisk got a fat-partition it > > should be accessible. > > > > - Eric Kohl > > > > > > ==================================================== > > = To remove yourself from this mailing list, go to = > > = http://www.reactos.com/home/mailing.html = > > ==================================================== > > ==================================================== > = To remove yourself from this mailing list, go to = > = http://www.reactos.com/home/mailing.html = > ==================================================== ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-11-01 16:26:48
|
I'm pulling down a clean copy of the CVS tree and doing a full rebuild. I'll email the results tonight. Steven -----Original Message----- From: Eric Kohl To: ros...@re... Sent: 11/1/01 10:31 AM Subject: [ros-kernel] Re: RE: Re: RE: New ide driver "Steven Edwards" <Ste...@kn...> wrote: > I have a 30 gig on the secound channel along with my CDrom Okay, the modifications are in the CVS tree now. It should recognize your 30 gig disk but not the cdrom drive. If the harddisk got a fat-partition it should be accessible. - Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ |
|
From: Hartmut B. <har...@te...> - 2001-11-01 16:12:12
|
The new ide driver fails. ... IDE Driver V0.1.5 xHalIoReadPartitionTable failed (Status = 0xc000000d) IoReadPartitionTable() failed \Device\Harddisk1\Partition1 27MB \Device\Harddisk1\Partition2 460MB \Device\Harddisk1\Partition3 496MB \Device\Harddisk1\Partition4 66MB xHalIoReadPartitionTable failed (Status = 0xc000000d) IoReadPartitionTable() failed No ATA drive 1 found on controller 1... Did not find any devices for controller 1 ... (ke/main.c:472) NtOpenSymbolicLinkObject() '\ArcName\multi(0)disk(0)rdisk(0)partition(1)' failed (Status 0xc0000001) Bug detected (code 0) ... The old ide driver prints this partition table: \Device\Harddisk0\Partition1 750MB \Device\Harddisk0\Partition2 63MB \Device\Harddisk1\Partition1 27MB \Device\Harddisk1\Partition2 460MB \Device\Harddisk1\Partition3 496MB \Device\Harddisk1\Partition4 66MB On the PC are two disks on the first controller and a disk + cdrom at the second. - Hartmut > -----Ursprungliche Nachricht----- > Von: Eric Kohl [SMTP:ek...@rz...] > Gesendet am: Donnerstag, 1. November 2001 16:32 > An: ros...@re... > Betreff: [ros-kernel] Re: RE: Re: RE: New ide driver > > > "Steven Edwards" <Ste...@kn...> wrote: > > > > I have a 30 gig on the secound channel along with my CDrom > > Okay, the modifications are in the CVS tree now. It should recognize your 30 > gig disk but not the cdrom drive. If the harddisk got a fat-partition it > should be accessible. > > - Eric Kohl > > > ==================================================== > = To remove yourself from this mailing list, go to = > = http://www.reactos.com/home/mailing.html = > ==================================================== ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Eric K. <ek...@rz...> - 2001-11-01 15:32:01
|
"Steven Edwards" <Ste...@kn...> wrote: > I have a 30 gig on the secound channel along with my CDrom Okay, the modifications are in the CVS tree now. It should recognize your 30 gig disk but not the cdrom drive. If the harddisk got a fat-partition it should be accessible. - Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-11-01 13:29:34
|
I have a 30 gig on the secound channel along with my CDrom -----Original Message----- From: Eric Kohl To: ros...@re... Sent: 11/1/01 6:31 AM Subject: [ros-kernel] Re: RE: New ide driver "Steven Edwards" <Ste...@kn...> wrote: > It tests fine now. It must of just been some fluke in Vmware. Great! I'll enable the secondary channel and test if it can handle (or ignore) atapi drives properly. Does anyone have a harddisk on the secondary ide channel?? - Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ |
|
From: Hartmut B. <har...@te...> - 2001-11-01 12:59:11
|
> No idea... afaik, this is a bug, CR shouldn't be removed from file > names. If we must also implement this bug, I'd say it should be done in > kernel32. > > At 10:59 PM 10/31/2001 +0100, you wrote: > > > On windows it opens the file with CR in the name, and windows ignores the > > > > > CR and opens the file correctly? > > > >Which part of ROS must remove the 'dummy' names (<CR>, '\.\', \..\, ..') in > >path names. Is this a part for kernel32.dll, for ntoskrnl or for each FSD? The <CR> comes frome msvcrt.dll. fgets doesn't translate from <CR><LF> to <LF>. Each string from fgets ends with <CR>. - Hartmut ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Eric K. <ek...@rz...> - 2001-11-01 11:32:39
|
"Steven Edwards" <Ste...@kn...> wrote: > It tests fine now. It must of just been some fluke in Vmware. Great! I'll enable the secondary channel and test if it can handle (or ignore) atapi drives properly. Does anyone have a harddisk on the secondary ide channel?? - Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Eric K. <ek...@rz...> - 2001-11-01 11:27:02
|
"Phillip Susi" <ps...@cf...> wrote: > I finally updated to the new binary packages on our sorceforge site for gcc > and binutils to get the g++ compiler, but it fails compiling a test app > with the error: > > ld: cannot find -lstdc++ > > Ideas? > Yep! I just had a look at my binary mingw tree. Libstdc++.a exists but 'make bindist' seems to cripple its name. I found 'libstdc++.a.2.10.0' in the lib subdirectory. Rename it to 'libstdc++.a' and everything should be okay. Please, tell me if it works. Guess this is just another makefile bug. :-/ - Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Phillip S. <ps...@cf...> - 2001-11-01 05:16:40
|
I finally updated to the new binary packages on our sorceforge site for gcc and binutils to get the g++ compiler, but it fails compiling a test app with the error: ld: cannot find -lstdc++ Ideas? ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
8 messages has been excluded from this view by a project administrator.
