About wfc

1. What is wfc?
It is a simple Win32 emulator, in order to run simple 32 bit >>TEXTMODE<<
programs for Windows 95/Windows NT. 


2. What are the things wfc cannot do:
   - windowing
   - graphics
   - multithreading				[*]
   - unicode         				[*]                    
   - networking        				[* (sockets)]                  
   - OLE
   - TAPI/MAPI
   - advanced interprocess communication	[*]
   - real WinNT security
   and much more

[*]: these features are planned in future releases

3. What are the features planned before calling it "beta".
 These are the API areas I want to have implemented, before jumping the
 version number to 1.0:
   - Virtual memory functions                    [v]
        VirtualAlloc, VirtualFree, VirtualProtect, VirtualQuery
   - Heap functions (Heap/Global/Local)
        HeapCreate, HeapAlloc, HeapFree, HeapDestroy, 
        GlobalAlloc, GlobalLock, GlobalUnlock, GlobalFree,
        LocalAlloc, LocalLock, LocalUnlock, LocalFree,
        GetProcessHeap				 
   - Basic filesystem functionality              [v]
   - Mapping files in virtual memory
   - Registry / .INI-file functions
   - Basic memory/string/time library functions  [v]
   - National Language Support			 [v]


4. Who is making wfc?

My name is Onno Hovers. I am reachable by e-mail. My current address is:
onno@stack.urc.tue.nl. 
I have started wfc, because I wanted to run the 32 bit Borland C++ command 
line tools under Linux. 

5. Where does the name 'wfc' come from. 
- "WinFree" Console.

6. Why the LGPL ?

I have not chosen for the plain GPL because I wanted to be able to 
make a portability library in the future. 

The LGPL protects me, the author, of any liability as applicable by law. 
It also ensures that anything derived from wfc remains under the LGPL.
