Autodoc updated.
[AROS.git] / tools / adflib / Win32 / readme_win32.html
blob7df53051dcf24a2cf67b09e2d6475d7bf77200bf
1 <html>
2 <head>
3 <title>Untitled Document</title>
4 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5 </head>
7 <body bgcolor="#FFFFFF">
8 <h1>Readme file for ADFLib on Win32</h1>
9 <p>
10 <p>This file contains additional information on using ADFLib under 32-bit Windows.
11 See the main library documentation for more general info.
12 <h2>Compiling the library on Win32 platforms</h2>
13 <p>The ADFLib distribution contains a two makefiles for nmake:
14 <p><b>Win32Lib.mak</b><br>
15 Compiles the ADFLib as a static library. To use it, simply link your program
16 with adflib.lib and #include adflibusr.h.
17 <p><b>Win32DLL.mak</b><br>
18 Compiles ADFLib as a DLL. This will produce the files ADFLib.dll, ADFLib.lib
19 (the import library to link with your
20 <p>Both makefiles contain debug and release targets. To specify which one to use,
21 use a command line like this:
22 <pre>NMAKE /f "ADFLib.mak" CFG="ADFLib - Win32 Release"</pre>
23 <p>The makefiles will produce a debug version of the library by default if no
24 configuration is specified.
25 <h2>The Win32 native functions</h2>
26 <p>When ADFLib is compiled under Win32, the Win32 native functions will be linked,
27 allowing you to access Amiga harddisks directly in Windows. Current only Windows
28 NT is supported - support for Windows 95 and 98 is in the pipeline.
29 <p>For the direct drive access routines to work under Windows NT, you need administrative
30 priviledges. This is a security feature of Windows NT and there is no way around
31 it.
32 <p>To open a physical device, simply use the following format as the filname:
33 <pre>|Hx</pre>
34 <p>Where x is the ID of the drive to mount. Example:
35 <pre>hd = adfMountDev(&quot;|H1&quot;);</pre>
36 <p>Your system boot device always has an ID of 0. Attempting to mount it is not
37 a good idea!
38 <p>&nbsp;
39 </body>
40 </html>