[Coco] 6309 microproccessor project - win32 Functions

[Roger Taylor]

It looks like your set of Win32 API functions will allow a gateway between 
the emulated CoCo and the PC file system.  Is this the idea?


At 09:49 AM 10/13/2003 -0400, you wrote:
>Hello,
>
>The list of win 32 functions I have for special opcode for $11FD should be 
>enough functions for manipulating files in windows. You'll recall that you 
>used special opcode $11FD by supplying a opcode that is the msdos int 21 
>function you wanted. You also put any values you needed for the particular 
>msdos int 21 function you were calling. I have changed it to use win32 
>functions instead of msdos int 21. You supply the function opcode as 
>before; however, this opcode only applies to the function opcode list that 
>I supply. You also have to use the registers to pass certain parameters 
>that the win32 functions need. Sometimes you'll need to pass pointers to 
>strings and sometimes you'll pass 16 bit values that will be expanded to 
>32 bits for you. These 16 bit values are used for handles, attributes, 
>flags, and etc. I'll supply all the necessary parameters you'll need and 
>info on how to setup and call each win32 function by using special opcode 
>$11FD.
>
>The win32 functions:
>
>CloseHandle
>CopyFile
>CreateDirectory
>CreateFile
>DeleteFile
>FindClose
>FindFirstFile
>FindNextFile
>FlushFileBuffers
>GetCurrentDirectory
>GetDiskFreeSpace
>GetFileAttributes
>GetFileSize
>GetFileTime
>GetFullPathName
>GetLastError
>GetLongPathName
>GetShortPathName
>GetTempFileName
>GetTempPath
>OpenFile
>ReadFile
>RemoveDirectory
>SearchPath
>SetCurrentDirectory
>SetEndOfFile
>SetFileAttributes
>SetFilePointer
>SetFileTime
>WriteFile
>As you can see this list covers a lot and you should easily be able to 
>manipulate files in windows with them.
>
>More to come later;
>
>John Collyer.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://five.pairlist.net/pipermail/coco/attachments/20031013/59d8cf31/attachment-0001.html>