Bernd Blaauw wrote:
> Christian Masloch schreef:
>   
>> Since disassembling MS-DOS is "considered legal" by UDOS and RBIL authors  
>> (and these sources are "considered legal" by all members of the FreeDOS  
>> project) I think there's no problem using some DLL examination tool.
>>
>> Regards,
>> Christian
>>   
>>     
> I hope you have heared about the term "clean room implementation" where 
> one team does the research and writes a specification, and another team 
> writes an implementation based on the specification. That way you never 
> violate anyone's copyright, patents etc.
> Reverse engineering is considered illegal in many countries (DMCA 
> anyone, US folks?). I assume RBIL forms the specification of interfaces, 
> upon which you can build an implementation if you want.
I'm not talking about disassembling the code. I talking about finding 
out what the methods are. Visual Studio does it to do intellisence etc. And I 
believe the tool
was provided by Visual C++ 6. I don't want the code for the functions/methods. 
Just what methods
there are and what the parameters are. I can write the internal code myself.

> I guess the only allowed tools are debuggers for virtual machines, and 
> general debuggers like SoftIce, just to see how software *interacts* 
> with Microsoft copyrighted products.
>
> As for running Windows 3.1 on FreeDOS, it's possible. Jeremy Davis 
> managed to do so once a few years ago. Seems like his FDOS.ORG website 
> has expired by now though.
> Requirements:
> * kernel 2037, specific compiled flavour of it though
> * Share, specific compiled flavour. Not sure if it's the FreeDOS one, or 
> the one by Michael Devore, or Japheth, or whoever.
> * MS memory drivers I think (HIMEM)
> * FAT16
>   
I would prefer to keep the environments separate. For comparisons etc.  
I have already
gotten the dual boot MSDOS\FreeDos working (just looking on a linux 
desktop that the laptop will run)
>
> Speaking of ReactOS, I think they have dropped their 486-compatibility, 
> but still that OS should work on anything which is i80586-compatible (or 
> newer/later). Recent fixes have brought the memory consumption back to 
> about 32MB.
>   
I am hoping that the 486 & 16bit code will be available in older 
versions of the source code.
I am thinking though it it may be easier to make a 32 bit app that looks 
like Win 3.x that can run 16 and 32 bit applications.
Than to make a complete clone.






------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to