Mail Archives: djgpp/2008/02/27/18:30:11
Rod Pemberton wrote:
> "Jim Michaels" <jmichae3REMOVE AT THISPLEASEyahoo DOT com> wrote in message
> news:DJmdnQRh5IpcQ17anZ2dnUVZ_o6knZ2d AT comcast DOT com...
>> Jim Michaels wrote:
>>> does gcc handle a 64-bit int in 2.03? if so, what type is it called?
>>>
>>> I was hoping to see if I could rewrite the existing biosdisk library
>>> with the new int13h extensions (as of 1995).
>>>
> http://www.phoenix.com/NR/rdonlyres/9BEDED98-6B3F-4DAC-BBB7-FA89FA5C30F0/0/specsedd11.pdf
>>> contains a reference to these, which refer to LBA methods of accessing
>>> the disk as well as chs, but using subfunctions 41-4e, and there is an
>>> eject media check function in int 15h. similar documents exist.
>>>
>>> biosdisk.c contains code that is now out of date for modern sized disks.
>> I found out that 64-bit int type is long long.
>>
>> as for the replacement for biosdisk.c, I am running into troubles. it
>> seems everything revolves around the Disk Packet, which is a structure
>> of size 16 bytes.
actually now it's 32 bytes with the upcoming standard by the T13 group.
>>
>> the problem is, the go32 libraries seem (?) to only allow allocation and
>> use of 1 block of dos memory at a time. I need 2: 1 for the Disk
>> Packet, and 1 for the disk buffer the Disk Packet points to...
>>
>> so what do I do now?
>>
>> it compiles now, but that's about it. testing reveals it doesn't work.
>> However, I do know that the interrupts themselves do work. it's my
> code.
>
> Chris Giese's DJGPPLBA shows how to implement int13h ah=0x41,0x42,0x43.
> http://my.execpc.com/CE/AC/geezer/software/djgpplba.c
I noticed it didn't allocate any DOS memory with
__dpmi_allocate_dos_memory() before it did its thing with dosmemput().
and yet it worked. does that mean I can do this too, or is this a bad
practice?
my current code which the C++ classes sort of works and sort of doesn't
is posted at http://jesusnjim.com/z/rattledisk-1.4.zip
it also includes just plain old BIOS level DIY straight interface.
>
> Both Chris and I did OpenWatcom ports. I did my port first. It seems he's
> removed his OpenWatcom port (djdisk.c). Although my port contains code for
> both compilers, the DJGPP code was reworked and may be more useful in the
> reworked format.
>
> http://groups.google.com/group/openwatcom.users.c_cpp/msg/dd21a94062d38ad8
> http://groups.google.com/group/openwatcom.users.c_cpp/msg/91921e7bfb09bcbc
>
>
> Rod Pemberton
>
--
Jim Michaels
for email, edit the address
- Raw text -