Win95 DOS Call: Difference between revisions

improve introduction
[unchecked revision][unchecked revision]
No edit summary
 
(improve introduction)
 
(2 intermediate revisions by 2 users not shown)
Line 1:
{{Stub}}
Windows '95, while not precisely a disk image utility itself, gives a programmer an easy access method for reading and writing data from/into disk image files. This comes from the total lack of security features in Win95. The method is the DOS interrupt call: INT21h, ax=0x7305. This might make Win95 a better choice for an OS development platform than Win98.
 
Windows '95, while not precisely a disk image utility itself, gives a programmer an easy access method for reading and writing data from/into disk image files. This comes from the total lack of security features in Win95the OS. The method is the DOS interrupt call: INT21h, ax=0x7305. This might make Win95Windows 95 a better choice for an OS development platform than Win98Windows 98.
 
==Usage==
The main reason to be working with disk images when doing OS development is that they are needed for [[emulators]] such as [[Bochs]]. If you are using a non-standard FileSystem[[filesystem]] in the emulator, then you must use a disk HexEditor[[hexeditor]], or read and write sectors in your disk image file directly, because no host OS will recognize your non-standard filesystem.
 
This interrupt call gives a programmer a method to read and write logical disk sectors. You need to use some utility to find the sector location on your disk partition of your disk image.
Line 9 ⟶ 11:
 
Set si to 0x6001 for a write, or 0 for a read. cx = 0xffff, ds:bx points to the DISKIO structure, dl = logical drive letter (1= A, 2= B, ... ), ax = 0x7305. Then do an INT 0x21.
 
 
{{Stub}}
 
[[Category:Disk Image Utilities]]
[[Category:Windows]]
Anonymous user