Alaska Software Inc. - Read Sector via INT25
Username: Password:
AuthorTopic: Read Sector via INT25
AUGE_OHRRead Sector via INT25
on Fri, 11 Aug 2006 07:23:27 +0200
hi,

i have a ASM Source for Cl*pper (protect mode) which use INT25
to read the Sector(Block) of the Harddisk where a given FileName resist.

can i use this ASM Source for Xbase++ ? if yes how ?

greetings by OHR
Jimmy
G. HenzlerRe: Read Sector via INT25
on Fri, 11 Aug 2006 09:23:31 +0200
No good Idea, i think we passed beyond FAT32 .... Now we have NTFS and 
stronger security on the PC.

Mfg

G. Henzler

"AUGE_OHR" <AUGE_OHR*AT*CSI.COM> schrieb im Newsbeitrag 
news:23572252$332c7863$119f7@news.alaska-software.com...
> hi,
>
> i have a ASM Source for Cl*pper (protect mode) which use INT25
> to read the Sector(Block) of the Harddisk where a given FileName resist.
>
> can i use this ASM Source for Xbase++ ? if yes how ?
>
> greetings by OHR
> Jimmy
>
>
Phil Ide
Re: Read Sector via INT25
on Fri, 11 Aug 2006 15:25:42 +0100
AUGE_OHR,

> i have a ASM Source for Cl*pper (protect mode) which use INT25
> to read the Sector(Block) of the Harddisk where a given FileName resist.
> 
> can i use this ASM Source for Xbase++ ? if yes how ?

CMD.EXE provides a layer for interrupt calls which invokes Win32API
functions which handle the same tasks. However, there are several caveats,
chief of these are:

1. CMD only supports DOS 6.2, and not all interrupts or sub-functions are
recognised (e.g. INT21/60h LFN support from Win95 is not available).

2. Some interrupt calls are only supported through the 16-bit layer and are
not available to 32-bit code.

Using NASM, you can mix 16-bit code with 32-bit code, but this requires a
good understanding of what you are doing. Converting code from MASM or TASM
to NASM also requires a good understanding of assembly AND the assembler the
code was written for - NASM generates EXACTLY the code you write, whereas
MASM and TASM attempt to re-write the code to generate what it hopes is an
optimised version of what it thinks you wanted.

Writing NASM code for Xbase++ is extremely trivial, but not for the
inexperienced or faint-hearted.

Windows access the HD via the IOCTL API, which is documented in the Platform
SDK under:
    System Services
       Device I/O
          Device Management
             Device Management Reference

Regards,

Phil Ide

-----------------------------------------------------------------
xbHCL (http://www.xbHCL.com)     Xbase++ HTML command layer
PBIH  (http://www.pbih.eu)       Polar Bear International Hosting
-----------------------------------------------------------------
Xbase++ FAQ, Libraries and Sources:
http://www.idep.org.uk/xbase

Better living through alchemy.