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: Steven E. <Ste...@kn...> - 2001-10-15 04:08:28
|
Using TWIN might work well for us for the WOW support. From what I have seen the the docs its very portable (POSIX and Mac 9.x systems) right now it just supports a x11driver and Mac Display driver, but rewriting it to be compatible with the ReactOS GDI souldnt be to hard. Making it a NT 4 compatible DOS VDM will be a lot harder. Eric and I we're discussing this earlier and porting the dlls from wine seems to be the best bet. I started looking in to this a week or to ago, but could only get about 20% of comctl32 to compile. Mostly due to unicode support issues. |
|
From: Phillip S. <ps...@cf...> - 2001-10-15 04:00:51
|
I'm working on getting the kernel debugger to use the COFF or CV4 debugging information in the image files instead of loading and parsing text .sym files. This should make it more useful for debugging. I can't find where MS has hidden their documentation on the PE file, COFF, and CV4 formats, does anyone know where they put it? ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-10-15 03:38:35
|
What is the syntax for building a static lib (not a dll) in a reactos makefile? |
|
From: James B. <ja...@dr...> - 2001-10-15 03:23:16
|
Nothing that I am aware of. I was looking at the TWIN as a source of missing DLL's for ReactOS. As I was familiar with ComCtl32 so I tried compiling it into the ReactOS source tree first. I am not trying to implement dos compatibility, but rather porting functional units I can test on m$ nt for basic compatibility, then under ReactOS building required functionality as necessary. Sorry for the confusion, James -----Original Message----- From: Phillip Susi [mailto:ps...@cf...] Sent: Sunday, October 14, 2001 10:50 PM To: ros...@re... Subject: [ros-kernel] Re: TWIN + ComCtl32 What does dos emulation have to do with comctl32? At 10:44 PM 10/14/2001 -0400, you wrote: >Good Evening All, > > I downloaded the TWIN source Steven mentioned and with a bit of > coaxing, >got ComCtl32 to compile. TWIN is GPL so I don't see any problem using the >code in ReactOS. I am going to play with some of the TWIN DLLs that are not >yet implemented in ReactOS. If I can get them working, I'll submit them for >your approval. I realize that it is premature to work on GUI code when >there remains much to be done in the kernel, but I have only written a >couple of NT drivers, and don't have the experience to code on that level. > >James ==================================================== = 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: Phillip S. <ps...@cf...> - 2001-10-15 03:01:18
|
What does dos emulation have to do with comctl32? At 10:44 PM 10/14/2001 -0400, you wrote: >Good Evening All, > > I downloaded the TWIN source Steven mentioned and with a bit of > coaxing, >got ComCtl32 to compile. TWIN is GPL so I don't see any problem using the >code in ReactOS. I am going to play with some of the TWIN DLLs that are not >yet implemented in ReactOS. If I can get them working, I'll submit them for >your approval. I realize that it is premature to work on GUI code when >there remains much to be done in the kernel, but I have only written a >couple of NT drivers, and don't have the experience to code on that level. > >James ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: James B. <ja...@dr...> - 2001-10-15 02:47:54
|
Good Evening All, I downloaded the TWIN source Steven mentioned and with a bit of coaxing, got ComCtl32 to compile. TWIN is GPL so I don't see any problem using the code in ReactOS. I am going to play with some of the TWIN DLLs that are not yet implemented in ReactOS. If I can get them working, I'll submit them for your approval. I realize that it is premature to work on GUI code when there remains much to be done in the kernel, but I have only written a couple of NT drivers, and don't have the experience to code on that level. James ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-10-15 01:10:10
|
Hola Folks, I know this is no where near top on the list of things to add to ROS, but I think I found a solution. A few weeks ago there was a thread discussing using dosemu for the 16bit WOW emulation, but that idea was droped because of the work need to port dosemu. I suggest we look a TWIN. http://www.willows.com/ It has a subset of dosemu for running 16 bit applications (dos/win16) on a large varity of systems. Check out the intp32 and the msdos lib. I think this could be what we will need. As far as making it 100% compatibly with the NT WOW subsystem, I dont think this should be a priority for the first release of ReactOS if ever. This should be looked at soon though, because if some company is still running dos/win16 apps then mabey this type of support would encorage moving off of 9x/NT and on to ReactOS. Steven |
|
From: <jim...@ad...> - 2001-10-15 00:45:15
|
Sorry I need to check this ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Phillip S. <ps...@cf...> - 2001-10-15 00:31:22
|
You didn't happen to also fix the bug that prevents it from generating binary output so we don't have to have djgpp to compile freeloader did you? ;) At 01:52 AM 10/15/2001 +0200, you wrote: >Hi! > >Today I wanted to publish a new gcc and binutils release. Instead of just >doing that I fixed a few older bugs in ld and sent the patches to Danny >Smith (MinGW maintainer). The ld-patch allows the creation of dll's using >'gcc -shared ...'. When fastcall functions were exported, the created dll >was broken. > >If the patches are okay and Danny doesn't find any more bugs, he will >publish a new MinGW release and the fastcall-feature will finally be >official. :-)) > >I hope you don't mind the delay, > >Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Eric K. <ek...@rz...> - 2001-10-15 00:17:25
|
Hi! Today I wanted to publish a new gcc and binutils release. Instead of just doing that I fixed a few older bugs in ld and sent the patches to Danny Smith (MinGW maintainer). The ld-patch allows the creation of dll's using 'gcc -shared ...'. When fastcall functions were exported, the created dll was broken. If the patches are okay and Danny doesn't find any more bugs, he will publish a new MinGW release and the fastcall-feature will finally be official. :-)) I hope you don't mind the delay, Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Phillip S. <ps...@cf...> - 2001-10-14 23:10:18
|
Who was it that recently did some work with the cache manager code? Are
you still working on it? The Cc code needs to be reworked to use mapped
section views like NT does instead of CACHE_SEGMENTs. Currently, trying to
copy a file on a machine with 8 megs of ram causes the cache to use all
available memory, run out, and then the system locks up. This is due to
several reasons, the first being that the cache does not currently have any
mechanism to prevent it from growing without bound. The cache needs to map
views of the files to be cached into the cache working set, and the working
set and page fault handling code will keep the cache working set from
growing without bound, as well as reclaiming cache memory. The other bug
in the current code is in cc/view.c in CcRosGetCacheSegment, which does this:
Status = MmCreateVirtualMapping(NULL,
current->BaseAddress + (i * PAGESIZE),
PAGE_READWRITE,
(ULONG)MmAllocPage(0));
Note that the call to MmAllocPage is not checked for failure. On my test
system, it fails when memory runs out, and returns 0, which then gets
passed to MmCreateVirtualMapping for the physical backing page. If noone
is working on this, I guess I'll go for it, but if someone already is, let
me know.
====================================================
= To remove yourself from this mailing list, go to =
= http://www.reactos.com/home/mailing.html =
====================================================
|
|
From: Brian P. <br...@sg...> - 2001-10-14 21:44:12
|
One more thing -- after this jump is made you have to make sure you're not trying to run 16-bit code in a 32-bit code segment. Brian -----Original Message----- From: Brian Palmer [mailto:br...@sg...] Sent: Sunday, October 14, 2001 1:19 AM To: ros...@re... Subject: [ros-kernel] RE: RE: Re: RE: Re: RE: Re: Old reactos You might try changing the jump instruction into a jump far instruction. This would both clear the prefetch queue and set the CS register to it's correct selector. You also might try removing jump instructions altogether because if I remember correctly there are only a few instructions between the time pmode is initialized and control is transferred to ReactOS. So clearing the prefetch queue is really not neccesary. The more I think about it however the more I dislike the idea of any jump instructions being there at all because if you did do a far jump you would need to calculate the 32-bit offset from the selector's base which makes it overly complex (just like this huge run-on sentence). Hope this helps. Brian -----Original Message----- From: Jurgen Van Gael [mailto:jur...@st...] Sent: Wednesday, October 10, 2001 1:08 PM To: ros...@re... Subject: [ros-kernel] RE: Re: RE: Re: RE: Re: Old reactos Sorry, I tried this but the system still reboots. This is getting a very anoying problem because I can't test the work I have done for reactos (ole32). Has anybody got freeloader, and would that work loading reactos on my system. The thing is I don't know enough assembler to solve the problem on my own. Hoping for a quick solution. Jurgen -----Original Message----- From: rene Tournois @free.fr [mailto:be...@fr...] Sent: Wednesday, October 10, 2001 19:36 To: ros...@re... Subject: [ros-kernel] Re: RE: Re: RE: Re: Old reactos Try to insert a couple of NOP between the Label declaration and the jump instruction. If i remember well, there a little bug in NASM about this... (unsure, but no relationship with the prefetch anyway). Betov. >I am very sorry, I also had to change the .exit to exit because >otherwise nasm wouldn't build loadros. > >And still the system reboots, but I can now put the loop after next: > mov eax,cr0 > or eax,0x10001 > mov cr0,eax > jmp next >next: >break: > jmp break > ;; > ;; NOTE: This must be position independant (no references to > ;; non absolute variables) > ;; > > ;; > ;; Initalize segment registers > ;; > mov ax,KERNEL_DS > mov ds,ax > mov ss,ax > mov es,ax > mov fs,ax > mov gs,ax > > >If I put the break after mov gs, ax though, the system reboots. > > >Jurgen > >-----Original Message----- >From: Casper Hornstrup [mailto:ch...@us...] >Sent: Wednesday, October 10, 2001 15:56 >To: ros...@re... >Subject: [ros-kernel] Re: RE: Re: Old reactos > > >On Wednesday 10 October 2001 00:40, Jurgen Van Gael wrote: >> When I use the loop in loadros.asm, I get these results: >> >> If I put the break here: >> >> ;; >> ;; Enter pmode and clear prefetch queue >> ;; >> mov eax,cr0 >> or eax,0x10001 >> mov cr0,eax >> .break: >> jmp .break >> jmp .next >> .next: >> >> Then the system freezes with a blue screen >> >> When I put the loop after jmp .next, the system reboots. >> >> Am I right we are talking pmode right now. Could it be that the gdt >> or > >> idt is not setup properly? > >Try changing: > >jmp .next >.next: > > >to: > >jmp next >next: > >IIRC, it should be a far jump to clear the prefetch queue. > >- Casper > >==================================================== >= 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 = ==================================================== ==================================================== = 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: Phillip S. <ps...@cf...> - 2001-10-14 15:17:02
|
Allocating 0 bytes is a useful idiom, and the alloc code handles it by returning 0. If you are going to allocate 0 bytes, you need to be able to free it as well. I fixed this because it was causing a crash in the xhal drive letter assignment code. I suppose you could choose some other invalid pointer value to return for 0 byte allocations and frees if you wanted to. I'm not sure what NT does in this case, but user mode malloc/free new/delete in C/C++ is required to accept this. At 01:21 AM 10/14/2001 -0600, you wrote: >Is it not a bug when kernel mode code trys to free a NULL pointer? Does this >call work under NT? > >Brian > >-----Original Message----- >From: Phillip Susi [mailto:ph...@mo...] >Sent: Saturday, September 29, 2001 12:41 PM >To: ros...@re... >Subject: [ros-cvs-commit] CVS Update: reactos > > >CVSROOT: /CVS/ReactOS >Module name: reactos >Repository: reactos/ntoskrnl/mm/ >Changes by: phreak@mok. 01/09/29 12:40:49 > >Modified files: > reactos/ntoskrnl/mm/: npool.c > >Log message: > Do not bugcheck on ExFreePool( 0 ) ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Brian P. <br...@sg...> - 2001-10-14 07:23:33
|
Is it not a bug when kernel mode code trys to free a NULL pointer? Does this call work under NT? Brian -----Original Message----- From: Phillip Susi [mailto:ph...@mo...] Sent: Saturday, September 29, 2001 12:41 PM To: ros...@re... Subject: [ros-cvs-commit] CVS Update: reactos CVSROOT: /CVS/ReactOS Module name: reactos Repository: reactos/ntoskrnl/mm/ Changes by: phreak@mok. 01/09/29 12:40:49 Modified files: reactos/ntoskrnl/mm/: npool.c Log message: Do not bugcheck on ExFreePool( 0 ) ==================================================== = 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: Brian P. <br...@sg...> - 2001-10-14 07:20:22
|
You might try changing the jump instruction into a jump far instruction. This would both clear the prefetch queue and set the CS register to it's correct selector. You also might try removing jump instructions altogether because if I remember correctly there are only a few instructions between the time pmode is initialized and control is transferred to ReactOS. So clearing the prefetch queue is really not neccesary. The more I think about it however the more I dislike the idea of any jump instructions being there at all because if you did do a far jump you would need to calculate the 32-bit offset from the selector's base which makes it overly complex (just like this huge run-on sentence). Hope this helps. Brian -----Original Message----- From: Jurgen Van Gael [mailto:jur...@st...] Sent: Wednesday, October 10, 2001 1:08 PM To: ros...@re... Subject: [ros-kernel] RE: Re: RE: Re: RE: Re: Old reactos Sorry, I tried this but the system still reboots. This is getting a very anoying problem because I can't test the work I have done for reactos (ole32). Has anybody got freeloader, and would that work loading reactos on my system. The thing is I don't know enough assembler to solve the problem on my own. Hoping for a quick solution. Jurgen -----Original Message----- From: rene Tournois @free.fr [mailto:be...@fr...] Sent: Wednesday, October 10, 2001 19:36 To: ros...@re... Subject: [ros-kernel] Re: RE: Re: RE: Re: Old reactos Try to insert a couple of NOP between the Label declaration and the jump instruction. If i remember well, there a little bug in NASM about this... (unsure, but no relationship with the prefetch anyway). Betov. >I am very sorry, I also had to change the .exit to exit because >otherwise nasm wouldn't build loadros. > >And still the system reboots, but I can now put the loop after next: > mov eax,cr0 > or eax,0x10001 > mov cr0,eax > jmp next >next: >break: > jmp break > ;; > ;; NOTE: This must be position independant (no references to > ;; non absolute variables) > ;; > > ;; > ;; Initalize segment registers > ;; > mov ax,KERNEL_DS > mov ds,ax > mov ss,ax > mov es,ax > mov fs,ax > mov gs,ax > > >If I put the break after mov gs, ax though, the system reboots. > > >Jurgen > >-----Original Message----- >From: Casper Hornstrup [mailto:ch...@us...] >Sent: Wednesday, October 10, 2001 15:56 >To: ros...@re... >Subject: [ros-kernel] Re: RE: Re: Old reactos > > >On Wednesday 10 October 2001 00:40, Jurgen Van Gael wrote: >> When I use the loop in loadros.asm, I get these results: >> >> If I put the break here: >> >> ;; >> ;; Enter pmode and clear prefetch queue >> ;; >> mov eax,cr0 >> or eax,0x10001 >> mov cr0,eax >> .break: >> jmp .break >> jmp .next >> .next: >> >> Then the system freezes with a blue screen >> >> When I put the loop after jmp .next, the system reboots. >> >> Am I right we are talking pmode right now. Could it be that the gdt >> or > >> idt is not setup properly? > >Try changing: > >jmp .next >.next: > > >to: > >jmp next >next: > >IIRC, it should be a far jump to clear the prefetch queue. > >- Casper > >==================================================== >= 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 = ==================================================== ==================================================== = 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: Brian P. <br...@sg...> - 2001-10-14 06:37:32
|
In Microsofts published FAT spec it says: " FAT32ClusEntryVal = (*((DWORD *) &SecBuff[ThisFATEntOffset])) & 0x0FFFFFFF; Note how the FAT32 code above works. A FAT32 FAT entry is actually only a 28-bit entry. The high 4 bits of a FAT32 FAT entry are reserved. The only time that the high 4 bits of FAT32 FAT entries should ever be changed is when the volume is formatted, at which time the whole 32-bit FAT entry should be zeroed, including the high 4 bits. A bit more explanation is in order here, because this point about FAT32 FAT entries seems to cause a great deal of confusion. Basically 32-bit FAT entries are not really 32-bit values; they are only 28-bit values. For example, all of these 32-bit cluster entry values: 0x10000000, 0xF0000000, and 0x00000000 all indicate that the cluster is FREE, because you ignore the high 4 bits when you read the cluster entry value. If the 32-bit free cluster value is currently 0x30000000 and you want to mark this cluster as bad by storing the value 0x0FFFFFF7 in it. Then the 32-bit entry will contain the value 0x3FFFFFF7 when you are done, because you must preserve the high 4 bits when you write in the 0x0FFFFFF7 bad cluster mark." I don't know what these bits mean, but they should be ignored. Brian -----Original Message----- From: David Welch [mailto:we...@cw...] Sent: Wednesday, October 03, 2001 12:48 PM To: ros...@re... Subject: [ros-kernel] Re: AW: problem with fat32 On Wed, Oct 03, 2001 at 07:38:52PM +0200, Hartmut Birr wrote: > This problem comes from ROS. FAT32WriteCluster writes a cluster > number to the fat. When the value is 0xffffffff (last cluster), the higher > 4 bits are set. Win9x does ignore this bits. > Linux does too. ==================================================== = 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: Chris H. <ho...@pl...> - 2001-10-14 04:02:01
|
This is just a question about ReactOS in general. Does ReactOS plan to have a Graphical User Interface like Micro$oft Windows 98? Does it plan to have the ability to load all WIN32 applications? If so what is the current progress of this project? I am only asking this because when XP is released are you going to add support to whatever XP has to offer? See ya! Sincerely, Chris Hocking (ho...@pl...) ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Jason F. <jas...@ya...> - 2001-10-13 21:26:44
|
Would the FSF really _want_ copyright of ReactOS code if this is the case? It may be easier and more convient for everyone to set up a seperate legal entity to take the fall if it happens. - Jason --- Richard Campbell <rc...@ca...> wrote: > Microsoft would drag you guys through court because they KNOW it > would kill > the project. The financial drain from court costs, etc. would > probably > cause most developers to leave the project. Personally I hope this > never > happens, because as I said before, ROS will replace Windows, mark > my words. > :) > > ----- Original Message ----- > From: "Rex Jolliff" <re...@lv...> > To: <ros...@re...> > Sent: Friday, October 12, 2001 5:46 PM > Subject: [ros-kernel] Re: RE: Re: Legal... > > > > At 09:52 AM 10/12/01 -0400, you wrote: > > >I'm not a lawyer and don't pretend to be one but I simply fail > to see how > M$ > > >have any legal standing. That's like Ford suing Chrysler for > copying the > > >automobile. Is it not? > > > > > >After all, M$ literally copied the Window concept from Xerox and > MS-DOS > was > > >a derivative of CP/M which they purchased and copied. > > > > I am sure that Microsoft believes they have hundreds of patents > on > > technology in the > > NT operating system. It does not matter than those patents are > bogus, one > > would > > have to defend oneself against them all the same and expend > scarce > > resources doing > > so. > > > > > > Rex Jolliff > > re...@lv... > > > > ==================================================== > > = 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 = > ==================================================== > __________________________________________________ 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: Richard C. <rc...@ca...> - 2001-10-13 17:44:17
|
Microsoft would drag you guys through court because they KNOW it would kill the project. The financial drain from court costs, etc. would probably cause most developers to leave the project. Personally I hope this never happens, because as I said before, ROS will replace Windows, mark my words. :) ----- Original Message ----- From: "Rex Jolliff" <re...@lv...> To: <ros...@re...> Sent: Friday, October 12, 2001 5:46 PM Subject: [ros-kernel] Re: RE: Re: Legal... > At 09:52 AM 10/12/01 -0400, you wrote: > >I'm not a lawyer and don't pretend to be one but I simply fail to see how M$ > >have any legal standing. That's like Ford suing Chrysler for copying the > >automobile. Is it not? > > > >After all, M$ literally copied the Window concept from Xerox and MS-DOS was > >a derivative of CP/M which they purchased and copied. > > I am sure that Microsoft believes they have hundreds of patents on > technology in the > NT operating system. It does not matter than those patents are bogus, one > would > have to defend oneself against them all the same and expend scarce > resources doing > so. > > > Rex Jolliff > re...@lv... > > ==================================================== > = 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: Phillip S. <ps...@cf...> - 2001-10-13 17:22:54
|
If there is a reason to break binary compatibility, then sure, I'm all for it, but if the NT way is good enough, we might as well be compatible with it not so that both OSes can share the same working hives, but so one can create and manipulate hives for the other to use. For instance, it might be nice to have a ReactOS boot disk that could be used to repair registry hives on an NT system. Of course, this is not of primary importance, so if there is a way to improve on the file layout that breaks compatibility, then so be it. At 03:43 PM 10/12/2001 -0700, you wrote: >At 02:43 PM 10/12/01 -0400, you wrote: >>Is it just in memory, or does it save them to an on disk hive? And if >>so, is this hive binary compatible with NT? > >It should not be binary compatible with NT hives. I cannot think of a >situation where >the same hive files could be used in two different OS installations, and >making >it binary compatible just for the sake of compatibility may mean sacrificing >performance or reliability. I think we sometimes lose focus of our primary >mission >and get carried away with making an exact copy of NT. Lets make it better and >not just a copy. > > >Rex Jolliff >re...@lv... ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Hartmut B. <har...@te...> - 2001-10-13 06:55:13
|
> I do believe that it only creates empty files, but I haven't played with > persistent registry entries. IIRC, much code for saving hives is there, but I > remember seeing an old comment, in the code for the configuration manager, > about the vfat driver not beeing able to create new files. The vfat driver can create new files. On booting, ROS creates some files in reactos\system32\config. Hartmut ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Rex J. <re...@lv...> - 2001-10-12 23:45:26
|
At 09:52 AM 10/12/01 -0400, you wrote: >I'm not a lawyer and don't pretend to be one but I simply fail to see how M$ >have any legal standing. That's like Ford suing Chrysler for copying the >automobile. Is it not? > >After all, M$ literally copied the Window concept from Xerox and MS-DOS was >a derivative of CP/M which they purchased and copied. I am sure that Microsoft believes they have hundreds of patents on technology in the NT operating system. It does not matter than those patents are bogus, one would have to defend oneself against them all the same and expend scarce resources doing so. Rex Jolliff re...@lv... ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Rex J. <re...@lv...> - 2001-10-12 23:36:56
|
At 02:43 PM 10/12/01 -0400, you wrote: >Is it just in memory, or does it save them to an on disk hive? And if so, >is this hive binary compatible with NT? It should not be binary compatible with NT hives. I cannot think of a situation where the same hive files could be used in two different OS installations, and making it binary compatible just for the sake of compatibility may mean sacrificing performance or reliability. I think we sometimes lose focus of our primary mission and get carried away with making an exact copy of NT. Lets make it better and not just a copy. Rex Jolliff re...@lv... ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: GenesisXG <Gen...@we...> - 2001-10-12 21:55:10
|
whats is with the little shell? everybody will help with the shell please send mail to: Gen...@we... my ReactOS page will sonn go online (1-2 weeks) greats GenesisXG |
|
From: Andrew W. <an...@ds...> - 2001-10-12 20:11:33
|
This is way off topic, but.. No, that was trademark, and I think they dropped the application. In that case they had a point though, every other major bike maker was coming out with a big V-twin engined cycle to try and take some of the market from Harley. That is what trademark is all about, protecting a business image and brand. However, I don't think anyone is going to argue that Harley was pushing the edge of the envelope trying to protect their marketshare. But trademark is very different than copyright. For trademark infringment the general rule is, is it a unique business "mark" and are consumers likely to be confused if that "mark" starts showing up on a competitor's stuff. For copyright, its was someone's "original" work (as in new to this world) "copied". As I understand it, the stuff in that work that is not new they generally don't have a huge claim to, as it is "old" or is considered a generally used technique. As ReactOS is not an exact copy of NT I think MS is going to have some problems, much like AT&T/USL (the owners of original Unix) did when the BSD4.4 code was released. --Andrew (another list lurker) > This reminds me of a case where Harley Davidson tried to copyright the sound > of their bikes. I never knew what happen (did it go to court? If so, what > was the outcome?) As if to say the sound was exactly the same on every bike > produced and that it encourage awesome innovation to the point they needed > to protect it saying it was from their custom engine designs bla bla bla. > Its like saying Honda built their bike engines based on the sound that > Harley's made? As John Stossel would say, Give me a break. ==================================================== = 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.
